Bug#1090913: transition: ruby3.3

[Lucas Kanashiro]

I am moving the content of the removal bug to here, as requested by
pochu on IRC. I will be closing the removal bug linked in the message
above.

In order to help the transition, I'd like to request the removal of
the following source, and associated binary, packages from testing
to unblock the ruby 3.3 transition:

* ruby-nokogumbo
* ruby-gitlab-flowdock-git-hook
* ruby-dataobjects
   - ruby-dataobjects-mysql (please, remove it as well, no rdep)
   - ruby-dataobjects-postgres (please, remove it as well, no rdep)
   - ruby-dataobjects-sqlite3 (please, remove it as well, no rdep)
* ruby-grib
* ruby-rails-assets-markdown-it-diaspora-mention
* ruby-roo
* ruby-rgfa
* ruby-puppetlabs-spec-helper
* ruby-puppet-syntax
   - ruby-puppetlabs-spec-helper (which is also in this removals list)
* ruby-puma-worker-killer
   - gitlab (which is not in testing)
* ruby-mail-room
   - gitlab (which is not in testing)
* ruby-hipchat
* ruby-googleapis-common-protos
* ruby-gelf
* ruby-file-validators
* ruby-cleanroom
* ruby-batch-loader
   - gitlab (which is not in testing)
* ruby-api-pagination
* redland-bindings (orphan package)
* ruby-rails-assets-underscore
   - ruby-backbone-on-rails (please, remove it as well, no rdep)

The sub-items above are reverse dependencies, but there is an
explanation in front of each of them, telling why they can be safely
removed.

If you have any question, do not hesitate to reach out to me!

TIA!

[Lucas Kanashiro]

We filed bugs for the packages that are failing to build with ruby 3.3
and are not in the removal request list above:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-***@lists.debian.org&tag=ruby3.3

[Lucas Kanashiro]

Hi Emilio,

Post by Lucas Kanashiro
We filed bugs for the packages that are failing to build with ruby
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-

