Bug 1068988 - Fedora lacks a package for pyload
Summary: Fedora lacks a package for pyload
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: NotReady
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-23 20:27 UTC by Florian Bäuerle
Modified: 2015-06-29 19:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:03:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
my packaging efforts for pyload (877.05 KB, application/gzip)
2014-02-23 20:35 UTC, Florian Bäuerle
no flags Details

Description Florian Bäuerle 2014-02-23 20:27:23 UTC
Description of problem:
cannot install pyload via yum

Version-Release number of selected component (if applicable):
20

How reproducible:
fairly.


Steps to Reproduce:
1. yum install pyload

Actual results:
package not available


Expected results:
package available

Comment 1 Florian Bäuerle 2014-02-23 20:35:42 UTC
Created attachment 866770 [details]
my packaging efforts for pyload

file list:

./build.sh
./pyload-0.4.9.spec
./pyload-0.4.9-1.fc20.src.rpm
./pyload.service
./pyload-0.4.9-1.fc20.noarch.rpm
./pyload.conf


many thanks to https://aur.archlinux.org/packages/pyload/ and to https://bitbucket.org/ranan/pyload-dist

Comment 2 Florian Bäuerle 2014-02-23 20:36:55 UTC
I tried to package it on my own, above is the result.

Since this is my first packaging effort for Fedora, I assume that it is done absolutely wrong, but maybe it can be made use of in any way.

usage:
./build.sh

result:
rpm package for pyload. it is even working.

Comment 3 Mukundan Ragavan 2014-02-23 21:27:32 UTC
Please take a look at the following links and follow the instructions as closely as possible

* http://fedoraproject.org/wiki/How_to_create_an_RPM_package

* https://fedoraproject.org/wiki/Packaging:Guidelines

I will mark this as NotReady.

Comment 4 Matthias Runge 2014-02-26 15:18:35 UTC
Florian, thank you for your contribution.

Are you trying to become a Fedora packager or did you just shared your first steps?

When contributing a package, you'll need to put the SPEC and SRPM somewhere else on a web server; if that's a problem, you could even get space in Fedora's infrastructure.

Comment 5 Fedora End Of Life 2015-05-29 11:01:58 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-06-29 19:03:16 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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