[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#102006: marked as done (oaf: .oaf and .oafinfo files should not be in /usr/share)

Your message dated Wed, 23 Apr 2008 01:39:29 +0100
with message-id <200804230039.m3N0dTui020791@kmos.homeip.net>
and subject line oaf has been removed from Debian, closing #102006
has caused the Debian Bug report #102006,
regarding oaf: .oaf and .oafinfo files should not be in /usr/share
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

102006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102006
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: oaf
Version: 0.6.5-5
Severity: wishlist

.oaf and .oafinfo files describe the location of binary component
factories that are not necessarily available for all architectures in
a given setup. i.e. if a central server is serving multiple clients of
various architectures, component C1 for architecture A1 may not be
available, yet the .oaf file for C1 is available to machines of A1
since they are in /usr/share which should be safely sharable among
clients of multiple architectures.
I propose moving .oaf files to /usr/lib/oaf.

Beside this bug report, I am also currently rallying on
gnome-components-list to have this fixed in upstream for GNOME 2.0.

--- End Message ---
--- Begin Message ---
Version: 0.6.10-9+rm

The oaf package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/470014 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Marco Rodrigues

--- End Message ---

Reply to: