[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1104286: marked as done (unblock: ruby-serialport/1.3.2-2)

Your message dated Wed, 30 Apr 2025 06:15:42 +0000
with message-id <E1uA0jO-001zwt-2u@respighi.debian.org>
and subject line unblock ruby-serialport
has caused the Debian Bug report #1104286,
regarding unblock: ruby-serialport/1.3.2-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1104286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104286
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ruby-serialport@packages.debian.org
Control: affects -1 + src:ruby-serialport

Please unblock package ruby-serialport.

This package was removed from testing a while back. However I fixed it
in unstable, and I think that it should be re-accepted into testing
(despite the release policy to not accept re-entry in that case):
* it's the only ruby library to interact with a serial port, so there's
  no alternative. I actually ran into the fact that it was missing in
  testing while upgrading a personal machine I use for home automation.
  I believe trixie is strictly better with it included.
* it was previously in Debian 10, 11, 12.
* I added an autopkgtest smoke test to detect potential problems earlier.
* It has no reverse dependency, so it's low-risk.

Debdiff against the version in stable attached.

unblock ruby-serialport/1.3.2-2

--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: