From duncan.gibson at xs4all.nl  Sun Feb  8 21:15:29 2009
From: duncan.gibson at xs4all.nl (Duncan Gibson)
Date: Sun, 8 Feb 2009 21:15:29 +0100 (CET)
Subject: Module submission review script on doppio
Message-ID: <46014.82.93.24.95.1234124129.squirrel@webmail.xs4all.nl>


This week I've had problems with left-behind cruft in my moonbase.git, and
after much document searching and experimentation, I think I've found a
solution by adding some steps to my review/git workflow. Of course, I could
be wrong - I frequently am - so I've documented it all at
http://wiki.lunar-linux.org/index.php/Module_Submission_for_developers
and I look forward to your constructive criticism and comments :-)

Cheers
D.


From dennisveatch at bellsouth.net  Mon Feb 16 03:26:43 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Sun, 15 Feb 2009 21:26:43 -0500
Subject: [Lunar-commits] <moonbase> bluez: bring our bluetooth up to date
In-Reply-To: <20081218004108.5AD739B1B2@doppio.foo-projects.org>
References: <20081218004108.5AD739B1B2@doppio.foo-projects.org>
Message-ID: <200902152126.43722.dennisveatch@bellsouth.net>

On Thursday 27 November 2008 3:59:16 am Zachary McGrew wrote:
> commit 3417452636ebe2dbe40debbb176d5e2f42e6e3d3
> Author: Zachary McGrew <zmcgrew at lunar-linux.org>
> Date:   Thu Nov 27 00:59:16 2008 -0800
>
>     bluez: bring our bluetooth up to date
>
>     this includes removing old modules, and renaming the current ones to
> match the official naming scheme also added bluez-gnome
> ---
>  bluetooth/bluez-gnome/DEPENDS         |    5 +++++
>  bluetooth/bluez-gnome/DETAILS         |   12 ++++++++++++
>  bluetooth/bluez-libs/DETAILS          |   13 -------------
>  bluetooth/bluez-utils/BUILD           |   14 --------------
>  bluetooth/bluez-utils/DEPENDS         |    8 --------
>  bluetooth/bluez-utils/DETAILS         |   13 -------------
>  bluetooth/bluez-utils/init.d/btdund   |   12 ------------
>  bluetooth/bluez-utils/init.d/bthcid   |   13 -------------
>  bluetooth/bluez-utils/init.d/btrfcomm |   25 -------------------------
>  bluetooth/bluez-utils/init.d/btsdpd   |   12 ------------
>  bluetooth/bluez/BUILD                 |   14 ++++++++++++++
>  bluetooth/bluez/DEPENDS               |    4 ++++
>  bluetooth/bluez/DETAILS               |   13 +++++++++++++
>  13 files changed, 48 insertions(+), 110 deletions(-)
>
> diff --git a/bluetooth/bluez-gnome/DEPENDS b/bluetooth/bluez-gnome/DEPENDS
> new file mode 100644
> index 0000000..97da7f3
> --- /dev/null
> +++ b/bluetooth/bluez-gnome/DEPENDS
> @@ -0,0 +1,5 @@
> +depends GConf
> +depends gtk+-2
> +depends libnotify
> +depends bluez
> +depends perl
> diff --git a/bluetooth/bluez-gnome/DETAILS b/bluetooth/bluez-gnome/DETAILS
> new file mode 100644
> index 0000000..fbaa49c
> --- /dev/null
> +++ b/bluetooth/bluez-gnome/DETAILS
> @@ -0,0 +1,12 @@
> +          MODULE=bluez-gnome
> +         VERSION=1.8
> +          SOURCE=$MODULE-$VERSION.tar.bz2
> +      SOURCE_URL=http://www.kernel.org/pub/linux/bluetooth/
> +      SOURCE_VFY=sha1:c1b950b6d08ffda7095f1edb7ae4dd8c36bb4314
> +        WEB_SITE=http://www.bluez.org
> +         ENTERED=20030927
> +         UPDATED=20081126
> +           SHORT="Gnome bluetooth configuration"
> +cat << EOF
> +Gnome interface for bluetooth keyboard and mouse configuration
> +EOF
> diff --git a/bluetooth/bluez-libs/DETAILS b/bluetooth/bluez-libs/DETAILS
> deleted file mode 100644
> index 2a36865..0000000
> --- a/bluetooth/bluez-libs/DETAILS
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -          MODULE=bluez-libs
> -         VERSION=3.36
> -          SOURCE=$MODULE-$VERSION.tar.gz
> -      SOURCE_URL=http://bluez.sf.net/download/
> -      SOURCE_VFY=sha1:c181384485a2258deedba7f1347dd53c08a70b45
> -        WEB_SITE=http://www.bluez.org
> -         ENTERED=20030927
> -         UPDATED=20080812
> -           SHORT="support for core Bluetooth layers and protocols"
> -cat << EOF
> -BlueZ provides support for core Bluetooth layers and protocols. It is
> -flexible, efficient and modular implementation.
> -EOF
> diff --git a/bluetooth/bluez-utils/BUILD b/bluetooth/bluez-utils/BUILD
> deleted file mode 100644
> index 61f24cd..0000000
> --- a/bluetooth/bluez-utils/BUILD
> +++ /dev/null
> @@ -1,14 +0,0 @@
> -(
> -
> -   ./configure  --prefix=/usr           \
> -                --sysconfdir=/etc       \
> -                --mandir=/usr/man       \
> -                --localstatedir=/var    \
> -                --sbindir=/sbin         \
> -                --datadir=/usr/share    \
> -                --enable-all            \
> -                $OPTS                  &&
> -
> -    default_make
> -
> -) > $C_FIFO 2>&1
> diff --git a/bluetooth/bluez-utils/DEPENDS b/bluetooth/bluez-utils/DEPENDS
> deleted file mode 100644
> index 59c76d6..0000000
> --- a/bluetooth/bluez-utils/DEPENDS
> +++ /dev/null
> @@ -1,8 +0,0 @@
> -depends bluez-libs
> -
> -optional_depends "hal"          "--enable-hal"       "" "to enable hal
> support" -optional_depends "alsa-lib"     "--enable-alsa"      "" "to
> enable alsa sound support" -optional_depends "gstreamer-10"
> "--enable-gstreamer" "" "to enable gstreamer sound support"
> -optional_depends "cups"         "--enable-cups"      "" "to enable cups
> printing support" -optional_depends "pcmcia-cs"    "--enable-pcmcia"    ""
> "to enable pcmcia support, 2.4 kernels" -optional_depends "pcmciautils" 
> "--enable-pcmcia"    "" "to enable pcmcia support, 2.6 kernels" diff --git
> a/bluetooth/bluez-utils/DETAILS b/bluetooth/bluez-utils/DETAILS deleted
> file mode 100644
> index 35df92a..0000000
> --- a/bluetooth/bluez-utils/DETAILS
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -          MODULE=bluez-utils
> -         VERSION=3.36
> -          SOURCE=$MODULE-$VERSION.tar.gz
> -      SOURCE_URL=http://bluez.sf.net/download/
> -      SOURCE_VFY=sha1:f53ba1d17829df2c5933fe062d7f8fb1ab8c8e60
> -        WEB_SITE=http://www.bluez.org
> -         ENTERED=20030927
> -         UPDATED=20080812
> -           SHORT="support for core Bluetooth layers and protocols"
> -cat << EOF
> -BlueZ provides support for core Bluetooth layers and protocols. It is
> -flexible, efficient and modular implementation.
> -EOF
> diff --git a/bluetooth/bluez-utils/init.d/btdund
> b/bluetooth/bluez-utils/init.d/btdund deleted file mode 100755
> index 82254ed..0000000
> --- a/bluetooth/bluez-utils/init.d/btdund
> +++ /dev/null
> @@ -1,12 +0,0 @@
> -#!/bin/bash
> -#
> -# btdund Bluetooth DUND daemon
> -#
> -# chkconfig: 345 80 20
> -# description: SDP Bluetooth Daemon
> -# processname: dund
> -
> -ARGS="--listen -s --channel 1"
> -
> -. /lib/lsb/init-functions
> -
> diff --git a/bluetooth/bluez-utils/init.d/bthcid
> b/bluetooth/bluez-utils/init.d/bthcid deleted file mode 100755
> index 363d861..0000000
> --- a/bluetooth/bluez-utils/init.d/bthcid
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -#!/bin/bash
> -#
> -# bthcid Bluetooth HCI Daemon
> -#
> -# chkconfig: 345 80 20
> -# description: HCI Bluetooth Daemon
> -# processname: hcid
> -# config:      /etc/bluetooth/hcid.conf
> -
> -ARGS="-f /etc/bluetooth/hcid.conf"
> -
> -. /lib/lsb/init-functions
> -
> diff --git a/bluetooth/bluez-utils/init.d/btrfcomm
> b/bluetooth/bluez-utils/init.d/btrfcomm deleted file mode 100755
> index 8248547..0000000
> --- a/bluetooth/bluez-utils/init.d/btrfcomm
> +++ /dev/null
> @@ -1,25 +0,0 @@
> -#!/bin/bash
> -#
> -# bind bt rfcomm devices
> -#
> -# chkconfig: 345 80 20
> -# description: bind rfcomm devices
> -# processname: rfcomm
> -# config:      /etc/bluetooth/rfcomm.conf
> -
> -ARGS="-f /etc/bluetooth/rfcomm.conf"
> -
> -. /lib/lsb/init-functions
> -
> -case "$1" in
> -    start)
> -    /usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all
> -    ;;
> -    stop)
> -    /usr/bin/rfcomm release all > /dev/null 2>&1
> -    ;;
> -    *)
> -    echo "Usage: $0 {start|stop}"
> -    exit 1
> -    ;;
> -esac
> diff --git a/bluetooth/bluez-utils/init.d/btsdpd
> b/bluetooth/bluez-utils/init.d/btsdpd deleted file mode 100755
> index 3aaa417..0000000
> --- a/bluetooth/bluez-utils/init.d/btsdpd
> +++ /dev/null
> @@ -1,12 +0,0 @@
> -#!/bin/bash
> -#
> -# btsdpd Bluetooth SDP Daemon
> -#
> -# chkconfig: 345 80 20
> -# description: SDP Bluetooth Daemon
> -# processname: sdpd
> -
> -ARGS=""
> -
> -. /lib/lsb/init-functions
> -
> diff --git a/bluetooth/bluez/BUILD b/bluetooth/bluez/BUILD
> new file mode 100644
> index 0000000..39a9cf3
> --- /dev/null
> +++ b/bluetooth/bluez/BUILD
> @@ -0,0 +1,14 @@
> +(
> +
> +  OPTS+=" --enable-tools   \
> +          --enable-bccmd   \
> +          --enable-hid2hci \
> +          --enable-dfutool \
> +          --enable-hidd    \
> +          --enable-pand    \
> +          --enable-dund    \
> +          --enable-manpages"
> +
> +  default_build
> +
> +) > $C_FIFO 2>&1
> diff --git a/bluetooth/bluez/DEPENDS b/bluetooth/bluez/DEPENDS
> new file mode 100644
> index 0000000..9bf1dc9
> --- /dev/null
> +++ b/bluetooth/bluez/DEPENDS
> @@ -0,0 +1,4 @@
> +depends dbus-glib
> +optional_depends gstreamer-10
> +optional_depends cups "--enable-cups" "--disable-cups" \
> +                      "for CUPS printing support"
> diff --git a/bluetooth/bluez/DETAILS b/bluetooth/bluez/DETAILS
> new file mode 100644
> index 0000000..edf63b1
> --- /dev/null
> +++ b/bluetooth/bluez/DETAILS
> @@ -0,0 +1,13 @@
> +          MODULE=bluez
> +         VERSION=4.19
> +          SOURCE=$MODULE-$VERSION.tar.bz2
> +      SOURCE_URL=http://www.kernel.org/pub/linux/bluetooth/
> +      SOURCE_VFY=sha1:ee8a30822ca085fa54da01c3055e1bc5785d54a9
> +        WEB_SITE=http://www.bluez.org
> +         ENTERED=20030927
> +         UPDATED=20081126
> +           SHORT="support for core Bluetooth layers and protocols"
> +cat << EOF
> +BlueZ provides support for core Bluetooth layers and protocols. It is
> +flexible, efficient and modular implementation.
> +EOF

