[Pkg-giraffe-discuss] z-push: some signed tags missing on the repository
Carsten Schoenert
c.schoenert at t-online.de
Thu Aug 3 01:40:24 UTC 2017
Hi again,
Am 02.08.2017 um 12:18 schrieb Carsten Schoenert:
...
>> Aside: how do you run lintian to get this error? I've tried to make the
>> package lintian-clean, and my own lintian (2.5.52) only says:
>>
>> rolek at sid:~/git$ lintian z-push*changes
>> W: z-push source: out-of-date-standards-version 3.9.8 (current is 4.0.0)
>> N: 3 tags overridden (1 error, 2 warnings)
>>
>> It would be nice if I could see those errors as well.
>
> I normally use the option(s) '-IE' to see all errors and informative
> tags. You can also use '-iIE' that print some more explanation on the
> found issues. And you can add '--pedantic' to minor and experimental
> issues, but this makes only sense once you only have see minor error,
> warning and info tags.
>
> If you want to see also the overridden tags you need to add '-o' too.
> More information is shown in the man page.
this brings some then some overrides on top that we probably can reduce
after the modification of some PHP files by z-push in the past. The
following output lintian is producing.
> root at x260:/build/z-push-2.3.7# lintian -oIE ../z-push_2.3.7-2~1.gbp0341b2_amd64.changes --no-tag-display-limit
> warning: the authors of lintian do not recommend running it with root privileges!
> W: z-push source: maintainer-upload-has-incorrect-version-number 2.3.7-2~1.gbp0341b2
> I: z-push source: composer-package-without-pkg-php-tools-builddep
> I: z-push source: testsuite-autopkgtest-missing
> W: z-push-common: non-standard-apache2-configuration-name z-push-autodiscover.conf != z-push-common.conf
> W: z-push-common: non-standard-apache2-configuration-name z-push.conf != z-push-common.conf
> X: z-push-common: embedded-pear-module usr/share/z-push/include/mimeDecode.php please use php-mail-mimedecode
> X: z-push-backend-imap: embedded-pear-module usr/share/z-push/backend/imap/Mail.php please use php-mail
> X: z-push-backend-imap: embedded-pear-module usr/share/z-push/backend/imap/Net/SMTP.php please use php-net-smtp
> X: z-push-backend-imap: embedded-pear-module usr/share/z-push/backend/imap/Net/Socket.php please use php-net-socket
> X: z-push-backend-imap: embedded-pear-module usr/share/z-push/backend/imap/mimePart.php please use php-mail-mime
Especially all the tags with 'please use package-foo' can now mostly
solved, if Debian is providing the correct versions. Let's look.
--------------
usr/share/z-push/include/mimeDecode.php please use php-mail-mimedecode
This suggested package isn't available right now in unstable/testing,
but someone is working on a reintroducing of this source package.
https://tracker.debian.org/pkg/php-mail-mimedecode
A email to the ITP holder can probably bring some light into. But the
linked source can be used to check for usability.
--------------
usr/share/z-push/backend/imap/Mail.php please use php-mail
Can be solved by linking against the package
https://tracker.debian.org/pkg/php-mail if the version is good enough.
Otherwise a request to update the package can be filled.
--------------
usr/share/z-push/backend/imap/Net/SMTP.php please use php-net-smtp
Can be solved by linking against the package
https://tracker.debian.org/pkg/php-net-smtp if the version is good
enough. Otherwise a request to update the package can be filled.
--------------
usr/share/z-push/backend/imap/Net/Socket.php please use php-net-socket
Can be solved by linking against the package
https://tracker.debian.org/pkg/php-net-socket if the version is good
enough. Otherwise a request to update the package can be filled.
--------------
usr/share/z-push/backend/imap/mimePart.php please use php-mail-mime
Can be solved by linking against the package
https://tracker.debian.org/pkg/php-mail-mime if the version is good
enough. Otherwise a request to update the package can be filled.
Roel, care to check this? If the packages are possible to use the
respective binary package needs a depends and a extra line in the
*.links sequencer file. I can give a advice then if needed. An example
for such a linking can be seen in the package libvmime1-doc.
https://anonscm.debian.org/cgit/pkg-giraffe/libvmime.git/tree/debian/libvmime1-doc.links
--
Regards
Carsten Schoenert
More information about the Pkg-giraffe-discuss
mailing list