Hello all,
although package Docky was lot of work for me (licensing patching etc) I
am no longer using it and last two releases were very unstable. There
are couple of bugzillas reported mainly because of gconf migration.
"""
Docky is an advanced shortcut bar that sits at the edges of your screen.
It provides easy access to some of the files, folders and applications
on your computer, displays which applications are currently running,
holds windows in their minimized state and more.
Docky is written in mono.
http://wiki.go-docky.com
"""
Please ping me if you are interested to maintain the package.
--
Later,
Lukas "lzap" Zapletal
#katello #systemengine

Hi
Because I need more concentration on fewer packages,
here is a list of packages I'm orphaning,
some might end deprecated at some point
One the same line are package linked together.
cinepaint (can be built without oyranos)
directfb tslib
libproxy (critical path) libmodman
oyranos icc_examin elektra
fmtools
makehuman animorph mhgui
libmpcdec
jrosetta matio
perl\* (see pkgdb)
Please add yourself as maintainer.
Nicolas (kwizart)

Hi,
PHP opcode cache is a very important feature for sites with large traffic.
APC is mostly a dead project.
No stable release for php 5.4, lot of issues.
Upstream move most of dev resources to new "Zend OPcache" which will be
the official opcode cache, integrated in PHP 5.5.0
To be able to drop this package, we need
1/ php-pecl-zendopcache, the Zend OPcache for php 5.3 / 5.4
https://bugzilla.redhat.com/show_bug.cgi?id=911111
Target version is EPEL-6 and Fedora <= 18 as Fedora >= 19 already have
php-opcache (subpackage of main php, same code)
2/ php-pecl-apcu, APCu, the drop-in replacement of APC for user data cache.
https://bugzilla.redhat.com/show_bug.cgi?id=928196
Target versions : Fedora >= 18 and EPEL-6
Please, review this.
Remi.

There still seems to be an issue with the update descriptions that we
present in PackageKit. A lot of people just write "update to version
x.y.z" which is not great, but a whole lot better than some of the ones
we've been seeing recently. For example, from two updates I got today:
* "Not tested locally yet, I need to spin back up a Fedora 18 VM."
* "Here is where you give an explanation of your update."
Now the first one is obviously a one-off mistake, but had the update
been checked over just once it would have been caught. The placeholder
one is a big recurring problem, though: it seems to show up at least
every week or so, which is not OK.
And once, about two months ago -- I really should have complained then
and not now -- an update was pushed where the text displayed in
PackageKit was something along the lines of "why do I have to describe
my update here when I've already filled out the RPM changelog." I wish
it was a joke, but something like that was actually pushed as the
description of a F18 update presented to every user who glances over the
updates....
We need written policy on update descriptions, since despite the last
discussion on this list [1], poor update descriptions continue to
blemish the otherwise-professional image of the distro. A starting point
suggestion: "Every update should have at least a one sentence
description." If the update is not worth writing one sentence about, it
is not worth pushing out.
Happy Friday,
Michael Catanzaro
[1]
https://lists.fedoraproject.org/pipermail/devel/2013-March/179655.html

Hi,
It is taking a bit too long for some dependencies to be rebuilt
in rawhide.
Could a compat-libgd be provided please? I am receiving daily
mails about broken deps, already posted to $pkg-owner@ asking
what I could help, but still no response neither problems corrected.
Remi Collet told me it appears there are some FTBFS packages in
the cycle.
I would like to also start working on packaging sagemath 5.10,
but am not providing as much time to work on fedora as I would
want, so also not providing a compat-libgd sample package,
sorry...
Thanks,
Paulo