I have tested a patch that fixes (for the most part) the broken bluez in 
kde-4.2.0, and a bluetooth mouse now works. So I was wondering what other apps 
the blues-4.xx breaks. Additionally I have made additions to the BUILD and 
DEPENDS for blues-4.xx, and a working /etc/init.d/bluetoothd. The latter still 
needs a bit of a twiddle for lunar compliance, but it does work, basically its 
just a hack of the one from bluez.

-- 
You can tuna piano but you can't tune a fish.

http://www.lunar-linux.org/
It's worth the spin.

From zbiggy at o2.pl  Tue Feb 24 00:51:18 2009
From: zbiggy at o2.pl (Zbigniew Luszpinski)
Date: Tue, 24 Feb 2009 00:51:18 +0100
Subject: udev 138 present in zbiggy-WIP
Message-ID: <200902240051.18673.zbiggy@o2.pl>

Hello,

here:
http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=refs/heads/zbiggy-WIP
on my personal zbiggy-WIP branch there is recent udev 138 I wrote for myself.

If some brave testers will find it fully working we could think of moving it 
to production branch. Now udev 138 works for me.

have a nice day,
Zbigniew 'zbiggy' Luszpinski

From dennisveatch at bellsouth.net  Tue Feb 24 02:02:27 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Mon, 23 Feb 2009 20:02:27 -0500
Subject: udev 138 present in zbiggy-WIP
In-Reply-To: <200902240051.18673.zbiggy@o2.pl>
References: <200902240051.18673.zbiggy@o2.pl>
Message-ID: <200902232002.27585.dennisveatch@bellsouth.net>

