Bug 652665 - Review Request: erlang-luwak - Large-object storage interface for Riak
Summary: Review Request: erlang-luwak - Large-object storage interface for Riak
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: NotReady
Depends On: 591926 639263 652546 652585 652598 652629 652648
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-12 13:48 UTC by Peter Lemenkov
Modified: 2016-03-14 11:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-04 12:04:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Lemenkov 2010-11-12 13:48:40 UTC
Spec URL: http://peter.fedorapeople.org/erlang-luwak.spec
SRPM URL: http://peter.fedorapeople.org/erlang-luwak-0-0.1.20101112gitb24f821.fc12.src.rpm
Description: Large-object storage interface for Riak.

This is another one of Riak's dependencies.

Comment 2 Peter Lemenkov 2012-07-29 16:10:24 UTC
Raising NotReady - cannot be built in Koji right now and (which concerns me much more) it fails to pass 3 unit-tests on my Fedora-PPC. I'm investigating this.

Comment 3 James Hogarth 2015-12-04 02:01:02 UTC
All the dependencies are marked as closed but there have been no comments on this review request in years.

Peter are you intending to do anything with this?

As per policy if there is no response in a week this bug will be closed.

https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews

Comment 4 Peter Lemenkov 2015-12-04 12:04:18 UTC
(In reply to James Hogarth from comment #3)
> All the dependencies are marked as closed but there have been no comments on
> this review request in years.
> 
> Peter are you intending to do anything with this?

Nope. This is an abandoned project (upstream no longer develops/uses this). So I suppose we should close this as well.


Note You need to log in before you can comment on or make changes to this bug.