Re: Bug#631769: [Debconf-devel] Bug#631769: New Kde frontend based on debconf-kde-helper
On Thu, Jun 30, 2011 at 02:03:56AM +0300, Modestas Vainius wrote:
> I pushed my changes to the debconf.git close on wagner [1], branch debconf-
> kde. Could you review and merge changes?
Sorry for dropping this on the floor for so long! I've reviewed this
and tested it on a Debian KDE stretch system, and I see no major
problems, so I've rebased and merged it.
The only substantive changes I made were to silence the rather noisy
debugging output from debconf-kde-helper (using QT_LOGGING_RULES) unless
DEBCONF_DEBUG=kde is set, and to make the Kde frontend fall back to the
Qt frontend.
> Notably, I renamed old Kde frontend to Qt (3ae06bf). Sune asked me to keep old
> frontend for now as he might try to keep qt4-perl alive. However, I think
> there is a consensus that debconf-kde-helper based one is the future so maybe
> we will get rid of that old frontend regardless in the end. That's still to be
> decided.
It seems likely that we'll need to get rid of it relatively soon, but
I'd first like to make sure that the new one works properly in more than
trivial test situations. I've CCed the maintainers of debconf-kde and
the debian-qt-kde list - is that something you could test, please? Use
debconf 1.5.68 once it hits unstable shortly, and also make sure that
you aren't seeing warnings about falling back to the Qt frontend.
> Regarding the last commit (0a4843c - NEWS entry), Kde frontend will stop
> working for its users unless they install debconf-kde-helper. I don't see how
> we can avoid this breakage via dependencies thus I added a NEWS entry.
> Surprisingly, there was no NEWS file before so I don't know if you want to add
> it. So feel free to ignore that commit.
Nowadays, task-kde-desktop happens to pull debconf-kde-helper in via
apper, so most people probably have it; but we should probably
explicitly add it to the task.
--
Colin Watson [cjwatson@debian.org]
Reply to: