Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 588508

Summary: games-strategy/openra-20160508 stable version bump
Product: Gentoo Linux Reporter: DrSlony <bugs>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: bugs, np-hardass
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://www.openra.net/news/release-20160508/
Whiteboard:
Package list:
Runtime testing required: ---

Description DrSlony 2016-07-10 11:03:38 UTC
Please add games-strategy/openra-20160508 to portage or explain what the community can do to help.

---

There is bug 582942 but its assigned to someone or to a group which has shown zero response, hasn't even answered what the community can do to help get this in portage, ergo a new bug not assigned to them.

Reproducible: Always
Comment 1 Adam Feldman gentoo-dev 2016-07-11 00:36:05 UTC
A separate bug really doesn't do much to further the cause.  I'd recommend contacting the maintainers directly, seeing if your version bump fixes the outstanding bugs (there are 2) and offer to take on maintenance as a proxy-maintainer to reduce the workload, since they typically have a heavy workload.
Comment 2 DrSlony 2016-07-11 10:11:15 UTC
I asked in that bug for guidance on what the problem is and how I could help, and received no reply. They surely can't be too busy to answer a question asked 40 days ago. I am very active in open-source development (RawTherapee etc.) and that is just not how you do things. Clearly opening a separate bug did further the cause, as you replied the very next day :)

Moving on.

Both of those bugs are for 20140722-r1 and both have been reported by a single individual with no other confirmations. Much has changed in OpenRA since that release. I could not reproduce either bug.

I'll get in touch with the OpenRA team and see what the situation with their Gentoo ebuild is, I recall some months ago that there was a problem with something related to the package manager it used.
Do we continue here or in bug 582942 ?
Comment 3 Adam Feldman gentoo-dev 2016-07-11 16:52:23 UTC
(In reply to DrSlony from comment #2)
> I asked in that bug for guidance on what the problem is and how I could
> help, and received no reply. They surely can't be too busy to answer a
> question asked 40 days ago. I am very active in open-source development
> (RawTherapee etc.) and that is just not how you do things. Clearly opening a
> separate bug did further the cause, as you replied the very next day :)
> 
> Moving on.
> 
> Both of those bugs are for 20140722-r1 and both have been reported by a
> single individual with no other confirmations. Much has changed in OpenRA
> since that release. I could not reproduce either bug.
> 
> I'll get in touch with the OpenRA team and see what the situation with their
> Gentoo ebuild is, I recall some months ago that there was a problem with
> something related to the package manager it used.
> Do we continue here or in bug 582942 ?

Contact the devs directly in #gentoo-games.  Opening the second bug really hasn't done anything.  It takes unrelated devs who have no impact on the orginal issue away from what they are doing and puts them in a position where, ultimately, all they can do is reassign it to the dev who you are bypassing by opening a separate bug.

I have no authority, nor does anyone else (ttbomk[save a security issue]) to force them to do a bump.

As stated previously, your best bet is to get in contact with the Gentoo maintainers, at this point, looks like outside of bugzilla would be best.  Regardless, you should continue bugzilla work in the old bug.

Add a thorough analysis of the build system changes between the two releases, in clude an up-to-date ebuild reflecting those, assess the old bugs to see if you can obsolete them...  Contribute, and I'm sure it will help move the whole thing along.

*** This bug has been marked as a duplicate of bug 582942 ***
Comment 4 DrSlony 2016-07-11 19:35:06 UTC
Roger, thank you.