Pagure completely broke after re-forking fedora-server #12388
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#12388
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NOTE
If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.
Describe what you would like us to do:
I wanted to contribute to fedora by creating a pull request for updates I made to the documentation.
In typical fashion, I completely broke the system and I am unable to recover:
It appears my account is completely fubared, with no way to recover it. Is there a way to "reset"?
When do you need this to be done by? (YYYY/MM/DD)
Few things first:
Metadata Update from @zlopez:
the issue began when clicking "fork" from this link https://pagure.io/fedora-server/blob/main/f/docs/modules/ROOT/pages/services/filesharing-nfs-installation.adoc
which is the https://pagure.io/fedora-server repo
There were definitely 2 projects for this fork, causing pagure to throw a 500 for returning 2 rows when it expected only one.
I tried to delete the older one, but somehow it's still showing up, and I can't see why. ;(
Probably needs some database cleaning as well.
Well, I deleted that row, but there must be something else thats keeping it thinking there's duplicates.
Perhaps @pingou could save us?
Or perhaps @abompard might be able to see something?