Steve Youngs | 10 Jul 15:04 2015
X-Face
Face

More build reports please.

If you're building SXEmacs, I, for one, would love to see your build
reports.

So build with: `make time-build-report'[1]

And then do: M-x build-rpt RET

All of the SXEmacs mailing lists will only accept posts from subscribers
so you _will_ have to subscribe to the sxemacs-builds list[2].  I know it
is a little inconvenient and I do apologise for that restriction, but
you know, spam and all that.  You can always subscribe and turn off
delivery if you'd rather not get build reports sent to you.

Footnotes: 
[1]  Parallel builds are supported and encouraged because you shouldn't
     have to wait too long to get your SXE on!  So go nuts with your
     `-j', for whatever value "nuts" is to get optimal performance from
     your processor(s). :-)

[2]  http://lists.sxemacs.org/listinfo.cgi/sxemacs-builds-sxemacs.org

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 7 Jul 09:00 2015
X-Face
Face

New hook script in use

Hey Peeps!

I've discovered a new post-receive git hook script.  It's called
"git-multimail" and is bundled with git these days.  However the dev
version could be better suited to us (well, you).  It allows setting
some regexps to include/exclude send/nosend which may be just what we've
been looking for to keep those unnecessary mails hitting the lists.

This hook is written in python and can either be called directly or
imported as a module into another python script.  Being able to do the
latter means you can pretty much make it do whatever the hell you want
it to without having to hack the script itself.  That's a win. :-)

  git clone https://github.com/git-multimail/git-multimail

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Steve Youngs | 27 Jun 08:16 2015

[Update] SXEmacs annotated tag devkey.HGB created. c897881f0a829b154d7e6701dff29d7441071fe9

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SXEmacs".

The annotated tag, devkey.HGB has been created
        at  c897881f0a829b154d7e6701dff29d7441071fe9 (tag)
   tagging  8fb2653c83b4f6cf224ba185639e7970e4306a75 (blob)
    length  4794 bytes
 tagged by  Horst G. Burkhardt
        on  Sat Jun 27 14:04:30 2015 +1000

- Log -----------------------------------------------------------------
Developer Key -- Horst G. Burkhardt

This is the GnuPG key used by Horst G. Burkhardt <mc <at> 680x0.com>
to sign commits, merges, and tags in this repository.

You may import this key into your GnuPG keyring with...

  'git show devkey.HGB | gpg --import'

To verify signed objects in the repo, use the '--show-signature'
option with the git-log and git-show commands.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJVjiDOAAoJEO3UDblgilKYnsYP/jEeLBS66VPS+wET52Cvda/P
bhsn/kq6bSmnd+P3bg/KlSiWs4/Nq4RaKa7z8uAtDFHQ+ulCFbE6dBVm++v6WzlO
XLHPNxO0Ci4j1hLp63SWD0jyXtY5SEjHJSacSN8/CJJch1Jj1Z0k1zq8NL8KmbVy
yFa/6Y/NnoYIIWTiLZrU4dYE1oRaB4Iiey/FOi5EimxkzfK1B8sEHIyM7MfTS2CA
(Continue reading)

Steve Youngs | 27 Jun 08:16 2015

[Update] SXEmacs annotated tag devkey.SY created. ed70f6fbb723ee769f40d8a7524ca12c1c29296c

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SXEmacs".

The annotated tag, devkey.SY has been created
        at  ed70f6fbb723ee769f40d8a7524ca12c1c29296c (tag)
   tagging  c098eec26fe14c698c6459e5d21677d31e3178c3 (blob)
    length  11745 bytes
 tagged by  Steve Youngs
        on  Wed Jun 10 18:05:44 2015 +1000

- Log -----------------------------------------------------------------
Developer Key -- Steve Youngs

This is the GnuPG key used by Steve Youngs <steve <at> sxemacs.org>
to sign commits, merges, and tags in this repository.

You may import this key into your GnuPG keyring with...

  'git show devkey.SY | gpg --import'

To verify signed objects in the repo, use the '--show-signature'
option with the git-log and git-show commands.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: The SXEmacs Project <http://www.sxemacs.org/>
Comment: EMchat - The SXEmacs IM client <http://www.emchat.org/>
Comment: SYcom <http://www.steveyoungs.com/>
Comment: the Reading Lamp <http://www.thereadinglamp.net/>

(Continue reading)

Steve Youngs | 26 Jun 04:23 2015
X-Face
Face

State of The SXEmacs

Hey Everyone!

OK, so it's probably about time we had a release.  Yeah, yeah, I know,
it's only been a couple of years since the last one, why so soon? :-)

When?  I have no exact date/time in mind, but it won't be tooooo far
aways (coupla weeks maybe, or sooner all going well).  But before I'm
ready, I need to tick a few things off of my SXEmacs todo.

Way back when we had our last release I had grand plans for doing all
kinds of wonderful things to SXEmacs.  My howm todos and notes filled up
like you wouldn't believe.  And then... well, dunno what happened
really, but suffice to say that most of "the things" are still undone.
Now, if I wait until I've cleared everything before I release, your
grandchildren will still be using v22.1.15, so I've reduced my list to a
couple of items, moving everything else to the future.

Here are the things I need to finish up before I'm ready for release.

  1) Disable dbus in configure so we're not building a useless
     non-functional emodule.  Please note that this is a temporary
     thing.  It is only so people won't be disappointed/annoyed at
     seeing "dbus" being detected and not being able to use it.  I fully
     intend to bring dbus to SXEmacs in the next release cycle.

  2) Clean up as much of the compiler (gcc) warnings as I can.  Most of
     the warnings I see will disappear once I turn off dbus so I don't
     expect this to be all that big or time consuming.

  3) FFmpeg media backend.  This is the big/hard one for me.  I want our
(Continue reading)

issue-tracking | 25 Jun 03:05 2015

[Bug 168] New: pdump causes segfault under OpenBSD during compile

Bug ID Summary Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
168
pdump causes segfault under OpenBSD during compile
SXEmacs
22.1.15
PC
BSD
NEW
major
P5
Compile/Install
steve <at> sxemacs.org
horst <at> sxemacs.org
sxemacs-devel <at> sxemacs.org

Attempting to compile on OpenBSD, the build fails as shown for make target sxemacs.dmp : Loading site-load... Finding pointers to doc strings... Note: Strange doc (not fboundp) for function root <at> 461099 Finding pointers to doc strings...done Dumping under the name sxemacs.dmp /home/burkhardth/sxemacs/=build/src/.libs/sxemacs:/usr/local/lib/libcompface.so.1.0: /usr/local/lib/libmp3lame.so.2.1 : WARNING: symbol(freqs) size mismatch, relink your program /usr/local/bin/bash: line 14: 6632 Segmentation fault (core dumped) DYLD_LIBRARY_PATH=.:./.libs:../src/ui/lwlib:../src/ui/lwlib/.libs:/opt/sxemacs/lib:$DYLD_LIBRARY_PATH: LD_LIBRARY_PATH=.:./.libs:../src/ui/lwlib:../src/ui/lwlib/.libs:/opt/sxemacs/lib:$LD_LIBRARY_PATH: SHLIB_PATH=.:./.libs:../src/ui/lwlib:../src/ui/lwlib/.libs:/opt/sxemacs/lib:$SHLIB_PATH: SOURCE_TREE_ROOT= BUILD_TREE_ROOT= ./sxemacs -batch -l shadow -f list-load-path-shadows Makefile:2538: recipe for target 'sxemacs.dmp' failed gmake[3]: *** [sxemacs.dmp] Error 139 gmake[3]: Leaving directory '/home/burkhardth/sxemacs/=build/src' Makefile:2207: recipe for target 'all-recursive' failed gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory '/home/burkhardth/sxemacs/=build/src' Makefile:881: recipe for target 'all' failed gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory '/home/burkhardth/sxemacs/=build/src' Makefile:818: recipe for target 'all-recursive' failed gmake: *** [all-recursive] Error 1 gdb shows that this error occurs in the portable dumper, but is not terribly helpful otherwise: #0 0x1ad44a17 in pdump_load () from /home/burkhardth/sxemacs/=build/src/.libs/sxemacs #1 0x1ac7ddeb in sxemacs_v22_1_15_173_g9706bca_pentiumm_unknown_openbsd5_7 () from /home/burkhardth/sxemacs/=build/src/.libs/sxemacs #2 0x1ac7e204 in main () from /home/burkhardth/sxemacs/=build/src/.libs/sxemacs This is specific to OpenBSD as far as I can tell, FreeBSD doesn't produce the same error, and I haven't tested NetBSD yet but will report back.
You are receiving this mail because:
  • You are the QA Contact for the bug.
