[DRE-maint] Processed: there are other things broken wiht graphql 2.0.18+ as well

2024-07-24 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://github.com/exAspArk/batch-loader/issues/87
Bug #1064754 [src:ruby-batch-loader] ruby-batch-loader: FTBFS: ERROR: Test 
"ruby3.1" failed: GraphQL::Error:
Set Bug forwarded-to-address to 
'https://github.com/exAspArk/batch-loader/issues/87'.

-- 
1064754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1076821: marked as done (ruby-ffaker: FTBFS: Tries to access Internet during build)

2024-07-24 Thread Debian Bug Tracking System
Your message dated Wed, 24 Jul 2024 09:34:53 +
with message-id 
and subject line Bug#1076821: fixed in ruby-ffaker 2.23.0-2
has caused the Debian Bug report #1076821,
regarding ruby-ffaker: FTBFS: Tries to access Internet during build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1076821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:ruby-ffaker
Version: 2.23.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

This package tries to access Internet during build:

SocketError: Failed to open TCP connection to dummyimage.com:443 (getaddrinfo: 
Temporary failure in name resolution)

For the full build log, please see:

https://buildd.debian.org/status/fetch.php?pkg=ruby-ffaker=all=2.23.0-1=1719910792=0

You can reproduce this easily by trying to build the package using sbuild 
unshare backend.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby-ffaker
Source-Version: 2.23.0-2
Done: Pirate Praveen 

We believe that the bug you reported is fixed in the latest version of
ruby-ffaker, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1076...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-ffaker package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 Jul 2024 17:55:19 +0900
Source: ruby-ffaker
Architecture: source
Version: 2.23.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Pirate Praveen 
Closes: 1076821
Changes:
 ruby-ffaker (2.23.0-2) unstable; urgency=medium
 .
   * Disable tests that need internet (Closes: #1076821)
Checksums-Sha1:
 a6978c66139d05ecae99bf1a20bc43c37cb3b709 2006 ruby-ffaker_2.23.0-2.dsc
 d9839413561ac20e7182de06f2fe683b64b955f8 4272 
ruby-ffaker_2.23.0-2.debian.tar.xz
 090929037f9eb8150ef6c5e626525cd82462 9128 
ruby-ffaker_2.23.0-2_amd64.buildinfo
Checksums-Sha256:
 be8d577c83bb16ed8b3cfe31fe5ad903fc16dd1dd29e54dd15d7d106380f8af7 2006 
ruby-ffaker_2.23.0-2.dsc
 820b53a723d27c0b76b97c30ad697dfd6446efc4d0440f997691ce05916cfc93 4272 
ruby-ffaker_2.23.0-2.debian.tar.xz
 439539800bae0fb44f1340540b368865a71a2b16f355ca3fae0c5be88e6fa615 9128 
ruby-ffaker_2.23.0-2_amd64.buildinfo
Files:
 8f10adec27e2baecf5f5c7c0e86973ae 2006 ruby optional ruby-ffaker_2.23.0-2.dsc
 8dbe7de5f4bedb4f68fcffaacd30cb48 4272 ruby optional 
ruby-ffaker_2.23.0-2.debian.tar.xz
 b62fb45fd020312eca3f450a416a1221 9128 ruby optional 
ruby-ffaker_2.23.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmagxS8ACgkQj1PgGTsp
S3WVLw//aEuK16ZAZvP3pvYxjIDOTuSqqB1qLhNltfizDEyEpE7CP4XmMzinHMCC
ulgvqcXN9SdOMjDdpQ+YZ7LvUYfwwRHpt1IfGO+53I/QkFDOdezNWRLMiwWQiizf
7IuYpt2i3UQF/mW2Z2Ba5QzhE4TRjSPEiVK1zwH62Uag0AfldtXwEXYnLPFvKclo
DzY/0xEk4ZmD9JTZZ5FV0aa87S0Fe/BkmK5r3/iDCguZu6+NrKcwYQidg9JAJxrX
5g/7hz42g4eIel1Y7ZeT7MSC7Fl8qvMQiyuR6kTstbnIC9/NAqVBEXi2fowC1fj/
m/uGd/RJLBryGglX55gDrphPiTq3wsxLFFwsXMW6NPKmH5X4MN7Y3L2PiR41IcbP
aAd6Du+YmWw/6LE7q9EQhA6gWqtPIcevcRgVrlCl8a7iZQn2noBtN20hUxLp0wvZ
0b5hwE9n68f1dPM5yeOzrOoqxzFJbEBdSiuroZcTq1zfeMfXIY2MBx471FySxyFg
6adZ9/3Z6CY0MiZX/eyrZrjO55k1U2w3vVXSx8QCfTTTwlyoUT3FYBFBjd96TaDc
uwhxiIB7xHezNVfxus6OV0pptSfLTnRSXv0O7o5T+zpu+Z3c5hZXYDV/HIrLKc30
DfWT8WFb+Yb4PhN/pJn5wSu0eKF8G66HLlt780YsfPbhrRB5hNs=
=cgEW
-END PGP SIGNATURE-



pgpOAWTFrifNQ.pgp
Description: PGP signature
--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Bug#1076821 marked as pending in ruby-ffaker

2024-07-24 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1076821 [src:ruby-ffaker] ruby-ffaker: FTBFS: Tries to access Internet 
during build
Added tag(s) pending.

-- 
1076821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: fixed 972941 in jekyll/3.9.0+dfsg-1

2024-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 972941 jekyll/3.9.0+dfsg-1
Bug #972941 {Done: Cédric Boutillier } [jekyll] jekyll: 
complains about missing kramdown-parser-gfm
Marked as fixed in versions jekyll/3.9.0+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1048945: marked as done (jekyll: Fails to build source after successful build)

2024-07-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Jul 2024 17:34:17 +
with message-id 
and subject line Bug#1048945: fixed in jekyll 4.3.2+dfsg-2
has caused the Debian Bug report #1048945,
regarding jekyll: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1048945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jekyll
Version: 4.3.1+dfsg-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> 
> 
> dpkg-buildpackage: info: source package jekyll
> dpkg-buildpackage: info: source version 4.3.1+dfsg-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Antonio Terceiro 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=ruby --with ruby
>dh_auto_clean -O--buildsystem=ruby
>   dh_ruby --clean
> W: XS-Ruby-Versions is deprecated, and will be ignored
>dh_autoreconf_clean -O--buildsystem=ruby
>dh_clean -O--buildsystem=ruby
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building jekyll using existing 
> ./jekyll_4.3.1+dfsg.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Cache/b7/9606fb3afea5bd1609ed40b622142f1c98125abcfe89a76a661b0e8e343910
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/04/8a801d42cbb15d352dfce6083417a36e0854348bedf08b61fecd08c5bcc6a5
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/05/3f54462c6cc89278c9c13e4bafbde670d5e8aeb4a1fd5feb6c5d138ace3196
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/0c/2d6e4d808d3342c2ec97d963f30777df289544869c013d00e6d327bb8debd2
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/0d/ec503d94d06e436baeb0f38288d0378e6b0dfc626fdfcf3ce954cf8c886509
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/14/d8491dd1d1b74611d21a072dfa520d3aceb8e3fcc4a0eafdb7a54534112ac7
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/16/fdf64059b9c3a03a70583538c96a4cd85e851d8814135f7ed240d06e5512e4
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/18/3d68312ffcffd3f0006669f4c504812f336f5b9889036e5ab5dfc3a1f17493
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/source/.jekyll-cache/Jekyll/Cache/Jekyll--Converters--Markdown/18/7b0d387fb29a2a8f9b2e94d6d5f53cc9a71b3d93d0adea45a6ce0ada9a
>  has no final newline (either original or modified version)
> dpkg-source: warning: file 
> jekyll-4.3.1+dfsg/test/so

[DRE-maint] Bug#1030465: marked as done (ruby-jekyll-asciidoc: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: ::Jekyll.configuration fixture_site_params name)

2024-07-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Jul 2024 17:34:17 +
with message-id 
and subject line Bug#1030465: fixed in jekyll 4.3.2+dfsg-2
has caused the Debian Bug report #1030465,
regarding ruby-jekyll-asciidoc: FTBFS: ERROR: Test "ruby3.1" failed: 
Failure/Error: ::Jekyll.configuration fixture_site_params name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jekyll-asciidoc
Version: 3.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>   Failure/Error: ::Jekyll.configuration fixture_site_params name
> 
>   Psych::DisallowedClass:
> Tried to load unspecified class: Symbol
>   # (eval):2:in `symbol'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/utils.rb:321:in
>  `safe_load_yaml'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/utils.rb:330:in
>  `safe_load_yaml_file'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/configuration.rb:129:in
>  `safe_load_file'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/configuration.rb:167:in
>  `read_config_file'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/configuration.rb:198:in
>  `block in read_config_files'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/configuration.rb:195:in
>  `each'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll/configuration.rb:195:in
>  `read_config_files'
>   # 
> /usr/share/rubygems-integration/all/gems/jekyll-4.3.1/lib/jekyll.rb:116:in 
> `configuration'
>   # ./spec/jekyll-asciidoc_spec.rb:5:in `block (2 levels) in  (required)>'
>   # ./spec/jekyll-asciidoc_spec.rb:9:in `block (2 levels) in  (required)>'
>   # ./spec/jekyll-asciidoc_spec.rb:1214:in `block (3 levels) in  (required)>'
> 
> Finished in 0.73097 seconds (files took 0.48283 seconds to load)
> 131 examples, 77 failures
> 
> Failed examples:
> 
> rspec ./spec/jekyll-asciidoc_spec.rb:150 # Jekyll::AsciiDoc parse YAML value 
> should parse string as YAML value
> rspec ./spec/jekyll-asciidoc_spec.rb:333 # Jekyll::AsciiDoc alternate page 
> attribute prefix should strip trailing hyphen from page attribute prefix 
> config value
> rspec ./spec/jekyll-asciidoc_spec.rb:338 # Jekyll::AsciiDoc alternate page 
> attribute prefix should recognize page attributes with alternate page 
> attribute prefix
> rspec ./spec/jekyll-asciidoc_spec.rb:357 # Jekyll::AsciiDoc blank page 
> attribute prefix should coerce null value for page attribute prefix to empty 
> string
> rspec ./spec/jekyll-asciidoc_spec.rb:362 # Jekyll::AsciiDoc blank page 
> attribute prefix should recognize page attributes with no page attribute 
> prefix
> rspec ./spec/jekyll-asciidoc_spec.rb:381 # Jekyll::AsciiDoc basic site should 
> add an implicit YAML header to a plain AsciiDoc file
> rspec ./spec/jekyll-asciidoc_spec.rb:386 # Jekyll::AsciiDoc basic site should 
> convert a plain AsciiDoc file
> rspec ./spec/jekyll-asciidoc_spec.rb:393 # Jekyll::AsciiDoc basic site should 
> promote AsciiDoc document title to page title
> rspec ./spec/jekyll-asciidoc_spec.rb:400 # Jekyll::AsciiDoc basic site should 
> convert an AsciiDoc with no doctitle or AsciiDoc header
> rspec ./spec/jekyll-asciidoc_spec.rb:411 # Jekyll::AsciiDoc basic site should 
> convert an AsciiDoc that has an AsciiDoc header, but no doctitle
> rspec ./spec/jekyll-asciidoc_spec.rb:423 # Jekyll::AsciiDoc basic site should 
> report an AsciiDoc file with a front matter header as having a YAML header
> rspec ./spec/jekyll-asciidoc_spec.rb:428 # Jekyll::AsciiDoc basic site should 
> convert an AsciiDoc file with a front matter header
> rspec ./spec/jekyll-asciidoc_spec.rb:436 # Jekyll::AsciiDoc basic site should 
> convert an AsciiDoc file that has only an AsciiDoc header, no body
> rspec ./spec/jekyll-asciidoc_spec.rb:444 # Jekyll::AsciiDoc basic site should 
> convert an AsciiDoc file that has only a front matter header, no body
> rspec ./spec/jekyll-asc

[DRE-maint] Processed: Bug#1048945 marked as pending in jekyll

2024-07-23 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1048945 [src:jekyll] jekyll: Fails to build source after successful build
Added tag(s) pending.

-- 
1048945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 942596

2024-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 942596
Bug #942596 [jekyll] Patch out bundler install call to not install dependencies 
via bundler
Marked Bug as done
> fixed 942596 jekyll/4.3.1+dfsg-1
Bug #942596 {Done: Cédric Boutillier } [jekyll] Patch out 
bundler install call to not install dependencies via bundler
Marked as fixed in versions jekyll/4.3.1+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
942596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed (with 1 error): closing 972941

2024-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 972941
Bug #972941 [jekyll] jekyll: complains about missing kramdown-parser-gfm
Marked Bug as done
> fixed jekyll/3.9.0+dfsg-1
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 1010758

2024-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1010758
Bug #1010758 [jekyll] jekyll: Should jekyll-theme-minima be Recommends rather 
than Suggests
Marked Bug as done
> fixed 1010758 jekyll/4.3.1+dfsg-1
Bug #1010758 {Done: Cédric Boutillier } [jekyll] jekyll: 
Should jekyll-theme-minima be Recommends rather than Suggests
Marked as fixed in versions jekyll/4.3.1+dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: reassign 1030465 to src:jekyll

2024-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1030465 src:jekyll
Bug #1030465 [src:ruby-jekyll-asciidoc] ruby-jekyll-asciidoc: FTBFS: ERROR: 
Test "ruby3.1" failed: Failure/Error: ::Jekyll.configuration 
fixture_site_params name
Bug reassigned from package 'src:ruby-jekyll-asciidoc' to 'src:jekyll'.
No longer marked as found in versions ruby-jekyll-asciidoc/3.0.0-2.
Ignoring request to alter fixed versions of bug #1030465 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1030465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby3.3: CVE-2024-39908

2024-07-22 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2 -3
Bug #1076766 [src:ruby3.3] ruby3.3: CVE-2024-39908
Bug 1076766 cloned as bugs 1076767-1076768
> reassign -2 ruby3.2 3.2.3-1
Bug #1076767 [src:ruby3.3] ruby3.3: CVE-2024-39908
Bug reassigned from package 'src:ruby3.3' to 'ruby3.2'.
No longer marked as found in versions ruby3.3/3.3.4-2.
Ignoring request to alter fixed versions of bug #1076767 to the same values 
previously set
Bug #1076767 [ruby3.2] ruby3.3: CVE-2024-39908
Marked as found in versions ruby3.2/3.2.3-1.
> retitle -2 ruby3.2: CVE-2024-39908
Bug #1076767 [ruby3.2] ruby3.3: CVE-2024-39908
Changed Bug title to 'ruby3.2: CVE-2024-39908' from 'ruby3.3: CVE-2024-39908'.
> reassign -3 ruby3.1 3.1.2-8.3
Bug #1076768 [src:ruby3.3] ruby3.3: CVE-2024-39908
Bug reassigned from package 'src:ruby3.3' to 'ruby3.1'.
No longer marked as found in versions ruby3.3/3.3.4-2.
Ignoring request to alter fixed versions of bug #1076768 to the same values 
previously set
Bug #1076768 [ruby3.1] ruby3.3: CVE-2024-39908
Marked as found in versions ruby3.1/3.1.2-8.3.
> retitle -3 ruby3.1: CVE-2024-39908
Bug #1076768 [ruby3.1] ruby3.3: CVE-2024-39908
Changed Bug title to 'ruby3.1: CVE-2024-39908' from 'ruby3.3: CVE-2024-39908'.

-- 
1076766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076766
1076767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076767
1076768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 1058426

2024-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1058426
Bug #1058426 [src:ruby-rugged] ruby-rugged: FTBFS: rugged_allocator.c:78:19: 
error: ‘git_allocator’ has no member named ‘gcalloc’; did you mean ‘gmalloc’?
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1058426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Re: Bug#1076659: ruby-gsl: FTBFS with gsl/2.8: bspline.c:101:37: error: ‘gsl_bspline_workspace’ has no member named ‘k’

2024-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1076659 [src:ruby-gsl] ruby-gsl: FTBFS with gsl/2.8: bspline.c:101:37: 
error: ‘gsl_bspline_workspace’ has no member named ‘k’
Added tag(s) patch.

-- 
1076659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby-gsl: FTBFS with gsl/2.8: bspline.c:101:37: error: ‘gsl_bspline_workspace’ has no member named ‘k’

2024-07-21 Thread Debian Bug Tracking System
Processing control commands:

> block 1072036 with -1
Bug #1072036 [release.debian.org] release.debian.org: Transition for gsl-2.8 / 
libgsl28
1072036 was blocked by: 1076470
1072036 was not blocking any bugs.
Added blocking bug(s) of 1072036: 1076659

-- 
1072036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072036
1076659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 1015307

2024-07-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1015307
Bug #1015307 [src:ruby-atomic] ruby-atomic: FTBFS: make: *** [debian/rules:15: 
binary] Error 25
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1043954: marked as done (asciidoctor: Fails to build source after successful build)

