Hi Antoine,

I've noticed that the package creates a database but doesn't populate it nor
gives user's credentials. So the problem may start here:

The following NEW packages will be installed:
  semanticscuttle
0 upgraded, 1 newly installed, 0 to remove and 498 not upgraded.
Need to get 0 B/614 kB of archives.
After this operation, 2,771 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package semanticscuttle.
(Reading database ... 42800 files and directories currently installed.)
Unpacking semanticscuttle (from .../semanticscuttle_0.98.4+dfsg-1_all.deb) ...
Setting up semanticscuttle (0.98.4+dfsg-1) ...
dbconfig-common: writing config to /etc/dbconfig-common/semanticscuttle.conf

Creating config file /etc/dbconfig-common/semanticscuttle.conf with new version

Creating config file /etc/semanticscuttle/database.php with new version
granting access to database semanticscuttle for semanticscuttle@localhost: 
success.
verifying access for semanticscuttle@localhost: success.
creating database semanticscuttle: success.
verifying database semanticscuttle exists: success.
dbconfig-common: flushing administrative password
vps:/home/tiago# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 19006
Server version: 5.1.61-0+squeeze1 (Debian)

Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> use semanticscuttle;
Database changed
mysql> show tables;
Empty set (0.00 sec)

mysql> 

There may be something wrong with config/post-install scripts.

The original reported issue related to config file can be easly fixed by
linking /usr/share/semanticscuttle/data/config.default.php to
/usr/share/php/data/SemanticScuttle/config.default.php in your debian/.links
file.

After manually populating database I got it working but didn't play enough to
say if it's really doing the job.

Btw, it would be nice if you had a HEAD refering to a master branch in the
git repository, so you can avoid this:

warning: remote HEAD refers to nonexistent ref, unable to checkout.

Regards,

-- 
--------------------------------------------------------------------------------
  .''`.  Tiago Bortoletto Vaz                         GPG  :      1024D/A504FECA
 : :' :  http://tiagovaz.org                          XMPP : tiago at jabber.org
 `. `'   tiago at {tiagovaz,debian}.org               IRC  :       tiago at OFTC
   `-    Debian GNU/Linux - The Universal OS               http://www.debian.org
--------------------------------------------------------------------------------



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to