Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/16 Thorsten van Lil :
> Am Donnerstag, 16. Juni 2011, 02:47:16 schrieb Wolfgang Bornath:
>> Btw: after latest updates I don't have the nice blue background in
>> Gnome, it is somehow distorted (blue but with lighter blue stripes,
>
> You mean like this?
> http://galleries.stefan-horning.de/d/7704-2/GNOME3-Info-o.png

Yes, exactly!

-- 
wobo

Re: [Mageia-dev] Problems with Gnome 3

[Thorsten van Lil]

Am Donnerstag, 16. Juni 2011, 02:47:16 schrieb Wolfgang Bornath:
> Btw: after latest updates I don't have the nice blue background in
> Gnome, it is somehow distorted (blue but with lighter blue stripes,

You mean like this?
http://galleries.stefan-horning.de/d/7704-2/GNOME3-Info-o.png

Greetings,
Thorsten

Re: [Mageia-dev] [RPM] cauldron core/release gthumb-2.12.3-1.mga2

[Charles A Edwards]

On Thu, 16 Jun 2011 05:31:44 +0300
Ahmad Samir  wrote:

> > Why the '3' digit in libraries ? We can not have this in parallel
> > with old one... 
> 
> Ask upstream, we don't add suffix libs with '3' manually, IINM.


Probably because is for/requires gtk+3 and latest stable brasero-2.32.1
is for gtk+2



Charles

-- 
You will wish you hadn't.
--
Mandriva Linux release 2011.0 (Cooker) for x86_64$
On SuperSizehttp://www.eslrahc.com
Registered Linux user #182463
2.6.38.7-tmb-server-1mdv x86_64
--


signature.asc
Description: PGP signature

Re: [Mageia-dev] [RPM] cauldron core/release gthumb-2.12.3-1.mga2

[Ahmad Samir]

2011/6/16 JA Magallón :
> On Thu, 16 Jun 2011 00:22:18 +0200 (CEST), Mageia Team 
>  wrote:
>
>> Name        : gthumb                       Relocations: (not relocatable)
>> Version     : 2.12.3                            Vendor: Mageia.Org
>> Release     : 1.mga2                        Build Date: Thu Jun 16 00:17:17 
>> 2011
>> Install Date: (not installed)               Build Host: ecosse
>> Group       : Graphics                      Source RPM: (none)
>> Size        : 5208589                          License: GPLv2+
>> Signature   : (none)
>> Packager    : Mageia Team 
>> URL         : http://gthumb.sourceforge.net/
>> Summary     : An image viewer and browser for GNOME
>> Description :
>> gThumb lets you browse your hard disk, showing you thumbnails of image files.
>> It also lets you view single files (including GIF animations), add comments 
>> to
>> images, organize images in catalogs, print images, view slideshows, set your
>> desktop background, and more.
>>
>> dmorgan  2.12.3-1.mga2:
>> + Revision: 107996
>> - Fix build
>
> one:~# urpmi gthumb
> A requested package cannot be installed:
> gthumb-2.12.3-1.mga1.x86_64 (due to unsatisfied libbrasero-burn.so.1()(64bit))
> Continue installation anyway? (Y/n)
>
> one:~# rpm -ql lib64brasero1
> /usr/lib64/girepository-1.0/BraseroBurn-3.0.0.typelib
> /usr/lib64/girepository-1.0/BraseroMedia-3.0.0.typelib
> /usr/lib64/libbrasero-burn3.so.1
> /usr/lib64/libbrasero-burn3.so.1.2.0
> /usr/lib64/libbrasero-media3.so.1
> /usr/lib64/libbrasero-media3.so.1.2.0
> /usr/lib64/libbrasero-utils3.so.1
> /usr/lib64/libbrasero-utils3.so.1.2.0
>
> Why the '3' digit in libraries ? We can not have this in parallel with old 
> one...
>

Ask upstream, we don't add suffix libs with '3' manually, IINM.

> --
> J.A. Magallon      \                 Winter is coming...
>



-- 
Ahmad Samir

Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/15 Thorsten van Lil :
> Am Donnerstag, 9. Juni 2011, 10:44:23 schrieb JA Magallón:
>> if I select "System settings" o launch firefox, immediately I get a
>> fullscreen error about "something went wrong, plz logout and in again"
>
> Same for me two days back. Since yesterday it works relatively well. I get the
> mentioned error right after login, but: If you just press Alt+F4 the error
> message vanish and you can start working us usual.

Wow! If I had known that you could get rid of error messages that easy
I would have used Alt+F4 many years ago in my Windows systems!
A nice lesson that you should not always do what a message box t4ells you to do!

Ok, seems to work, so all my testing this afternoon was void :(

Btw: after latest updates I don't have the nice blue background in
Gnome, it is somehow distorted (blue but with lighter blue stripes,
artefacts?). When I switch to KDE I have normal background, when
switching back to Gnome I have those stripes again (Nvidia proprietary
driver installed).

Re: [Mageia-dev] [RPM] cauldron core/release rhythmbox-0.13.3-7.mga2

[JA Magallón]

On Tue, 14 Jun 2011 18:32:23 +0200 (CEST), Mageia Team 
 wrote:

> Name: rhythmboxRelocations: (not relocatable)
> Version : 0.13.3Vendor: Mageia.Org
> Release : 7.mga2Build Date: Tue Jun 14 18:24:25 
> 2011
> Install Date: (not installed)   Build Host: ecosse
> Group   : Sound Source RPM: (none)
> Size: 10009472 License: GPLv2+ with exception
> Signature   : (none)
> Packager: Mageia Team 
> URL : http://www.gnome.org/projects/rhythmbox/
> Summary : Music Management Application
> Description :
> Music Management application with support for ripping audio-cd's,
> playback of Ogg Vorbis and Mp3 and burning of CD-Rs.
> 
> dmorgan  0.13.3-7.mga2:
> + Revision: 106171
> - Fix file list
> - Add libproxy-devel as buildRequire
> - Rebuild against new brasero
> 

Needs another rebuild for new gnome-media:

ne:~# rpm -qa *gnome-media*
lib64gnome-media0-2.32.0-3.mga1
gnome-media-2.91.2-1.mga2
libgnome-media-profiles-3.0.0-6.mga2
lib64gnome-media-profiles0-3.0.0-6.mga2
one:~# urpme lib64gnome-media0
To satisfy dependencies, the following 3 packages will be removed (15MB):
  lib64gnome-media0-2.32.0-3.mga1.x86_64
  lib64rhythmbox3-0.13.3-7.mga2.x86_64
   (due to missing libgnome-media-profiles.so.0()(64bit))
  rhythmbox-0.13.3-7.mga2.x86_64
   (due to missing librhythmbox-core.so.3()(64bit),
due to unsatisfied lib64rhythmbox3 >= 0.13.3-7.mga2)
Remove 3 packages? (y/N)


-- 
J.A. Magallon  \ Winter is coming...

Re: [Mageia-dev] [RPM] cauldron core/release gthumb-2.12.3-1.mga2

[JA Magallón]

On Thu, 16 Jun 2011 00:22:18 +0200 (CEST), Mageia Team 
 wrote:

> Name: gthumb   Relocations: (not relocatable)
> Version : 2.12.3Vendor: Mageia.Org
> Release : 1.mga2Build Date: Thu Jun 16 00:17:17 
> 2011
> Install Date: (not installed)   Build Host: ecosse
> Group   : Graphics  Source RPM: (none)
> Size: 5208589  License: GPLv2+
> Signature   : (none)
> Packager: Mageia Team 
> URL : http://gthumb.sourceforge.net/
> Summary : An image viewer and browser for GNOME
> Description :
> gThumb lets you browse your hard disk, showing you thumbnails of image files.
> It also lets you view single files (including GIF animations), add comments to
> images, organize images in catalogs, print images, view slideshows, set your
> desktop background, and more.
> 
> dmorgan  2.12.3-1.mga2:
> + Revision: 107996
> - Fix build

one:~# urpmi gthumb
A requested package cannot be installed:
gthumb-2.12.3-1.mga1.x86_64 (due to unsatisfied libbrasero-burn.so.1()(64bit))
Continue installation anyway? (Y/n)

one:~# rpm -ql lib64brasero1
/usr/lib64/girepository-1.0/BraseroBurn-3.0.0.typelib
/usr/lib64/girepository-1.0/BraseroMedia-3.0.0.typelib
/usr/lib64/libbrasero-burn3.so.1
/usr/lib64/libbrasero-burn3.so.1.2.0
/usr/lib64/libbrasero-media3.so.1
/usr/lib64/libbrasero-media3.so.1.2.0
/usr/lib64/libbrasero-utils3.so.1
/usr/lib64/libbrasero-utils3.so.1.2.0

Why the '3' digit in libraries ? We can not have this in parallel with old 
one...

-- 
J.A. Magallon  \ Winter is coming...

Re: [Mageia-dev] Question about backports: calibre (bug 1659)

[Radu-Cristian FOTESCU]

>From: andre999 
>
[...]
>
>In my mind you make an excellent case for upgrading this application from 
>upstream, and installing 
>under /opt, as you say you do already.
>Which I do for Mozilla Seamonkey, for example, because of relatively frequent 
>updates.  (In that 
>case I also apply some personal patches, but that is another question.)
>It is appropriate to report bugs for the application upstream.  The fixes will 
>trickle down to Mageia.
>Just because you use Mageia (or any other distro) doesn't mean you can't 
>install 3rd party 
>applications.  Although certainly it is preferable that most are packaged in 
>Mageia.
>
>Which brings up another point.  Considering your concern for the application, 
>maybe you would like 
>to package it for Mageia.  You could ensure that it is always up to date, and 
>that it works 
>properly, and is properly supported.  (The packager is a key player in 
>support.)
>Just because it is called a backport doesn't mean that it won't work.
>The packager mentoring program will help you get started :)
>
>-- 
>André


Well, first of all, I never liked the _concept_ of backports. Too many 
repositories, too complex tree already. One of the reasons I wasn't very fond 
of Mandriva (the other reason being the IaOra theme(s).)

From the NON-rolling distros, Fedora is arguably the only one who tries to 
bring newer versions of a number of applications throughout its 12+1 months 
lifecycle. w/o using backports. My opinion is that, as long as system libraries 
are _not_ upgraded, many other packages (applications!) should be updated as 
appropriate. Otherwise, the result would be that Windows users would have more 
freedom and ease in decided what version of the [multi-platform open-source] 
applications to use than Linux users! (Except, of course, the users of 
rolling-release distros, and except for users of 
unstable/rawhide/cooker/cauldron...)

I know, I should probably be using Fedora as long as _some_ of their principles 
suit my views much more than Mageia does or than Mandriva did. However, Fedora 
lacks something like Mandriva Control Center, and yum is millions of times 
slower than urpmi, therefore...

Not to mention that most of the best people Mandriva had are now with Mageia, 
which makes this distro hard to ignore... (Je crois qu'on appelle cela 
zugzwang...)

R-C


R-C

Re: [Mageia-dev] Finalizing update process

[Balcaen John]

Le mercredi 15 juin 2011 17:32:35, Stew Benedict a écrit :
[...]
> 
> Bugs:
> 
> https://bugs.mageia.org/show_bug.cgi?id=1678 (vde2)
> https://bugs.mageia.org/show_bug.cgi?id=1554 (mysql)
> https://bugs.mageia.org/show_bug.cgi?id=1813 (curl)
> https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion)
> 
i've added a new one for gtkglext https://bugs.mageia.org/show_bug.cgi?id=1195 
(i'm also installing 2 mageia for both arch in vm to help test them)

Regards
-- 
Balcaen John
Jabber ID: mik...@jabber.littleboboy.net

Re: [Mageia-dev] Release cycles proposals, and discussion

[andre999]

Samuel Verschelde a écrit :


Le mardi 14 juin 2011 20:00:39, Anne nicolas a écrit :

2011/6/14 Wolfgang Bornath


2011/6/14 Anne nicolas:

I guess because of Mandriva policy. We did provide backports but it was
explicitely said to be unsupported. "Use it at your own risks"
We may have to rewrite  this and make things clear


Right.  Define a (somewhat lower) level of support -- but enough to assure most users that 
backports can be reliable.

Mandriva was defining _corporate_ support, which doesn't apply in a community 
volonteer-based distro.


Do you mean, just telling people that it is no risk or do you mean a
change which lessens the risk?


not at all


As Michael wrote earlier in this thread, if there was the risk to
break the system by low quality of backports then the quality has to
be improved (not his own words but that's how I understood it).


exactly what I had in mind. Having backports can allow choice between
"the last version of" and "the stable version with which I'm happy
  with". But indeed we need more quality in backport rpms that is policy and
tests.


Few words could make me more happy about the potential future status of our
backports. And if backports have a bad reputation among our users, maybe we
should rename updates to "maintenance updates" and backports to "feature
updates" ?

Samuel


Not a bad idea -- even if only as a subtitle :)

--
André

Re: [Mageia-dev] Question about backports: calibre (bug 1659)

[andre999]

Radu-Cristian FOTESCU a écrit :



Release frequency never was a criteria for differentiating between
pushing something to updates and something to backports.


It should be. Otherwise, we should all be using OpenOffice.org 1.0.1. --
security issues set aside.


And I see no reason why it would be in favor of doing a bug fix update
rather than a backport, especially if we ask to do a more stringent QA
checking on updates, as it would put too much work on the team.


Because Mageia (and Mandriva)'s vision of the concept of "backports" is not
compatible with my common-sense.

I have not used Mandriva very much in the past, because I hate the concept of
"backports" -- yes, Ubuntu does them too, but Ubuntu backports are totally
unsupported, so you can imagine their "quality"...

I'd rather stick to "updates" -- this is also the reason I stopped using
Debian, because the morons (yes, morons) were only pushing tzdata updates
in "volatile", not in "updates", whereas ALL the other distro weres pushing
tzdata updates in "updates".

If Mageia considers that a 6-7 months old package (for an application that
released 32 times in the meantime) only deserves updates in "backports",
then I will probably stop reporting any possible bugs with this distro
-- as a protest.

It is indeed a matter of principle. I am personally using the latest
calibre installed in /opt, not the official one, but again, it's a
matter of principle.


Whatever is important and comes from upstream  should go into updates IMHO.
Backports, in my view, only make sense if they're  coming from Release N+1
*and* if they represent a major version bump -- such as FF4 over FF3.6, etc.


WRT calibre, Fedora has a simple way: it keeps a newer calibre packages in
updates/testing for 1 week, and if no user complains about regressions, it
goes into updates. This is because calibre is a "leaf" package -- no other
package depends on it, so it only impacts those who are using it.


Again, that's not a criteria. Every software is important to at least
one person, and that would mean we should update everything if we start
to update everything important to one group of users.


I can see how important is calibre to Mageia users. Nobody noticed or cared
that it is an antiquated version. They could have as well used notepad.exe
from Win95.



And for what it is worth, Fedora is discussing having separate update
and backport ( https://fedorahosted.org/fesco/ticket/515 ), even if the
discussion seems to be going nowhere at the moment


BS. I hope Fedora *never* uses backports!

Their update policy is very clear *and* flexible:
http://fedoraproject.org/wiki/Updates_Policy

Please note these:

"Exceptions: Some classes of software will not fit in these guidelines.
If your package does not fit in one of the classes below, but you think
it should be allowed to update more rapidly . . .


Things that would make it more likely to grant a request:
--  The package is a "leaf" node. Nothing depends on it or requires it."

Calibre is a "leaf" package.

If not, in the same document:

"All other updates must either:
-- reach the criteria laid out in the previous section OR
-- reach the positive Bodhi karma threshold specified by the updates submitter 
OR
-- spend some minimum amount of time in updates-testing, currently one week."

I am not sure why F15 stopped updating calibre to 0.8.0 in updates (Rawhide went
up to 0.8.4, maybe 0.8.5 now), but for the versions up to and including 0.8.0,
here's the dynamics of the updates:


...

Indeed, Mageia does not have the number of packagers that Fedora has.
However, if Mageia's _policy_ is to rather have 6-7 months old versions in
updates, I should probably realize that Mageia is not for me.

No, I have not, and never will use any repository called "backports". When a
newer stable  release of a distro is available, I should update to it if
updates I need are not pushed into Release N-1 "updates" (even if that release
is officially still supported with security patches), but again, "backports"
as Mandriva and Mageia are seeing them -- i.e. backporting
from  Cooker/Cauldron, not from "updates/testing" nor from "Release N+1"
-- does not fit my Zen.

R-C


In my mind you make an excellent case for upgrading this application from upstream, and installing 
under /opt, as you say you do already.
Which I do for Mozilla Seamonkey, for example, because of relatively frequent updates.  (In that 
case I also apply some personal patches, but that is another question.)

It is appropriate to report bugs for the application upstream.  The fixes will 
trickle down to Mageia.
Just because you use Mageia (or any other distro) doesn't mean you can't install 3rd party 
applications.  Although certainly it is preferable that most are packaged in Mageia.


Which brings up another point.  Considering your concern for the application, maybe you would like 
to package it for Mageia.  You could ensure that it is always up to date, and that it works 
properly, and i

Re: [Mageia-dev] Lib policy change needed ?

[Colin Guthrie]

'Twas brillig, and Anssi Hannula at 15/06/11 18:06 did gyre and gimble:
> On 15.06.2011 19:15, Ahmad Samir wrote:
>> For example look at Amarok:
>> $ urpmf --sourcerpm :amarok | sort | grep lib
>> lib64amarokcore1:amarok-2.4.1-0.mga1.src.rpm
>> lib64amaroklib1:amarok-2.4.1-0.mga1.src.rpm
>> lib64amarokocsclient4:amarok-2.4.1-0.mga1.src.rpm
>> lib64amarokpud1:amarok-2.4.1-0.mga1.src.rpm
>> lib64amarok-sqlcollection1:amarok-2.4.1-0.mga1.src.rpm
>> lib64amarok-transcoding1:amarok-2.4.1-0.mga1.src.rpm
>>
>> every lib is in a separate package, even though:
>> - Nothing else uses any of those libs other than Amarok
>> - Amarok is linked against all of those libs and it wouldn't work if
>> you uninstall any of them
>>
>> In such a case grouping all of them in one lib*amarok package would be
>> easier, there'll never be any file conflicts when the mojor of any of
>> them changes.
> 
> IMO we should have an exception so that libraries like these that are
> related to and required by a single program/package that are not
> expected (i.e. there are no header files) to be used by others, should
> be packaged in the main package itself.
> 
> I.e. I'd put all of those in amarok package itself, if there is zero
> advantage from splitting them.

Yeah, on reflection, I think this makes sense. IMO the lib policy is
generally very good and useful, particularly on 64 vs 32 bit systems,
but I cannot install both amarok in 32 and 64 bit flavours anyway, so
there is no advantage in this regard to splitting it's libs.

That said, it makes the lib policy that bit vaguer and harder to
understand... but it does also help keep orphaned files down.

Col


-- 

Colin Guthrie
mageia(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

Re: [Mageia-dev] Firefox 5

[Donald Stewart]

On 15 June 2011 13:35, Ahmad Samir  wrote:
> On 14 June 2011 14:32, Frank Griffin  wrote:
>> On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
>>>
>>> Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
>>> are two distinct orthogonal things IMHO.
>>>
>>> since firefox5 is near being released, I think we should update
>>> main xulrunner+firefox to 5 anyway
>>>
>> Whatever we do, please don't put it in Core to replace FF4 until the add-ons
>> have been updated.  It was really annoying to lose the Tor add-on for months
>> because the beta FF4 just showed up and replaced FF3, and the Tor add-on
>> wasn't updated until the release or just before.
>>
>
> As I said, we have to have the Beta versions, so as to work out the
> niggles to be ready to push the stable version to stable releases
> (Mageia 1).
>
> You can always workaround the compatibility, either:
> - Adding it manually http://kb.mozillazine.org/Extensions.checkCompatibility 
> OR
> - Using this extension
> https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
>
> in my experience, 90% of the time the addon will work with a new
> version of FF (but then again I use a limited number of addons).
>
> --
> Ahmad Samir
>

I'm with Ahmad, going for beta for testing seems right. The beta
release stage should be long enough for issues to be sorted so aurora
isn't needed.

Re: [Mageia-dev] Firefox 5

[Ahmad Samir]

On 14 June 2011 14:32, Frank Griffin  wrote:
> On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
>>
>> Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
>> are two distinct orthogonal things IMHO.
>>
>> since firefox5 is near being released, I think we should update
>> main xulrunner+firefox to 5 anyway
>>
> Whatever we do, please don't put it in Core to replace FF4 until the add-ons
> have been updated.  It was really annoying to lose the Tor add-on for months
> because the beta FF4 just showed up and replaced FF3, and the Tor add-on
> wasn't updated until the release or just before.
>

As I said, we have to have the Beta versions, so as to work out the
niggles to be ready to push the stable version to stable releases
(Mageia 1).

You can always workaround the compatibility, either:
- Adding it manually http://kb.mozillazine.org/Extensions.checkCompatibility OR
- Using this extension
https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/

in my experience, 90% of the time the addon will work with a new
version of FF (but then again I use a limited number of addons).

-- 
Ahmad Samir

Re: [Mageia-dev] Finalizing update process

[Stew Benedict]

On 06/15/2011 09:22 AM, Stew Benedict wrote:

On 06/15/2011 08:50 AM, Dexter Morgan wrote:

On Wed, Jun 15, 2011 at 2:20 PM, Thomas Backlund  wrote:
BTW, should we have a read-only security/update-announce ml that 
where we

mail about all updates ?

yes seems a must have to push updates descriptions , distributions 
affected, ...



That is accounted for in the policy document (last line)

Due to the unbridled enthusiasm for getting started on updates, we now 
have 4 trial packages :)


vde2, mysql, curl, subversion

Bugs:

https://bugs.mageia.org/show_bug.cgi?id=1678 (vde2)
https://bugs.mageia.org/show_bug.cgi?id=1554 (mysql)
https://bugs.mageia.org/show_bug.cgi?id=1813 (curl)
https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion)

Packages need fixes applied, built for mga1 (I believe mysql is already 
in updates_testing), packager should do some initial testing then 
re-assign the bug to QA


QA process for updates:

http://mageia.org/wiki/doku.php?id=qa_updates



--
Stew Benedict

Re: [Mageia-dev] Firefox 5

[Ahmad Samir]

On 14 June 2011 17:54, Antoine Pitrou  wrote:
> On Tue, 14 Jun 2011 14:14:02 +0200
> Samuel Verschelde 
> wrote:
>>
>> Le mardi 14 juin 2011 13:56:29, Dexter Morgan a écrit :
>> > Hello,
>> >
>> > do we wait firefox 5 rc or we can start to update to firefox 5 soon ?
>>
>> Mandriva now has several packages for firefox (like for chromium), following
>> the upstream channels, maybe we could envision doing it too ?
>
> As a user, I will download the mozilla.org binaries if I want to
> try/test a non-stable release. Not sure there's any point for Mageia in
> packaging beta versions (except to get feedback for distro-specific
> patches).
>
> Just my 2 cents.
>
> Regards
>
> Antoine.
>
>
>

The whole alpha/beta/rc concept has changed a lot in Firefox upstream:
https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/

So, we have to have the Beta versions, so as to work out the niggles
to be ready to push the stable version to stable releases (Mageia 1).

As for Aurora... I don't know I think Beta should be enough, for the
brave souls they can use the upstream binary tarballs, I think

-- 
Ahmad Samir

Re: [Mageia-dev] Firefox 5

[Thierry Vignaud]

On 14 June 2011 17:54, Antoine Pitrou  wrote:
>> > do we wait firefox 5 rc or we can start to update to firefox 5 soon ?
>>
>> Mandriva now has several packages for firefox (like for chromium), following
>> the upstream channels, maybe we could envision doing it too ?
>
> As a user, I will download the mozilla.org binaries if I want to
> try/test a non-stable release. Not sure there's any point for Mageia in
> packaging beta versions (except to get feedback for distro-specific
> patches).

Well, a mdv package would integrate nicely with gnome & kde, aka
it would run oowriter to open a document instead of asking you
to choose an app...

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[José Jorge]

Le mercredi 15 juin 2011 20:27:52, Dexter Morgan a écrit :
> > I can begin the list of the edubuntu packages and check those who
> > already are in Megeia ( with the project name/url/type/packager when
> > it's possible ).

A task-education rpm would be simple to use.

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[Dexter Morgan]

On Wed, Jun 15, 2011 at 7:10 PM, mammig_linux mammig_linux
 wrote:
> Hello
>
> I can begin the list of the edubuntu packages and check those who
> already are in Megeia ( with the project name/url/type/packager when
> it's possible ).
> When the wiki page will be open, we will only have to paste it.
>
> see you
> mammig

This is really a good idea for a start.

i would say : go for it :)

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[Angelo Naselli]

mercoledì 15 giugno 2011 alle 19:10, mammig_linux mammig_linux ha scritto:
> packager
Well packager should mean who of us take care about :)


signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[mammig_linux mammig_linux]

Hello

I can begin the list of the edubuntu packages and check those who
already are in Megeia ( with the project name/url/type/packager when
it's possible ).
When the wiki page will be open, we will only have to paste it.

see you
mammig


2011/6/15 Angelo Naselli :
> mercoledì 15 giugno 2011 alle 17:43, mammig_linux mammig_linux ha scritto:
>> Hello,
> Hello and welcome!
>
>> I'm very interresting by this project.
>> Currently i'm a member of the french i18n team ( transator ) and i
>> never make those strange things you call "package".
>> ( but maybe i can learn how to do it )
>> I will be happy to help you ( if i can )
> As said via irc, we can start collecting the most educational project
> links, maybe starting to add what are into edubuntu and that
> are not in mageia already.
> It could be easier for me -and for other packagers who partecipate-
> to start packaging things, instead of looking for them and working on them 
> after :)
>
> We could start a wiki page in which adding missing packages for instance.
> Something like
> project name - project url - type  - packager
>
> Edu Type could help to get a kind of group info, i mean how they could be
> grouped in.
>
> I'd like to start with international projects, those that have localizations
> and can be used by almost all. Local project should be added by users that can
> maintain them and can *understand* them ;)
>
> WDYT?
>
> Cheeers,
>        Angelo
>
>

Re: [Mageia-dev] Lib policy change needed ?

[Anssi Hannula]

On 15.06.2011 19:15, Ahmad Samir wrote:
> On 15 June 2011 10:44, Christiaan Welvaart  wrote:
>> On Wed, 15 Jun 2011, Dexter Morgan wrote:
>>
>>> the last BS breakage makes me thing that we should adjust our
>>> packaging policy and add only one lib per lib package.
>>>
>>>
>>> On our last BS breakage we had as error :
>>>
>>>
>>> A requested package cannot be installed:
>>> seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))
>>>
>>>
>>> because libgp11.so.0 was in libgcr0 but disappeared.
>>
>> This was of course a packaging error, the version postfix in the package
>> name should have been modified.
>>
>>> WDYT about this new policy ?
>>
>> Fine with me, always considered it strange when the lib version in the pkg
>> name does not correspond to major version of some of the libraries in a
>> package. I agree this policy change or clarification (if followed) will
>> likely prevent such mistakes in the future. And it should not cause any
>> problems since we have automatic library provides and dependencies.
>>
>>
>>Christiaan
>>
> 
> Splitting every single lib in a separate package isn't ideal, IMHO
> (just look at how many kde library packages we have).
> 
> Libraries that have the same major from the same src.rpm should be in
> the same sub-package as much as possible (i.e. all glib-related libs
> in one package, extensions (e.g. nautilus extensions) could be each in
> a sub-package); and split only if something would require one lib but
> not another from that lib package, i.e. split when needed, not
> generally.

