| Summary: | feff, front-end for FFmpeg. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dimitrios Glentadakis <dglent> |
| Component: | New RPM package request | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | andr55, doktor5000, marja11, misc, oliver.bgr |
| Version: | Cauldron | Keywords: | PATCH |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://qt-apps.org/content/show.php/Feff?content=140298 | ||
| Whiteboard: | X | ||
| Source RPM: | feff | CVE: | |
| Status comment: | |||
|
Description
Dimitrios Glentadakis
2011-08-16 13:08:03 CEST
Marja Van Waes
2011-11-03 20:50:59 CET
Keywords:
(none) =>
PATCH You're on the list of Mageia packagers https://wiki.mageia.org/en/Packaging#Packaging_team but you don't seem to maintain any http://pkgsubmit.mageia.org/data/maintdb.txt Wouldn't it be an idea to import this one and maintain it yourself? Yes off course i can do this. I had asked before to maintain certain rpm that i know that i am able to do (them present in the repo that i maintain), and i had a "negative" answer (to be more explicit i was be suggested to continue maintain my community repository, is better than participate to the official repos packaging) so i continue maintain the mageia-gr.org repository and i ask here for the rpm to be imported each time. (In reply to comment #2) > and i had > a "negative" answer (to be more explicit i was be suggested to continue > maintain my community repository, is better than participate to the official > repos packaging) so i continue maintain the mageia-gr.org repository and i ask > here for the rpm to be imported each time. Would you mind sharing a link or something to that answer? Normally 3rd party repos are discouraged, because we want those people to work directly on Mageia packages and to import their packages, like for example the blogdrake guys are doing. CC:
(none) =>
doktor5000 I dont have any link, it was a discussion that i had with Michael Shearer in #mageia-devel last year. I asked if there is any need to ask for a mentor, or is better to continue sharing the rpm that i maintain, in the local community repo. Michael told me that is better to continue share them from the local community repo. It is ok i dont have any problem with this, but some packages i find them usefull and if they are included in the official repos is a + for the distribution and for other users that maybe wants them, so i asked here to be imported if you agree.
andré blais
2011-12-30 06:56:55 CET
CC:
(none) =>
andre999mga (In reply to comment #4) > I dont have any link, it was a discussion that i had with Michael Shearer in > #mageia-devel last year. I asked if there is any need to ask for a mentor, or > is better to continue sharing the rpm that i maintain, in the local community > repo. Michael told me that is better to continue share them from the local > community repo. > It is ok i dont have any problem with this, but some packages i find them > usefull and if they are included in the official repos is a + for the > distribution and for other users that maybe wants them, so i asked here to be > imported if you agree. So that was at least a year ago, he might think differently now. Anyway, we are short on packagers and I think it would be great if you got a mentor and would start packaging directly for Mageia. cc'ing misc CC:
(none) =>
misc I do not have log, but my point was rather : - we have some rules regarding what goes , and we have some good reasons to have those rules ( reasons like "needed for quality" ( quality itself that was requested repeatedly by users ) ). And while I think we should avoid 3rd parties repositories, I perfectly know that they are unavoidable, because no matter how much or how few rules you place, there will always be conflicts leading to them ( with enough packagers, that's unavoidable ). So now, I have nothing against Dimitrios becoming packager, but I think that if the goal is to maintain backports, or to push software that we cannot ship, that's not the time for that ( and unless some laws change drastically, people will wait quite a long time ), and he would be better to be outside of Mageia. However, there is still useful stuff to do, like making sure that no backports are needed in the next version by taking care of the software, and keeping them up to date. Or by making sure that the rpm we can ship needed by those we cannot are shipped. I would like to provide more but unfortunately in packaging this is all that i can offer. My only goal is to help and contribute the most i can for the best of Mageia as i follow the distribution since many years (mandriva) and i do trust the same persons. (In reply to comment #7) > My only goal is to help and contribute the most i can for the best > of Mageia as i follow the distribution since many years (mandriva) and i do > trust the same persons. And that is good. I'm very glad your name is on the list of apprentice candidates, now :)
Marja Van Waes
2012-02-17 16:39:03 CET
Whiteboard:
(none) =>
X A very good alternative of a conversion program is the ffmulticonverter http://pkgs.org/mageia-cauldron/mageia-core-release-i586/ffmulticonverter-1.2.0-1.mga2.noarch.rpm.html (just imported in mageia) I close this bug if there is no objection Status:
NEW =>
RESOLVED The version 1.9 has some sinificatives improvement and it seems that this project will have a good future. I imported the rpm: http://svnweb.mageia.org/packages?view=revision&revision=262670 I added Oliver Burger to verify the rpm. Status:
RESOLVED =>
REOPENED
Dimitrios Glentadakis
2012-06-24 08:13:30 CEST
CC:
(none) =>
oliver.bgr Submitted. I did some (little) changes to your spec file. Please check and ask me about them, when unsure why I did them. Status:
REOPENED =>
RESOLVED Thanks Oliver, ok, i see that i did n't set the attributes for the desktop file to 644, i have to remember next time. |