--- Comment #29 from Dominic Robinson <development-K9RvgheM1OmXW9pm(a)dcrdev.com> ---
(In reply to Nicolas Chauvet from comment #28)
(In reply to Dominic Robinson from comment #26)
> Also bit confused - is this package approved, I note the fedora-review +
> flag and also the repository having been created here:
Yep, seems like this package was mass imported along the other ones from
I will transfer the ownership to you once this package got formally approved
can you remind your RPM Fusion FAS account name ?
Yes it's "dcrdev" .
(In reply to Nicolas Chauvet from comment #27)
(In reply to Dominic Robinson from comment #25)
> I hadn't planned on changing it -
> I mean might be a problem if I reuse this spec for other addons, but I don't
> see an issue in the context of this addon and makes things neater.
Well, this is not the case from a RPM Fusion rel-eng perspective.
If ever the aname is changed, which might happen if the package get fixed ,
the package name will be automatically changed. This is not possible with
the infra where koji expect the spec file to be named according to the git
As a consequence, the build will fails, but it may requires additional steps
to cure this issue.
For example, upstream may consider to change inputstream.adaptive to
inputstream_adaptive. So the point of using a variable in this case doesn't
OK makes sense - I'll hardcode it to "kodi-inputstream-adaptive" . I'll
off a build this evening, as I don't have access to my build system right now.
You are receiving this mail because:
You are on the CC list for the bug.