On Monday 23 February 2009 6:51:18 pm Zbigniew Luszpinski wrote:
> Hello,
>
> here:
> http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=refs/heads/
>zbiggy-WIP on my personal zbiggy-WIP branch there is recent udev 138 I wrote
> for myself.
>
> If some brave testers will find it fully working we could think of moving
> it to production branch. Now udev 138 works for me.
>
> have a nice day,
> Zbigniew 'zbiggy' Luszpinski

Well your in luck, just got started rebuilding a box. So gave it a whirl. A 
successful reboot and no errors seen at that stage. One only curious thing I 
noticed in /var/log/messages. There was only one instance of udev starting and 
that was for 128, even though the box had been rebooted several times, and I 
had just barely gotten past the lunar rebuild part, recompile kernel, etc. I 
was expecting to see more than one. I mention that because a grep on messages 
after installing 138 and a reboot, there were no messages about udev 138 
starting. 
A  udev stop/start produced one. 

On a side note after starting udev, dmesg showed this;

udev: starting version 138
udev: deprecated sysfs layout; update the kernel or disable 
CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly

Right now your looking pretty good.

> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev


From zbiggy at o2.pl  Tue Feb 24 09:35:12 2009
From: zbiggy at o2.pl (=?UTF-8?Q?zbiggy?=)
Date: Tue, 24 Feb 2009 09:35:12 +0100
Subject: =?UTF-8?Q?Re:_udev_138_present_in_zbiggy-WIP?=
In-Reply-To: <200902232002.27585.dennisveatch@bellsouth.net>
References: <200902240051.18673.zbiggy@o2.pl>
	<200902232002.27585.dennisveatch@bellsouth.net>
