This repository was archived by the owner on Jul 14, 2022. It is now read-only.
Draft
Conversation
I am not an expert in this, but to my knowledge debian/control file is auto-regenerated during the build
Owner
|
The way of handling this has been copied verbatim from another (official) Debian package. I do not remember which one anymore. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Try to use auto-generated debian/control file
I saw this in gzip postgres extension - https://github.com/pramsey/pgsql-gzip/blob/7c26e8b0056631ec0bb7c8fdd9bf2a24076e4a49/debian/rules
But apparently this extension does not have
pg_buildextavailable. I saw that during the builddebian/controlwas auto-updated, which implies that it probably shouldn't be part of git?