Your message dated Wed, 25 Sep 2013 18:53:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#724491: localepurge: "debconf-communicate
-fnoninteractive localepurge" does not work
has caused the Debian Bug report #724491,
regarding localepurge: "debconf-communicate -fnoninteractive localepurge" does
not work
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 [email protected]
immediately.)
--
724491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724491
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: localepurge
Version: 0.7.3
Severity: normal
Dear Maintainer,
After upgrading to localepurge 0.7.3, the following commands do not work:
=========================
debconf-communicate -fnoninteractive localepurge <<EOF
set localepurge/nopurge ca_ES.UTF-8, de_DE.UTF-8
fset localepurge/nopurge seen true
EOF
dpkg-reconfigure --priority=low --unseen-only localepurge
=========================
Before I run this script,
Running:
grep -A3 localepurge/nopurge /var/cache/debconf/config.dat
shows me:
=========================
Name: localepurge/nopurge
Template: localepurge/nopurge
Value: en, en_US.UTF-8
Owners: localepurge
Flags: seen
=========================
Now after I run that script, then following command:
grep -A3 localepurge/nopurge /var/cache/debconf/config.dat
still shows me:
=========================
Name: localepurge/nopurge
Template: localepurge/nopurge
Value: en, en_US.UTF-8
Owners: localepurge
Flags: seen
=========================
I expect it should be changed as
Value: ca_ES.UTF-8, de_DE.UTF-8
However, if I downgrade localepurge to 0.6.3, this issue is gone.
Did I miss something for the new version of localepurge?
Thanks.
Steven.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.10-3-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages localepurge depends on:
ii debconf [debconf-2.0] 1.5.51
ii locales 2.17-93
ii procps 1:3.3.8-2
ii ucf 3.0027+nmu1
localepurge recommends no packages.
Versions of packages localepurge suggests:
pn bleachbit <none>
pn debfoster <none>
pn deborphan <none>
-- debconf information:
localepurge/none_selected: false
localepurge/mandelete: true
localepurge/showfreedspace: true
* localepurge/nopurge: en, en_US.UTF-8
* localepurge/use-dpkg-feature: false
localepurge/dontbothernew: false
localepurge/remove_no:
localepurge/verbose: false
localepurge/quickndirtycalc: true
--- End Message ---
--- Begin Message ---
On 2013-09-25 09:23, Steven Shiau wrote:
>
>
> On 09/25/2013 02:46 PM, Niels Thykier wrote:
>> Mmm, honestly I have never done much of that so I can only be of limited
>> help here. By the looks of it though, it seems that you should use
>> debconf-set-selections. Apparently, debconf-communicate is for
>> "debugging"-purposes. Note that debconf-det-selections does seem to use
>> a slightly different format (and defaults to marking things as "seen").
> Hi Niels,
> Cool! Thanks for telling me to use debconf-set-selections. It works
> well. Awesome!
> By doing this:
> debconf-set-selections <<EOF
> [...]
> EOF
>
> I can preseed the localepurge.
> Appreciate! Thank you very much!
>
> Steven.
>
Hi,
Glad to hear it all works for you know. For the record, I have taken
the liberty of closing this ticket (you should get a mail about the mail
being marked as "done")
~Niels
--- End Message ---