Message-ID: <1e2d67bd.32b60000.49a3b140.ba439@o2.pl>




Dnia 24 lutego 2009 2:02 Dennis Veatch <dennisveatch at bellsouth.net> napisa?(a):

> On Monday 23 February 2009 6:51:18 pm Zbigniew Luszpinski wrote:
> > Hello,
> >
> > here:
> > http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=refs/heads/
> >zbiggy-WIP on my personal zbiggy-WIP branch there is recent udev 138 I wrote
> > for myself.
> >
> > If some brave testers will find it fully working we could think of moving
> > it to production branch. Now udev 138 works for me.
> >
> > have a nice day,
> > Zbigniew 'zbiggy' Luszpinski
> 
> Well your in luck, just got started rebuilding a box. So gave it a whirl. A 
> successful reboot and no errors seen at that stage. One only curious thing I 
> noticed in /var/log/messages. There was only one instance of udev starting and 
> that was for 128, even though the box had been rebooted several times, and I 
> had just barely gotten past the lunar rebuild part, recompile kernel, etc. I 
> was expecting to see more than one. I mention that because a grep on messages 
> after installing 138 and a reboot, there were no messages about udev 138 
> starting. 
> A  udev stop/start produced one. 
> 
> On a side note after starting udev, dmesg showed this;
> 
> udev: starting version 138
> udev: deprecated sysfs layout; update the kernel or disable 
> CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
> 
> Right now your looking pretty good.

