On 07/11/2018 10:04 AM, Umang Parmar wrote:
> You should uploading your package on mentors.debian.net
> <http://mentors.debian.net> and ask for sponsorship on debian-mentors
> mailing list to get in contact with more Debian Developers who can
> review and then upload ypur package.
This is definitely more appropriate for debian-mentors, but just a minor
note that lintian can help find many problems with packages.
There's a check for just critical (autoreject) problems below.
I would recommend using debhelper (see dh_make(7) ) and the new
maintainer's guide:
https://www.debian.org/doc/manuals/maint-guide/
Thanks for your suggestion.
If possible I would prefer to improve the script so that it generates
the package in the right format, rather than doing everything manually.
lintian -F pw.deb
E: pw: no-copyright-file
N:
N: Each binary package has to include a plain file
N: /usr/share/doc/<pkg>/copyright
N:
N: Refer to Debian Policy Manual section 12.5 (Copyright information) for
N: details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: copyright-file, Type: binary
N:
E: pw: extended-description-is-empty
N:
N: The extended description (the lines after the first line of the
N: "Description:" field) is empty.
N:
N: Refer to Debian Policy Manual section 3.4 (The description of a
package)
N: for details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: description, Type: binary, udeb
N:
E: pw: maintainer-address-missing https://github.com/dashohoxha/pw
N:
N: The maintainer field must contain the package maintainer's name and
N: email address, with the name followed by the address inside angle
N: brackets (< and >). The address seems to be missing.
N:
N: Refer to Debian Policy Manual section 5.6.2 (Maintainer) for details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: fields, Type: binary, udeb, source
N:
E: pw: wrong-file-owner-uid-or-gid usr/ 1000/1000
N:
N: The user or group ID of the owner of the file is invalid. The
owner user
N: and group IDs must be in the set of globally allocated IDs, because
N: other IDs are dynamically allocated and might be used for varying
N: purposes on different systems, or are reserved. The set of the
allowed,
N: globally allocated IDs consists of the ranges 0-99, 64000-64999 and
N: 65534.
N:
N: It's possible for a Policy-compliant package to trigger this tag
if the
N: user is created in the preinst maintainer script, but this is a very
N: rare case and doesn't appear to be necessary. If you found yourself
N: needing to create a package that works this way, please file a bug
N: against Lintian to let the maintainers know.
N:
N: Refer to Debian Policy Manual section 9.2 (Users and groups) for
N: details.
N:
N: Severity: serious, Certainty: certain
N:
N: Check: files, Type: binary, udeb
N:
E: pw: wrong-file-owner-uid-or-gid usr/bin/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/bin/pw 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/cmd_field.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/cmd_find.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/cmd_gen.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/cmd_qr.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/ext/cmd_test1.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/platform/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/platform/cygwin.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/platform/darwin.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/platform/freebsd.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/lib/pw/platform/openbsd.sh 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/share/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/share/man/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/share/man/man1/ 1000/1000
E: pw: wrong-file-owner-uid-or-gid usr/share/man/man1/pw.1 1000/1000