[2018-12-19 15:41] Adrian Nuta
> > * your documentation should be in /usr/share/doc/manticore, not MANTICORE
> >
> removed that folder (not sure why cmake was using uppercased name)
>
> > * I believe you install not all available documentation. You may want
> >to create bin:manticore-doc
Uploaded a new version.
> You run `lintian -EvIL +pedantic', don't you? Missing `debian/watch'
> considered low-severity issue
>
Didn't knew about these switches, I'll use that from now on.
* no manpage for wordbreaker. You will not pass NEW without it.
>
* whitespace errors in debian/rules,
> Added a debian/watch, not sure why mentor lintian doesn't see it, uscan
> doesn't report any error, it should get our official tar.gz release for
> github.
You run `lintian -EvIL +pedantic', don't you? Missing `debian/watch'
considered low-severity issue
> Fixed the overrides and
>
>
> (Programmer hat) Why build system need to know, which distro it is build
> on? I guess (did not check sources) you actually interested in
> something more specific, then name of distribution (my
> linux-from-scratch installation does not have name, for example).
>
Yes, name of distribution
[2018-12-10 22:13] Adrian Nuta
> * Using output of `lsb_release' in CPP flags could be issue for
> > reproducibility. Is it strictly necessary?
> >
>
> That flag is for our cmake to know on which distro is (the output of that
> command involving lsb_release should be 'debian' ) - we
>
> * there is no point in such overrides:
> override_dh_auto_build:
> dh_auto_build
>
understood
* Using output of `lsb_release' in CPP flags could be issue for
> reproducibility. Is it strictly necessary?
>
That flag is for our cmake to know on which distro is
[2018-12-09 23:03] Adrian Nuta
> Hi, git repo is at https://github.com/manticoresoftware/manticoresearch.
>
> Right now I have debhelper (>= 11), but previous used debhelper-compat (=
> 11), same message.
[ Comments below are about commit 0f016406 ---
remote HEAD at time of writing ]
Can't
Hi, git repo is at https://github.com/manticoresoftware/manticoresearch.
Right now I have debhelper (>= 11), but previous used debhelper-compat (=
11), same message.
[2018-12-07 16:39] Adrian Nuta
> Switched to quilt, but I don't understand why mentor lintian says "No
> compatibility level set!"
Can you please remind, where are git sources of your package?
I could be that mentor lintian is old and does not recognize
Build-Depends:
Hi,
Switched to quilt, but I don't understand why mentor lintian says "No
compatibility level set!"
Thanks
[ Top posting is discouraged ]
[2018-11-27 21:11] Adrian Nuta
> * Since this package is not debian-specific, and have its own release
>process, package must be foreign (with -1 revision), not native.
> changed to 1.0, not sure if this is correct
No. Source format 1.0 is long deprecated.
Hi Dmitry,
* Since this package is not debian-specific, and have its own release
process, package must be foreign (with -1 revision), not native.
changed to 1.0, not sure if this is correct
* You claim compat=11, but build-depends on debhelper >= 10. You'd
better use new style:
[2018-10-29 09:39] Manticore Search Maintainers
> I am looking for a sponsor for my package "manticore"
> dget -x
> https://mentors.debian.net/debian/pool/main/m/manticore/manticore_2.7.3.dsc
As time of writing (Mon Oct 29 20:44:20 UTC 2018), I see following
issues with package on
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "manticore"
* Package name: manticore
Version : 2.7.3
Upstream Author : Manticore Search
* URL : https://www.manticoresearch.com/
* License : GPL-2
14 matches
Mail list logo
