Hello, On Mon 21 Dec 2020 at 09:01PM +01, Paul Gevers wrote:
> In the end I resorted to > paul@mulciber ~/packages/bugs $ dgit clone f2fs-tools testing > as unstable and testing have the same version, but that doesn't work if > unstable and testing don't have the same version. In this situation what it seems we want to achieve is a) get the version you want to hack on into dgit as if `dgit clone` had given it you b) make it easy to `dgit push` your new version, which is based on the result of (a). How dgit could automate this is if it could detect that the upload on dgit-repos never made it to the archive, it could then prepare a new repo for you as if there was nothing on dgit-repos, and then pseudomerge that on top of the contents of dgit-repos, so a push would just work. However, detecting whether an upload made it to the archive would require incorporating a lot of idiosyncratic knowledge about dak into dgit, I think, with a fair bit of guessing? Or is the way that dak keeps track of such things amenable to adding a new ftp-master API query to find out? In the meantime what I would have done is `apt-get source` followed by `dgit import-dsc` followed by pseudomerging in the result of `dgit fetch unstable`. What do you think about the error message suggesting that for this sort of situation? -- Sean Whitton
signature.asc
Description: PGP signature