Thanks for testing. When go back home will look for these. I will also downgrade udev to Lunar's current official and then update back to 138 to make sure some old files were not left on system. Also I will rethink if we should keep udev compat rules to keep compatibility with older kernels. Thanks for detailed report.

have a nice day,
Zbigniew 'zbiggy' Luszpinski


From dennisveatch at bellsouth.net  Tue Feb 24 12:19:10 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Tue, 24 Feb 2009 06:19:10 -0500
Subject: udev 138 present in zbiggy-WIP
In-Reply-To: <1e2d67bd.32b60000.49a3b140.ba439@o2.pl>
References: <200902240051.18673.zbiggy@o2.pl>
	<200902232002.27585.dennisveatch@bellsouth.net>
	<1e2d67bd.32b60000.49a3b140.ba439@o2.pl>
Message-ID: <200902240619.10357.dennisveatch@bellsouth.net>

On Tuesday 24 February 2009 3:35:12 am zbiggy wrote:
> Dnia 24 lutego 2009 2:02 Dennis Veatch <dennisveatch at bellsouth.net> 
napisa?(a):
> > On Monday 23 February 2009 6:51:18 pm Zbigniew Luszpinski wrote:
> > > Hello,
> > >
> > > here:
> > > http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=refs/he
> > >ads/ zbiggy-WIP on my personal zbiggy-WIP branch there is recent udev
> > > 138 I wrote for myself.
> > >
> > > If some brave testers will find it fully working we could think of
> > > moving it to production branch. Now udev 138 works for me.
> > >
> > > have a nice day,
> > > Zbigniew 'zbiggy' Luszpinski
> >
> > Well your in luck, just got started rebuilding a box. So gave it a whirl.
> > A successful reboot and no errors seen at that stage. One only curious
> > thing I noticed in /var/log/messages. There was only one instance of udev
> > starting and that was for 128, even though the box had been rebooted
> > several times, and I had just barely gotten past the lunar rebuild part,
> > recompile kernel, etc. I was expecting to see more than one. I mention
> > that because a grep on messages after installing 138 and a reboot, there
> > were no messages about udev 138 starting.
> > A  udev stop/start produced one.
> >
> > On a side note after starting udev, dmesg showed this;
> >
> > udev: starting version 138
> > udev: deprecated sysfs layout; update the kernel or disable
> > CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
> >
> > Right now your looking pretty good.
>
> Thanks for testing. When go back home will look for these. I will also
> downgrade udev to Lunar's current official and then update back to 138 to
> make sure some old files were not left on system. Also I will rethink if we
> should keep udev compat rules to keep compatibility with older kernels.
> Thanks for detailed report.
>
> have a nice day,
> Zbigniew 'zbiggy' Luszpinski
>

Actually, I think you could leave it as it is for now, and see what falls 
down. I normally have that CONFIG turned off, just forgot to do that. 

Dennis

From dennisveatch at bellsouth.net  Tue Feb 24 13:18:37 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Tue, 24 Feb 2009 07:18:37 -0500
Subject: udev 138 present in zbiggy-WIP- followup
In-Reply-To: <200902240619.10357.dennisveatch@bellsouth.net>
References: <200902240051.18673.zbiggy@o2.pl>
	<1e2d67bd.32b60000.49a3b140.ba439@o2.pl>
	<200902240619.10357.dennisveatch@bellsouth.net>
Message-ID: <200902240718.37736.dennisveatch@bellsouth.net>

