The case of lacking an /etc/mailname is
https://bugs.launchpad.net/bzr/+bug/884502
Note that you don't need to have an actual mailer, just a mailname that
contains one line giving the mail domain of the box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: bzr
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity (should look at /etc/mailname)
To man
This was inside debian-installer, no mailer installed on the box. So it
does seem to be a different use-case than one would get from the
original bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
It is still possible to get this error, although in most cases it should
be able to automatically determine your user id. Do you have a valid
/etc/mailname, and does the current user have an entry in the passwd
database?
--
You received this bug notification because you are a member of Ubuntu
Bug
2.4.0-0ubuntu2~11.IS.8.04 from jelmer, if that helps get the
conversation going
** Changed in: bzr
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
% bzr init; bzr add
...
% bzr commit -m 'Initial import.'
bzr: ERROR: Unable to determine your name.
I believe this means we have regressed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title
This bug was fixed in the package bzr - 2.3.4-0ubuntu1
---
bzr (2.3.4-0ubuntu1) natty-proposed; urgency=low
* New upstream release.
+ Fix bzr version number in deprecation warnings. LP: #794960
+ Prevent write attemps on remote branch during "bzr up". LP: #786980
+ Fix conf
Verified by running the bzr testsuite from the package in a clean natty
install.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616
** Branch linked: lp:~ubuntu-branches/ubuntu/natty/bzr/natty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity (should look at /etc/mailnam
Accepted bzr into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: bzr (Ubuntu Natty)
Sta
** Changed in: bzr (Ubuntu Natty)
Assignee: (unassigned) => Jelmer Vernooij (jelmer)
** Changed in: bzr (Ubuntu Natty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Branch linked: lp:~jelmer/ubuntu/natty/bzr/sru-2.3.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity (should look at /etc/mailname)
To manage
** Also affects: bzr (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: bzr (Ubuntu Natty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
** Changed in: bzr (Ubuntu)
Status: In Progress => Fix Released
** Changed in: bzr (Ubuntu)
Milestone: maverick-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
** Branch linked: lp:debian/experimental/bzr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity (should look at /etc/mailname)
--
ubuntu-bugs maili
** Summary changed:
- bzr commit error because of no identity
+ bzr commit error because of no identity (should look at /etc/mailname)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bz
** Changed in: bzr (Ubuntu)
Status: Confirmed => In Progress
** Changed in: bzr
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr com
Martin, your branch for this has landed, should we be considering it Fix
Released instead of In Progress? Or did you have more you needed to do.
Maybe that should be split out as another bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: bzr/2.3
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity
--
ubuntu-bugs mailing list
ub
** Changed in: bzr/2.3
Status: New => In Progress
** Changed in: bzr/2.3
Assignee: (unassigned) => Martin Pool (mbp)
** Changed in: bzr (Ubuntu)
Milestone: None => maverick-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: bzr/2.3
Importance: Undecided
Status: New
** Changed in: bzr/2.3
Milestone: None => 2.3.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error
** Branch linked: lp:~mbp/bzr/whoami
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
** Changed in: bzr
Status: Confirmed => In Progress
** Changed in: bzr
Assignee: canonical-bazaar (canonical-bazaar) => Martin Pool (mbp)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/6168
** Changed in: bzr
Assignee: (unassigned) => canonical-bazaar (canonical-bazaar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity
--
ubuntu-
** Changed in: bzr
Assignee: Registry Administrators (registry) => Curtis Hovey (sinzui)
** Changed in: bzr
Assignee: Curtis Hovey (sinzui) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
After discussing with lamont, we think trusting mailname is fine (by
default).. provided that it won't require us to set an option to enable
that behaivor.
Can this be in v2.3?
Thanks!
-Charlie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Changed in: bzr
Assignee: (unassigned) => bazaar-core-staff (bazaar-core-staff)
** Changed in: bzr
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
** Tags added: whoami
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
** Changed in: bzr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/616878
Title:
bzr commit error because of no identity
--
ubuntu-bugs mailing list
ubuntu-b
On 26 November 2010 07:57, Max Bowsher wrote:
> Could we not just add a branch.conf boolean setting (and corresponding
> switches to 'bzr init', 'bzr reconfigure') which reverts to the previous
> behaviour?
So, it would default to warning or failing, to help people who don't
realize they ought to
I think considering the machine's mailname is perhaps not necessary.
As I see it, there are two significant divisions of use-cases here:
1) The ones that bug 549310 was filed about, where users are committing
revisions to be shared with the world, and the email address really
really ought to be a
Martin: For this and for Bug #647475 I think even filling it full of
gub...@example.com would be fine, as etckeeper/manual-etc-in-bzr trees
do not typically get published anywhere for obvious reasons. We're not
actually concerned with the value of this field, as we have ignored it
for a long time
I asked before if trusting the mailname would be a good solution for
this. What do you think, Nick?
--
Martin
--
bzr commit error because of no identity
https://bugs.launchpad.net/bugs/616878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Bug #647475 overlaps heavily with this bug. It concerns the fact that
this problem breaks etckeeper rather terribly, especially in the update-
manager where it's not made as clear what's actually going wrong. It's
likely worth marking a duplicate of this one.
--
bzr commit error because of no i
The main problem with inferring the email address seems to be is that
checked both the email domain and the hostname. Perhaps it would be
reasonable to assume that if the machine's mail domain is set, it is
correct. So we might get auto commits from j...@home.example.com but not
from j...@home.
Would a switch like --guess-committer or --committer=ARG for 'bzr ci'
satisfy this use case?
--
bzr commit error because of no identity
https://bugs.launchpad.net/bugs/616878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
James Troup пишет:
> John A Meinel writes:
>
>>> (A per branch/checkout/whatever way to disable this error would be
>>> sufficient to downgrade this from a blocker on us upgrading to a simple
>>> annoyance.)
>> bzr whoami --branch
>>
>> Is a per-branch way to disable this error...
>
> I meant
** Tags added: affects-canonical
--
bzr commit error because of no identity
https://bugs.launchpad.net/bugs/616878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
John A Meinel writes:
>> (A per branch/checkout/whatever way to disable this error would be
>> sufficient to downgrade this from a blocker on us upgrading to a simple
>> annoyance.)
>
> bzr whoami --branch
>
> Is a per-branch way to disable this error...
I meant a way that works across all use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Troup wrote:
> John A Meinel writes:
>
>> I think downgrading it to a warning would be ok. I've noticed other
>> systems do the same thing.
>>
>> That said, if you are upgrading 400 machines to a newer version of bzr,
>> can't that same mechani
John A Meinel writes:
> I think downgrading it to a warning would be ok. I've noticed other
> systems do the same thing.
>
> That said, if you are upgrading 400 machines to a newer version of bzr,
> can't that same mechanism be used to call 'bzr whoami' one time on each
> of those machines?
Sure
Jelmer Vernooij <616...@bugs.launchpad.net> writes:
> On Thu, 2010-08-12 at 16:07 +, James Troup wrote:
>> Our use case is /etc in bzr. We don't care at all about having valid
>> email addresses in the bzr history for these branches. This change is
>> really problematic for us. We're either
I think downgrading it to a warning would be ok. I've noticed other
systems do the same thing.
That said, if you are upgrading 400 machines to a newer version of bzr,
can't that same mechanism be used to call 'bzr whoami' one time on each
of those machines? (It doesn't have to happen on every comm
On Thu, 2010-08-12 at 16:59 +, Parth Malwankar wrote:
> Maybe a option (bzr ci --guess-user|--guess-whoami) can be provided. I
> would prefer a new option to a warning as it would allow special cases
> to be handled explicitly and in the normal case the user won't need to
> commit uncommit -
Maybe a option (bzr ci --guess-user|--guess-whoami) can be provided. I
would prefer a new option to a warning as it would allow special cases
to be handled explicitly and in the normal case the user won't need to
commit uncommit - whoami - commit. Instead commit whoami
- commit sequence would re
On Thu, 2010-08-12 at 16:07 +, James Troup wrote:
> Our use case is /etc in bzr. We don't care at all about having valid
> email addresses in the bzr history for these branches. This change is
> really problematic for us. We're either going to have to patch it out
> or fix hundreds of machin
Our use case is /etc in bzr. We don't care at all about having valid
email addresses in the bzr history for these branches. This change is
really problematic for us. We're either going to have to patch it out
or fix hundreds of machines (either by running bzr whoami or setting
BZR_EMAIL with som
Warning the user when they do a commit while the username was guessed
seems like a good idea, in the same spirit as the --strict
warning/errors for "bzr push".
--
bzr commit error because of no identity
https://bugs.launchpad.net/bugs/616878
You received this bug notification because you are a me
Some users ended up doing commits with a committer email / hostname set
that was invalid or private. See bug 549310.
Other than running "bzr whoami", it should be possible to prevent this
error by setting the EMAIL or BZR_EMAIL environment variables. bzr
doesn't really care about whether those val
49 matches
Mail list logo