2024-07-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jul 2024 14:34:56 +
with message-id 
and subject line Bug#1043954: fixed in asciidoctor 2.0.23-1
has caused the Debian Bug report #1043954,
regarding asciidoctor: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1043954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asciidoctor
Version: 2.0.20-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> --
> 
> dpkg-buildpackage: info: source package asciidoctor
> dpkg-buildpackage: info: source version 2.0.20-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Cédric Boutillier 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=ruby --with ruby
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
>   dh_ruby --clean
> rm -rf doc
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=ruby
>dh_clean -O--buildsystem=ruby
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building asciidoctor using existing 
> ./asciidoctor_2.0.20.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file asciidoctor-2.0.20/README-de.html has no final 
> newline (either original or modified version)
> dpkg-source: warning: file asciidoctor-2.0.20/README-fr.html has no final 
> newline (either original or modified version)
> dpkg-source: warning: file asciidoctor-2.0.20/README-jp.html has no final 
> newline (either original or modified version)
> dpkg-source: warning: file asciidoctor-2.0.20/README-zh_CN.html has no final 
> newline (either original or modified version)
> dpkg-source: warning: file asciidoctor-2.0.20/README.html has no final 
> newline (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  asciidoctor-2.0.20/README-de.html
>  asciidoctor-2.0.20/README-fr.html
>  asciidoctor-2.0.20/README-jp.html
>  asciidoctor-2.0.20/README-zh_CN.html
>  asciidoctor-2.0.20/README.html
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/asciidoctor_2.0.20-1.diff.C4Dryr
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/asciidoctor_2.0.20-1_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: asciidoctor
Source-Version: 2.0.23-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
asciidoctor, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which

[DRE-maint] Bug#1073352: marked as done (ruby-libxml: FTBFS: ruby_xml_encoding.h:12:27: error: unknown type name ‘xmlChar’)

2024-07-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jul 2024 11:20:15 +
with message-id 
and subject line Bug#1073352: fixed in ruby-libxml 5.0.3-1
has caused the Debian Bug report #1073352,
regarding ruby-libxml: FTBFS: ruby_xml_encoding.h:12:27: error: unknown type 
name ‘xmlChar’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-libxml
Version: 3.2.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> gcc -fdebug-prefix-map=/<>=. -I. 
> -I/usr/include/x86_64-linux-gnu/ruby-3.1.0 
> -I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. 
> -I/usr/include/libxml2 -DRUBY_EXTCONF_H=\"extconf.h\" -Wdate-time 
> -D_FORTIFY_SOURCE=2   -fPIC -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=BUILDDIR=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fPIC  -o libxml.o -c libxml.c
> In file included from ruby_libxml.h:13,
>  from libxml.c:1:
> ruby_xml_encoding.h:12:27: error: unknown type name ‘xmlChar’
>12 | VALUE rxml_new_cstr(const xmlChar* xstr, const xmlChar* xencoding);
>   |   ^~~
> ruby_xml_encoding.h:12:48: error: unknown type name ‘xmlChar’
>12 | VALUE rxml_new_cstr(const xmlChar* xstr, const xmlChar* xencoding);
>   |^~~
> ruby_xml_encoding.h:13:31: error: unknown type name ‘xmlChar’
>13 | VALUE rxml_new_cstr_len(const xmlChar* xstr, const long length, const 
> xmlChar* xencoding);
>   |   ^~~
> ruby_xml_encoding.h:13:71: error: unknown type name ‘xmlChar’
>13 | VALUE rxml_new_cstr_len(const xmlChar* xstr, const long length, const 
> xmlChar* xencoding);
>   |   
> ^~~
> ruby_xml_encoding.h:15:60: error: unknown type name ‘xmlCharEncoding’
>15 | rb_encoding* rxml_xml_encoding_to_rb_encoding(VALUE klass, 
> xmlCharEncoding xmlEncoding);
>   |
> ^~~
> ruby_xml_encoding.h:16:41: error: unknown type name ‘xmlChar’
>16 | rb_encoding* rxml_figure_encoding(const xmlChar* xencoding);
>   | ^~~
> In file included from ruby_libxml.h:14:
> ruby_xml_attributes.h:9:27: error: unknown type name ‘xmlNodePtr’
> 9 | VALUE rxml_attributes_new(xmlNodePtr xnode);
>   |   ^~
> In file included from ruby_libxml.h:15:
> ruby_xml_attr.h:9:22: error: unknown type name ‘xmlAttrPtr’
> 9 | VALUE rxml_attr_wrap(xmlAttrPtr xattr);
>   |  ^~
> In file included from ruby_libxml.h:16:
> ruby_xml_attr_decl.h:9:27: error: unknown type name ‘xmlAttributePtr’
> 9 | VALUE rxml_attr_decl_wrap(xmlAttributePtr xattribute);
>   |   ^~~
> In file included from ruby_libxml.h:17:
> ruby_xml_document.h:8:26: error: unknown type name ‘xmlDocPtr’; did you mean 
> ‘xmlErrorPtr’?
> 8 | VALUE rxml_document_wrap(xmlDocPtr xnode);
>   |  ^
>   |  xmlErrorPtr
> ruby_xml_document.h:10:9: error: unknown type name ‘xmlChar’
>10 | typedef xmlChar * xmlCharPtr;
>   | ^~~
> In file included from ruby_libxml.h:18:
> ruby_xml_node.h:9:21: error: unknown type name ‘xmlNodePtr’
> 9 | void rxml_node_mark(xmlNodePtr xnode);
>   | ^~
> ruby_xml_node.h:10:22: error: unknown type name ‘xmlNodePtr’
>10 | VALUE rxml_node_wrap(xmlNodePtr xnode);
>   |  ^~
> ruby_xml_node.h:11:23: error: unknown type name ‘xmlNodePtr’
>11 | void rxml_node_manage(xmlNodePtr xnode, VALUE node);
>   |   ^~
> ruby_xml_node.h:12:25: error: unknown type name ‘xmlNodePtr’
>12 | void rxml_node_unmanage(xmlNodePtr xnode, VALUE node);
>   | 

[DRE-maint] Bug#1047895: marked as done (ruby-libxml: Fails to build source after successful build)

2024-07-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jul 2024 11:20:15 +
with message-id 
and subject line Bug#1047895: fixed in ruby-libxml 5.0.3-1
has caused the Debian Bug report #1047895,
regarding ruby-libxml: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1047895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-libxml
Version: 3.2.4-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> -
> 
> dpkg-buildpackage: info: source package ruby-libxml
> dpkg-buildpackage: info: source version 3.2.4-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Lucas Kanashiro 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=ruby --with ruby
>dh_auto_clean -O--buildsystem=ruby
>   dh_ruby --clean
>dh_autoreconf_clean -O--buildsystem=ruby
>dh_clean -O--buildsystem=ruby
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ruby-libxml using existing 
> ./ruby-libxml_3.2.4.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  ruby-libxml-3.2.4/test/test.xml
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/ruby-libxml_3.2.4-2.diff.vI2nPR
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/ruby-libxml_3.2.4-2_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-libxml
Source-Version: 5.0.3-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-libxml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1047...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-libxml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jun 2024 10:22:16 +0200
Source: ruby-libxml
Architecture: source
Version: 5.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1047895 1072017 1073352
Changes:
 ruby-libxml (5.0.3-1) unstable; urgency=medium
 .
   * New upstream version 5.0.3
 + compatibility with libxml2 v2.12+ (Closes: #1073352, #1072017)
   * update how test suite is run
   * Re

[DRE-maint] Bug#1072017: marked as done (ruby-libxml: new upstream release, addressing test failures with libxml2 >= 2.12)

2024-07-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Jul 2024 11:20:15 +
with message-id 
and subject line Bug#1072017: fixed in ruby-libxml 5.0.3-1
has caused the Debian Bug report #1072017,
regarding ruby-libxml: new upstream release, addressing test failures with 
libxml2 >= 2.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1072017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-libxml
Version: 3.2.4-2
X-Debbugs-Cc: debian-xml-sgml-pkgs at alioth-lists.debian.net

Hi,

libxml2 has been updated to upstream 2.12.7 release and the
autopkgtest shows regressions[1] regarding ruby-libxml:

47s 1) Failure:
47s TestSaxParser#test_parse_seg_fail
[/tmp/autopkgtest-lxc.00ga17my/downtmp/build.LIY/src/test/test_sax_parser.rb:321]:
47s --- expected
47s +++ actual
47s @@ -1 +1 @@
47s -"Fatal error: xmlParseEntityRef: no name at :5."
47s +"Fatal error: xmlParseEntityRef: no name at :4."
47s
47s
47s 2) Failure:
47s TestParser#test_file_encoding
[/tmp/autopkgtest-lxc.00ga17my/downtmp/build.LIY/src/test/test_parser.rb:66]:
47s Expected nil to be truthy.
47s
47s 3) Failure:
47s TestParser#test_bad_xml
[/tmp/autopkgtest-lxc.00ga17my/downtmp/build.LIY/src/test/test_parser.rb:286]:
47s --- expected
47s +++ actual
47s @@ -1 +1 @@
47s -"Fatal error: Extra content at the end of the document at :1."
47s +"Fatal error: Couldn't find end of Start Tag ruby_array line 1 at :1."
47s
47s
47s 4) Failure:
47s TestReader#test_string_encoding
[/tmp/autopkgtest-lxc.00ga17my/downtmp/build.LIY/src/test/test_reader.rb:362]:
47s Expected: 10
47s Actual: 0
47s
47s 353 runs, 42311 assertions, 4 failures, 0 errors, 0 skips

Upstream has fixed a few issues with libxml2 2.12.x in 5.0.x release.
It would be nice if upstream release or some patch works can be
considered to help unblock the migration of new libxml2. I would give
it a try on patching but I'm unfortunately not a Ruby expert.

