This bug was fixed in the package ruby-safely-block - 0.4.1-1
Sponsored for Pushkar Kulkarni (pushkarnk)
---------------
ruby-safely-block (0.4.1-1) unstable; urgency=medium
* Team upload.
[ Debian Janitor ]
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete field Contact from debian/upstream/metadata (already present
in machine-readable debian/copyright).
* Update standards version to 4.5.0, no changes needed.
* Update watch file format version to 4.
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
[ Lucas Kanashiro ]
* New upstream version 0.4.1
* Refresh patches
* Declare compliance with Debian Policy 4.7.0
* Runtime depend on ${ruby:Depends} instead of ruby interpreter
-- Lucas Kanashiro <kanash...@debian.org> Tue, 17 Dec 2024 12:07:08
-0300
** Changed in: ruby-safely-block (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098672
Title:
Sync ruby-safely-block 0.4.1-1 (universe) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-safely-block/+bug/2098672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
