Hi Joshua, <div><br></div><div>Yes looks neat and clean now :) and now lintain warning so far. I have also build with pbuilder and able to build successfully.</div><div><br></div><div>See log for more details.</div><div><a href="http://pbuilder.wordpress.com/2010/05/28/chef_0-8-16-4_i386-dsc/">http://pbuilder.wordpress.com/2010/05/28/chef_0-8-16-4_i386-dsc/</a></div>
<div><br></div><div><br></div><div><a href="http://pbuilder.wordpress.com/2010/05/28/chef_0-8-16-4_i386-dsc/"></a>Thanks</div><div>Deepak<br><br><div class="gmail_quote">On Thu, May 27, 2010 at 10:49 PM, Joshua Timberman <span dir="ltr"><<a href="mailto:joshua@opscode.com">joshua@opscode.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hello!<br>
<br>
Thanks for the review. Tollef is involved in the Chef project community and had volunteered to sponsor. I pushed new packaging to both the repositories:<br>
<br>
<a href="http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/chef/debian/#_trunk_chef_debian_" target="_blank">http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/chef/debian/#_trunk_chef_debian_</a><br>
<a href="http://github.com/opscode/opscode-packages/tree/master/debian/chef/debian/" target="_blank">http://github.com/opscode/opscode-packages/tree/master/debian/chef/debian/</a><br>
<br>
The packages should be ready for Upload.<br>
<br>
Thank you<div><div></div><div class="h5"><br>
<br>
On May 24, 2010, at 3:45 AM, Deepak Tripathi wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Joshua,<br>
<br>
I have build chef from (svn+ssh://<a href="http://deepak-guest@svn.debian.org/svn/pkg-ruby-extras" target="_blank">deepak-guest@svn.debian.org/svn/pkg-ruby-extras</a> ) and found that there are couple of lintian errors/warnings are there.<br>
<br>
see below lintian logs using ( lintian --info --display-info --display-experimental --pedantic --show-overrides --checksums --color auto)<br>
<br>
--<br>
I: chef source: missing-debian-source-format<br>
N:<br>
N: Explicitly selecting a source format by putting the format in<br>
N: debian/source/format is recommended. This allows for future removal of<br>
N: the 1.0 default for the package source format and, depending on the<br>
N: source format, may allow unambiguous declaration of whether this package<br>
N: is native or non-native.<br>
N:<br>
N: If you don't have a reason to stay with the old format for this package,<br>
N: please consider switching to "3.0 (quilt)" (for packages with a separate<br>
N: upstream tarball) or to "3.0 (native)" (for Debian native packages).<br>
N:<br>
N: If you wish to keep using the old format, please create that file and<br>
N: put "1.0" in it to be explicit about the source package version. If you<br>
N: have problems with the 3.0 format, the dpkg maintainers are interested<br>
N: in hearing, at <a href="mailto:debian-dpkg@lists.debian.org" target="_blank">debian-dpkg@lists.debian.org</a>, the (technical) reasons why<br>
N: the new formats do not suit you.<br>
N:<br>
N: Refer to the dpkg-source(1) manual page and<br>
N: <a href="http://wiki.debian.org/Projects/DebSrc3.0" target="_blank">http://wiki.debian.org/Projects/DebSrc3.0</a> for details.<br>
N:<br>
N: Severity: wishlist, Certainty: certain<br>
N:<br>
I: chef source: no-complete-debconf-translation<br>
N:<br>
N: Even though this package provides debconf translation support, there are<br>
N: no translations or none of the translations are complete. This may mean<br>
N: that translators weren't properly warned about new strings.<br>
N:<br>
N: Translators may be notified of changes using podebconf-report-po, for<br>
N: example:<br>
N:<br>
N: podebconf-report-po --call --withtranslators --deadline="+10 days" \<br>
N: --languageteam<br>
N:<br>
N: Refer to Debian Developer's Reference section 6.5.2.2 (Be kind to<br>
N: translators) for details.<br>
N:<br>
N: Severity: wishlist, Certainty: possible<br>
N:<br>
E: chef: init.d-script-missing-dependency-on-remote_fs /etc/init.d/chef-server: required-start<br>
N:<br>
N: The given init script seems to refer to /usr, possibly using a file or<br>
N: binary from there. Without a dependency on $remote_fs in Required-Start<br>
N: or Required-Stop, as appropriate, the init script might be run before<br>
N: /usr is mounted or after it's unmounted.<br>
N:<br>
N: Using Should-Start or Should-Stop to declare the dependency is<br>
N: conceptually incorrect since the $remote_fs facility is always<br>
N: available. Required-Start or Required-Stop should be used instead. Also,<br>
N: please note that $all should not be used in Required-Stop, only<br>
N: Required-Start.<br>
N:<br>
N: Refer to <a href="http://wiki.debian.org/LSBInitScripts" target="_blank">http://wiki.debian.org/LSBInitScripts</a> for details.<br>
N:<br>
N: Severity: important, Certainty: possible<br>
N:<br>
E: chef: init.d-script-missing-dependency-on-remote_fs /etc/init.d/chef-server: required-stop<br>
P: chef: maintainer-script-without-set-e postinst<br>
N:<br>
N: The maintainer script passes -e to the shell on the #! line rather than<br>
N: using set -e in the body of the script. This is fine for normal<br>
N: operation, but if the script is run by hand with sh /path/to/script<br>
N: (common in debugging), -e will not be in effect. It's therefore better<br>
N: to use set -e in the body of the script.<br>
N:<br>
N: Refer to Debian Policy Manual section 10.4 (Scripts) for details.<br>
N:<br>
N: Severity: pedantic, Certainty: certain<br>
N:<br>
P: chef: maintainer-script-without-set-e config<br>
P: chef-solr: maintainer-script-without-set-e postinst<br>
P: chef-solr: maintainer-script-without-set-e config<br>
E: chef-solr: dir-or-file-in-var-run var/run/chef/<br>
N:<br>
N: /var/run may be a temporary filesystem, so any directories or files<br>
N: needed there must be created dynamically at boot time.<br>
N:<br>
N: Refer to Debian Policy Manual section 9.3.2 (Writing the scripts) for<br>
N: details.<br>
N:<br>
N: Severity: serious, Certainty: possible<br>
N:<br>
E: chef-server: duplicate-updaterc.d-calls-in-postinst chef-server<br>
N:<br>
N: The postinst script calls update-rc.d several times for the same<br>
N: /etc/init.d script.<br>
N:<br>
N: Severity: important, Certainty: certain<br>
N:<br>
E: chef-server: duplicate-updaterc.d-calls-in-postrm chef-server<br>
N:<br>
N: The postrm script calls update-rc.d several times for the same<br>
N: /etc/init.d script.<br>
N:<br>
N: Severity: important, Certainty: certain<br>
N:<br>
E: chef-server: init.d-script-missing-dependency-on-remote_fs /etc/init.d/chef-server: required-start<br>
E: chef-server: init.d-script-missing-dependency-on-remote_fs /etc/init.d/chef-server: required-stop<br>
P: chef-server: maintainer-script-without-set-e postinst<br>
P: chef-server-webui: maintainer-script-without-set-e postinst<br>
P: chef-server-webui: maintainer-script-without-set-e config<br>
---<br>
Please fix them so that it will be in "Ready to upload" state.<br>
<br>
I am changing debian/changelog mode to 'UNREALEASD' now.<br>
<br>
-- <br>
Thanks<br>
Deepak Tripathi<br>
E3 71V3 8Y C063 (We Live By Code)<br>
blog: <a href="http://deepaktripathi.blogspot.com" target="_blank">http://deepaktripathi.blogspot.com</a><br>
pbuilder log: <a href="http://pbuilder.wordpress.com" target="_blank">http://pbuilder.wordpress.com</a><br>
</blockquote>
<br></div></div>
- --<br>
Opscode, Inc<br>
Joshua Timberman, Senior Solutions Engineer<br>
C: 720.334.RUBY E: <a href="mailto:joshua@opscode.com" target="_blank">joshua@opscode.com</a><br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (Darwin)<br>
<br>
iEYEARECAAYFAkv+qaYACgkQO97WSdVpzT1N8QCggxbqNk4ayVcsNpJ+UY/zchTs<br>
bQYAn2Hzoj21Q4ZCvKHUCW54sD4GWR7B<br>
=jCb+<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br><br clear="all"><br>-- <br>Deepak Tripathi <br>E3 71V3 8Y C063 (We Live By Code)<br><a href="http://deepaktripathi.blogspot.com">http://deepaktripathi.blogspot.com</a><br><br>
</div>