Packaging guidelines for the scenario where an upstream repository no longer exists #1548
Labels
No labels
announce
bootstrap
Closed As
accepted
Closed As
duplicate
Closed As
exceptionexpired
Closed As
fixed
Closed As
invalid
Closed As
nothingtodo
Closed As
permanentexception
Closed As
rejected
Closed As
temporaryexception
Closed As
wontfix
cmake
committee
draftneeded
hasdraft
meeting
meson
needinfo
Priority
In Committee
Priority
Needs Review
Priority
Waiting For Reporter
rust
writeup
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
packaging/guidelines#1548
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?
I saw a comment in the Fedora Python Matrix group asking if a project without an upstream source could be packaged (I assume he got the source somewhere). I was looking into the main packaging guidelines and https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ and couldn't find any mention about it.
Should something be added in that case? To me, adding a package in Fedora without an upstream source seems extremely sketchy.
I've seen this happen for two "common" cases:
Both cases are usually OK, if not ideal, since it's hard to contribute back to such projects.
Of course, there's the third case, of the project actually being dead - in which case I'd rather not package it. :)
Yeh, even for old packages they tend to either slowly die or people packaging them in distros. tend to create an new upstream. So I'd suggest they see what the other big distros. have for the package, and/or ping the packagers.