Sean Whitton writes ("Bug#977845: dgit: unhelpful behavior in case previous
upload contained new upstream release"):
> It can't distinguish between stuck in some dak queue vs. actually
> rejected, though?
dgit doesn't currently distinguish that. Mostly because I thought
Hello,
On Mon 28 Dec 2020 at 12:08PM GMT, Ian Jackson wrote:
> Sean Whitton writes ("Bug#977845: dgit: unhelpful behavior in case previous
> upload contained new upstream release"):
>> On Mon 21 Dec 2020 at 09:01PM +01, Paul Gevers wrote:
>> > In the end I
Hi Ian, Sean,
On 28-12-2020 13:08, Ian Jackson wrote:
> Sean Whitton writes ("Bug#977845: dgit: unhelpful behavior in case previous
> upload contained new upstream release"):
>> On Mon 21 Dec 2020 at 09:01PM +01, Paul Gevers wrote:
>>> In the end I resorted to
&g
Sean Whitton writes ("Bug#977845: dgit: unhelpful behavior in case previous
upload contained new upstream release"):
> 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
&g
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
Package: dgit
Version: 9.12
Severity: normal
Hi,
As discussed on IRC, I had a slightly bad experience using dgit to
prepare an NMU for f2fs-tools.
paul@mulciber ~/packages/bugs $ dgit clone f2fs-tools
canonical suite name for unstable is sid
fetching existing git history
last upload to archive:
6 matches
Mail list logo
