j...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
> Manuel Giraud writes:
>
>> timo.my...@iki.fi (Timo Myyrä) writes:
>>
>>> I've noticed regression after updating emacs. In Gnus I browse through my
>>> mails with 'n'
>>> (gnus-summary-next-unread-article). When changing to next group using the
Hi,
just to clarify the current state of haskell ports (because it looks
like it's *not* obvious):
- lang/ghc and meta/haskell-platform are marked as BROKEN to avoid
error spam for package builders and to avoid trouble for people
using snapshot packages. it's just a harsh method to stop any
On Tue, Dec 02, 2014 at 09:43:54AM -0800, Ryan Freeman wrote:
> On Tue, Dec 02, 2014 at 09:41:03AM -0800, Ryan Freeman wrote:
> > Hey,
> >
> > Patch to update to chocolate-doom 2.1.0. Lots of fixes/enhancements, see:
> > https://github.com/chocolate-doom/chocolate-doom/releases/tag/chocolate-doom
Manuel Giraud writes:
> timo.my...@iki.fi (Timo Myyrä) writes:
>
>> I've noticed regression after updating emacs. In Gnus I browse through my
>> mails with 'n'
>> (gnus-summary-next-unread-article). When changing to next group using the 'n'
>> and first mail of next group is not selected. So if
Manuel Giraud writes:
> Manuel Giraud writes:
>
>> Sorry but I cannot help here (but I'm just going to use your version).
>
> Hi,
Hi Manuel,
> It seems that we should have this patch too:
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2014-10/msg01232.html
> because we are affected and it
On Tue, Dec 02, 2014 at 09:41:03AM -0800, Ryan Freeman wrote:
> Hey,
>
> Patch to update to chocolate-doom 2.1.0. Lots of fixes/enhancements, see:
> https://github.com/chocolate-doom/chocolate-doom/releases/tag/chocolate-doom-2.1.0
>
> Builds/runs fine on amd64, ok?
forgot the best part of the
Hey,
Patch to update to chocolate-doom 2.1.0. Lots of fixes/enhancements, see:
https://github.com/chocolate-doom/chocolate-doom/releases/tag/chocolate-doom-2.1.0
Builds/runs fine on amd64, ok?
Cheers,
-ryan
? chocolate-doom-2.1.0.diff
Index: Makefile
=
Manuel Giraud writes:
> Sorry but I cannot help here (but I'm just going to use your version).
Hi,
It seems that we should have this patch too:
https://lists.gnu.org/archive/html/bug-gnu-emacs/2014-10/msg01232.html
because we are affected and it is annoying.
--
Manuel Giraud
Stuart Henderson said:
> On 2014/12/02 09:41, Stuart Henderson wrote:
> > (except that OpenBSD doesn't run on systems where sizeof(char) != 1 ;)
>
> Oh I just spotted that was in the original files in cvs ;)
>
> 1.1 (sturm15-Feb-06): - if ( (logline_buffer=(char
> *)malloc(logline_
In my current i386 bulk build I'm seeing problems building emacs21 (both
no_x11 and gtk2 flavours). Failures seen so far look like this
LC_ALL=C ./temacs -batch -l loadup dump
Illegal instruction (core dumped)
or
LC_ALL=C ./temacs -batch -l loadup dump
Segmentation fault (core dumped)
I haven
On 2014/12/02 09:41, Stuart Henderson wrote:
> (except that OpenBSD doesn't run on systems where sizeof(char) != 1 ;)
Oh I just spotted that was in the original files in cvs ;)
1.1 (sturm15-Feb-06): -if ( (logline_buffer=(char
*)malloc(logline_buffer_size)) == NULL ) {
1.1
On 2014/11/30 18:03, Gökhan Güler wrote:
> Hello. I ported /security/logsurfer to 64-bit system a while ago and wanted
> to submit it to ports. However I don't have an account and I need help on
> submitting. I had to delete the OpenBSD system but I have patch files. Can
> anybody help and submit t
On 12/02/14 04:20, Otto Moerbeek wrote:
On Tue, Dec 02, 2014 at 03:48:35AM -0500, Brad Smith wrote:
On 12/02/14 03:40, Otto Moerbeek wrote:
It's better to read the 5.6 ini file...
-Otto
Nice catch! How long were you scratching your head wondering why it
wasn't doing what you expecte
On Tue, Dec 02, 2014 at 03:48:35AM -0500, Brad Smith wrote:
> On 12/02/14 03:40, Otto Moerbeek wrote:
> >It's better to read the 5.6 ini file...
> >
> > -Otto
>
> Nice catch! How long were you scratching your head wondering why it
> wasn't doing what you expected?
Nothing a little ktrace'ing
On 12/02/14 03:50, Stuart Henderson wrote:
On 2014/12/02 09:40, Otto Moerbeek wrote:
It's better to read the 5.6 ini file...
This also needs "REVISION-main=0" in lang/php/5.6/Makefile (putting it
with the PV= / V= lines is probably best), then it's OK sthen@
Well it would be -main, -fastcgi
On 2014/12/02 09:40, Otto Moerbeek wrote:
> It's better to read the 5.6 ini file...
This also needs "REVISION-main=0" in lang/php/5.6/Makefile (putting it
with the PV= / V= lines is probably best), then it's OK sthen@
> -Otto
>
> Index: patch-main_php_ini_c
> ==
On 12/02/14 03:40, Otto Moerbeek wrote:
It's better to read the 5.6 ini file...
-Otto
Nice catch! How long were you scratching your head wondering why it
wasn't doing what you expected?
OK.
I also noticed for the 5.3 / 5.4 ports that php_ini.c has ${PV} instead
of the hardcoded versi
It's better to read the 5.6 ini file...
-Otto
Index: patch-main_php_ini_c
===
RCS file: /cvs/ports/lang/php/5.6/patches/patch-main_php_ini_c,v
retrieving revision 1.1
diff -u -p -r1.1 patch-main_php_ini_c
--- patch-main_php_i
18 matches
Mail list logo
