Hello,
After reading this:
http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7
We will support mageia 2 for 18 months (May 2012 to Nov 2013). But
upstream will end ruby 1.8.7 at the time of June 2013. That means, we
won't have any support from upstream even for security issues from
June
Le 31/10/2011 07:12, Funda Wang a écrit :
Hello,
After reading this:
http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7
We will support mageia 2 for 18 months (May 2012 to Nov 2013). But
upstream will end ruby 1.8.7 at the time of June 2013. That means, we
won't have any support
Le samedi 29 octobre 2011 à 18:38 +0100, Philippe Reynes a écrit :
Hi all,
Another solution is to package e17 twice (like chromium):
- an E17 -stable based stable tarball, as it was almost/already done
- an E17-unstable based on svn, as it's done now
I am a little bit stupid, but can you
Le lundi 31 octobre 2011 à 14:12 +0800, Funda Wang a écrit :
Hello,
After reading this:
http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7
We will support mageia 2 for 18 months (May 2012 to Nov 2013). But
upstream will end ruby 1.8.7 at the time of June 2013. That means, we
Hi all,
If you talk about this page :
http://www.mageia.org/wiki/doku.php?id=updates_policys[]=updates[]=policy
I think that I'm the stupid guy. I don't really understand where is the issue
with
this page and e17.
I understand that e17 don't provide stable release with tarball. But I never
On Mon, Oct 31, 2011 at 06:12, Funda Wang fundaw...@gmail.com wrote:
Hello,
After reading this:
http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7
We will support mageia 2 for 18 months (May 2012 to Nov 2013). But
upstream will end ruby 1.8.7 at the time of June 2013. That means,
Am 31.10.2011 13:40, schrieb Philippe Reynes:
Hi all,
If you talk about this page :
http://www.mageia.org/wiki/doku.php?id=updates_policys[]=updates[]=policy
http://www.mageia.org/wiki/doku.php?id=updates_policys[]=updates[]=policy
I think that I'm the stupid guy. I don't really understand
Le dimanche 30 octobre 2011 à 14:19 +0200, Thomas Backlund a écrit :
Colin Guthrie skrev 30.10.2011 13:26:
'Twas brillig, and Thomas Backlund at 29/10/11 21:13 did gyre and gimble:
So?
it's less impact on / than stuffing all of /usr on /
I don't understand what point you're trying to
Le lundi 31 octobre 2011 à 12:40 +, Philippe Reynes a écrit :
Hi all,
If you talk about this page :
http://www.mageia.org/wiki/doku.php?id=updates_policys[]=updates[]=policy
I think that I'm the stupid guy. I don't really understand where is
the issue with
this page and e17.
Ok
Ok so there is a bug to fix in e17, what do you do ?
I report it to upstream team (on irc or on the ML)
Or a security issue like the one I found ( and that should be fixed I
hope soon, after reporting it 3 times upstream ).
Same way, report it upstream.
If upstream don't fix a bug (or
Michael Scherer skrev 31.10.2011 18:07:
Le dimanche 30 octobre 2011 à 14:19 +0200, Thomas Backlund a écrit :
I'm saying moving the stuff that is _really_ needed, not based on udev
might run...
well, thinking some more on it I guess the real design flaw (not systemd
specific) is using all of
Le lundi 31 octobre 2011 à 19:06 +0200, Thomas Backlund a écrit :
Michael Scherer skrev 31.10.2011 18:07:
Le dimanche 30 octobre 2011 à 14:19 +0200, Thomas Backlund a écrit :
I'm saying moving the stuff that is _really_ needed, not based on udev
might run...
well, thinking some more
'Twas brillig, and Thomas Backlund at 31/10/11 17:06 did gyre and gimble:
Michael Scherer skrev 31.10.2011 18:07:
Le dimanche 30 octobre 2011 à 14:19 +0200, Thomas Backlund a écrit :
I'm saying moving the stuff that is _really_ needed, not based on udev
might run...
well, thinking some more
[Sorry for multiple replies, missed this bit in the last one :s]
'Twas brillig, and Thomas Backlund at 31/10/11 17:06 did gyre and gimble:
But I guess that's the development trend nowdays: I cant be bothered to
fix things properly so I just call it depreceated... and go ahead
and break things
Colin Guthrie skrev 31.10.2011 19:54:
[Sorry for multiple replies, missed this bit in the last one :s]
'Twas brillig, and Thomas Backlund at 31/10/11 17:06 did gyre and gimble:
But I guess that's the development trend nowdays: I cant be bothered to
fix things properly so I just call it
Op maandag 31 oktober 2011 13:16:55 schreef Manuel Hiebel:
[...]
##Package with more than 3 bugs:
2392, 3200, 3198;chromium-browser
2249, 2740, 3199, 2449, 1633;desktop-common-data
1867, 2650, 2644, 2653, 2627;evolution
1857, 1721, 2937;f-spot
942, 1483, 2628;gdm
416, 2888, 1759, 2121;grub
'Twas brillig, and Thomas Backlund at 31/10/11 19:01 did gyre and gimble:
Colin Guthrie skrev 31.10.2011 19:47:
Just have initramfs mount / and /usr, no need to merge.
Yes, this is exactly what is intended, but it depends on the use case:
Then I have misread something somewhere along the
Op maandag 31 oktober 2011 21:19:13 schreef Samuel Verschelde:
Le lundi 31 octobre 2011 20:37:14, Maarten Vanraes a écrit :
Op maandag 31 oktober 2011 13:16:55 schreef Manuel Hiebel:
[...]
##Package with more than 3 bugs:
2392, 3200, 3198;chromium-browser
2249, 2740, 3199, 2449,
On Mon, Oct 31, 2011 at 9:23 PM, Maarten Vanraes maar...@rmail.be wrote:
Op maandag 31 oktober 2011 21:19:13 schreef Samuel Verschelde:
Le lundi 31 octobre 2011 20:37:14, Maarten Vanraes a écrit :
Op maandag 31 oktober 2011 13:16:55 schreef Manuel Hiebel:
[...]
##Package with more than
Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan:
[...]
But seriously, if we can't maintain/fix something like chromium-browser,
we should just drop it completely, maybe have a get-chromium package
instead
why ? i package it regularly and tvignaud too.
what about dropping all
'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble:
Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan:
[...]
But seriously, if we can't maintain/fix something like chromium-browser,
we should just drop it completely, maybe have a get-chromium package
instead
why ? i
On Mon, Oct 31, 2011 at 10:06 PM, Colin Guthrie mag...@colin.guthr.ie wrote:
'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble:
Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan:
[...]
But seriously, if we can't maintain/fix something like chromium-browser,
we should
Op maandag 31 oktober 2011 22:06:25 schreef Colin Guthrie:
[...]
For example things like initscripts, udev, systemd etc. should be
maintained by a core team, and IMO, not a single person (tho' if
someone steps up and is proven to be reliable then this is obviously not
a bad thing per-se!). I'm
On 31/10/11 21:12, Maarten Vanraes wrote:
Op maandag 31 oktober 2011 22:06:25 schreef Colin Guthrie:
[...]
For example things like initscripts, udev, systemd etc. should be
maintained by a core team, and IMO, not a single person (tho' if
someone steps up and is proven to be reliable then this
Le lundi 31 octobre 2011 à 16:56 +, Philippe Reynes a écrit :
So, yes, there isn't any way to manage bug/security issue in a very
easy way when upstream team don't provide stable tarball. So, what is
the mageia policy in this case ? no packaging at all ? private
packaging ?
So far,
Le lundi 31 octobre 2011 à 21:06 +, Colin Guthrie a écrit :
'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble:
Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan:
[...]
But seriously, if we can't maintain/fix something like chromium-browser,
we should just
Le lundi 31 octobre 2011 à 21:06 +, Colin Guthrie a écrit :
I think the attempts to get more official partnerships by Samuel and
yourself are very valuable, but by the same token, I think we need to
accept that having a single maintainer for some packages just doens't
make sense.
For
'Twas brillig, and Michael Scherer at 31/10/11 21:44 did gyre and gimble:
Le lundi 31 octobre 2011 à 21:06 +, Colin Guthrie a écrit :
'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble:
Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan:
[...]
But seriously, if we
Le lundi 31 octobre 2011 à 22:16 +, Colin Guthrie a écrit :
'Twas brillig, and Michael Scherer at 31/10/11 21:44 did gyre and gimble:
Le lundi 31 octobre 2011 à 21:06 +, Colin Guthrie a écrit :
'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble:
Op maandag 31
On Mon, 31 Oct 2011, Colin Guthrie wrote:
I certainly don't expect a package maintained by a team to be marked as
nobody (well, certainly not longer term). But again, I think even
allocating a gatekeeper or a team leader puts too many social pressures
on that person, and imposes something of
On Mon, 31 Oct 2011 13:17:15 -0400, Michael Scherer m...@zarb.org wrote:
What is the usable feature ?
To be able to put some kind of quota on /usr ?
To be able to use a different fs for / and /usr ?
I once ran into the situation where installing a package
succeeded, but caused the /
31 matches
Mail list logo
