On Wed, Nov 27, 2013 at 18:25:31 -0800,
Adam Williamson wrote:
Misc: I haven't filed bureaucracy bugs for them yet, but we do still
need to make sure the final artwork, release notes, fedora-release (and
generic-release) and spin-kickstarts are all in place prior to ship.
spin-kickstarts-0.
On Thu, 2013-11-28 at 10:00 -0800, Adam Williamson wrote:
> If something is FTBFS there ought to be a bug report for it - have you
> attached the patch there? Thanks!
Yep. There's a FTBFS bug report and I've attached the updated spec with
required changes to it.
https://bugzilla.redhat.com/show_b
On Thu, 2013-11-28 at 18:15 +1100, Ankur Sinha wrote:
> On Thu, 2013-11-28 at 12:10 +0800, Christopher Meng wrote:
> > ncmpcpp in
> > Fedora is in FTBFS status.
>
> Updated spec with fix attached. It's just the new unversioned package
> doc dir change.
If something is FTBFS there ought to be a b
On Thu, 2013-11-28 at 15:18 +0800, Christopher Meng wrote:
> Yes, but we still need to wait for the irresponsive maintainer
> maybe...
A proven packager could apply the update in time being. I'll try to get
in touch with the maintainer to request co-maintainership of the package
since I use it on
Yes, but we still need to wait for the irresponsive maintainer maybe...
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On Thu, 2013-11-28 at 12:10 +0800, Christopher Meng wrote:
> ncmpcpp in
> Fedora is in FTBFS status.
Updated spec with fix attached. It's just the new unversioned package
doc dir change.
--
Thanks,
Warm regards,
Ankur (FranciscoD)
http://fedoraproject.org/wiki/User:Ankursinha
Join Fedora! Come
I've added 2 karma on system-config-services and taglib.
However after looking into taglib issue deeply I found that ncmpcpp in
Fedora is in FTBFS status.
Thanks.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Hi, folks. We have just over one week to the Fedora 20 Go/No-Go meeting,
and a big happy pile of blocker bugs - everyone's having fun! In order
to be able to complete testing in time for the go/no-go meeting
comprehensively and comfortably, we would need a build with all these
bugs addressed by the