issue-tracking | 21 Jun 10:45 2015

[Bug 167] New: lisp-initd won't byte-complile init.d.el if howm-mode is active

Bug ID Summary Product Version Hardware OS Status Severity Priority Component Assignee Reporter QA Contact
167
lisp-initd won't byte-complile init.d.el if howm-mode is active
SXEmacs
22.1.15
PC
Linux
NEW
trivial
P5
Core Lisp
njsf <at> sxemacs.org
steve <at> sxemacs.org
sxemacs-devel <at> sxemacs.org

(defun turn-on-howm-mode () (turn-on-font-lock) (howm-mode 1)) (add-hook 'emacs-lisp-mode-hook #'turn-on-howm-mode) That will prevent lisp-initd from byte-compiling your init.d.el file. Calling #'byte-compile-file interactively on an elisp file later on is not affected if howm-mode is on or off. I've worked around this in my local settings by simply moving the #'add-hook into my init.el _after_ #'lisp-initd-compile-and-load. So I'm not overly concerned about this. Nelson, I'll leave it up to you, but I'm happy for this to be marked "Resolved/Wontfix" or similar. I am wondering though if it might be useful for lisp-initd to have some hooks that could be run before/after it does its thing? I also wonder if that'd be worth the effort. :-)
You are receiving this mail because:
  • You are the QA Contact for the bug.
Steve Youngs | 13 Jun 07:03 2015
X-Face
Face

New snapshots available -- v22.1.15p168

Hey Everyone!

I'm currently uploading new snapshot tarballs (will probably be there by
the time you read this).

Get em while they're hot...

        http://downloads.sxemacs.org/snapshots/

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|
Nelson Ferreira | 9 Jun 15:06 2015
Picon

Fwd: autoconf failed at

Forwarding to the devel list

---------- Forwarded message ----------
From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
Date: Tue, Jun 9, 2015 at 7:45 AM
Subject: Re: autoconf failed at
To: Nelson Ferreira <nelson.ferreira <at> ieee.org>



Am 08.06.2015 um 21:57 schrieb Nelson Ferreira:
On Mon, Jun 8, 2015 at 3:18 PM, Andreas Röhler
<andreas.roehler <at> easy-emacs.de> wrote:
Am 08.06.2015 um 16:30 schrieb Nelson Ferreira:
...
After installing libtool configure worked.

However make -k ends with some error "could not update target" or so.

Seeing a sxemacs.dmp in directory src. An executable sxemacs displays some
frame but hangs.

Any info I may send?
I'd ask you to rebuild with:

     SRCDIR=`pwd`
     HAMMER=1 ./autogen.sh
     # if you do build dir != source dir change to build dir
     $SRCDIR/configure <your options>
     make time-build-report

This will generate a bunch of files that contrib/tar-build-failure.sh
will tar up.
Send that tar

attached

BTW do you need the real user-name, real hostname delivered by this script?

Attachment (build-failure.tar.gz): application/gzip, 314 KiB
Steve Youngs | 7 Jun 17:06 2015

