Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove Reprepro Dependencies & Limitations for Releasing .deb Package #336

Open
hollowaykeanho opened this issue Jun 15, 2024 · 2 comments
Open

Remove Reprepro Dependencies & Limitations for Releasing .deb Package #336

hollowaykeanho opened this issue Jun 15, 2024 · 2 comments
Assignees
@hollowaykeanho
Labels
Done and Pending Release Completed and staging for next release. Enhancement Case is about improving an existing feature/aspect. NON-Backward Compatible Solution is NOT backward compatible.

Comments

@hollowaykeanho
Copy link
Member

Description

Debian actually documented the repository format here: https://wiki.debian.org/DebianRepository/Format and reprepro tends to overcomplicate things so bad that it restricts everything from working efficiently. Hence, it's best we develop the algorithm internally and drop reprepro entirely.

Expected Behavior

Reprepro dependency is dropped and AutomataCI can publish .deb repository internally.

Current Behavior

.deb repository publication still depends on Reprepro.

Associated Data Files

No response
@hollowaykeanho hollowaykeanho added the Enhancement Case is about improving an existing feature/aspect. label Jun 15, 2024
@hollowaykeanho hollowaykeanho self-assigned this Jun 15, 2024
@github-project-automation github-project-automation bot moved this to Buckets in AutomataCI Jun 15, 2024
@hollowaykeanho hollowaykeanho added the In Progress Someone is working on the case. label Jun 15, 2024
@hollowaykeanho hollowaykeanho moved this from Buckets to v2.2.0 in AutomataCI Jun 15, 2024
@hollowaykeanho
Copy link
Member Author

Since we're removing an entire hard-coded implementations (reprepro internal execution), it should be marked as non backward-compatible even though it is. This is to reduce assumptions.

@hollowaykeanho hollowaykeanho added the NON-Backward Compatible Solution is NOT backward compatible. label Jun 15, 2024
@hollowaykeanho
Copy link
Member Author

Implemented: 6177cca

@hollowaykeanho hollowaykeanho added Done and Pending Release Completed and staging for next release. and removed In Progress Someone is working on the case. labels Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hollowaykeanho hollowaykeanho

Labels
Done and Pending Release Completed and staging for next release. Enhancement Case is about improving an existing feature/aspect. NON-Backward Compatible Solution is NOT backward compatible.
Projects
AutomataCI
Status: v3.0.0
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hollowaykeanho