GitLab

follow-up #13101

We need ruby-rexml < ruby-power_assert to be built and available in
the repository. The problem is with the version change - going from
higher version to lower.

We need ruby-power_assert to be built and available in the repository.
The problem is with the version change - going from higher version to
lower.

We need ruby-power_assert to be built and available in the repository.
The problem is with the version change - going from higher version to
lower.

Without this, soju fails to start when built with abuild:

    daemon.info supervise-daemon[5733]: Supervisor command line: supervise-daemon soju --start --chdir /var/lib/soju --stderr /var/log/soju.log --user soju:soju /usr/bin/soju -- -config /etc/soju/config
    daemon.err /etc/init.d/soju[5736]: supervise-daemon: chdir `/var/lib/soju': No such file or directory

I'm moving "Bundled gems" (https://stdgems.org/3.0.2/#bundled-gems) to
separate aports mainly to provide correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

This gem is on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

This gem is on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

This gem was bundled in main/ruby and it's on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

When the gem was bundled its pkgver was set to that of the ruby package,
now its pkgver is set to its upstream version which is lower so users
upgrading need to pass `--available` to the `apk upgrade` command.

This is a "bundled gem" in Ruby 3.0.

See https://stdgems.org/#bundled-gems-ruby-302

This gem was bundled in main/ruby and it's on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

This gem was bundled in main/ruby and it's on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

When the gem was bundled its pkgver was set to that of the ruby package,
now its pkgver is set to its upstream version which is lower so users
upgrading need to pass `--available` to the `apk upgrade` command.

This gem was bundled in main/ruby and it's on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

When the gem was bundled its pkgver was set to that of the ruby package,
now its pkgver is set to its upstream version which is lower so users
upgrading need to pass `--available` to the `apk upgrade` command.

This gem was bundled in main/ruby and it's on the list of the "Bundled gems"
(https://stdgems.org/#bundled-gems-ruby-302) for Ruby 3.0.2. I'm moving it
to a separate aport to provide a correct pkgver - to avoid confusion and
future complications if the upstream decide to remove it from the
"Bundled gems" (as they did for some other gems with 3.0.0 release).

When the gem was bundled its pkgver was set to that of the ruby package,
now its pkgver is set to its upstream version which is lower so users
upgrading need to pass `--available` to the `apk upgrade` command.

This gem is unbundled by upstream Ruby from 3.0.0.

When the gem was bundled its pkgver was set to that of the ruby-lang
package, now its pkgver is set to its upstream version which is lower so
users upgrading need to pass `--available` to the `apk upgrade` command.

I could find no aport that depend on this gem.
Co-Authored-By: omni <omni+alpine@hack.org>

This gem is unbundled by upstream Ruby from 3.0.0.

When the gem was bundled its pkgver was set to that of the ruby-lang
package, now its pkgver is set to its upstream version which is lower so
users upgrading need to pass `--available` to the `apk upgrade` command.
Co-Authored-By: omni <omni+alpine@hack.org>

This gem is unbundled by upstream Ruby from 3.0.0.

When the gem was bundled its pkgver was set to that of the ruby-lang
package, now its pkgver is set to its upstream version which is lower so
users upgrading need to pass `--available` to the `apk upgrade` command.

I could find no aport that depend on this gem.
Co-Authored-By: omni <omni+alpine@hack.org>

This gem is unbundled by upstream Ruby from 3.0.0.

When the gem was bundled its pkgver was set to that of the ruby-lang
package, now its pkgver is set to its upstream version which is lower so
users upgrading need to pass `--available` to the `apk upgrade` command.

I could find no aport that depend on this gem.
Co-Authored-By: omni <omni+alpine@hack.org>

See https://stdgems.org/3.0.2/#default-gems

rdoc is big (2.2 MiB) and used only for development/build.

It's not needed anymore.

Resolves #10808

To fix build of community/xapian-bindings.

I already maintain most of the ruby aports and ncopa doesn't
actively maintain this aport, so it's logical to claim the
maintainership.

net-telnet, sdbm, webrick and xmlrpc have been excluded from the stdlib
in Ruby 3.0.

See https://rubyreferences.github.io/rubychanges/3.0.html#libraries-excluded-from-the-standard-library