> > Oh. I read “Forwarded: no” as “it should be forwarded, but it's not been > done yet”. In this case “Forwarded: not-needed” would be more adequate; or > even better, use “Origin: upstream”, and then you don't need Forwarded at > all.
Thank you for that. > > >>I didn't get answer to my question about mprotect(2): > >>>Shouldn't we run this code also on non-Linux architectures? At least > >>>on kfreebsd-amd64, heap is not executable by default, which is what > >>>this code is trying to work around. > > > >Yes, forgot to clear this. I am not sure I fully undestand. Crashme is > >built on all archs but this is probably not what you meant. > > > >Won't this conditional catch for kfreebsd-amd64 (defined(__FreeBSD__) > >compiler macro will catch it ? > > Nope, __FreeBSD__ is not defined on GNU/kFreeBSD, only on “true” FreeBSD > systems. > > Here's useful piece of documentation about porting to kFreeBSD: > http://glibc-bsd.alioth.debian.org/porting/PORTING > (the relvant section is “Add our system name to checks here and there”) > > Another problem on kFreeBSD is that I get this warning: > > crashme.c:758:17: warning: incompatible implicit declaration of built-in > function 'execlp' [enabled by default] > {status = execlp(cmd,cmd,nb,arg2,nt,arg4,arg5,subprocess_ind,NULL); > ^ It appears that package has been sponsored by Laszlo today, I will tackle porting problem when preparing 2.8.2 upstream release, meanwhile I will install kfreebsd vm. You mentioned earlier that 2.7 should be also uploaded to stable because of [1]. Could you please tell me, or point out a source of information, how this should be done ? Should I create a debian-stable branch and prepare a package release stable there (in changelog it should be stable instead of unstable). Or should I just use backporting procedures and upload to backports? [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749816 -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org