On Monday 29 of March 2010 09:30:38 Peter Volkov wrote: > В Вск, 28/03/2010 в 07:47 +0200, Maciej Mrozowski пишет: > > No, seriously - given the fact that some of my packages were even > > stabilized without contacting me (app-misc/hal-cups-utils, > > app-admin/system-config- printer-common) > > If you know packages are broken why they were not hardmasked? If they > have no problems what why it was bad idea to mark them stable?
They are not broken, they're just not suitable. It's like stabilizing gcc-2.95 now, even when it won't work with some recent KDE/boost. hal-cups-utils is not a problem system-config-printer-common-1.1.13 is as it's being used by maybe incompatible now system-config-printer-kde from testing arch (I've raised those deps now), besides I wanted to wait for polkit-1 with this package (otherwise dbus "newprinternotifications" can be received only by root or require tweaking dbus conf to work out of the box . That's why kde- base/system-config-printer-kde and kde-base/printer-applet were intentionally left out from KDE-4.3.3 stabilization list. -- regards MM
