Folks,
WRT https://bugs.mageia.org/show_bug.cgi?id=1659
[Bug 1659] Calibre is too old (0.7.32 vs. 0.8.4, i.e. 31 versions behind!)
Two people asserted that a newer calibre package should go into backports, not
updates.
I strongly believe quite the contrary.
I'd like to bring to your attenti
On 13/06/11 10:51, Radu-Cristian FOTESCU wrote:
Therefore, I strongly believe that all calibre updates be packaged
into updates, not backports, especially as there isn't any Mageia 2.0
as of yet.
The reference to backporting means backporting from Cauldron.
Jim
>Two people asserted that a newer calibre package should go into backports, not
>updates.
I said also that there could be exceptions...
> Therefore, I strongly believe that all calibre updates be packaged into
> updates, not backports, especially as there isn't any Mageia 2.0 as of yet.
> Onc
Le lundi 13 juin 2011 à 02:51 -0700, Radu-Cristian FOTESCU a écrit :
> Folks,
>
> WRT https://bugs.mageia.org/show_bug.cgi?id=1659
> [Bug 1659] Calibre is too old (0.7.32 vs. 0.8.4, i.e. 31 versions behind!)
>
>
> Two people asserted that a newer calibre package should go into backports,
> not
> So why does it have to be treated differently than the others since
> there is nothing special about this release cycle ?
Michael, please give me an example of an application that releases on average 5
time a month. Really, give me an example.
And, like it or not, calibre is _THE_ applicati
Le mardi 14 juin 2011 à 03:00 -0700, Radu-Cristian FOTESCU a écrit :
>
> > So why does it have to be treated differently than the others since
> > there is nothing special about this release cycle ?
>
> Michael, please give me an example of an application that releases on average
> 5 time a mon
martedì 14 giugno 2011 alle 12:00, Radu-Cristian FOTESCU ha scritto:
> Fedora made a better judgment
I didn't find my commoncpp2 version there, for me is blocking, they
ship 0.7.x and 0.8.x is out with *important* fixings!
Every time a kernel update (upgrade) is pushed, we need to wait
nvidia kerne
2011/6/14 Angelo Naselli
> martedì 14 giugno 2011 alle 12:00, Radu-Cristian FOTESCU ha scritto:
> .
>
> Said that every distros have problems. Mageia has no monodevelop
> for me taht's blocking as well...
>
I will push monodevelop in svn asap (maybe this evening), for the revision
of my ment
> 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 up
On 14 June 2011 15:52, Angelo Naselli wrote:
> martedì 14 giugno 2011 alle 12:00, Radu-Cristian FOTESCU ha scritto:
>> Fedora made a better judgment
> I didn't find my commoncpp2 version there, for me is blocking, they
> ship 0.7.x and 0.8.x is out with *important* fixings!
> Every time a kernel u
On Tue, 14 Jun 2011, Radu-Cristian FOTESCU wrote:
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.
This will ultimately be up to the peo
Le mardi 14 juin 2011 13:28:43, Ahmad Samir a écrit :
> On 14 June 2011 15:52, Angelo Naselli wrote:
> > martedì 14 giugno 2011 alle 12:00, Radu-Cristian FOTESCU ha scritto:
> >> Fedora made a better judgment
> > I didn't find my commoncpp2 version there, for me is blocking, they
> > ship 0.7.x an
> Would this 'backports' repository section sound better to you if it is
> renamed e.g. to 'rolling' ? (:
No, backports sounds very bad, except maybe for people coming from Mandriva.
They (you!) must love the concept.
(Oh, maybe "trolling" instead of "rolling" :-))
Let me put it this way. Pe
I
> > (FWIW I've not seen the nvidia proprietary kernel module fail to
> > compile in about 6-8months, and the kernel got updated many times
> > during the previous Cauldron release cycle).
>
> Maybe he was talking about fglrx :)
and not in Cauldron but in fedora not the last kernel update tho
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
>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 pers
Le jeudi 16 juin 2011 00:57:45, Radu-Cristian FOTESCU a écrit :
> 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).)
>
Or, like some of u
Radu-Cristian FOTESCU a écrit :
From: andre999
[...]
...
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
su
>So what I propose is that you seriously consider packaging your application
>for Mageia.
>We find a mentor for you to apprentice with, to familiarise you with the
>process.
>In choosing a mentor, it would help to find someone in the same time zone.
>You're in Canada ? What time zone ?
>(I'd off
On 13 June 2011 11:51, Radu-Cristian FOTESCU wrote:
> Therefore, I strongly believe that all calibre updates be packaged into
> updates, not backports, especially as there isn't any Mageia 2.0 as of yet.
> Once Mageia 2.0 is released, whatever newer calibre releases will be
> available might go
Radu-Cristian FOTESCU a écrit :
André,
No matter what my e-mail address is, I am not in Canada, but in Romania.
Ok. So you're close (in time zone) to most contributors :)
Anyway, I'll think of packaging once I fix some other issues. Right now I'm
investigating a very
peculiar crash in KCh
>Maybe KCharSelect wasn't updated for KDE 4 ?
It was, and very much so. Before having a kcharselect binary in kdeutils, it
had prepared especially for that purpose a kcharselect widget as part of kdeui,
in kdelibs. Amazing contournement...
>Why not use gucharmap ? It seems complete, is deskto
Radu-Cristian FOTESCU a écrit :
Maybe KCharSelect wasn't updated for KDE 4 ?
It was, and very much so. Before having a kcharselect binary in kdeutils, it
had prepared especially for that purpose a kcharselect widget as part of kdeui,
in kdelibs. Amazing contournement...
Why not use guchar
23 matches
Mail list logo
