Control: close -1
I'm not sure this is very actionable any more. Hopefully forthcoming
ideas about "push to upload" will make this unnecessary.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypas
Ansgar pointed out that this could be simplified some if there were a
way to reproducible build the same *source* package from info in git.
The remote machine then does not need to cobble together the dsc and
changes, but can just be sent the signed dsc and changes from the build
machine, pair them
Ian Jackson wrote:
> > I envision something like: dgit push --via somehost
>
> I don't understand what the somehost is for.
>
> Why wouldn't dgit just generate the necessary source package files in
> the usual way ?
> Perhaps your --via is simply the build-host for rpush.
The use case is that i
Joey Hess writes ("Bug#756978: .tar-less push"):
> Now that the archive finally supports .deb-less uploads, dgit should be
> able to take it a step further, to .tar-less push.
>
> I envision something like: dgit push --via somehost
I don't understand what the somehost
Package: dgit
Version: 0.21
Severity: wishlist
Now that the archive finally supports .deb-less uploads, dgit should be
able to take it a step further, to .tar-less push.
I envision something like: dgit push --via somehost
That would push the git repository as usual, then go to somehost and
dgit
5 matches
Mail list logo
