Bob Proulx wrote:
Glenn Morris wrote:
I think that may have removed the revision_history attribute that
bzr-hookless uses. It was deprecated in 2.5:
https://bugs.launchpad.net/bzr-hookless-email/+bug/988195
has a possible patch.
Thank you for doing that research! That is very
Date: Thu, 2 May 2013 00:30:10 -0600
From: Bob Proulx b...@proulx.com
Did you get any notifications from it?
Yes, 3 minutes before you sent this message. Does that sound right?
Thanks!
Bob Proulx wrote (on Thu, 2 May 2013 at 00:30 -0600):
I applied that patch. It didn't apply cleanly due to file
differences. I manually and rather mechanically patched the
rejections into the vcs.savannah copy of the file. I ran the hourly
cron script just now and if no output is good
Eli Zaretskii wrote:
Bob Proulx wrote:
Did you get any notifications from it?
Yes, 3 minutes before you sent this message. Does that sound right?
Yes. I ran it manually so I could see any output without waiting for
the cron mail to deliver it. Then sent that message.
I assume that
Glenn Morris wrote:
If you have time, would you be willing to try the patch from
https://bugs.launchpad.net/bzr-hookless-email/+bug/533009/comments/3
- msg.add_inline_attachment(diff_val, diff_name)
+ msg.add_inline_attachment(diff_val, diff_name, 'x-diff')
It is just a piece of trivia
Date: Thu, 2 May 2013 10:45:18 -0600
From: Bob Proulx b...@proulx.com
Cc: r...@gnu.org
I assume that means that all of the new commits that hadn't been
notified in the last couple of days all went out at that time?
A few minutes after that.
Thanks for all your hard work.
Bob Proulx wrote (on Thu, 2 May 2013 at 10:47 -0600):
I added that change to the script. I imagine we will need to wait
for the next commit before there is a notification. If you would
keep an eye open and report on the result that would be great.
Seems ok, thanks.
Glenn Morris wrote:
Bob Proulx wrote:
I added that change to the script. I imagine we will need to wait
for the next commit before there is a notification. If you would
keep an eye open and report on the result that would be great.
Seems ok, thanks.
Bob Proulx wrote:
/etc/cron.hourly/bzr_commit_mail_notification:
Traceback (most recent call last):
File /usr/src/bzr-hookless-email/bzr_hookless_email.py, line 328, in
module
main()
File /usr/src/bzr-hookless-email/bzr_hookless_email.py, line 79, in main
branch.update()
Glenn Morris wrote:
I'm pining for commit notifications...
Sorry!
Maybe try asking baz...@lists.canonical.com for help?
Karl suggested asking on gnu-prog-discuss.
They'll probably want to know what the versions of bzr etc were before
and after the upgrade.
Did you upgrade to bzr 2.6?
In
Bob Proulx wrote (on Wed, 1 May 2013 at 21:17 -0600):
In theory bzr wasn't upgraded. The package manager thinks it has
2.1.2-1 installed and there isn't an upgrade for it in Stable so there
shouldn't have been any changes. The log doesn't show any changes to
it. However bzr itself reports
Glenn Morris wrote:
Bob Proulx wrote:
In theory bzr wasn't upgraded. The package manager thinks it has
2.1.2-1 installed and there isn't an upgrade for it in Stable so there
shouldn't have been any changes. The log doesn't show any changes to
it. However bzr itself reports 2.6b2 so I
12 matches
Mail list logo
