Bug 3857 - hg record --user ... is broken
Summary: hg record --user ... is broken
Status: RESOLVED FIXED
Alias: None
Product: Mercurial
Classification: Unclassified
Component: record (show other bugs)
Version: earlier
Hardware: PC Windows
: normal bug
Assignee: Bugzilla
URL:
Keywords: easy
: 4107 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-15 06:59 UTC by techtonik
Modified: 2017-11-01 18:04 UTC (History)
5 users (show)

See Also:
Python Version: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description techtonik 2013-03-15 06:59 UTC
> hg record --user "anatoly techtonik <techtonik@gmail.com>"
abort: no username supplied (see "hg help config")

> hg record -h
...
 -d --date DATE           record the specified date as commit date
 -u --user USER           record the specified user as committer
 -S --subrepos            recurse into subrepositories
...
Comment 1 Bryan O'Sullivan 2013-04-02 12:04 UTC
Works for me. Got more details about version, etc?
Comment 2 Matt Mackall 2013-04-02 13:57 UTC
I think the crucial fact here is no ui.username setting. dorecord invokes ui.username at various points.

$ HGRCPATH= hg --config extensions.record= record -u bob
abort: no username supplied (see "hg help config")
Comment 3 techtonik 2013-04-02 13:58 UTC
> hg --version
Mercurial Distributed SCM (version 2.5.2)

Vista 32
Comment 4 Matt Mackall 2013-11-20 17:06 UTC
*** Bug 4107 has been marked as a duplicate of this bug. ***
Comment 5 HG Bot 2013-12-16 15:00 UTC
Fixed by http://selenic.com/repo/hg/rev/a765611e06dc
Prasoon Shukla <prasoon92.iitr@gmail.com>
record: --user/-u now works with record when ui.username not set (issue3857)

The -u flag didn't work when ui.username was not set and resulted in an
abort message. This was fixed by checking for the 'user' key in the opts
dictionary. If the key is present, the step causing the exception is not
executed.

(please test the fix)
Comment 6 techtonik 2014-01-15 10:47 UTC
2.8.1 - still broken.

>hg record --user "anatoly techtonik <techtonik@gmail.com>"
abort: no username supplied (see "hg help config")

>hg version
Mercurial Distributed SCM (version 2.8.1)
Comment 7 Bugzilla 2015-02-26 01:00 UTC
Bug was inactive for 406 days, archiving
Comment 8 techtonik 2015-02-26 01:43 UTC
Not sure it is RESOLVED. The correct Status should be something like
ARCHIVED with no Resolution.

On Thu, Feb 26, 2015 at 9:00 AM,  <mercurial-bugs@selenic.com> wrote:
> http://bz.selenic.com/show_bug.cgi?id=3857
>
> Bugzilla <bugzilla@selenic.com> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|CONFIRMED                   |RESOLVED
>          Resolution|---                         |ARCHIVED
>
> --- Comment #7 from Bugzilla <bugzilla@selenic.com> ---
> Bug was inactive for 406 days, archiving
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 9 Matt Mackall 2015-02-26 01:52 UTC
Take it up with the Bugzilla project. RESOLVED is what they call the terminal state of bugs, ARCHIVED is what we call the "insufficient interest" substate.

http://mercurial.selenic.com/wiki/BugTracker#Why_we_auto-close_old_issues

But as it happens, this bug was in fact correctly fixed ages ago and you tested the wrong branch.
Comment 10 techtonik 2015-02-27 03:30 UTC
I thought that all modern trackers allow to configure the states and
workflow. But I don't know Bugzilla - I tried to add OpenID support to
it, but it is written in Perl, so I abandoned it long ago.

I suspected that it resolved, but don't have time to test it, so hoped
to find it at some point later - like query all archived bugs that are
not resolved and see if I can test all at once. Right now it is
impossible.