DEB: debian packege needs some updates - missed some changes

[JuergeN]

Today I did some testing of the debian package again and I discovered some errors which seem to be a result of the fact, that some of the latest changes did not make it into the package finally.

1. /usr/lib/deepamehta/conf - obsolete, please remove from package.
2. /var/log/deepamehta - needs to be chown -R deepamehta:deepamehta
3. /etc/deepamehta/* - files are executeble. This comes from the sources, I think.
4. /etc/deepamehta/logging.properties - wrong settings, no file logging.

[silke]

WHAT!?!?!? Oh no!

[JuergeN]

I have done some editing of the config files. Maybe you want to use those for your package instead:

config.properties

# --------------------------------------
# Main configuration file for DeepaMehta
# --------------------------------------
 
# HTTP port setting: (default is 8080)
org.osgi.service.http.port = 8080

# The file repository's root directory: An absolute path with *no* slash at the end.
# To enable the entire file system specify an empty string (instead of "/"). 
# This is only recommended in a desktop installation on your private computer.
dm4.proxy.files.path = /var/lib/deepamehta/deepamehta-filedir

# Remote access filter: an address range specified by network number and netmask.
# To allow only local access specify "127.0.0.1/32". This is the default.
dm4.proxy.net.filter = 127.0.0.1/32

# -------------------------------------------------------------------------------
# No changes beyond this line, please, unless you really know what you are doing.
# -------------------------------------------------------------------------------

# Path to bundle cache: (Make sure DeepaMehta has write access!)
org.osgi.framework.storage = /var/cache/deepamehta/bundle-cache

# Some felix settings:
felix.log.level = 1
felix.auto.deploy.action = install,start

# Path to database: (Make sure DeepaMehta has write access!)
dm4.database.path    = /var/lib/deepamehta/deepamehta-db

# Path to logging config file:
java.util.logging.config.file = /etc/deepamehta/logging.properties

# Encoding:
file.encoding = UTF-8

logging.properties

# FILE LOGGING
handlers = java.util.logging.FileHandler
java.util.logging.FileHandler.level = ALL
java.util.logging.FileHandler.pattern = /var/log/deepamehta/deepamehta.log
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.FileHandler.append = true

# You can also log to console and file at the same time. 
# Just define both handlers in one "handlers" line, separated by whitespace or comma.
# You should keep console logging disabled, when running in daemon mode.

# CONSOLE LOGGING
# handlers = java.util.logging.ConsoleHandler
# java.util.logging.ConsoleHandler.level = ALL

# GLOBAL LOG LEVEL
# Use of one of these values:
#     WARNING - high level, sparse logging
#     INFO    - mid level, the default
#     FINE    - lower level, verbose logging
# Enabling logging at a given level also enables logging at all higher levels.
# Their are two additional levels:
#     ALL     - logging all messages
#     OFF     - turn off logging
# Do not miss the dot at the beginning of the line. 
# (default: .level = INFO)
.level = INFO

# PER-CLASS LOG LEVELS
# State the fully qualified class name and add ".level", e.g.:
# de.deepamehta.core.impl.service.EmbeddedService.level = WARNING
# de.deepamehta.plugins.accesscontrol.AccessControlPlugin.level = FINE
# de.deepamehta.plugins.workspaces.WorkspacesPlugin.level = OFF

[silke]

Thanks for testing and reporting, JuergeN! I'll fix this as soon as possible.

Some first notes:

The first problem comes from the .install file in the debian directory:

bin/* /usr/lib/deepamehta                                                           
bin/conf/* /etc/deepamehta

Obviously bin/conf is part of bin/*... I'll find out if I can just change the order of the two lines or if further "action" is required.

The second problem should not have occured. The postinst script had a case ("configure") in which chown -R deepamehta:deepamehta /var/log/deepamehta is executed. I wonder if the script was executed or if the file's syntax was wrong. This was what it looked like.

 chown -R deepamehta:deepamehta /var/lib/deepamehta \
    /var/cache/deepamehta \
    /var/log/deepamehta \
    /var/run/deepamehta

I changed it into single lines each calling the whole chown stuff.

To solve the third problem, I'll put

chmod 644 /etc/deepamehta/*

into debian/postinst.

The fourth problem must have been an error that occured to me while copying files. We talked about it - time for a script!

[silke]

Ok, I uploaded the bugfix to launchpad, but I'm afraid, it's waiting in the queue to be built in about 24 hours only...

[silke]

It's online, ready for further testing! ;-)

[jri]

Milestone Build .deb Package deleted