Your message dated Thu, 20 Jul 2006 15:23:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#378957: cofiguration file overwritten on upgrade
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libactiveldap-ruby1.8
Version: 0.7.4-1
Severity: minor
This package contains a file
/usr/lib/ruby/1.8/activeldap/configuration.rb which is customizable
for the particular LDAP criteria for a location. Upon upgrade, any
changes made to that file are overwritten without the customary apt
warnings. This can lead to some bad headaches for developers who
clumsily upgrade the package.
Suggested fix: tweak the package so that the file is marked as a
configuration file which triggers prompting by apt/debconf upon
upgrade if changes have been made to the old version.
just a minor thing, though.
Aaron
--
Aaron Dulles-Coelho
Engineering IT Consultant
Cornell University
Tel: (210) 347 1423
--- End Message ---
--- Begin Message ---
Coin,
"Aaron Dulles-Coelho" <[EMAIL PROTECTED]> writes:
> This package contains a file
> /usr/lib/ruby/1.8/activeldap/configuration.rb which is customizable
> for the particular LDAP criteria for a location. Upon upgrade, any
> changes made to that file are overwritten without the customary apt
> warnings. This can lead to some bad headaches for developers who
> clumsily upgrade the package.
No, there is absolutly no bug, you just don't understand how this works.
The file you're modifying contains the *default* parameters, which are
defined as values used in most common configurations by upstream
authors. This is an arbitrary choice which has not to be modified,
because this would change the software behavior, like doing a fork
(leading to being unable to run your application on another box with
another location parameters).
Parameters must be setup *per application* this way :
ActiveLDAP::Base.connect(
:host => 'ldap.mydom.org',
:port => 389,
:base => 'dc=mydom,dc=org',
:bind_format => "uid=%s,ou=Users,dc=mydom,dc=org",
:user => 'myuser',
:password_block => Proc.new { 'mypasswd' },
:logger => logger,
:allow_anonymous => false,
:try_sasl => false
)
--
Marc Dequènes (Duck)
pgp8nj2OeOARU.pgp
Description: PGP signature
--- End Message ---
