We're trying to retire package eclipse-wtp-common on F21 and Rawhide. My
understanding is that this should be done F21 first, then Rawhide. F21
has proven problematic so far.
Bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=1117475
1. Package eclipse-wtp-common is obsoleted/provided by eclipse-webtools
2. A package "administrator" (note: not owner), tries to use fedpkg to
retire, but it fails: Performs dead.package commit, then can't change
point of contact to orphan in the second part of that process.
3. Proven packager comes to help; tries to retire, gets message "You are
not allowed to retire this package."
4. Package owner comes along, tries to retire. Get's a little further in
that the package is now orphan for that branch, but then gets message:
"You are not allowed to retire the package: eclipse-wtp-common on branch
Is there something additional that we need to do, or is there something
in the above sequence of events that has screwed things up? Or is F21 in
some state that is preventing package retirement? Or is it something else?
Thanks in advance for any help that any of you can provide!
WG meeting will be at 13:00 UTC (14:00 London, 15:00 Brno, 9:00 Boston,
22:00 Tokyo) in #fedora-meeting on Freenode.
= Topic =
* [RFE] Teach COPR build layered Docker images - discussed on Copr
mailing list. Some follow up?
* anything new with rpmgrill?
As upstream didn't seriously consider the API breakage, json
0.11->0.12 brings an issue of one function which is deprecated from
now on. This has caused bug 1123785 so I will bump the soname
However, some don't use json_tokener_errors() in the code, for example
zmap, is not affected, so there are some false positives here. Please
rebuild your package on f21+ branches. I've unpushed the update of
json-c on elder branches.
My name is Japheth Cleaver.
I've been using Fedora (and RHL) since the early 2000's at a number of
smaller regional ISPs, and RHEL or CentOS regularly for about the last 10
years. I'm primarily involved in monitoring systems and operational
engineering at ServiceNow, where I've been at for the past several years.
My first BZ seems to have been back in 2004 (BZ#130288) and involved some
device name issues.
I've been building RPMs for internal use for at least that long, but I
feel like I'd like to begin to take a more active contributor in helping
Fedora as a project itself. I'm seeking a sponsor who would be willing to
help me through this process.
My first official package for submission is: nanomsg, a new socket library
from the authorship of ZeroMQ, which seemed to be missing from Fedora
despite its apparent growing popularity:
I'm looking forward to helping out more directly with Fedora in the future!
Japheth "J.C." Cleaver