Sign me up Login

Details about package formiko

Name: formiko (PTS)
Uploader: Ondřej Tůma <mcbig@zeropage.cz> (Debian QA page)
Description: formiko - reStructuredText and MarkDown editor and live previewer
formiko-vim - reStructuredText and MarkDown editor and live previewer - Vim mode

Package uploads

Upload #2

Information

Version: 2.0.0-2
Uploaded: 2026-09-14 14:52
Source package: formiko_2.0.0-2.dsc
Distribution: unstable
Section: editors
Priority: optional
Homepage: https://github.com/ondratu/formiko
Vcs-Git: https://github.com/ondratu/formiko-debian.git
Vcs-Browser: https://github.com/ondratu/formiko-debian
Closes bugs: #1145686

Changelog

 formiko (2.0.0-2) unstable; urgency=medium
 .
   * debian/patches: add pynvim-optional-import.patch, fixing a startup
     crash of formiko (without formiko-vim) when python3-pynvim is not
     installed but gir1.2-vte-3.91 is (Recommends installs it by
     default); backported from upstream commit
     7ac2d9dc203ad60f796cb9c97efec6da51bee37b
   * debian/control: split formiko-vim into its own binary package
     (Closes: #1145686)
     - New formiko-vim package ships the formiko-vim binary, its
       .desktop file and man page, with an explicit Depends on
       formiko (= ${binary:Version}) and python3-pynvim: pynvim was
       previously only a Suggests on formiko, so the Vim mode silently
       failed to work without it
     - formiko no longer ships the formiko-vim binary, .desktop file
       or man page
     - Move python3-m2r2 and python3-pygments from Suggests to
       Recommends for formiko: they are small and worth having
       installed by default
     - Drop Suggests entirely (python3-pynvim is now a hard Depends
       of formiko-vim instead)
     - Add Breaks/Replaces (<< 2.0.0-2~) on formiko-vim for the files
       moved out of formiko
     - Drop dh-sequence-single-binary from Build-Depends, required
       now that the source builds two binary packages
   * debian/rules: add formiko.install/formiko-vim.install to split
     the pybuild install tree between the two packages; override
     dh_installdocs so formiko-vim's doc directory is a symlink to
     formiko's

QA information

Comments

  1. The entry about `formiko` caught my eye because I maintain `ruby-mdl` as a
Markdown syntax checker (and since version 0.17.0 for some of the rules,
reformatter).  So far, I did not attempt to package an implementation in Python
into a .deb.

My recommendations are:

- consider to move the repository _to package_ to salsa.debian.org.  This is
  free of charge for you, either in a namespace of your choice, or of the
  corresponding team.  Benefits include the optional use of quality checks
  already established and maintained (file `d/salsa-ci.yml`) already while
  preparing the package, well before uploading a .deb to the mentors page.
  (Private repositories on salsa equally allow to run `d/salsa-ci.yml` to
  experiment, too.)  An already established presence there likely eases
  `formiko` to become a team maintained package - while you remain the default
  uploader, team members can help (including preparation of an upload) if you a
  stuck in a problem, or temporarily unable to maintain the package (bus
  factor).
  
  Me too, I started packaging `ruby-mdl`outside the Ruby team.
- within the repository _to package_, consider a three-branch layout:
  `pristine-tar` to retain the upstream `.tar.gz` or `tar.xz` archive, and
  `upstream` about the fetched upstream source code, and a branch
  `debian/latest` dedicated to adjustments (including optional patches) to
  Debian.  Names here use the convention for Ruby, including an auxillary file
  `d/gbp.conf` - see https://salsa.debian.org/ruby-team/ruby-mdl - which seem to
  differ a bit from the practice adopted for Python
  https://wiki.debian.org/Teams/Ruby/Packaging (e.g.,
  https://salsa.debian.org/python-team/packages/pylint) For one, this layout
  would ease review by a potential sponsor for a cleaner separation of upstream
  code vs. adjustments for Debian, probing to build the .deb, maintenance
  (updates & optional branches for backports), and optional move to become a
  team maintained package.
  
  
Because I'm sponsored myself and can't sponsor others' work don't want to delay
an upload here and thus use "ready" here.  To me, the previous upload (September
11th) with the erroneous (and now corrected) version - because outdated - can be
removed if you like.
    Ready Norwid Behrnd at Sept. 15, 2026, 5:26 p.m.

Upload #1

Information

Version: 2.0.0-3
Uploaded: 2026-09-11 06:52
Source package: formiko_2.0.0-3.dsc
Distribution: unstable
Section: editors
Priority: optional
Homepage: https://github.com/ondratu/formiko
Vcs-Git: https://github.com/ondratu/formiko-debian.git
Vcs-Browser: https://github.com/ondratu/formiko-debian

Changelog

 formiko (2.0.0-3) unstable; urgency=medium
 .
   * debian/patches: add pynvim-optional-import.patch, fixing a startup
     crash of formiko (without formiko-vim) when python3-pynvim is not
     installed but gir1.2-vte-3.91 is (Recommends installs it by
     default); backported from upstream commit
     7ac2d9dc203ad60f796cb9c97efec6da51bee37b

QA information

Comments

  1. If you improve the packaging in multiple steps, and thus by multiple uploads to
the mentor page, beside the time stamp of the upload to the mentors page, the
uploads obtain a counter (1; 2, 3, ...) to visually facilitate navigation on the
mentors website.  Keep in mind these usually do not justify to change `2.0.0-2`
to `2.0.0-3` in d/changelog, because substring `-2` is about the Debian
revision, i.e. to easily discern versions if the package eventually is admitted
to Debian testing (section 5.6.12 of the Debian manual,
https://www.debian.org/doc/debian-policy/ch-controlfields.html).

Standard's version 4.7.4 (d/control) retains the change introducted by standard
4.7.3 that a priority `optional` is presumed implicit default (section 10.3,
https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-7-4).

Does current upload #2 (2026-09-11 06:52 utc) include changes of upload #1
(2026-08-27 08:37 utc)?  If so, the d/changelog of the more recent upload should
retain / contain (parts) of the earlier.
    Needs work Norwid Behrnd at Sept. 14, 2026, 8:36 a.m. 
  2. Thanks for the review and for pointing out the versioning issue. You're right — 2.0.0-2 was never accepted into the archive, so the pynvim crash fix shouldn't have been released as a new 2.0.0-3, but merged into the still-unreleased 2.0.0-2 instead. I've fixed this: the 2.0.0-2 changelog entry now contains both changes (the formiko-vim split and the pynvim fix) in a single entry. The corrected package has been uploaded — please have another look.
    Ready Ondřej Tůma at Sept. 14, 2026, 3:01 p.m.