Dear Maintainer,

I created the upstream project
https://github.com/media-types/media-types to create a pure IANA based
mime.types file that can be used as basis for the different
distributions and consumers. The project just ships the media types and
file extensions declared in the IANA database. You can see the generated
data on https://media-types.github.io/

As user of this project you would only need to maintain the non-standard
media types and additional file extensions. As hopefully more and more
media types get officially registered this delta should shrink over
time.

I created two branches on https://salsa.debian.org/bdrung/media-types:

1. use-media-types to use media-types as upstream project. Special note
for the "Add Debian customization" that adds the Debian delta for extra
media types and additional file extensions.

2. reduce-delta-to-media-types contains commits on top of the master
branch to reduce the diff between the current Debian package and the
variant that uses media-types.

Let me know what you think and in case you need adjustments in the
upstream code.

Hi Benjamin,

Le Thu, Aug 20, 2026 at 01:33:43AM +0200, Benjamin Drung a écrit :

Thank you so much for doing this!

When I split the old mime-support package into mailcap and media-types I was
hoping that this would happen one day.  I really appreciate your effort to
minimise the detla between Debian and the IANA.

I have been neglecting the mailcap package too much while working on
media-types by batch at the end of releases.  I do not want to be a such a
bottleneck anymore.  Would you be interested in adopting our media-types
package?  Do you think we should discuss such a handover on -devel first?

Have a nice day,

Charles

You're welcome. This project started as side-project a few weeks ago.

I am open for becoming a co-maintainer to keep the IANA changes rolling,
but I am not keen on handling users requesting adding non IANA mime
types. I am happy to help bolting the current package on top of the new
media-type project. I think that it makes sense to do it in two steps:
Do another release with changes to reduce the delta in mime.types. Then
do a second upload with the switch.

I like the overall explanation in README.md and that we urge people to
officially register media types.

Feel free to broaden the discussion on -devel.

Le Thu, Aug 20, 2026 at 02:54:05AM +0200, Benjamin Drung a écrit :

No problem, I will add you to the Uploaders and announce the changes on
debian-devel.

By the way, I would be keen on using dgit to update and upload the package,
would that be fine for you?

https://manpages.debian.org/trixie/dgit/dgit-maint-merge.7.en.html

Have a nice day,

Charles

Thanks.

Yes. That will be the reason for me to have a deeper look at dgit and
learn how to use it. Does it support using upstream tarballs plus their
signatures? I create upstream tarballs that match the exact git content.

Le Fri, Aug 21, 2026 at 06:06:20PM +0200, Benjamin Drung a écrit :

Hi Benjamin,

I think that the philosophy of dgit is to prefer git merges over tarball
imports.  I started to look more in details at the dgit-maint-merge workflow
and it seems to fit our needs, since your system is designed so that deviations
to the upstream repository do not need to be represented as patches.

The main difficulty seems to be to stitch the histories of the two
repositories, but it does not seem to be too hard.

How about we go ahead with dgit-maint-merge?

Have a nice day,

Charles

Hi Charles,

I read the dgit-maint-merge man page and that workflow sounds good to
me. I still have one open question how to handle tarball signatures.

Before we do the dgit merge, I recommend to do one more media-types
upload with fixes to bring both closer together. I created some merge
requests for that. Can you review those:
https://salsa.debian.org/debian/media-types/-/merge_requests