Bug#599073: Tests of the new package

2011-05-25 Thread Stéphan Gorget
Thank you very much for the work you did.

I built with this command line :

git-buildpackage --git-debian-branch=phantez/debian/master
--git-upstream-branch=phantez/debian/master
--git-export-dir=~/projects/debian/build-area -uc -us

and I had this output :

steph@mirage:~/projects/debian/build-area$ lintian -I -E
shinken_0.6.4-1_amd64.changes
I: shinken source: debian-watch-file-is-missing
I: shinken-scheduler: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-scheduler.8shinken.gz:33
I: shinken-receiver: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-receiver.8shinken.gz:33
I: shinken-arbiter: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-arbiter.8shinken.gz:33
I: shinken-discovery: spelling-error-in-manpage
usr/share/man/man8/shinken-discovery.8shinken.gz ouput output
I: shinken-poller: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-poller.8shinken.gz:33
I: shinken-reactionner: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-reactionner.8shinken.gz:33
I: shinken-broker: hyphen-used-as-minus-sign
usr/share/man/man8/shinken-broker.8shinken.gz:33

so I guess this is OK


But then I tried to install and I got this output :

steph@mirage:~/projects/debian/build-area$ sudo dpkg -i
shinken-core_0.6.4-1_all.deb
(Lecture de la base de données... 202300 fichiers et répertoires déjà
installés.)
Préparation du remplacement de shinken-core 0.6.4-1 (en utilisant
shinken-core_0.6.4-1_all.deb) ...
Dépaquetage de la mise à jour de shinken-core ...
Paramétrage de shinken-core (0.6.4-1) ...
usage: update-rc.d [-n] [-f] basename remove
   update-rc.d [-n] basename defaults [NN | SS KK]
   update-rc.d [-n] basename start|stop NN runlvl [runlvl] [...] .
   update-rc.d [-n] basename disable|enable [S|2|3|4|5]
-n: not really
-f: force

The disable|enable API is not stable and might change in the future.
dpkg : erreur de traitement de shinken-core (--install) :
 le sous-processus script post-installation installé a retourné une
erreur de sortie d'état 1
Des erreurs ont été rencontrées pendant l'exécution :
 shinken-core

I patched the debian files (defaults instead of default for update-rc.d)

and then dpkg -i shinken-*.deb works perfectly

You can find the commits here :
git://github.com/phantez/shinken.git

But then I tried to start the process and I got this :

root@mirage:/etc/init.d# ./shinken start
cd: 105: can't cd to
/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
Starting scheduler:
FAILED: did not found scheduler file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-scheduler)
; are you sure shinken-scheduler is installed ? ... failed!
 failed!
Starting poller:
FAILED: did not found poller file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-poller)
; are you sure shinken-poller is installed ? ... failed!
 failed!
Starting reactionner:
FAILED: did not found reactionner file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-reactionner)
; are you sure shinken-reactionner is installed ? ... failed!
 failed!
Starting broker:
FAILED: did not found broker file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-broker)
; are you sure shinken-broker is installed ? ... failed!
 failed!
Starting receiver:
FAILED: did not found receiver file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-receiver)
; are you sure shinken-receiver is installed ? ... failed!
 failed!
Starting arbiter:
cd: 414: can't cd to
/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
FAILED: did not found arbiter file
(/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin/shinken-arbiter)
; are you sure shinken-arbiter is installed ? ... failed!
 failed!

I haven't time to go deeper in init.d script but obviously sthg went
wrong :).


BTW, Do you think you will join the PAPT team as this is a Python
application ? But this means you will have to use SVN.

Again thank you for your work.

--
Stéphan Gorget



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ddd1eb0.2010...@gmail.com



Bug#599073: shinken : Some hardcoded string might have to be changed

2011-05-25 Thread Stéphan Gorget
I might have miss something because during the building process the
following files were hardcoded with
/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp

To solve this I changed :

$ cat /etc/default/shinken
...
## These vars will overRide the hardcoded ones in init script
ETC=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/etc/shinken
VAR=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
BIN=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/bin
...

changed into  :

## These vars will overRide the hardcoded ones in init script
ETC=/etc/shinken
VAR=/var/lib/shinken
BIN=/usr/bin

and the same for the following files :

brokerd.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
brokerd-windows.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
pollerd.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
pollerd-windows.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
reactionnerd.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
receiverd.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
receiverd-windows.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
resource.cfg:$USER1$=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/usr/lib/nagios/plugins
schedulerd.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken
schedulerd-windows.ini:workdir=/home/steph/projects/debian/build-area/shinken-0.6.4/debian/tmp/var/lib/shinken

and then it works  !

$ sudo /etc/init.d/shinken start
Starting scheduler:
.
Starting poller:
.
Starting reactionner:
.
Starting broker:
.
Starting receiver:
.
Starting arbiter:
.

--
Stéphan Gorget



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ddd452b.9040...@gmail.com



Bug#584769: RFS: clustershell

