Remove ruby-gitlab-labkit from the archive

Bug #1960803 reported by Simon Chopin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ruby-gitlab-labkit (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,

The package ruby-gitlab-labkit should be removed from Jammy. It is

* out of date with upstream (0.11 was released on March 2020, upstream is at 0.22 released in January 2022),
* is RC-buggy in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995359
* its autopkgtests are either not run (release pocket) or fail (-proposed, where the ruby 3.0 is still ongoing).

Notably, it would need porting to the newer Rails 6.1, which can be non-trivial.
The package currently prevents src:grpc and src:rails from migrating.

The package has no reverse dependencies in the archive:

❯ reverse-depends -a source src:ruby-gitlab-labkit
No reverse dependencies found

❯ reverse-depends src:ruby-gitlab-labkit
No reverse dependencies found

Revision history for this message
Steve Langasek (vorlon) wrote :

Removing packages from jammy:
 ruby-gitlab-labkit 0.12.2-1 in jammy
  ruby-gitlab-labkit 0.12.2-1 in jammy amd64
  ruby-gitlab-labkit 0.12.2-1 in jammy arm64
  ruby-gitlab-labkit 0.12.2-1 in jammy armhf
  ruby-gitlab-labkit 0.12.2-1 in jammy i386
  ruby-gitlab-labkit 0.12.2-1 in jammy ppc64el
  ruby-gitlab-labkit 0.12.2-1 in jammy riscv64
  ruby-gitlab-labkit 0.12.2-1 in jammy s390x
Comment: Failing tests, removed from Debian testing, blocks ruby transition; Debian bug #995359, LP: #1960803
1 package successfully removed.

Changed in ruby-gitlab-labkit (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.