Bug#481778: lynx-cur-wrapper: Does not preserve local changes to configuration

2008-06-23 Thread Atsuhito Kohda
On Sat, 21 Jun 2008 19:07:51 +0200, Andreas Metzler wrote:

 Hello,

Hi Andreas,

 afaict conffiles won't work since you build the configuration files in
 postinst using debconf inputs. You'd need to use some clever
 scripting, like ucf.

I guess if I keep them as configuration files, it needs 
only to check if a file exists or not before copying
configuration files and if I changed them as conffiles
I needs to check if they were changed or not with, for example,
md5sums and rmoved unmodified files in preinst (with 
version check).  ucf might be another option but I don't
understand your point of conffiles won't work.

 Do you think you will be able get lync-cur rc-bug-free and add a
 transition package for lynx in time for lenny?

I've concentrated on recent developement of Japanese TeX
these days (if you have interests in this, please visit
http://www1.pm.tokushima-u.ac.jp/~kohda/tex/ptexlive.en.html) 
so I don't take so much time for investigating this problem 
but I'll take time to fix this silly mistakes.

Regards,2008-6-23(Mon)

-- 
 Debian Developer - much more I18N of Debian
 Atsuhito Kohda kohda AT debian.org
 Department of Math., Univ. of Tokushima 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#481778: lynx-cur-wrapper: Does not preserve local changes to configuration

2008-06-23 Thread Andreas Metzler
On 2008-06-23 Atsuhito Kohda [EMAIL PROTECTED] wrote:
 On Sat, 21 Jun 2008 19:07:51 +0200, Andreas Metzler wrote:
[...]
  afaict conffiles won't work since you build the configuration files in
  postinst using debconf inputs. You'd need to use some clever
  scripting, like ucf.

 I guess if I keep them as configuration files, it needs 
 only to check if a file exists or not before copying
 configuration files and if I changed them as conffiles
 I needs to check if they were changed or not with, for example,
 md5sums and rmoved unmodified files in preinst (with 
 version check).  ucf might be another option but I don't
 understand your point of conffiles won't work.
[...]

Hello,
Probably just a misunderstanding. I use the term confile exclusively
for configuration files shipped directly in the .deb, where dpkg
itself takes care of not overwriting local customizations. Your
configuration file is not shipped in the .deb package but generated at
installation time using locally supplied input (default homepage).

*Imho* the default homepage debconf question is not worth the pain
it causes, requiring configuration file managment in maintainer
scripts. If it it was my package I would simply drop the debconf
thingy and go for dpkg conffiles. ;-)
cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#481778: lynx-cur-wrapper: Does not preserve local changes to configuration

2008-06-21 Thread Andreas Metzler
On 2008-05-29 Atsuhito Kohda [EMAIL PROTECTED] wrote:
 Hi Andreas,

 On Sun, 18 May 2008 15:31:28 +0200, Andreas Metzler wrote:

  Package: lynx-cur-wrapper
  Version: 2.8.7dev9-1
  Severity: serious
  Justification: Policy 10.7.3

 It seemed I forgot to reply to this report, sorry.
 I think I'll make the files as conffiles instead of
 configuration files at present but I need a bit more
 consideration.

Hello,

afaict conffiles won't work since you build the configuration files in
postinst using debconf inputs. You'd need to use some clever
scripting, like ucf.

Do you think you will be able get lync-cur rc-bug-free and add a
transition package for lynx in time for lenny?

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#481778: lynx-cur-wrapper: Does not preserve local changes to configuration

2008-05-29 Thread Atsuhito Kohda
Hi Andreas,

On Sun, 18 May 2008 15:31:28 +0200, Andreas Metzler wrote:

 Package: lynx-cur-wrapper
 Version: 2.8.7dev9-1
 Severity: serious
 Justification: Policy 10.7.3

It seemed I forgot to reply to this report, sorry.
I think I'll make the files as conffiles instead of
configuration files at present but I need a bit more
consideration.

Thanks for your report.
Regards,2008-5-29(Thu)

-- 
 Debian Developer - much more I18N of Debian
 Atsuhito Kohda kohda AT debian.org
 Department of Math., Univ. of Tokushima



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#481778: lynx-cur-wrapper: Does not preserve local changes to configuration

2008-05-18 Thread Andreas Metzler
Package: lynx-cur-wrapper
Version: 2.8.7dev9-1
Severity: serious
Justification: Policy 10.7.3

---
(SID)[EMAIL PROTECTED]:/# apt-get --purge install lynx-cur-wrapper=2.8.7dev8-1
[...]
Setting up lynx-cur (2.8.7dev9-1) ...
Setting up lynx-cur-wrapper (2.8.7dev8-1) ...
(SID)[EMAIL PROTECTED]:/# echo '#locally modified'  /etc/lynx-cur/lynx-de.cfg
(SID)[EMAIL PROTECTED]:/# apt-get --purge install lynx-cur-wrapper=2.8.7dev9-1
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  lynx-cur-wrapper
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/15.3kB of archives.
After this operation, 0B of additional disk space will be used.
(Reading database ... 15850 files and directories currently installed.)
Preparing to replace lynx-cur-wrapper 2.8.7dev8-1 (using 
.../lynx-cur-wrapper_2.8.7dev9-1_all.deb) ...
Unpacking replacement lynx-cur-wrapper ...
Processing triggers for man-db ...
(SID)[EMAIL PROTECTED]:/# grep '#locally modified' \
  /etc/lynx-cur/lynx-de.cfg || echo not found
not found
---

cu andreas



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]