On Tuesday 24 February 2009 6:19:10 am Dennis Veatch wrote:
> On Tuesday 24 February 2009 3:35:12 am zbiggy wrote:
> > Dnia 24 lutego 2009 2:02 Dennis Veatch <dennisveatch at bellsouth.net>
>
> napisa?(a):
> > > On Monday 23 February 2009 6:51:18 pm Zbigniew Luszpinski wrote:
> > > > Hello,
> > > >
> > > > here:
> > > > http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=refs/
> > > >he ads/ zbiggy-WIP on my personal zbiggy-WIP branch there is recent
> > > > udev 138 I wrote for myself.
> > > >
> > > > If some brave testers will find it fully working we could think of
> > > > moving it to production branch. Now udev 138 works for me.
> > > >
> > > > have a nice day,
> > > > Zbigniew 'zbiggy' Luszpinski
> > >
> > > Well your in luck, just got started rebuilding a box. So gave it a
> > > whirl. A successful reboot and no errors seen at that stage. One only
> > > curious thing I noticed in /var/log/messages. There was only one
> > > instance of udev starting and that was for 128, even though the box had
> > > been rebooted several times, and I had just barely gotten past the
> > > lunar rebuild part, recompile kernel, etc. I was expecting to see more
> > > than one. I mention that because a grep on messages after installing
> > > 138 and a reboot, there were no messages about udev 138 starting.
> > > A  udev stop/start produced one.
> > >
> > > On a side note after starting udev, dmesg showed this;
> > >
> > > udev: starting version 138
> > > udev: deprecated sysfs layout; update the kernel or disable
> > > CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
> > >
> > > Right now your looking pretty good.
> >
> > Thanks for testing. When go back home will look for these. I will also
> > downgrade udev to Lunar's current official and then update back to 138 to
> > make sure some old files were not left on system. Also I will rethink if
> > we should keep udev compat rules to keep compatibility with older
> > kernels. Thanks for detailed report.
> >
> > have a nice day,
> > Zbigniew 'zbiggy' Luszpinski
>
> Actually, I think you could leave it as it is for now, and see what falls
> down. I normally have that CONFIG turned off, just forgot to do that.
>
> Dennis
> _______________________________________________

Tried it on my T60+X1400+fglrx with CONFIG_SYSFS_DEPRECATED disabled, and 
another box with NVIDIA, and found no problems. To me those are a couple of 
the biggies.

Again just a minor thing with udev starting up, obviously 138 is working but 
not throwing that into /var/log/messages. Not big deal, but it would warm my 
fuzzies if a notification was given some where. 



From dennisveatch at bellsouth.net  Tue Feb 24 14:15:20 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Tue, 24 Feb 2009 08:15:20 -0500
Subject: udev 138 present in zbiggy-WIP- followup
In-Reply-To: <200902240718.37736.dennisveatch@bellsouth.net>
References: <200902240051.18673.zbiggy@o2.pl>
	<200902240619.10357.dennisveatch@bellsouth.net>
	<200902240718.37736.dennisveatch@bellsouth.net>
Message-ID: <200902240815.20614.dennisveatch@bellsouth.net>

On Tuesday 24 February 2009 7:18:37 am Dennis Veatch wrote:
> On Tuesday 24 February 2009 6:19:10 am Dennis Veatch wrote:
> > On Tuesday 24 February 2009 3:35:12 am zbiggy wrote:
> > > Dnia 24 lutego 2009 2:02 Dennis Veatch <dennisveatch at bellsouth.net>
> >
> > napisa?(a):
> > > > On Monday 23 February 2009 6:51:18 pm Zbigniew Luszpinski wrote:
> > > > > Hello,
> > > > >
> > > > > here:
> > > > > http://foo-projects.org/git/?p=zbiggy/moonbase.git;a=shortlog;h=ref
> > > > >s/ he ads/ zbiggy-WIP on my personal zbiggy-WIP branch there is
> > > > > recent udev 138 I wrote for myself.
> > > > >
> > > > > If some brave testers will find it fully working we could think of
> > > > > moving it to production branch. Now udev 138 works for me.
> > > > >
> > > > > have a nice day,
> > > > > Zbigniew 'zbiggy' Luszpinski
> > > >
> > > > Well your in luck, just got started rebuilding a box. So gave it a
> > > > whirl. A successful reboot and no errors seen at that stage. One only
> > > > curious thing I noticed in /var/log/messages. There was only one
> > > > instance of udev starting and that was for 128, even though the box
> > > > had been rebooted several times, and I had just barely gotten past
> > > > the lunar rebuild part, recompile kernel, etc. I was expecting to see
> > > > more than one. I mention that because a grep on messages after
> > > > installing 138 and a reboot, there were no messages about udev 138
> > > > starting. A  udev stop/start produced one.
> > > >
> > > > On a side note after starting udev, dmesg showed this;
> > > >
> > > > udev: starting version 138
> > > > udev: deprecated sysfs layout; update the kernel or disable
> > > > CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
> > > >
> > > > Right now your looking pretty good.
> > >
> > > Thanks for testing. When go back home will look for these. I will also
> > > downgrade udev to Lunar's current official and then update back to 138
> > > to make sure some old files were not left on system. Also I will
> > > rethink if we should keep udev compat rules to keep compatibility with
> > > older kernels. Thanks for detailed report.
> > >
> > > have a nice day,
> > > Zbigniew 'zbiggy' Luszpinski
> >
> > Actually, I think you could leave it as it is for now, and see what falls
> > down. I normally have that CONFIG turned off, just forgot to do that.
> >
> > Dennis
> > _______________________________________________
>
> Tried it on my T60+X1400+fglrx with CONFIG_SYSFS_DEPRECATED disabled, and
> another box with NVIDIA, and found no problems. To me those are a couple of
> the biggies.
>
> Again just a minor thing with udev starting up, obviously 138 is working
> but not throwing that into /var/log/messages. Not big deal, but it would
> warm my fuzzies if a notification was given some where.
>
>
> _______________________________________________


