Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #388273 > unrolled thread

Bug#1101902: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?

Started byAndreas Tille <tille@debian.org>
First post2025-04-02 07:40 +0200
Last post2025-04-16 22:00 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#1101902: ruby-cleanroom: Should ruby-cleanroom be removed from unstable? Andreas Tille <tille@debian.org> - 2025-04-02 07:40 +0200
    Processed: Re: ruby-cleanroom: Should ruby-cleanroom be removed  from unstable? "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-04-16 22:00 +0200

#388273 — Bug#1101902: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?

FromAndreas Tille <tille@debian.org>
Date2025-04-02 07:40 +0200
SubjectBug#1101902: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?
Message-ID<KwYZr-aqGe-1@gated-at.bofh.it>
Source: ruby-cleanroom
Version: 1.0.0-1.1
Severity: serious
Justification: grab attention of maintainer
X-Debbugs-Cc: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>, Hleb Valoshka <375gnu@gmail.com>, debian-ruby@lists.debian.org, 1092691@bugs.debian.org, Package Salvaging Team <team+salvage@tracker.debian.org>

Dear maintainer,

I suggest removing ruby-cleanroom from Debian for the following reasons:

BEGIN FIXME
 * It accumulated one RC-bug:
   + #1092691: ruby-cleanroom: FTBFS: with ruby3.3: ERROR: Test "ruby3.3" failed: Failure/Error:
 * It is not part of bookworm or trixie and is not a key package.
 * There are no votes in popcon
   https://qa.debian.org/popcon-graph.php?packages=ruby-cleanroom&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
 * There seems to be no active maintainer

This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.

In case the package should be kept in unstable, please evaluate the
RC-bugs listed above.
 * If the bug no longer applies, please close it. If it is closed, check
   whether the fixed version is correct and adjust if necessary.

 * Is the bug really release-critical? If not, please downgrade.

 * If the bug still applies, please send a status update at least once a year.

Once the mentioned RC bugs has been acted upon in one way or another,
please close this bug.

In case the package should be removed from unstable, you may reassign this
bug report:

    Control: severity -1 normal
    Control: retitle -1 RM: ruby-cleanroom -- RoM; rc-buggy
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:ruby-cleanroom

Alternatively, you may wait a month and have it reassigned.

In case you disagree with the above, please add a wontfix tag to this bug.

    Control: tags -1 + wontfix

Doing so will also prevent automatic reassignment.

Your package was highlighted in the Bug of the Day[1] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to familiarize newcomers with a
consistent Git-based workflow.


Kind regards
    Andreas.


[1] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.19-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]


#389963 — Processed: Re: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-04-16 22:00 +0200
SubjectProcessed: Re: ruby-cleanroom: Should ruby-cleanroom be removed from unstable?
Message-ID<KCh5n-e0FS-7@gated-at.bofh.it>
In reply to#388273
Processing control commands:

> severity -1 normal
Bug #1101902 [src:ruby-cleanroom] ruby-cleanroom: Should ruby-cleanroom be removed from unstable?
Severity set to 'normal' from 'serious'
> retitle -1 RM: ruby-cleanroom -- RoM; rc-buggy
Bug #1101902 [src:ruby-cleanroom] ruby-cleanroom: Should ruby-cleanroom be removed from unstable?
Changed Bug title to 'RM: ruby-cleanroom -- RoM; rc-buggy' from 'ruby-cleanroom: Should ruby-cleanroom be removed from unstable?'.
> reassign -1 ftp.debian.org
Bug #1101902 [src:ruby-cleanroom] RM: ruby-cleanroom -- RoM; rc-buggy
Bug reassigned from package 'src:ruby-cleanroom' to 'ftp.debian.org'.
No longer marked as found in versions ruby-cleanroom/1.0.0-1.1.
Ignoring request to alter fixed versions of bug #1101902 to the same values previously set
> affects -1 + src:ruby-cleanroom
Bug #1101902 [ftp.debian.org] RM: ruby-cleanroom -- RoM; rc-buggy
Added indication that 1101902 affects src:ruby-cleanroom

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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web