Bug#1144561: ITP: ruby-uri -- This module provides classes to handle Uniform Resource Identifiers.

Norwid Behrnd <[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <178689853192.49287.14951599429262103698.reportbug__11911.3895970926$1786898737$gmane$org@debian>
Package: wnpp
Severity: wishlist
Owner: Norwid Behrnd <[email protected]>
X-Debbugs-Cc: [email protected], [email protected]

* Package name    : ruby-uri
  Version         : 1.1.1
  Upstream Contact: to be determined / pending[1]
* URL             : https://github.com/ruby/uri
* License         : Ruby or BSD-2-Clause
  Programming Lang: Ruby
  Description     : This module provides classes to handle Uniform Resource
Identifiers.

 Features include:

  * Uniform way of handling URIs.
  * Flexibility to introduce custom URI schemes.
  * Flexibility to have an alternate URI::Parser (or just different
    patterns and regexp's).

Separate from this, the upstream reference of already admitted `ruby-mdl`
published new versions, and starting with version 0.18.0 an additional
dependency is `uri`.[2]  However (Ruby 3.3.8 from servers of Debian forky)

```bash
$ ruby -e "require 'uri'; puts URI::VERSION"
0.13.2
```

published by February 26, 2025 appears to be behind the current version
1.1.1 (November 04, 2025), which might contribute to an issue previously
reported upstream.[3]  The later update of `ruby-mdl` is the motivation.

According to the Debian package tracker, there is no `ruby-uri` yet.

Eventually, I am going to need a sponsor for an upload to Debian.  I would
feel more comfortable if there were a co-maintainer in addition to the
usual review process.

[1] https://github.com/ruby/uri/issues/243 -- is the addition of Hiroshi
    SHIBATA, maintainer of the .gem on rubygems.org, an option here?
[2] https://rubygems.org/gems/mdl/versions/0.18.1/dependencies
[3] https://github.com/markdownlint/markdownlint/issues/605
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.