Ticket #141 (closed Defect: fixed)

Opened 13 years ago

Last modified 10 years ago

DEB: Notes for next package update

Reported by: silke Owned by: silke
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.0.5
Keywords: Cc: JuergeN
Complexity: 3 Area:


  • Delete the obsolete config files /etc/deepamehta/logging.properties and /etc/deepamehat/config.properties

Change History

comment:1 Changed 13 years ago by silke

  • Status changed from new to accepted

comment:2 Changed 13 years ago by JuergeN

Update went fine. No errors were reported. But then I wanted to start DeepaMehta and got this message:

~$ sudo /home/jpn# /etc/init.d/deepamehta start
/usr/lib/deepamehta/deepamehta-daemon not found

so I checked it:

~$ file /usr/lib/deepamehta/deepamehta-daemon
/usr/lib/deepamehta/deepamehta-daemon: POSIX shell script text executable

and it was there. Then I checked permissions:

~$ ls -la /usr/lib/deepamehta/deepamehta-daemon
-rw-r--r-- 1 root root 145 2011-10-26 18:47 /usr/lib/deepamehta/deepamehta-daemon

and to run it, I guess it must be executable. So I

~$ sudo chmod 755 /usr/lib/deepamehta/deepamehta-daemon

and then DeepaMehta started again.

You need to make /usr/lib/deepamehta/deepamehta-daemon executable - must be 755.
I think the setting of permissions has to be done explicitly in general.

Also I had the notion that the logfiles were deleted during update, which they should not. But I am not completely sure about that.

comment:3 Changed 13 years ago by silke

Fixed permissions and delete old conf files. This raised a new question: At the moment *every* package update will move the database to the backup. Shouldn't this only occur if necessary? (So be careful: Upgrading to deepamehta - 4.0.5-1ubuntu3 will backup your data...)

comment:4 Changed 13 years ago by JuergeN

I upgraded to the latest version today. Update went fine, but now i am sure, that the logfiles are being deleted. This should only happen, when purging DeepaMehta with dpkg -P or a likewise apt based command. Not even sure, if other logfiles are removed when packages are just removed.

comment:5 Changed 13 years ago by silke

  • Status changed from accepted to closed
  • Resolution set to fixed

Ok, thanks! I saw you wrote this into #143, so I'll close this one.

comment:6 Changed 10 years ago by jri

  • Milestone Build .deb Package deleted

Milestone Build .deb Package deleted

Note: See TracTickets for help on using tickets.