#4409 Figure out how to access a namespaced project named ``tree``
Opened 6 years ago by pingou. Modified 3 years ago

Basically the dist-git deployment of pagure on https://src.fedoraproject.org has a RPM package named tree which should thus be at https://src.fedoraproject.org/rpms/tree

However, pagure in this case does not know if the user is trying to view the tree of the rpms project, or the tree project in the rpms namespace.

Source: https://pagure.io/fedora-infrastructure/issue/7031


@pingou Would a good solution for this be to change /tree/ to /filelist/ or something similar for Pagure 6.0?

Metadata Update from @ngompa:
- Issue priority set to: Normal
- Issue set to the milestone: 6.0

3 years ago

That works until someone wants to add a filelist package. Playing whack-a-mole with package names doesn't seem like a good idea. How about a special character (that is an invalid package name) just before the paths? Something like:

That's not a bad idea either. I think we do something similar for the API routes already?

That works until someone wants to add a filelist package. Playing whack-a-mole with package names doesn't seem like a good idea. How about a special character (that is an invalid package name) just before the paths? Something like:

This would be the better way indeed. It's going to break quite a few links
though :(

I think we'll have to grin and bear it, though. At least doing it for 6.0 means everyone can expect breakage.

@pingou Would a good solution for this be to change /tree/ to /filelist/ or something similar for Pagure 6.0?

Nope because it would invalidate existing URLs.

@pingou Would a good solution for this be to change /tree/ to /filelist/ or something similar for Pagure 6.0?

Nope because it would invalidate existing URLs.

There are two schools I could see when it comes to URLs, those who believes that
URLs are static and must always be preserved and those who think that the web is
dynamic by nature and URLs come and go every day.

Maybe we could do something a little bit like:
4eb3a7f but that could quickly become tricky :(

I think for 6.0, it's reasonable for us to change things so we disambiguate stuff properly.

Anyway, the tree package appeared to cause problems to Gitlab as well, so I have initiated a package rename request to sort it out: https://bugzilla.redhat.com/2001467

Nope because it would invalidate existing URLs.

Only if we break them. We can keep them working as a redirect. The only one that would obviously break would be the conflicting one, but all the other existing ones would keep working.

Log in to comment on this ticket.

Metadata