On 2019-04-10 8:36 a.m., Stephen John Smoogen wrote:
>
>
>
>
> Please try it again, and if it doesn't work please do the following:
>
> curl -O https://puiterwijk.fedorapeople.org/fedpkg_new-sources.sh
>
> run the command with the upload and paste the output and also a
> `klist` as some of the prob
On Wed, 10 Apr 2019 at 11:29, Luya Tshimbalanga
wrote:
> On 2019-04-10 5:06 a.m., Dridi Boukelmoune wrote:
> >> From looking at it quickly, it seems like you've updated the .spec for
> >> version 19.17 but have only uploaded sources for 19.16. > > If he's not
> the maintainer he probably doesn't
On 2019-04-10 5:06 a.m., Dridi Boukelmoune wrote:
>> From looking at it quickly, it seems like you've updated the .spec for >>
>> version 19.17 but have only uploaded sources for 19.16. > > If he's
not the maintainer he probably doesn't have the privileges to do so. > >
Dridi > ___
> From looking at it quickly, it seems like you've updated the .spec for
> version 19.17 but have only uploaded sources for 19.16.
If he's not the maintainer he probably doesn't have the privileges to do so.
Dridi
___
devel mailing list -- devel@lists.f
On Wed, Apr 10, 2019 at 4:08 AM Luya Tshimbalanga
wrote:
>
> Hello team,
>
> dlib needs an update but the maintainer has not responded for month to
> verify and merge the change.
> Can a proven test push the merge and update that package matching
> upstream release.
From looking at it quickly, it
Hello team,
dlib needs an update but the maintainer has not responded for month to
verify and merge the change.
Can a proven test push the merge and update that package matching
upstream release.
See https://release-monitoring.org/project/18600/
Reference:
---
https://src.fedorapro