[Update] SXEmacs annotated tag devkey.NF created. d059fa4bb1ebf6b4d89579f8bb36a483df2ed6bb

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "SXEmacs".

The annotated tag, devkey.NF has been created
        at  d059fa4bb1ebf6b4d89579f8bb36a483df2ed6bb (tag)
   tagging  4dac805833e498844f67eb37c91a2786516e189c (blob)
    length  2900 bytes
 tagged by  Nelson Ferreira
        on  Sun Jun 7 09:57:02 2015 -0400

- Log -----------------------------------------------------------------
PGP Key for Nelson Ferreira <njsf <at> sxemacs.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iD8DBQBVdE3bPGQXiXQg7SARAgO8AJ9M9CwjUV4NIfH5ST/D3+PazYNCDQCcDy86
dZRITFf7umeDlSNPMI3J9+o=
=xPH/
-----END PGP SIGNATURE-----

-----------------------------------------------------------------------

hooks/post-receive
--

-- 
SXEmacs

Steve Youngs | 7 Jun 08:36 2015
X-Face
Face

GnuPG signing all the things

Hey-Ho!

When we first started using git the only thing you could sign were tags.
That was a bit of a let down for me because back in the day when we were
using tla, pretty much everything was signed.

That was then.

A few weeks ago I updated my git (I have v2.4.0 now) and discovered that
you can now sign, not only tags, but commits and merges as well.  Whee!!
As soon as I learned of this, I jumped in and...

  git config --global commit.gpgSign true [1]

For merges I use `git merge -S...', however I only sign merges going
into master.  So if I'm hacking on something in a sub-sub-sub-branch
somewhere I won't sign the merges up to the "topic" branch, just when I
merge that into master.  All of the commits along the way would have
been signed anyway.

Verifying the things:

  git log --show-signature
  git show --show-signature
  git tag -v

If you do `git log --show-signature' on my repo you'll see that the last
few commits (including merge commits) I've done have been signed.

I'd like us all to start signing our commits.  At this stage, at least,
I'm not going to make it mandatory, but I'll be strongly encouraging
(nagging?) you to do so.

If you guys are on board with signing your stuff (to be honest, I can't
think why you wouldn't be), I'd like to add your keys to the repo in the
same fashion as how I did mine[2].  The following one-liner is all you
need to do to get your key into the repo (don't blindly kill/yank it, my
key is already in the repo :-P)...

  git tag -s devkey.SY \
    $(gpg --armor --export steve <at> sxemacs.org|git hash-object -w --stdin)

That will drop you in your editor (gnuclient, right!?) to add a log
message.

,----[ Example log message ]
| This is the GnuPG key used by Steve Youngs <steve <at> sxemacs.org> to sign
| commits, merges, and tags in this repository.
| 
| You may import this key into your GnuPG keyring with...
| 
|   `git show devkey.SY | gpg --import'
| 
| To verify signed objects in the repo, use the `--show-signature'
| option with the git-log and git-show commands.
`----

Then push it to your remote with...

  git push --tags myremote [3]

Let me know you've done it, so I can then fetch the tag into my repo.

Please use the naming convention of "devkey.$INITIALS" to keep things
nice and neat.

I do not know if it is possible to posthumously sign the commits already
in the repo.  I'll research it, and if it turns out to be trivial and
risk free I may do so, otherwise... nope, not gonna worry about it.

I'm going to add all of this to the SPPM.

Nelson, it might be nice for contrib/git-for-steve.sh to include this
too?

Have fun, guys!

Footnotes: 
[1]  If git can't find the right key, you can set `user.signingKey'

[2]  See: `git show maintainer-pgp'

[3]  That will push _all_ of your tags, so if you are in the habit of
     adding your own private tags in your WDs it might be better to push
     _just_ the devkey.$INITIALS with: `git push myremote
     devkey.$INITIALS'.  But I'll delete any private tags to leak through.

--

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve <at> sxemacs.org>---|

Gmane