Bug 12697 - Please update uGet package (repo=1.10.3 / current=1.10.4) [also to Cauldron]
Summary: Please update uGet package (repo=1.10.3 / current=1.10.4) [also to Cauldron]
Status: RESOLVED DUPLICATE of bug 17132
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL: http://sourceforge.net/projects/urlge...
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-02-09 23:48 CET by Michael Tunnell
Modified: 2015-11-11 21:07 CET (History)
3 users (show)

See Also:
Source RPM: uget
CVE:
Status comment:


Attachments

Description Michael Tunnell 2014-02-09 23:48:30 CET
Description of problem:
uGet Download Manager is 1.10.3 which was the latest version of the app during the time it was added to Mageia 4 but we have recently released a new version and would like for it to be included in Cauldron and backported to Mageia 4.

Version-Release number of selected component (if applicable):
1.10.3 -> 1.10.4

Also there may be a patch needed due to GNUtils but it is not always an issue with every distro.

Here is a link to the patch in case it is an issue with Mageia.

http://ugetdm.com/files/uget-1.10.4-gnutls.patch

Reproducible: 

Steps to Reproduce:
Comment 1 Michael Tunnell 2014-02-10 00:07:55 CET
Also please update the app description to:

uGet is a download manager with downloads queue, pause/resume, clipboard monitor, batch downloads, browser integration (Firefox & Chrome), multiple connections, speed limit controls, powerful category based control and much more. Each Category has an independent configuration that can be inherited by each download in that category.

--------

and update the official website link to:

http://ugetdm.com
Manuel Hiebel 2014-02-10 16:58:53 CET

Keywords: (none) => Triaged
CC: (none) => fundawang, n54

Comment 2 Samuel Verschelde 2015-09-21 12:07:56 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further updates. As a 
result we are closing this bug report. 

If you would like to help with updates and backports in the future, don't 
hesitate to join the packager team via our mentoring program [1], our QA 
Team (who tests the updates and backport candidates and always welcomes 
help) [2] or join the teams that fit you most [3].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] https://wiki.mageia.org/en/QA_Team
[3] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 3 Michael Tunnell 2015-11-10 23:08:10 CET
I submitted the bug report over a year and a half before your reply. It was current then and there would have been no need for a backport had someone cared even remotely.

If it takes me over a year and a half to just get a response and the response is not even about updating my app then I think it would be best for us to not even pay attention to this distro as effort to update on our part should at least be met with an effort to merely respond.
Comment 4 claire robinson 2015-11-11 13:58:06 CET
Packages require maintainers Michael. Whilst your frustration at 'they' and 'someone' is understandable, it is misdirected and self defeating. 

Mageia is made by people - a relatively small team of volunteers, like yourself, who contribute their spare time. It is not a corporation with human resources to direct and there are currently no employees to instruct. Some packagers maintain many hundreds or even upwards of a thousand packages, so you can hopefully appreciate how busy that makes them and how dedicated they are in their contribution to the community.

It is not difficult to become a packager (link already provided in comment 2). We have a friendly and helpful mentoring system in place to train anybody who is interested in doing so and always need more people to get involved.

Whilst the information you provided initially is indeed useful to a maintainer, you can hopefully see that the hostility is misplaced and become more involved as part of the community.
Comment 5 claire robinson 2015-11-11 14:04:38 CET
You may also like to browse http://madb.mageia.org/
Comment 6 David GEIGER 2015-11-11 15:26:08 CET
I'm on it and I will maintain this package now. :)

Status: RESOLVED => REOPENED
CC: (none) => geiger.david68210
Version: 4 => 5
Resolution: OLD => (none)
Assignee: bugsquad => geiger.david68210

Comment 7 David GEIGER 2015-11-11 15:34:32 CET
So done for Cauldron and mga5 too updating uget to latest 2.0.2 release.


Packages in 5/core/updates_testing:
========================
uget-2.0.2-1.mga5.i586.rpm
uget-2.0.2-1.mga5.x86_64.rpm

Source RPM: 
========================
uget-2.0.2-1.mga5.src.rpm


@ Claire:

Can you provides an advisory for this update, please?

Thanks in advance!

Component: Backports => RPM Packages

