Re: [Mageia-dev] Mageia 1 EOL.
On Sat, Dec 01, 2012 at 09:36:36PM -0500, David wrote in : As the person who does a lot of the packaging for security updates, I am willing to continue the work I do on it, especially since I haven't had time yet to move my and my family's workstations to Mageia 2, and probably won't until late December, but I don't have a way to distribute any new packages. The build system has closed for Mageia 1. SVN should still be open, so I suppose I could check things in there and anyone interested could build from it locally? I don't want to host my own repository somewhere. If there is user demand for it, and packagers willing to provide security updates for a few more months, I'm willing to host the packages built. All with the understanding that: 1) I don't have the time or the skills to set up a full flexed build system; 2) All packages are made available "as is" and may break the users system, destroy their homework, offend mothers in law, or kick their pets; 3) No promises on availability other than on a best effort base. Lemme know should there be interested takers :) Remmy pgpA0d2XSogIU.pgp Description: PGP signature
Re: [Mageia-dev] What is happening with WiFi on Mageia-3?
Le 02/12/2012 17:39, Maurice Batey a écrit : When can we have a Mageia with WiFi that works and is reliable, please? WiFi works in Mageia 3 with lots of hardware. Your bug is a driver problem, not a global Mageia configuration one. Try with an USB Wi-Fi dongle if you can
Re: [Mageia-dev] Mageia 1 EOL.
02.12.2012 21:14, Kamil Rytarowski kirjutas: > Hello! > > It's not the best idea to start with packaging Firefox and Thunderbird: > 1. Both packages are advanced and hard to maintain > 2. If someone really wants the newest release of FF or TB, then he will > simply download a > binary from the upstream webpage, unpack in $HOME and use... First Funda, now you.. please stop that top-posting, both of you :/ -- Sander
Re: [Mageia-dev] Packages for review
On 02/12/12 12:42, Barry Jackson wrote:
On 02/12/12 09:37, Joseph Wang wrote:
Can someone check the following package submissions
quantlib
python-pyp2rpm
leocad
leocad-data
Also, does anyone object if I add the following to task-games?
vassal
simutrans
leocad (once it gets run)
Joseph I notice that some e.g. quantlib (I didn't look at all) of your
specs are missing proper tabbed (or spaced) indentation.
example here http://paste.kde.org/618332/
quantlib:
There is a dot ending summary(s)
svn should be part of release not version and I don't think the
%if...%endif is going to work as you expect.
The %if is OK ignore my last comment ;)
Attached is a patch that shows a possible approach regarding the Release
tag.
Index: SPECS/quantlib.spec
===
--- SPECS/quantlib.spec (revision 325459)
+++ SPECS/quantlib.spec (working copy)
@@ -1,11 +1,11 @@
%define svn 0
-%define baseversion 1.2.1
+%define rel 1
%define major 0
%if %svn
-%define version %{baseversion}.svn%{svn}
+%define release %mkrel -c %{svn} %{rel}
%else
-%define version %{baseversion}
+%define release %mkrel %{rel}
%endif
# Define some specific macros
@@ -15,8 +15,8 @@
Summary: The free/open-source library for quantitative finance.
Name: quantlib
-Version: %{version}
-Release: %mkrel 1
+Version: 1.2.1
+Release: %{release}
License: BSD License
Group: System/Libraries
Vendor: QuantLib.org
@@ -29,6 +29,7 @@
URL: http://quantlib.org/
BuildRequires: boost-devel >= 1.34.1
BuildRequires: doxygen >= 1.3, graphviz
+BuildRequires: emacs
%define libname %mklibname %{name} 1
%define libname_devel %mklibname -d %{name}
@@ -77,7 +78,7 @@
pre-constructed test cases, and helps in validating the library.
%prep
-%setup -q -n QuantLib-%{baseversion}
+%setup -q -n QuantLib-%{version}
%apply_patches
%build
Re: [Mageia-dev] urpmi --download-all --no-clean does not work any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I opened a bug report for that: > https://bugs.mageia.org/show_bug.cgi?id=8272 Fixed tv, thanks Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7ra0ACgkQqEs9DA4DquBi4wCfSXlLzdUYOTVP4tONmrdQPnKh DSsAn3BrGQDqnpCbRTKQw/MidpN4+DoF =dxzD -END PGP SIGNATURE-
Re: [Mageia-dev] What is happening with WiFi on Mageia-3?
On Sun, 02 Dec 2012 17:14:17 +, Claire Robinson wrote: > Have you created a bug for this Maurice? Yes - see: https://bugs.mageia.org/show_bug.cgi?id=7844 Regards, -- /\/\aurice
Re: [Mageia-dev] Mageia 1 EOL.
Hello! It's not the best idea to start with packaging Firefox and Thunderbird: 1. Both packages are advanced and hard to maintain 2. If someone really wants the newest release of FF or TB, then he will simply download a binary from the upstream webpage, unpack in $HOME and use... On 02.12.2012 15:23, Stan Thomas wrote: I'd be interested in doing some backports to Mageia 1 to keep it going a little longer; Firefox and Thunderbird would be my main focus. I've always thought I should learn how to build packages for a Linux distro. Are there any documents you can point me at? Anyone want to mentor me for this?
Re: [Mageia-dev] Mageia 1 EOL.
Le 02/12/12 14:23,Stan Thomas nous adresse ces quelques mots : > I'd be interested in doing some backports to Mageia 1 to keep it going a > little longer; Firefox and Thunderbird would be my main focus. I've > always thought I should learn how to build packages for a Linux distro. > Are there any documents you can point me at? Anyone want to mentor me > for this? Not for this, but if you want to work on Mageia 3, or on QA for Mageia 2, please join! https://wiki.mageia.org/en/Becoming_a_Mageia_Packager https://wiki.mageia.org/en/QA_Team -- Malo
Re: [Mageia-dev] What is happening with WiFi on Mageia-3?
On 12/02/2012 12:14 PM, Claire Robinson wrote: Have you created a bug for this Maurice? There probably already is one. Or, he can just search the ML archives. This has been discussed to death, several times. I can't recall whether an authoritative decision was made, but IIRC most people were happy with including nonfree on the media and then having an install option allowing the user to activate the nonfree repo in the install and the finished system so that drakconnect can install the needed firmware when the connection is set up.
Re: [Mageia-dev] filesystem update
On 2 December 2012 01:23, Thomas Spuhler wrote: > Are we going to stay with filesystem-2.1.9? > Fedora is on version 3.2 version is quite arbitrary...
Re: [Mageia-dev] NOTE: dont upgrade / submit ppl to the bs/mirrors...
David Walser skrev 2.12.2012 19:30: Thomas Backlund wrote: Thomas Backlund skrev 1.12.2012 18:09: Hi, as shown with the recent pcre case, we need to be more verbose on the -dev ml about packages that are WIP and/or known to break bs... I'm in the process of updating ppl from 0.11.2 to 1.0 (and cloog-ppl to whatever matching version is) Now, if this package hits the buildsystem & mirrors before it's properly tested it _will_ break atleast gcc, so all builds will come to a full stop in cauldron. So whatever you do... _dont_ touch theese packages until I have tested and submitted them. You can forget about this update ... I forgot to check what gcc actually supports :/ Thanks for looking into this. gcc-4.7 requires ppl-0.11 branch and cloog-ppl-0.15 branch Are you sure about cloog-ppl? Current mdv/ROSA has cloog-ppl 0.16.1 with gcc 4.7.3-development. Actually ROSA 2012 LTS has gcc 4.6.1 with cloog-ppl 0.16.1. I guess they package CLooG 0.16 as cloog-ppl. But I dont think I want to switch to that as it's still considered being in testing stage... From GCC-4.7 prerequisites.html: CLooG-PPL version 0.15 or CLooG 0.16: Necessary to build GCC with the Graphite loop optimizations. There are two versions available. CLooG-PPL 0.15 as well as CLooG 0.16. The former is the default right now. It can be downloaded from ftp://gcc.gnu.org/pub/gcc/infrastructure/ as cloog-ppl-0.15.tar.gz. CLooG 0.16 support is still in testing stage, but will be the default in future GCC releases. It is also available at ftp://gcc.gnu.org/pub/gcc/infrastructure/ as cloog-0.16.1.tar.gz. -- Thomas
Re: [Mageia-dev] NOTE: dont upgrade / submit ppl to the bs/mirrors...
Thomas Backlund wrote: > Thomas Backlund skrev 1.12.2012 18:09: >> Hi, >> >> as shown with the recent pcre case, we need to be more verbose on >> the -dev ml about packages that are WIP and/or known to break bs... >> >> I'm in the process of updating ppl from 0.11.2 to 1.0 >> (and cloog-ppl to whatever matching version is) >> >> Now, if this package hits the buildsystem & mirrors before it's >> properly tested it _will_ break atleast gcc, so all builds will >> come to a full stop in cauldron. >> >> So whatever you do... _dont_ touch theese packages until I have >> tested and submitted them. > > > You can forget about this update ... > > I forgot to check what gcc actually supports :/ Thanks for looking into this. > gcc-4.7 requires ppl-0.11 branch and cloog-ppl-0.15 branch Are you sure about cloog-ppl? Current mdv/ROSA has cloog-ppl 0.16.1 with gcc 4.7.3-development. Actually ROSA 2012 LTS has gcc 4.6.1 with cloog-ppl 0.16.1.
Re: [Mageia-dev] What is happening with WiFi on Mageia-3?
On 02/12/12 16:39, Maurice Batey wrote: > I'm using Mageia-2 on my netbook for normal work, at the same checking out > Mageia-3-Alpha2 (fully updated). WiFi adaptor is Broadcom BCM43225. > > On Mageia-2 the Wifi worked fine - at first - but after the recent s/w update > it started all over again 'Looking for software', after which it suffered the > 'Cannot found network' dead end. No WiFi. > > However, looking around Google-land I saw a suggestion to install > "kernel-firmware-nonfree", which I did, and this has brought WiFi back to > life. > > So I then tried the same install on Mageia-3-Alpha2, but sadly it still (and > always has) failed "Connection failed" (though it sees the SSID). > > I also tried Ubuntu 12.01 and Mint 13 KDE, on both of which WiFi worked 'out > of > the can'. > > When can we have a Mageia with WiFi that works and is reliable, please? > > Have you created a bug for this Maurice? Claire
[Mageia-dev] What is happening with WiFi on Mageia-3?
I'm using Mageia-2 on my netbook for normal work, at the same checking out Mageia-3-Alpha2 (fully updated). WiFi adaptor is Broadcom BCM43225. On Mageia-2 the Wifi worked fine - at first - but after the recent s/w update it started all over again 'Looking for software', after which it suffered the 'Cannot found network' dead end. No WiFi. However, looking around Google-land I saw a suggestion to install "kernel-firmware-nonfree", which I did, and this has brought WiFi back to life. So I then tried the same install on Mageia-3-Alpha2, but sadly it still (and always has) failed "Connection failed" (though it sees the SSID). I also tried Ubuntu 12.01 and Mint 13 KDE, on both of which WiFi worked 'out of the can'. When can we have a Mageia with WiFi that works and is reliable, please? -- /\/\aurice
Re: [Mageia-dev] NOTE: dont upgrade / submit ppl to the bs/mirrors...
Thomas Backlund skrev 1.12.2012 18:09: Hi, as shown with the recent pcre case, we need to be more verbose on the -dev ml about packages that are WIP and/or known to break bs... I'm in the process of updating ppl from 0.11.2 to 1.0 (and cloog-ppl to whatever matching version is) Now, if this package hits the buildsystem & mirrors before it's properly tested it _will_ break atleast gcc, so all builds will come to a full stop in cauldron. So whatever you do... _dont_ touch theese packages until I have tested and submitted them. You can forget about this update ... I forgot to check what gcc actually supports :/ gcc-4.7 requires ppl-0.11 branch and cloog-ppl-0.15 branch I've reverted ppl in svn to the state before I started the upgrade and updated the warning at top of the spec. I've also added warning in cloog-ppl spec about the needed version match for gcc. -- Thomas
Re: [Mageia-dev] Asia-Pacific packager newbie needs mentor
Le 02/12/2012 11:23, Marja van Waes a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/10/12 01:42, Funda Wang wrote: 2012/10/24 Anne Nicolas: Here somebody you may be able to help to become a Mageia packager. Can you see with him if it's possible ? Sure, I'm happy with that. Please update the mentoring page. Thanks. The mentoring page was never updated. However, there was another mail in this thread, where someone else offered to mentor Joseph. Maybe no one felt *fully* accepted as Joseph's mentor, and that contributed to the communication problems?? Not a all. there was a mail of Funda answering on it and accepting to mentor him. Cheers, Marja -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQuyw5AAoJEKWubDMI5nEBL+IIAI5C9/mQrSPTP1E/APcQ3pCj TBZbNpu+rfLhyQiSR2FFyOXp8Bm26nAFgHbrzHXmWIxS2pOJUsxnXYe+ECDmQtD7 US3tNwlVJpEF605dwTavQBZL2niZJtl0aYv1wXsnt4vWemlvvxhY+yi5B6ktyDXk m8CtPagispifamweml0PZ4w/7T1aXMjjYY9qvsunZOY5ZegZai+np1Cfn06cvzWe rhMlg1IsIvmw67EHGq6RsF10z1aUk3l1atupmhJQcehUXHlOr0DjSe1igL5VQUcw 8wnJSmrM/zemvZPNtITI6Hq1FF8sHAFBhs6iBFe+Dozz5Ic6GgTl3q9vCT/yse4= =ZJI0 -END PGP SIGNATURE- -- Anne http://mageia.org
Re: [Mageia-dev] Mageia 1 EOL.
I'd be interested in doing some backports to Mageia 1 to keep it going a little longer; Firefox and Thunderbird would be my main focus. I've always thought I should learn how to build packages for a Linux distro. Are there any documents you can point me at? Anyone want to mentor me for this?
Re: [Mageia-dev] sankore versioning (and naming) problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/12/2012 14:59, Kamil Rytarowski ha scritto: > svn mv over package name, spec name, Name tag, misc directory > > Add Provides: oldpackage-name and Obsoletes: oldpackage-name > > No need to add/bump Epoch. > But I'm not sure that changing the name to open sankore is right, since the haven't changed the tarball name... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7YMIACgkQqEs9DA4DquCoIwCdEQfdgdo3KDCQsVmRKLCbUFWt tUoAn2LJOsP6k026BMlyz8fclT6MdUDR =oWNP -END PGP SIGNATURE-
Re: [Mageia-dev] sankore versioning (and naming) problem
svn mv over package name, spec name, Name tag, misc directory Add Provides: oldpackage-name and Obsoletes: oldpackage-name No need to add/bump Epoch. On 02.12.2012 14:21, Angelo Naselli wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sankore [1] has recently changed the name in Open-Sankore. Moreover i have a historical mistake i made e.g. the version is not 3.1 but "3.1" is part of its name, while real version is inside of its project (2.0 beta 10 at the moment). Now i'd like to fix it up, but i need some suggestions in how to work. Should i change the project to open-sankore and obsoleting the old one? (is that enough?) Or should i leave it as it is by now and add en epoch to remove 3.1? Any other suggestion? TIA, Angelo [1] https://github.com/Sankore/Sankore-3.1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7VdYACgkQqEs9DA4DquA/DgCcC15lIdsinUPHRyeDT+RYJzPU 49gAnAwVMHejJO9FynAdPOxCkuceL1TT =UcIt -END PGP SIGNATURE-
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 01/12/12 02:30,Pierre-Malo Deniélou nous adresse ces quelques mots : > Le 29/11/12 11:04,Malo nous adresse ces quelques mots : >> On 27/11/12 23:02, Pierre-Malo Deniélou wrote: >>> Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: > Total = 1338 >>> >>> Today, 1273 remains to be changed. Thanks! >>> >>> Keep up the good work! >> >> This morning, 1182 are left. > > Tonight, only 1103 remain, thanks notably to Olav. > > Let's pass under 1000 by tomorrow night! Thanks to the effort of many, the number of remaining packages is now of 972. Many remain in Video. Please keep fixing! Thanks! -- Malo
[Mageia-dev] sankore versioning (and naming) problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sankore [1] has recently changed the name in Open-Sankore. Moreover i have a historical mistake i made e.g. the version is not 3.1 but "3.1" is part of its name, while real version is inside of its project (2.0 beta 10 at the moment). Now i'd like to fix it up, but i need some suggestions in how to work. Should i change the project to open-sankore and obsoleting the old one? (is that enough?) Or should i leave it as it is by now and add en epoch to remove 3.1? Any other suggestion? TIA, Angelo [1] https://github.com/Sankore/Sankore-3.1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7VdYACgkQqEs9DA4DquA/DgCcC15lIdsinUPHRyeDT+RYJzPU 49gAnAwVMHejJO9FynAdPOxCkuceL1TT =UcIt -END PGP SIGNATURE-
Re: [Mageia-dev] Packages for review
On 02/12/12 09:37, Joseph Wang wrote: Can someone check the following package submissions quantlib python-pyp2rpm leocad leocad-data Also, does anyone object if I add the following to task-games? vassal simutrans leocad (once it gets run) Joseph I notice that some e.g. quantlib (I didn't look at all) of your specs are missing proper tabbed (or spaced) indentation. example here http://paste.kde.org/618332/ quantlib: There is a dot ending summary(s) svn should be part of release not version and I don't think the %if...%endif is going to work as you expect.
Re: [Mageia-dev] Mageia 1 EOL.
On Sun, 02 Dec 2012 10:32:41 + Robert Wood wrote: > FWIW, I agree wholeheartedly with having a longer support time. Getting > Mageia 1 right on my laptop was a long and painful process; I feel I've > only just got it going (OK, it's a year down the line really) and I have > to go through it all again in a few weeks. I accept it might be much > easier because the kernel improves at light speed, but it would much > rather not have to do it for a while! > > I run Mageia 2 on my desktop and the one and [from my perspective] the > only thing that is better about it is GIMP 2.8. I miss nothing > whatsoever other than that. Even if it was two years rather than > eighteen months it would be great. As a different data point, I still use Mageia 1 (mainly because I'm happy with Gnome 2 and don't want to switch to hell), but I'm ok with Mageia 1 being EOL'ed. I think the developers would better spend their time concentrating on making a polished, high-quality Mageia 3 (and then I can install it and switch to XFCE :-)). Regards Antoine.
Re: [Mageia-dev] Will the 'official' Mageia-3 installer have a 'GRUB Legacy' option?
On Sat, 01 Dec 2012 21:43:28 +0200, Thomas Backlund wrote: > I guess he means that if we switch to Grub2 by default, will we still > support greb legacy ? Correct! I.e. when installing 'GRUB2' Mageia-3, will there be an option to use GRUB-Legacy instead? The reason I ask is that: (1) On my desktop I use the excellent GAG bootloader in the MBR, and it cannot boot GRUB2 installs. See e.g.: http://sourceforge.net/projects/gag/forums/forum/230439/topic/3533186 http://en.wikipedia.org/wiki/GAG_%28boot_loader%29 (2) On my netbook, I chainload via a GRUB-legacy Mageia MBR, where the Mageia menu.lst picks up all the other installs. (This includes the GRUB2 Ubuntu and Mint, whose GRUB2 menu's purport to boot the GRUB-legacy installs but fail to do so, hence though I know how to chainload from a GRUB-legacy menu.lst into a GRUB2 boot install, I do not know how to boot into a GRUB-legacy install from a GRUB2 menu. If you see what I mean... Those are just some of the reasons why I would like to avoid - or postpone - conversion to GRUB2, the need for which I still fail to comprehend. -- /\/\aurice
Re: [Mageia-dev] Mageia 1 EOL.
Op zondag 2 december 2012 12:28:39 schreef Sander Lepik: > 02.12.2012 08:46, blind Pete kirjutas: > > One and a half release cycles? > > > > Perhaps future realeases could have; > > 9 month release cycle, > > 12 month "full" support, > > 15 months "partial" support? > > Our releases already have 18 months "full" support. And as David already > said, we lack enough QA people. QA can't support 2 releases + test 3rd one > at the same time. If we want Mageia 3 to be good and tested distro then we > have to give QA more time to play with it. perhaps > > 9 month release cycle, > > 12 month "full" support, > > 15 months "partial" support? is a good idea, if there's an LTS version. on the one end, i like overlap, so i'd like to propose this: release cycle: 9months supported release: releasetime(release + 1) + 3 months only security support: support-time + 3 months this means whatever our releasetime becomes (if it's delayed into 10 or even 11 months we can stick with this. the same structure could be done with LTS (if we ever have it): LTS release cycle: (3 normal releases) LTS support: ( LTS-release - 1) + 6 months (in practice: this will mean 3y LTS support, due to delays) ==> this would mean all our users would need to go to the next version and not skip one. ==> this means we can lessen the burden on QA upgrade support would be from (release - 1) to release LTS upgrade support would be from (LTSrelease - 1) to LTSrelease no other upgrade path supported. Can we agree on this? (even if we don't have LTS now, nor even have to decide on it yet) steps if we have more QA resources: 1) having LTS 2) increasing 1 normal release 3) increasing release cycle of LTS so as to have a longer supported LTS the big point here, is that overlap is very useful, and until we have enough resources, having only overlap on top of 1 release, is good for now.
Re: [Mageia-dev] Mageia 1 EOL.
FWIW, I agree wholeheartedly with having a longer support time. Getting Mageia 1 right on my laptop was a long and painful process; I feel I've only just got it going (OK, it's a year down the line really) and I have to go through it all again in a few weeks. I accept it might be much easier because the kernel improves at light speed, but it would much rather not have to do it for a while! I run Mageia 2 on my desktop and the one and [from my perspective] the only thing that is better about it is GIMP 2.8. I miss nothing whatsoever other than that. Even if it was two years rather than eighteen months it would be great. Just my tuppence worth. I am very, very grateful for the fantastic work everyone does on this distribution whatever happens. :~) On 02/12/12 06:46, blind Pete wrote: David Walser wrote: Pierre Jarillon wrote: Le dimanche 2 décembre 2012 01:11:44, Thomas Backlund a écrit : Mageia 1 is now EOL. BS is locked down and updates_testing wiped. Blog post pushed and mail sent to updates-announce ML. I have several systems installed with Mageia 1 and I wish to move them to Mageia 3 (I make always a new install). During 4 or 5 month, I agree to have no improvements or no bug corrections but security updates are useful. I dont' want to replace Mga1 with Mga2 and 4 month later play again for Mga2 to Mga3. I have also other machines with Mga2 and with Mandriva 2010.2. I dont need a LTS but a Short Term Support is a bad thing and I don't want to waste my time. Is it possible to have security updates until a month after Mga3 is out? My feeling on this is that we have an 18 month support cycle *because* we have a 9 month development cycle, so we support for the length of two release cycles, so that if one release causes major problems, or you don't have time to upgrade every single time, you can skip one release and still stay supported. This works fine unless a release gets delayed like Mageia 2 did (which is fine) and probably most will a little bit at least. I believe the support should continue to run until release+2 is out. Sounds like a good reason for having a support period of either one and a half or two and a half release cycles. Aiming for exactly an integer means that there will be a day where updating has to happen. Worse when there is a delay the overlap could be negative. The problem is there isn't a company with paid employees providing the support, it's a community distro with all volunteers, so we can only continue to provide support if there are people willing and able to do the work. One and a half release cycles? Perhaps future realeases could have; 9 month release cycle, 12 month "full" support, 15 months "partial" support? As you may know, I do a lot of the packaging work on security updates. I also depend on some other packagers to do some of that work, but as time passes, less and less of them have either the time or willingness to continue to work on Mageia 1, so it gets more difficult to continue to support everything as time passes. Also, even if we can get updates packaged, we need QA people to test them, and we continue to need more help with QA, as it's a very small number of people doing the vast majority of the work. QA is responsible for not only testing updates for stable distros, but also testing every single ISO (including alphas, betas, and RCs) we release. So, to make a long story short, extending support for Mageia 1 was discussed by the council, but unfortunately rejected, mostly IINM because of the burden on QA. Again, that's not to blame anyone, but QA is a lot of work that's done by few people. So if they're not willing or able to continue to support it, unless new people step up to fill that void, we just don't have the ability to continue to provide support. As the person who does a lot of the packaging for security updates, I am willing to continue the work I do on it, especially since I haven't had time yet to move my and my family's workstations to Mageia 2, and probably won't until late December, but I don't have a way to distribute any new packages. The build system has closed for Mageia 1. SVN should still be open, so I suppose I could check things in there and anyone interested could build from it locally? I don't want to host my own repository somewhere.
[Mageia-dev] urpmi --download-all --no-clean does not work any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, last night i realized i cannot use -or at least i believe- urpmi "cached" any more. I'm trying to update and fix livecd-tools but the above problem breaks some livecd-creator functionality... I opened a bug report for that: https://bugs.mageia.org/show_bug.cgi?id=8272 In which is clear that urpm::init_cache_dir has been removed from urpm.pl: Undefined subroutine &urpm::init_cache_dir called at /usr/lib/perl5/vendor_perl/5.16.2/urpm/main_loop.pm line 101, line 2. help and manual are showing --download-all --no-clean, so i'd expect they work. Any help here? Thanks in advance. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7NrsACgkQqEs9DA4DquCKqQCfUzaU6Nuhsh6pLBw91nfExk8I nmsAn0ubX+IpCs/z8jn8MV5J9d15I5Zk =LuKh -END PGP SIGNATURE-
[Mageia-dev] Proposal to drop avant-window-navigator
Hi! Awant-window-navigator (awn) [1] and awn-extras-applets are near dead. Both packages are unbuildable due to old vala dependencies (it needs 0.14 generation, since we are already using 0.18). Maintaining it currently means becoming a developer. Fedora has already removed it from repositories [2] Is there anyone who want to fix upstream revision? If not, I will obsolete it. [1] https://launchpad.net/awn [2] http://pkgs.fedoraproject.org/cgit/avant-window-navigator.git/tree/dead.package
Re: [Mageia-dev] Mageia 1 EOL.
Le 02/12/2012 01:11, Thomas Backlund a écrit : > Mageia 1 is now EOL. > > BS is locked down and updates_testing wiped. > > Blog post pushed and mail sent to updates-announce ML. > > -- > Thomas Oh thanks so I will close (before this evening) the mga1 bugs as said previously. https://wiki.mageia.org/en/Maintenance_of_bug_reports#End_of_life_.28EOL.29_Release And bye Mageia 1, thanks for these 23 months on my laptop.
[Mageia-dev] Please help to fix build ecl and gcl
Hi! We have got problems with building ecl and gcl (both Lisp machines). There are packages that depends on it (like Maxima), and this has to be fixed before the mass rebuild. It is a BR blocker for other packages. I cannot do it now myself. Regards,
Re: [Mageia-dev] Mageia 1 EOL.
02.12.2012 08:46, blind Pete kirjutas: > One and a half release cycles? > > Perhaps future realeases could have; > 9 month release cycle, > 12 month "full" support, > 15 months "partial" support? Our releases already have 18 months "full" support. And as David already said, we lack enough QA people. QA can't support 2 releases + test 3rd one at the same time. If we want Mageia 3 to be good and tested distro then we have to give QA more time to play with it. -- Sander
Re: [Mageia-dev] Asia-Pacific packager newbie needs mentor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/10/12 01:42, Funda Wang wrote: > 2012/10/24 Anne Nicolas : >> >> Here somebody you may be able to help to become a Mageia >> packager. Can you see with him if it's possible ? > Sure, I'm happy with that. > > Please update the mentoring page. Thanks. The mentoring page was never updated. However, there was another mail in this thread, where someone else offered to mentor Joseph. Maybe no one felt *fully* accepted as Joseph's mentor, and that contributed to the communication problems?? Cheers, Marja -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQuyw5AAoJEKWubDMI5nEBL+IIAI5C9/mQrSPTP1E/APcQ3pCj TBZbNpu+rfLhyQiSR2FFyOXp8Bm26nAFgHbrzHXmWIxS2pOJUsxnXYe+ECDmQtD7 US3tNwlVJpEF605dwTavQBZL2niZJtl0aYv1wXsnt4vWemlvvxhY+yi5B6ktyDXk m8CtPagispifamweml0PZ4w/7T1aXMjjYY9qvsunZOY5ZegZai+np1Cfn06cvzWe rhMlg1IsIvmw67EHGq6RsF10z1aUk3l1atupmhJQcehUXHlOr0DjSe1igL5VQUcw 8wnJSmrM/zemvZPNtITI6Hq1FF8sHAFBhs6iBFe+Dozz5Ic6GgTl3q9vCT/yse4= =ZJI0 -END PGP SIGNATURE-
Re: [Mageia-dev] Improving communications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/12 07:10, Joseph Wang wrote: > I have a few suggestions for improving packaging communications > > * https://wiki.mageia.org/en/Pending_packages > > where I'll keep updated the status of my packaging, and I'll try > to forward notices from the mailing list. Having something on the > wiki makes things a bit more organized. I've changed the links a > bit so to tell people to look on that page first for important > notices. > > * Mageia-mentors mailing list or backup mentors > > It would be good if there was a mageia-mentors mailing list in > which private e-mail to and from the mentors could be cc'ed to so > that all of the mentors would have an overview of what > conversations would happen and there would be a "backup" in case a > mentor goes offline. Alternatively, people could get in a the habit > of having a backup mentor cc'ed that can respond if something comes > up. > > It would also be good to change the instruction page with > something instructions like "if you don't hear back from X in three > days, then do Y" > > What happened with me was that I had been packaging a large number > of packages and coordinating things offline with my mentor. I > mentioned that I was packaging cinnamon and then when I was done > (and it was just a minor project), I mentioned that I was done. I > didn't hear back, but that's happened before, and that's not a > problem. The problem was that when I looked on the dev list for > something unrelated, I found out that the cinnamon packages had > been bounced. That wasn't a problem since they had been bounced for > very good technical reasons, which I've been fixing. > Unfortunately, I was reading the e-mail out of context so it looked > to me like some tiny cabal had bounced all my packages for no > reason at all, and so I went ballistic. The most annoying problem > is that no one mentioned it me that there was a technical issue > with cinnamon. > > Part of the issue is since I'm new, I don't know the people, and so > I can't tell based on limited information if people are being > reasonable or not. Automatically assuming that people are being > reasonable won't work, because you'll find a lot of groups on the > internet in which people aren't reasonable (i.e. there is a reason > why people are dumping Gnome3 for Cinnamon) and people don't have > the time and energy to find out what's going on, and there is a lot > of "pseudo-reasonableness" out there. Working with a lot of > volunteer groups has made me a little paranoid when someone seems > nice. > > For people with a CS bent, a lot of issues that you run into with > coordinating people are the same that you run into in coordinating > CPU/GPU's and doing parallel computing. You can map some of the > issues that I've run into into the "two generals problem". http://en.wikipedia.org/wiki/Two_Generals%27_Problem (It was new to me ;) ) Thanks, Joseph, for your effort to improve things :) As documenter, I'm glad with the wiki page. Also as documenter, I'm wondering whether a mailing list would cause missing or not completely clear or up-to-date packaging pages in our wiki to be made or improved faster. Even if that wouldn't be the case: having packaging questions and answers in the mailing list archive, seems a good thing to me. As a very incidental packaging trainee, I think if there isn't a mailing list and my mentor is, e.g., on holiday without internet connection, it would be best to go to #mageia-mentoring and ask for assistance there. Cheers, marja -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQuyCTAAoJEKWubDMI5nEBDr0H+QH6jZHT0JVLC08Wverskbqd QyZ4dEmoR4FKx8r274cSclcn6ZZfsz8fPRItu/VsqsFz6XmUUCr3vk3XetTO4Wn1 PV2jnNlOpOGmv4S/GV6DMgh82QVFM1a2/e6YbQBd+B26AZspvejd//R7D+oAgRgD my/3GMPr9StslOjPpP8Gts0oWKaPJ4lE5wYPKbpLzGBEC+dfACZIgOV67xtY3bk4 IVtLyWC0P8jJ9cr70ISfLM8eMCJ5aRqHaACgvxELbmQw2OzOM6o53o8OOzA+Dx96 P9CUocVqjblohq5N88cUUWE7AQQ7Ea8/b6A2LkTvbvaA96I8/4ut5AaOZic3/1I= =dEgX -END PGP SIGNATURE-
Re: [Mageia-dev] python-tagpy build fail under cauldron
Le dimanche 2 décembre 2012 17:30:33 Joseph Wang a écrit : > I just checked in a fix for this (325101). I don't have the > permission to kick off a build, so someone > else needs to do that. > > Also, if there are any python related issues let me know. I've been > working a lot on my local > machine on python packages so it is easy for me to work on them right now. you should see this with your mentor, this is him that is supposed to upload for you.
[Mageia-dev] python-tagpy build fail under cauldron
I just checked in a fix for this (325101). I don't have the permission to kick off a build, so someone else needs to do that. Also, if there are any python related issues let me know. I've been working a lot on my local machine on python packages so it is easy for me to work on them right now.