Oh, and you will want to do a `lunar fix hal`.


From duncan.gibson at xs4all.nl  Sat Feb 28 02:08:02 2009
From: duncan.gibson at xs4all.nl (Duncan Gibson)
Date: Sat, 28 Feb 2009 02:08:02 +0100 (CET)
Subject: Ohloh listing for Lunar Linux
Message-ID: <20098.82.93.24.95.1235783282.squirrel@webmail.xs4all.nl>

Did someone take active measures to register Lunar on Ohloh?

There don't appear to have been updates for months.
Could this be linked to the switch from svn to git?
See https://www.ohloh.net/p/9483 for details.

Does that same someone need to do something or contact Ohloh?
Or can anyone do it?

Cheers
D



From dennisveatch at bellsouth.net  Sat Feb 28 02:19:28 2009
From: dennisveatch at bellsouth.net (Dennis Veatch)
Date: Fri, 27 Feb 2009 20:19:28 -0500
Subject: Ohloh listing for Lunar Linux
In-Reply-To: <20098.82.93.24.95.1235783282.squirrel@webmail.xs4all.nl>
References: <20098.82.93.24.95.1235783282.squirrel@webmail.xs4all.nl>
Message-ID: <200902272019.28758.dennisveatch@bellsouth.net>

On Friday 27 February 2009 8:08:02 pm Duncan Gibson wrote:
> Did someone take active measures to register Lunar on Ohloh?
>
> There don't appear to have been updates for months.
> Could this be linked to the switch from svn to git?
> See https://www.ohloh.net/p/9483 for details.
>
> Does that same someone need to do something or contact Ohloh?
> Or can anyone do it?
>
> Cheers
> D
>

I have posted in their forums, twice, about their site not updating developer 
activity. But that was long ago, and I gave up on them.




From 0lvin at ukr.net  Sat Feb 28 11:21:05 2009
From: 0lvin at ukr.net (Denis)
Date: Sat, 28 Feb 2009 12:21:05 +0200
Subject: [Lunar-commits] <moonbase> Xfce 4.6.0 Squashed commit of
	thefollowing:
In-Reply-To: <20090228082500.2242DF4208@doppio.foo-projects.org>
Message-ID: <E1LdMJd-0002SS-Fx@ffe11.ukr.net>

Hello!      
      
I found little mistake in update for xfce-mixer: not exist depends from gstreamer-plugins-base and error in build and details file.      
      
This patch I think resolve this error(also I submit this changes to 'Lunar module submission queue'):      
      

diff a/xfce4/apps/xfce4-mixer b/xfce4/apps/xfce4-mixer
--- a/xfce4/apps/xfce4-mixer/BUILD        2009-02-28 10:54:46.000000000 +0200
+++ b/xfce4/apps/xfce4-mixer/BUILD       2009-02-28 11:55:29.000000000 +0200
@@ -9,9 +9,6 @@
                 --disable-static                                \
                 $OPTS                                           &&
 
-   # bug in 4.1.90
-   cp settings/stringlist.inc lib/                                &&-
    default_make
 
 ) > $C_FIFO 2>&1
--- a/xfce4/apps/xfce4-mixer/DEPENDS       2009-02-28 10:54:46.000000000 +0200
+++ b/xfce4/apps/xfce4-mixer/DEPENDS     2009-02-28 11:42:13.000000000 +0200
@@ -1 +1,2 @@
 depends xfce4-panel