Comment 8 Rémi Verschelde 2015-11-11 15:41:07 CET
(In reply to David GEIGER from comment #7)
> @ Claire:
> 
> Can you provides an advisory for this update, please?
> 
> Thanks in advance!

I guess it would be best that you do it, Claire is not particularly involved in this update candidate apart from trying to be diplomatic with the angry reporter.
Comment 9 Rémi Verschelde 2015-11-11 15:41:44 CET
Forgot my smiley at the end: :)
Comment 10 claire robinson 2015-11-11 15:49:15 CET
Thanks David. I suppose something simple would do, like..

=============================
This updates uget to a version which is supported upstream
and enhances the package description.
=============================

Assign to QA David whenever you're ready.
Comment 11 claire robinson 2015-11-11 15:52:38 CET
Could you please amend the description also David, as comment 1
Comment 12 Michael Tunnell 2015-11-11 16:30:10 CET
> "Packages require maintainers Michael. Whilst your frustration at 'they' and 'someone' is understandable, it is misdirected and self defeating."

At the time of the bug report there was a maintainer, at least I think there was. It has been a very long time. There was no misdirected frustration by use of the term "someone" because I was referring to absolutely anyone involved in the distro. I used the term someone to imply ambiguity as any reply is better than no reply.

The reply of "There is no one maintaining your app so if you'd like to take over then here's how" from anyone a year ago would have been better than no response at all.

> "We have a friendly and helpful mentoring system in place to train anybody who is interested in doing so and always need more people to get involved."

We don't have time to be maintainers but if a distro will allow us to maintain just our own app then that could work, so far no distro is willing to let that happen. I've tried multiple times in many distros.

We actually make RPMs for Fedora, how much different are Mageia RPMs from Fedora's?


> "you can hopefully see that the hostility is misplaced and become more involved as part of the community."

There was not any hostility, I've only expressed frustration in my comments. My barrier to not be satisfied was very low as all I requested was "to merely respond". After realizing the report wasn't getting answered the only thing I was requesting was just "to merely respond" and I'd say that is a completely reasonable request.


> You may also like to browse http://madb.mageia.org/

Thanks for the link, you all should probably add that link to the sitemap because when I went to the sitemap and it didn't have that, and searching didn't find it, I just assumed it didn't exist. (please add the link to http://www.mageia.org/en/map/)


> "I'm on it and I will maintain this package now. :)"

That's AWESOME! Thank you very much!


> "Claire is not particularly involved in this update candidate apart from trying to be diplomatic with the angry reporter."

I'm not angry and never was. I was frustrated and disappointed. I think it is fair to say that I was justified in my frustration. I also didn't curse at anyone, yell at anyone, etc. so I think to classify it as anger or hostility (as Claire did) is exaggerating my responses.


> "Could you please amend the description also David, as comment 1"

I'd like to amend my suggested description to:


uGet is an open source download manager based on GTK+. uGet Features: Downloads Queue, Pause/Resume, Clipboard Monitor, Batch Downloads, Browser Integration, Multiple Connections, Speed Limit Controls, Powerful Category based control and much more. Each Category has an independent configuration that can be inherited by each download in that category.
Comment 13 claire robinson 2015-11-11 17:40:07 CET
My comments were partly based on the text I found on your website regarding Mageia, Michael. Please bear in mind that our bugsquad who triage new bugs is also very small and also that you took almost two months to respond yourself. 

In this case though the bug was triaged immediately after it was created and assigned to the then maintainer. He is one who maintains very many packages and, partly due to his location, is occasionally not available - so it's entirely understandable I think that this one slipped through the net.

You are very welcome to maintain just one package in Mageia if you wish. We all contribute what we are able to contribute and one extra package being well maintained is a plus for the community :)

David has stepped in and offered to do so. If you want though, I'm sure he would welcome you taking over and Rémi is exactly the right person to arrange some mentoring if you decide to do so.
Comment 14 Michael Tunnell 2015-11-11 18:08:26 CET
> "My comments were partly based on the text I found on your website regarding Mageia, Michael. Please bear in mind that our bugsquad who triage new bugs is also very small

I think the page only expressed my frustration not hostility however after seeing David's response I have already updated the Mageia page to reflect the new information and removing the bug link.


