Bug#1067043: libruby: needs updating for libruby3.1t64

[Chris Hofstaedtler]

Control: tags -1 + pending

* Simon McVittie  [240317 15:57]:
> Package: libruby
> Version: 1:3.1
[..]

> Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
> the architectures affected by the 64-bit time_t transition, 
[..]

> I suspect the only change needed here is to update the libruby metapackage
> so that it depends on libruby3.1t64 instead of libruby3.1. Please could
> someone who knows Ruby check this?

Indeed. I've uploaded ruby-defaults 1:3.1+nmu1 and pushed to salsa.

Chris

PS: @ruby-team: if you disagree / want to take over, please let me know.

Processed: Re: Bug#1067043: libruby: needs updating for libruby3.1t64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1067043 [libruby] libruby: needs updating for libruby3.1t64
Ignoring request to alter tags of bug #1067043 to the same tags previously set

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

Bug#1067043: libruby: needs updating for libruby3.1t64

[Simon McVittie]

Package: libruby
Version: 1:3.1
Severity: serious
Justification: blocker for 64-bit time_t transition
X-Debbugs-Cc: z...@debian.org, debian-...@lists.debian.org
Control: affects -1 + src:graphviz src:vala

Now that libruby3.1t64 has reached unstable, libruby is uninstallable on
the architectures affected by the 64-bit time_t transition, blocking the
rebuild of packages such as graphviz and vala via this dependency chain:

... -> vala -> graphviz -> ruby -> libruby -> libruby3.1

The impact of this is visible in for example
.

I suspect the only change needed here is to update the libruby metapackage
so that it depends on libruby3.1t64 instead of libruby3.1. Please could
someone who knows Ruby check this?

Thanks,
smcv