Ubuntu
cinder package

not lintian clean

Bug #1022641 reported by Jamie Strandboge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cinder (Ubuntu)
Fix Released
Low
Unassigned
lintian (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

In performing bin deNEW, I noticed the following:
$ lintian cinder-api_2012.2~f1~20120503.2-0ubuntu1_all.deb:
E: cinder-api: postrm-does-not-call-updaterc.d-for-init.d-script etc/init.d/cinder-api
$ lintian cinder-common_2012.2~f1~20120503.2-0ubuntu1_all.deb:
$ lintian cinder-scheduler_2012.2~f1~20120503.2-0ubuntu1_all.deb:
E: cinder-scheduler: postrm-does-not-call-updaterc.d-for-init.d-script etc/init.d/cinder-scheduler
$ lintian cinder-volume_2012.2~f1~20120503.2-0ubuntu1_all.deb:
E: cinder-volume: postrm-does-not-call-updaterc.d-for-init.d-script etc/init.d/cinder-volume
$ lintian python-cinder_2012.2~f1~20120503.2-0ubuntu1_all.deb:
W: python-cinder: wrong-section-according-to-package-name python-cinder => python

Note, the postrm-does-not-call-updaterc.d-for-init.d-script issue might be because of the recent debhelper adding something to postinst without a corresponding postrm entry.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

The warning about python-cinder's section is valid, but Low priority

The other one is bogus IMO, as dh_installinit seems to be adding an update-rc.d to *remove* the deprecated /etc/init.d start in favor of the upstart job. So the lintian check needs to make sure that the call in postinst is *adding* and not *removing*.

Changed in cinder (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in lintian (Ubuntu):
status: New → Invalid
Revision history for this message
James Page (james-page) wrote :

Remaining lint:

W: cinder-backup: binary-without-manpage usr/bin/cinder-backup
W: cinder-common: binary-without-manpage usr/bin/cinder-rtstool
W: cinder-common: binary-without-manpage usr/bin/cinder-wsgi
W: cinder-volume: binary-without-manpage usr/bin/cinder-volume-usage-audit

Revision history for this message
James Page (james-page) wrote :

I'm going to mark this bug as Fix Released as the original issues have gone, and the others are simply warnings.

Changed in cinder (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.