+depends gst-plugins-base
\ No newline at end of file
--- a/xfce4/apps/xfce4-mixer/DETAILS        2009-02-28 10:54:46.000000000 +0200
+++ b/xfce4/apps/xfce4-mixer/DETAILS     2009-02-28 12:11:59.000000000 +0200
@@ -2,11 +2,11 @@
          VERSION=4.6.0
           SOURCE=$MODULE-$VERSION.tar.bz2
       SOURCE_URL=http://www.xfce.org/archive/xfce-$VERSION/src/
-      SOURCE_VFY=sha1:ebf035a32d8b7b84094b6477a916d692cfe6a6af
+      SOURCE_VFY=sha1:ebcbc2cefbd6f0a24c339d61bdb138e2bbe1335c
    MODULE_PREFIX=${XFCE4_PREFIX:-/usr}
         WEB_SITE=http://www.xfce.org
          ENTERED=20030715
-         UPDATED=20090227
+         UPDATED=20090228
            PSAFE=no
            SHORT="Volume control and mixer for the Xfce4 panel"
 cat << EOF
      Best regards,      
????????????????? Denis.      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20090228/4ef59287/attachment.html>

From samuel.verstraete at gmail.com  Sat Feb 28 12:55:49 2009
From: samuel.verstraete at gmail.com (samuel)
Date: Sat, 28 Feb 2009 12:55:49 +0100
Subject: [Lunar-commits] <moonbase> Xfce 4.6.0 Squashed commit of 
	thefollowing:
In-Reply-To: <E1LdMJd-0002SS-Fx@ffe11.ukr.net>
References: <20090228082500.2242DF4208@doppio.foo-projects.org>
	<E1LdMJd-0002SS-Fx@ffe11.ukr.net>
Message-ID: <bc122a250902280355q699b2e06pe93f70fd0cbfc711@mail.gmail.com>

2009/2/28 Denis <0lvin at ukr.net>:
> Hello!
>
> I found little mistake in update for xfce-mixer: not exist depends from
> gstreamer-plugins-base and error in build and details file.
>
> This patch I think resolve this error(also I submit this changes to 'Lunar
> module submission queue'):
>
> diff a/xfce4/apps/xfce4-mixer b/xfce4/apps/xfce4-mixer
>
> --- a/xfce4/apps/xfce4-mixer/BUILD        2009-02-28 10:54:46.000000000
> +0200
>
> +++ b/xfce4/apps/xfce4-mixer/BUILD       2009-02-28 11:55:29.000000000 +0200
>
> @@ -9,9 +9,6 @@
>
>                  --disable-static                                \
>
>                  $OPTS                                           &&
>
>
>
> -   # bug in 4.1.90
>
> -   cp settings/stringlist.inc lib/                                &&
> -
>
>     default_make
>
>
>
>  ) > $C_FIFO 2>&1
>
> --- a/xfce4/apps/xfce4-mixer/DEPENDS       2009-02-28 10:54:46.000000000
> +0200
>
> +++ b/xfce4/apps/xfce4-mixer/DEPENDS     2009-02-28 11:42:13.000000000 +0200
>
> @@ -1 +1,2 @@
>
>  depends xfce4-panel
>
> +depends gst-plugins-base
>
> \ No newline at end of file
>
> --- a/xfce4/apps/xfce4-mixer/DETAILS        2009-02-28 10:54:46.000000000
> +0200
>
> +++ b/xfce4/apps/xfce4-mixer/DETAILS     2009-02-28 12:11:59.000000000 +0200
>
> @@ -2,11 +2,11 @@
>
>           VERSION=4.6.0
>
>            SOURCE=$MODULE-$VERSION.tar.bz2
>
>        SOURCE_URL=http://www.xfce.org/archive/xfce-$VERSION/src/
>
> -      SOURCE_VFY=sha1:ebf035a32d8b7b84094b6477a916d692cfe6a6af
>
> +      SOURCE_VFY=sha1:ebcbc2cefbd6f0a24c339d61bdb138e2bbe1335c
>
>     MODULE_PREFIX=${XFCE4_PREFIX:-/usr}
>
>          WEB_SITE=http://www.xfce.org
>
>           ENTERED=20030715
>
> -         UPDATED=20090227
>
> +         UPDATED=20090228
>
>             PSAFE=no
>
>             SHORT="Volume control and mixer for the Xfce4 panel"
>
>  cat << EOF
>
>
> Best regards,
> ????????????????? Denis.
> _______________________________________________
> Lunar-commits mailing list
> Lunar-commits at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-commits
>
>

fixed, thnx
gr,S.