Comment 1 for bug 1761821

On Fri, Apr 6, 2018 at 11:00 AM, Steve Langasek
<email address hidden> wrote:
> Public bug reported:
>
> error message at the end of a 'git ubuntu clone cryptsetup':
>
> fatal: could not read Username for 'https://git.launchpad.net': terminal
> prompts disabled

Yeah, it's annoying, but we're living with it for now, because Git
doesn't let us differentiate between a non-existing and
not-viewable-due-to-permissions repository. And we don't want an auth
prompt here.

> $ snap info git-ubuntu
> name: git-ubuntu
> summary: Ubuntu development git tooling
> publisher: nacc
> license: unknown
> description: |
> Imports, clones, etc. a source package in a git tree
> commands:
> - git-ubuntu
> - git-ubuntu.import-source-packages
> - git-ubuntu.man
> - git-ubuntu.merge-changelogs
> - git-ubuntu.reconstruct-changelog
> - git-ubuntu.self-test
> - git-ubuntu.source-package-walker
> - git-ubuntu.update-repository-alias
> snap-id: VAGSRAriUyDDlqsLunShJTe7503Uw4GF
> tracking: candidate
> refreshed: 2018-03-02T13:47:36-08:00
> installed: 0.7.4 (392) 105MB classic
> channels:
> stable: 0.7.4+git16.0a79cbc (391) 104MB classic
> candidate: 0.7.4 (392) 105MB classic
> beta: ↑
> edge: 0.7.4+git28.50ce40e (411) 115MB classic
> $
>
> The version numbers seem confusing, I would expect 0.7.4+git16.0a79cbc
> to be newer than 0.7.4 but 0.7.4 has the later revision. Is the version
> on the candidate channel newer or older than the one on stable?

This is because snap/stable (in the repository) actually has some
backported bugfixes from way back when. That is git's interpretation
of the merge result.

I think for the forthcoming 0.8 release, I'm just going to hard reset
everything to the same commit in the repository, so all three channels
will start at the same point.

-Nish