On Sat, Oct 07, 2023 at 07:56:23PM +0200, Norwid Behrnd wrote:
>
> Dear subscribers,
>
> I seek assistance to rename an application in Ruby, especially the sequence to
> file a RFS.
>
> Just prior to the freeze of Debian bookworm, I packaged `ruby-mdl` from
> rubygems with `gem2deb`. Though it was accepted, Daniel Leidert and one
> sponsor of the package recommended to to consider a different name of the
> package because it isn't a library, but an application; a task better
> postponed for the time after the release of `bookworm`.
>
> There are two questions building on top of each other:
>
> + Because a new version 0.13.0 was released on rubygems, I started to prepare a
> new package for Debian[1] and equally wish to improve this detail now. Based
> on repology.org,[2] plain `mdl` seems to be a name suitable. Reading about
> the documented «Transition package method»,[3] I would have to replace the
> currently used file `/debian/control` (copied below) by a new one (copied
> below) for one RFS, commit the changes to salsa, build, sign, dput as usual.
> Once this hurdle is taken, I would file a subsequent separate RFS for a dummy
> package. Any objections for this part?
You don't need this many steps. Just a new upload with a changed
debian/control, and the transitional package in the same source.
Something like this:
----------------8<----------------8<----------------8<-----------------
--- ruby-mdl-0.12.0.orig/debian/control 2023-10-10 09:05:30.164287531 -0300
+++ ruby-mdl-0.12.0/debian/control 2023-10-10 09:08:55.690078066 -0300
@@ -1,4 +1,4 @@
-Source: ruby-mdl
+Source: mdl
Section: text
Priority: optional
Maintainer: Norwid Behrnd <nbehrnd@yahoo.com>
@@ -20,13 +20,24 @@
Testsuite: autopkgtest-pkg-ruby
Rules-Requires-Root: no
-Package: ruby-mdl
+Package: mdl
Architecture: all
Depends: ${misc:Depends},
${ruby:Depends},
${shlibs:Depends}
Description: Markdown lint tool
- ruby-mdl checks an individual markdown file, or a directory of markdown
+ mdl checks an individual markdown file, or a directory of markdown
+ files against a set of 47 rules for syntax consistency. In its report back
+ to the CLI, the Ruby based implementation reports the line(s) with an issue
+ identified and how to improve it.
+
+Package: ruby-mdl
+Architecture: all
+Depends: mdl
+Description: Markdown lint tool - transitional package
+ mdl checks an individual markdown file, or a directory of markdown
files against a set of 47 rules for syntax consistency. In its report back
to the CLI, the Ruby based implementation reports the line(s) with an issue
identified and how to improve it.
+ .
+ This is a transitional package for mdl. It can be safely removed.
----------------8<----------------8<----------------8<-----------------
You will need to make a few other changes in your git repository, like
renaming files in the pristine-tar branch if you are using that, and
maybe renaming the repository as well.
Of course, given this this is a new source package, it will need to go
through NEW. After it's accepted the old source package will be removed
automatically because all of its binaries are not provided by a
different source.
> + Second, I found `equivs` described elsewhere[4] to prepare a dummy package
> and I am able to replicate their example with their control file (`equivs`
> version 2.3.1). However, a copy my dummy control file as a plain file in a
> separate empty folder only yields
>
> ```shell
> $ equivs-build ./control
> syntax error in control file: This is a transitional package. It can safely be
> removed. ```
>
> To me, `Depends: mdl, ${misc:Depends}` reads like I should thus i) await
> a successful RFS of `ruby-mdl` 0.13.0 as `mdl` to then ii) copy my control
> file as `/debian/control` into the folder which was used to prepare the
> package `mdl`. Really this simple (no commit to salsa.debian.org, but sign
> and dput to mentors.debian.net as usual)?
equivs is meant as a tool to trick dpkg locally, and it should not be
used to maintain actual packages in the Debian archive.
Attachment:
signature.asc
Description: PGP signature