Hey guys,
I got 3 important mails from Jud <jud@judfilm.net>. I actually liked
the work he put into it, and have included the messages below.

Jud, if you are willing to do this kind of work and keep up to date on
these things, I will gladly give you write access to arch-dev-public
to keep us on the ball here. Let me know.

Anyone willing to step up to the plate for any of these (especially
tomk's packages)? I know some of them have already been addressed.

---------- Forwarded message ----------
Subject: Stalled Testing Packages 20080917

nasm 2.01-1
bluez 4.1-1
miro 1.2.7-1
policykit 0.9-2
tor 0.2.0.30-1
gnash-common 0.8.3-4
smc 1.5-1
python-vpython 3.2.9-4
boost 1.35.0-1
mkpxelinux 2008.03-1
mksyslinux 2008.03-1



---------- Forwarded message ----------
Subject: Core Packages Updates 20080917

Packages in question (with latest stable version):

Tom - tom@archlinux.org
e2fsprogs 1.41.1
dhcpcd 4.0.1
nfs-utils 1.1.3
bridge-utils 1.4 new url www.linuxfoundation.org/en/Net:Bridge
libevent 1.4.7
nfsidmap 0.21
libldap 2.4.11

Thomas - thomas@archlinux.org
lvm 2.02.39
device-mapper 1.02.27
fuse 2.7.4
iptables 1.4.1.1



---------- Forwarded message ----------
Subject: Core Packages with No Maintainer 20080917

Sorry to bother you with this but I noticed that the Core package:
linux-atm is listed without a maintainer. According the the PKGBUILD
Tobias Powalowski <tpowa@archlinux.org> is listed as the maintainer.


linux-atm 2.5.0
Changes: Version 2.4.1 to 2.5.0 (30-DEC-2007)

Bug fixes
---------
- building outside the source tree should now work properly
- TimeTicks (in ilmid) should be unsigned
- fix zeppelin's handling of LE_ARP REMOTE_ADDRESS flag

New features
------------
- zeppelin now has a -b option (run in background)
- zeppelin creates /var/run/lec[itf].pid at startup
- ilmid updates from ekinzie@cmf.nrl.navy.mil
- atmswitch from eleblond@init-sys.com
- point to multipoint signalling support
- routed br2684 support from ekinzie@cmf.nrl.navy.mil

Other changes
-------------
- updated to support later versions of autoconf

On Thu, Sep 25, 2008 at 7:41 AM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> Anyone willing to step up to the plate for any of these (especially
> tomk's packages)? I know some of them have already been addressed.
>

Sure I can do so today. But remember I can only push them to testing
and not send them to core thereafter unless you give me core acess
IIRC.


>
> Tom - tom@archlinux.org
> e2fsprogs 1.41.1
> dhcpcd 4.0.1
> nfs-utils 1.1.3
> bridge-utils 1.4 new url www.linuxfoundation.org/en/Net:Bridge
> libevent 1.4.7
> nfsidmap 0.21
> libldap 2.4.11
>



> miro 1.2.7-1
> boost 1.35.0-1

what is the status on boost 1.36.0? Do we still need additionally
rebuilds Kevin?

Ronald

Aaron Griffin schrieb:

Hey guys,
I got 3 important mails from Jud <jud@judfilm.net>. I actually liked
the work he put into it, and have included the messages below.

Jud, if you are willing to do this kind of work and keep up to date on
these things, I will gladly give you write access to arch-dev-public
to keep us on the ball here. Let me know.


I'd appreciate it if you give Jud write access to this ML, as I can't
always respond to the personal E-Mails. I'd rather have his messages
sent here.



---------- Forwarded message ----------
Subject: Stalled Testing Packages 20080917

bluez 4.1-1


I don't really have time for bluez and I'd appreciate someone else
taking it. The problem with bluez 4 is that the DBUS interface is
incompatible to the DBUS interface in bluez 3, thus all applications
using it are broken (kdebluetooth4 for example).



---------- Forwarded message ----------
Subject: Core Packages Updates 20080917

Thomas - thomas@archlinux.org
lvm 2.02.39
device-mapper 1.02.27
fuse 2.7.4
iptables 1.4.1.1


I received an updated iptables PKGBUILD, but again had no time to look
at it yet. I actually updated device-mapper but couldn't resolve a
compile problem in lvm, now it's been sitting there.

On Thu, 2008-09-25 at 10:12 +0200, Thomas Bächler wrote:
> I don't really have time for bluez and I'd appreciate someone else
> taking it. The problem with bluez 4 is that the DBUS interface is
> incompatible to the DBUS interface in bluez 3, thus all applications
> using it are broken (kdebluetooth4 for example).

The solution for bluez4 is that redhat already converted their whole
distribution to it, so anything that breaks has patches at redhat.