I'd do the split when there is a potential for the majors to be
different (i.e. the major numbers are defined separately for each library).

> For example look at Amarok:
> $ urpmf --sourcerpm :amarok | sort | grep lib
> lib64amarokcore1:amarok-2.4.1-0.mga1.src.rpm
> lib64amaroklib1:amarok-2.4.1-0.mga1.src.rpm
> lib64amarokocsclient4:amarok-2.4.1-0.mga1.src.rpm
> lib64amarokpud1:amarok-2.4.1-0.mga1.src.rpm
> lib64amarok-sqlcollection1:amarok-2.4.1-0.mga1.src.rpm
> lib64amarok-transcoding1:amarok-2.4.1-0.mga1.src.rpm
> 
> every lib is in a separate package, even though:
> - Nothing else uses any of those libs other than Amarok
> - Amarok is linked against all of those libs and it wouldn't work if
> you uninstall any of them
> 
> In such a case grouping all of them in one lib*amarok package would be
> easier, there'll never be any file conflicts when the mojor of any of
> them changes.

IMO we should have an exception so that libraries like these that are
related to and required by a single program/package that are not
expected (i.e. there are no header files) to be used by others, should
be packaged in the main package itself.

I.e. I'd put all of those in amarok package itself, if there is zero
advantage from splitting them.