What's the plan for those? I.e. what would happen if we started this
transition now? Would those block it? I don't see any activity in them
(haven't checked them all). Looks like most of them are not key
packages, but these two are, so they should be addressed or there
should be a plan for them before we go ahead.
  ruby-amq-protocol
  ruby-excon

I just addressed those 2 bugs, they should be closed at this point. For
ruby-excon, it was a problem in the rebuild we did, I closed the bug and
added an explanation and a link to the successful build log. For
ruby-amq-protocol, it was a problem in the upstream code, I patched it
and uploaded version 2.3.2-2 fixing it.

I hope this helps with the beginning of the ruby 3.3 transition.

Cheers!

[Lucas Kanashiro]

On Fri, 10 Jan 2025 11:08:07 +0100 Emilio Pozuelo Monfort

Control: tags -1 confirmed

Post by Lucas Kanashiro
Hi Emilio,

Post by Lucas Kanashiro
We filed bugs for the packages that are failing to build with

ruby 3.3 and

Post by Lucas Kanashiro

Post by Lucas Kanashiro
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-

What's the plan for those? I.e. what would happen if we started this
transition now? Would those block it? I don't see any activity in them
(haven't checked them all). Looks like most of them are not key

packages, but

Post by Lucas Kanashiro

these two are, so they should be addressed or there should be a

plan for them

Post by Lucas Kanashiro

before we go ahead.
  ruby-amq-protocol
  ruby-excon

I just addressed those 2 bugs, they should be closed at this point.

For ruby-

Post by Lucas Kanashiro
excon, it was a problem in the rebuild we did, I closed the bug and

added an

Post by Lucas Kanashiro
explanation and a link to the successful build log. For

ruby-amq-protocol, it

Post by Lucas Kanashiro
was a problem in the upstream code, I patched it and uploaded

version 2.3.2-2

Post by Lucas Kanashiro
fixing it.
I hope this helps with the beginning of the ruby 3.3 transition.

Ack. Go ahead with the transition.

Thanks! I just uploaded ruby-defaults/3.1+support3.3 to unstable, it
should be available in the archive soon.

Cheers!

[Lucas Kanashiro]

Hi Emilio,

Hi Lucas,

Post by Lucas Kanashiro
I am moving the content of the removal bug to here, as requested by
pochu on IRC. I will be closing the removal bug linked in the message
above.
In order to help the transition, I'd like to request the removal of
the following source, and associated binary, packages from testing
* ruby-nokogumbo
* ruby-gitlab-flowdock-git-hook
* ruby-dataobjects
    - ruby-dataobjects-mysql (please, remove it as well, no rdep)
    - ruby-dataobjects-postgres (please, remove it as well, no rdep)
    - ruby-dataobjects-sqlite3 (please, remove it as well, no rdep)
* ruby-grib
* ruby-rails-assets-markdown-it-diaspora-mention
* ruby-roo
* ruby-rgfa
* ruby-puppetlabs-spec-helper
* ruby-puppet-syntax
    - ruby-puppetlabs-spec-helper (which is also in this removals list)
* ruby-puma-worker-killer
    - gitlab (which is not in testing)
* ruby-mail-room
    - gitlab (which is not in testing)
* ruby-hipchat
* ruby-googleapis-common-protos
* ruby-gelf
* ruby-file-validators
* ruby-cleanroom
* ruby-batch-loader
    - gitlab (which is not in testing)
* ruby-api-pagination
* redland-bindings (orphan package)
* ruby-rails-assets-underscore
    - ruby-backbone-on-rails (please, remove it as well, no rdep)
The sub-items above are reverse dependencies, but there is an
explanation in front of each of them, telling why they can be safely
removed.
If you have any question, do not hesitate to reach out to me!

What prevents those packages from re-entering testing if we remove
them now? E.g. ruby-hipchat has no RC bug reported against it.

Right now nothing TBH, I was considering those removals to allow
ruby-defaults, with ruby3.3 support, migration, so once it is migrated
to testing those packages wouldn't migrate since they do not work with
ruby 3.3 at the moment. If you prefer to remove them before starting the
transition, I can file RC bugs to block migration. Let me know what you
prefer.

[Lucas Kanashiro]

Post by Lucas Kanashiro
Hi Emilio,

Hi Lucas,

Post by Lucas Kanashiro
I am moving the content of the removal bug to here, as requested by
pochu on IRC. I will be closing the removal bug linked in the message
above.
In order to help the transition, I'd like to request the removal of
the following source, and associated binary, packages from testing
* ruby-nokogumbo
* ruby-gitlab-flowdock-git-hook
* ruby-dataobjects
    - ruby-dataobjects-mysql (please, remove it as well, no rdep)
    - ruby-dataobjects-postgres (please, remove it as well, no rdep)
    - ruby-dataobjects-sqlite3 (please, remove it as well, no rdep)
* ruby-grib
* ruby-rails-assets-markdown-it-diaspora-mention
* ruby-roo
* ruby-rgfa
* ruby-puppetlabs-spec-helper
* ruby-puppet-syntax
    - ruby-puppetlabs-spec-helper (which is also in this removals
list)
* ruby-puma-worker-killer
    - gitlab (which is not in testing)
* ruby-mail-room
    - gitlab (which is not in testing)
* ruby-hipchat
* ruby-googleapis-common-protos
* ruby-gelf
* ruby-file-validators
* ruby-cleanroom
* ruby-batch-loader
    - gitlab (which is not in testing)
* ruby-api-pagination
* redland-bindings (orphan package)
* ruby-rails-assets-underscore
    - ruby-backbone-on-rails (please, remove it as well, no rdep)
The sub-items above are reverse dependencies, but there is an
explanation in front of each of them, telling why they can be safely
removed.
If you have any question, do not hesitate to reach out to me!

What prevents those packages from re-entering testing if we remove
them now? E.g. ruby-hipchat has no RC bug reported against it.

Right now nothing TBH, I was considering those removals to allow
ruby-defaults, with ruby3.3 support, migration, so once it is
migrated to testing those packages wouldn't migrate since they do not
work with ruby 3.3 at the moment. If you prefer to remove them before
starting the transition, I can file RC bugs to block migration. Let
me know what you prefer.

IIUC, they are buggy anyway, right? So yes, then file bugs for them.
That should make things easier for us as well.

OK. We are going to file bugs against them. Just to be sure, since we
had this build issue with ruby-excon, I rebuilt all the packages I
requested removal from testing and some of them actually successfully
built (maybe a build issue or someone fixed it in the meantime). So this
is the updated list:

* ruby-nokogumbo
* ruby-gitlab-flowdock-git-hook
* ruby-dataobjects
   - ruby-dataobjects-mysql (please, remove it as well, no rdep)
    - ruby-dataobjects-postgres (please, remove it as well, no rdep)
    - ruby-dataobjects-sqlite3 (please, remove it as well, no rdep)
* ruby-grib
* ruby-rails-assets-markdown-it-diaspora-mention
* ruby-roo
* ruby-rgfa
* ruby-puppetlabs-spec-helper
* ruby-puppet-syntax
    - ruby-puppetlabs-spec-helper (which is also in this removals list)
* ruby-cleanroom
* ruby-api-pagination
* ruby-rails-assets-underscore
    - ruby-backbone-on-rails (please, remove it as well, no rdep)

All the build logs are accessible here:

https://ruby-builds.debian.net/ruby3.3

The bugs are going to be filled against the packages above. We are also
going to increase the severity of the bugs we filed before since the
transition is going to start.

[Debian Bug Tracking System]

tags -1 confirmed

Bug #1090913 [release.debian.org] transition: ruby3.3
Added tag(s) confirmed.

[Antonio Terceiro]

Post by Lucas Kanashiro
I am moving the content of the removal bug to here, as requested by
pochu on IRC. I will be closing the removal bug linked in the message
above.
In order to help the transition, I'd like to request the removal of
the following source, and associated binary, packages from testing
* ruby-nokogumbo
* ruby-gitlab-flowdock-git-hook
* ruby-dataobjects
   - ruby-dataobjects-mysql (please, remove it as well, no rdep)
   - ruby-dataobjects-postgres (please, remove it as well, no rdep)
   - ruby-dataobjects-sqlite3 (please, remove it as well, no rdep)
* ruby-grib
* ruby-rails-assets-markdown-it-diaspora-mention
* ruby-roo
* ruby-rgfa
* ruby-puppetlabs-spec-helper
* ruby-puppet-syntax
   - ruby-puppetlabs-spec-helper (which is also in this removals list)
* ruby-puma-worker-killer
   - gitlab (which is not in testing)
* ruby-mail-room
   - gitlab (which is not in testing)
* ruby-hipchat
* ruby-googleapis-common-protos
* ruby-gelf
* ruby-file-validators
* ruby-cleanroom
* ruby-batch-loader
   - gitlab (which is not in testing)
* ruby-api-pagination
* redland-bindings (orphan package)
* ruby-rails-assets-underscore
   - ruby-backbone-on-rails (please, remove it as well, no rdep)
The sub-items above are reverse dependencies, but there is an
explanation in front of each of them, telling why they can be safely
removed.

Can you please remove the packages above from testing? 2 of them are
currently listed as bad in the transition tracker, and the others FTBFS
but do not show up in the tracker because they do not have C extensions.

Also please remove vagrant as well (#1092987).

[Antonio Terceiro]

Post by Lucas Kanashiro
* redland-bindings (orphan package)

Why does this need to be removed? It doesn't have an RC bug, and seems to
only build against the default ruby, so it doesn't seem buggy in terms of
this transition.

True. I think this was included in the list by mistake. I even tried a
rebuild with src:ruby-defaults from experimental (making 3.3 the
default and dropping 3.1) and it built just fine.

[Lucas Kanashiro]

Post by Antonio Terceiro

Post by Lucas Kanashiro
* redland-bindings (orphan package)

Why does this need to be removed? It doesn't have an RC bug, and seems to
only build against the default ruby, so it doesn't seem buggy in terms of
this transition.

True. I think this was included in the list by mistake. I even tried a
rebuild with src:ruby-defaults from experimental (making 3.3 the
default and dropping 3.1) and it built just fine.

If you follow the thread you will see that I sent an updated list which does not contain this package (and some others).

Lucas Kanashiro

[Debian Bug Tracking System]

retitle -1 transition: ruby3.3-add

Bug #1090913 [release.debian.org] transition: ruby3.3
Changed Bug title to 'transition: ruby3.3-add' from 'transition: ruby3.3'.