[1]https://ci.debian.net/packages/r/ruby-libxml/testing/amd64/47035876/
--- End Message ---
--- Begin Message ---
Source: ruby-libxml
Source-Version: 5.0.3-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-libxml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-libxml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jun 2024 10:22:16 +0200
Source: ruby-libxml
Architecture: source
Version: 5.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1047895 1072017 1073352
Changes:
 ruby-libxml (5.0.3-1) unstable; urgency=medium
 .
   * New upstream version 5.0.3
 + compatibility with libxml2 v2.12+ (Closes: #1073352, #1072017)
   * update how test suite is run
   * Refresh 0003-Skip-test-relying-on-internet-connection.patch
   * Add 0004-Skip-failing-tests-v5.patch to skip temporarily failing tests
   * Remove test.xml when cleaning (Closes: #1047895)
Checksums-Sha1:
 4afb10415d804a6e89157fd20357c1c5f1654aa1 1497 ruby-libxml_5.0.3-1.dsc
 6f7c93cad141abcf98ccc51e3624c98c3e98ff8f 367866 ruby-libxml_5.0.3.orig.tar.gz
 0e80535a8a1f81c5957cce2ac8bb2e04cdedbce8 8332 ruby-libxml_5.0.3-1.debian.tar.xz
 29fd0ffeceb18acfb78b0a6d32ac2141e75160ff 8873 
ruby-libxml_5.0.3-1_amd64.buildinfo
Checksums-Sha256:
 440f91200c7ae261550363ee9f45d5f86579dfce9a0654a345712cb53c0af710 1497 
ruby-libxml_5.0.3-1.dsc
 2cf2bdae2a9720d961f426d698533350ad9b03e0293ed363d298dab8773ab1df 367866 
ruby-libxml_5.0.3.orig.tar.gz
 b0848180b872018822ac6454ed2a7b37545b12c2c4527615bc5c51fab198abeb 8332 
ruby-libxml_5.0.3-1.debian.tar.xz
 16e99bd9ce6300d1156bd6e34e2734f98d422462f3e3082870e3a1b7be24ecd4 8873 
ruby-libxml_5.0.3-1_amd64.buildinfo
Files:
 7f6b2313061628878ac5d6f12f06bc4f 1497 ruby optional ruby-libxml_5.0.3-1.dsc
 566e3f28f1fafe581319db2f6a6ce147 367866 ruby optional 
ruby-libxml_5.0.3.orig.tar.gz
 14f2f1bab70385b51d9645b279987df5 8332 ruby 

[DRE-maint] Processed: Bug#1047895 marked as pending in ruby-libxml

2024-07-18 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1047895 [src:ruby-libxml] ruby-libxml: Fails to build source after 
successful build
Added tag(s) pending.

-- 
1047895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1073364: marked as done (ruby-ronn: FTBFS: ERROR: Test "ruby3.1" failed.)

2024-07-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 16:29:29 +
with message-id 
and subject line Bug#1073364: fixed in ruby-ronn 0.10.1-1
has caused the Debian Bug report #1073364,
regarding ruby-ronn: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ronn
Version: 0.9.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/tmp/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/tmp/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"ronn-ng\"
> mv Gemfile.lock ./.gem2deb.Gemfile.lock
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/tmp/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/tmp/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 debian/ruby-tests.rb
> mv Gemfile.lock ./.gem2deb.Gemfile.lock
> Loaded suite debian/ruby-tests
> Started
> .F
> ===
> Failure: test_angle_bracket_syntax_HTML(RonnTest):
>   --- /<>/test/angle_bracket_syntax.html 2020-04-09 
> 22:36:44.0 +
>   +++ /<>/test/angle_bracket_syntax.html.wrong   2024-06-16 
> 12:15:52.503318090 +
>   @@ -13,5 +13,5 @@
>
>or when WORD is enclosed in backticks.
>
>   -or when WORD has a  or .
>   +or when WORD has a  or 
> .
>
>   .
> /<>/test/test_ronn.rb:43:in `flunk_with_diff'
> /<>/test/test_ronn.rb:96:in `block (2 levels) in 
> '
> ===
> 
> Finished in 9.947068359 seconds.
> ---
> 66 tests, 113 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
> notifications
> 98.4848% passed
> ---
> 6.64 tests/s, 11.36 assertions/s
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.1" failed.


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/ruby-ronn_0.9.1-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
S

[DRE-maint] Bug#1069258: marked as done (ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read)

2024-07-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 16:29:16 +
with message-id 
and subject line Bug#1069258: fixed in ruby-curb 1.0.5-2
has caused the Debian Bug report #1069258,
regarding ruby-curb: test regression with curl 8.7.1: client read function EOF 
fail, only only 4/5 of needed bytes read
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-curb
Version: 1.0.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ruby-curb=amd64=1.0.5-1%2Bb3=1712538836=0

┌──┐
│ Run tests for ruby3.1 from debian/ruby-tests.rake│
└──┘

RUBYLIB=. 
GEM_PATH=/<>/debian/ruby-curb/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
 ruby3.1 -S rake --rakelibdir /gem2deb-nonexistent -f debian/ruby-tests.rake
/<>/tests/tc_curl_multi.rb:189: warning: assigned but unused 
variable - in_file_stack
Loaded suite 
/usr/share/rubygems-integration/all/gems/rake-13.2.0/lib/rake/rake_test_loader
Started
.E
===
Error: test_easy_http_verbs(TestCurbCurlEasy): Curl::Err::ReadError: Failed to 
open/read local data from file/application: client read function EOF fail, only 
only 4/5 of needed bytes read
/<>/lib/curl/easy.rb:80:in `perform'
/<>/tests/tc_curl_easy.rb:1064:in `http_put'
/<>/tests/tc_curl_easy.rb:1064:in `test_easy_http_verbs'
 1061: assert_equal "POST\n", curl.body_str
 1062: curl.http('PURGE')
 1063: assert_equal 'PURGE', curl.body_str
  => 1064: curl.http_put('hello')
 1065: assert_equal "PUT\nhello", curl.body_str
 1066: curl.http('COPY')
 1067: assert_equal 'COPY', curl.body_str
===
E
===
Error: test_put_data(TestCurbCurlEasy): Curl::Err::ReadError: Failed to 
open/read local data from file/application: client read function EOF fail, only 
only 6/7 of needed bytes read
/<>/lib/curl/easy.rb:80:in `perform'
/<>/tests/tc_curl_easy.rb:885:in `test_put_data'
 882: curl = Curl::Easy.new(TestServlet.url)
 883: curl.put_data = 'message'
 884: 
  => 885: curl.perform
 886: 
 887: assert_match(/^PUT/, curl.body_str)
 888: assert_match(/message$/, curl.body_str)
===
E
===
Error: test_put_data_null_bytes(TestCurbCurlEasy): Curl::Err::ReadError: Failed 
to open/read local data from file/application: client read function EOF fail, 
only only 2/3 of needed bytes read
/<>/lib/curl/easy.rb:80:in `perform'
/<>/tests/tc_curl_easy.rb:896:in `test_put_data_null_bytes'
 893: curl = Curl::Easy.new(TestServlet.url)
 894: curl.put_data = "a\0b"
 895:  
  => 896: curl.perform
 897: 
 898: assert_match(/^PUT/, curl.body_str)
 899: assert_match("a\0b", curl.body_str)
===
.E
===
Error: test_put_remote(TestCurbCurlEasy): Curl::Err::ReadError: Failed to 
open/read local data from file/application: client read function EOF fail, only 
only 6/7 of needed bytes read
/<>/lib/curl/easy.rb:80:in `perform'
/<>/tests/tc_curl_easy.rb:873:in `http_put'
/<>/tests/tc_curl_easy.rb:873:in `test_put_remote'
 870:   def test_put_remote
 871: curl = Curl::Easy.new(TestServlet.url)
 872: curl.headers['Con

[DRE-maint] Bug#1063630: marked as done (ronn: Please package new upstream version)

2024-07-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 16:29:29 +
with message-id 
and subject line Bug#1063630: fixed in ruby-ronn 0.10.1-1
has caused the Debian Bug report #1063630,
regarding ronn: Please package new upstream version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ronn
Version: 0.9.1-3
Severity: wishlist

Dear Maintainer,

after some years without releases upstream recently released a new 
version.
I would appreciate it, if the new version would be packaged for debian.

Best regards,
Martin

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

Kernel: Linux 6.1.0-17-amd64 (SMP w/4 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

Versions of packages ronn depends on:
ii  ruby   1:3.1
ii  ruby-ronn  0.9.1-3

ronn recommends no packages.

ronn suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-ronn
Source-Version: 0.10.1-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-ronn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-ronn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jul 2024 17:06:55 +0200
Source: ruby-ronn
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1063355 1063630 1073364
Changes:
 ruby-ronn (0.10.1-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Cédric Boutillier ]
   * New upstream version 0.10.1 (Closes: #1063630)
 + -m and -date options work without PAGER set (Closes: #1063355)
 + libxml 2.10+ compatibility for  and  angle-bracket
   syntax (Closes: #1073364)
Checksums-Sha1:
 06e4e655eea08174714809df2e69b4937204b3a8 1581 ruby-ronn_0.10.1-1.dsc
 ebe933c9286d836186e7bb0d39d2d78cef494151 78696 ruby-ronn_0.10.1.orig.tar.gz
 423d60f06f74ae1f94c33cb8e2574d88065c2c48 16648 ruby-ronn_0.10.1-1.debian.tar.xz
 797a575ab680fdf02cd20bd35a61ceb071393992 8885 
ruby-ronn_0.10.1-1_amd64.buildinfo
Checksums-Sha256:
 ded7b56158ba9b8f505fdafce6bbf1e1c7200297ec2c104042be9b8801cc2be8 1581 
ruby-ronn_0.10.1-1.dsc
 180f18015ce01be1d10c24e13414134363d56f9efb741fda460358bb67d96684 78696 
ruby-ronn_0.10.1.orig.tar.gz
 6bbf205eb579210b869683b7eba59155d4dc3815e495430281f726d4af3bcebc 16648 
ruby-ronn_0.10.1-1.debian.tar.xz
 083278f8770e3ab46ed4e3d738fd2009655176c8311f0b01756ac740badbd82f 8885 
ruby-ronn_0.10.1-1_amd64.buildinfo
Files:
 b625da1cf1a404ff9ba5a7e94f7fe345 1581 ruby optional ruby-ronn_0.10.1-1.dsc
 a4bddf3ebddbcc47ecbd9225f3f969e8 78696 ruby optional 
ruby-ronn_0.10.1.orig.tar.gz
 42b552f7b9b0a7d48a9d090251faf916 16648 ruby optional 
ruby-ronn_0.10.1-1.debian.tar.xz
 f13e984222741fb6503c1688650fdf03 8885 ruby optional 
ruby-ronn_0.10.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCZpfibgAKCRBSaZq2P58r
w1UcAP9VdStk38AfU/mF2fj9TGnugZGxLMeWQLUXMJHSqdiWbgEAlUTJZkAcxA81
0iiKRNjSHqcH8DJQf0TgkEJr/agzMwo=
=6biG
-END PGP SIGNATURE-



pgpXhcrKatEg4.pgp
Description: PGP signature
--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1063355: marked as done (ronn: -m and --date options do not work)

2024-07-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 16:29:29 +
with message-id 
and subject line Bug#1063355: fixed in ruby-ronn 0.10.1-1
has caused the Debian Bug report #1063355,
regarding ronn: -m and --date options do not work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ronn
Version: 0.9.1-3
Severity: normal
X-Debbugs-Cc: rstan...@rsiny.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Two problems:

With PAGER and MAMPAGER Not set:
ronn -m --style=man sample.3.ronn
more: invalid option -- 'i'
Try 'more --help' for more information.

--date option does not work trying all options:
--date="2024-02-06"
--date=2024-02-06
--date=`date "+%Y-%m-%d"`

mtime file in same directory with one line:
2024-02-06

Output file only displays:
February 2024


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
As listed above, both options failed.

   * What was the outcome of this action?
I could not use either option

   * What outcome did you expect instead?
more command should have worked without the 'i' option, Typo?.
--date option should have replaced "February 2024" with "2024-02-06"

*** End of the template - remove these template lines ***


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

Kernel: Linux 6.6.13-amd64 (SMP w/16 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

Versions of packages ronn depends on:
ii  ruby   1:3.1
ii  ruby-ronn  0.9.1-3

ronn recommends no packages.

ronn suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-ronn
Source-Version: 0.10.1-1
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-ronn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-ronn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Jul 2024 17:06:55 +0200
Source: ruby-ronn
Architecture: source
Version: 0.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1063355 1063630 1073364
Changes:
 ruby-ronn (0.10.1-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.2, no changes needed.
 .
   [ Cédric Boutillier ]
   * New upstream version 0.10.1 (Closes: #1063630)
 + -m and -date options work without PAGER set (Closes: #1063355)
 + libxml 2.10+ compatibility for  and  angle-bracket
   syntax (Closes: #1073364)
Checksums-Sha1:
 06e4e655eea08174714809df2e69b4937204b3a8 1581 ruby-ronn_0.10.1-1.dsc
 ebe933c9286d836186e7bb0d39d2d78cef494151 78696 ruby-ronn_0.10.1.orig.tar.gz
 423d60f06f74ae1f94c33cb8e2574d88065c2c48 16648 ruby-ronn_0.10.1-1.debian.tar.xz
 797a575ab680fdf02cd20bd35a61ceb071393992 8885 
ruby-ronn_0.10.1-1_amd64.buildinfo
Checksums-Sha256:
 ded7b56158ba9b8f505fdafce6bbf1e1c7200297ec2c104042be9b8801cc2be8 1581 
ruby-ronn_0.10.1-1.dsc
 180f18015ce01be1d10c24e13414134363d56f9efb741fda460358bb67d96684 78696 
ruby-ronn_0.10.1.orig.tar.gz
 6bbf205eb579210b869683b7eba59155d4dc3815e495430281f726d4af3bcebc 16648 
ruby-ronn_0.10.1-1.debian.tar.xz
 083278f8770e3ab46ed4e3d738fd2009655176c8311f0b01756ac740badbd82f 8885 
ruby-ronn_0.10.1-1_amd64.buildinfo
Files:
 b625da1cf1a404ff9ba5a7e94f7fe345 1581 ruby optional ruby-ronn_0.10.1-1.dsc
 a4bddf3ebddbcc47ecbd9225f3f969e8 78696 ruby optional 
ruby-ronn_0.10.1.orig.tar.gz
 42b552f7b9b0a7d48a9d090251faf916 16648 ruby optional 
ruby-ronn_0.10.1-1.debian.tar.xz
 f13e984222741fb6503c1688650fdf03 8885 ruby optional 
ruby-ronn_0.10.1-1_a

[DRE-maint] Processed: Bug#1069258 marked as pending in ruby-curb

2024-07-17 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1069258 [src:ruby-curb] ruby-curb: test regression with curl 8.7.1: client 
read function EOF fail, only only 4/5 of needed bytes read
Added tag(s) pending.

-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 964322

2024-07-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 964322
Bug #964322 {Done: Cédric Boutillier } [ronn] ronn 0.9.1 
does not render code blocks properly
Bug 964322 is already marked as done; not doing anything.
> fixed 964322 0.10.1-1
Bug #964322 {Done: Cédric Boutillier } [ronn] ronn 0.9.1 
does not render code blocks properly
There is no source info for the package 'ronn' at version '0.10.1-1' with 
architecture ''
Unable to make a source version for version '0.10.1-1'
Marked as fixed in versions 0.10.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
964322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 964322

2024-07-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 964322
Bug #964322 [ronn] ronn 0.9.1 does not render code blocks properly
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
964322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: bug 1073364 is forwarded to https://github.com/apjanke/ronn-ng/issues/102

2024-07-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1073364 https://github.com/apjanke/ronn-ng/issues/102
Bug #1073364 [src:ruby-ronn] ruby-ronn: FTBFS: ERROR: Test "ruby3.1" failed.
Set Bug forwarded-to-address to 'https://github.com/apjanke/ronn-ng/issues/102'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1073364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1073357: marked as done (ruby-mechanize: FTBFS: ERROR: Test "ruby3.1" failed.)

2024-07-17 Thread Debian Bug Tracking System
Your message dated Wed, 17 Jul 2024 14:53:13 +
with message-id 
and subject line Bug#1073357: fixed in ruby-mechanize 2.10.1-1
has caused the Debian Bug report #1073357,
regarding ruby-mechanize: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mechanize
Version: 2.8.5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-mechanize/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"mechanize\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-mechanize/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake --rakelibdir /gem2deb-nonexistent -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/share/rubygems-integration/all/gems/rake-13.2.1/lib/rake/rake_test_loader.rb
>  "test/test_mechanize.rb" "test/test_mechanize_cookie.rb" 
> "test/test_mechanize_cookie_jar.rb" "test/test_mechanize_directory_saver.rb" 
> "test/test_mechanize_download.rb" 
> "test/test_mechanize_element_not_found_error.rb" 
> "test/test_mechanize_file.rb" "test/test_mechanize_file_connection.rb" 
> "test/test_mechanize_file_request.rb" "test/test_mechanize_file_response.rb" 
> "test/test_mechanize_file_saver.rb" "test/test_mechanize_form.rb" 
> "test/test_mechanize_form_check_box.rb" 
> "test/test_mechanize_form_encoding.rb" "test/test_mechanize_form_field.rb" 
> "test/test_mechanize_form_file_upload.rb" 
> "test/test_mechanize_form_image_button.rb" 
> "test/test_mechanize_form_keygen.rb" 
> "test/test_mechanize_form_multi_select_list.rb" 
> "test/test_mechanize_form_option.rb" 
> "test/test_mechanize_form_radio_button.rb" 
> "test/test_mechanize_form_select_list.rb" 
> "test/test_mechanize_form_textarea.rb" "test/test_mechanize_headers.rb" 
> "test/test_mechanize_history.rb" "test/test_mechanize_http_agent.rb" 
> "test/test_mechanize_http_auth_challenge.rb" 
> "test/test_mechanize_http_auth_realm.rb" 
> "test/test_mechanize_http_auth_store.rb" 
> "test/test_mechanize_http_content_disposition_parser.rb" 
> "test/test_mechanize_http_www_authenticate_parser.rb" 
> "test/test_mechanize_image.rb" "test/test_mechanize_link.rb" 
> "test/test_mechanize_page.rb" "test/test_mechanize_page_encoding.rb" 
> "test/test_mechanize_page_frame.rb" "test/test_mechanize_page_image.rb" 
> "test/test_mechanize_page_link.rb" "test/test_mechanize_page_meta_refresh.rb" 
> "test/test_mechanize_parser.rb" "test/test_mechanize_pluggable_parser.rb" 
> "test/test_mech

[DRE-maint] Processed: tagging 1075985, tagging 1076031, tagging 1076063, tagging 1076067, tagging 1070900

2024-07-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1075985 + sid trixie
Bug #1075985 [libfftw3-mpi3] libfftw3-mpi3 might be misbuilt with MPICH as 
default
Added tag(s) trixie and sid.
> tags 1076031 + sid trixie
Bug #1076031 [pyside2] freecad seems linked to python 3.11
Added tag(s) trixie and sid.
> tags 1076063 + sid trixie
Bug #1076063 [src:ruby-mpi] ruby-mpi: FTBFS with mpich as default MPI 
implementation on 32 bit architectures: mpi.c:64:13: error: ‘MPI_2COMPLEX’ 
undeclared (first use in this function); did you mean ‘MPI_COMPLEX’?
Added tag(s) sid and trixie.
> tags 1076067 + sid trixie
Bug #1076067 [avifile] avifile: armhf test regression with ffmpeg 6.1.1-5 and 
no neon instructions [PATCH]
Added tag(s) trixie and sid.
> tags 1070900 + sid trixie
Bug #1070900 [src:valentina] valentina: FTBFS: Error copying 
/<>/src/app/tape/bin/tape to 
/<>/debian/tmp/usr/bin/tape: Cannot create 
/<>/debian/tmp/usr/bin/tape for output
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1070900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070900
1075985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075985
1076031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076031
1076063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076063
1076067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1074362: marked as done (src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary)

2024-07-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Jul 2024 11:47:54 +
with message-id 
and subject line Bug#1074362: fixed in ruby-redis-client 0.22.2-1.1
has caused the Debian Bug report #1074362,
regarding src:ruby-redis-client: fails to migrate to testing for too long: 
uploader built arch:all binary
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1074362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: ruby-redis-client
Version: 0.19.1-2
Severity: serious
Control: close -1 0.22.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-redis-client has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ruby-redis-client



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-redis-client
Source-Version: 0.22.2-1.1
Done: Paul Gevers 

We believe that the bug you reported is fixed in the latest version of
ruby-redis-client, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ruby-redis-client package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 27 Jun 2024 12:15:21 +0200
Source: ruby-redis-client
Architecture: source
Version: 0.22.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Paul Gevers 
Closes: 1074362
Changes:
 ruby-redis-client (0.22.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1074362)
Checksums-Sha1:
 86ab6695f83852f7fa98f5aa0a40de22178835df 1871 ruby-redis-client_0.22.2-1.1.dsc
 ac799104d4d6405329329de06be853524262ae2a 2920 
ruby-redis-client_0.22.2-1.1.debian.tar.xz
Checksums-Sha256:
 63ffe7bcdade2fcca929d61f6596b60f2842a12591ebb95551b8ea4dd16d4c77 1871 
ruby-redis-client_0.22.2-1.1.dsc
 d1b2820ca25cacc10743e87d1381af24803c30707bd9963f67d17ca69d23eb47 2920 
ruby-redis-client_0.22.2-1.1.debian.tar.xz
Files:
 75393546568941554d5dd3af17cc813c 1871 ruby optional 
ruby-redis-client_0.22.2-1.1.dsc
 b1130dadc4c4390fe886fcf9a627cd5b 2920 ruby optional 
ruby-redis-client_0.22.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZ9O/cACgkQnFyZ6wW9
dQoW8gf7BqMaEP19Q0UvH+qoJsrCNLF7knsmNrlXHJiWWACC6QEK6+QELjzOWdvH
7VzdwOkmnxtd9y96k584g/pJnO2KDeExPLKfSEOLi9CFLy2Hhx/UZmTKt/n1Gq1C
7U05R4o42WOvyUKS3CFNPh6Pnyr6Xd77ZaTjng3MdPXlIb+OSssZicQ+gYiJ0Xbl

[DRE-maint] Processed: [bts-link] source package src:ruby3.1

2024-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:ruby3.1
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1075922 (http://bugs.debian.org/1075922)
> # Bug title: ruby3.1: FTBFS with openssl 3.3
> #  * https://github.com/ruby/openssl/pull/728
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1075922 + fixed-upstream
Bug #1075922 [src:ruby3.1] ruby3.1: FTBFS with openssl 3.3
Added tag(s) fixed-upstream.
> usertags 1075922 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1075922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: [bts-link] source package src:ruby3.2

2024-07-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:ruby3.2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1075923 (http://bugs.debian.org/1075923)
> # Bug title: ruby3.2: FTBFS with openssl 3.3
> #  * https://github.com/ruby/openssl/pull/728
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1075923 + fixed-upstream
Bug #1075923 [src:ruby3.2] ruby3.2: FTBFS with openssl 3.3
Added tag(s) fixed-upstream.
> usertags 1075923 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1075923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1074300: marked as done (ruby3.3: Update symbols file for loong64)

2024-07-10 Thread Debian Bug Tracking System
Your message dated Wed, 10 Jul 2024 22:01:31 +
with message-id 
and subject line Bug#1074300: fixed in ruby3.3 3.3.4-2
has caused the Debian Bug report #1074300,
regarding ruby3.3: Update symbols file for loong64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1074300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: ruby3.3
Version: 3.3.1-3
Severity: normal
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64

Hi maintainers,

Compiling the ruby3.3 failed for loong64 in the Debian Package 
Auto-Building environment.

The build error log is as follows,
```
..
  rb_resume_coverages@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_call_p@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_compile@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_opts@Base 3.3.1
+#MISSING: 3.3.1-3# (arch=!ppc64el !s390x !riscv64 !i386 
!mips64el)rb_rjit_call_p@Base 3.3.1
+#MISSING: 3.3.1-3# (arch=!ppc64el !s390x !riscv64 !i386 
!mips64el)rb_rjit_compile@Base 3.3.1
+#MISSING: 3.3.1-3# (arch=!ppc64el !s390x !riscv64 !i386 
!mips64el)rb_rjit_opts@Base 3.3.1

  rb_rs@Base 3.3.0~preview1
.
```
The full log can be found at 
https://buildd.debian.org/status/logs.php?pkg=ruby3.3=3.3.1-3=loong64.


Please consider the patch I attached.
Your opinions are welcome.

Thanks,
Dandan Zhang

diff -Nru ruby3.3-3.3.1/debian/libruby3.3.symbols 
ruby3.3-3.3.1/debian/libruby3.3.symbols
--- ruby3.3-3.3.1/debian/libruby3.3.symbols 2024-06-01 01:44:10.0 
+
+++ ruby3.3-3.3.1/debian/libruby3.3.symbols 2024-06-12 20:16:55.0 
+
@@ -1390,9 +1390,9 @@
  rb_resolve_me_location@Base 3.3.0~preview1
  rb_respond_to@Base 3.3.0~preview1
  rb_resume_coverages@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_call_p@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_compile@Base 3.3.1
- (arch=!ppc64el !s390x !riscv64 !i386 !mips64el)rb_rjit_opts@Base 3.3.1
+ (arch=!ppc64el !s390x !riscv64 !i386 !mips64el !loong64)rb_rjit_call_p@Base 
3.3.1
+ (arch=!ppc64el !s390x !riscv64 !i386 !mips64el !loong64)rb_rjit_compile@Base 
3.3.1
+ (arch=!ppc64el !s390x !riscv64 !i386 !mips64el !loong64)rb_rjit_opts@Base 
3.3.1
  rb_rs@Base 3.3.0~preview1
  rb_ruby_debug_ptr@Base 3.3.0~preview1
  rb_ruby_parser_compile_string@Base 3.3.1
--- End Message ---
--- Begin Message ---
Source: ruby3.3
Source-Version: 3.3.4-2
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
ruby3.3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1074...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated ruby3.3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jul 2024 21:52:32 -0300
Source: ruby3.3
Architecture: source
Version: 3.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Kanashiro 
Closes: 1074300
Changes:
 ruby3.3 (3.3.4-2) unstable; urgency=medium
 .
   * d/libruby3.3.symbols: fix FTBFS in armel and loong64 (Closes: #1074300).
Checksums-Sha1:
 bcbdc7e82db480c0de19263e76ea25c2674a940f 2592 ruby3.3_3.3.4-2.dsc
 eed0330ce76e3df4f4bce17bcecf85c3a5af7222 61460 ruby3.3_3.3.4-2.debian.tar.xz
Checksums-Sha256:
 a8fbf5e034d15c23a185165b7fb18f0287d291e2ae83e673c544dfc27384f66f 2592 
ruby3.3_3.3.4-2.dsc
 f04cbf8d42020503afb475753b9022d9335fa33914e90bca97b3b87e575a98c9 61460 
ruby3.3_3.3.4-2.debian.tar.xz
Files:
 e50d7decd64e60ed388cff446bc61785 2592 ruby optional ruby3.3_3.3.4-2.dsc
 412f88a8136097e7d5eed3adb5010c50 61460 ruby optional 
ruby3.3_3.3.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmaO+YcVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8uaUQAK2etha+NqY5mqbRYhM6wBnKd57P
yQsbAKJwZeIMvQOiOqqrbJ9YE0RPxnvB6qxTwoxK5UaVNDhy7x0xCvvwol4Q9l59
WZlLrgxuEk9ymtNmk2vy8VNSJ3p57CoRHBppFv7ItfIE5Fua8ODyP+rRBzN+pLIh
FOrvbGTm9i/zfe9MxIgfjkWW80W2I7zdUlhZ6HKh2amRPCvx9AIeuJR2MZNSNNhl
kt8r5u7B1C6dZrQWpASi3

[DRE-maint] Processed: Bug#1074300 marked as pending in ruby

2024-07-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1074300 [src:ruby3.3] ruby3.3: Update symbols file for loong64
Added tag(s) pending.

-- 
1074300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1075924: marked as done (ruby3.3: FTBFS with openssl 3.3)

2024-07-09 Thread Debian Bug Tracking System
Your message dated Tue, 9 Jul 2024 22:25:59 -0300
with message-id <04c51688-89ef-4808-8e0a-e04b98db8...@debian.org>
and subject line ruby3.3: FTBFS with openssl 3.3
has caused the Debian Bug report #1075924,
regarding ruby3.3: FTBFS with openssl 3.3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1075924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby3.3
Version: 3.3.1-6
Severity: important
Tags: sid patch
control: affects -1 src:openssl
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-3.3
control: forwarded -1 https://github.com/ruby/openssl/pull/728

Ruby fails the CI-testsuite against openssl 3.3 in experimental. Based
on CI-log:
|  1) Error:
|OpenSSL::TestASN1#test_utctime:
|OpenSSL::ASN1::ASN1Error: utctime is too short
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:698:in
 `decode'
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:698:in
 `decode_test'
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:411:in
 `test_utctime'
|
|  2) Error:
|OpenSSL::TestASN1#test_generalizedtime:
|OpenSSL::ASN1::ASN1Error: generalizedtime is too short
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:698:in
 `decode'
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:698:in
 `decode_test'
|
/tmp/autopkgtest-lxc.9xrphuye/downtmp/autopkgtest_tmp/test/openssl/test_asn1.rb:433:in
 `test_generalizedtime'
|
|Finished tests in 732.831411s, 26.2202 tests/s, 7769.1375 assertions/s.
|19215 tests, 5693468 assertions, 0 failures, 2 errors, 83 skips

The patch appears to have been merged into the release branch.

Sebastian
--- End Message ---
--- Begin Message ---
The patch forwarded upstream is already included in version 3.3.4 which 
was uploaded to unstable earlier today:


https://tracker.debian.org/news/1543130/accepted-ruby33-334-1-source-into-unstable/

--
Lucas Kanashiro--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Merge duplicates

2024-07-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1069439 src:openmpi
Bug #1069439 [src:arpack] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: 
test-suite.log] Error 1
Bug reassigned from package 'src:arpack' to 'src:openmpi'.
No longer marked as found in versions arpack/3.9.1-1.1 and arpack/3.9.1-1.
Ignoring request to alter fixed versions of bug #1069439 to the same values 
previously set
> reassign 1069418 src:openmpi
Bug #1069418 [src:ruby-mpi] ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" 
failed: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug reassigned from package 'src:ruby-mpi' to 'src:openmpi'.
No longer marked as found in versions ruby-mpi/0.3.2-4.
Ignoring request to alter fixed versions of bug #1069418 to the same values 
previously set
> forcemerge 1069433 1069439 1069418
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Bug #1069439 [src:openmpi] arpack: FTBFS on armhf: make[6]: *** [Makefile:831: 
test-suite.log] Error 1
Marked Bug as done
Added indication that 1069439 affects src:python-escript,src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-3 and openmpi/4.1.6-12.
Bug #1069418 [src:openmpi] ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" 
failed: /usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Marked Bug as done
Added indication that 1069418 affects src:python-escript,src:gtg-trace
Marked as fixed in versions openmpi/4.1.6-13.
Marked as found in versions openmpi/4.1.6-12 and openmpi/4.1.6-3.
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Merged 1069418 1069433 1069439 1069512
> affects 1069433 src:arpack src:ruby-mpi
Bug #1069433 {Done: Samuel Thibault } [src:openmpi] 
gtg-trace: FTBFS on armhf: tests fail
Bug #1069418 {Done: Samuel Thibault } [src:openmpi] 
ruby-mpi: FTBFS on armhf: ERROR: Test "ruby3.1" failed: 
/usr/share/pmix/help-pmix-runtime.txt: No such file or directory. Sorry!
Bug #1069439 {Done: Samuel Thibault } [src:openmpi] 
arpack: FTBFS on armhf: make[6]: *** [Makefile:831: test-suite.log] Error 1
Bug #1069512 {Done: Samuel Thibault } [src:openmpi] 
python-escript: FTBFS on armhf: tests fail
Added indication that 1069433 affects src:arpack and src:ruby-mpi
Added indication that 1069418 affects src:arpack and src:ruby-mpi
Added indication that 1069439 affects src:arpack and src:ruby-mpi
Added indication that 1069512 affects src:arpack and src:ruby-mpi
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069418
1069433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069433
1069439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069439
1069512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby3.3: FTBFS with openssl 3.3

2024-07-07 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:openssl
Bug #1075924 [src:ruby3.3] ruby3.3: FTBFS with openssl 3.3
Added indication that 1075924 affects src:openssl
> forwarded -1 https://github.com/ruby/openssl/pull/728
Bug #1075924 [src:ruby3.3] ruby3.3: FTBFS with openssl 3.3
Set Bug forwarded-to-address to 'https://github.com/ruby/openssl/pull/728'.

-- 
1075924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby3.2: FTBFS with openssl 3.3

2024-07-07 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:openssl
Bug #1075923 [src:ruby3.2] ruby3.2: FTBFS with openssl 3.3
Added indication that 1075923 affects src:openssl
> forwarded -1 https://github.com/ruby/openssl/pull/728
Bug #1075923 [src:ruby3.2] ruby3.2: FTBFS with openssl 3.3
Set Bug forwarded-to-address to 'https://github.com/ruby/openssl/pull/728'.

-- 
1075923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby3.1: FTBFS with openssl 3.3

2024-07-07 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:openssl
Bug #1075922 [src:ruby3.1] ruby3.1: FTBFS with openssl 3.3
Added indication that 1075922 affects src:openssl
> forwarded -1 https://github.com/ruby/openssl/pull/728
Bug #1075922 [src:ruby3.1] ruby3.1: FTBFS with openssl 3.3
Set Bug forwarded-to-address to 'https://github.com/ruby/openssl/pull/728'.

-- 
1075922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1073372: marked as done (ruby-roadie: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(result.at_css("a.two")["href"]).to eq("%24UNSUBSCRIBE_URL"))

2024-07-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jul 2024 06:59:03 +
with message-id 
and subject line Bug#1073372: fixed in ruby-roadie 5.2.1-1
has caused the Debian Bug report #1073372,
regarding ruby-roadie: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: 
expect(result.at_css("a.two")["href"]).to eq("%24UNSUBSCRIBE_URL")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-roadie
Version: 5.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  Failure/Error: expect(result.at_css("a.two")["href"]).to 
> eq("%24UNSUBSCRIBE_URL")
> 
>expected: "%24UNSUBSCRIBE_URL"
> got: "$UNSUBSCRIBE_URL"
> 
>(compared using ==)
>  # ./spec/integration_spec.rb:255:in `block (3 levels) in  (required)>'
>  # 
> /usr/share/rubygems-integration/all/gems/webmock-3.18.1/lib/webmock/rspec.rb:37:in
>  `block (2 levels) in '
> 
> Finished in 0.31385 seconds (files took 0.56868 seconds to load)
> 260 examples, 1 failure, 1 pending
> 
> Failed examples:
> 
> rspec ./spec/integration_spec.rb:234 # Roadie functionality on full documents 
> does not change URLs of ignored elements, but still inlines styles on them
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2024/06/15/ruby-roadie_5.1.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240615;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240615=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-roadie
Source-Version: 5.2.1-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
ruby-roadie, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated ruby-roadie package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Thu, 04 Jul 2024 02:12:48 -0400
Source: ruby-roadie
Architecture: source
Version: 5.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Unit 193 
Closes: 1073372
Changes:
 ruby-roadie (5.2.1-1) unstable; urgency=medium
 .
   * New upstream version 5.2.1.
 - Fix Nokogiri test for 1.15. (Closes: #1073372)
   * Update Standards-Version to 4.7.0.
Checksums-Sha1:
 ec3ee59f626448364743eb650d749f8ea3012a39 2088 ruby-roadie_5.2.1-1.dsc
 f51ef4518070276d1168b44a95dd199267c1f10c 51062 ruby-roadie_5.2.1.orig.tar.gz
 83a9e9ebc22416c12d85bb243dc3986c0bd735c7 3116 ruby-roadie_5.2.1-1.debian.tar.xz
 ce696e6e4ec933350a5c28a11c0d78ac87cb8d8a 9562 
ruby-roadie_5.2.1-1_amd64.buildinfo
Checksums-Sha256:
 f6c68f114123a3520e3cc509cca1bc359e3a60e8efb33f0d379f4c4ae76bd583 2088 
ruby-roadie_5.2.1-1.dsc
 44c2b40d44deb3221ac3cdd584a00

[DRE-maint] Bug#1073244: marked as done (ruby-xmlrpc has an undeclared file conflict on /usr/bin/console)

2024-07-03 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jul 2024 05:36:19 +
with message-id 
and subject line Bug#1073244: fixed in ruby-xmlrpc 0.3.3-2
has caused the Debian Bug report #1073244,
regarding ruby-xmlrpc has an undeclared file conflict on /usr/bin/console
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-xmlrpc
Version: 0.3.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + conserver-client

ruby-xmlrpc has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/bin/console is contained in the packages
 * conserver-client
   * 8.2.6-2 as present in bullseye
   * 8.2.7-2+b1 as present in bookworm
   * 8.2.7-2+b3 as present in trixie|unstable
 * ruby-xmlrpc/0.3.3-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: ruby-xmlrpc
Source-Version: 0.3.3-2
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
ruby-xmlrpc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated ruby-xmlrpc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Jul 2024 17:24:36 -0300
Source: ruby-xmlrpc
Architecture: source
Version: 0.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Kanashiro 
Closes: 1073152 1073244
Changes:
 ruby-xmlrpc (0.3.3-2) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: do no ship delevelopment binaries (Closes: #1073152, #1073244).
Checksums-Sha1:
 6c3caf4edf4666b69ae76ee141bf47c728d0ffa1 2041 ruby-xmlrpc_0.3.3-2.dsc
 51f2b725a14f11454c12fc3fe8a395be42a2ea72 3280 ruby-xmlrpc_0.3.3-2.debian.tar.xz
Checksums-Sha256:
 388431727d1890c096f18917ae422b5c1465fe67f96db97c9da707c35ffaf1cb 2041 
ruby-xmlrpc_0.3.3-2.dsc
 5a88fde03a01017c6e44a90290ebfdab61b703648acbb7ca2972e0bd06f55466 3280 
ruby-xmlrpc_0.3.3-2.debian.tar.xz
Files:
 dc11aef0dcfede97a5577e18bf908678 2041 ruby optional ruby-xmlrpc_0.3.3-2.dsc
 dd24fe49e2880bea7fe0ab715853de13 3280 ruby optional 
ruby-xmlrpc_0.3.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmaFt40VHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8h8IP/0cU/fTL8bkTDbE8MmvfK6P10Owp
FZQOKxAVgERx1fX/+LPNTBWHzxjsg/K04I8SoajYsHiAetDvgy3gREgW4WNF5UOV
xOqfDsk5eCcRHnlYHjMNZiMjCiJzMU0Lhowgwbb9mMqqop30sGX5l4hw/Dc3AIiJ
zsI6f+xVlFsPnnvsL+JP8HJE45o2DI/uoQ43bn+ajdLfEI4xh2yZ2vkoi6c0/160
7u+L0l3nQeexK2+gaz291AdPP7cWVxu1L3Q75uUEj1etsVUcvXMHW6IrqJIu05cW
A9U6noJOpgiBlEXmmCMrpjUD+/P0uuiCneD6U6wbkCVfyOcuOgVcU6Vb0gjRKaDw
85N8vhqEwMug41KhIPFaHaF/HOl8/BseBeE6uLcfYImcZjH2fkkzVTGiyipktX4N
HyuwSkWyR+bPNWP1bbRcCQs3JsiE1xj2RFKACbGmgwLaJMpoInSAaM3OgwX3PJEb
M2yQV186AjqXEZNWgLGNqdGfqGupyybOUZKKn7/rWSGbiC4hSwO3l1Us5cw1FDfX
+w7+1p88vIyrK1kP0W4350+lBcJ1SLwrMzNNzyyjmGFg+yHPhpqXa45JDijU/+ye
0ivOWI8oidWfbYzx5OVkAhztV7+m7Nv8ecglgI4Fmiu6Rse0r1kKhI8O9ftwf0QL
jEA5USaWluaFIk6A
=eEpn
-END PGP SIGNATURE-



pgpfkIcyUT0DO.pgp
Description: PGP signature
--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1073152: marked as done (ruby-xmlrpc 0.3.3-1 has a file conflict with conserver-client)

2024-07-03 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jul 2024 05:36:19 +
with message-id 
and subject line Bug#1073152: fixed in ruby-xmlrpc 0.3.3-2
has caused the Debian Bug report #1073152,
regarding ruby-xmlrpc 0.3.3-1 has a file conflict with conserver-client
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1073152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-xmlrpc
Version: 0.3.2-2
Severity: serious

Dear Maintainer,

ruby-xmlrpc 0.3.3-1 ships a new file named /usr/bin/console

This file already exists in another package named conserver-client.
Conserver has been shipping this binary for a very long time. (probably
since 2001 when that package was introduced)


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

Kernel: Linux 6.8.12-amd64 (SMP w/8 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ruby-xmlrpc depends on:
ii  ruby-webrick  1.8.1-1

ruby-xmlrpc recommends no packages.

ruby-xmlrpc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-xmlrpc
Source-Version: 0.3.3-2
Done: Lucas Kanashiro 

We believe that the bug you reported is fixed in the latest version of
ruby-xmlrpc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1073...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated ruby-xmlrpc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 Jul 2024 17:24:36 -0300
Source: ruby-xmlrpc
Architecture: source
Version: 0.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Kanashiro 
Closes: 1073152 1073244
Changes:
 ruby-xmlrpc (0.3.3-2) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: do no ship delevelopment binaries (Closes: #1073152, #1073244).
Checksums-Sha1:
 6c3caf4edf4666b69ae76ee141bf47c728d0ffa1 2041 ruby-xmlrpc_0.3.3-2.dsc
 51f2b725a14f11454c12fc3fe8a395be42a2ea72 3280 ruby-xmlrpc_0.3.3-2.debian.tar.xz
Checksums-Sha256:
 388431727d1890c096f18917ae422b5c1465fe67f96db97c9da707c35ffaf1cb 2041 
ruby-xmlrpc_0.3.3-2.dsc
 5a88fde03a01017c6e44a90290ebfdab61b703648acbb7ca2972e0bd06f55466 3280 
ruby-xmlrpc_0.3.3-2.debian.tar.xz
Files:
 dc11aef0dcfede97a5577e18bf908678 2041 ruby optional ruby-xmlrpc_0.3.3-2.dsc
 dd24fe49e2880bea7fe0ab715853de13 3280 ruby optional 
ruby-xmlrpc_0.3.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmaFt40VHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8h8IP/0cU/fTL8bkTDbE8MmvfK6P10Owp
FZQOKxAVgERx1fX/+LPNTBWHzxjsg/K04I8SoajYsHiAetDvgy3gREgW4WNF5UOV
xOqfDsk5eCcRHnlYHjMNZiMjCiJzMU0Lhowgwbb9mMqqop30sGX5l4hw/Dc3AIiJ
zsI6f+xVlFsPnnvsL+JP8HJE45o2DI/uoQ43bn+ajdLfEI4xh2yZ2vkoi6c0/160
7u+L0l3nQeexK2+gaz291AdPP7cWVxu1L3Q75uUEj1etsVUcvXMHW6IrqJIu05cW
A9U6noJOpgiBlEXmmCMrpjUD+/P0uuiCneD6U6wbkCVfyOcuOgVcU6Vb0gjRKaDw
85N8vhqEwMug41KhIPFaHaF/HOl8/BseBeE6uLcfYImcZjH2fkkzVTGiyipktX4N
HyuwSkWyR+bPNWP1bbRcCQs3JsiE1xj2RFKACbGmgwLaJMpoInSAaM3OgwX3PJEb
M2yQV186AjqXEZNWgLGNqdGfqGupyybOUZKKn7/rWSGbiC4hSwO3l1Us5cw1FDfX
+w7+1p88vIyrK1kP0W4350+lBcJ1SLwrMzNNzyyjmGFg+yHPhpqXa45JDijU/+ye
0ivOWI8oidWfbYzx5OVkAhztV7+m7Nv8ecglgI4Fmiu6Rse0r1kKhI8O9ftwf0QL
jEA5USaWluaFIk6A
=eEpn
-END PGP SIGNATURE-



pgpafXiqkPXyF.pgp
Description: PGP signature
--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1074986: marked as done (gem2deb: ftbfs with GCC-14)

2024-07-03 Thread Debian Bug Tracking System
Your message dated Wed, 03 Jul 2024 16:49:15 +
with message-id 
and subject line Bug#1074986: fixed in gem2deb 2.2.4
has caused the Debian Bug report #1074986,
regarding gem2deb: ftbfs with GCC-14
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1074986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gem2deb
Version: 2.2.3
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/gem2deb_2.2.3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
test: with gemspec should obtain gem name from gemspec. :   .: (0.000532)
test: with gemspec should obtain gem version from gemspec. :.: (0.000574)
test: with gemspec should obtain homepage from gemspec. :   .: (0.000914)
test: with gemspec should obtain long detect from gemspec. :.: (0.000602)
test: with gemspec should obtain short description from gemspec. :  .: 
(0.000545)
test: with gemspec should obtain test files list from gemspec. :.: 
(0.002486)
test: with gemspec should resist bindir being false. :  .: (0.000574)
test: with gemspec should use whatever directory gemspec says as bindir. :  
.: (0.000847)
test: with gemspec should use whatever programs the gemspec says. : .: 
(0.001829)
test: without gemspec should have no dependencies. :.: (0.000366)
test: without gemspec should have no homepage. :.: (0.000572)
test: without gemspec should have no long description. :.: (0.000211)
test: without gemspec should have no short description. :   .: (0.000183)
test: without gemspec should have no test files. :  .: (0.000202)
test: without gemspec should provide a fallback version number. :   .: 
(0.000280)
test: without gemspec should provide a gem name from source dir. :  .: 
(0.000200)
test: without gemspec should read version number from source dir name when 
available. : .: (0.000513)
test: without gemspec should use all programs under bin/. : .: (0.001131)
test: without gemspec should use bin/ as bindir. :  .: (0.000211)
  PackageNameMappingTest: 
test: PackageNameMapping should strip architecture qualifier off package 
names. :   .: (0.051144)
test: converting gem name to package name without a cache should convert 
foo to ruby-foo. : .: (0.000718)
test: converting gem name to package name without a cache should convert 
foo-bar_baz to ruby-foo-bar-baz. : .: (0.000865)
test: using data from installed packages should have data for mocha. :  
.: (0.070716)
  SecureCodeTest: 
test: SecureCode should not interpolate variables into shell commands. :
.: (0.004061)
  SourceTest: 
test: determining debhelper compat level should always be a number. :   
.: (0.000904)
test: determining debhelper compat level should detect from Build-Depends 
with multiple lines. :.: (0.000299)
test: determining debhelper compat level should detect from Build-Depends. 
:.: (0.000401)
test: determining debhelper compat level should detect from DH_COMPAT. :
.: (0.001510)
test: determining debhelper compat level should detect from debian/compat. 
:.: (0.000498)
test: selecting package layout should default to single-binary. :   .: 
(0.000394)
test: selecting package layout should detect multibinary. : .: (0.000590)
test: selecting package layout should ignore packages without X-DhRuby-Root 
when one of them has it. :  .: (0.000398

[DRE-maint] Processed: Bug#1074986 marked as pending in gem2deb

2024-07-03 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1074986 [src:gem2deb] gem2deb: ftbfs with GCC-14
Added tag(s) pending.

-- 
1074986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Re: Bug#1074791: be_enabled only checks for init scripts and upstart services

2024-07-03 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 ruby-serverspec
Bug #1074791 [ruby-specinfra] be_enabled only checks for init scripts and 
upstart services
Bug reassigned from package 'ruby-specinfra' to 'ruby-serverspec'.
No longer marked as found in versions ruby-specinfra/2.89.0-1.
Ignoring request to alter fixed versions of bug #1074791 to the same values 
previously set

-- 
1074791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: severity of 1069089 is serious, found 1069089 in 3.4.20-1~0

2024-07-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1069089 serious
Bug #1069089 [ruby-rubygems] ruby-rubygems: Broken platform detection which 
lead to unability to install sass-embedded
Severity set to 'serious' from 'important'
> found 1069089 3.4.20-1~0
Bug #1069089 [ruby-rubygems] ruby-rubygems: Broken platform detection which 
lead to unability to install sass-embedded
Marked as found in versions rubygems/3.4.20-1~0.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary

2024-06-27 Thread Debian Bug Tracking System
Processing control commands:

> close -1 0.22.2-1
Bug #1074362 [src:ruby-redis-client] src:ruby-redis-client: fails to migrate to 
testing for too long: uploader built arch:all binary
Marked as fixed in versions ruby-redis-client/0.22.2-1.
Bug #1074362 [src:ruby-redis-client] src:ruby-redis-client: fails to migrate to 
testing for too long: uploader built arch:all binary
Marked Bug as done

-- 
1074362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1042415: marked as done (ruby-aws-partitions: Package missing partitions.json)

2024-06-19 Thread Debian Bug Tracking System
Your message dated Wed, 19 Jun 2024 18:32:10 +
with message-id 
and subject line Bug#1042415: fixed in ruby-aws-partitions 1.653.0-3~deb12u1
has caused the Debian Bug report #1042415,
regarding ruby-aws-partitions: Package missing partitions.json
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-aws-partitions
Version: 1.653.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: ssg...@debian.org

In version 1.653.0-1, 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json 
is not present. It is there in version 1.354.0-2 in bullseye. Without that 
file, any actual use of this gem fails:

$ irb
irb(main):001:0> require 'aws-partitions'
=> true
irb(main):002:1* Aws::Partitions.each do |partition|
irb(main):003:1*   puts partition.name
irb(main):004:0> end
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in
 `read': No such file or directory @ rb_sysopen - 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json 
(Errno::ENOENT)
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in
 `defaults'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:214:in
 `default_partition_list'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:137:in
 `each'
from (irb):2:in `'
from /usr/lib/ruby/gems/3.1.0/gems/irb-1.4.1/exe/irb:11:in `'
from /usr/bin/irb:25:in `load'
from /usr/bin/irb:25:in `'

Patch to fix is attached


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

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 ruby-aws-partitions depends on:
ii  ruby  1:3.1

ruby-aws-partitions recommends no packages.

ruby-aws-partitions suggests no packages.

-- no debconf information
diff -Nru ruby-aws-partitions-1.653.0/debian/changelog 
ruby-aws-partitions-1.653.0/debian/changelog
--- ruby-aws-partitions-1.653.0/debian/changelog2022-10-30 
08:49:35.0 -0500
+++ ruby-aws-partitions-1.653.0/debian/changelog2023-07-27 
17:39:10.0 -0500
@@ -1,3 +1,11 @@
+ruby-aws-partitions (1.653.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Change DH_RUBY_GEM_INSTALL_WHITELIST_APPEND to DH_RUBY_GEM_INSTALL_INCLUDE
+in debian/rules to work with newer gem2deb
+
+ -- Stephen Gelman   Thu, 27 Jul 2023 17:39:10 -0500
+
 ruby-aws-partitions (1.653.0-1) unstable; urgency=medium
 
   * Team Upload
diff -Nru ruby-aws-partitions-1.653.0/debian/rules 
ruby-aws-partitions-1.653.0/debian/rules
--- ruby-aws-partitions-1.653.0/debian/rules2022-10-30 08:49:35.0 
-0500
+++ ruby-aws-partitions-1.653.0/debian/rules2023-07-27 17:36:38.0 
-0500
@@ -2,7 +2,7 @@
 
 export GEM2DEB_TEST_RUNNER = --check-dependencies
 export DH_RUBY = --gem-install
-export DH_RUBY_GEM_INSTALL_WHITELIST_APPEND := partitions.json
+export DH_RUBY_GEM_INSTALL_INCLUDE := partitions.json
 
 %:
dh $@ --buildsystem=ruby --with ruby
--- End Message ---
--- Begin Message ---
Source: ruby-aws-partitions
Source-Version: 1.653.0-3~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
ruby-aws-partitions, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated ruby-aws-partitions 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jun 2024 17:26:08 +0200
Source: ruby-aws-partitions
Architectur

[DRE-maint] Processed: tagging 1055297, tagging 1047864, tagging 1042983, tagging 1071992, tagging 1073557 ...

2024-06-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1055297 + sid trixie
Bug #1055297 {Done: Aurelien Jarno } [ruby3.1] ruby3.1: 
fails to build against glibc 2.38
Added tag(s) sid and trixie.
> tags 1047864 + sid trixie
Bug #1047864 {Done: Gunnar Wolf } [impressive] impressive: 
Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»
Added tag(s) trixie and sid.
> tags 1042983 + sid trixie
Bug #1042983 {Done: Arnaud Ferraris } [squeekboard] 
squeekboard - rust gtk stack update.
Added tag(s) trixie and sid.
> tags 1071992 + sid trixie experimental
Bug #1071992 [src:sqlmodel] sqlmodel: please make this package compatible with 
SQL Alchemy 2.x
Added tag(s) experimental, sid, and trixie.
> tags 1073557 + sid trixie
Bug #1073557 [python3-motor] python3-motor: Fails to import and crashes the 
entire program
Added tag(s) trixie and sid.
> notfound 1073299 2.4.90
Bug #1073299 [roger-router] debian package version 2.4.2 does not work in 
stable, and was not updated to 2.4.90 in testing and unstable.
There is no source info for the package 'roger-router' at version '2.4.90' with 
architecture ''
Unable to make a source version for version '2.4.90'
No longer marked as found in versions 2.4.90.
> found 1073299 2.4.2-3
Bug #1073299 [roger-router] debian package version 2.4.2 does not work in 
stable, and was not updated to 2.4.90 in testing and unstable.
Marked as found in versions roger-router/2.4.2-3.
> found 1073290 256~rc1-1~exp
Bug #1073290 [systemd] systemd: Please breaks against dracut-core << 102-2~
Marked as found in versions systemd/256~rc1-1~exp.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042983
1047864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047864
1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297
1071992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071992
1073290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073290
1073299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073299
1073557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby-xmlrpc has an undeclared file conflict on /usr/bin/console

2024-06-15 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + conserver-client
Bug #1073244 [ruby-xmlrpc] ruby-xmlrpc has an undeclared file conflict on 
/usr/bin/console
Added indication that 1073244 affects conserver-client

-- 
1073244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: fix ruby-xmlrpc bug

2024-06-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1073152 0.3.3-1
Bug #1073152 [ruby-xmlrpc] ruby-xmlrpc 0.3.3-1 has a file conflict with 
conserver-client
Marked as found in versions ruby-xmlrpc/0.3.3-1.
> notfound 1073152 0.3.2-2
Bug #1073152 [ruby-xmlrpc] ruby-xmlrpc 0.3.3-1 has a file conflict with 
conserver-client
No longer marked as found in versions ruby-xmlrpc/0.3.2-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1073152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1064720: marked as done (ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 08:36:03 +
with message-id 
and subject line Bug#1064720: fixed in ruby-capybara 3.40.0+ds-1
has caused the Debian Bug report #1064720,
regarding ruby-capybara: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara
Version: 3.36.0+ds-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>   NoMethodError:
> undefined method `stdio' for Puma::Events:Class
> 
>   events = conf.options[:Silent] ? ::Puma::Events.strings : 
> ::Puma::Events.stdio
>   
> ^^
>   # /<>/lib/capybara/registrations/servers.rb:32:in `block 
> in '
>   # /<>/lib/capybara.rb:252:in `run_default_server'
>   # /<>/lib/capybara/registrations/servers.rb:4:in `block in 
> '
>   # /<>/lib/capybara/server.rb:77:in `block in boot'
> 
> Finished in 52.8 seconds (files took 1.06 seconds to load)
> 2512 examples, 36 failures, 6 pending
> 
> Failed examples:
> 
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:1]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by visiting a page directly
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:2]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host returns to 
> the app host when visiting a relative url
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:3]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by setting Capybara.app_host
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:4]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is 
> unaffected by following a relative link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:5]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by following an absolute link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:6]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is 
> unaffected by posting through a relative form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:7]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by posting through an absolute form
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:8]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host is affected 
> by following a redirect
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:9]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host maintains 
> fragment
> rspec '/<>/lib/capybara/spec/spec_helper.rb[1:27:10]' # 
> Capybara::Session DSL #current_url, #current_path, #current_host redirects to 
> a fragment
> rspec /<>/spec/dsl_spec.rb:165 # Capybara::DSL#current_session 
> should change with the current driver
> rspec /<>/spec/dsl_spec.rb:171 # Capybara::DSL#current_session 
> should be persistent even across driver changes
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:1]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by visiting a page directly
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:2]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host returns 
> to the app host when visiting a relative url
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:3]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by setting Capybara.app_host
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:4]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> unaffected by following a relative link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:5]' # 
> Capybara::Session RackTest #current_url, #current_path, #current_host is 
> affected by following an absolute link
> rspec '/<>/lib/capybara/spec/spec_helper.rb[2:27:6]' # 
> Cap