> P.S. I am not a packaging expert.

-- 
Anssi Hannula

Re: [Mageia-dev] Problems with Gnome 3

[Thorsten van Lil]

Am Donnerstag, 9. Juni 2011, 10:44:23 schrieb JA Magallón:
> if I select "System settings" o launch firefox, immediately I get a
> fullscreen error about "something went wrong, plz logout and in again"

Same for me two days back. Since yesterday it works relatively well. I get the 
mentioned error right after login, but: If you just press Alt+F4 the error 
message vanish and you can start working us usual.

Regards,
Thorsten

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[Angelo Naselli]

mercoledì 15 giugno 2011 alle 17:43, mammig_linux mammig_linux ha scritto:
> Hello,
Hello and welcome!

> I'm very interresting by this project.
> Currently i'm a member of the french i18n team ( transator ) and i
> never make those strange things you call "package".
> ( but maybe i can learn how to do it )
> I will be happy to help you ( if i can )
As said via irc, we can start collecting the most educational project
links, maybe starting to add what are into edubuntu and that
are not in mageia already.
It could be easier for me -and for other packagers who partecipate-
to start packaging things, instead of looking for them and working on them 
after :) 

We could start a wiki page in which adding missing packages for instance.
Something like
project name - project url - type  - packager 

Edu Type could help to get a kind of group info, i mean how they could be
grouped in.

