Skip to content

Update ruby-amazing-print to 2.0.0#12007

Draft
github-actions[bot] wants to merge 1 commit intodeb/developfrom
bump_deb/ruby-amazing-print
Draft

Update ruby-amazing-print to 2.0.0#12007
github-actions[bot] wants to merge 1 commit intodeb/developfrom
bump_deb/ruby-amazing-print

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented May 11, 2025

No description provided.

@github-actions github-actions Bot requested a review from a team as a code owner May 11, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch from 53e141e to 155f116 Compare May 14, 2025 04:11
@ekohl
Copy link
Copy Markdown
Member

ekohl commented May 14, 2025

[2025-05-14T04:13:00.910Z] ERROR:  Error installing /tmp/d20250514-318289-j3a8fg/amazing_print-1.8.0.gem:
[2025-05-14T04:13:00.910Z] 	amazing_print-1.8.0 requires Ruby version >= 3.1.0. The current ruby version is 3.0.2.107.

@evgeni
Copy link
Copy Markdown
Member

evgeni commented May 14, 2025

Yeah, Debian bumping is less smart than RPM

@ekohl ekohl marked this pull request as draft May 14, 2025 11:29
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 2 times, most recently from e0797db to 0cd5532 Compare May 21, 2025 04:12
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch from 0cd5532 to da6a399 Compare May 25, 2025 04:14
@github-actions github-actions Bot changed the title Update ruby-amazing-print to 1.8.0 Update ruby-amazing-print to 1.8.1 May 25, 2025
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 4 times, most recently from 3df062e to 0eacb94 Compare June 8, 2025 04:17
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from cadad8e to ab7a6b2 Compare June 18, 2025 04:15
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 5 times, most recently from 908354a to d37f960 Compare June 26, 2025 15:06
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from 5fa0efe to af63f7f Compare July 6, 2025 04:18
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 2 times, most recently from 49c2af5 to 6167f1c Compare July 13, 2025 04:22
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 2 times, most recently from 3deec0d to 2b93e9b Compare July 16, 2025 07:35
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 8 times, most recently from 1a65e1f to ea93e8a Compare August 13, 2025 07:41
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from 7f6a054 to 051744c Compare August 24, 2025 04:14
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 4 times, most recently from 71b6fa8 to cab25ad Compare September 3, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 2 times, most recently from 8bacfa8 to 84eb79a Compare September 10, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from 1f1a7ef to 549a548 Compare September 17, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from 37bdcbd to f7665a2 Compare September 24, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch 3 times, most recently from 630cd6c to 0140b3d Compare October 5, 2025 04:11
@github-actions github-actions Bot force-pushed the bump_deb/ruby-amazing-print branch from 0140b3d to 37baf88 Compare October 8, 2025 04:11
@github-actions github-actions Bot changed the title Update ruby-amazing-print to 1.8.1 Update ruby-amazing-print to 2.0.0 Oct 8, 2025
@ogajduse
Copy link
Copy Markdown
Member

Yeah, Debian bumping is less smart than RPM

Does that mean we should update only Bookworm and not update Jammy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants