Week passed since your upload into experimental.
Is it good time to go forward and upload into unstable?
Binary packages were built successfully on all supported architectures except
mips and sparc. They are still waiting for build. But as I observed packages
in experimental have the lowest priority and they can wait very long time.
As I see in  queues are quite big. But I am not sure that these
timestamps mean. This is not the time since upload. But also this is not the
estimate time before build, because I can compare timestamps for my packages
uploaded in different days.
In any case I see no reason to wait build on these two architectures. Program
does not have architecture-specific code and was build successfully on all
As for the tests I use this module on few machines since February without
any problems. Migration of config was implemented recently. Is any other
2012-06-08 11:29, Boris Pek wrote:
> Now package builds fine on kfreebsd-* and hurd-i386:
> And it should be no problems with linux-based environments on other supported
> architectures. So I have updated the package:
> kde-gtk-config (3:2.0-3) unstable; urgency=low
> * Package moved to unstable after tests: no changes required.
> * This package replaces src:kcm-gtk and closes its bugs:
> - fixed working on clean install (Closes: #631591)
> - added support of Gtk+ 3.x (LP: #734979)
> You could upload it when you decide it is ready.
> Direct link for download:
> And now I have questions about translations.
> 1) There are no translation files in the source tree.
> 2) Translations are available only in common svn repository of KDE project
> 1) Should I package them manually into separate package or they will be
> automatically in common package (like src:kde-l10n)?
> 2) If I should package them manually how to do this in comfortable way?
> I mean: select and copy them one by one from svn repository doesn't look
> good. It should be more common way.
> 3) If I should package them manually should I make the separate package
> kde-config-gtk-style-i18n or just add them into the same binary package?
> (Note: they will no weigh much)
> First part of message is only for sponsor of this package. But any suggestions
> and explanations for the second part of message are welcome.
> Best regards,
>  For example:
pkg-kde-extras mailing list