Re: [Mageia-dev] Packager meetings for tonight
On Mon, Feb 7, 2011 at 12:08, Thierry Vignaud thierry.vign...@gmail.com wrote: On 3 February 2011 17:06, Michael Scherer m...@zarb.org wrote: So as discussed tonight ( but if you couldn't be present at the meeting, do not hesitate to express yourself now ), we proposed to have some order in the import of rpm ( ie avoid the resulting anarchy due to lack of process for bootstrap ). In order to start by something tangible and easy to manage, let's take a concrete case. The sysadmin team discussed to use mageia on the servers ( once the stable release is out ie, not now ) for obvious reasons of dogfooding. But for this, we will have to import the needed rpms. I extracted from puppet logs the lists of rpm, and I have a list of the major component needed. The rule would be to take 1 and only 1 rpm ( or family ) at the time, to make sure it work fine ( ie, compile for the moment, and also install ), to make sure the package is cleaned ( ie, patchs sent upstream, commented, etc ), and to make sure that everybody can find something to do. And that of course requires to do the same for missing BuildRequires, and Requires ( but since lots of rpm have been imported without being fully cleaned, and since there is now a fast web interface for svn, people have no excuse to not check ). I will place the list on the wiki tomorrow, and people wishing to work on importing a rpm should add their name/login/whatever after the rpm, and then to work on it. If there is already someone working on a rpm, just take another one, or try to work with this person. So it seems that my list of 20 rpms is now much lower than needed, as most servers applications needed have been imported. The only thing left are : What would really help us is the list of actually successfully build package rather than the list of submitted packages that we previously have on pkgsubmit.mga.org It has been replaced by the list of missing BR for currently submited packages (http://pkgsubmit.mageia.org/data/missing-deps.i586.txt) but having the list of succesfully rebuild packages would help too. OK, I removed the list of built one when removing the (empty) list of missing one to get rid of the ugly temporary code I can add it back until having something better... Or maybe add the generation of those lists to the script run every 15 minutes that lists missing deps.
Re: [Mageia-dev] Packager meetings for tonight
2011/2/3 philippe makowski makowski.mag...@gmail.com: 2011/2/3 Michael Scherer m...@zarb.org: The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial So any taker ? seeing the Mandriva spec, I take mercurial done but sorry, I was disturbed during the wok and I forgot to mention the new upstream (1.7.5) in the changelog :(
Re: [Mageia-dev] Packager meetings for tonight
Le vendredi 04 février 2011 à 10:11 +0100, philippe makowski a écrit : 2011/2/3 philippe makowski makowski.mag...@gmail.com: 2011/2/3 Michael Scherer m...@zarb.org: The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial So any taker ? seeing the Mandriva spec, I take mercurial done but sorry, I was disturbed during the wok and I forgot to mention the new upstream (1.7.5) in the changelog :( ie ? You can do a svn propedit svn:log if there is something to change -- Michael Scherer
Re: [Mageia-dev] Packager meetings for tonight
2011/2/4 Michael Scherer m...@zarb.org: ie ? You can do a svn propedit svn:log if there is something to change yes ;) I'll do I posted the email as a reminder, because I really have to switch to other tasks
Re: [Mageia-dev] Packager meetings for tonight
Le jeudi 03 février 2011 à 02:44 +0100, Michael Scherer a écrit : Le mercredi 02 février 2011 à 17:26 +0100, Michael Scherer a écrit : Hi, Next meeting will happen tonight on #mageia-dev at 20h UTC. Quick proposal for agenda ( the meeting must be quick ) : - review of the task distributed last week ( http://meetbot.mageia.org/mageia-dev/2011/mageia-dev.2011-01-26-20.03.html ) - proposal on what should be imported in priority ( and distribution of the work ) So as discussed tonight ( but if you couldn't be present at the meeting, do not hesitate to express yourself now ), we proposed to have some order in the import of rpm ( ie avoid the resulting anarchy due to lack of process for bootstrap ). In order to start by something tangible and easy to manage, let's take a concrete case. The sysadmin team discussed to use mageia on the servers ( once the stable release is out ie, not now ) for obvious reasons of dogfooding. But for this, we will have to import the needed rpms. I extracted from puppet logs the lists of rpm, and I have a list of the major component needed. The rule would be to take 1 and only 1 rpm ( or family ) at the time, to make sure it work fine ( ie, compile for the moment, and also install ), to make sure the package is cleaned ( ie, patchs sent upstream, commented, etc ), and to make sure that everybody can find something to do. And that of course requires to do the same for missing BuildRequires, and Requires ( but since lots of rpm have been imported without being fully cleaned, and since there is now a fast web interface for svn, people have no excuse to not check ). I will place the list on the wiki tomorrow, and people wishing to work on importing a rpm should add their name/login/whatever after the rpm, and then to work on it. If there is already someone working on a rpm, just take another one, or try to work with this person. So it seems that my list of 20 rpms is now much lower than needed, as most servers applications needed have been imported. The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial Mercurial should be simple, bugzilla will likely be done by dmorgan as soon as the list will be posted. Rails is likely to be handled by shikamaru ( as he is working on redmine ), so you should see with him to help Sympa is not hard to package either. And that let us with apache + various modules. So any taker ? -- Michael Scherer
Re: [Mageia-dev] Packager meetings for tonight
2011/2/3 Michael Scherer m...@zarb.org: The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial So any taker ? seeing the Mandriva spec, I take mercurial
Re: [Mageia-dev] Packager meetings for tonight
On 3 February 2011 18:06, Michael Scherer m...@zarb.org wrote: Le jeudi 03 février 2011 à 02:44 +0100, Michael Scherer a écrit : Le mercredi 02 février 2011 à 17:26 +0100, Michael Scherer a écrit : Hi, Next meeting will happen tonight on #mageia-dev at 20h UTC. Quick proposal for agenda ( the meeting must be quick ) : - review of the task distributed last week ( http://meetbot.mageia.org/mageia-dev/2011/mageia-dev.2011-01-26-20.03.html ) - proposal on what should be imported in priority ( and distribution of the work ) So as discussed tonight ( but if you couldn't be present at the meeting, do not hesitate to express yourself now ), we proposed to have some order in the import of rpm ( ie avoid the resulting anarchy due to lack of process for bootstrap ). In order to start by something tangible and easy to manage, let's take a concrete case. The sysadmin team discussed to use mageia on the servers ( once the stable release is out ie, not now ) for obvious reasons of dogfooding. But for this, we will have to import the needed rpms. I extracted from puppet logs the lists of rpm, and I have a list of the major component needed. The rule would be to take 1 and only 1 rpm ( or family ) at the time, to make sure it work fine ( ie, compile for the moment, and also install ), to make sure the package is cleaned ( ie, patchs sent upstream, commented, etc ), and to make sure that everybody can find something to do. And that of course requires to do the same for missing BuildRequires, and Requires ( but since lots of rpm have been imported without being fully cleaned, and since there is now a fast web interface for svn, people have no excuse to not check ). I will place the list on the wiki tomorrow, and people wishing to work on importing a rpm should add their name/login/whatever after the rpm, and then to work on it. If there is already someone working on a rpm, just take another one, or try to work with this person. So it seems that my list of 20 rpms is now much lower than needed, as most servers applications needed have been imported. The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial Taking icecream (pun included :)). -- Michael Scherer -- Ahmad Samir
Re: [Mageia-dev] Packager meetings for tonight
On 3 February 2011 18:06, Michael Scherer m...@zarb.org wrote: [..] The only thing left are : * apache ( and apache-mod_fastcgi, apache-mod_perl, apache-mod_php, apache-mod_ssl, apache-mod_wsgi * bugzilla * icecream * rails * sympa * mercurial apache-mod_fastcgi imported apache-mod_php already available apache-mod_ssl src.rpm is apache itself apache-mod_wsgi imported -- Ahmad Samir
Re: [Mageia-dev] Packager meetings for tonight
Le mercredi 02 février 2011 à 17:26 +0100, Michael Scherer a écrit : Hi, Next meeting will happen tonight on #mageia-dev at 20h UTC. Quick proposal for agenda ( the meeting must be quick ) : - review of the task distributed last week ( http://meetbot.mageia.org/mageia-dev/2011/mageia-dev.2011-01-26-20.03.html ) - proposal on what should be imported in priority ( and distribution of the work ) So as discussed tonight ( but if you couldn't be present at the meeting, do not hesitate to express yourself now ), we proposed to have some order in the import of rpm ( ie avoid the resulting anarchy due to lack of process for bootstrap ). In order to start by something tangible and easy to manage, let's take a concrete case. The sysadmin team discussed to use mageia on the servers ( once the stable release is out ie, not now ) for obvious reasons of dogfooding. But for this, we will have to import the needed rpms. I extracted from puppet logs the lists of rpm, and I have a list of the major component needed. The rule would be to take 1 and only 1 rpm ( or family ) at the time, to make sure it work fine ( ie, compile for the moment, and also install ), to make sure the package is cleaned ( ie, patchs sent upstream, commented, etc ), and to make sure that everybody can find something to do. And that of course requires to do the same for missing BuildRequires, and Requires ( but since lots of rpm have been imported without being fully cleaned, and since there is now a fast web interface for svn, people have no excuse to not check ). I will place the list on the wiki tomorrow, and people wishing to work on importing a rpm should add their name/login/whatever after the rpm, and then to work on it. If there is already someone working on a rpm, just take another one, or try to work with this person. Of course, nothing prevent people from working on something else if they wish, but this list of package are IMHO the one that we are sure to find testers ( aka sysadmins ). Moreover, as most if not all are servers, or at least, stuff without graphical interface, they will be ready to be tested once the mirror will be ready. Once this list wil be cleared, we will likely be ready on more consequent bunch of rpms ( like kde, gnome, xfce, etc, etc ). So if someone has remarks, or questions, do not hesitate. -- Michael Scherer
