On Wed, Nov 2, 2011 at 9:00 AM,
<mageia-dev-request@mageia.org> wrote:
Send Mageia-dev mailing list submissions to
mageia-dev@mageia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://www.mageia.org/mailman/listinfo/mageia-dev
or, via email, send a message with subject or body 'help' to
mageia-dev-request@mageia.org
You can reach the person managing the list at
mageia-dev-owner@mageia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Mageia-dev digest..."
Today's Topics:
1. Re: [changelog] [RPM] cauldron core/release
perl-SOAP-Lite-0.714.0-1.mga2 (D.Morgan)
2. Re: Please test: initscripts+systemd in updates_testing
(Johnny A. Solbu)
3. Re: Please test: initscripts+systemd in updates_testing (andre999)
4. mentors + apprentices (andre999)
5. i18n corrections in drak tools (Oliver Burger)
----------------------------------------------------------------------
Message: 1
Date: Wed, 2 Nov 2011 01:40:07 +0100
From: "D.Morgan" <dmorganec@gmail.com>
To: Mageia development mailing-list <mageia-dev@mageia.org>
Subject: Re: [Mageia-dev] [changelog] [RPM] cauldron core/release
perl-SOAP-Lite-0.714.0-1.mga2
Message-ID:
<CAL+dqvDutg406MXZVTzaAsyYeO2JXQpbprQHjrpx9CXp=vbRmw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Fri, Oct 28, 2011 at 9:02 AM, Thierry Vignaud
<thierry.vignaud@gmail.com> wrote:
> On 27 October 2011 17:11, Mageia Team <buildsystem-daemon@mageia.org> wrote:
>> takashi <takashi> 0.714.0-1.mga2:
>> + Revision: 158214
>> - update to 0.714
>
> A requested package cannot be installed:
> perl-SOAP-Lite-0.714.0-1.mga2.noarch (due to unsatisfied
> perl(SOAP::Transport::FTP)[>= 0.712.0])
> Continue installation anyway? (Y/n)
>
still broken.
The main issue is that i don't see perl(SOAP::Transport::FTP)[>=
0.712.0]) see : http://search.cpan.org/dist/SOAP-Transport-FTP/
------------------------------
Message: 2
Date: Wed, 2 Nov 2011 03:49:02 +0100
From: "Johnny A. Solbu" <cooker@solbu.net>
To: mageia-dev@mageia.org
Subject: Re: [Mageia-dev] Please test: initscripts+systemd in
updates_testing
Message-ID: <201111020349.05223.cooker@solbu.net>
Content-Type: text/plain; charset="utf-8"
On Wednesday 02 November 2011 01:05, andre999 wrote:
> No offense intended
None detected. ;-)=
> but you don't see a slight advantage of not having
> to mount a separate partition, and of sharing the space available on the
> otherwise 2 separate partitions, particularly if the disk space is
> somewhat limited ?
If the diskspace is limited, there often is no available space to host a separate /usr.
The old drive in my gateway was a 4G drive. There was One partition. ;-)=
I do see the need to have all in one partition in many cases.
But there is a diffenrece in having a need and require it. :-)=
> Since you have read the reference, you didn't notice that the option of
> separate partitions is _not_ precluded ?
Some of the answers I got here suggested otherwize. if /usr needs to be mounted in order for the system to boot normally. Then have systemd mount it.
I do see that there might be some problems involved in solving it.
> However if one has / and /usr on the same partition, combining /bin,
> /sbin, /usr/bin and /usr/sbin would certainly be a lot simpler than it
> is now.
Yes. I see that, and I see that it can be agood idea to merge /*bin with /usr/*bin
> I never could understand why the complication of separate /bin and /sbin,
I still feel that the daemon's executeable's belongs in sbin rather than bin.
> and never appreciated the gymnastics of different commands with
> the same name to handle root/non-root permissions for certain commands.
I haven't noticed that. do you have an example?
> To me, avoiding unnecessary complication by design is a big plus.
Agreed. But don't throw the baby out with the water. ;-)=
--
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20111102/60ae76e7/attachment-0001.asc>
------------------------------
Message: 3
Date: Wed, 02 Nov 2011 02:47:21 -0400
From: andre999 <andre999mga@laposte.net>
To: Mageia development mailing-list <mageia-dev@mageia.org>
Subject: Re: [Mageia-dev] Please test: initscripts+systemd in
updates_testing
Message-ID: <4EB0E779.5020101@laposte.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Johnny A. Solbu a ?crit :
> On Wednesday 02 November 2011 01:05, andre999 wrote:
>
[...]
>> Since you have read the reference, you didn't notice that the option of
>> separate partitions is _not_ precluded ?
>>
> Some of the answers I got here suggested otherwize. if /usr needs to be mounted in order for the system to boot normally. Then have systemd mount it.
> I do see that there might be some problems involved in solving it.
>
I think it is better to mount any separate /usr as early in the boot
process as possible.
[...]
>> and never appreciated the gymnastics of different commands with
>> the same name to handle root/non-root permissions for certain commands.
>>
> I haven't noticed that. do you have an example?
>
See the attached file of duplications of names on my computer.
There are 76 duplications in the 4 directories.
Those ending in @ are symbolic links. Such duplications will disappear
with the merging.
The others are mostly (if not all) scripts which link to a routine which
asks for the root password for certain commands, according to enabled
permissions. If the permissions are enabled and the password correctly
entered, the user is rerouted to the initial command. A less obscure
way of dealing with it would be better.
(I forget the details, but someone like tv or misc would know.)
>> To me, avoiding unnecessary complication by design is a big plus.
>>
> Agreed. But don't throw the baby out with the water. ;-)=
>
If just changing initramfs to load any separate /usr partition will fix
it, I don't see that we are losing anything.
Although if someone like tmb can initially misunderstand the impact, I
guess anyone can. (It took me a while.)
Maybe it will be more trouble to make such an initramfs, but once it is
made, it should work nicely. Without a special reason to have a
separate /usr, I would say that it is better to avoid it.
I see that ensuring that everything necessary to fully boot being
guaranteed to be available very early in the boot process is a big plus.
If /home isn't available, one can always login to root. As well,
keeping /home on a separate partition has advantages for ensuring the
persistance of personal data and configuration in the event of
reformatting /.
--
Andr?
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bin_dup.txt
URL: </pipermail/mageia-dev/attachments/20111102/0f52d042/attachment-0001.txt>
------------------------------
Message: 4
Date: Wed, 02 Nov 2011 03:54:38 -0400
From: andre999 <andre999mga@laposte.net>
To: Mageia development mailing-list <mageia-dev@mageia.org>
Subject: [Mageia-dev] mentors + apprentices
Message-ID: <4EB0F73E.9060108@laposte.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi everyone,
We have a new packager, takashi, who has successfully mentored with jquelin.
We now have 2 apprentice candidates with .rpm packaging experience, waiting for
a mentor.
mcb30 (Michael Brown), who I introduced last week,
is a longtime Mandrake/Mandriva and now Mageia user who has maintained several
private RPM repos, and while waiting for a mentor has been making spec files
for some python applications.
We also have
neocrust (Alexander Scherbakov),
who has experience maintaining packages for openSuse and Lunar Linux, as well
as translating to Russion, and doing documentation with the Gentoo Russion team.
You can find more details at:
http://www.mageia.org/wiki/doku.php?id=packages_mentoring#packager_apprentice_candidates
Mentors, let me know who you take on, and I'll update the tables for you.
Thanks :-)
----
We now have 49 active packagers (maintaining at least one package), with
several who have yet to take a package.
We currently have about 40 apprentices.
Over 75% of packages have a maintainer.
----
Anyone else looking for a mentor, let me know so I can add your name as an
apprentice candidate -- or you can do it yourself.
http://www.mageia.org/wiki/doku.php?id=packages_mentoring#packager_apprentice_candidates
See also the section just above, on becoming a Mageia packager :
http://www.mageia.org/wiki/doku.php?id=packages_mentoring#becoming_a_mageia_packager
To find a mentor, you can also post to this list, or on IRC at freenode
#mageia-mentoring.
Regards :-)
--
Andr?
(Packager mentoring program coordinator)
------------------------------
Message: 5
Date: Wed, 2 Nov 2011 09:45:10 +0100
From: Oliver Burger <oliver.bgr@googlemail.com>
To: mageia-dev@mageia.org
Subject: [Mageia-dev] i18n corrections in drak tools
Message-ID: <201111020945.10325.oliver.bgr@googlemail.com>
Content-Type: Text/Plain; charset="us-ascii"
Hi there,
I'd like to get all corrections made by i18n teams since the Mga1 release into
the distribution. Imho that is important because not all teams managed to
finish their translation work for the Mga1 freeze, and we were told at that
time, that we would be able to get our work into Mga1 via an update later on
and thus I told the teams to set a priority on the translation of the
installer po files, which couldn't be updated later.
As I mentioned in https://bugs.mageia.org/show_bug.cgi?id=1784 I would propose
a "i18n bug hunting day". We could do a blog post calling people to actively
look for translation errors and file bug reports about them. I18n teams could
then fix as many of those as possible and commit the corrections to the "1"
branch of the drak tools svn (and also to cauldron if they are still present
there).
What do you think?
Let's say "i18n bug hunting day" somewhen in the middle of next week and an
update of the drak tools for Mga1 arround december 1st?
Oliver
End of Mageia-dev Digest, Vol 15, Issue 5
*****************************************