[DRE-maint] Bug#1045929: marked as done (ruby-capybara: Fails to build source after successful build)

2024-06-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Jun 2024 08:36:03 +
with message-id 
and subject line Bug#1045929: fixed in ruby-capybara 3.40.0+ds-1
has caused the Debian Bug report #1045929,
regarding ruby-capybara: Fails to build source after successful build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1045929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-capybara
Version: 3.36.0+ds-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> -
> 
> dpkg-buildpackage: info: source package ruby-capybara
> dpkg-buildpackage: info: source version 3.36.0+ds-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Daniel Leidert 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --buildsystem=ruby --with ruby
>dh_auto_clean -O--buildsystem=ruby
>   dh_ruby --clean
> W: XS-Ruby-Versions is deprecated, and will be ignored
>dh_autoreconf_clean -O--buildsystem=ruby
>dh_clean -O--buildsystem=ruby
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ruby-capybara using existing 
> ./ruby-capybara_3.36.0+ds.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file 
> ruby-capybara-3.36.0+ds/save_path_tmp/capybara-20230812124218505961329.html 
> has no final newline (either original or modified version)
> dpkg-source: warning: file 
> ruby-capybara-3.36.0+ds/save_path_tmp/capybara-20230812124246052052.html 
> has no final newline (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  ruby-capybara-3.36.0+ds/save_path_tmp/capybara-20230812124218505961329.html
>  ruby-capybara-3.36.0+ds/save_path_tmp/capybara-20230812124246052052.html
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/ruby-capybara_3.36.0+ds-2.diff.ZLVvl4
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/ruby-capybara_3.36.0+ds-2_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-capybara
Source-Version: 3.40.0+ds-1
Done: Leandro Cunha 

We believe that the bug you reported is fixed in the latest version of
ruby-capybara, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1045...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Leandro Cunha  (supplier of updated ruby-capybara 
package)

(This message was generated automatically at their request; if you
believe that there is a 

[DRE-maint] Processed: Bug#1064720 marked as pending in ruby-capybara

2024-06-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" 
failed: NoMethodError:
Ignoring request to alter tags of bug #1064720 to the same tags previously set

-- 
1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Bug#1064720 marked as pending in ruby-capybara

2024-06-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" 
failed: NoMethodError:
Ignoring request to alter tags of bug #1064720 to the same tags previously set

-- 
1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: tagging 1072784, found 1072752 in 0.11.0+5-1.1, tagging 1072615, tagging 1070693 ..., tagging 1000118 ...

2024-06-07 Thread Debian Bug Tracking System
=1072586
1072594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072594
1072597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072597
1072598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072598
1072600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072600
1072601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072601
1072602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072602
1072603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072603
1072604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072604
1072608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072608
1072615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072615
1072643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072643
1072752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072752
1072762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072762
1072764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072764
1072767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072767
1072784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: rails: CVE-2024-28103

2024-06-06 Thread Debian Bug Tracking System
Processing control commands:

> found -1 2:6.1.7.3+dfsg-1
Bug #1072705 [src:rails] rails: CVE-2024-28103
Marked as found in versions rails/2:6.1.7.3+dfsg-1.

-- 
1072705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Re: ruby-libxml: new upstream release, addressing test failures with libxml2 >= 2.12

2024-06-06 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1072017 [src:ruby-libxml] ruby-libxml: new upstream release, addressing 
test failures with libxml2 >= 2.12
Severity set to 'serious' from 'normal'

-- 
1072017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: your mail

2024-05-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags #1064720 pending
Bug #1064720 [src:ruby-capybara] ruby-capybara: FTBFS: ERROR: Test "ruby3.1" 
failed: NoMethodError:
Added tag(s) pending.
> tags #1045929 pending
Bug #1045929 [src:ruby-capybara] ruby-capybara: Fails to build source after 
successful build
Added tag(s) pending.
> # https://salsa.debian.org/ruby-team/ruby-capybara/-/merge_requests/1
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
1045929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045929
1064720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: src:rake: fails to migrate to testing for too long: causes autopkgtest issues

2024-05-31 Thread Debian Bug Tracking System
Processing control commands:

> close -1 13.2.1-1
Bug #1072268 [src:rake] src:rake: fails to migrate to testing for too long: 
causes autopkgtest issues
Marked as fixed in versions rake/13.2.1-1.
Bug #1072268 [src:rake] src:rake: fails to migrate to testing for too long: 
causes autopkgtest issues
Marked Bug as done

-- 
1072268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: tags

2024-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1032555 + ftbfs
Bug #1032555 [nvda2speechd] nvda2speechd fails to build due to the external 
network access
Added tag(s) ftbfs.
> tags 1036369 + ftbfs
Bug #1036369 [ruby-rest-client] ruby-rest-client: network-dependent tests fail
Added tag(s) ftbfs.
> tags 1056708 + ftbfs
Bug #1056708 [src:node-wikibase-cli] node-wikibase-cli: Using internet during 
tests
Added tag(s) ftbfs.
> tags 1060772 + ftbfs
Bug #1060772 [python3-jupyterlab] python3-jupyterlab: Using node-corepack 
downloads yarnpkg from Internet
Added tag(s) ftbfs.
> tags 1070003 + ftbfs
Bug #1070003 [sbuild] sbuild/unshare: bind mounting individual /dev entries 
causes inconsistent readdir results
Added tag(s) ftbfs.
> tags 1070317 + ftbfs
Bug #1070317 [src:golang-github-likexian-gokit] fails to build without a non lo 
IP address
Added tag(s) ftbfs.
> tags 1070319 + ftbfs
Bug #1070319 [src:google-guest-agent] fails to build without a non lo IP address
Added tag(s) ftbfs.
> tags 1070325 + ftbfs
Bug #1070325 [src:servefile] fails to build without a non local IP
Added tag(s) ftbfs.
> tags 1070333 + ftbfs
Bug #1070333 [src:python-eventlet] python-eventlet fails to build with an empty 
/etc/resolv.conf
Added tag(s) ftbfs.
> tags 1070411 + ftbfs
Bug #1070411 [src:containerd] containerd fails to build as a normal user due to 
sysctl
Added tag(s) ftbfs.
> tags 1070414 + ftbfs
Bug #1070414 [src:kel-agent] fails to build when not build inside schroot
Added tag(s) ftbfs.
> tags 1070415 + ftbfs
Bug #1070415 [src:runc] runc fails to build as a normal user due to cgroups 
access
Added tag(s) ftbfs.
> tags 1072067 + ftbfs
Bug #1072067 [src:golang-github-containerd-stargz-snapshotter] 
golang-github-containerd-stargz-snapshotter fails to build on non tmpfs
Added tag(s) ftbfs.
> tags 1072145 + ftbfs
Bug #1072145 [src:docker.io] docker.io: Failing test Can't find mount point of /
Added tag(s) ftbfs.
> tags 1072147 + ftbfs
Bug #1072147 [src:golang-github-containers-buildah] test fail in sbuild+unshare
Added tag(s) ftbfs.
> tags 1072151 + ftbfs
Bug #1072151 [src:golang-github-containerd-cgroups] 
src:golang-github-containerd-cgroups tries to access /sys/kernel/mm/hugepages 
in tests
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032555
1036369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036369
1056708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056708
1060772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060772
1070003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070003
1070317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070317
1070319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070319
1070325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070325
1070333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070333
1070411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070411
1070414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070414
1070415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070415
1072067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072067
1072145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072145
1072147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072147
1072151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:36:39 +
with message-id 
and subject line Bug#1064516: fixed in ruby-rack 2.1.4-3+deb11u2
has caused the Debian Bug report #1064516,
regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for ruby-rack.

CVE-2024-26141[0]:
Reject Range headers which are too large
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/62457686b26d33a15a254c7768c2076e8e02b48b 
(v2.2.8.1)

CVE-2024-25126[1]:
Fixed ReDoS in Content Type header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1

CVE-2024-26146[2]:
Fixed ReDoS in Accept header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/e4c117749ba24a66f8ec5a08eddf68deeb425ccd 
(v2.2.8.1)


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-26141
https://www.cve.org/CVERecord?id=CVE-2024-26141
[1] https://security-tracker.debian.org/tracker/CVE-2024-25126
https://www.cve.org/CVERecord?id=CVE-2024-25126
[2] https://security-tracker.debian.org/tracker/CVE-2024-26146
https://www.cve.org/CVERecord?id=CVE-2024-26146

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.1.4-3+deb11u2
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
ruby-rack, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ruby-rack package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 May 2024 23:46:12 +0300
Source: ruby-rack
Architecture: source
Version: 2.1.4-3+deb11u2
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Adrian Bunk 
Closes: 1064516
Changes:
 ruby-rack (2.1.4-3+deb11u2) bullseye-security; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2024-25126: ReDoS in Content Type header parsing
   * CVE-2024-26141: Reject Range headers which are too large
   * CVE-2024-26146: ReDoS in Accept header parsing
   * Closes: #1064516
Checksums-Sha1:
 e840c3306e8cea596b611a04565f85e59bff2e48 2345 ruby-rack_2.1.4-3+deb11u2.dsc
 fb78585706dacc2ec7997b7c1af7d6320acd33c3 251772 ruby-rack_2.1.4.orig.tar.gz
 398b6cb6427457998dd3e1d22db83437f2138d80 14780 
ruby-rack_2.1.4-3+deb11u2.debian.tar.xz
Checksums-Sha256:
 49f54f8f3a7fadd1f2a6a9cb2a73800cf5b3a54e620005f214735f7715ff0c02 2345 
ruby-rack_2.1.4-3+deb11u2.dsc
 f0b67c0a585d34a135c1434ac2d0bdbb9611726afafc005d9da91a451b1a7855 251772 
ruby-rack_2.1.4.orig.tar.gz
 ff8697ec5799cd71a7995f601f67639aa747447fbadf7f1012e968597b18f965 14780 
ruby-rack_2.1.4-3+deb11u2.debian.tar.xz
Files:
 a2e328e5b24577e914bc62e8e28de814 2345 ruby optional 
ruby-rack_2.1.4-3+deb11u2.dsc
 92633b2d98f6caa2fdaebcd0b15eb42d 251772 ruby optional 
ruby-rack_2.1.4.orig.tar.gz
 862f1e6641c5f34de6a892857bdef19f 14780 ruby optional 
ruby-rack_2.1.4-3+deb11u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmY7eyoACgkQiNJCh6LY
mLGHbw/+OP0+3O50ZlSIP2vbZUuw6+ddp56oMRl2V6/nNsuV7zrMp0KDZxPLAAnC
AAkGBKRSHqQw6SaU2SFG2qs3MCe0nRNNT4/rKaGKe06J7o1BEgtFV9vcHEWzvamn
zcL6bZIk8ybCKzGoZIC7SsDF6A9jDEu455GsLwGaD+Xfqpj2AJfdrFk05TZaHAKz
3PvUtM6wscwAis1uO1T3AFeGSmMPhT+4wmFY4VKMc3FB5/XoZpr/6xrqyJnrNK0b
LC6Dhcl0mvkguSMgZTzaxRn+x9jOP27YGACz+ScJzT5czF1AJrYI1FAkoOF/V5ol
mrBInyOWGIFHM5thCr6eGpiON/c5336qECUKhJZuxXEdUq9a40WAksiipaj4CI7v
6pwp3xYtS4c6y5yX1mpFkHdwwuN6OWiJ2h3OuB37Kqvcw3AN64grI/bMTJvUOIM2
S1qWxLZp59ha7iyhlYI7DD0jPe0oewmJmi/J+yQElfdoUFsLc7az0zwZ+WNaWz6f
wKjk8yb2fnMdoZICF9vd01aBc

[DRE-maint] Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 19:32:10 +
with message-id 
and subject line Bug#1064516: fixed in ruby-rack 2.2.6.4-1+deb12u1
has caused the Debian Bug report #1064516,
regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for ruby-rack.

CVE-2024-26141[0]:
Reject Range headers which are too large
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/62457686b26d33a15a254c7768c2076e8e02b48b 
(v2.2.8.1)

CVE-2024-25126[1]:
Fixed ReDoS in Content Type header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1

CVE-2024-26146[2]:
Fixed ReDoS in Accept header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/e4c117749ba24a66f8ec5a08eddf68deeb425ccd 
(v2.2.8.1)


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-26141
https://www.cve.org/CVERecord?id=CVE-2024-26141
[1] https://security-tracker.debian.org/tracker/CVE-2024-25126
https://www.cve.org/CVERecord?id=CVE-2024-25126
[2] https://security-tracker.debian.org/tracker/CVE-2024-26146
https://www.cve.org/CVERecord?id=CVE-2024-26146

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.2.6.4-1+deb12u1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
ruby-rack, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ruby-rack package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 May 2024 23:39:36 +0300
Source: ruby-rack
Architecture: source
Version: 2.2.6.4-1+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Adrian Bunk 
Closes: 1064516
Changes:
 ruby-rack (2.2.6.4-1+deb12u1) bookworm-security; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2024-25126: ReDoS in Content Type header parsing
   * CVE-2024-26141: Reject Range headers which are too large
   * CVE-2024-26146: ReDoS in Accept header parsing
   * Closes: #1064516
Checksums-Sha1:
 59cfba059f5e804d0f88cbcf7e340facc8bf1351 2385 ruby-rack_2.2.6.4-1+deb12u1.dsc
 c112aa25347c7eb7657ccde6a3c2315800cfef97 279212 ruby-rack_2.2.6.4.orig.tar.gz
 88a2b1c2c9db017508d364d0e323104ccf791a08 10924 
ruby-rack_2.2.6.4-1+deb12u1.debian.tar.xz
Checksums-Sha256:
 137cdca52c7f1dfb0a3468018ddf09d145bc7155467d47e134d8872706f9ad53 2385 
ruby-rack_2.2.6.4-1+deb12u1.dsc
 3cae965f53c4d556fd3d919729dfb698e86b8b6507045096c635ef4cf998f14b 279212 
ruby-rack_2.2.6.4.orig.tar.gz
 5f374d8bf401898ac557cb2d3a124c050741472f490642454830b49b37671598 10924 
ruby-rack_2.2.6.4-1+deb12u1.debian.tar.xz
Files:
 b682b52017acf8a03824460b889e62a9 2385 ruby optional 
ruby-rack_2.2.6.4-1+deb12u1.dsc
 77b35ec78eda851646a0c2bfe0f91e9e 279212 ruby optional 
ruby-rack_2.2.6.4.orig.tar.gz
 9d43b6a5f8218baceb0cbc452c0f17d2 10924 ruby optional 
ruby-rack_2.2.6.4-1+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmY7ekEACgkQiNJCh6LY
mLEIxBAAq3QahDFUt6FGWwz76IRzvf+Vfl+g5nFPW1wkWPKMQZtJ5UDzaha2Qygc
pGtAC0dWteIFe3iQGQxP1AaPR++MkmdywV9+L92NL5j3L4P25UQ3yw8hsbQUxIE9
DsWocaT6/CC4310juwpdE7LG4zOHV8exod1pgGKENAv/xWTE+0XYfiX90lLHWWS4
xORnKt8hHElax2u8iRQQ9KS0JPAQBgm9lrAqpIlDRGF8d1Kiaay7WNwIFMhO6omT
TWfSfgrpEMwN8SYbNckWMAlcQlyXUzCjmThcJOt6ldrCVTxTE2NAPph3CkqpX1FZ
rhWzyqjaPetPvPe1mAcp4tA4cbzHMZVALk/ClNUgqmc6eR2dmCXZjNIzrdhlll70
jJvWm36YhjHSbFjVVllRIs+hQHP1fPsSkAsDGaX8zTw2+7sBRrrR+xjszkpje9yS
AepYDWstJMWkapnYfHZPzUOHa/bzuY60TCYsibkbvBiMJaM3SoDvj2+n2Ulm

[DRE-maint] Bug#1055474: marked as done (redmine: CVE-2023-47258 CVE-2023-47259 CVE-2023-47260)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 19:32:09 +
with message-id 
and subject line Bug#1055474: fixed in redmine 5.0.4-5+deb12u1
has caused the Debian Bug report #1055474,
regarding redmine: CVE-2023-47258 CVE-2023-47259 CVE-2023-47260
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redmine
Version: 5.0.4-7
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for redmine.

CVE-2023-47258[0]:
| Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS in a
| Markdown formatter.


CVE-2023-47259[1]:
| Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS in the
| Textile formatter.


CVE-2023-47260[2]:
| Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS via
| thumbnails.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-47258
https://www.cve.org/CVERecord?id=CVE-2023-47258
[1] https://security-tracker.debian.org/tracker/CVE-2023-47259
https://www.cve.org/CVERecord?id=CVE-2023-47259
[2] https://security-tracker.debian.org/tracker/CVE-2023-47260
https://www.cve.org/CVERecord?id=CVE-2023-47260

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: redmine
Source-Version: 5.0.4-5+deb12u1
Done: Moritz Mühlenhoff 

We believe that the bug you reported is fixed in the latest version of
redmine, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated redmine package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 22 May 2024 19:53:22 +0200
Source: redmine
Architecture: source
Version: 5.0.4-5+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Moritz Mühlenhoff 
Closes: 1055474
Changes:
 redmine (5.0.4-5+deb12u1) bookworm-security; urgency=medium
 .
   * CVE-2023-47258 / CVE-2023-47259 / CVE-2023-47260 (Closes: #1055474)
Checksums-Sha1:
 37566e5d36f36f1725652317be1f1e12a09a568f 3397 redmine_5.0.4-5+deb12u1.dsc
 2cacdad65c92107403dc7825285a01af50193200 1882896 redmine_5.0.4.orig.tar.xz
 e0386a5e30bfef40cb57210583d397afea3869cb 181040 
redmine_5.0.4-5+deb12u1.debian.tar.xz
 a47e047f4136c7f81c9c85d979d55e9593431bf5 14204 
redmine_5.0.4-5+deb12u1_amd64.buildinfo
Checksums-Sha256:
 1e1174b4508f3881c170603dac68191c9e2007b8b75770a029ab6ee5d44acab6 3397 
redmine_5.0.4-5+deb12u1.dsc
 6fccf53629e8beaa6b0c5020a24f5c66acbb7b546d4e6f3fb62974d5e9274ec6 1882896 
redmine_5.0.4.orig.tar.xz
 d57b13f4b3f30eef2a0fecaec76b66c1e0db3653f56531cde6d3111b3580828f 181040 
redmine_5.0.4-5+deb12u1.debian.tar.xz
 8a8363a41937177b7f6abefe1e731a9d12f7c6aeb39f65a89e95c70bbff40d68 14204 
redmine_5.0.4-5+deb12u1_amd64.buildinfo
Files:
 33f796d2e0b633dfefdd06e41e5e6f29 3397 web optional redmine_5.0.4-5+deb12u1.dsc
 b260593aa05fd253f7742b856e061cde 1882896 web optional redmine_5.0.4.orig.tar.xz
 af9116dd0d61dda19182ddfd6e8ef00d 181040 web optional 
redmine_5.0.4-5+deb12u1.debian.tar.xz
 f7e84c6cb6426a837f8d44a843694f9e 14204 web optional 
redmine_5.0.4-5+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmZOMSAACgkQEMKTtsN8
TjaqRBAAsAl3fOX8SHjoUkwvyKodzfRaErU5JKugPUrgYnq1BwxoFQ+KQuBkGxJa
SHXk9SAxsQdaqE3t6W/kGdVSS/N+8S8+QqdjlNVg7DEuVow2NgjRw4wNPUrRdqwP
Ytz6jk7uUv50mUDT9AkNHprF9uTPVoE8orkUgFlSd+QjKWIsfMowc1n2lAjiz/QC
nLLu1PiGfgqlAIia79ANbLbxSnpFsDCreW70v7tNARPuI+kpVUeJfNZ8JrUYasIV
HLdt1dCsEHeNh3e8y5XKUXm34qh/VUb+FwJAPT9vnOEuqRxxiphPMbbOAxcTFtFu
HetU7sHwtRbG9QMJjdAisOZKuVqsxBnz/uaR+ElR5Vo2d7yfPsAvIrlrPDNzZtaG
ZoMBPczrROBHjpLfJhXf0gONfLxpqr4+bfaXvfneoKfiyJPTiBm9OmUK5z7cXFII
rCwJ2ZhQ8rYewf5Qm8q62eQ+KFDmAowHOkmNRzJGSn0SyuRIVWVsr45gnPT7lAqF
ZGQ6Yfh8jmYiM8HkY5HDQIA4nqLyGMZRkEQKM98TQyjjTD3KbFnIHse4MzUi

[DRE-maint] Bug#1042415: marked as done (ruby-aws-partitions: Package missing partitions.json)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:08:57 +
with message-id 
and subject line Bug#1042415: fixed in ruby-aws-partitions 1.653.0-3
has caused the Debian Bug report #1042415,
regarding ruby-aws-partitions: Package missing partitions.json
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-aws-partitions
Version: 1.653.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: ssg...@debian.org

In version 1.653.0-1, 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json 
is not present. It is there in version 1.354.0-2 in bullseye. Without that 
file, any actual use of this gem fails:

$ irb
irb(main):001:0> require 'aws-partitions'
=> true
irb(main):002:1* Aws::Partitions.each do |partition|
irb(main):003:1*   puts partition.name
irb(main):004:0> end
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in
 `read': No such file or directory @ rb_sysopen - 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/partitions.json 
(Errno::ENOENT)
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:225:in
 `defaults'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:214:in
 `default_partition_list'
from 
/usr/share/rubygems-integration/all/gems/aws-partitions-1.653.0/lib/aws-partitions.rb:137:in
 `each'
from (irb):2:in `'
from /usr/lib/ruby/gems/3.1.0/gems/irb-1.4.1/exe/irb:11:in `'
from /usr/bin/irb:25:in `load'
from /usr/bin/irb:25:in `'

Patch to fix is attached


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

Kernel: Linux 6.3.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 ruby-aws-partitions depends on:
ii  ruby  1:3.1

ruby-aws-partitions recommends no packages.

ruby-aws-partitions suggests no packages.

-- no debconf information
diff -Nru ruby-aws-partitions-1.653.0/debian/changelog 
ruby-aws-partitions-1.653.0/debian/changelog
--- ruby-aws-partitions-1.653.0/debian/changelog2022-10-30 
08:49:35.0 -0500
+++ ruby-aws-partitions-1.653.0/debian/changelog2023-07-27 
17:39:10.0 -0500
@@ -1,3 +1,11 @@
+ruby-aws-partitions (1.653.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Change DH_RUBY_GEM_INSTALL_WHITELIST_APPEND to DH_RUBY_GEM_INSTALL_INCLUDE
+in debian/rules to work with newer gem2deb
+
+ -- Stephen Gelman   Thu, 27 Jul 2023 17:39:10 -0500
+
 ruby-aws-partitions (1.653.0-1) unstable; urgency=medium
 
   * Team Upload
diff -Nru ruby-aws-partitions-1.653.0/debian/rules 
ruby-aws-partitions-1.653.0/debian/rules
--- ruby-aws-partitions-1.653.0/debian/rules2022-10-30 08:49:35.0 
-0500
+++ ruby-aws-partitions-1.653.0/debian/rules2023-07-27 17:36:38.0 
-0500
@@ -2,7 +2,7 @@
 
 export GEM2DEB_TEST_RUNNER = --check-dependencies
 export DH_RUBY = --gem-install
-export DH_RUBY_GEM_INSTALL_WHITELIST_APPEND := partitions.json
+export DH_RUBY_GEM_INSTALL_INCLUDE := partitions.json
 
 %:
dh $@ --buildsystem=ruby --with ruby
--- End Message ---
--- Begin Message ---
Source: ruby-aws-partitions
Source-Version: 1.653.0-3
Done: Pirate Praveen 

We believe that the bug you reported is fixed in the latest version of
ruby-aws-partitions, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-aws-partitions 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 May 2024 21:07:46 +0530
Source: ruby-aws-partitions
Architecture: source
Version: 

[DRE-maint] Processed: tagging 1071626, found 1071626 in 3.1.2-8.3, tagging 1071627, found 1071627 in 3.2.3-1 ...

2024-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1071626 + upstream
Bug #1071626 [src:ruby3.1] ruby3.1: CVE-2024-35176
Added tag(s) upstream.
> found 1071626 3.1.2-8.3
Bug #1071626 [src:ruby3.1] ruby3.1: CVE-2024-35176
Marked as found in versions ruby3.1/3.1.2-8.3.
> tags 1071627 + upstream
Bug #1071627 [src:ruby3.2] ruby3.2: CVE-2024-35176
Added tag(s) upstream.
> found 1071627 3.2.3-1
Bug #1071627 [src:ruby3.2] ruby3.2: CVE-2024-35176
Marked as found in versions ruby3.2/3.2.3-1.
> tags 1071628 + upstream
Bug #1071628 [src:python-pymysql] python-pymysql: CVE-2024-36039
Added tag(s) upstream.
> found 1071628 1.1.0-1
Bug #1071628 [src:python-pymysql] python-pymysql: CVE-2024-36039
Marked as found in versions python-pymysql/1.1.0-1.
> found 1071628 1.0.2-2
Bug #1071628 [src:python-pymysql] python-pymysql: CVE-2024-36039
Marked as found in versions python-pymysql/1.0.2-2.
> found 1071628 0.9.3-2
Bug #1071628 [src:python-pymysql] python-pymysql: CVE-2024-36039
Marked as found in versions python-pymysql/0.9.3-2.
> tags 1071630 + upstream
Bug #1071630 [src:maxima] maxima: CVE-2024-34490
Added tag(s) upstream.
> forwarded 1071630 https://sourceforge.net/p/maxima/bugs/3755/
Bug #1071630 [src:maxima] maxima: CVE-2024-34490
Set Bug forwarded-to-address to 'https://sourceforge.net/p/maxima/bugs/3755/'.
> found 1071630 5.46.0-11
Bug #1071630 [src:maxima] maxima: CVE-2024-34490
Marked as found in versions maxima/5.46.0-11.
> found 1071630 5.44.0-3
Bug #1071630 [src:maxima] maxima: CVE-2024-34490
Marked as found in versions maxima/5.44.0-3.
> tags 1071631 + upstream
Bug #1071631 [src:node-micromatch] node-micromatch: CVE-2024-4067
Added tag(s) upstream.
> forwarded 1071631 https://github.com/micromatch/micromatch/issues/243
Bug #1071631 [src:node-micromatch] node-micromatch: CVE-2024-4067
Set Bug forwarded-to-address to 
'https://github.com/micromatch/micromatch/issues/243'.
> tags 1071632 + upstream
Bug #1071632 [src:node-braces] node-braces: CVE-2024-4068
Added tag(s) upstream.
> forwarded 1071632 https://github.com/micromatch/braces/issues/35
Bug #1071632 [src:node-braces] node-braces: CVE-2024-4068
Set Bug forwarded-to-address to 
'https://github.com/micromatch/braces/issues/35'.
> tags 1071633 + upstream
Bug #1071633 [src:libmodbus] libmodbus: CVE-2024-34244
Added tag(s) upstream.
> forwarded 1071633 https://github.com/stephane/libmodbus/issues/743
Bug #1071633 [src:libmodbus] libmodbus: CVE-2024-34244
Set Bug forwarded-to-address to 
'https://github.com/stephane/libmodbus/issues/743'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1071626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071626
1071627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071627
1071628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071628
1071630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071630
1071631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071631
1071632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071632
1071633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: metadata

2024-05-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1063527 + ftbfs
Bug #1063527 [src:einsteinpy] einsteinpy: test_plotting fails to converge with 
scipy 1.11
Added tag(s) ftbfs.
> tags 1040334 + ftbfs
Bug #1040334 [facet-analyser] facet-analyser - build-depends on conflicting 
packages
Added tag(s) ftbfs.
> tags 1071043 + ftbfs
Bug #1071043 [libpsml-dev] libpsml-dev: unsatisfiable (Build-)Depends: 
libxmlf90-dev
Added tag(s) ftbfs.
> tags 1012320 + ftbfs
Bug #1012320 [src:materialize] materialize: build-depends on non-existing 
libjs-anime
Added tag(s) ftbfs.
> tags 1014605 + ftbfs
Bug #1014605 [src:node-functional.js] node-functional.js: FTBFS, missing 
build-dependencies
Added tag(s) ftbfs.
> tags 1002847 + ftbfs
Bug #1002847 [src:nttcp] nttcp: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Added tag(s) ftbfs.
> tags 1071017 + ftbfs
Bug #1071017 [obs-source-copy] FTBFS: source-copy.cpp:615:31: error: ‘void 
obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is 
deprecated [-Werror=deprecated-declarations]
Added tag(s) ftbfs.
> severity 1070545 serious
Bug #1070545 [src:php-fig-log-test] php-fig-log-test: FTBFS with phpunit 11: 
build-dependency not installable: php-psr-log (>= 2.0)
Severity set to 'serious' from 'normal'
> tags 1019042 + ftbfs
Bug #1019042 [src:qwertone] rust-qwertone: FTBFS - dep issue
Added tag(s) ftbfs.
> severity 1057677 serious
Bug #1057677 [src:resteasy] resteasy: ftbfs due to the missing dependency 
org.jboss.resteasy:resteasy-jaxrs:jar:3.6.2.Final
Severity set to 'serious' from 'important'
> tags 1025094 + ftbfs
Bug #1025094 [ruby-behance] ruby-behance fails to rebuild after new upstream of 
ruby-faraday
Added tag(s) ftbfs.
> tags 1025092 + ftbfs
Bug #1025092 [ruby-faraday-middleware] ruby-faraday-middleware fails to rebuild 
after updating ruby-faraday
Added tag(s) ftbfs.
> tags 1025090 + ftbfs
Bug #1025090 [ruby-gh] ruby-gh fails to rebuild on updating ruby-faraday
Added tag(s) ftbfs.
> tags 1037529 + ftbfs
Bug #1037529 [ruby-jekyll-github-metadata] ruby-jekyll-github-metadata: FTBFS 
with test failures when there's no network
Added tag(s) ftbfs.
> tags 1050580 + ftbfs
Bug #1050580 [src:ruby-roxml] ruby-roxml: broken by ruby-nokogiri 1.15.4
Added tag(s) ftbfs.
> tags 1050097 + ftbfs
Bug #1050097 [scrcpy] scrcpy: fails to build from source on arch:indep
Added tag(s) ftbfs.
> tags 1063827 + ftbfs
Bug #1063827 [src:tahoe-lafs] tahoe-lafs: new package tahoe-lafs depends on 
python3-future which is pending removal
Added tag(s) ftbfs.
> severity 1063827 serious
Bug #1063827 [src:tahoe-lafs] tahoe-lafs: new package tahoe-lafs depends on 
python3-future which is pending removal
Severity set to 'serious' from 'important'
> tags 1011492 + ftbfs
Bug #1011492 [src:tika] tika: FTBFS cannot find symbols
Added tag(s) ftbfs.
> tags 1050355 + ftbfs
Bug #1050355 [src:tiledarray] tiledarray has unfulfilled build dependencies
Added tag(s) ftbfs.
> tags 934977 + ftbfs
Bug #934977 [src:verilog-mode] verilog-mode: unbuildable in testing due to 
missing B-D emacs25
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1002847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002847
1011492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011492
1012320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012320
1014605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014605
1019042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019042
1025090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025090
1025092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025092
1025094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025094
1037529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037529
1040334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040334
1050097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050097
1050355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050355
1050580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050580
1057677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057677
1063527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063527
1063827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063827
1070545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070545
1071017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071017
1071043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071043
934977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1071002: marked as done (ruby-mysql2: FTBFS on ppc64el: test suite hangs)

2024-05-14 Thread Debian Bug Tracking System
Your message dated Tue, 14 May 2024 20:39:18 +
with message-id 
and subject line Bug#1071002: fixed in ruby-mysql2 0.5.5-3
has caused the Debian Bug report #1071002,
regarding ruby-mysql2: FTBFS on ppc64el: test suite hangs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1071002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-mysql2
Version: 0.5.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-powe...@lists.debian.org

Hi,

https://buildd.debian.org/status/fetch.php?pkg=ruby-mysql2=ppc64el=0.5.5-2=1715331286=0

It hangs with:

+ ruby3.1 -S rspec
E: Build killed with signal TERM after 150 minutes of inactivity

Build finished at 2024-05-10T08:54:25Z

It fails identically on powerpc and ppc64, so at least there's some
logic.

It built fine rather recently (2024-03-17) but that was a different
upstream version.

Lucas
--- End Message ---
--- Begin Message ---
Source: ruby-mysql2
Source-Version: 0.5.5-3
Done: Lucas Nussbaum 

We believe that the bug you reported is fixed in the latest version of
ruby-mysql2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1071...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated ruby-mysql2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 May 2024 22:16:29 +0200
Source: ruby-mysql2
Architecture: source
Version: 0.5.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Nussbaum 
Closes: 1071002
Changes:
 ruby-mysql2 (0.5.5-3) unstable; urgency=medium
 .
   * Rework patch 0008-Ignore-NotImplementedError-on-GC-compaction.patch
 into 0008-Ignore-compaction-bug-on-ruby3.1.patch
 to work around Compaction bug in ruby3.1. Closes: #1071002
Checksums-Sha1:
 a6bf560a53de54fc7b3adeea2dbb0e062f49e7df 2179 ruby-mysql2_0.5.5-3.dsc
 cb51a5d49fc9de8ef041433fef53273afadb0d94 9588 ruby-mysql2_0.5.5-3.debian.tar.xz
 d985f1d24e1253594f487d8680b9534afbe4619b 13143 
ruby-mysql2_0.5.5-3_source.buildinfo
Checksums-Sha256:
 6bb850ac28de40f907135d6bcdc513cec8cccd2859056e785b62430eed8975f2 2179 
ruby-mysql2_0.5.5-3.dsc
 9c3ab40a912e438f1e6f5d5b5460591e491c2b57b36d54252f6b7ca4c5cf7418 9588 
ruby-mysql2_0.5.5-3.debian.tar.xz
 2806d6a9339db75c019ae79212c018a1b1ed9abf829bdfc1b01476dc21af05c3 13143 
ruby-mysql2_0.5.5-3_source.buildinfo
Files:
 9a1f87c66e60f17495cc7e3816af0705 2179 ruby optional ruby-mysql2_0.5.5-3.dsc
 6c34c81266950d85174b9b904c587bca 9588 ruby optional 
ruby-mysql2_0.5.5-3.debian.tar.xz
 b899e06676d098d0524446eeb0a79d0b 13143 ruby optional 
ruby-mysql2_0.5.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE/t7ByzN7z1CfQ8IkORS1MvTfvpkFAmZDxsQACgkQORS1MvTf
vpk17hAAq7uwKsvNVZR3sOpbxCmkjQ+2NrTTCHUqWKc4EVqnwLGgxBy5V9Id4RHk
F3XcfAaX9XGMSVvrj7Ktn8vsAsWgiw1IU3te+nKSRwCXHubmfuiaszmcGLowtfIv
9ig5jCJj3cehddf9NTeZt8eNH4/fuygBWzugcQIMZDva8tY071aeESoBYUWR82s2
k6I9p9i8W71bdo/IhgvU2xffj/z6L5h0DmZLH9UfSfy4acKGom7MSfZ/lmruE8Ov
x6WOEilm5YTJS8+j99r50Xrgn/Zsvup4QcgXcG+vq9p/rDCdGpdwzgAA8CnX6ou1
snjZJ8Yt1l2TfpMcFPj76lybggy/E/4IedyUbq/GyUL5O1/LH8+gbOX2jNcrGRBC
NW9kKJALvZIXBWI18pNMsp9bnRqK53a5FY0R45Xj/TUwbNvLBT5bY8PN8uM/uDwK
Nt2FqC6K3wpeDZq8t8Nl9y2JbBIpVSwSQ+kq5A8ZNUZJhcxfeS6UvS9TWwoESKAr
fp/i0ABE5teffe8AvteNfXj/DAjCCaYZea/b01CqTowqzrcHSrrP8/VTlVGoZ+N1
GSY2zUwit7PoJ0PP8goOabnsetJ8mP98CIuksDxt+dAukW1NVqSmJaU1XwO3hn8w
UN5PWvIaNxhsz8Kj32vOVzEZ/18XDn/uj9BItfHV9BXkSTFf6rc=
=ZDw4
-END PGP SIGNATURE-



pgppKnHGBGbOw.pgp
Description: PGP signature
--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Bug#1071002 marked as pending in ruby-mysql2

2024-05-14 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1071002 [ruby-mysql2] ruby-mysql2: FTBFS on ppc64el: test suite hangs
Added tag(s) pending.

-- 
1071002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: user debian...@lists.debian.org, usertagging 1071010, tagging 1071010, found 1025090 in 0.18.0-5 ...

2024-05-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1071010 piuparts
Usertags were: fileconflict.
Usertags are now: piuparts fileconflict.
> tags 1071010 + fixed-upstream
Bug #1071010 [pcp] pcp has an undeclared file conflict on /usr/bin/pmcheck
Added tag(s) fixed-upstream.
> found 1025090 0.18.0-5
Bug #1025090 [ruby-gh] ruby-gh fails to rebuild on updating ruby-faraday
Marked as found in versions ruby-gh/0.18.0-5.
> usertags 1059228 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1059228 + libs2-0t64
Bug #1059228 [src:s2geometry] build system hard-codes -std=c++11
Added indication that 1059228 affects libs2-0t64
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1025090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025090
1059228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059228
1071010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1070835: marked as done (OBS does not correctly implement the bootstrap protocol)

2024-05-14 Thread Debian Bug Tracking System
Your message dated Tue, 14 May 2024 09:45:21 +0200
with message-id 
and subject line Re: Bug#1070835: update-alternatives: error: alternative path 
/bin/ed doesn't exist
has caused the Debian Bug report #1070835,
regarding OBS does not correctly implement the bootstrap protocol
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1070835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ed
Version: 1.20.2-2

Dear maintainer,

in Debian sid, installing ed fails with:

  [49/600] installing ed-1.20.2-2
  update-alternatives: error: alternative path /bin/ed doesn't exist

It looks like this is related to usr merge, the binary seems to be in
/usr/bin/ed now: https://packages.debian.org/sid/amd64/ed/filelist

The error happens in an opensuse build server, trying to build a Debian
package that depends on ed.

Best regards,
Oliver

--
- Oliver Smith https://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Siemensstr. 26a
* 10551 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
--- End Message ---
--- Begin Message ---

Thanks! Closing this bug report then.

If anybody else has the same problem and finds this, I've worked around
it with the following project config in OBS now:

%if %_repository == "Debian_Unstable"
Ignore: ed
%endif

Best regards,
Oliver


On 13.05.24 20:58, Helmut Grohne wrote:

Control: retitle -1 OBS does not correctly implement the bootstrap protocol
Control: reassign -1 src:open-build-service
Control: affects -1 + ed

Hi,

On Fri, May 10, 2024 at 10:48:54AM +0200, Oliver Smith wrote:

in Debian sid, installing ed fails with:

   [49/600] installing ed-1.20.2-2
   update-alternatives: error: alternative path /bin/ed doesn't exist

It looks like this is related to usr merge, the binary seems to be in
/usr/bin/ed now: https://packages.debian.org/sid/amd64/ed/filelist

The error happens in an opensuse build server, trying to build a Debian
package that depends on ed.


The bootstrap protocol requires that every transitively essential
package has been configured at least once before installing other
packages. ed is such an other package.  Therefore, we may assume that
usrmerge or usr-is-merged (which are a dependency of essential
init-system-helpers) has been configured at least once. OBS has its own
bootstrap strategy that violates this requirement. The bug is to be
found there rather than in ed.

Helmut



--
- Oliver Smith https://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Siemensstr. 26a
* 10551 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: BTS housekeeping

2024-05-13 Thread Debian Bug Tracking System
 src:python-marshmallow-sqlalchemy
Added indication that 1066784 affects 
src:prettytable,src:python-marshmallow-sqlalchemy,src:python-b2sdk,src:pyresample,src:satpy,src:pycoast
Removed indication that 1066785 affects src:python-b2sdk, src:satpy, 
src:prettytable, src:pyresample, src:python-marshmallow-sqlalchemy, and 
src:pycoast
Added indication that 1066785 affects 
src:prettytable,src:python-marshmallow-sqlalchemy,src:python-b2sdk,src:pyresample,src:satpy,src:pycoast
Removed indication that 1066789 affects src:python-marshmallow-sqlalchemy, 
src:pycoast, src:python-b2sdk, src:satpy, src:prettytable, and src:pyresample
Added indication that 1066789 affects 
src:prettytable,src:python-marshmallow-sqlalchemy,src:python-b2sdk,src:pyresample,src:satpy,src:pycoast
Bug #1066757 [src:python-pytest-lazy-fixture] prettytable: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Set Bug forwarded-to-address to 
'https://github.com/TvoroG/pytest-lazy-fixture/issues/65'.
1071069 was blocked by: 1066757
1071069 was not blocking any bugs.
Removed blocking bug(s) of 1071069: 1066757
Added indication that 1066757 affects 
src:prettytable,src:python-marshmallow-sqlalchemy,src:python-b2sdk,src:pyresample,src:satpy,src:pycoast
The source python3-pytest-lazy-fixture and version 0.6.3-2 do not appear to 
match any binary packages
Marked as found in versions python-pytest-lazy-fixture/0.6.3-2 and 
python3-pytest-lazy-fixture/0.6.3-2.
Added tag(s) upstream.
Bug #1066727 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: Needs 
update for Pytest 8 (AttributeError: 'CallSpec2' object has no attribute 
'funcargs')
Bug #1066784 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.12 3.11" returned exit code 13
Bug #1066785 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
"3.12 3.11" returned exit code 13
Bug #1066789 [src:python-pytest-lazy-fixture] pycoast: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Merged 1063957 1063973 1066727 1066757 1066784 1066785 1066789
> forcemerge 1057443 1057639
Bug #1057443 [src:sqlalchemy] sqlalchemy ftbfs with Python 3.12
Bug #1057639 [src:sqlalchemy] sqlalchemy ftbfs with Python 3.12 (segfault 
during tests)
Added tag(s) experimental, trixie, ftbfs, and sid.
Merged 1057443 1057639
> close 1066771 0.0.16-1
Bug #1066771 [src:sqlmodel] sqlmodel: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked as fixed in versions sqlmodel/0.0.16-1.
Bug #1066771 [src:sqlmodel] sqlmodel: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked Bug as done
> reassign 1067251 src:rust-isahc 1.7.2+ds-26
Bug #1067251 [librust-isahc-dev] librust-isahc-dev: impossible to install
Bug reassigned from package 'librust-isahc-dev' to 'src:rust-isahc'.
No longer marked as found in versions rust-isahc/1.7.2+ds-25.
Ignoring request to alter fixed versions of bug #1067251 to the same values 
previously set
Bug #1067251 [src:rust-isahc] librust-isahc-dev: impossible to install
The source 'rust-isahc' and version '1.7.2+ds-26' do not appear to match any 
binary packages
Marked as found in versions rust-isahc/1.7.2+ds-26.
> retitle 1067251 rust-isahc FTBFS with polling 3
Bug #1067251 [src:rust-isahc] librust-isahc-dev: impossible to install
Changed Bug title to 'rust-isahc FTBFS with polling 3' from 'librust-isahc-dev: 
impossible to install'.
> tags 1067251 ftbfs
Bug #1067251 [src:rust-isahc] rust-isahc FTBFS with polling 3
Added tag(s) ftbfs.
> affects 1067251 librust-isahc-dev
Bug #1067251 [src:rust-isahc] rust-isahc FTBFS with polling 3
Added indication that 1067251 affects librust-isahc-dev
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1027339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027339
1027350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027350
1057443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057443
1057639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057639
1063957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063957
1063973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063973
1066727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066727
1066757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066757
1066771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066771
1066784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066784
1066785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066785
1066789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066789
1067251: https://bugs.d

[DRE-maint] Processed: Re: Bug#1070835: update-alternatives: error: alternative path /bin/ed doesn't exist

2024-05-13 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 OBS does not correctly implement the bootstrap protocol
Bug #1070835 [ed] update-alternatives: error: alternative path /bin/ed doesn't 
exist
Changed Bug title to 'OBS does not correctly implement the bootstrap protocol' 
from 'update-alternatives: error: alternative path /bin/ed doesn't exist'.
> reassign -1 src:open-build-service
Bug #1070835 [ed] OBS does not correctly implement the bootstrap protocol
Bug reassigned from package 'ed' to 'src:open-build-service'.
No longer marked as found in versions ed/1.20.2-2.
Ignoring request to alter fixed versions of bug #1070835 to the same values 
previously set
> affects -1 + ed
Bug #1070835 [src:open-build-service] OBS does not correctly implement the 
bootstrap protocol
Added indication that 1070835 affects ed

-- 
1070835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: src:ruby-parslet: fails to migrate to testing for too long: triggers autopkgtest issues

2024-05-12 Thread Debian Bug Tracking System
Processing control commands:

> close -1 2.0.0-1
Bug #1070989 [src:ruby-parslet] src:ruby-parslet: fails to migrate to testing 
for too long: triggers autopkgtest issues
Marked as fixed in versions ruby-parslet/2.0.0-1.
Bug #1070989 [src:ruby-parslet] src:ruby-parslet: fails to migrate to testing 
for too long: triggers autopkgtest issues
Marked Bug as done

-- 
1070989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby2.7: FTBFS: failing tests

2024-05-11 Thread Debian Bug Tracking System
Processing control commands:

> close -1 2.7.5-1+rm
Bug #1070962 [src:ruby2.7] ruby2.7: FTBFS: failing tests
The source 'ruby2.7' and version '2.7.5-1+rm' do not appear to match any binary 
packages
Marked as fixed in versions ruby2.7/2.7.5-1+rm.
Bug #1070962 [src:ruby2.7] ruby2.7: FTBFS: failing tests
Marked Bug as done

-- 
1070962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby-sinatra: FTBFS in bullseye

2024-05-11 Thread Debian Bug Tracking System
Processing control commands:

> close -1 3.0.5-3
Bug #1070953 [src:ruby-sinatra] ruby-sinatra: FTBFS in bullseye
Marked as fixed in versions ruby-sinatra/3.0.5-3.
Bug #1070953 [src:ruby-sinatra] ruby-sinatra: FTBFS in bullseye
Marked Bug as done

-- 
1070953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1070731: marked as done (ruby-kramdown-rfc2629: new upstream version 1.7.11 available)

2024-05-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 May 2024 19:20:30 +
with message-id 
and subject line Bug#1070731: fixed in ruby-kramdown-rfc2629 1.7.11-1~exp1
has caused the Debian Bug report #1070731,
regarding ruby-kramdown-rfc2629: new upstream version 1.7.11 available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1070731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-kramdown-rfc2629
Version: 1.7.1-1~exp1
Severity: wishlist
X-Debbugs-Cc: Daniel Kahn Gillmor 

Dear Maintainer,

kramdown-rfc 1.7.11 is available upstream -- it would be great to have
this in debian, because it offers a feature that i hope to use for
draft-ietf-lamps-header-protection (nested ordered lists).

If there's a reason to keep it in experimental, i could deal with that,
but it'd be even nicer if we could put it directly in unstable ☺

Thanks for maintaining kramdown-rfc in debian!

 --dkg

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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)

Versions of packages ruby-kramdown-rfc2629 depends on:
ii  libruby3.1t64 [ruby-json]  3.1.2-8.3
ii  ruby   1:3.1+nmu1
ii  ruby-kramdown  2.4.0-2
ii  ruby-kramdown-parser-gfm   1.1.0-3
ii  ruby-net-http-persistent   4.0.2-2

ruby-kramdown-rfc2629 recommends no packages.

Versions of packages ruby-kramdown-rfc2629 suggests:
ii  aasvg0.3.2-1
ii  xml2rfc  3.21.0-1

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-kramdown-rfc2629
Source-Version: 1.7.11-1~exp1
Done: Daniel Kahn Gillmor 

We believe that the bug you reported is fixed in the latest version of
ruby-kramdown-rfc2629, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated 
ruby-kramdown-rfc2629 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 May 2024 14:24:48 -0400
Source: ruby-kramdown-rfc2629
Architecture: source
Version: 1.7.11-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Daniel Kahn Gillmor 
Closes: 1070731
Changes:
 ruby-kramdown-rfc2629 (1.7.11-1~exp1) experimental; urgency=medium
 .
   * New upstream version 1.7.11 (Closes: #1070731)
Checksums-Sha1:
 28427e57c3a91db45958912bdecdf1cc12374c59 1783 
ruby-kramdown-rfc2629_1.7.11-1~exp1.dsc
 b48736cca40087ec2e050d36851c5fb9f2abb1b8 60314 
ruby-kramdown-rfc2629_1.7.11.orig.tar.gz
 c767c109a8ad454c4d8edc5702be49c01eb819f0 6488 
ruby-kramdown-rfc2629_1.7.11-1~exp1.debian.tar.xz
 1dd4879ffc7c1e0e59ff347f0f9d97c1c4fc 18645 
ruby-kramdown-rfc2629_1.7.11-1~exp1_amd64.buildinfo
Checksums-Sha256:
 007c15bd7fbfd091a5f085150ba46e273f894c499fa3e0be13ade35f9fad87fc 1783 
ruby-kramdown-rfc2629_1.7.11-1~exp1.dsc
 c7e052dd528f4e1c045bc43cbad532dbab852042f4f0dc948f7780f9dcba976c 60314 
ruby-kramdown-rfc2629_1.7.11.orig.tar.gz
 249e5e2c60f59a318c74463a24952c899cc03b96d65ad53263a757b74e5c460a 6488 
ruby-kramdown-rfc2629_1.7.11-1~exp1.debian.tar.xz
 18fb0c754cde3381ed1c6bc5fa72b2b9bae767e1475f0a78f138baa7d768467f 18645 
ruby-kramdown-rfc2629_1.7.11-1~exp1_amd64.buildinfo
Files:
 6dab722ee0532e14c8861dbdfe432c81 1783 ruby optional 
ruby-kramdown-rfc2629_1.7.11-1~exp1.dsc
 062d8e3ef1058a69016293ab1c8aec0c 60314 ruby optional 
ruby-kramdown-rfc2629_1.7.11.orig.tar.gz
 a3a20b8e8073441f32bc4a9bffbd4f5c 6488 ruby optional 
ruby-kramdown-rfc2629_1.7.11-1~exp1.debian.tar.xz
 cb780eea2e316a7db661834c7f407f22 18645 ruby optional 
ruby-kramdown-rfc2629_1.7.11-1~exp1_amd64

[DRE-maint] Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-05-07 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://github.com/taf2/curb/issues/451
Bug #1069258 [src:ruby-curb] ruby-curb: test regression with curl 8.7.1: client 
read function EOF fail, only only 4/5 of needed bytes read
Set Bug forwarded-to-address to 'https://github.com/taf2/curb/issues/451'.

-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: reassign 1070652 to how-can-i-help

2024-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1070652 how-can-i-help
Bug #1070652 [ruby-json] ruby-json: breaks how-can-i-help
Bug reassigned from package 'ruby-json' to 'how-can-i-help'.
No longer marked as found in versions ruby-json/2.7.2+dfsg-1.
Ignoring request to alter fixed versions of bug #1070652 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1070652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1070420: marked as done (src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2))

2024-05-06 Thread Debian Bug Tracking System
Your message dated Mon, 06 May 2024 20:15:54 +
with message-id 
and subject line Bug#1070420: fixed in vagrant 2.3.7+git20230731.5fc64cde+dfsg-1
has caused the Debian Bug report #1070420,
regarding src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp 
(>= 0.2) | ruby-net-ftp (>= 0.2)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1070420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: vagrant
Version: 2.3.6+dfsg-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing. ruby3.2 which provides these versions of 
ruby-net-ftp is currently blocked by three RC bugs. I also note that the 
runtime dependency of bin:vagrant is non-versioned.


Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Done: Lucas Nussbaum 

We believe that the bug you reported is fixed in the latest version of
vagrant, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1070...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated vagrant package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 May 2024 21:08:41 +0200
Source: vagrant
Architecture: source
Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Lucas Nussbaum 
Closes: 1070420
Changes:
 vagrant (2.3.7+git20230731.5fc64cde+dfsg-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Drop myself from Uploaders
 .
   [ Lucas Nussbaum ]
   * New upstream version 2.3.7+git20230731.5fc64cde+dfsg
 + This is the last commit before the license change to BUSL.
   * Add patch: 0009-Raise-error-if-openssl-headers-not-found.patch
   * Add build-dep on libssl-dev and switch to Architecture: any to build the
 vagrant_ssl extension
   * Fix rubygems-integration path due to the above arch:any change
   * Drop Build-dep on ruby-net-ftp, which is provided by libruby3.X anyway.
 Closes: #1070420
   * Remove watch file: we don't expect upstream updates
   * Add patch 0010-Remove-shebang-from-bash-completion-file.patch to fix
 lintian warning.
Checksums-Sha1:
 eee205a181034b05eb8b9ad83ffb89abaebee5dc 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ef0f0bc1a4197501b9a450a29f0c130d4e0a621d 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 7eddd398161025cd378398e63e818bcd853a885f 16952 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.debian.tar.xz
 f60e9d518236336deae93f016aa0303789f9093f 11025 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1_source.buildinfo
Checksums-Sha256:
 6efdd239246811af8ca5c35e9278c06539b3707fcf9af8f9f537699d302ad576 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ccddc8f97704a7d393d932ec0bd3d46b85ad71a7ca5c6c74ee5d7163b96925d2 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 fa67d6c4791d69d3a42e665f404498028f5fb64ca7c3a657ad2822c9f6863305

[DRE-maint] Processed: Bug#1070420 marked as pending in vagrant

2024-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1070420 [src:vagrant] src:vagrant: unsatisfied build dependency in 
testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2)
Added tag(s) pending.

-- 
1070420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1064034: marked as done (FTBFS: Expired test certificate)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:49:19 +
with message-id 
and subject line Bug#1064034: fixed in ruby3.1 3.1.2-7+deb12u1
has caused the Debian Bug report #1064034,
regarding FTBFS: Expired test certificate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby3.1
Version: 3.1.2-8
Severity: serious
Tags: ftbfs

A build of ruby3.1 fails on the test stage, since multiple
test/net/http/test_https.rb tests return 

> "ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0
peeraddr=(null) state=error: sslv3 alert certificate expired\n"

where no error was expected.


Failing tests:
TestNetHTTPS#test_get, TestNetHTTPS#test_skip_hostname_verification,
TestNetHTTPS#test_skip_hostname_verification, TestNetHTTPS#test_post,
TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI,
TestNetHTTPS#test_get, TestNetHTTPS#test_post,
TestNetHTTPS#test_min_version, TestNetHTTPS#test_get_SNI


The actual reason is that the certificate it uses (file
test/net/fixtures/server.crt) *IS* expired:

$ openssl x509 -in test/net/fixtures/server.crt -text
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 2 (0x2)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = JP, ST = Shimane, L = Matz-e city, O = Ruby Core Team, CN = 
Ruby Test CA, emailAddress = secur...@ruby-lang.org
Validity
Not Before: Jan  2 03:27:13 2019 GMT
Not After : Jan  1 03:27:13 2024 GMT
Subject: C = JP, ST = Shimane, O = Ruby Core Team, OU = Ruby Test, CN = 
localhost


This was fixed upstream on 
https://github.com/ruby/ruby/commit/d3933fc753187a055a4904af82f5f3794c88c416
--- End Message ---
--- Begin Message ---
Source: ruby3.1
Source-Version: 3.1.2-7+deb12u1
Done: Moritz Mühlenhoff 

We believe that the bug you reported is fixed in the latest version of
ruby3.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Moritz Mühlenhoff  (supplier of updated ruby3.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Apr 2024 09:47:47 +0200
Source: ruby3.1
Architecture: source
Version: 3.1.2-7+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Moritz Mühlenhoff 
Closes: 1064034
Changes:
 ruby3.1 (3.1.2-7+deb12u1) bookworm-security; urgency=medium
 .
   * CVE-2024-27280 / CVE-2024-27281 / CVE-2024-27282
   * Cherrypick changes from 3.1.2-8.2 upload to sid:
 * Update test certificates from ruby 3.2.3. (Closes: #1064034)
 * Disable test needing a working DNS resolver.
Checksums-Sha1:
 7f14017ddc58d15190bf308efcb60030ec3c0b26 2595 ruby3.1_3.1.2-7+deb12u1.dsc
 9a0840a5a26dcdbd9e9eebe3354598375a4a6b6d 12885596 ruby3.1_3.1.2.orig.tar.xz
 dcf086fd43032b9ec0b8c975e2e6baa810408749 80764 
ruby3.1_3.1.2-7+deb12u1.debian.tar.xz
 bf19498a307a05e8e312fe33bb9a525a25706a7f 8628 
ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo
Checksums-Sha256:
 a04e26298ae7202d46a45587dc7ce4fb696aa2d3df2699e1684ccf126b6f6840 2595 
ruby3.1_3.1.2-7+deb12u1.dsc
 350013ef6640f15c42eae48d25c035999dcbb32e4be038d27ad891cb48d685a5 12885596 
ruby3.1_3.1.2.orig.tar.xz
 c2687c741a45046b9652f84734ceb83554b1583c88acc6ac94660d1d504d14a8 80764 
ruby3.1_3.1.2-7+deb12u1.debian.tar.xz
 b92d271efacaa6c4bbeb7e8a06d58a90eb0a0848f4445a17d11c7ce65601b17f 8628 
ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo
Files:
 7bd09d163012362edf54a117ff937926 2595 ruby optional ruby3.1_3.1.2-7+deb12u1.dsc
 69cf9ca520a804bff39ab22e1b798b4b 12885596 ruby optional 
ruby3.1_3.1.2.orig.tar.xz
 85e50f242976d9f3706fcada55d13f24 80764 ruby optional 
ruby3.1_3.1.2-7+deb12u1.debian.tar.xz
 a6b17b3f8bf8f52363eaad9234e5bf38 8628 ruby optional 
ruby3.1_3.1.2-7+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmYraMcACgkQEMKTtsN8
TjaHJg//YH99gZzNbYuqw9kkhZ9yxCjLirfgOOMRKpQLZvqYcDzcDvyDnfClat7A
VHMfXPpYl9WcPu6agx0r4JMXGBouY27W1DvSZRNl+Eg1CANos5Z

[DRE-maint] Bug#1055297: marked as done (ruby3.1: fails to build against glibc 2.38)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 5 May 2024 12:26:40 +0200
with message-id 
and subject line Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38
has caused the Debian Bug report #1055297,
regarding ruby3.1: fails to build against glibc 2.38
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby3.1
Version: 3.1.2-7
Severity: important
Tags: patch

Hello,

ruby3.1 fails to build against glibc 2.38:

dpkg-gensymbols -plibruby3.1 -Idebian/libruby3.1.symbols -Pdebian/libruby3.1 
-edebian/libruby3.1/usr/lib/x86_64-gnu/libruby-3.1.so.3.1.2
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libruby3.1/DEBIAN/symbols doesn't match 
completely debian/libruby3.1.symbols
--- debian/libruby3.1.symbols (libruby3.1_3.1.2-7_hurd-amd64)
+++ dpkg-gensymbols5L9SYx   2023-11-03 17:57:31.0 +
[...]
@@ -1818,5 +1818,5 @@
  ruby_xrealloc2@Base 3.1.0~preview1
  ruby_xrealloc@Base 3.1.0~preview1
  setproctitle@Base 3.1.0~preview1
- strlcat@Base 3.1.0~preview1
- strlcpy@Base 3.1.0~preview1
+#MISSING: 3.1.2-7# strlcat@Base 3.1.0~preview1
+#MISSING: 3.1.2-7# strlcpy@Base 3.1.0~preview1

strlcat and strlcpy were indeed added to glibc in version 2.38, so it's
not surprising that ruby3.1 doesn't define its internal versions any
more, and the attached patch can probably be applied?

Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 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 ruby3.1 depends on:
ii  libc6 2.37-12
ii  libcrypt1 1:4.4.36-2
ii  libgmp10  2:6.3.0+dfsg-2
ii  libruby3.13.1.2-7
ii  rubygems-integration  1.18
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages ruby3.1 recommends:
ii  fonts-lato2.015-1
ii  libjs-jquery  3.6.1+dfsg+~3.5.14-1

ruby3.1 suggests no packages.

-- no debconf information

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/libruby3.1.symbols.original  2023-11-03 18:01:01.0 +
+++ debian/libruby3.1.symbols   2023-11-03 18:01:23.0 +
@@ -1818,5 +1818,5 @@
  ruby_xrealloc2@Base 3.1.0~preview1
  ruby_xrealloc@Base 3.1.0~preview1
  setproctitle@Base 3.1.0~preview1
- strlcat@Base 3.1.0~preview1
- strlcpy@Base 3.1.0~preview1
+ (optional)strlcat@Base 3.1.0~preview1
+ (optional)strlcpy@Base 3.1.0~preview1
--- End Message ---
--- Begin Message ---
Version: 3.1.2-8

Hi again,

On 2024-05-05 12:18, Aurelien Jarno wrote:
> control: severity -1 serious
> 
> Hi,
> 
> On 2023-11-03 19:45, Samuel Thibault wrote:
> > Package: ruby3.1
> > Version: 3.1.2-7
> > Severity: important
> > Tags: patch
> > 
> > Hello,
> > 
> > ruby3.1 fails to build against glibc 2.38:
> > 
> > dpkg-gensymbols -plibruby3.1 -Idebian/libruby3.1.symbols 
> > -Pdebian/libruby3.1 
> > -edebian/libruby3.1/usr/lib/x86_64-gnu/libruby-3.1.so.3.1.2
> > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> > file: see diff output below
> > dpkg-gensymbols: warning: debian/libruby3.1/DEBIAN/symbols doesn't match 
> > completely debian/libruby3.1.symbols
> > --- debian/libruby3.1.symbols (libruby3.1_3.1.2-7_hurd-amd64)
> > +++ dpkg-gensymbols5L9SYx   2023-11-03 17:57:31.0 +
> > [...]
> > @@ -1818,5 +1818,5 @@
> >   ruby_xrealloc2@Base 3.1.0~preview1
> >   ruby_xrealloc@Base 3.1.0~preview1
> >   setproctitle@Base 3.1.0~preview1
> > - strlca

[DRE-maint] Processed: Re: Bug#1055297: ruby3.1: fails to build against glibc 2.38

2024-05-05 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1055297 [ruby3.1] ruby3.1: fails to build against glibc 2.38
Severity set to 'serious' from 'important'

-- 
1055297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 May 2024 21:17:14 +
with message-id 
and subject line Bug#1064516: fixed in ruby-rack 2.2.7-1.1
has caused the Debian Bug report #1064516,
regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for ruby-rack.

CVE-2024-26141[0]:
Reject Range headers which are too large
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/62457686b26d33a15a254c7768c2076e8e02b48b 
(v2.2.8.1)

CVE-2024-25126[1]:
Fixed ReDoS in Content Type header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1

CVE-2024-26146[2]:
Fixed ReDoS in Accept header parsing
https://github.com/rack/rack/releases/tag/v2.2.8.1
https://github.com/rack/rack/commit/e4c117749ba24a66f8ec5a08eddf68deeb425ccd 
(v2.2.8.1)


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-26141
https://www.cve.org/CVERecord?id=CVE-2024-26141
[1] https://security-tracker.debian.org/tracker/CVE-2024-25126
https://www.cve.org/CVERecord?id=CVE-2024-25126
[2] https://security-tracker.debian.org/tracker/CVE-2024-26146
https://www.cve.org/CVERecord?id=CVE-2024-26146

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.2.7-1.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
ruby-rack, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated ruby-rack package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 May 2024 22:55:26 +0300
Source: ruby-rack
Architecture: source
Version: 2.2.7-1.1
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Team 

Changed-By: Adrian Bunk 
Closes: 1064516
Changes:
 ruby-rack (2.2.7-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * CVE-2024-25126: ReDoS in Content Type header parsing
   * CVE-2024-26141: Reject Range headers which are too large
   * CVE-2024-26146: ReDoS in Accept header parsing
   * Closes: #1064516
Checksums-Sha1:
 f74ea2d462b8737d733fabf353e6c3d9797b2d84 2347 ruby-rack_2.2.7-1.1.dsc
 5f0f4c3a182eba4c4066b011623f01053c8ebc8e 279222 ruby-rack_2.2.7.orig.tar.gz
 6150b1489f5bbf7e4164c9da072976b3d3988d51 10932 
ruby-rack_2.2.7-1.1.debian.tar.xz
Checksums-Sha256:
 1dd5f94772d834d6b0f24d64d4890223f7fdc6c6b1248190acaf2e7726f3779d 2347 
ruby-rack_2.2.7-1.1.dsc
 e942379fba7a6aa18951973a95cc323c10af7aa7ff61207794bf6fea3ec822b4 279222 
ruby-rack_2.2.7.orig.tar.gz
 0bf5154539fdedd122ec3faef1f207681503559d0af4e348c29da701e31dda71 10932 
ruby-rack_2.2.7-1.1.debian.tar.xz
Files:
 d34fa63feef913c5426dfaa79cdaa82b 2347 ruby optional ruby-rack_2.2.7-1.1.dsc
 09f5512b2919ceffc5ab777aebf0c88a 279222 ruby optional 
ruby-rack_2.2.7.orig.tar.gz
 946e35965f30969180924c81317cb52f 10932 ruby optional 
ruby-rack_2.2.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmYz8XMACgkQiNJCh6LY
mLFy/Q/+OEpOrUfoSpwiFtXW6q5qSRCeRMCFTn40LGI3Qtfn5r8Yrj9/cMh7XTIE
OBXyEItK6BO5InugVO8qBe89dC77aql4L5AcGcZYpOBySGjWd7+WBY7HLqWjjDN5
d3jVq/kYQnpgahh0NkN9wu6Pe+e5J9/OSXW2XRAuAfEi8hMcpJSMnKlUp79GTNVE
ht92LRprlftq4tkCMeB47gTQF16fTZHTsaN02rdN5yoTiGyw3IGto6+flMztzq5e
EDaK3AnMwYgkzmlKT/xSz6zKCNi9N51kuyOpcUHFvQ5WieLoHvQ9TOjrU5W4Gq8y
2oWTZmVbwn0r+SbKtzsUWGT2bB4Omun618yvqDcwMuLe+L7oHjdIdGDsWIVeT/o1
7p1OYoGjhfZbje6YG5ckb3CPaaeGbxDhy/Zo/Is82buU+kFG0nOPunYUpyyfXMk7
n6fqBt2Fup/iPA9JFL6J+Fu2TpC3UpA+Kr/2pEqFnxIdB2YhNNmY44qTdpfu6pKP
sK0xoTlAM+H0ZpKqkybAG737+06b3PrC7kpWEcnPNCXUs5vqoGM1R3AyBpcJvpCT
nVbU3G3yHX6dIIBuBZr7muR47UGio+Wp

[DRE-maint] Processed: ruby-rack: diff for NMU version 2.2.7-1.1

2024-05-02 Thread Debian Bug Tracking System
Processing control commands:

> tags 1064516 + patch
Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 
CVE-2024-26146
Added tag(s) patch.
> tags 1064516 + pending
Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 
CVE-2024-26146
Added tag(s) pending.

-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: found 1064516 in 2.0.6-3

2024-04-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 1064516 2.0.6-3
Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 
CVE-2024-26146
Marked as found in versions ruby-rack/2.0.6-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1064516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 946983

2024-04-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 946983
Bug #946983 [src:ruby-rack] ruby-rack: CVE-2019-16782
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
946983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Re: Bug#1036369: ruby-rest-client: network-dependent tests fail

2024-04-27 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1036369 [ruby-rest-client] ruby-rest-client: network-dependent tests fail
Severity set to 'serious' from 'normal'

-- 
1036369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: reassign 1069969 to src:ruby3.1, found 1069969 in 3.1.2-7

2024-04-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1069969 src:ruby3.1 3.1.2-8
Bug #1069969 [src:ruby3.2] ruby3.1: CVE-2024-27282
Bug reassigned from package 'src:ruby3.2' to 'src:ruby3.1'.
No longer marked as found in versions ruby3.2/3.1.2-7 and ruby3.2/3.2.3-1.
Ignoring request to alter fixed versions of bug #1069969 to the same values 
previously set
Bug #1069969 [src:ruby3.1] ruby3.1: CVE-2024-27282
Marked as found in versions ruby3.1/3.1.2-8.
> found 1069969 3.1.2-7
Bug #1069969 [src:ruby3.1] ruby3.1: CVE-2024-27282
Marked as found in versions ruby3.1/3.1.2-7.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed (with 1 error): ruby3.2: CVE-2024-27282

2024-04-27 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #1069968 [src:ruby3.2] ruby3.2: CVE-2024-27282
Bug 1069968 cloned as bug 1069969
> reassign -2 src;ruby3.1 3.1.2-8
Unknown command or malformed arguments to command.

> retitle -2 ruby3.1: CVE-2024-27282
Bug #1069969 [src:ruby3.2] ruby3.2: CVE-2024-27282
Changed Bug title to 'ruby3.1: CVE-2024-27282' from 'ruby3.2: CVE-2024-27282'.
> found -2 3.1.2-7
Bug #1069969 [src:ruby3.2] ruby3.1: CVE-2024-27282
The source 'ruby3.2' and version '3.1.2-7' do not appear to match any binary 
packages
Marked as found in versions ruby3.2/3.1.2-7.

-- 
1069968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069968
1069969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: ruby3.1: CVE-2024-27280: Buffer overread vulnerability in StringIO

2024-04-27 Thread Debian Bug Tracking System
Processing control commands:

> found -1 3.1.2-7
Bug #1069966 [src:ruby3.1] ruby3.1: CVE-2024-27280: Buffer overread 
vulnerability in StringIO
Marked as found in versions ruby3.1/3.1.2-7.

-- 
1069966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: Re: Bug#1069258: ruby-curb: test regression with curl 8.7.1: client read function EOF fail, only only 4/5 of needed bytes read

2024-04-25 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 ruby-curb: test regression with curl 8.7.1: client read function 
> EOF fail, only only 4/5 of needed bytes read
Bug #1069258 [src:ruby-curb] ruby-curb: FTBFS: 178 tests, 699 assertions, 0 
failures, 7 errors, 0 pendings, 0 omissions, 0 notifications
Changed Bug title to 'ruby-curb: test regression with curl 8.7.1: client read 
function EOF fail, only only 4/5 of needed bytes read' from 'ruby-curb: FTBFS: 
178 tests, 699 assertions, 0 failures, 7 errors, 0 pendings, 0 omissions, 0 
notifications'.

-- 
1069258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Processed: closing 1069348

2024-04-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1069348 0.16.0-2
Bug #1069348 [src:ruby-ethon] ruby-ethon: FTBFS
Marked as fixed in versions ruby-ethon/0.16.0-2.
Bug #1069348 [src:ruby-ethon] ruby-ethon: FTBFS
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1069348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#974014: marked as done (Fails to install due to depending on ruby-rails < 6.0)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 +
with message-id 
and subject line Bug#1069615: Removed package(s) from unstable
has caused the Debian Bug report #974014,
regarding Fails to install due to depending on ruby-rails < 6.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
974014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora
Version: 0.7.9.0+dfsg-4
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While investigating the other RC issue I discovered that diaspora is
uninstallable in Sid:

The following packages have unmet dependencies:
 diaspora : Depends: ruby-rails (< 2:6.0) but 2:6.0.3.4+dfsg-1 is to be 
installed

Regards, Daniel


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
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 diaspora depends on:
ii  bc1.07.1-2+b2
hi  bundler   2.1.4-2
pn  diaspora-common   
pn  fonts-roboto-hinted   
ii  imagemagick   8:6.9.11.24+dfsg-1+b1
ii  imagemagick-6.q16 [imagemagick]   8:6.9.11.24+dfsg-1+b1
ii  libruby2.7 [ruby-json]2.7.2-3
ii  nodejs12.19.0~dfsg-1
ii  rake  13.0.1-4
ii  ruby  1:2.7+2
pn  ruby-active-model-serializers 
pn  ruby-activerecord-import  
pn  ruby-acts-as-api  
pn  ruby-acts-as-taggable-on  
ii  ruby-addressable  2.7.0-1
pn  ruby-asset-sync   
pn  ruby-autoprefixer-rails   
pn  ruby-backbone-on-rails
pn  ruby-bootstrap-sass   
pn  ruby-bootstrap-switch-rails   
pn  ruby-carrierwave  
pn  ruby-chunky-png   
pn  ruby-configurate  
pn  ruby-devise   
pn  ruby-devise-lastseenable  
pn  ruby-devise-two-factor
pn  ruby-diaspora-federation-json-schema  
pn  ruby-diaspora-federation-rails
pn  ruby-diaspora-prosody-config  
pn  ruby-entypo-rails 
pn  ruby-eye  
ii  ruby-faraday  0.17.3-1
pn  ruby-faraday-cookie-jar   
pn  ruby-faraday-middleware   
pn  ruby-fog-aws  
pn  ruby-gon  
pn  ruby-hamlit   
pn  ruby-handlebars-assets
pn  ruby-http-accept-language 
pn  ruby-i18n-inflector-rails 
pn  ruby-jquery-rails 
pn  ruby-jquery-ui-rails  
pn  ruby-js-image-paths   
pn  ruby-js-routes
ii  ruby-json 2.3.0+dfsg-1+b3
ii  ruby-json-schema  2.8.1-2
pn  ruby-leaflet-rails
pn  ruby-logging-rails
pn  ruby-markdown-it-html5-embed  
pn  ruby-markerb  
ii  ruby-mini-magick  4.10.1-1
pn  ruby-mobile-fu
ii  ruby-nokogiri 1.10.9+dfsg-1+b1
pn  ruby-

[DRE-maint] Bug#924109: marked as done (diaspora: fails to install noninteractively)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 +
with message-id 
and subject line Bug#1069615: Removed package(s) from unstable
has caused the Debian Bug report #924109,
regarding diaspora: fails to install noninteractively
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
924109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora
Version: 0.7.9.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up diaspora (0.7.9.0+dfsg-4) ...
  
  We trust you have received the usual lecture from the local System
  Administrator. It usually boils down to these three things:
  
  #1) Respect the privacy of others.
  #2) Think before you type.
  #3) With great power comes great responsibility.
  
  sudo: no tty present and no askpass program specified
  [ESC][31mBundler::SudoNotPermittedError: Bundler requires sudo access to 
install at the
  moment. Try installing again, granting Bundler sudo access when prompted, or
  installing into a different path.
  [ESC][0m[ESC][0m[ESC][31mAn error occurred while installing sass (3.4.25), 
and Bundler
  cannot continue.
  [ESC][0m
  
  In Gemfile:
bootstrap-sass was resolved to 3.3.5.1, which depends on
  sass[ESC][0m
  dpkg: error processing package diaspora (--configure):
   installed diaspora package post-installation script subprocess returned 
error exit status 1
  Processing triggers for libc-bin (2.28-8) ...
  Processing triggers for ca-certificates (20190110) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   diaspora


piuparts tests are run under DEBIAN_FRONTEND=noninteractive
in case this does matter ...


cheers,

Andreas


diaspora_0.7.9.0+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.7.9.0+dfsg-4+rm

Dear submitter,

as the package diaspora has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1069615

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#991245: marked as done (diaspora fails to handle triggers in postinst)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 +
with message-id 
and subject line Bug#1069615: Removed package(s) from unstable
has caused the Debian Bug report #991245,
regarding diaspora fails to handle triggers in postinst
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
991245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: diaspora
Version: 0.7.15.0-7
severity: grave

Processing triggers for diaspora (0.7.15.0-7~bpo11+1) ...
Updating bundler configuration for migration from diaspora-installer...
postinst called with unknown argument `triggered'
dpkg: error processing package diaspora (--configure):
installed diaspora package post-installation script subprocess 
returned error exit status 1

Processing triggers for libc-bin (2.31-12) ...
Errors were encountered while processing:
diaspora

postinst script should be adapted to handle this case like gitlab does 
in


https://salsa.debian.org/ruby-team/gitlab/-/blob/master/debian/gitlab.postinst#L342

and 
https://salsa.debian.org/ruby-team/gitlab/-/blob/master/debian/gitlab.postinst#L82
--- End Message ---
--- Begin Message ---
Version: 0.7.9.0+dfsg-4+rm

Dear submitter,

as the package diaspora has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1069615

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


[DRE-maint] Bug#788939: marked as done (ruby-sigar: Function sigar_proc_port_get sometimes does not find valid PID)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:26:18 +
with message-id 
and subject line Bug#1069619: Removed package(s) from unstable
has caused the Debian Bug report #788939,
regarding ruby-sigar: Function sigar_proc_port_get sometimes does not find 
valid PID
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
788939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-sigar
Version: 0.7.2-1
Severity: important
Tags: upstream patch

Dear Maintainer,
There is a problem with sigar_proc_port_get function. While looking for
the process that owns a socket, it assumes that the UID of the process
is the same as the UID of the port, which is not always true. I use Chef
to configure some servers, Chef calls Ohai, which uses the function to
generate the port-process map. When a process was started as root,
opened a socket and then dropped priviliges, the function returns 0,
which causes some problems with Ohai and Chef. I tried deleting the
lines related to skipping processes with different UID - after
installing the rebuilt package everything is working fine. I attach
the patch.

Best regards,
Piotr Panczyk

-- System Information:
Debian Release: 7.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.bsd54h0 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ruby-sigar depends on:
ii  libc6 2.13-38+deb7u8
ii  libruby1.9.1  1.9.3.194-8.1+deb7u5
ii  ruby  1:1.9.3
ii  ruby1.9.1 [ruby-interpreter]  1.9.3.194-8.1+deb7u5

ruby-sigar recommends no packages.

ruby-sigar suggests no packages.

-- no debconf information
--- ruby-sigar-0.7.2.orig/src/os/linux/linux_sigar.c
+++ ruby-sigar-0.7.2/src/os/linux/linux_sigar.c
@@ -2502,9 +2502,6 @@ int sigar_proc_port_get(sigar_t *sigar,
 if (stat(pid_name, ) < 0) {
 continue;
 }
-if (sb.st_uid != netconn.uid) {
-continue;
-}
 
 /* sprintf(fd_name, "%s/fd", pid_name) */
 memcpy(_name[0], pid_name, len);
--- End Message ---
--- Begin Message ---
Version: 0.7.3-3+rm

Dear submitter,

as the package ruby-sigar has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1069619

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers


  1   2   3   4   5   6   7   8   9   10   >