2010-06-08 Thread Stéphan Gorget
On 07/06/2010 13:42, Lucas Nussbaum wrote:
 On 07/06/10 at 13:13 +0200, Stéphan Gorget wrote:
 On Mon, Jun 7, 2010 at 11:09 AM, Lucas Nussbaum 
 lu...@lucas-nussbaum.netwrote:

 (Please Cc me on replies, I don't follow -mentors@ very closely).

 First question: why do we need yet another parallel command execution
 tool? Why is it better than pdsh, dsh, dish, fabric, capistrano,
 taktuk+kanif, etc? I'm not arguing that it is not better, but we have so
 many of those that it would make sense to elaborate a bit.

 Clustershell is a tool like dsh or pdsh but it also provides a python API.
 It is used by lustre-shine[1]
 
 So your plan is to also package lustre-shine? Have you gotten in touch
 with the Lustre packaging team, then?

I do not intend to package lustre-shine for now, as I am only using
clustershell and not lustre-shine.

 
 and it can also be used to script actions on a cluster.

 [1] lustre-shine (https://sourceforge.net/apps/trac/lustre-shine/) is a
 command
  line tool designed to setup and manage the Lustre file system on a cluster.

 On 06/06/10 at 23:37 +0200, Stéphan Gorget wrote:
 Dear mentors,

 I am looking for a sponsor for my package clustershell.

 * Package name: clustershell
   Version : 1.2.83
   Upstream Author : Stephane Thiell stephane.thi...@cea.fr
 * URL : https://sourceforge.net/projects/clustershell/
 * License : CeCILL-C
   Programming Lang: Python

 It builds these binary packages:
 clustershell - An event-based Python library to execute commands on
 distant cluster nodes

 Description: An event-based Python library to execute commands on local
 or distant cluster nodes in parallel depending on the selected
 engine and worker mechanisms.
 .
 The library provides also advanced nodeset handling methods. Its goal
 is to improve the administration of cluster by providing a lightweight
 but scalable API for developers.
 .
 Example : clush -w node[001-256] hostname
 or clush -w node[001-256] apt-get update|clubak -c

 That's not how Description: works. first line is supposed to be a 1-line
 summary. And I don't think that it's a place for providing documentation
 (or examples).



 A better description would maybe be :
 Description : Distributed shell that provides an efficient python interface
  Event-based Python library to execute commands on local or distant
  cluster nodes in parallel depending on the selected engine and
  worker mechanisms.
  .
  The library provides also advanced nodeset handling methods. Its goal
  is to improve the administration of cluster by providing a lightweight
  but scalable API for developers.
 
 This doesn't explain what makes the interface efficient.
 
 In any case, I would recommend getting in touch with either pkg-lustre
 (http://pkg-lustre.alioth.debian.org/) or the PAPT team
 (http://wiki.debian.org/Teams/PythonAppsPackagingTeam). I'm not
 qualified myself to sponsor python stuff.

I am in contact with PAPT team and hope they will be able to review the
package.

 
   Lucas

Thank you,

Stéphan



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c0e3600.6070...@gmail.com



Bug#584769: RFS: clustershell

2010-06-07 Thread Stéphan Gorget
On Mon, Jun 7, 2010 at 11:09 AM, Lucas Nussbaum lu...@lucas-nussbaum.netwrote:

 (Please Cc me on replies, I don't follow -mentors@ very closely).

 First question: why do we need yet another parallel command execution
 tool? Why is it better than pdsh, dsh, dish, fabric, capistrano,
 taktuk+kanif, etc? I'm not arguing that it is not better, but we have so
 many of those that it would make sense to elaborate a bit.

 Clustershell is a tool like dsh or pdsh but it also provides a python API.
It is used by lustre-shine[1] and it can also be used to script actions on a
cluster.

[1] lustre-shine (https://sourceforge.net/apps/trac/lustre-shine/) is a
command
 line tool designed to setup and manage the Lustre file system on a cluster.


 On 06/06/10 at 23:37 +0200, Stéphan Gorget wrote:
  Dear mentors,
 
  I am looking for a sponsor for my package clustershell.
 
  * Package name: clustershell
Version : 1.2.83
Upstream Author : Stephane Thiell stephane.thi...@cea.fr
  * URL : https://sourceforge.net/projects/clustershell/
  * License : CeCILL-C
Programming Lang: Python
 
  It builds these binary packages:
  clustershell - An event-based Python library to execute commands on
  distant cluster nodes
 
  Description: An event-based Python library to execute commands on local
  or distant cluster nodes in parallel depending on the selected
  engine and worker mechanisms.
  .
  The library provides also advanced nodeset handling methods. Its goal
  is to improve the administration of cluster by providing a lightweight
  but scalable API for developers.
  .
  Example : clush -w node[001-256] hostname
  or clush -w node[001-256] apt-get update|clubak -c

 That's not how Description: works. first line is supposed to be a 1-line
 summary. And I don't think that it's a place for providing documentation
 (or examples).



A better description would maybe be :
Description : Distributed shell that provides an efficient python interface
 Event-based Python library to execute commands on local or distant
 cluster nodes in parallel depending on the selected engine and
 worker mechanisms.
 .
 The library provides also advanced nodeset handling methods. Its goal
 is to improve the administration of cluster by providing a lightweight
 but scalable API for developers.


 --
 | Lucas Nussbaum
 | lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
 | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |




-- 
Stéphan Gorget


Bug#584770: ITP: clustershell -- An event-based python library to execute commands on local or distant cluster nodes in parallel

2010-06-06 Thread Stéphan Gorget
Package: wnpp
Severity: wishlist
Owner: stephan gorget phan...@gmail.com


* Package name: clustershell
  Version : 1.2.83
  Upstream Author : Stephane Thiell stephane.thi...@cea.fr
* URL : https://sourceforge.net/projects/clustershell/
* License : CeCILL
  Programming Lang: Python
  Description : An event-based Python library to execute commands on
local or distant cluster nodes in parallel depending on the selected
engine and worker mechanisms.

The library provides also advanced nodeset handling methods. Its goal is
to improve the administration of cluster by providing a lightweight but
scalable API for developers.

Example : clush -w node[001-256] hostname
or clush -w node[001-256] apt-get update|clubak -c



-- 
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c0b9d1e.7090...@gmail.com