> "also that you took almost two months to respond yourself."

two months while a long time in general is not even remotely long when compared to the year and a half issue. :)

I actually forgot I even had reported this bug and got a reply until yesterday when someone reported an old version of a different distro. Then I started looking through all distros we support on our site.


> "In this case though the bug was triaged immediately after it was created and assigned to the then maintainer. He is one who maintains very many packages and, partly due to his location, is occasionally not available - so it's entirely understandable I think that this one slipped through the net."

I agree it's understandable. The lack of reply hadn't really bothered me that much, since I forgot about it. The part that frustrated me was the part where I was told that my bug report was no longer relevant because it was for Mageia 4. 


> "You are very welcome to maintain just one package in Mageia if you wish. We all contribute what we are able to contribute and one extra package being well maintained is a plus for the community :)"

I would like to do this in the future when I have the time to learn how to do it but at the moment I don't.

Though what are the differences between Fedora RPMs and Mageia RPMs?


> "David has stepped in and offered to do so. If you want though, I'm sure he would welcome you taking over and Rémi is exactly the right person to arrange some mentoring if you decide to do so."

I would appreciate it if David would continue to maintain the app until which time I can devote to learning how to maintain for Mageia. It is a nice refreshing response to get in allowing me to maintain it myself because every other distro has either ignored the question or completely refused.
Comment 15 Rémi Verschelde 2015-11-11 18:18:03 CET
> > "also that you took almost two months to respond yourself."

> two months while a long time in general is not even remotely long when
> compared to the year and a half issue. :)

Well if I do the math, two months to answer _one_ email against 18 months to answer something like 5k emails, I guess you can see who was the most efficient. Anyway this is not a contest, but it would be nice of you to acknowledge that even if your bug was not handle as best as we would like to, we do our best (and from my experience, we do _very well_ for a community-led open source project of this scale).

> The part that frustrated me was the part where I was told that my bug
> report was no longer relevant because it was for Mageia 4. 

Well you do realise that the answer you got was a generic text sent to hundreds of Mageia 4 issues that have been closed as OLD at once, because for the 2/3 contributors of our bug triage team it just isn't possible to give a specific attention to *each* bug. Just check the bug ID, you'll see that we have plenty to do (though we're now more around ~18k).


Here the true issue is a triage mistake just after you reported the bug: the person who triaged the bug should have set the version tag to "Cauldron", and added the MGA4TOO label to the whiteboard, so that we know even when doing automatic measures that this issue is still relevant.
Comment 16 Michael Tunnell 2015-11-11 18:38:39 CET
> "Well if I do the math, two months to answer _one_ email against 18 months to answer something like 5k emails, I guess you can see who was the most efficient. Anyway this is not a contest . . . "

:) Well it wasn't until you just made it one. You are implying that email I received was the only email I ever get regarding uGet and that is just absurd. I manage the project for every distro (stuff like this), I handle all of the support questions, I maintain all of the social media accounts, and I can go on and on but the point is thus far I have only been defending myself in this thread.

You and Claire made a point about the length of time it took for me to reply, not relevant because most people would read the email and do one of two things: 1.) yell and scream at people. 2.) dismiss the distro completely and never look back.

I did not do either. I replied explaining why the response was unacceptable to me and expressed my frustration.

At no point did I express anger or hostility, only frustration and disappointment.

> "but it would be nice of you to acknowledge that even if your bug was not handle as best as we would like to, we do our best (and from my experience, we do _very well_ for a community-led open source project of this scale)."

I have in multiple comments expressed my gratitude and my improved perception of this project. I thanked David for his willingness to maintain our app, that's awesome of him. I also stated it was refreshing to get the responses I have regarding developers maintaining their own packages.

So I don't understand why you felt the need to say the above quoted comment.


> "Well you do realise that the answer you got was a generic text sent to hundreds of Mageia 4 issues that have been closed as OLD at once, because for the 2/3 contributors of our bug triage team it just isn't possible to give a specific attention to *each* bug. Just check the bug ID, you'll see that we have plenty to do (though we're now more around ~18k)."

Of course I could tell it was a mass message but that doesn't negate the frustration I had in any way.