I'd like to start with international projects, those that have localizations
and can be used by almost all. Local project should be added by users that can
maintain them and can *understand* them ;)

WDYT?

Cheeers,
Angelo



signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] Tonight's meeting

[Angelo Naselli]

mercoledì 15 giugno 2011 alle 17:00, Anne nicolas ha scritto:
> As usual at 19h UTC on #mageia-dev. Here are the topics
> 
> - post-mortem review
> - quick summary of current cycle release discussion
> - start of stable updates
> - mentoring review
> 
> Cheers !
I cannot attend tonight sorry, i will read all after.

Once we've decided the release cycle etc, i'd like to add
a topic, about my proposal of improving educational 
programs.

It seems people like the idea, I received some private good feed-backs.

What they ask mainly is to have info from main channels (e.g. blog, forum...)
in which users can give their contribution. Before having users requests though,
i believe we need to know how to start/go on this adventure...

I'm ready to go on working on what i started i mageia 1, but i'm also 
need to be honest and tell people clear i do that in my very little spare
time, so i could not probably be able to follow all the requests (and all
our channels).

Is that possible and make sense? -add a future topic, i mean-

Cheers,
Angelo


signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] Lib policy change needed ?

[Ahmad Samir]

On 15 June 2011 10:44, Christiaan Welvaart  wrote:
> On Wed, 15 Jun 2011, Dexter Morgan wrote:
>
>> the last BS breakage makes me thing that we should adjust our
>> packaging policy and add only one lib per lib package.
>>
>>
>> On our last BS breakage we had as error :
>>
>>
>> A requested package cannot be installed:
>> seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))
>>
>>
>> because libgp11.so.0 was in libgcr0 but disappeared.
>
> This was of course a packaging error, the version postfix in the package
> name should have been modified.
>
>> WDYT about this new policy ?
>
> Fine with me, always considered it strange when the lib version in the pkg
> name does not correspond to major version of some of the libraries in a
> package. I agree this policy change or clarification (if followed) will
> likely prevent such mistakes in the future. And it should not cause any
> problems since we have automatic library provides and dependencies.
>
>
>    Christiaan
>

Splitting every single lib in a separate package isn't ideal, IMHO
(just look at how many kde library packages we have).

Libraries that have the same major from the same src.rpm should be in
the same sub-package as much as possible (i.e. all glib-related libs
in one package, extensions (e.g. nautilus extensions) could be each in
a sub-package); and split only if something would require one lib but
not another from that lib package, i.e. split when needed, not
generally.

For example look at Amarok:
$ urpmf --sourcerpm :amarok | sort | grep lib
lib64amarokcore1:amarok-2.4.1-0.mga1.src.rpm
lib64amaroklib1:amarok-2.4.1-0.mga1.src.rpm
lib64amarokocsclient4:amarok-2.4.1-0.mga1.src.rpm
lib64amarokpud1:amarok-2.4.1-0.mga1.src.rpm
lib64amarok-sqlcollection1:amarok-2.4.1-0.mga1.src.rpm
lib64amarok-transcoding1:amarok-2.4.1-0.mga1.src.rpm

every lib is in a separate package, even though:
- Nothing else uses any of those libs other than Amarok
- Amarok is linked against all of those libs and it wouldn't work if
you uninstall any of them

In such a case grouping all of them in one lib*amarok package would be
easier, there'll never be any file conflicts when the mojor of any of
them changes.

P.S. I am not a packaging expert.

-- 
Ahmad Samir

[Mageia-dev] nspluginwrapper reborn!

[Ahmad Samir]

Hello,

nspluginwrapper has been updated to 1.3.x and now to 1.4.x, i.e. it
has a new upstream maintainer http://nspluginwrapper.davidben.net

For the first time in probably 2-3years, the 32bit Adobe Flash player
seemed to work for me in a 64bit browser (I tested firefox and
konqueror).

So give it a shot.

(I've been suggesting, to users, _not_ to use nspluginwrapper for some
years now, since it never worked for me and I saw a lot of reports of
it not working in forums and bug reports, so this is my "I take that
back, it just needed some upstream love and care").

-- 
Ahmad Samir

Re: [Mageia-dev] Mageia 2 - Improving educational programs

[mammig_linux mammig_linux]

Hello,

I'm very interresting by this project.
Currently i'm a member of the french i18n team ( transator ) and i
never make those strange things you call "package".
( but maybe i can learn how to do it )
I will be happy to help you ( if i can )

see you,
mammig

Re: [Mageia-dev] [RPM] cauldron core/release task-gnome-2-0.1.mga2

[Dexter Morgan]

On Wed, Jun 15, 2011 at 5:05 PM, Thierry Vignaud
 wrote:
> On 15 June 2011 16:29, Dexter Morgan  wrote:
>>> Shouldn't we have task-gnome3?
>>> Or do we plan to just have gnome3 in Mga2?
>>
>> in fact i named it task-gnome because this is supposed to be '"main
>> gnome"
>
> That's fine
>
>> but i see no pb to rename it to task-gnom3 , just that i think
>> it will add useless provides/obsoletes
>
> Logically we should got task-gnome & task-gnome2 if we ever support both
>

i am fine with this naming too.

Re: [Mageia-dev] [RPM] cauldron core/release task-gnome-2-0.1.mga2

[Thierry Vignaud]

On 15 June 2011 16:29, Dexter Morgan  wrote:
>> Shouldn't we have task-gnome3?
>> Or do we plan to just have gnome3 in Mga2?
>
> in fact i named it task-gnome because this is supposed to be '"main
> gnome"

That's fine

> but i see no pb to rename it to task-gnom3 , just that i think
> it will add useless provides/obsoletes

Logically we should got task-gnome & task-gnome2 if we ever support both

[Mageia-dev] Tonight's meeting

[Anne nicolas]

As usual at 19h UTC on #mageia-dev. Here are the topics

- post-mortem review
- quick summary of current cycle release discussion
- start of stable updates
- mentoring review

Cheers !

-- 
Anne
http://www.mageia.org

Re: [Mageia-dev] [RPM] cauldron core/release task-gnome-2-0.1.mga2

[Dexter Morgan]

On Wed, Jun 15, 2011 at 3:31 PM, Thierry Vignaud
 wrote:
> On 15 June 2011 12:07, Mageia Team  wrote:
>> dmorgan  1:2-0.1.mga2:
>> + Revision: 106759
>> - Add some more requires for gnome3
>> - Remove buildroot
>>  Remove old obsoletes
>
> Shouldn't we have task-gnome3?
> Or do we plan to just have gnome3 in Mga2?
> See you
>

in fact i named it task-gnome because this is supposed to be '"main
gnome" but i see no pb to rename it to task-gnom3 , just that i think
it will add useless provides/obsoletes

Re: [Mageia-dev] Release cycles proposals, and discussion

[Olav Vitters]

On Sun, Jun 12, 2011 at 10:46:33PM +0200, Michael Scherer wrote:
> Proposal 1: 
> 6 months release cycle -> 12 months life cycle

> Proposal 2: 
> 9 months release cycle -> 18 months life cycle  

> Proposal 3: 
> 12 months release cycle -> 24 months life cycle


Regarding release cycles from a GNOME perspective (so 6 months):
+ 6 months is great for stability; with the various freezes and so on,
  there is not a lot of development going on, so code doesn't become too
  unstable

+ very predictable for everyone (releases + freezes are always in the
same period)

+ more immediate feedback from users

- developers might get too focussed on the 6 months, and development
  might slow down after a few years (happened with GNOME 2.x until 3.0
  was suggested)
  to avoid it you need something like a 'feature map' (plan beforehand
  what to do next and when you think the development would be done;
  don't focus too much on the next version)

- big changes are difficult to do in 6 months; though you can branch and
  so on, it isn't always possible (interaction between modules and so
  on)
  e.g. new GDM or the gnome-vfs -> gvfs switch

- stable release is not supported/looked after for too long

Distribution is of course different from just software, so feel free to
ignore.

There was discussion in the past to make a release every 6 months, but
work on it for 9 (there would be a 3 month overlap where developers had
to work on both branches). E.g. by having a restricted 'Mageia 2' while
still having an 'anything goes' Cauldron.
-- 
Regards,
Olav

Re: [Mageia-dev] [RPM] cauldron core/release task-gnome-2-0.1.mga2

[Christiaan Welvaart]

On Wed, 15 Jun 2011, Thierry Vignaud wrote:


On 15 June 2011 12:07, Mageia Team  wrote:

dmorgan  1:2-0.1.mga2:
+ Revision: 106759
- Add some more requires for gnome3
- Remove buildroot
 Remove old obsoletes


Shouldn't we have task-gnome3?
Or do we plan to just have gnome3 in Mga2?


If someone fixes gnome2 so it's parallel installable we can have a 
task-gnome2.



Christiaan

Re: [Mageia-dev] [RPM] cauldron core/release task-gnome-2-0.1.mga2

[Thierry Vignaud]

On 15 June 2011 12:07, Mageia Team  wrote:
> dmorgan  1:2-0.1.mga2:
> + Revision: 106759
> - Add some more requires for gnome3
> - Remove buildroot
>  Remove old obsoletes

Shouldn't we have task-gnome3?
Or do we plan to just have gnome3 in Mga2?
See you

Re: [Mageia-dev] Finalizing update process

[Stew Benedict]

On 06/15/2011 08:50 AM, Dexter Morgan wrote:

On Wed, Jun 15, 2011 at 2:20 PM, Thomas Backlund  wrote:

BTW, should we have a read-only security/update-announce ml that where we
mail about all updates ?


yes seems a must have to push updates descriptions , distributions affected, ...


That is accounted for in the policy document (last line)

--
Stew Benedict

Re: [Mageia-dev] [RPM] cauldron core/release networkmanager-0.8.9997-0.1.1.mga2

[John Balcaen]

2011/6/15 JA Magallón :
[...]
>
> This is missing the 'ifcfg-mdv' and 'keyfile' plugins...
>
in fact only the ifcfg-mdv plugin is really missing.
keyfile should be available.

-- 
Balcaen John

Re: [Mageia-dev] Finalizing update process

[Dexter Morgan]

On Wed, Jun 15, 2011 at 2:20 PM, Thomas Backlund  wrote:
>
> BTW, should we have a read-only security/update-announce ml that where we
> mail about all updates ?
>
yes seems a must have to push updates descriptions , distributions affected, ...

Re: [Mageia-dev] [RPM] cauldron core/release networkmanager-0.8.9997-0.1.1.mga2

[Dexter Morgan]

On Tue, Jun 14, 2011 at 8:12 PM, Mageia Team
 wrote:
> Name        : networkmanager               Relocations: (not relocatable)
> Version     : 0.8.9997                          Vendor: Mageia.Org
> Release     : 0.1.1.mga2                    Build Date: Tue Jun 14 20:07:17 
> 2011
> Install Date: (not installed)               Build Host: ecosse
> Group       : System/Base                   Source RPM: (none)
> Size        : 1554806                          License: GPLv2+
> Signature   : (none)
> Packager    : Mageia Team 
> URL         : http://www.gnome.org/projects/NetworkManager/
> Summary     : Network connection manager and user applications
> Description :
> NetworkManager attempts to keep an active network connection available at all
> times.  It is intended only for the desktop use-case, and is not intended for
> usage on servers.   The point of NetworkManager is to make networking
> configuration and setup as painless and automatic as possible.  If using DHCP,
> NetworkManager is _intended_ to replace default routes, obtain IP addresses
> from a DHCP server, and change nameservers whenever it sees fit.
>
> dmorgan  0.8.9997-0.1.1.mga2:
> + Revision: 106192
> - Use autogen.sh
> - New version 0.8.9997

Yes i added a comment on the spec file telling  this need to be rediffed.

Re: [Mageia-dev] [RPM] cauldron core/release networkmanager-0.8.9997-0.1.1.mga2

[JA Magallón]

On Tue, 14 Jun 2011 20:12:24 +0200 (CEST), Mageia Team 
 wrote:

> Name: networkmanager   Relocations: (not relocatable)
> Version : 0.8.9997  Vendor: Mageia.Org
> Release : 0.1.1.mga2Build Date: Tue Jun 14 20:07:17 
> 2011
> Install Date: (not installed)   Build Host: ecosse
> Group   : System/Base   Source RPM: (none)
> Size: 1554806  License: GPLv2+
> Signature   : (none)
> Packager: Mageia Team 
> URL : http://www.gnome.org/projects/NetworkManager/
> Summary : Network connection manager and user applications
> Description :
> NetworkManager attempts to keep an active network connection available at all
> times.  It is intended only for the desktop use-case, and is not intended for
> usage on servers.   The point of NetworkManager is to make networking
> configuration and setup as painless and automatic as possible.  If using DHCP,
> NetworkManager is _intended_ to replace default routes, obtain IP addresses
> from a DHCP server, and change nameservers whenever it sees fit.
> 
> dmorgan  0.8.9997-0.1.1.mga2:
> + Revision: 106192
> - Use autogen.sh
> - New version 0.8.9997

This is missing the 'ifcfg-mdv' and 'keyfile' plugins...

-- 
J.A. Magallon  \ Winter is coming...

Re: [Mageia-dev] Finalizing update process

[Thomas Backlund]

Michael Scherer skrev 15.6.2011 15:10:

Le mercredi 15 juin 2011 à 07:55 -0400, Stew Benedict a écrit :

On 06/12/2011 08:25 AM, Angelo Naselli wrote:

In data mercoledì 8 giugno 2011 23:53:51, Ahmad Samir ha scritto:

Right, I probably phrased that one wrongly; I meant:
fixes a serious bug, e.g. crashing, segfaulting

I don't think we should exclude non-serious bugs :)

Depends, overworking the sec team doesn't look like a good aspect...
(that's why I liked contrib in mdv, I could push an update any time,
without having to go though the bug report ->   QA ->   Sec team loop).

Well here we could stop at QA team step, or at least someone more that can
test  and say that the fixing is good...


So,

We've had a lot of discussion, which is good, but imho we need to start
getting some updates out the door. Users are asking for them and the
CVEs just keep rolling in.

As I understand it, the mechanics are in place to issue updates, and
I've put together a page as a first pass at a policy, based on my memory
of how things worked in the past and what I've picked up from the
discussion.

http://mageia.org/wiki/doku.php?id=updates_policy

Randomly, I'm targeting 2 bugs to push through, to test the process:

https://bugs.mageia.org/show_bug.cgi?id=1084 (vde2, app crashes)
https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion, security issue)

Now, first problem is we still don't have a maintainer database, so who
gets the assignment, the person that first imported the package?
Perhaps this is the first change to the policy - maintainer or any
interested packager initiates the update


Sound sensible, yes.

The idea IMHO is not to prevent people for doing the work if they wish,
but if there is no volunteer, it should be the duty of someone, and this
someone is the maintainer.
Now, we do not have a official maintainer db, but the test instance is
still here afaik. So yes, picking someone from the list of person that
committed would do the trick.



BTW, should we have a read-only security/update-announce ml that where 
we mail about all updates ?


--
Thomas

Re: [Mageia-dev] Release cycles proposals, and discussion - messages from the forum

[lebarhon]

  
  
by dave
» Jun 14th, '11, 22:32
One release every year with the related updated
  (don't wait one year for have ad updated software) is better. The
  best could be an half-rolling like chakra but this option isn't in
  the proposals 


  

Re: [Mageia-dev] Finalizing update process

[Michael Scherer]

Le mercredi 15 juin 2011 à 07:55 -0400, Stew Benedict a écrit :
> On 06/12/2011 08:25 AM, Angelo Naselli wrote:
> > In data mercoledì 8 giugno 2011 23:53:51, Ahmad Samir ha scritto:
>  Right, I probably phrased that one wrongly; I meant:
>  fixes a serious bug, e.g. crashing, segfaulting
> >>> I don't think we should exclude non-serious bugs :)
> >> Depends, overworking the sec team doesn't look like a good aspect...
> >> (that's why I liked contrib in mdv, I could push an update any time,
> >> without having to go though the bug report ->  QA ->  Sec team loop).
> > Well here we could stop at QA team step, or at least someone more that can
> > test  and say that the fixing is good...
> >
> So,
> 
> We've had a lot of discussion, which is good, but imho we need to start 
> getting some updates out the door. Users are asking for them and the 
> CVEs just keep rolling in.
> 
> As I understand it, the mechanics are in place to issue updates, and 
> I've put together a page as a first pass at a policy, based on my memory 
> of how things worked in the past and what I've picked up from the 
> discussion.
> 
> http://mageia.org/wiki/doku.php?id=updates_policy
> 
> Randomly, I'm targeting 2 bugs to push through, to test the process:
> 
> https://bugs.mageia.org/show_bug.cgi?id=1084 (vde2, app crashes)
> https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion, security issue)
> 
> Now, first problem is we still don't have a maintainer database, so who 
> gets the assignment, the person that first imported the package?
> Perhaps this is the first change to the policy - maintainer or any 
> interested packager initiates the update

Sound sensible, yes.

The idea IMHO is not to prevent people for doing the work if they wish,
but if there is no volunteer, it should be the duty of someone, and this
someone is the maintainer.
Now, we do not have a official maintainer db, but the test instance is
still here afaik. So yes, picking someone from the list of person that
committed would do the trick. 

-- 
Michael Scherer

Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/15 Olav Vitters :
> On Wed, Jun 15, 2011 at 01:22:54PM +0200, Wolfgang Bornath wrote:
>> Installed the packages including dependencies, rebooted, logged in for
>> Gnome3 - same result!
>
> Could you also run:
>  gnome-shell --replace > ~/tmp/gnome-shell-log 2>&1
>
> >From e.g. XFCE? This as I wonder what error messages gnome-shell
> produces.

Did it in a xterm in icewm - hitting [Enter] with this command string
*immediately* kicked me out of the session and restarted xserver.

Contents of ~/tmp/gnome-shell-log is:
---
Fensterverwalter-Warnung:Thema »Adwaita« konnte nicht geladen werden:
Es konnte keine gültige Datei für das Thema »Adwaita« gefunden werden
---
Translates to:
windowmanager-warning: Theme "Adwaita" could not be loaded. No valid
file found for theme "Adwaita".

BTW: Before I carried out the command I did an update, last mirror
sync was 11:30 UTC (32 minutes ago)

-- 
wobo

Re: [Mageia-dev] Finalizing update process

[Stew Benedict]

On 06/12/2011 08:25 AM, Angelo Naselli wrote:

In data mercoledì 8 giugno 2011 23:53:51, Ahmad Samir ha scritto:

Right, I probably phrased that one wrongly; I meant:
fixes a serious bug, e.g. crashing, segfaulting

I don't think we should exclude non-serious bugs :)

Depends, overworking the sec team doesn't look like a good aspect...
(that's why I liked contrib in mdv, I could push an update any time,
without having to go though the bug report ->  QA ->  Sec team loop).

Well here we could stop at QA team step, or at least someone more that can
test  and say that the fixing is good...


So,

We've had a lot of discussion, which is good, but imho we need to start 
getting some updates out the door. Users are asking for them and the 
CVEs just keep rolling in.


As I understand it, the mechanics are in place to issue updates, and 
I've put together a page as a first pass at a policy, based on my memory 
of how things worked in the past and what I've picked up from the 
discussion.


http://mageia.org/wiki/doku.php?id=updates_policy

Randomly, I'm targeting 2 bugs to push through, to test the process:

https://bugs.mageia.org/show_bug.cgi?id=1084 (vde2, app crashes)
https://bugs.mageia.org/show_bug.cgi?id=1521 (subversion, security issue)

Now, first problem is we still don't have a maintainer database, so who 
gets the assignment, the person that first imported the package?
Perhaps this is the first change to the policy - maintainer or any 
interested packager initiates the update


--
Stew Benedict

Re: [Mageia-dev] dokuwiki import

[Cazzaniga Sandro]

Le 15/06/2011 10:17, Cazzaniga Sandro a écrit :
> hi,
> 
> I've updated and imported dokuwiki
> (https://bugs.mageia.org/show_bug.cgi?id=1096). Can someone review it
> before push, please?
> 
> thanks in advance.
Any answers. I push it.

-- 
Sandro Cazzaniga - https://lederniercoupdarchet.wordpress.com
IRC: Kharec (irc.freenode.net)
Software/Hardware geek
Conceptor
Magnum's Coordinator/editor (http://magnum.tuxfamily.org)
Mageia and Mandriva contributor

Re: [Mageia-dev] Problems with Gnome 3

[Olav Vitters]

On Wed, Jun 15, 2011 at 01:22:54PM +0200, Wolfgang Bornath wrote:
> Installed the packages including dependencies, rebooted, logged in for
> Gnome3 - same result!

Could you also run:
  gnome-shell --replace > ~/tmp/gnome-shell-log 2>&1

>From e.g. XFCE? This as I wonder what error messages gnome-shell
produces.

Regarding the xsession stuff. The network manager seems to be that it
couldn't find the dbus service.

The 'failed to register' seems to be related to gnome-power-manager:
https://bugzilla.redhat.com/show_bug.cgi?id=480206
-- 
Regards,
Olav

Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/15 Dexter Morgan :
>
> can you try to install :
>
> networkmanager
> adwaita-gtk3-theme
> adwaita-cursor-theme
>
> and to restart gnome 3 ?

Installed the packages including dependencies, rebooted, logged in for
Gnome3 - same result!
The warning about networkmanager is gone but some others came up. I
saved .xsession-errors in the state when the desktop error message
appeared on the screen.

Attached is xsession-errors.sav

-- 
wobo


xsession-errors.sav
Description: Binary data

Re: [Mageia-dev] Problems with Gnome 3

[Dexter Morgan]

On Wed, Jun 15, 2011 at 12:06 PM, Christiaan Welvaart
 wrote:
> On Wed, 15 Jun 2011, Wolfgang Bornath wrote:
>
>> BTW: I get the same errors when starting Gnome (2.x) on the same system.
>
> How do you start it? There's no gnome 2.x session listed in gdm, both
> 'GNOME' and GNOME3' are gnome 3 sessions (without any difference AFAIK). I
> was thinking of making the current 'GNOME' start up a 'fallback' session,
> while current 'GNOME3' would stay automatic: 'shell' session switching to
> 'fallback' when no 3d acceleration is available. But this is not entirely
> trivial.
>
>
>    Christiaan
>

For now there is only Gnome ( the Gnome 3 preview is not here anymore
)  but as soon as you know how to start the fallback session we will
be able to readd Gnome 3 startup

Re: [Mageia-dev] Problems with Gnome 3

[Christiaan Welvaart]

On Wed, 15 Jun 2011, Wolfgang Bornath wrote:


BTW: I get the same errors when starting Gnome (2.x) on the same system.


How do you start it? There's no gnome 2.x session listed in gdm, both 
'GNOME' and GNOME3' are gnome 3 sessions (without any difference AFAIK). I 
was thinking of making the current 'GNOME' start up a 'fallback' session, 
while current 'GNOME3' would stay automatic: 'shell' session switching 
to 'fallback' when no 3d acceleration is available. But this is not 
entirely trivial.



Christiaan

Re: [Mageia-dev] Problems with Gnome 3

[Dexter Morgan]

On Wed, Jun 15, 2011 at 11:02 AM, Wolfgang Bornath
 wrote:
> 2011/6/15 Dexter Morgan :
>> On Wed, Jun 15, 2011 at 10:34 AM, Wolfgang Bornath
>>  wrote:
>>> 2011/6/15 Dexter Morgan :
 On Wed, Jun 15, 2011 at 3:02 AM, Wolfgang Bornath
  wrote:
> 2011/6/15 Frank Griffin :
>> On 06/14/2011 06:40 PM, Dexter Morgan wrote:
>>>
>>> Do you have gnome-control-center installed
>>
>> I have the same situation, and gnome-control-center is installed.
>
> Confirmed, same problem.
>
> Just switched a Mageia 1 to Cauldron via urpmi, installed task-gnome, no 
> errors.
> After reboot and selecting Gnome3 the desktop builds nicely but as
> soon as I start any application after a couple of seconds I get the
> same error message, pressing "OK" does a restart of the xserver and
> I'm back at login.

 Do you have errors in your .xsession-errors ?
>>>
>>> Yes. lots of them! Many things are missing:
>>>  - Theme "Adwaita" can't be loaded, file not found
>>>  - JS ERROR about NetworkManager
>>>  - gnome-session WARNING: Application 'gnome-shell.desktop' failed to
>>> register before timeout
>>>  - failed to play sound: file or data not found
>>>  ... and more
>>>
>>> Last section of errors is:
>>> ---
>>> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
>>> assertion 'CLUTTER_IS_ACTOR (self) failed
>>> Cannot open /dev/input/eventX: permission denied ## this was repeated 15 
>>> times
>>>
>>> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
>>> assertion 'CLUTTER_IS_ACTOR (self) failed
>>> --EOF-
>>>
>>
>> ok tks,  this is mor ethan task-gnome miss them.
>>
>> I will fix task-gnome and push it really quickly
>
> Take your time, Gnome3 is not on my priority list :)
> BTW: I get the same errors when starting Gnome (2.x) on the same system.
>
> Other installed DEs working fine (KDE, icewm)
> --
> wobo
>

can you try to install :

networkmanager
adwaita-gtk3-theme
adwaita-cursor-theme

and to restart gnome 3 ?

Re: [Mageia-dev] Broken BS

[Dexter Morgan]

On Wed, Jun 15, 2011 at 10:16 AM, Dexter Morgan  wrote:
> Hi,
>
> sorry the update of gnome keyring broke the BS.
>
> I am fixing it .
>

The BS is now fixed .

Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/15 Dexter Morgan :
> On Wed, Jun 15, 2011 at 10:34 AM, Wolfgang Bornath
>  wrote:
>> 2011/6/15 Dexter Morgan :
>>> On Wed, Jun 15, 2011 at 3:02 AM, Wolfgang Bornath
>>>  wrote:
 2011/6/15 Frank Griffin :
> On 06/14/2011 06:40 PM, Dexter Morgan wrote:
>>
>> Do you have gnome-control-center installed
>
> I have the same situation, and gnome-control-center is installed.

 Confirmed, same problem.

 Just switched a Mageia 1 to Cauldron via urpmi, installed task-gnome, no 
 errors.
 After reboot and selecting Gnome3 the desktop builds nicely but as
 soon as I start any application after a couple of seconds I get the
 same error message, pressing "OK" does a restart of the xserver and
 I'm back at login.
>>>
>>> Do you have errors in your .xsession-errors ?
>>
>> Yes. lots of them! Many things are missing:
>>  - Theme "Adwaita" can't be loaded, file not found
>>  - JS ERROR about NetworkManager
>>  - gnome-session WARNING: Application 'gnome-shell.desktop' failed to
>> register before timeout
>>  - failed to play sound: file or data not found
>>  ... and more
>>
>> Last section of errors is:
>> ---
>> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
>> assertion 'CLUTTER_IS_ACTOR (self) failed
>> Cannot open /dev/input/eventX: permission denied ## this was repeated 15 
>> times
>>
>> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
>> assertion 'CLUTTER_IS_ACTOR (self) failed
>> --EOF-
>>
>
> ok tks,  this is mor ethan task-gnome miss them.
>
> I will fix task-gnome and push it really quickly

Take your time, Gnome3 is not on my priority list :)
BTW: I get the same errors when starting Gnome (2.x) on the same system.

