[DRE-maint] Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='

Andreas Beckmann anbe at debian.org
Sat Jun 24 21:38:38 BST 2023


Control: reassign -1 ruby-activerecord 2:6.1.7.3+dfsg-1
Control: retitle -1 ruby-activerecord: missing Conflicts: ruby-arel
Control: affects -1 + src:schleuder
Control: clone -1 -2 -3
Control: reassign -2 ruby-arel 9.0.0-2
Control: tag -2 sid trixie
Control: retitle -2 ruby-arel: obsolete, integrated into ruby-activerecord, incompatible with ruby-activerecord 6.1.x
Control: reassign -3 src:ruby-premailer-rails 1.10.3-3
Control: tag -3 sid trixie bookworm
Control: retitle -3 ruby-premailer-rails: B-D on obsolete ruby-arel, incompatible with ruby-activerecord 6.1.x

On 24/06/2023 15.07, Georg Faerber wrote:
> So, given the above, I believe this bug should be reassigned to
> ruby-activerecord, and schleuder should be marked as affected? Also, I

Doing that, and cloning it for ruby-arel and ruby-premailer-rails.

> guess, as this issue is not specific to schleuder, probably more
> packages which rely on ruby-activerecord are affected.

But schleuder seems to be the only one using it "sufficiently" to expose
the bug already in the maintainer scripts.

> I'll prepare a ruby-activerecord proposed-update targeting bookworm.

This needs to be fixed in sid first.

Adding the Conflicts against ruby-arel in ruby-activerecord requires
changes in src:ruby-premailer-rails, too, since that (directly)
build-depends on ruby-arel and indirectly on ruby-activerecord.
Maybe dropping the B-D: ruby-arel is already sufficient.
These changes need to be backported to bookworm-pu as well.
If that is fixed, ruby-arel can be removed from sid (and it could be
considered to remove it from bookworm as well).


Andreas



More information about the Pkg-ruby-extras-maintainers mailing list