Hi,
I have updated gbrowse to move "db" related data to /var/lib instead of
/usr/share
I removed call to metadb_config script and updated config to disable
user management by default (in fact I think it is best for default install).
I made a few updates too for the gbrowse_slave where a restart is
required at gbrowse-data install.
To test it, please reload patches as I updated them.
Olivier
Le 4/11/11 9:33 AM, Olivier Sallou a écrit :
Hi Charles,
the script metadb is used for the "user management". It creates a new
"database" (sqlite) if not already created. It is required for some actions enabled by
default at install.
I think we can remove it from post-install however. User can still execute it
if required.
Olivier
----- Mail original -----
De: "Charles Plessy"<ple...@debian.org>
À: "Olivier Sallou"<olivier.sal...@irisa.fr>, debian-med@lists.debian.org
Envoyé: Dimanche 10 Avril 2011 13:28:04
Objet: Uploading GBrowse to experimental ?
Dear Olivier,
as you probably have seen on the commit mailing list, I have made a
couple of
changes to the gbrowse package. The goal of many of them was to make
the build
process more simple according to the common practices in Debian. I
hope that
you are not offended that I undid some of your work, just to redo it
“our way”.
I think that it will help other members of the Debian Med team to
contribute.
My main problem is the postinst script that calls
/usr/bin/gbrowse_metadb_config, as I do not understand well that this
script is
doing exactly. It looks like it creates and deletes directories under
/usr and
/var. I think that it is difficult to justify, as these directories
may belong
to the package itself. Indeed, gbrowse fails to be installed twice in
a row
when this script is enabled. Since it does not look necessary to at
least run
the examples, I disabled it for the moment. Similarly, GBrowse seems
to create
some files or directory under /usr at run time. This is also something
that
we will have to correct.
This said, I do not want to postpone the upload of the package ad
vitam aeternam.
How about uploading it to the experimental section of our archive ?
Then we
can keep on working on the issues above, and the proper setup of the
render farm.
In the past, Upstream has been very suppportive and if we have GBrowse
in
experimental, I think that they will be very motivated to help us by
adding
some flexibility in GBrowse where needed.
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
--
gpg key id: 4096R/326D8438 (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4da4441a.4080...@irisa.fr
