Hi,

> I looked into it and after populating the database by hand and also fixing
> manually the initial issue [1]. It doesn't work anyway, the following
> errors appear:

> [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: 
include(bookmarks.tpl.php): failed to open stream: No such file or directory 
in /usr/share/php/SemanticScuttle/Model/Template.php on line 89
> [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: include(): 
Failed opening 'bookmarks.tpl.php' for inclusion 
(include_path='/etc/semanticscuttle/templates/default:/etc/semanticscuttle/templates/default:.:/usr/share/php:/usr/share/pear:/usr/share/php/SemanticScuttle/../')
 
in /usr/share/php/SemanticScuttle/Model/Template.php on line 89

> I wonder if this package have ever worked (looking at popcorn doesn't look
> like). At this stage, I prefer looking for a nicer replacement of
> scuttle/semanticscuttle. I doubt a NMU would have small changes, I would go
> with removing semanticscuttle from Wheezy.

I got it to work (that is, not throw obvious immediate errors) from a clean 
install by fixing three separate problems:

1) Initial issue reported in bug: "No default configuration file 
config.default.php found. This is really, really strange".
Fixed by creating a symlink from 
/usr/share/semanticscuttle/data/config.default.php to 
/usr/share/php/data/SemanticScuttle/

2) Database not populated. This is because the dbconfig-common file is named 
/usr/share/dbconfig-common/data/semanticscuttle/install/tables.sql, while it 
should be named /usr/share/dbconfig-common/data/semanticscuttle/install/mysql.

3) Spews strict standards errors to the browser. Fixed by setting $debugMode 
to false in /etc/semanticscuttle/config.php.

After fixing these three errors I didn't see any immediate (!) errors anymore.

So while I think each one of those could be fixed by a one or few lines change 
in the packaging, it's more that the package was apparently in wheezy for over 
a year in this state, with these three rather orthogonal but immediately 
obvious errors. This, combined with the fact that semanticscuttle was never in 
a stable release and the maintainer has agreed already with removal from 
wheezy as an option, leads me to the conclusion that removal from wheezy is 
the best option at this point.

Hence, I'm filing a removal request with the release team.


Cheers,
Thijs

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to