Bug#712610: RFS: meson/0.4.1-22-gea3e8f1-1 [ITP]
(I don't intend to sponsor this package.)
* Jussi Pakkanen <jpakkane@gmail.com>, 2013-06-18, 00:15:
http://mentors.debian.net/debian/pool/main/m/meson/meson_0.4.1-22-gea3e8f1-1.dsc
How was .orig.tar generated? There's neither get-orig-source target nor
README.source that would explain it...
Is there a reason you based the Debian package on a VCS snapshot instead
of a released version?
What does "high-productivity" in the package description mean?
d/copyright should refer to the /usr/share/common-licenses/Apache-2.0
file; see Policy §12.5.
The package FTBFS if built twice in a row:
| dpkg-source -b meson-0.4.1-22-gea3e8f1
| dpkg-source: info: using source format `3.0 (quilt)'
| dpkg-source: info: building meson using existing ./meson_0.4.1-22-gea3e8f1.orig.tar.gz
| dpkg-source: error: cannot represent change to work area/.ninja_deps: binary file contents changed
Please honour DEB_BUILD_OPTIONS=nocheck; see Policy §4.9.1.
Python modules should be byte-compiled. You probably want to use
dh_python3 for this purpose.
You should depend on python3-ply.yacc-X.Y, where X.Y is tabversion from
you parsetab.py. Unfortunately there's no tool to generate this
dependency automatically. (Such tool would be trivial to implement,
because there is already dh_python-ply for Python 2.)
"-tt" is a no-op in Python 3.
'wrapper to run tests with (e.g. valgrind' - an unmatched left
parenthesis creates an unresolved tension that will stay with you all
day.
The manual page is not very helpful.
symbolextractor should probably gain support for kFreeBSD and Hurd.
Do I understand correctly that meson will always use ccache if it is
installed? That sounds like a bad design.
get_library_dirs() is broken on most Debian architectures. It's also
broken if the compiler's architecture is not native.
Lintian emits:
I: meson source: quilt-patch-missing-description explicit33.patch
I: meson source: quilt-patch-missing-description noqt5.patch
I: meson source: debian-watch-file-is-missing
P: meson: no-homepage-field
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/backends.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/delwithsuffix.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/depfixer.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/environment.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/interpreter.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/meson_install.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/meson_test.py
E: meson: python-script-but-no-python-dep usr/share/meson-0.5.0-research/symbolextractor.py
(I suppose python-script-but-no-python-dep is emitted because of
"#!/usr/bin/env python3" shebang without "python3" dependency.)
--
Jakub Wilk
Reply to: