gmane.linux.mageia.devel

OpenVZ template

Luis Daniel Lucio Quiroz — 2013-05-25T21:06:42

In the past I was sucessfully able to do a Mageia 1 openvz template, but
since mga2 the glibc complains about host kernel 2.6.32.  Wondering if
there is a way we can have support for openvz template,

Maybe an old glibc replacement?

Re: Feature Proposal: Mate Desktop Environment

AL13N — 2013-05-25T20:28:26

Op zaterdag 25 mei 2013 23:05:10 schreef atilla ontas:

While i haven't read your feature yet (and i'm sure features will be talked 
about only in a few weeks in the packaging team meeting; you should try to be 
present if possible) I'm not adverse to the idea, if it's well maintained and 
it doesn't conflict with other packages and follows the policies etc...

but given the size of the project, we'll likely want to know that you can keep 
maintaining it, so that we don't have extra unmaintained packages next 
release.

In short, i'm not saying anything yet, but you seem to present a wellprepared 
clear case, so i'd advise you to present your feature when the time comes 
(likely this will be in the meeting after the one about the post-release 
discussion.)

good luck.

Feature Proposal: Mate Desktop Environment

atilla ontas — 2013-05-25T20:05:10

Hi. Let me introduce myself first. I'm former Mandriva Turkiye community
admin and now Mageia & OpenMandriva community member. Also one of Turkish
translators of Mageia. A packaging padawan, thanks to my mentor zezinho. I
had maintain Mandriva Turkey' s community repository until 2011.

I'm willing to package and maintain Mate DE.  As you may already noticed i
put a Mate DE feature proposal for Mageia 4. I know there were discussions
about it but mainly for Cinnamon. I clearly understand objections about
Cinnamon and have answers like those objections.

Please look at https://wiki.mageia.org/en/Feature:Mate

I tried to get everything together, including answers to possible
objections. Thank all who interest in my proposal.

Re: [changelog] [RPM] cauldron core/release systemd-204-1.mga4

Colin Guthrie — 2013-05-25T20:00:55

'Twas brillig, and Thierry Vignaud at 25/05/13 20:45 did gyre and gimble:

Because it's now implemented in C as opposed to the old python version
with no additional deps over those already in the main package.


No need.

Col

Re: [changelog] [RPM] cauldron core/release systemd-204-1.mga4

Thierry Vignaud — 2013-05-25T19:45:54

Why? Why?
This will bloat minimal install again!
Please revert.

Re: ml receiving mode options clear as mud

Felix Miata — 2013-05-25T16:31:13

On 2013-05-25 12:05 (GMT-0400) Thomas Spuhler composed:



What graph?


Lucky you. Not everyone has perfect connectivity.

Re: Cauldron is open again

AL13N — 2013-05-25T16:07:56

i think this too is playing an (arguably big) part in this... i just
figured that we'd did a cleaning like we said we would :-)

Re: ml receiving mode options clear as mud

Thomas Spuhler — 2013-05-25T16:05:22

I actually like the graph. And as far as I am concerned, I never experienced any delays.

Re: ml receiving mode options clear as mud

Felix Miata — 2013-05-25T15:55:05

On 2013-05-25 18:39 (GMT+0300) Thomas Backlund composed:




Not clearly evident from the content there.


What I wrote wasn't meant to imply I was actually missing any. Sometimes 
there is delay between sender and recipient. I just went to the page to 
ensure that delay should be only reason I don't see, not because not sent.

I like standard Mailman pages. They are unambiguous and respectful of browser 
settings, not mystery meat.

Re: ml receiving mode options clear as mud

Thomas Backlund — 2013-05-25T15:39:25

25.05.2013 18:20, Felix Miata skrev:

That's because by default the ml send mails to all subscribed, so you
only need options to disable default features.

If you are missing your own mails, but see them in the ml archive I
guess you are either using gmail, wich hides your own mails, or you
have some spamfilter issues...

--

Thomas

ml receiving mode options clear as mud

Felix Miata — 2013-05-25T15:20:35

https://ml.mageia.org/l/suboptions/dev is much different than Mailman pages. 
Besides the rude mousetype surrounded by vast amounts of whitespace, the 
select list for receiving mode is ambiguous. Among the selections is "do not 
receive your own posts", but nothing to indicate receiving your own posts is 
even possible, which is what I want, so that if I see no responses to what I 
sent, I don't have to visit the archive to find out whether it reached the 
list instead of disappearing into the ether.

Re: UEFI/GPT/cauldron questions

Thomas Spuhler — 2013-05-25T15:19:23

I don't know why this should be a problem. The way I understand it, extended partitions are needed 
because of the DOS partion table only being able to provide 4 partitions. This way you can put a 
partion into the extended.
This is why our partition numbering goes from 1 to 6

Re: Re: Re: [changelog] [RPM] 3 core/updates_testing openswan-2.6.28-4.mga3

Jani Välimaa — 2013-05-25T14:02:27

On Sat, 25 May 2013 07:20:10 -0400
David Walser <luigiwalser-/E1597aS9LQAvxtiuMwx3w< at >public.gmane.org> wrote:


You can always do 'svn rm $SVN/updates/3/foo' and 'svn cp
$SVN/packages/cauldron/foo $SVN/updates/3' to sync changes from
cauldron to mga3 tree.

Re: Re: [changelog] [RPM] cauldron core/release texlive-20120701-4.mga4

Colin Guthrie — 2013-05-25T13:07:53

'Twas brillig, and nicolas vigier at 24/05/13 10:07 did gyre and gimble:

Yup, I *really* don't fancy having texlive split up quite so
aggressively as on Fedora. There is a large amount of opposition to that
move judging by the rants from various high profile Fedora
users/developers on Google+

So while doing something with textlive is needed, having 4.5k pgks does
not sound like the best of options...

Col

Re: Re: Re: [changelog] [RPM] 3 core/updates_testing openswan-2.6.28-4.mga3

Sander Lepik — 2013-05-25T12:35:09

release and caused a bunch of
mga2 and no warning was

AFAIK it was done the same way for Mageia 2 too. That's why I warned in
some bugs that QA work at this point will be useless.

--
Sander

Re: rpm "provide" naming standard?

Guillaume Rousse — 2013-05-25T10:06:24

Le 24/05/2013 17:05, Jean-Marc Pigeon a écrit :
"To be part of mageiea" implies that the package is shipped by mageia 
directly, not by a third-party, which is what you're apparently trying 
to do. At least, that's my understanding :)

Caution, "webserver" doesn't implies mandatorily "apache", it's a 
virtual package for any kind of web server.

There is no official list, AFAIK.

However, they are ad-hoc solution, tough, such as mappings configured in 
applications needing to compare packages between distributions, even if 
package name differs. Here is some examples:
http://check.mageia.org/cauldron/updates.html

There have been some discussion and proposal in the past on this topic 
(I remember at least one conference during FOSDEM), to standardize 
package metatadata (name, summaries, descriptions, etc...) in the past. 
But I don't think they have been much results.

I think part of the problem is than usual distribution attitude toward 
upstream developpers is "let us do the packaging, that's our duty", 
rather than "we'll try to make it easier for you to maintain third-party 
packages".

Re: perl 5.18.0 update (Re: please refrain from updating perl modules)

Shlomi Fish — 2013-05-25T11:42:20

Hi all,

On Sat, 25 May 2013 01:55:45 +0200
Olivier Blin <mageia-RZzICDNEOQ/YtjvyW6yDsg< at >public.gmane.org> wrote:


I can reproduce this here on my i586 VM running Mageia 3. I'll try to
investigate further:  

http://www.shlomifish.org/Files/files/code/bugs/mageia/mageia-3-perl-i586-bm-l-b-failure.png

Regards,

Shlomi Fish

Re: Re: rpm --resign does nt work any more ?

Dimitrios Glentadakis — 2013-05-25T11:34:18

Στις 25/05/2013 11:08:42 Thierry Vignaud έγραψε:

Thanks, i did nt think that a rpm command option could consist a different package.

Re: Re: [changelog] [RPM] 3 core/updates_testing openswan-2.6.28-4.mga3

David Walser — 2013-05-25T11:20:10

wrote:
<luigiwalser-/E1597aS9LQAvxtiuMwx3w< at >public.gmane.org>
all of these updates.  I'll have to re-fix them in SVN manually and re-upload.  Ugh!  Thanks for 
catching this Thierry.  :o(

Which gave us no way to get work prepared for updates ahead of the release and caused a bunch of 
work to have to be re-done.  Furthermore it was done the other way for mga2 and no warning was 
given that this was going to be changed.

Re: RFT: mgaonline upgrade on MGA2

Luca Olivetti — 2013-05-25T11:19:41

Al 24/05/13 16:33, En/na Luca Olivetti ha escrit:


I tried again a direct upgrade mga1->mga3.
I installed systemd before starting (there's a systemd package in mga1),
though I don't think that's strictly necessary.
Once the upgrade started and having selected the medias, I tried to
install dracut from tty2, but that interfered with the installer.
So I waited until the first error then, before acknowledging it (which
would remove the medias from the chrooted system), I did a

chroot /mnt
urpmi dracut

which pulled in ~100 packages.
Once that ended, I acknowledged the error and the installer went back to
the installing phase, installing the remaining ~1000 packages
successfully (the only error being flash-player-plugin).
After that, the only "issue" was that kde didn't have the bottom panel
(it also reverted to the default wallpaper, but that also happened going
from mga1 to mga2 then mga3).
I wonder if, had I upgraded the real system, it would have maintained
the rest of the settings.
So, it is possible to upgrade from mga1 to mga3 with some hand holding.
Now, my wife's netbook is still running mandriva 2010.....
;-)

Bye

Re: Cauldron is open again

Guillaume Rousse — 2013-05-25T07:44:36

Le 24/05/2013 19:38, AL13N a écrit :
I'm not convinced than long freeze time are mainly caused with missing 
dependencies in actively maintained packages. I'm more inclined toward 
the always increasing number of packages introduced in the distribution 
'because it might be useful to someone else' and then slowly bitrotting 
because there is no real interest for them. Just look at the long list 
of package never rebuild since mga1 or mga2 regulary established by 
Pascal to see what I mean.

In order to speed up freeze period, we should try to be as much 
efficient in old package dropping than we are for new package introducing...