I'm no longer frustrated regarding the maintenance of the package, at this point I'm only defending my right to be frustrated which I find rather amusing.


> "Here the true issue is a triage mistake just after you reported the bug: the person who triaged the bug should have set the version tag to "Cauldron", and added the MGA4TOO label to the whiteboard, so that we know even when doing automatic measures that this issue is still relevant."

Good to know, thanks for the information.
Comment 17 Michael Tunnell 2015-11-11 18:59:06 CET
By the way, I noticed that you all were creating manual line breaks the make the quotes not expand past the box where as I was just doing a normal markdown quote so here is some CSS to fix that issue.

Apply to global.css on line 345:


.bz_comment_text span.quote {
    color: #65379C;
    white-space: pre-wrap;
}

right now it is "white-space: pre;" which ignores the size of the container so the text escapes the box.
Comment 18 Michael Tunnell 2015-11-11 19:38:49 CET
Also please change the screenshot listed in the MADB to be this one, http://ugetdm.com/images/screenshots/uget-1-10-4-gnome-3-fedora-20-main-window.png

I don't have any screenshots for 2.0.2 yet but the one listed in the MADB is roughly 6 years old, maybe older, so a year old screenshot would still be an improvement. :)
Comment 19 claire robinson 2015-11-11 19:44:34 CET
I'm glad we found a way forward Michael and a solution to the frustrations of all involved. It's always good to see upstream developers contributing in the Mageia community. However it may have started, everyone is a winner today. Thankyou for getting the ball rolling :)

You might want to subscribe to our 'dev' mailing list, you can find that here https://ml.mageia.org/wwsympa-wrapper.fcgi/info/dev

To log in there use your registered email/password (rather than username/password) and click subscribe. Whenever you're ready to begin packaging for Mageia just have a read and send an email.

https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

MADB I believe makes use of screenshots from elsewhere, but it is most likely cached, feel free to create a new bug for that.

Let's please allow David to continue with the update in this one.
Comment 20 Rémi Verschelde 2015-11-11 19:53:15 CET
(In reply to Michael Tunnell from comment #18)
> Also please change the screenshot listed in the MADB to be this one,
> http://ugetdm.com/images/screenshots/uget-1-10-4-gnome-3-fedora-20-main-
> window.png

MADB pulls the screenshots from Debian, so we can't change it directly: https://screenshots.debian.net/package/uget
You could try uploading a new screenshot there though, so that both Mageia and Debian benefit from it :)
Comment 21 David GEIGER 2015-11-11 20:14:51 CET
@  Michael Tunnell:

you're welcome! it is with great pleasure that I am going now maintain uget. :)

If I had seen this bug report before, I would have done for a long time.

I'll now change the proposed description, so what 'description' must I use?

this one?

-------------------------------------------------
uGet is an open source download manager based on GTK+. uGet Features: Downloads Queue, Pause/Resume, Clipboard Monitor, Batch Downloads, Browser Integration, Multiple Connections, Speed Limit Controls, Powerful Category based control and much more. Each Category has an independent configuration that can be inherited by each download in that category.
-------------------------------------------------
Comment 22 David GEIGER 2015-11-11 20:19:07 CET
something like this (in spec file):

%description
uGet is an open source download manager based on GTK+.

uGet Features:

 * Downloads Queue,
 * Pause/Resume,
 * Clipboard Monitor,
 * Batch Downloads,
 * Browser Integration,
 * Multiple Connections,
 * Speed Limit Controls,
 * Powerful Category based control and much more.

Each Category has an independent configuration that can be inherited by each
download in that category.
Comment 23 Michael Tunnell 2015-11-11 20:26:50 CET
Your fix of the description is good. Most distros limit what can be said and the format that it can be said in but if you can do the list format in Mageia then I prefer that.

Also I apologize for this but there was an unexpected update to 2.0.3 today, https://bugs.mageia.org/show_bug.cgi?id=17132

I don't expect you to transition to 2.0.3 so quickly so if you need more time for that one feel free to do so.
Comment 24 David GEIGER 2015-11-11 21:07:55 CET
Closing of this bug to work now on bug #17132

*** This bug has been marked as a duplicate of bug 17132 ***

Status: REOPENED => RESOLVED
Resolution: (none) => DUPLICATE


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