git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Representing Debian Metadata in Git

From
SWSean Whitton <spwhitton@spwhitton.name>
Date
Aug 23, 2024, 02:20 UTC
Message-ID
<874j7cou8s.fsf@melete.silentflame.com>
In-Reply-To
<eb963843-9e2c-49f2-911f-fa36f33f9bfd@debian.org>
Hello,
I think that more than you realise of this already exists :)
On Tue 20 Aug 2024 at 04:10pm +09, Simon Richter wrote:
Show 5 quoted lines
> From a requirements perspective, I'd like to be able to
>
>  - express patches as commits:
>    - allow cherry-picking upstream commits as Debian patches
>    - allow cherry-picking Debian patches for upstream submission
git-debrebase and git-dpm already achieve this.
>  - express filter steps for generating the upstream archive(s) from a tree‑ish
>   and some metadata

Excluded-Files in d/copyright is for this. I guess that you disprefer that because it's part of the tree, though.

>  - store upstream signatures inside Git
Well, there's signatures on their tags.
>  - keep a history of patches, including patches applied to previously released
>   packages

This is already there with git-debrebase and git-dpm, though it is a bit fiddly to dig it out.

-- 
Sean Whitton
Previous: Blair Noctis
Message 6 of 6 in “Representing Debian Metadata in Git”
  1. Simon RichterAug 20, 2024
  2. Chris HofstaedtlerAug 21, 2024
  3. rsbecker@nexbridge.comAug 21, 2024
  4. Chris HofstaedtlerAug 21, 2024
  5. Blair NoctisAug 22, 2024
  6. Sean WhittonAug 23, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.