Comment # 5 on bug 1155691 from Giovan Isa Musthofa

(In reply to Matthias Gerstner from comment #3)
> Thank you for opening the bug!
> 
> (In reply to giovanmail@gmail.com from comment #2)
> > (In reply to Johannes Segitz from comment #1)
> > > do you intend to submit this to openSUSE? rpmlint will (soonish) ignore such
> > > issues in home directories, so if this for your own use nothing needs to be
> > > done here and it should solve itself
> > 
> > When do I expect this change to take effect?
> 
> There is no fixed date we can give you yet but it's probably a few weeks.
> Us actually reviewing the code would also take a while, however. Do you have
> plans to forward this package to openSUSE:Factory?
> 
> The chrome-sandbox you package here is actually already packaged in the
> chromium package. What is the background of that? Could you probably use just
> the chrome-sandbox from the chromium package? Then no review would be
> necessary at all. Having the same setuid binary twice in the distribution
> would be rather unfortunate anyways.

It would be nice if it can get to openSUSE:Factory. What does it take to
forward this to openSUSE:Factory?

I just checked the package files and yes there is a chrome-sandbox. Actually, I
just forked this package from
https://build.opensuse.org/package/show/home:nuklly/slack and download the
latest package from slack official website. They only provide this rpm, so
that's all I have.

I'm all for less work and faster release schedule for the packages. But I
haven't found guides or example for editing and building package from existing
one.