Re: [Mageia-dev] [changelog] [RPM] cauldron core/release libxslt-1.1.27-1.mga3
Le 19/09/2012 09:28, oden a écrit : oden oden 1.1.27-1.mga3: + Revision: 296149 - 1.1.27 - dropped all security patches, applied upstream - added autogen.sh as it was missing Which is generally useless nowadays, as 'autoreconf -fi' fills the same purpose.
[Mageia-dev] Mageia 3 final set of isos
Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. Let say we take one week on this so until 26/09 then we will make a final proposal Cheers -- Anne http://mageia.org
Re: [Mageia-dev] Mageia 3 final set of isos
On Wed, 19 Sep 2012 09:40:27 +0200 Anne Nicolas enna...@gmail.com wrote: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) IMHO you could simply go for CD == live (and installable). Regards Antoine. -- Software development and contracting: http://pro.pitrou.net
Re: [Mageia-dev] Mageia 3 final set of isos
On Wed, Sep 19, 2012 at 9:40 AM, Anne Nicolas enna...@gmail.com wrote: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. I would vote for - Live DVDs (1 per arch) - dual arch free CD - dual arch nonfree CD maybe we can replace the dual-arch CDs by enlarged boot.iso, need to send more about it :) I know machines with CD and not DVD still exist but I believe than in 99% of the cases they are either a server or an old machine which will probably have a hard time running a recent KDE or GNOME
Re: [Mageia-dev] Mageia 3 final set of isos
On Wed, Sep 19, 2012 at 10:11 AM, Antoine Pitrou solip...@pitrou.net wrote: On Wed, 19 Sep 2012 09:40:27 +0200 Anne Nicolas enna...@gmail.com wrote: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. This allows for example magazines to distribute it - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) IMHO you could simply go for CD == live (and installable). But we have a huge amount of live CDs currently because you can't fit a full GNOME or KDE desktop with all locales on a single CD
Re: [Mageia-dev] Mageia 3 final set of isos
Anne Nicolas skrev 19.9.2012 10:40: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) I'd suggest for livecds: 2 liveCDs: - 1 GNOME 700M i586 - english only - for FOSDEM co - 1 KDE 700M i586 - english only - for FOSDEM co 4 liveDVDs: - 1 GNOME DVD i586 - all locales-* - 1 GNOME DVD x86_64 - all locales-* - 1 KDE DVD i586 - all locales-* - 1 KDE DVD x86_64 - all locales-* Question... do we need to provide XFCE (or LXDE) for those that does not like the GNOME/KDE bloat (and phone/pad gui) ? - decrease isos number. QA is just a hell on the set we had for Mageia 2 Doing 2 livecds 4 livecds would drop live isos from 16 - 6 - provide localization as large as possible liveDVDs would carry all langs... Install DVDs already carry most (all?) langs - provide isos including major drivers including proprietary one to make it easier to install and configure liveCDs/DVDs already does... for normal install DVDs I guess we need to add nonfree firmwares to the isos in separate media with an option to enable/use them in the install phase as some hw need it to actually work. (IIRC tv had something like this in progress) Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. Let say we take one week on this so until 26/09 then we will make a final proposal Cheers -- Thomas
Re: [Mageia-dev] Mageia 3 final set of isos
Am 19.09.2012 09:40, schrieb Anne Nicolas: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Here is my proposal: 2 DVDs (32 and 64 bit) 2 LiveCDs KDE (32/64 bit) 2 LiveCDs GNOME (32/64 bit) 2 USB KDE (32/64 bit) ~1GB large (same as LiveCDs but with all languages) 2 USB GNOME (32/64 bit) ~1GB large (same as LiveCDs but with all languages) 1 dual arch CD --- 11 ISOs instead of 19 (the current state) Explanation: Only 2 LiveCDs per DE: Just put the most used languages or maybe only English on it. LiveCDs are usefull to check if everything is supported and bugfree or as a rescue system. This can be done with english as well. If you install the LiveCD a language selection could be used to download the preferred language. 4 USB Images: Nearly the same as the LiveCDs but as an USB-Image. So we are more flexible with the size of the ISOs. I guess ~1GB is usefull, as you can put all languages on it but is still small enough for a quick download or for restricted bandwidth ... 2 DVDs as it it now If we try to focus on USB-Images, we may get rid of the 64bit LiveCD Images. Regards, Thorsten Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. Let say we take one week on this so until 26/09 then we will make a final proposal Cheers
Re: [Mageia-dev] Mageia 3 final set of isos
19.09.2012 10:40, Anne Nicolas kirjutas: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. Let say we take one week on this so until 26/09 then we will make a final proposal Cheers My proposal: dual and DVDs - as they are today. 32-bit LiveCD-s as they are today. Replace 64-bit LiveCDs with two LiveDVDs (KDE and GNOME versions) which contain all languages. I think 32-bit LiveCDs are still needed as they will be used by those users who don't have computer that can read DVDs and when the CD is in english it will be really hard for them localize their system after installing. -- Sander
[Mageia-dev] autogen.sh
Hello people. Someone was wondering why i added autogen.sh in libxslt. There is a reason for this after long time maintaining open source softwares. See it as a last known good way of using the autopoo stuff as done upstream. If autoreconf - fi should ever fail in libxslt use the provided autogen.sh file. These files tends to disappear or be moved to the upstream release managers private hard drive only, or something like that. It's simply wise to keep autogen.sh for ourselves for reference. If you don't need to use it, fine, but keep it. -- Regards // Oden Eriksson Security team manager - Mandriva CEO NUX AB
[Mageia-dev] Rakudo perl6
Hi guys, I've submitted a spec file for rakudo in #7385, can someone package it before Mageia 3 release? I think it's a important package, it just needs to be built on a Cauldron box, I don't have one for now. Thanks for your help!
Re: [Mageia-dev] Rakudo perl6
Sandro CAZZANIGA skrev 19.9.2012 12:45: Hi guys, I've submitted a spec file for rakudo in #7385, can someone package it before Mageia 3 release? I think it's a important package, it just needs Well, if it's important, I guess it should have a maintainer... to be built on a Cauldron box, I don't have one for now. So set up a VM in virtualbox or KVM or XEN or... Thanks for your help! -- Thomas
Re: [Mageia-dev] autogen.sh
Le 19/09/2012 10:55, Oden Eriksson a écrit : Hello people. Someone was wondering why i added autogen.sh in libxslt. There is a reason for this after long time maintaining open source softwares. See it as a last known good way of using the autopoo stuff as done upstream. Just because you never understood autoconf is not an excuse to use such kind of derogative comments. If autoreconf - fi should ever fail in libxslt use the provided autogen.sh file. These files tends to disappear or be moved to the upstream release managers private hard drive only, or something like that. It's simply wise to keep autogen.sh for ourselves for reference. If you don't need to use it, fine, but keep it. Those dedicated scripts disappear because they are now obsoletes in favor of a generic solution maintained upstream. You'd better find an actual case where using the standard tool fails, whereas using such kind of ad-hoc wrapper works, before bloating packages with useless hacks. BTW, libxslt builds perfectly without ever regenerating the build system... -- BOFH excuse #189: SCSI's too wide.
Re: [Mageia-dev] Weekly meetings
'Twas brillig, and Anne Nicolas at 18/09/12 20:04 did gyre and gimble: Hi there Due to personal constraints, I will not be able to organize meetings on wednesday anymore. So either somebody does it or we can move it to tuesday, same hour. Comments ? Tuesdays are generally better for me, so from a purely selfish perspective, I'd prefer the move to Tuesday :) Col -- Colin Guthrie colin(at)mageia.org 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] Mageia 3 final set of isos
'Twas brillig, and Antoine Pitrou at 19/09/12 09:11 did gyre and gimble: On Wed, 19 Sep 2012 09:40:27 +0200 Anne Nicolas enna...@gmail.com wrote: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. I would personally prefer this too. That said, having a separate repository on the media itself is almost the same as having two iso's with different package selections (where one is a subset of the other), so in terms of QA, it's about the same (less downloading but the same number of installs). Still probably a net positive tho'. - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) IMHO you could simply go for CD == live (and installable). Perhaps, but the live version(s) did not necessarily specify a CD... it could well have been a Live DVD. So I guess that's a question to answer, should the live media be CD sized? (and I don't want to suggest for a second that it would be worth providing both!) Col -- Colin Guthrie colin(at)mageia.org 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] autogen.sh
onsdagen den 19 september 2012 12.34.46 skrev Guillaume Rousse: Le 19/09/2012 10:55, Oden Eriksson a écrit : Hello people. Someone was wondering why i added autogen.sh in libxslt. There is a reason for this after long time maintaining open source softwares. See it as a last known good way of using the autopoo stuff as done upstream. Just because you never understood autoconf is not an excuse to use such kind of derogative comments. If autoreconf - fi should ever fail in libxslt use the provided autogen.sh file. These files tends to disappear or be moved to the upstream release managers private hard drive only, or something like that. It's simply wise to keep autogen.sh for ourselves for reference. If you don't need to use it, fine, but keep it. Those dedicated scripts disappear because they are now obsoletes in favor of a generic solution maintained upstream. You'd better find an actual case where using the standard tool fails, whereas using such kind of ad-hoc wrapper works, before bloating packages with useless hacks. BTW, libxslt builds perfectly without ever regenerating the build system... Funny... An ignorant, patronizing and belittling responce is what I get on my first ever mail here. I really don't have time with this childish crap. -- Regards // Oden Eriksson Security team manager - Mandriva CEO NUX AB
Re: [Mageia-dev] autogen.sh
'Twas brillig, and Oden Eriksson at 19/09/12 09:55 did gyre and gimble: Hello people. Someone was wondering why i added autogen.sh in libxslt. There is a reason for this after long time maintaining open source softwares. See it as a last known good way of using the autopoo stuff as done upstream. If autoreconf - fi should ever fail in libxslt use the provided autogen.sh file. These files tends to disappear or be moved to the upstream release managers private hard drive only, or something like that. It's simply wise to keep autogen.sh for ourselves for reference. If you don't need to use it, fine, but keep it. autogen.sh or bootstrap.sh and similar scripts are usually in upstream SCM repositories but simply are often marked as NODIST or similar such that they do not make it into tarballs (that's not always the case - it varies from project to project). They are typically just wrappers around various auto* stuff, but 9 times out of 10 if you change some of the .am or .in files in patches, you don't need to redo the full bootstrap process, it's often just a matter of calling autoreconf or similar. But this is also only needed if: 1. We apply patches that touch some of the .am/.in files. or 2. The system on which make dist was run is somehow very broken and doesn't play nice with our environment (quite rare) I don't see either being true in the libxslt case so I wonder why autogen.sh is needed to make it build? Col -- Colin Guthrie colin(at)mageia.org 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] Rakudo perl6
Le 19/09/2012 12:10, Thomas Backlund a écrit : Sandro CAZZANIGA skrev 19.9.2012 12:45: Hi guys, I've submitted a spec file for rakudo in #7385, can someone package it before Mageia 3 release? I think it's a important package, it just needs Well, if it's important, I guess it should have a maintainer... to be built on a Cauldron box, I don't have one for now. So set up a VM in virtualbox or KVM or XEN or... Thanks for your help! -- Thomas Can't mount a VM on this computer, no enought ressources...
Re: [Mageia-dev] Mageia 3 final set of isos
Le 19/09/12 10:17, Pascal Terjan a écrit : On Wed, Sep 19, 2012 at 9:40 AM, Anne Nicolas enna...@gmail.com wrote: Hi there So here is the discussion about what isos we should keep or have for final release. We had several (many!) proposals on that topics and we need to take some decisions. Here are some prerequisites I can see for what I can read in comments and review about Mageia on the web. - provide a full open source software version - provide CD iso(s) so that it can be quick to download (people having low band-width or paying depending how much they use it) - provide live version(s) - decrease isos number. QA is just a hell on the set we had for Mageia 2 - provide localization as large as possible - provide isos including major drivers including proprietary one to make it easier to install and configure Keep in mind that what you want is not necessarily what another one want. So let start proposals here and discussion. Please add all explanations to your proposal. I would vote for - Live DVDs (1 per arch) - dual arch free CD - dual arch nonfree CD that seems good :) maybe we can replace the dual-arch CDs by enlarged boot.iso, need to send more about it :) it may be as problematic as boot.iso for people with bad connections. I personally prefer a CD that brings correctly the base system than rely on my connection and finish with an installation without rpm (as it did once). Claire
Re: [Mageia-dev] Rakudo perl6
Le 19/09/2012 12:10, Thomas Backlund a écrit : Sandro CAZZANIGA skrev 19.9.2012 12:45: Hi guys, I've submitted a spec file for rakudo in #7385, can someone package it before Mageia 3 release? I think it's a important package, it just needs Well, if it's important, I guess it should have a maintainer... to be built on a Cauldron box, I don't have one for now. So set up a VM in virtualbox or KVM or XEN or... Thanks for your help! -- Thomas It's good thomas, thanks :)
Re: [Mageia-dev] Mageia 3 final set of isos
On Wednesday 19 September 2012 14:23, Claire Revillet wrote: boot.iso for people with bad connections. I always use boot.iso when installing, as I install over the network. Then I don't have to remember to remove the CD/DVDs as available repos. The only time I use DVDs for installation, is when I'm installing for other people, either here at my place or at their places. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
[Mageia-dev] Import msec into our SVN
Hello all, I as looking into the mageia svn and seen that we didn't import msec at the time of the fork. Is there any reason for that? If not, I think we have to import this excellent software in our SVN to give it love and attention. Does someone wants to work on it specifically? It's mostly written in Python. What do you think? Thanks :)
Re: [Mageia-dev] Mageia 3 final set of isos
On 09/19/2012 04:20 AM, Pascal Terjan wrote: On Wed, Sep 19, 2012 at 10:11 AM, Antoine Pitrou solip...@pitrou.net wrote: Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. This allows for example magazines to distribute it Then put the nonfree and tainted stuff on a separate non-installable CD/DVD containing only those packages, and have the installer provide an option to use either that or a network-location nonfree/tainted. The magazine can distribute the base DVD, and those who want nonfree/tainted can simply opt to download the second ISO themselves or have the installer connect them to a network nonfree/tainted repo.
Re: [Mageia-dev] Import msec into our SVN
On Wed, 19 Sep 2012, Sandro CAZZANIGA wrote: Hello all, I as looking into the mageia svn and seen that we didn't import msec at the time of the fork. Is there any reason for that? Because there is no need to import it when nobody plans to make significant changes on it. If somebody wants to work on it, they can import it at that time.
Re: [Mageia-dev] Import msec into our SVN
Le 19/09/2012 15:25, nicolas vigier a écrit : On Wed, 19 Sep 2012, Sandro CAZZANIGA wrote: Hello all, I as looking into the mageia svn and seen that we didn't import msec at the time of the fork. Is there any reason for that? Because there is no need to import it when nobody plans to make significant changes on it. If somebody wants to work on it, they can import it at that time. Ok, but it seems that nobody still maintain it, the last commit is from Nicolas L., ten months ago...
Re: [Mageia-dev] Import msec into our SVN
On Wednesday 19 September 2012 15:25, nicolas vigier wrote: Because there is no need to import it when nobody plans to make significant changes on it. Then how do you rebuild it if it's not in the svn repo? -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Import msec into our SVN
Le 19/09/2012 15:28, Nicolas Lécureuil a écrit : Le mercredi 19 septembre 2012 14:27:44 Johnny A. Solbu a écrit : On Wednesday 19 September 2012 15:25, nicolas vigier wrote: Because there is no need to import it when nobody plans to make significant changes on it. Then how do you rebuild it if it's not in the svn repo? using existing tarball ? Yep, like for all others softwares that mageia don't develop :)
Re: [Mageia-dev] Import msec into our SVN
On Wednesday 19 September 2012 15:28, Nicolas Lécureuil wrote: Then how do you rebuild it if it's not in the svn repo? using existing tarball ? My point exactly. From where does the tarball come if it's not in our svn repo? According to mgarepo it is in the svn repo, so I'm not sure how someone came to the conclusion that it's not imported into the svn. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Import msec into our SVN
Le 19/09/2012 15:33, Johnny A. Solbu a écrit : On Wednesday 19 September 2012 15:28, Nicolas Lécureuil wrote: Then how do you rebuild it if it's not in the svn repo? using existing tarball ? My point exactly. From where does the tarball come if it's not in our svn repo? According to mgarepo it is in the svn repo, so I'm not sure how someone came to the conclusion that it's not imported into the svn. You're confusing the package and the software: the msec package is in the repository, in the package branch, the msec source tree is not. -- BOFH excuse #208: Your mail is being routed through Germany ... and they're censoring us.
Re: [Mageia-dev] Import msec into our SVN
On Wednesday 19 September 2012 15:35, Guillaume Rousse wrote: You're confusing the package and the software: the msec package is in the repository, in the package branch, the msec source tree is not. And I think here you lost a few of us. :-)= What is the difference between these two? (I didn't know there was one) -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Import msec into our SVN
Le 19/09/2012 15:39, Johnny A. Solbu a écrit : On Wednesday 19 September 2012 15:35, Guillaume Rousse wrote: You're confusing the package and the software: the msec package is in the repository, in the package branch, the msec source tree is not. And I think here you lost a few of us. :-)= What is the difference between these two? (I didn't know there was one) svn.mageia.org/soft contains source of softwares developped by Mageia team.
Re: [Mageia-dev] Mageia 3 final set of isos
2012/9/19 Pascal Terjan pter...@gmail.com: On Wed, Sep 19, 2012 at 10:11 AM, Antoine Pitrou solip...@pitrou.net wrote: Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. This allows for example magazines to distribute it Are paper magazines still relevant here? (true question)
Re: [Mageia-dev] Mageia 3 final set of isos
Le 19/09/2012 15:04, Johnny A. Solbu a écrit : On Wednesday 19 September 2012 14:23, Claire Revillet wrote: boot.iso for people with bad connections. I always use boot.iso when installing, as I install over the network. Then I don't have to remember to remove the CD/DVDs as available repos. The only time I use DVDs for installation, is when I'm installing for other people, either here at my place or at their places. I don't understand the relation between my point and yours. My point is that with a bad connection (like mine and i'm not living in the worse country concerning internet acces) boot.iso is not safe so we should continue providing dual-cd. Dual-cd can make a complete base installation safely and is less to download compare to DVDs.
Re: [Mageia-dev] Mageia 3 final set of isos
2012/9/19 Romain d'Alverny rdalve...@gmail.com: 2012/9/19 Pascal Terjan pter...@gmail.com: On Wed, Sep 19, 2012 at 10:11 AM, Antoine Pitrou solip...@pitrou.net wrote: Is that necessary? Instead you could have a checkbox install optional proprietary software in the installer. This allows for example magazines to distribute it Are paper magazines still relevant here? (true question) Yes, they are an important distribution method. Additionally there will be reviews/articles accompanying the cover DVDs. Don't forget, this is cost free advertizing! My view: - Free DVD (32/64) with a proper installer - distributing only live media is a bad habit of some distributors, let's make a difference there! As we have support of the idea of free software written in our values we should stick to that. In addition to that we could include non-free firmware in a part of the DVD, to be activated in the installer (opt-in). - 4 life ISOs (Gnome KDE, 32 64) for USB sticks (up to 1GB), they work for all kinds of machines, even such without optical drives. The additional space would be enough to include all langs. - boot.iso, this is done anyway, so it's no extra work -- wobo -
Re: [Mageia-dev] Mageia 3 final set of isos
On Wed, 19 Sep 2012 10:17:55 +0200 Pascal Terjan pter...@gmail.com wrote: I would vote for - Live DVDs (1 per arch) - dual arch free CD - dual arch nonfree CD maybe we can replace the dual-arch CDs by enlarged boot.iso, need to send more about it :) I know machines with CD and not DVD still exist but I believe than in 99% of the cases they are either a server or an old machine which will probably have a hard time running a recent KDE or GNOME So, for the record, as a user the reason I prefer CD images is not that I don't have a DVD reader (I do have one) but simply that CD images are much smaller to download and keep around. Just my two overrated cents of course ;-) Regards Antoine. -- Software development and contracting: http://pro.pitrou.net
[Mageia-dev] Any progress on the NFS mount problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My laptop uses fstab lines to mount directories on the old server and also on a QNAS box. I've no idea what version of Linux is running on the QNAS, but the mounts are working there. The old server is running Mageia 2, and mount to that don't work. Working line example: 192.168.0.200:/DataFromBorg2 /mnt/QNAS-Borg2-Data nfs user,timeo=14 0 0 Non-working (M2) example: 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs user,rsize=8192,wsize=8192,nosuid,soft 0 0 Note that I initially wrote it the same way as the QNAS line, and reverted to this older style when I found that didn't work. mount -a gives mount.nfs: requested NFS version or transport protocol is not supported If I forget and click on the mount point in Dolphin I get An error occurred while accessing 'Data1 on 192.168.0.40', the system responded: mount.nfs: requested NFS version or transport protocol is not supported Is this https://bugs.mageia.org/show_bug.cgi?id=6541? And is there anything I can do to improve matters? Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBZ8TkACgkQj93fyh4cnBe/hQCfc2pxINIChlRFpBAy3ch6ZUvp h5MAoIOfoWgE0jt0MBS4RhvblLeShgm/ =UeIV -END PGP SIGNATURE-
Re: [Mageia-dev] Mageia 3 final set of isos
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/09/12 15:53, Wolfgang Bornath wrote: Are paper magazines still relevant here? (true question) Yes, they are an important distribution method. Additionally there will be reviews/articles accompanying the cover DVDs. Don't forget, this is cost free advertizing! Interestingly, one of the leading UK computer magazines has just stopped including cover media. The reviews are still there, as is the What's on this month's disk, but the disk is downloadable. It's too early to know whether this is the start of a trend, but my personal reaction is one less to send to the tip each month. We've seen the move away from disks in plastic folders replaced by cardboard sleeves. It does seem likely that this will be the next step. Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBaCAYACgkQj93fyh4cnBeZRwCfWWa/az3ySxPrCJI9B85PGGzr uY4AniuLpI5wbsuLe1G9cLIjkOcU9PUR =BEGx -END PGP SIGNATURE-
Re: [Mageia-dev] Any progress on the NFS mount problem?
Le 19/09/2012 19:46, Anne Wilson a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My laptop uses fstab lines to mount directories on the old server and also on a QNAS box. I've no idea what version of Linux is running on the QNAS, but the mounts are working there. The old server is running Mageia 2, and mount to that don't work. Working line example: 192.168.0.200:/DataFromBorg2 /mnt/QNAS-Borg2-Data nfs user,timeo=14 0 0 Non-working (M2) example: 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs user,rsize=8192,wsize=8192,nosuid,soft 0 0 First, your are clearly not mounting the same path (/DataFromBorg2 vs /Data1), so your comparaison is quite biased. Second, you'd rather use mount command, than hardcoded entries in /etc/fstab entries, to debug the issues. You'll get much more input. Third, you'd rather avoid useless options such as rsize and wsize, unless you know what you're doing. Note that I initially wrote it the same way as the QNAS line, and reverted to this older style when I found that didn't work. mount -a gives mount.nfs: requested NFS version or transport protocol is not supported If I forget and click on the mount point in Dolphin I get An error occurred while accessing 'Data1 on 192.168.0.40', the system responded: mount.nfs: requested NFS version or transport protocol is not supported Is this https://bugs.mageia.org/show_bug.cgi?id=6541? And is there anything I can do to improve matters? According to the error message, you have probably a version negotiation issue between your client and your server. Add -d option to rpc.mountd (RPCMOUNTDOPTS variable in /etc/sysconfig/nfs) on server side, and -v option to mount.nfs on client side to get more verbose error reporting. -- BOFH excuse #275: Bit rot
Re: [Mageia-dev] Mageia 3 final set of isos
Op woensdag 19 september 2012 11:31:13 schreef Thomas Backlund: I'd suggest for livecds: 2 liveCDs: - 1 GNOME 700M i586 - english only - for FOSDEM co - 1 KDE 700M i586 - english only - for FOSDEM co 4 liveDVDs: - 1 GNOME DVD i586 - all locales-* - 1 GNOME DVD x86_64 - all locales-* - 1 KDE DVD i586 - all locales-* - 1 KDE DVD x86_64 - all locales-* i like your proposal the best, but with small addendum: no QA: (but often tested, so this works out ok) (autogenerated?) 2 - boot (32/64) 2 - boot nonfree (32/64) install: 1 - dual arch CD nonfree 2 - DVD installer with nonfree option (32/64) live: 1 - liveDVD/USB dual arch KDE nonfree 1 - liveDVD/USB dual arch Gnome nonfree 2 - liveCD KDE english only (32) 2 - liveCD Gnome english only (32) total 9 iso's to be tested, of which 3 of them will need more testing due to dual arch; (and perhaps the nonfree option will need a bit of extra testing too in the DVD in the 2 DVD installer isos). i don't think it can be any shorter than this... Personally only 3 isos are important: - dual arch CD nonfree (it's only for advanced users, mostly used for servers, so need hardware raid firmware and network firmware; don't care about graphic drivers; and i also can use it as a rescue CD, that means i only need one CD in my coat inner pocket at all times) - 64bit DVD install (preferably nonfree) for desktop installs. - boot nonfree (64bit) for PXE installs and such after this,if people want more and there IS resources, people can make more iso's like with edu selection or whatnot... speaking of dual arch CD; i'm missing iproute2 bridge-utils (commands: ip (mostly for vlan support) and brctl) in the rescue
