Jul 18 2017
01:34 AM archivist: jepler, can you fix the bot name so it is not so long, I see no need for the channel name in its name
07:24 AM jepler: archivist: no, I have no control over the bot name.
07:38 AM archivist: odd
07:42 AM Tom_L: b-bot
08:09 AM jepler: In irssi with the default theme, the bot's announcements (which are a NOTICE in IRC terms) look like: -linuxcnc-github:#linuxcnc-devel- followed by the text of the notice itself
08:10 AM jepler: but the notice goes to the channel window
08:10 AM jepler: so the :#linuxcnc-devel portion is redundant
08:10 AM jepler: anyway, in irssi you can customize how a notice is displayed, for instance by setting pubnotice_channel = ""; in default.theme
08:11 AM jepler: but the actual bot name, linuxcnc-github, is simply set from the project name on github, and the initial [linuxcnc] in the message text says which of the many repositories within that project the message is related to
08:11 AM jepler: I know you have said in the past that you use xchat, and I was unable to find documentation on whether the appearance of notice messages can be customized in xchat in this way.
08:11 AM jepler: 4.10 Print Events
08:11 AM jepler: As of 0.9.7 you can now change XChat's output strings. Open up Settings - Edit Event Texts to display the current settings.
08:12 AM jepler: you might investigate these settings though
08:12 AM jepler: archivist: ^
08:12 AM jepler: afk
08:16 AM archivist: if I do that, it would screw up freenode notices too
08:34 AM jepler: again I don't know about xchat but having made that first setting about how notices to channels look, a private notice to me still shows plenty of relevant info, viz.: [freenode] -jepler(~firstname.lastname@example.org)- test
08:35 AM jepler: obviously I can't test wallops ;-)
08:35 AM archivist: it seems the wrong fix to me
08:37 AM jepler: .. so it looks like the similar setting in xchat is Channel Notice, by changing "$1/$2" to just "$1" makes a channel notice shorter by omitting the channel name
08:37 AM cradek: From: Jeff Epler <email@example.com>
08:38 AM cradek: jepler: I like having the real name in there, but I guess I agree we probably shouldn't use the full emails.
08:38 AM cradek: I'm not entirely sure why I think that, though
08:39 AM jepler: " send_from_author uses the commit author email address in the From address of the email.
08:39 AM jepler: "
08:39 AM archivist: $1 is the from, $2 is the message
08:42 AM jepler: in "Edit Events" when I click the row "Channel Notice" the table at the bottom states that $2 is "The Channel it's going to", $3 is "the message". The meaning of $-Number is different per message. Or maybe it's different in your version; I have xchat 2.8.8.
08:45 AM archivist: yes I agree, I was looking at notice not channel notice
08:47 AM jepler: cradek: I get a scary message when pushing to glo, but it doesn't appear to be fatal
08:47 AM jepler: remote: Transport error: 500 Can't connect to localhost:9999 (Invalid argument)
08:47 AM jepler: remote: Unable to relay message. All servers failed
08:48 AM jepler: cradek: yes, with "send_from_author" set, it uses the whole committer (or maybe author) name and e-mail address in the From: line, so that push just came back out in e-mail with the header From: Jeff Epler <firstname.lastname@example.org>
08:48 AM jepler: I don't think we can use that setting with our mailing list, unless we can use the Approved: header
08:49 AM jepler: some mailman documentation implies that Mailman supports the Approved: header, so it might be worth looking for it
08:53 AM cradek: oops that's the kgb hook I bet
08:56 AM cradek: > As a result of the latest electronic messaging and privacy requirements around the world, SourceForge has implemented a number of changes that affect email privacy. One part of this is that it is no longer possible for project admins to view the member emails of their mailing lists. If you need to make changes to a mailing list's members, please let our support staff know about it.
08:56 AM cradek: oh jeez
08:56 AM cradek: this is going to be worse than it was
08:58 AM cradek: apparently I can no longer moderate or unsubscribe someone
09:00 AM cradek: I can't figure out how to subscribe an address
09:44 AM cradek: jepler: ok I can subscribe that address, but I can no longer set the "temporarily don't send messages to me" bit for it
09:45 AM cradek: I set it to "require approval [only]" and tried to subscribe it, but that didn't work
09:45 AM cradek: it said it sent a confirmation email anyway
09:50 AM jepler: cradek: email@example.com ?
09:51 AM cradek: yes
09:52 AM cradek: also I unhooked kgb
09:52 AM cradek: hey I already got one
09:52 AM jepler: that had the "send from author" flag turned on, I've turned it off again because I don't know how it'll interact with spf/dmarc/etc
09:53 AM cradek: I got spf=pass but I don't dmarc
10:08 AM skunkworks_: does github have a mailing list :)
10:09 AM jepler: skunkworks_: no, but we can use issues instead of a forum
10:09 AM jepler: github.com/linuxcnc/forum/issues
11:00 AM linuxcnc-build_: build #164 of 4025.deb-jessie-armhf is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4025.deb-jessie-armhf/builds/164 blamelist: Jeff Epler <firstname.lastname@example.org>
11:37 AM seb_kuzminsky: asciidoc: include: /tmp/buildd/linuxcnc-2.8.0~pre1.3265.ge200479/docs/src/common/gpld-copyrighSegmentation fault
11:38 AM seb_kuzminsky: when i get home i'll swap the wheezy-armhf and the jessie-armhf SD cards and see if the problem follows the SD card or stays with the U3 board
11:57 AM jepler: good idea
02:14 PM linuxcnc-build_: build #35 of 4030.deb-stretch-rtpreempt-i386 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4030.deb-stretch-rtpreempt-i386/builds/35 blamelist: chris morley <email@example.com>, Chris Morley <firstname.lastname@example.org>
02:22 PM linuxcnc-build_: build #35 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4031.deb-stretch-rtpreempt-amd64/builds/35 blamelist: chris morley <email@example.com>, Chris Morley <firstname.lastname@example.org>
02:41 PM jepler: > a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl
02:42 PM jepler: is this based on an old tree without a right debian/configure?
03:37 PM seb_kuzminsky: it's gladevcp_gtk3 (9a116cf0a1407f) so maybe?
03:39 PM seb_kuzminsky: yes, gladevcp_gtk3 doesn't include f5e0a5b78e01317cb2ef1d81fd3434837ce9b606, which fixes that docs build error
05:51 PM andypugh: Ah, is this a side-effect of not using glo any more?
05:53 PM seb_kuzminsky: that's the github irc announcer thingy jepler set up
05:53 PM andypugh: I am wondering why “cradek” pushed the new commit?
05:54 PM seb_kuzminsky: oh
05:54 PM seb_kuzminsky: that's because you pushed to glo, and cradek runs a cronjob or something on glo that pushes everything to github
05:55 PM seb_kuzminsky: he's the pusher, but you're still the author and committer of the commits
05:55 PM seb_kuzminsky: it's always been that way, it's just more obvious now that the github irc squawker is here
05:57 PM seb_kuzminsky: it would be nice if there was a url to click on in these github issue & push announcements
08:43 PM seb_kuzminsky: the armhf buildslaves had a head transplant
08:43 PM seb_kuzminsky: linuxcnc-build_: force build --branch=2.7 0000.checkin
08:43 PM linuxcnc-build_: build forced [ETA 1h45m08s]
08:43 PM linuxcnc-build_: I'll give a shout when the build finishes
10:57 PM seb_kuzminsky: wonder if that will work
11:04 PM cradek: whoah a release!
11:38 PM seb_kuzminsky: but will the buildbot built it?
11:42 PM cradek: I hope so...
11:43 PM linuxcnc-build_: Hey! build 0000.checkin #5062 is complete: Success [3build successful]
11:43 PM linuxcnc-build_: Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5062