Other installed DEs working fine (KDE, icewm)
-- 
wobo

Re: [Mageia-dev] Lib policy change needed ?

[Christiaan Welvaart]

On Wed, 15 Jun 2011, Dexter Morgan wrote:


the last BS breakage makes me thing that we should adjust our
packaging policy and add only one lib per lib package.


On our last BS breakage we had as error :


A requested package cannot be installed:
seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))


because libgp11.so.0 was in libgcr0 but disappeared.


This was of course a packaging error, the version postfix in the package 
name should have been modified.



WDYT about this new policy ?


Fine with me, always considered it strange when the lib version in the pkg 
name does not correspond to major version of some of the libraries in a 
package. I agree this policy change or clarification (if followed) will 
likely prevent such mistakes in the future. And it should not cause any 
problems since we have automatic library provides and dependencies.



Christiaan

Re: [Mageia-dev] Problems with Gnome 3

[Dexter Morgan]

On Wed, Jun 15, 2011 at 10:34 AM, Wolfgang Bornath
 wrote:
> 2011/6/15 Dexter Morgan :
>> On Wed, Jun 15, 2011 at 3:02 AM, Wolfgang Bornath
>>  wrote:
>>> 2011/6/15 Frank Griffin :
 On 06/14/2011 06:40 PM, Dexter Morgan wrote:
>
> Do you have gnome-control-center installed

 I have the same situation, and gnome-control-center is installed.
>>>
>>> Confirmed, same problem.
>>>
>>> Just switched a Mageia 1 to Cauldron via urpmi, installed task-gnome, no 
>>> errors.
>>> After reboot and selecting Gnome3 the desktop builds nicely but as
>>> soon as I start any application after a couple of seconds I get the
>>> same error message, pressing "OK" does a restart of the xserver and
>>> I'm back at login.
>>
>> Do you have errors in your .xsession-errors ?
>
> Yes. lots of them! Many things are missing:
>  - Theme "Adwaita" can't be loaded, file not found
>  - JS ERROR about NetworkManager
>  - gnome-session WARNING: Application 'gnome-shell.desktop' failed to
> register before timeout
>  - failed to play sound: file or data not found
>  ... and more
>
> Last section of errors is:
> ---
> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
> assertion 'CLUTTER_IS_ACTOR (self) failed
> Cannot open /dev/input/eventX: permission denied ## this was repeated 15 times
>
> (gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
> assertion 'CLUTTER_IS_ACTOR (self) failed
> --EOF-
>
> --
> wobo
>

ok tks,  this is mor ethan task-gnome miss them.

I will fix task-gnome and push it really quickly

Re: [Mageia-dev] Lib policy change needed ?

[Dexter Morgan]

On Wed, Jun 15, 2011 at 10:32 AM, Colin Guthrie  wrote:
> 'Twas brillig, and Dexter Morgan at 15/06/11 09:26 did gyre and gimble:
>> hello
>>
>> the last BS breakage makes me thing that we should adjust our
>> packaging policy and add only one lib per lib package.
>>
>>
>> On our last BS breakage we had as error :
>>
>>
>> A requested package cannot be installed:
>> seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))
>>
>>
>> because libgp11.so.0 was in libgcr0 but disappeared.
>>
>> if it was on libgp11_0 we would have been able to rebuilde seahorse
>> against new libgcr-devel and the remove libgp11_0 when not needed
>> anymore .
>>
>>
>> WDYT about this new policy ?
>
> I'm not 100% sure it's all that different anyway. The same issue would
> be true of sticking two libs into one lib package when they happen to
> have the same major, but they later diverge and one of them changes
> major before the other...

Yes this is why i think we should enforce "one lib per package".


> I guess it's just good practice to keep things
> separated out and I'm not sure the current lib policy actively
> encourages the opposite.
>
> I'd say this is more of clarification of the policy :)

Maybe  but clarification is always good :D

Re: [Mageia-dev] Problems with Gnome 3

[Wolfgang Bornath]

2011/6/15 Dexter Morgan :
> On Wed, Jun 15, 2011 at 3:02 AM, Wolfgang Bornath
>  wrote:
>> 2011/6/15 Frank Griffin :
>>> On 06/14/2011 06:40 PM, Dexter Morgan wrote:

 Do you have gnome-control-center installed
>>>
>>> I have the same situation, and gnome-control-center is installed.
>>
>> Confirmed, same problem.
>>
>> Just switched a Mageia 1 to Cauldron via urpmi, installed task-gnome, no 
>> errors.
>> After reboot and selecting Gnome3 the desktop builds nicely but as
>> soon as I start any application after a couple of seconds I get the
>> same error message, pressing "OK" does a restart of the xserver and
>> I'm back at login.
>
> Do you have errors in your .xsession-errors ?

Yes. lots of them! Many things are missing:
 - Theme "Adwaita" can't be loaded, file not found
 - JS ERROR about NetworkManager
 - gnome-session WARNING: Application 'gnome-shell.desktop' failed to
register before timeout
 - failed to play sound: file or data not found
 ... and more

Last section of errors is:
---
(gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
assertion 'CLUTTER_IS_ACTOR (self) failed
Cannot open /dev/input/eventX: permission denied ## this was repeated 15 times

(gnome-shell:5091): Clutter-CRITICAL **: clutter_actor_queue_relayout:
assertion 'CLUTTER_IS_ACTOR (self) failed
--EOF-

-- 
wobo

Re: [Mageia-dev] Lib policy change needed ?

[Colin Guthrie]

'Twas brillig, and Dexter Morgan at 15/06/11 09:26 did gyre and gimble:
> hello
> 
> the last BS breakage makes me thing that we should adjust our
> packaging policy and add only one lib per lib package.
> 
> 
> On our last BS breakage we had as error :
> 
> 
> A requested package cannot be installed:
> seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))
> 
> 
> because libgp11.so.0 was in libgcr0 but disappeared.
> 
> if it was on libgp11_0 we would have been able to rebuilde seahorse
> against new libgcr-devel and the remove libgp11_0 when not needed
> anymore .
> 
> 
> WDYT about this new policy ?

I'm not 100% sure it's all that different anyway. The same issue would
be true of sticking two libs into one lib package when they happen to
have the same major, but they later diverge and one of them changes
major before the other... I guess it's just good practice to keep things
separated out and I'm not sure the current lib policy actively
encourages the opposite.

I'd say this is more of clarification of the policy :)

Col


-- 

Colin Guthrie
mageia(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

[Mageia-dev] Lib policy change needed ?

[Dexter Morgan]

hello

the last BS breakage makes me thing that we should adjust our
packaging policy and add only one lib per lib package.


On our last BS breakage we had as error :


A requested package cannot be installed:
seahorse-2.32.0-2.mga1.x86_64 (due to unsatisfied libgp11.so.0()(64bit))


because libgp11.so.0 was in libgcr0 but disappeared.

if it was on libgp11_0 we would have been able to rebuilde seahorse
against new libgcr-devel and the remove libgp11_0 when not needed
anymore .


WDYT about this new policy ?

[Mageia-dev] dokuwiki import

[Cazzaniga Sandro]

hi,

I've updated and imported dokuwiki
(https://bugs.mageia.org/show_bug.cgi?id=1096). Can someone review it
before push, please?

thanks in advance.
-- 
Sandro Cazzaniga - https://lederniercoupdarchet.wordpress.com
IRC: Kharec (irc.freenode.net)
Software/Hardware geek
Conceptor
Magnum's Coordinator/editor (http://magnum.tuxfamily.org)
Mageia and Mandriva contributor

[Mageia-dev] Broken BS

[Dexter Morgan]

Hi,

sorry the update of gnome keyring broke the BS.

I am fixing it .

Re: [Mageia-dev] Problems with Gnome 3

[Dexter Morgan]

On Wed, Jun 15, 2011 at 1:03 AM, Frank Griffin  wrote:
> On 06/14/2011 06:40 PM, Dexter Morgan wrote:
>>
>> Do you have gnome-control-center installed
>
> I have the same situation, and gnome-control-center is installed.
>
> I think it's time for you to actually test the reproducible cases we've
> given you.  Unless you have first-hand knowledge that your packages actually
> work in some scenario, the indication is that they don't work at all,
> anywhere.  So please either fix them, or withdraw them until they are
> functional.
>
>

i will install a mageia 1 on the new machine i just received .