Re: [leaf-devel] Update shorewall to version 4.5.x

2012-06-11 Thread KP Kirchdoerfer
Am 05.06.2012 10:40, schrieb Yves Blusseau: Le 04/06/2012 20:04, KP Kirchdoerfer a écrit : Hi Yves, Am 04.06.2012 19:33, schrieb Yves Blusseau: Hi all, i find a bug in the management of proxy NDP in shorewall 4.4.27.3 package. So do you think it's possible to merge the modifications done

[leaf-devel] Upgrade of uClibc

2012-06-11 Thread Yves Blusseau
Hi all, i'm trying to build a new package: ndppd (http://www.priv.nu/projects/ndppd/) but our uClibc (v 0.9.30.3) have one missing defined constant: ETHERTYPE_IPV6. This constant is in the /usr/include/net/ethernet.h. For the moment i made a patch to add this constant for ndppd, but i think it

Re: [leaf-devel] Upgrade of uClibc

2012-06-11 Thread Andrew
Hi. This is bad idea, it can break all userland that was compiled for older uClibc - so mixing different versions of base libs/compilers/kernels isn't good idea for minor releases. You can include new package into 5.x branch (I think we'll have first alpha in June/July), or you can try to patch

[leaf-devel] BuC-next: errors during build

2012-06-11 Thread Andrew
Hi all. I noticed that there are some packages that are built with errors. Some of them I fixed (for ex., shorewall6 - it installs init file as shorewall, not shorewall6, and so on), and some of them have unresolved dependencies (includes), among them - samba and librpcsecgss. Here are parts of

Re: [leaf-devel] BuC-next: errors during build

2012-06-11 Thread david M brooke
On 11 Jun 2012, at 17:49, Andrew wrote: Hi all. I noticed that there are some packages that are built with errors. Some of them I fixed (for ex., shorewall6 - it installs init file as shorewall, not shorewall6, and so on), and some of them have unresolved dependencies (includes), among

Re: [leaf-devel] Upgrade of uClibc

2012-06-11 Thread KP Kirchdoerfer
Am 11.06.2012 17:38, schrieb Andrew: Hi. This is bad idea, it can break all userland that was compiled for older uClibc - so mixing different versions of base libs/compilers/kernels isn't good idea for minor releases. You can include new package into 5.x branch (I think we'll have first