I'll try and get some stuff on the visual side of things done. I know
just saying it is not doing it, but I will try and dedicate as much time
as possible and help get 3.1 out.
Later,
User
>
> _| _|
> _| _| _|_| _|_|_| _|_| _| _|_|
> _| _| _| _| _| _|_|_|_| _|_|
> _| _| _| _| _| _| _|
> _| _|_| _|_|_| _|_|_| _|
> _|
> _|
>
>
apriori wrote:
> Hi all!
>
> I guess it's time that I show up here again. Well, about the release.. .I'll
> have time after the 31th of July - I won't have any time before that date.
> Nearly the whole semester now was unexpectedly 60h+/week work.
>
> Even though, in the few hours I had time to work on yoper I tried to update
> NetworkManager to 0.7, which itself has quite some new dependencies, e.g.
> PolicyKit. I'd need help to implement it successfully in yoper.
>
> About the packages mentioned:
> qt4 in dynamite was my testbuild of a very early snapshot of 4.4 and should
> not be used in any way - I've no idea about the others.
>
> Also I'd like to know wether Tobias was able to make any progess with kmix.
> If
> not, I'd suggest that I concentrate 1 week - and only 1 - on getting it into
> useful shape for a release (even if not 100% functional, but at least
> muting/volume control has to work).
>
> I'm really looking forward to continue working on yoper when I have time...
> especially lcc made some valuable progress and a first alpha might be ready
> for implementation within a month.
>
> Carlos and the others, thank you for pushing the wheel, I won't let you down
> -
> I just need some more time to come back into business.
>
> Best regards
>
> Armin
>
>> Hi guys!
>>
>> ----------------------------------------
>>
>>
>>> Date: Tue, 8 Jul 2008 08:54:49 +1200
>>> From: [EMAIL PROTECTED]
>>> To: yoper-dev@lists.yoper.com
>>> Subject: [yoper-dev] Getting 3.1 finally out
>>>
>>> Hi,
>>>
>>>
>>> Is it possible that we as a team can agree on a 2 week time frame for
>>> massively increased activity to get the 3.1 release done?
>>>
>>> On my personal to do list is
>>>
>>> 1) a new kernel
>>> 2) cleaning up pam
>>> 3) cleaning up ISO
>>>
>>> RC1 , 2 weeks feedback , release
>>>
>>> So what does the rest of the team think ? Getting this release out
>>> myself is almost impossible. We got to get this done together as a
>>> team.
>>>
>>> So when can we do this?
>>>
>> Well, I am lately having a bitter taste like of being quite alone in the
>> jungle, and well, it would be good to see a bit more activity around. I
>> don't know what each one personal / private life is going on, but we
>> definitely need to finish with this endless release. Just to put my two
>> pennies I would like to point out that we still have a few package not
>> migrated from Yoper 3.0. I think this will cause problems in systems (like
>> mine) that comes from Yoper 3.0 since many people will opt for upgrading to
>> Yoper 3.1 (something that most distros allow and Yoper should also do). I
>> have the next packages still from Yoper 3.0 (is any of the following
>> packages deprecated/unmaintained?):
>>
>> [EMAIL PROTECTED] ~ $ rpm -qa | grep yoper_3.0 | sort
>> compat-libstdc++-3.4.3-3.4.3-15._yoper_3.0_rocketfuel_
>> gnome-python-extras-2.19.1-1._yoper_3.0_dynamite_
>> gnome-python-gtkmozembed-2.19.1-1._yoper_3.0_dynamite_
>> grub-0.97-31._yoper_3.0_dynamite_
>> gtkglext-1.2.0-1._yoper_3.0_rocketfuel_
>> kchmviewer-1.3-4._yoper_3.0_rocketfuel_
>> kdebluetooth-1.0_beta2-5._yoper_3.0_rocketfuel_
>> kernel-2.6.21_yos-8-2.6.21-42._yoper_3.0_rocketfuel_
>> kernel-2.6.22_yos-50-2.6.22-50._yoper_3.0_dynamite_
>> kxgenerator-0.3.7-2._yoper_3.0_dynamite_
>> libselinux-1.22-7._yoper_3.0_rocketfuel_
>> libsoup-2.2.98-3._yoper_3.0_dynamite_
>> libtheora-1.0alpha7-11._yoper_3.0_rocketfuel_
>> ntp-date-4.2.2p1-9._yoper_3.0_rocketfuel_
>> qt4-4.4.4_20070908-16._yoper_3.0_dynamite_
>> qt4-designer-4.4.4_20070908-16._yoper_3.0_dynamite_
>> qt4-devel-4.4.4_20070908-16._yoper_3.0_dynamite_
>> sysklogd-1.4.1-11._yoper_3.0_rocketfuel_
>> xorg-x11-7.2-18._yoper_3.0_rocketfuel_
>> xsane-0.994-2._yoper_3.0_rocketfuel_
>>
>>
>> As I mentioned in my previous email, I think it would be needed to agree in
>> the group IDs for each application username. I have done an small search
>> that can shed a bit (although not much :D) here:
>>
>> [EMAIL PROTECTED] ~/svn/yoper/3.1/rocketfuel $ find -name '*.spec' -exec grep
>> -H groupadd '{}' ';' | sort ./avahi/avahi.spec:/usr/sbin/groupadd -g 70
>> avahi 2>/dev/null:
>> ./clamav/clamav.spec:groupadd -g %{freshclam_guid} -f
>> %{freshclam_group_n_user} ./cups/cups.spec:groupadd -f system
>> ./fcron/fcron.spec:/usr/sbin/groupadd -g 117 -f crontab 2>/dev/null ||:
>> ./hal/hal.spec:/usr/sbin/groupadd -g 51 hald 2>/dev/null ||:
>> ./lockdev/lockdev.spec:groupadd -g 54 -r -f lock>/dev/null ||:
>> ./mach-copy/mach.spec:groupadd -g 499 mach || :
>> ./mach/mach.spec:groupadd -g 38 mach>/dev/null 2>&1 || :
>> ./MAKEDEV/MAKEDEV.spec:Prereq: /usr/sbin/groupadd, /usr/sbin/useradd,
>> grep, mktemp ./MAKEDEV/MAKEDEV.spec:/usr/sbin/groupadd -g 19 floppy>
>> /dev/null 2>/dev/null || : ./netinitscripts/netinitscripts.spec:Prereq:
>> /sbin/chkconfig, /usr/sbin/groupadd, /bin/sed, coreutils
>> ./netinitscripts/netinitscripts.spec:/usr/sbin/groupadd -g 23 -f utmp
>> 2>/dev/null||: ./ntp/ntp.spec:PreReq: /sbin/chkconfig /usr/sbin/groupadd
>> /usr/sbin/useradd ./ntp/ntp.spec:/usr/sbin/groupadd -g 38 ntp 2> /dev/null
>> || :
>> ./openssh/openssh.spec:/usr/sbin/groupadd -g 30 admin 2>/dev/null ||:
>> ./postfix/postfix.spec:Requires(pre): %{_sbindir}/groupadd
>> ./postfix/postfix.spec:%{_sbindir}/groupadd -g 21 mail 2>/dev/null
>> ./postfix/postfix.spec:%{_sbindir}/groupadd -g %{maildrop_gid}
>> %{maildrop_group} 2>/dev/null ./postfix/postfix.spec:%{_sbindir}/groupadd
>> -g %{postfix_gid} %{postfix_group} 2>/dev/null
>> ./postgresql/postgresql.spec:/usr/sbin/groupadd -g 88 -f postgres
>> 2>/dev/null ||: ./rpm/rpm.spec:/usr/sbin/groupadd -g 37 rpm> /dev/null 2>&1
>> || :
>> ./sane-backends/sane-backends.spec:groupadd scanner
>> ./shadow/shadow.spec:%{_sbindir}/groupadd
>> ./sudo/sudo.spec: groupadd -f -g 31 wheel
>> ./sudo/sudo.spec: #groupadd -g 31 wheel 2>/dev/null ||:
>>
>>
>> I just can say that clamav and postgres are using the same GID, 88, and one
>> should be changed - Please have a look at the next link:
>> http://www.yoper.com/wiki/index.php?title=Proposal_for_Application_Group_Li
>> st_Formalization
>>
>> Is there anyone else ready/willing to push a bit to the wheel?
>>
>> Regards! :)
>>
>>
>>> regards
>>>
>>> --
>>> Tobias Gerschner
>>> Yoper Linux - www.yoper.com
>>>
>>> Knowing is not enough; we must apply. Willing is not enough; we must do.
>>> _______________________________________________
>>> yoper-dev mailing list
>>> yoper-dev@lists.yoper.com
>>> http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
>>>
>> _________________________________________________________________
>> MSN Video.
>> http://video.msn.com/?mkt=es-es
>> _______________________________________________
>> yoper-dev mailing list
>> yoper-dev@lists.yoper.com
>> http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
>>
> _______________________________________________
> yoper-dev mailing list
> yoper-dev@lists.yoper.com
> http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
>
>
_______________________________________________
yoper-dev mailing list
yoper-dev@lists.yoper.com
http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
