* Package name    : mutt-ical
  Version         : 2.0.2~20240916.g7c795ee1fd74-1
  Upstream Contact: Pip! Gold <https://github.com/asciipip/>
* URL             : https://github.com/asciipip/mutt-ical/
* License         : GPL3+
  Programming Lang: Python
  Description     : iCalendar event integration for mutt and neomutt

I often work with clients who send me meeting requests via Google or MS Teams,
which only put the relevant time and date into iCalendar MIME attachments
Mutt and Neomutt don't have native support for rendering iCalendar events, so
this package contains a small Python script which can be used for that purpose
via a user's ~/.mailcap file.

Some work has already been done to make the package mostly functional, see
<https://git.pengutronix.de/cgit/rhi/mutt-ical/tree/>.

This is a small project and upstream development is not very active, although
there are some improvement opportunities, especially replying and accepting or
refusing attendance for iCal events via mutt. I've sent pull requests to
upstream in the past, but I expect that the maintainance load in Debian will be
fairly small and manageable. As said, I'm using this project for work, and I'm
willing to maintain the package in Debian as part of the Mutt packaging team.
Currently I will need a sponsor to upload this package.

Cheers,
  - Roland

Sounds really useful! I'd be happy to sponsor.

This being a simple(?) pypy package would it not be better to maintain it
in python team? Is there any reason you can see not to?

https://wiki.debian.org/Teams/PythonTeam

Thanks,
--Daniel

Cool, thanks!

No reason other than the fact that it has to do with mutt and it was the first
team that came to mind :) I have no strong opinion on either option.

 - Roland

Hi Roland e.a.,

Thanks for expressing your interest in working on getting mutt-ical shipped
with Debian.  I'd love this to get tackled!

I've just tried to take look at
https://git.pengutronix.de/cgit/rhi/mutt-ical/tree/ , but that currently gives
me:

 Forbidden
 You don't have permission to access this resource.
 Apache/2.4.67 (Debian) Server at git.pengutronix.de Port 443

.  Anyway, it'd be cool if your work was available from somewhere (e.g.
https://salsa.debian.org/python-team/packages .)  Happy to help by e.g. testing
release candidates.

Thanks, Bye,

Joost

Oh right, sorry, we had to disable that cgit since, because the AI bots were
just eating too many resources :-/
https://salsa.debian.org/rohieb/mutt-ical

I also noticed that I still have to assemble the debian/copyright, which was not
really needed for our internal use case… I can do that next week.

If all the packaging is ready, the repo could also be transferred to the
python-packaging namespace.

Thanks,

 - Roland

Alright, it's been a bit more than a week, but I consider this ready now. I've
fixed some things that Joost mentioned to me personally, also added a man page
(based on the project's REAMDE) and fixed a lot of other lintian complaints. (It
still warns about 'hyphen-in-upstream-part-of-debian-changelog-version', since
the 2.0.2 release tag is missing in the upstream repo, I've resorted to a 'git
describe'-style version number.)

My current state is at
<https://salsa.debian.org/rohieb/mutt-ical/-/commits/debian%2Flatest>, and I've
uploaded the resulting package to mentors.debian.org for sponsorship review:
<https://mentors.debian.net/package/mutt-ical/>

Thanks,

 - Roland

Hi Roland,

I'm happy you found the time to work on this :)

Le Sun, Aug 09, 2026 at 07:26:39PM +0200, Roland Hieber a écrit :

@ https://mentors.debian.net/package/mutt-ical/ :

– Package has lintian warnings: mutt-ical source
    W missing-debian-watch-file-standard
        [debian/watch]
    W recommended-field
        (in section for source) Priority [debian/control:1]
    P hyphen-in-upstream-part-of-debian-changelog-version
        2.0.2-20240916-g7c795ee1fd74 [debian/changelog:1]

It has, in d/control:

 Vcs-Git: https://salsa.debian.org/rohieb/mutt-ical.git

Maybe that could better be https://salsa.debian.org/debian/ (so that
cooperation would be easier) or https://salsa.debian.org/python-team/packages
(after an ACK from the Python team, and after consulting the Team's policy
document at https://www.debian.org/doc/packaging-manuals/python-policy/ ; I
believe having team+python@tracker.debian.org as Maintainer would require
that.)

(Also: https://salsa.debian.org/rohieb/mutt-ical/-/pipelines : "This project is
not currently set up to run pipelines."  Hrm, but upstream doesn't seem to ship
any test infrastructure, so I guess that would be non-trivial...)

Anyway: Once your package is lintian-clean I'd be happy to upload it.

HTH!

Bye,

Joost

Hi Joost,

Thanks!

I have the feeling that this is a false-positive. I converted the file to
Version 5 format (because my lintian told me so ;)), and the warning does not
happen on my machine with lintian v2.138.0. The full warning text mentions: "The
first non-comment line of debian/watch should be a version= or Version:
declaration.", which is definitely the case here… 🤔

Same for this one. This warning was removed in lintian v2.128.0 according to
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111513>.

That indeed also happens on my machine, but I'm not sure how to handle it and
keep 'gbp buildpackage' happy. Upstream forgot to push the Git tag for version
2.0.2 (I've opened an upstream issue about that), so I set the version in
d/changelog to something that can be parsed by 'git rev-parse' (using the 'git
describe' format, which must include at least two dashes).

The 2.0.1 release is not buildable by pybuild due to a syntax error in pyproject.toml
which was fixed in 2.0.2.

However, when re-read my own bug report [2], strictly speaking there is no 2.0.2
release (on GitHub) yet, even if there claims to be one on PyPI [3].

  [2]: https://github.com/asciipip/mutt-ical/issues/5
  [3]: https://pypi.org/project/mutt-ical/

When thinking about it again, the best way to solve this is by packaging the
latest release on GitHub, 2.0.1, instead, and pull in the changes between 2.0.1
and 2.0.2 as a Debian patch series, and name it '2.0.1-1` or even
`2.0.1+really2.0.2-1` in debian/changelog.

Does that sound reasonable?

I'm all for it, but I'm not sure who can move it to another namespace. I
certainly don't have the access rights for it.

Hmm yes, there are no tests, but we could at least include the deb build
infrastructure. I've done so for now by setting up pipelines via
<https://salsa.debian.org/rohieb/mutt-ical/-/blob/debian/latest/debian/salsa-ci.yml>.

Cheers,

 - Roland