Quoting José Luis Tallón (jltal...@adv-solutions.net): > Christian PERRIER wrote: > > Dear maintainer of up-imapproxy, > > > > On Wednesday, February 10, 2010 I sent you a notice announcing my intent to > > upload a > > NMU of your package to fix its pending l10n issues, after an initial > > notice sent on Friday, February 05, 2010. > > > Updated version of the package available at: > > http://devel.adv-solutions.net/debian/pool/main/mail/imapproxy/up-imapproxy_1.2.7~rc3-2.dsc > > > You either agreed for this NMU or did not respond to my notices. > > > I did, as usual :-) > Please upload the package referenced above instead; It includes all > localization updates as submitted.
Hmmm, forgot about that.
Built and upload in progress...
You may want to update the packaging for the few lintian warnings and
errors. Feel free to ask me for another sponsoring when the fixed
package is ready. particularly the two errors should be fixed.
W: up-imapproxy source: debian-rules-ignores-make-clean-error line 56
N:
N: A rule in the debian/rules file for this package calls the package's
N: clean or distclean target with a line like:
N:
N: -$(MAKE) distclean
N: or
N: $(MAKE) -i distclean
N:
N: The leading "-" or the option -i tells make to ignore all errors.
N: Normally this is done for packages using Autoconf since Makefile may not
N: exist. However, this line ignores all other error messages, not just the
N: missing Makefile error. It's better to use:
N:
N: [ ! -f Makefile ] || $(MAKE) distclean
N:
N: so that other error messages from the clean or distclean rule will still
N: be caught (or just remove the "-" if the package uses a static
N: makefile).
N:
N: Severity: normal, Certainty: certain
N:
W: up-imapproxy source: out-of-date-standards-version 3.8.3 (current is 3.8.4)
N:
N: The source package refers to a Standards-Version older than the one that
N: was current at the time the package was created (according to the
N: timestamp of the latest debian/changelog entry). Please consider
N: updating the package to current Policy and setting this control field
N: appropriately.
N:
N: If the package is already compliant with the current standards, you
N: don't have to re-upload the package just to adjust the Standards-Version
N: control field. However, please remember to update this field next time
N: you upload the package.
N:
N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
N: debian-policy package for a summary of changes in newer versions of
N: Policy.
N:
N: Severity: normal, Certainty: certain
N:
E: imapproxy: debian-changelog-file-uses-obsolete-national-encoding at line 8
N:
N: The Debian changelog file must be valid UTF-8, an encoding of the
N: Unicode character set.
N:
N: There are many ways to convert a changelog from an obsoleted encoding
N: like ISO-8859-1; you may for example use "iconv" like:
N:
N: $ iconv -f ISO-8859-1 -t UTF-8 changelog > changelog.new
N: $ mv changelog.new changelog
N:
N: Refer to Debian Policy Manual section 4.4 (Debian changelog:
N: debian/changelog) for details.
N:
N: Severity: serious, Certainty: certain
N:
E: imapproxy: init.d-script-missing-dependency-on-remote_fs
/etc/init.d/imapproxy: required-start
N:
N: The given init script seems to refer to /usr, possibly using a file or
N: binary from there. Without a dependency on $remote_fs in Required-Start
N: or Required-Stop, as appropriate, the init script might be run before
N: /usr is mounted or after it's unmounted.
N:
N: Using Should-Start or Should-Stop to declare the dependency is
N: conceptually incorrect since the $remote_fs facility is always
N: available. Required-Start or Required-Stop should be used instead.
N:
N: Refer to http://wiki.debian.org/LSBInitScripts for details.
N:
N: Severity: important, Certainty: possible
N:
E: imapproxy: init.d-script-missing-dependency-on-remote_fs
/etc/init.d/imapproxy: required-stop
signature.asc
Description: Digital signature
