Packaging for Debian

Hi all,

This looks interesting and important, at the same time.. ;) I would like to package this in Debian and wanted to know: what do you think regarding this?

Thanks for your work, cheers, Georg

I would be happy to help to make this happen once we're reached the second release (since bugs tend to appear out of nothing right after a release)

changed milestone to %0.2.0 - Bunny

assigned to @georg

Would it be possible to include the nautilus extension (#2 (closed)), or should this go in an other package?

@jvoisin Up until now I've never dealt with Nautilus, but this shouldn't be a big deal. I'll ship it via the mat2 package. Also, two more questions / notes:

• Is the name "mat2" "settled"?
• I've found a co-maintainer as well.

Thanks for your work, cheers, Georg

• Yup, I would like to keep "mat2", since it's a completely new implementation of the old "mat"
• Amazing

If it's beta you might want to upload that package to experimental only for now I guess?

Well, actually I wanted to go straight to unstable. It's still a quite early stage, that's true, but unstable and testing increases the potential amount of people willing to test. If we're running into big problems, we still can remove it from testing again, to prevent it from being included in buster.

@jvoisin We'll start to package this within the next upcoming days. Could you release an initial first beta version?

Also: Could you tell me which information (email) we should use in copyright etc. files?

Here is the very first release of MAT2 \o/

I added mail email information in the README file: julien.voisin+mat2@dustri.org.

Thanks a lot for tagging the release, @jvoisin!

We just started packaging mat2 for Debian and ran into some issues (which was expected and is not meant as criticism at all)

The most important one touches the file structure of mat2. The current one with main.py as main script and a src directory containing the libs makes it complicated to properly package mat2.

Do you intend to add some Python setup/installation support (e.g. setuptools) into mat2 anytime soon? And appart from that, renaming the src directory to mat2 and main.py to mat2.py would make packaging much easier. Otherwise, we'll have to patch mat2 in the package

Sure, no problem, it's done in 38fae60b

I don't have any plans with regard to using some python-specific installer/setup. Last time I checked (something like 5 years ago I think), it was an horrible mess. Maybe things have changed now, I don't know. Would it ease the packaging to use one? If so, I'll be happy to do it.

Thanks a ton, @jvoisin. The patch helps us a lot with packaging mat2 for Debian.

I don't have a strong opinion on python installer/setup tools. We don't need it for packaging mat2, it was more asked out of couriousity.

added packaging label

Thanks a ton for adding setup.py, @jvoisin!

You missed to rename mat2.py in setup.py after renaming the script, though

changed milestone to %1.0 - Pony

There is a blocked for the packaging of the Nautilus extension ( #2 (closed) ): the required version (1.2.) of nautilus-python isn't packaged in Debian yet.

I will ask the maintainers listed here to take care of this. You'll be in Cc:.

thanks for this work! i'd love to see mat2 available in debian, even if the nautilus extension isn't ready yet.

i've filed https://bugs.debian.org/907591 to explicitly request an update of nautilus-python in debian to a version that mat2 needs.

@dkg: thanks! I've never received an answer to neither of my two emails, so a bug on Debian's bug tracker seems like a better way to trace this :)

@jvoisin Besides the above problem, which we need to deal in Debian with (so shouldn't be a concern for you), I've encountered another problem: the tests in tests/test_climat2.py invoke mat2 via ./mat2.

Packages in Debian are, besides other techniques, tested via autopkgtest: In these tests, the software "as-installed" is tested, that is, in this case, tests and mat2 are not stored in the same directory: the tests directory is stored in some possibly random directory somewhere, and mat2 is located in /usr/bin. Calling mat2 via ./mat2 therefore doesn't work.

Maybe tests/test_climat2.py could just rely on $PATH, and adding the parent dir to it (and removing if afterwards again)?

Check a1c39104 :)

@jvoisin Thanks a lot! \m/

Initial upload upcoming.

Initial upload done. The package now needs manual approval by the Debian FTP masters. Will update this ticket once again, as soon as the package hit the archive.

https://ftp-master.debian.org/new/mat2_0.4.0-1.html woohoo \o/

Damn, that was fast. Already got accepted: https://tracker.debian.org/news/993286/accepted-mat2-040-1-source-all-into-unstable-unstable/

Should be in unstable archive in a few hours from now \o/

As per the above: ACCEPTed into unstable, thus closing this ticket.

closed