Greetings.
Long ago I used to use dircproxy and took over maintaining the Fedora
pacakge of it.
However, many years ago I moved to znc, and no longer use dircproxy.
Upstream is pretty much dead (no commits in 5 years or so).
There's currently one outstanding fedora bug (to drop the sysvinit
file).
Accordingly I have orphaned the package.
If someone has need to keep it alive, feel free to take it.
kevin

To save anyone else doing the same detective work I did, which I
subsequently discovered Lukas Slebodnik had already done:
sssd-client in Rawhide needs rebuilding - the lack of a rebuild is
causing various issues. A rebuild was tried, but it failed:
http://koji.fedoraproject.org/koji/buildinfo?buildID=602291
the failure turns out to be caused by a Samba problem:
https://bugzilla.samba.org/show_bug.cgi?id=11033
that's all been filed appropriately, so I guess we'd expect a fix to
come downstream from Samba soon and then sssd can be rebuilt for
Rawhide.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

Hi,
does someone know about the status of maintainer odysseus?
His package zukitwo-themes isn't update to GTK3-3.14.x.
Upstream updated to gtk3-3.14x since october 2014.
Cinnamon desktop are waiting for an update, see fesco ticket
https://fedorahosted.org/fesco/ticket/1381
Please send him an email if you know other email adresses than fedora one.
Wolfgang

Hello list,
upstream (Lasse Collin), _thanks a lot_ BTW, was able to cut new xz
(stable) release 5.2.0. I rather write here to inform you about upcoming
rebase in Fedora Rawhide (tomorrow or day after) as there is quite a few
dependant packages..
There shouldn't be a need to rebuild huge amount of packages as the soname
was not bumped and the API upgrade is clean. There are small nits but the
rebase should be pretty safe (for more info/discussion, look at #1023718
and stop me there possibly).
I also plan to remove old "xz-compat-libs" subpackage in near future,
which, IIRC, is not used at all currently. Stop this initiative in bug
#1179193 if you feel it is not OK.
Pavel

Hi!
Summary: Try to prevent a package from being updated/installed from
repositories regardless of the package management tool you use. As it
seems, then only way you can do this is to exclude it from the
repositories themselves inside their configuration file in
/etc/yum.repos.d/, because these are the only common settings between
all three (yum/dnf/PackageKit). TBH, I'm not sure about PackageKit, but
I feel that it don't read /etc/dnf/dnf.conf as it doesn't use DNF but
its backends. This is fine if the package is in a single known
repository, but what if it is in 3 repositories that you might not be
aware of all of them?
More details:
As you might already know, nvidia drivers in RPMFusion F21 repositories
doesn't work for all nvidia cards. In one system, I finally installed
akmod-nvidia from RPMFusion F20 repositories which worked fine. Soon
after I realized that I should exclude akmod-nvidia and dependencies
from F21 repositories. I added "exclude=*nvidia*" to /etc/yum.conf as I
was lazy to check which repository these packages come from. But then I
noticed that dnf doesn't consider it excluded. Then I thought that
probably PackageKit doesn't use dnf.conf too. So, how should I excluded
these packages? Well, these were in rpmfusion-nonfree-updates
repository, so I added the exclude directive there. Then I found that I
should add it to rpmfusion-nonfree repository too. However, since I use
yum-plugin-local I also have a local repository (I actually copied the
repository from another system, so it was enabled on this system so that
I could install software from it) which also included these packages.
Therefore, I should exclude "*nvidia*" in 3 repository configuration
files to make sure (hopefully!) that these will not be installed by any
package manager I know.
Suggestion: Please add a single configuration file to configure common
package manager options (Specially between DNF and PackageKit, which are
there to stay). As I mentioned in "F21 downloads repository metadata in
3 places!" thread, Fedora package management should be consistent and
integrated; and the current situation is really frustrating. If I want
to exclude some packages, I should be able to do it once for all. If I
want to disable automatic download of metadata/packages, there should be
a single place where I can define my desired package management policy.
If I want to specify default metadata_expire timeout for all
repositories, there should be one place to do it. There really should be
a single package management policy that must be respected by every
package manager in Fedora, specially the main ones: DNF and PackageKit
(and currently Yum).
Regards,
Hedayat

Hi,
I've just orphaned python-psutil for rawhide, since none of my
packages require it anymore.
For potential packagers who'd like to take ownership of this package,
be careful when updating to latest major version which breaks API
(upstream: 2.1.3/fedora: 1.2.1); many packages depending on psutil may
need some patching/report upstream. You can find more details here:
http://grodola.blogspot.com/2014/01/psutil-20-porting.html
Regards,
Mohamed El Morabity