When doing initial modules->flatpaks namespace migration, two flatpak modules were missed:
baobab, cheese
Please move these to the flatpaks/ namespace.
In addition, we ended up accidentally requesting geany twice (in both modules and flatpaks namespace). Please remove the empty modules/geany repo.
Thanks, Kalev
This needs @mohanboddu for the releng side and @pingou for the pagure side...
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: src.fp.o
@pingou We need to collaborate on doing this work, please ping me on irc when you get to this ticket.
@mohanboddu and @pingou Perhaps you could do this tomorrow morning? (2019-09-27)
I'll already be AFK tomorrow. I will likely not be available to work on this before the 7th.
Metadata Update from @pingou: - Issue assigned to pingou
git repo moved and db adjusted, the pagure side is done
Metadata Update from @pingou: - Issue assigned to mohanboddu (was: pingou)
On pdc end, this is fixed and on koji side, I am not seeing that they are not built for f32 yet.
If they needs to be build for f32, please reopen the ticket and I will add them to the appropriate tags.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks guys!
Metadata Update from @kalev: - Issue status updated to: Open (was: Closed)
Reopening. I'm getting an error pushing to cheese:
$ git push Enumerating objects: 1, done. Counting objects: 100% (1/1), done. Writing objects: 100% (1/1), 184 bytes | 184.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: remote unpack failed: unpack-objects abnormal exit To ssh://pkgs.fedoraproject.org/flatpaks/cheese ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'ssh://kalev@pkgs.fedoraproject.org/flatpaks/cheese'
Could you try again?
Still the same.
Any now?
Works now! Thanks :)
Metadata Update from @kalev: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.