On 31/01/2013 16:19, Maurice Batey wrote:
On Wed, 30 Jan 2013 17:22:43 +, James Kerr wrote:
Mageia 2's Grub boot-loader was installed to the MBR of the boot disk.
But earlier you said:
"On a recent install of Beta1, I chose Grub2 and selected to put
the b
On 30/01/2013 11:54, Maurice Batey wrote:
On Sun, 20 Jan 2013 14:39:26 +, James Kerr wrote:
Grub2 created a boot menu that enables me to
successfully boot the pre-existing Mageia2 installation.
James, does the Mageia2 installation have GRUB-Legacy in the PBR?
No. Mageia 2's
On 20/01/2013 13:30, Maurice Batey wrote:
On Sun, 20 Jan 2013 13:08:57 +, Barry Jackson wrote:
Installing the grub2 package will not impact your current bootloader in
any way.
Installing GRUB2 where, Barry?
(MBR or Root partition?)
If - as I did with Ubuntu 12.01 - GRUB2 goes into th
On 03/10/2012 12:58, tv wrote:
Name: drakx-installer-stage2 Relocations: (not relocatable)
Version : 14.46.2 Vendor: Mageia.Org
Release : 1.mga3Build Date: Wed Oct 3 13:54:37 2012
Install Date: (not installed)
On 02/10/2012 13:58, Wolfgang Bornath wrote:
2012/10/2 James Kerr :
On 02/10/2012 12:26, Frank Griffin wrote:
At least for my part, I always viewed tainted as being the equivalent of
PLF,
PLF had both free and non-free repo's.
If you include both free and non-free in tainted, whi
On 02/10/2012 12:26, Frank Griffin wrote:
At least for my part, I always viewed tainted as being the equivalent of
PLF,
PLF had both free and non-free repo's.
If you include both free and non-free in tainted, which is probably the
"least bad" solution, then there needs to be a way for FOSS e
On 28/09/2012 10:36, tmb wrote:
Name: draklive Relocations: (not relocatable)
Version : 2.1 Vendor: Mageia.Org
Release : 1.mga3Build Date: Fri Sep 28 11:36:11 2012
Install Date: (not installed)
On 27/07/2012 21:26, Olivier Blin wrote:
Thierry Vignaud writes:
On 25 June 2012 09:25, wrote:
Revision 5019 Author fwang Date 2012-06-25 09:25:45 +0200 (Mon, 25 Jun 2012)
Log Message
drop duplicated Mageia wording
This break translations.
Please fix translations w/o fuzzying them.
Else
On 24/05/2012 18:44, David wrote:
Is it safe to update Cauldron?
Yes it is safe to update cauldron.
I ask because the package
mageia-release-common-2-3.mga2.x86_64.rpm that urpmi wants to install
from the /Cauldron directory says that this is "Mageia release 2
(Official) for x86_64"
Or shoul
On 21/05/2012 09:35, Colin Guthrie wrote:
Hi,
Random question... I've only just noticed that mgaapplet/rpmdrake
started telling me that I had no media... is this just because we've
"flipped a switch" telling it to only update media marked as update
while 99% of the cauldron cycle it would updat
On 28/04/2012 11:21, Mika Laitio wrote:
Just tried to boot (and also install) the
Mageia-2-beta3-LiveCD-GNOME-Europe2-i586-CD.iso
on Zotac Atom 330 NVIDIA Ion system and it didn't really work out.
Install starts up just fine and it shows up the Mageia splash screen
with 2 balls on top of it.
Th
This thread has strayed far from the original question, which could be
re-stated as:
Should tainted free software and tainted nonfree software be commingled
in a single tainted repository?
Given Mageia's commitment to the promotion of free software, I believe
that they should not. If Mageia
On 07/07/11 06:07, Remco Rijnders wrote:
On Wed, Jul 06, 2011 at 07:47:49PM -0400, David W. Hodgins wrote:
On Wed, 06 Jul 2011 08:44:07 -0400, Michael scherer
wrote:
Since we took one month for various things ( such as discussing
everything ), we propose
the next release to be on 4th april, a
On 06/07/11 12:58, Romain d'Alverny wrote:
On Wed, Jul 6, 2011 at 12:10, Wolfgang Bornath wrote:
If we go back to the beginning of the discussion where to put such
packages which were in PLF we made a clear difference:
1. All non-free goes into non-free
2. Software which may be illegal in som
On 19/06/11 18:43, Mageia Team wrote:
Name: drakx-installer-binaries Relocations: (not relocatable)
Version : 1.50 Vendor: Mageia.Org
Release : 3.mga2Build Date: Sun Jun 19 19:40:17 2011
Install Date: (not installed)
On 13/06/11 13:06, Dick Gevers wrote:
On Mon, 13 Jun 2011 09:37:40 +0200, Cazzaniga Sandro wrote about Re:
[Mageia-dev] [RPM] cauldron core/release biew-6.1.0-1.mga2:
Quite a few packages reached the mirrors since this one, but biew has
not.
So it needs a rebuild?
Anything similar to rebui
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
On 10/06/11 22:44, andre999 wrote:
James Kerr a écrit :
On 10/06/11 15:09, James Kerr wrote:
On 10/06/11 13:54, Michael Scherer wrote:
Le vendredi 10 juin 2011 à 14:21 +0200, Oliver Burger a écrit :
Thomas Backlund schrieb am 10.06.2011
So the path would then be */updates_testing
On 10/06/11 15:27, Oliver Burger wrote:
James Kerr schrieb am 10.06.2011
Even though backports are disabled rpmdrake can display a list of
available backports. (The sources are automatically updated by
mgaonline.)
I make you parden, but: no!
When a repo is disabled it doesn't get up
On 10/06/11 15:09, James Kerr wrote:
On 10/06/11 13:54, Michael Scherer wrote:
Le vendredi 10 juin 2011 à 14:21 +0200, Oliver Burger a écrit :
Thomas Backlund schrieb am 10.06.2011
So the path would then be */updates_testing -> */updates _if_ we
decide that's the way to go...
As
On 10/06/11 13:54, Michael Scherer wrote:
Le vendredi 10 juin 2011 à 14:21 +0200, Oliver Burger a écrit :
Thomas Backlund schrieb am 10.06.2011
So the path would then be */updates_testing -> */updates _if_ we
decide that's the way to go...
As I see it, it's the only user friendly way. Using
On 08/06/11 08:42, Oliver Burger wrote:
Hi,
after some discussion in the German forums, I saw, that there are
discrepancies between /etc/version and /etc/release, both coming from
the mageia-release-common-1-2.mga1 package.
While /etc/release calls my system
--
Mageia release 1 (Officia
On 15/05/11 12:23, Mageia Team wrote:
Name: java-1.6.0-sun Relocations: (not relocatable)
Version : 1.6.0.25 Vendor: Mageia.Org
Release : 1.mga1Build Date: Sun May 15 13:19:30 2011
Install Date: (not installed)
On 09/05/11 10:28, Stefano Negro wrote:
Hi
I am trying to install my 3G usb pen modem.
It is recognized :
usb 5-3: new high speed USB device using ehci_hcd and address 5
usb 5-3: New USB device found, idVendor=19d2, idProduct=2000
usb 5-3: New USB device strings: Mfr=2, Product=1, SerialNumber=3
When marking a bug as a duplicate, bugzilla insists that a comment be
added. This seems redundant since bugzilla itself adds an explanatory
comment automatically.
Is it possible to make an exception in this case, to the requirement to
add a comment when changing the status of a bug?
Jim
On 04/04/11 10:49, Donald Stewart wrote:
On 4 April 2011 10:35, Anne nicolas wrote:
Hi there
While working on beta1 isos, looks like recent improvement in deps
management for base system made some more free space. I know have 30
Mo available to add more packages. Just keep in mind that dual co
On 01/03/11 18:52, Ahmad Samir wrote:
At the moment when a new bug report is filed bugzilla adds the string
"New:" to the subject line of the email, this is removed in subsequent
emails (once the bug is not new any more, i.e. more comments were
added... etc).
This is a sort of an unofficial poll
On 18/02/11 12:07, Michael Scherer wrote:
Le vendredi 18 février 2011 à 12:43 +0100, Oliver Burger a écrit :
Philippe DIDIER schrieb am 2011-02-18
And what I talked about (in the other thread with the same name)
was about the easiness to build and use different rpms with the
same spec having m
On 16/02/11 21:37, bugzilla-dae...@mageia.org wrote:
test
I assume that this was a test of the bugs list. It seems to have worked. :)
Jim
A couple of issues that I've not seen mentioned elsewhere:
1. There are multiple builds of some packages on the mirrors. For example:
drakconf-12.21-1
drakconf-12.21-2
drakconf-12.21-3
2. In /core/release/media_info there is an ever-increasing number of
symlinks to the meta-data files (hdlist
30 matches
Mail list logo
