Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Trashed package name after propose-update
See original GitHub issueWe had to do some post-release spec fixing and a colleague used packit propose-update with --no-pr --local-content --force-new-sources. Packit (or rebase-helper?) somehow took the version and replaced part of the name with it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Android application name after deleted - Stack Overflow
1 Answer 1 ... No, you cannot. package ID's are uniquie throughout the play store, There cannot be two apps with same name....
Read more >Unlocked packages names can be reused after total uninstall?
I have a question related to name reusability of unlocked packages. While going through Salesforce DX trailhead exercises, I've created ...
Read more >Can't reuse name of package I deleted · Issue #620 - GitHub
I uploaded a package called "simtree", and I was making a bunch of ... that after deleting a package, that name is forever...
Read more >78111 – x11-libs/openmotif libXpm vulnerabilities
So I propose: - update openmotif to 2.2.4 with this symlink - update lesstif to ... I have since deleted the 2.2.4 ebuild...
Read more >Suggested Package Names - Oracle Help Center
A deployed server package cannot be revised, rebuilt, or deleted. It must be replaced with another package first. For this reason, you must...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The problem is in the specfile sync:
https://github.com/packit-service/packit/blob/8833635fdfbc681a518f75b7a1a363785a319ee2/packit/base_git.py#L366-L370
When we copy content from the upstream specfile to the downstream one, the rebase-helper does not refresh the indices. And when the old and new specfile differ in the number of lines before version, it uses a bad line to save the version. (Saving the content after sync solves the problem.)
Thanks for the quick fix!