Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp

2022-12-30 Thread Antonio Terceiro
Control: tag -1 + pending

On Fri, Dec 30, 2022 at 08:08:50PM -0300, Antonio Terceiro wrote:
> Control: reassign -1 dhelp
> Control: severity -1 serious
> Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm)
> 
> On Fri, Dec 30, 2022 at 06:09:03PM +0100, Drew Parsons wrote:
> > Package: ruby-rubygems
> > Version: 3.3.15-1
> > Severity: important
> > 
> > /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb from
> > ruby-rubygems causes a LoadError which prevents dhelp from updating
> > succcessfully (when packages register a doc-base entry).
> > 
> > This affects all other packages (unrelated to ruby) registering with
> > doc-base, hence marking Severity: important
> > 
> > The error message (when installing any packing using doc-base, in this
> > case python-lmfit-doc) is
> > 
> > Setting up python-lmfit-doc (1.1.0-1) ...
> > Processing triggers for doc-base (0.11.1) ...
> > Processing 1 added doc-base file...
> > Registering documents with dhelp...
> > :85:in
> >  `require': cannot load such file -- dbm (LoadError)
> > from 
> > :85:in
> >  `require'
> > from /usr/lib/ruby/vendor_ruby/dhelp.rb:21:in `'
> > from 
> > :85:in
> >  `require'
> > from 
> > :85:in
> >  `require'
> > from /usr/sbin/dhelp_parse:32:in `'
> 
> The issue is that dhelp depends on a module that has been removed from
> the Ruby standard library (dbm). I imagine the dhelp database is just a
> cache and can be rebuilt from scratch on upgrades, so one way to fix
> this would be to migrate to a similar module that is available and
> probably has a similar enough API, like sdbm (ruby-sdbm).

Actually this would invalidate existing databases, creating extra
complications. I have just uploaded a ruby-dbm package to NEW, and made
the necessary adjustments to the dhelp git repository to use it. I will
make an upload when the new package is accepted.


signature.asc
Description: PGP signature


Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp

2022-12-30 Thread Antonio Terceiro
Control: reassign -1 dhelp
Control: severity -1 serious
Control: retitle: dhelp: depends on module removed from the Ruby stdlib (dbm)

On Fri, Dec 30, 2022 at 06:09:03PM +0100, Drew Parsons wrote:
> Package: ruby-rubygems
> Version: 3.3.15-1
> Severity: important
> 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb from
> ruby-rubygems causes a LoadError which prevents dhelp from updating
> succcessfully (when packages register a doc-base entry).
> 
> This affects all other packages (unrelated to ruby) registering with
> doc-base, hence marking Severity: important
> 
> The error message (when installing any packing using doc-base, in this
> case python-lmfit-doc) is
> 
> Setting up python-lmfit-doc (1.1.0-1) ...
> Processing triggers for doc-base (0.11.1) ...
> Processing 1 added doc-base file...
> Registering documents with dhelp...
> :85:in
>  `require': cannot load such file -- dbm (LoadError)
>   from 
> :85:in
>  `require'
>   from /usr/lib/ruby/vendor_ruby/dhelp.rb:21:in `'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from /usr/sbin/dhelp_parse:32:in `'

The issue is that dhelp depends on a module that has been removed from
the Ruby standard library (dbm). I imagine the dhelp database is just a
cache and can be rebuilt from scratch on upgrades, so one way to fix
this would be to migrate to a similar module that is available and
probably has a similar enough API, like sdbm (ruby-sdbm).


signature.asc
Description: PGP signature


Bug#1027407: ruby-rubygems: kernel_require.rb LoadError breaks dhelp

2022-12-30 Thread Drew Parsons
Package: ruby-rubygems
Version: 3.3.15-1
Severity: important

/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb from
ruby-rubygems causes a LoadError which prevents dhelp from updating
succcessfully (when packages register a doc-base entry).

This affects all other packages (unrelated to ruby) registering with
doc-base, hence marking Severity: important

The error message (when installing any packing using doc-base, in this
case python-lmfit-doc) is

Setting up python-lmfit-doc (1.1.0-1) ...
Processing triggers for doc-base (0.11.1) ...
Processing 1 added doc-base file...
Registering documents with dhelp...
:85:in 
`require': cannot load such file -- dbm (LoadError)
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/dhelp.rb:21:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/sbin/dhelp_parse:32:in `'


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ruby-rubygems depends on:
ii  ruby  1:3.1

ruby-rubygems recommends no packages.

ruby-rubygems suggests no packages.

-- no debconf information