Re: [Mageia-dev] broken dependencies are growing again...
On 12/04/22 01:22 +0200, Maarten Vanraes wrote: > Op zaterdag 21 april 2012 21:42:23 schreef Pascal Terjan: > > On Sat, Apr 21, 2012 at 20:15, Maarten Vanraes wrote: > [...] > > > ==> missing perl modules: > > > perl-Catalyst-Authentication-Credential-OpenID > > > perl-JavaScript > > > > Yes and we can't do more about them, we should probably just remove > > them from mirrors > [...] > > iinm identity uses perl-Catalyst-Authentication-Credential-OpenID (or planned > to at some point) > > besides, it points to perl-Catalyst-Engine-HTTP not being there. which seems > to me (a novice) a more important package (unless renames or stuff) catalyst::engine::http does not exist anymore upstream. i already reported a bug. until the bug is solved (either by providing back ::http or to do without it), there's nothing much i can do. perl-javascript doesn't compile anymore with latest javascript libs, once again a bug exists upstream. so, nothing much to do for those. jérôme
[Mageia-dev] microcode needed by default
Hi, when booting i alwas saw that systemd was complaning about not being able to start service microcode.service (Description: LSB: Update the Intel / AMD CPU microcode). I made a research with urpmq and found the package microcode, i installed it and now theres no complains in systemd regarding microcode.
[Mageia-dev] Beta3 test
Besides all the crazy things, I spared a little time and installed the Live CD on a memory stix and put it into my Dell Laptop D630 I boots pretty fast and it is fast to use. The wireless work great and the software is fast too. However I need to keep the touchpad active otherwise the system falls to sleep before completing the boot and it doesn't shut down. -- Best regards Thomas Spuhler
Re: [Mageia-dev] Freeze push: openjpeg 1.5.0
no :( 2012/4/22 David Walser : > Funda, do you know what upstream commit(s) fixes this? >
Re: [Mageia-dev] Freeze push: openjpeg 1.5.0
David Walser wrote: > Funda Wang wrote: >> Hello, >> >> Could somebody push openjpeg 1.5.0 into cauldron? It fixed >> CVE-2012-1499: The JPEG 2000 codec in OpenJPEG before 1.5 does not >> properly allocate memory during file parsing, which allows remote >> attackers to execute arbitrary code via a crafted file. >> >> Thanks. > > Funda, does a patch exist for this? Mageia 1 should be vulnerable to this. Funda, do you know what upstream commit(s) fixes this?
Re: [Mageia-dev] Freeze Push: mythtv + mythplugins
'Twas brillig, and nicolas vigier at 22/04/12 00:43 did gyre and gimble: > On Fri, 20 Apr 2012, Colin Guthrie wrote: > >> Hi, >> >> Please push mythtv and then, after it's built, mythplugins. >> >> Built both normal and tainted locally. >> >> Please see earlier discussions on this topic, but also feel free to veto >> still. I can always revert SVN. > > Since it is a leaf package, and nobody seems to be against it in earlier > discussions, I have submitted mythtv. However there was an error at the > end of package build : > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120421233447.boklm.valstar.6145/log/mythtv-0.25-20120418.1.mga2/build.0.20120421233448.log > Thanks. It was missing a dep for python bindings which caused this. I've added that and enabled a few features I realised were missing. Please resubmit when you can. 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] freeze push: mgaonline
On Sat, 21 Apr 2012, Thierry Vignaud wrote: > Hi > > Please let in mgaonline. Submitted. > > It invalidate urpmi cache on upgrade (mga#1588) > > We should either push it as an update to mga1 too or backport that fix > as an mga1 update. Yes.
Re: [Mageia-dev] Freeze push: screengrab
On Sat, 21 Apr 2012, Matteo wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > can someone push screengrab? Submitted.
Re: [Mageia-dev] Freeze Push: mythtv + mythplugins
On Fri, 20 Apr 2012, Colin Guthrie wrote: > Hi, > > Please push mythtv and then, after it's built, mythplugins. > > Built both normal and tainted locally. > > Please see earlier discussions on this topic, but also feel free to veto > still. I can always revert SVN. Since it is a leaf package, and nobody seems to be against it in earlier discussions, I have submitted mythtv. However there was an error at the end of package build : http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120421233447.boklm.valstar.6145/log/mythtv-0.25-20120418.1.mga2/build.0.20120421233448.log
Re: [Mageia-dev] Freeze push: python and python3
I guess yes. But I couldn't find relative notes in here: http://www.python.org/news/security/ 2012/4/22 David Walser : > Funda Wang wrote: >> Hello, >> >> Could somebody push python-2.7.3 and python3-3.2.3 into cauldron? They >> fixed CVE-2012-0876, oCERT-2011-003, CVE-2012-0845, CVE-2011-3389, >> and a lot of other minor bugs. > > Do these affect Mageia 1 as well? >
Re: [Mageia-dev] Freeze push: wesnoth
On Fri, 20 Apr 2012, Samuel Verschelde wrote: > Le jeudi 19 avril 2012 13:59:12, Samuel Verschelde a écrit : > > Please push wesnoth 1.10.2, a bugfix release. > > > > I tested it locally, no obvious regression. > > > > Best regards > > > > Samuel Verschelde > > ping Submitted by ennael.
Re: [Mageia-dev] Freeze push: nginx
On Sat, 21 Apr 2012, David Walser wrote: > Funda Wang wrote: > > hello, > > > > Could nginx 1.0.15 be pushed into cauldron? It fixed CVE-2012-2089 and > > CVE-2012-1180. > > > > Thanks. > > Ping? Submitted.
Re: [Mageia-dev] broken dependencies are growing again...
Op zaterdag 21 april 2012 21:42:23 schreef Pascal Terjan: > On Sat, Apr 21, 2012 at 20:15, Maarten Vanraes wrote: [...] > > ==> missing perl modules: > > perl-Catalyst-Authentication-Credential-OpenID > > perl-JavaScript > > Yes and we can't do more about them, we should probably just remove > them from mirrors [...] iinm identity uses perl-Catalyst-Authentication-Credential-OpenID (or planned to at some point) besides, it points to perl-Catalyst-Engine-HTTP not being there. which seems to me (a novice) a more important package (unless renames or stuff)
Re: [Mageia-dev] Freeze push - quota
On 21.04.2012 23:31, Barry Jackson wrote: > On 20/04/12 15:06, Thierry Vignaud wrote: >> On 20 April 2012 16:00, Barry Jackson wrote: >>> Please push 'quota' package. >>> >>> Fixes bug 3053 :) >> >> That is? >> Like for packages description, one should always include a one liner >> description >> of the actual issue. >> Thanks. >> > Fixes incorrect permissions on root only readable file. > We aren't in release freeze yet, so you can push it by yourself.
Re: [Mageia-dev] Freeze push - quota
On 20/04/12 15:06, Thierry Vignaud wrote: On 20 April 2012 16:00, Barry Jackson wrote: Please push 'quota' package. Fixes bug 3053 :) That is? Like for packages description, one should always include a one liner description of the actual issue. Thanks. Fixes incorrect permissions on root only readable file.
Re: [Mageia-dev] freeze push: linux ha cluster stack
nicolas vigier wrote: > Hello, > > In Mageia 1, some HA cluster tools have been imported from Mandriva. > Most of them have not been updated since they were imported, they are > maintained by nobody, are old versions, and I'm not sure they are working. In addition to the ones you mention, do you know anything about ipvsadm? I looked into updating it before the freeze, but it doesn't build, and looking at it I don't see how in the hell it's supposed to.
Re: [Mageia-dev] Freeze push: nginx
Funda Wang wrote: > hello, > > Could nginx 1.0.15 be pushed into cauldron? It fixed CVE-2012-2089 and > CVE-2012-1180. > > Thanks. Ping?
Re: [Mageia-dev] Freeze push: python and python3
Funda Wang wrote: > Hello, > > Could somebody push python-2.7.3 and python3-3.2.3 into cauldron? They > fixed CVE-2012-0876, oCERT-2011-003, CVE-2012-0845, CVE-2011-3389, > and a lot of other minor bugs. Do these affect Mageia 1 as well?
Re: [Mageia-dev] broken dependencies are growing again...
On Sat, Apr 21, 2012 at 20:43, John Balcaen wrote: > 2012/4/21 Maarten Vanraes : >> plz look at: http://check.mageia.org/cauldron/dependencies.html > [...] >> ==> likely need rebuild due to newer dependant libs: >> telepathy-qt4 > Nop. > Here the telepathy-farsight library needed to be remove manually by a > sysadmin since wally disabled the build of thoses with the last > telepathy-qt src.rpm It should get removed automatically after some time.
Re: [Mageia-dev] broken dependencies are growing again...
2012/4/21 Maarten Vanraes : > plz look at: http://check.mageia.org/cauldron/dependencies.html [...] > ==> likely need rebuild due to newer dependant libs: > telepathy-qt4 Nop. Here the telepathy-farsight library needed to be remove manually by a sysadmin since wally disabled the build of thoses with the last telepathy-qt src.rpm -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
[Mageia-dev] Freeze push request: uhd and gnuradio
Please push uhd and gnuradio. Note:- Make sure uhd is built and updated in repos before pushing gnuradio. Reason:- A final version of the 3.5.x API of gnuradio was released a week ago. I have been working with upstream to fix a bug causing a build fail in Mageia since then, and it is now fixed. uhd is an update to the current stable and is required by gnuradio. Since this technology is cutting edge, users need the latest version and to have this in Mageia 2 would be really good. Both packages pass all the extensive built-in tests, and I have tested as far as I can. These packages do not impact anything else. Thanks, Barry
Re: [Mageia-dev] broken dependencies are growing again...
On Sat, Apr 21, 2012 at 20:15, Maarten Vanraes wrote: > plz look at: http://check.mageia.org/cauldron/dependencies.html > > ==> wrong strict versioned requires? (or not enough rebuilt packages) > brasero Probably normal, I would guess that libbrasero-burn-gir3.4.0 changed name to libbrasero-burn-gir3.4.1 and the old package is still present. It will be cleaned up. > ==> needs dropping: > cluster > > ==> rebuild without the dropped openais? > ocfs2-tools > > ==> missing perl modules: > perl-Catalyst-Authentication-Credential-OpenID > perl-JavaScript Yes and we can't do more about them, we should probably just remove them from mirrors > ==> likely need rebuild due to newer dependant libs: > telepathy-qt4 farsight no longer exist, they will get cleaned there is now libtelepathy-qt4-farstream2 but they are not compatible
Re: [Mageia-dev] broken dependencies are growing again...
On 21.04.2012 22:15, Maarten Vanraes wrote: > plz look at: http://check.mageia.org/cauldron/dependencies.html > > ==> wrong strict versioned requires? (or not enough rebuilt packages) > brasero These are old pkgs with old major, new ones are available. Should be removed automatically from repos after a while (newer src.rpm is available). > > ==> needs dropping: > cluster > > ==> rebuild without the dropped openais? > ocfs2-tools > > ==> missing perl modules: > perl-Catalyst-Authentication-Credential-OpenID > perl-JavaScript > > ==> likely need rebuild due to newer dependant libs: > telepathy-qt4 Old and obsoleted pkg. Should be removed automatically after a while (no src.rpm available).
[Mageia-dev] broken dependencies are growing again...
plz look at: http://check.mageia.org/cauldron/dependencies.html ==> wrong strict versioned requires? (or not enough rebuilt packages) brasero ==> needs dropping: cluster ==> rebuild without the dropped openais? ocfs2-tools ==> missing perl modules: perl-Catalyst-Authentication-Credential-OpenID perl-JavaScript ==> likely need rebuild due to newer dependant libs: telepathy-qt4
Re: [Mageia-dev] freeze push: linux ha cluster stack
Op vrijdag 20 april 2012 20:38:55 schreef Anne Nicolas: > Le 20/04/2012 20:13, nicolas vigier a écrit : [...] > > - cluster (including cman, rmanager) : obsoleted upstream, pacemaker > > should be used instead : > > https://fedorahosted.org/cluster/wiki/HomePage cluster seems not to be deleted... see http://check.mageia.org/cauldron/dependencies.html [...] > > - openais : project seems dead (no website online anymore), and nothing > > require this (except cman from cluster package which we are dropping) ocfs2-tools seems to require openais-devel, and as such is now broken: see http://check.mageia.org/cauldron/dependencies.html
Re: [Mageia-dev] Freeze push: anjuta-extras
Le 21/04/2012 19:28, Dimitri a écrit : Please push the anjuta-extras package. We have Anjuta 3.4.0, while this package is still 3.3.90. Thanks! submitted -- http://mageia.org
Re: [Mageia-dev] [Mageia-discuss] A proposal of some kind to get point of views & comments
On 21/04/12 14:08, Oliver Burger wrote: I think for every idea, there is a right time, and since we are all busy with Mga2 right, now. This definitely is not the right time. I am quite sure, we will have a post mortal after Mga2 as we had after Mga1, so please discuss this then. and don't cross-post over several lists. Oliver Yep indeed I don't think this is the right time for PPA's or something like it, as I tried to make clear in my emails. However since Umeaboy had sent his email about them, I decided to reply about them. Those emails are in the mailing list archives, I can link back to them when the time is more right :). As for cross posting sorry about that, and most or all people on the dev mailing list are probably on the discuss mailing list as well anyway, which is something I'll keep in mind for next time when I want people from both mailing lists to read an email. Sebastian
Re: [Mageia-dev] Help: Please find me initscripts without LSB headers!
'Twas brillig, and Guillaume Rousse at 18/04/12 13:02 did gyre and gimble: > Le 18/04/2012 14:00, Colin Guthrie a écrit : >> I figured using the google doc would be generally easier than editing a >> wiki page, but if we prefer I can just migrate the extra data in the >> google doc over to the wiki? > Yes, please. I think it's still easier using the Google Doc, so I've gone through the wiki and made sure the data there was reflected in the Google doc. I then saved the doc as CSV and piped it through a quick awk command to generate the table layout which I just pasted into the Wiki. IMO we should just continue using the Google Doc and periodically update the wiki page with the same awk command. WDYT? -- 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] RPM groups change: Productivity ?
Le 21/04/12 18:44,Malo Deniélou nous adresse ces quelques mots : > Le 21/04/12 06:33,Remco Rijnders nous adresse ces quelques mots : >> Hi all, >> >> I've just submitted taskwarrior, a command line tool to organise, >> prioritise, and track tasks etc. >> >> From the Fedora spec which I adopted, they have it in the group >> "Applications/Productivity". We have no such group available on >> https://wiki.mageia.org/en/RPM_groups_policy . In the end I resorted to >> picking "Text tools", but it just didn't feel right to me. As I have >> similar tools I'm thinking of packaging, as well as we have other tools >> in the distro such as taskcoach in "Office", I think a "Productivity" >> category might be of use. What do you think? > > May be we can discuss that after Mageia 2 is out. There are other > categories that would deserve to be created/renamed/moved. > One example is to clear a bit what is in Development/Other (some > languages, like Ocaml can have there own category, there could also be a > category Development/IDE or Development/tools for language-independent tools > ). Another > clean-up might be in the Books section, where you have docs that seems > randomly distributed between the subcategories. > Another example are forensic tools, that are in File tools for now, but > it's not completely satisfying, as they do not necessarily work on files. > ... > Etc. > > Cheers, -- Malo
Re: [Mageia-dev] RPM groups change: Productivity ?
Le 21/04/12 06:33,Remco Rijnders nous adresse ces quelques mots : > Hi all, > > I've just submitted taskwarrior, a command line tool to organise, > prioritise, and track tasks etc. > > From the Fedora spec which I adopted, they have it in the group > "Applications/Productivity". We have no such group available on > https://wiki.mageia.org/en/RPM_groups_policy . In the end I resorted to > picking "Text tools", but it just didn't feel right to me. As I have > similar tools I'm thinking of packaging, as well as we have other tools > in the distro such as taskcoach in "Office", I think a "Productivity" > category might be of use. What do you think? May be we can discuss that after Mageia 2 is out. There are other categories that would deserve to be created/renamed/moved. One example is to clear a bit what is in Development/Other (some languages, like Ocaml can have there own category, there could also be a category Development/IDE or Development/tools for language). Another clean-up might be in the Books section, where you have docs that seems randomly distributed between the subcategories. Another example are forensic tools, that are in File tools for now, but it's not completely satisfying, as they do not necessarily work on files. ... Etc. Cheers, -- Malo
[Mageia-dev] Freeze push: anjuta-extras
Please push the anjuta-extras package. We have Anjuta 3.4.0, while this package is still 3.3.90. Thanks!
[Mageia-dev] Mounting nfs4 shares
I have been using lines such as this to mount nfs shares: 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs4 rsize=8192,wsize=8192,timeo=14,intr mount -a Mount is denied because the NTFS volume is already exclusively opened. The volume may be already mounted, or another software may use it which could be identified for example by the help of the 'fuser' command. mount.nfs4: an incorrect mount option was specified Do I need to change these mount lines in some way? Do I need some extra package? (I've already installed nfs-utils-client) Shorewall should be allowing anything from the LAN. What else could I have missed? Anne
Re: [Mageia-dev] RPM groups change: Productivity ?
On Sat, 21 Apr 2012, Maarten Vanraes wrote: > Op zaterdag 21 april 2012 07:33:23 schreef Remco Rijnders: > > Hi all, > > > > I've just submitted taskwarrior, a command line tool to organise, > > prioritise, and track tasks etc. > > > > From the Fedora spec which I adopted, they have it in the group > > "Applications/Productivity". We have no such group available on > > https://wiki.mageia.org/en/RPM_groups_policy . In the end I resorted to > > picking "Text tools", but it just didn't feel right to me. As I have > > similar tools I'm thinking of packaging, as well as we have other tools > > in the distro such as taskcoach in "Office", I think a "Productivity" > > category might be of use. What do you think? > > > > Remmy > > Since our license policy is fedora based, i see no problem with this group > policy change This has nothing to do with license policy.
Re: [Mageia-dev] RPM groups change: Productivity ?
Op zaterdag 21 april 2012 07:33:23 schreef Remco Rijnders: > Hi all, > > I've just submitted taskwarrior, a command line tool to organise, > prioritise, and track tasks etc. > > From the Fedora spec which I adopted, they have it in the group > "Applications/Productivity". We have no such group available on > https://wiki.mageia.org/en/RPM_groups_policy . In the end I resorted to > picking "Text tools", but it just didn't feel right to me. As I have > similar tools I'm thinking of packaging, as well as we have other tools > in the distro such as taskcoach in "Office", I think a "Productivity" > category might be of use. What do you think? > > Remmy Since our license policy is fedora based, i see no problem with this group policy change
[Mageia-dev] Migrating systemd units. Be careful and please test
Hello, I've been trying to review the LSB initscript headers and systemd unit migration. It's really great to see packagers helping out here and I'd like to thank everyone for their effort, but sadly there have been a couple of errors cropping up in the process. So to help people out I'm including some advice in this mail. I'll also include the same advice on the systemd wiki page once I get around to updating it (trying to consolidate the list of packages there with a Google docs spreadsheet I have which is more detailed and easier to work with than the wiki page - when done with that, this info will be on the wiki). Be careful when copying Fedora units Fedora use /run for .pid files. On Fedora /var/run is just a symlink to /run. We don't do that yet, but we will will likely do this for mga3 as it solves a few problems we've had to hackily work around. In the mean time, we should in most cases use /var/run as the PID file path. The only time when using /run for the PID file is when the ExecStart command itself has an argument for the pidfile name passed in. If these two match up then all is well. Also Fedora often has different syntax in /etc/sysconfig files. During the migration to systemd they have likely simplified a few of them too. Again, do not blindly assume the files are the same format. You have to double check what we do in our initscript with the files and take appropriate action. You may have to edit the initscript too if you simplfy the syntax and you may also want to add default values for some environment variables inside the unit itself. Be careful of naming differences to sysvinit script === If a native systemd unit has a different name to the sysvinit script (ignoring the .service suffix) make sure to include a masking symlink such that we know the two services are the same. e.g. in dhcp-forwarder, the sysvinit script name is dhcp-fwd, but the systemd service is dhcp-forwarder.service. It's essential that you include a symlink to dhcp-forwarder.service with the name dhcp-fwd.service in order for both the upgrade migration and general running of the system to work. Please test the result or do not migrate for now Some of the problems above are quite obvious when testing. Please make sure to test things fully. If you are in any doubt, it's probably best to NOT migrate to a native unit over a sysvinit script at this stage of the cycle as it could introduce new problems quite easily. An exception would be if the initscript does not have LSB headers. In this case I'm happy for either a native systemd unit to be added or for the sysvinit script to simply have LSB headers inserted. Cheers! 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] push java-1.7.0-openjdk
Le 21/04/2012 14:12, D.Morgan a écrit : On Sat, Apr 21, 2012 at 2:03 PM, Guillaume Rousse wrote: Le 21/04/2012 13:44, D.Morgan a écrit : Thanks for taking care of the tomcats too. tomcat5 just needs patched for the last two CVEs, and it'll be good to go. yes as told i will do :) tomcat5 is the first on my todo ;) Do we really need to have 3 different tomcat versions in the distribution (5, 6 and 7) given the relatively high maintainance cost ? I'd rather drop tomcat 5 than continue to have it on the list of blocker bugs before every release. this is planned for mga3 when we will have ported all packages needing tomcat5 to use a newer version. I'd rather first have the same interrogation for those packages before investing any manpower in porting them: do we really need all of them in the distribution ? For instance, struts12 is a deprecated version of struts, dating from 2005, whereas current major version is 2.3. tiles20 is a deprecated version of tiles, whose current version is 2.2.2. Etc... I would have nothing againt those gazillion packages being present in the distribution if their had no side-effect for the rest of the world not using them. However, they do, when they involves release-blockers bugs. And given you're almost the only guy working on the java stack, I'd personnaly prefer to have you working on real issues affecting end users (for instance #2516 and #2517) than fixing security issues for softwares very unlikely to be used at all... My point is that we could achieve better results with more focused objectives in this regard. -- BOFH excuse #103: operators on strike due to broken coffee machine
Re: [Mageia-dev] [Mageia-discuss] A proposal of some kind to get point of views & comments
I think for every idea, there is a right time, and since we are all busy with Mga2 right, now. This definitely is not the right time. I am quite sure, we will have a post mortal after Mga2 as we had after Mga1, so please discuss this then. and don't cross-post over several lists. Oliver
[Mageia-dev] Packages in Mageia liveCD
First I would congratulate everybody for the nice job done to build a quite perfect KDE Beta3 LiveCD... I only want to suggest to provide Gimp instead of hugin in the livecd : Hugin is a perfect software to built panoramic photographs but is not needed by every user ... and is limited in its use if you don't have the tainted version of libpano and libpanotools Even more it is useless to have it alone because you always need to use gimp to correct, cut, print, the panoramas you have made. Gimp would be more useful for everyone (but it's perhaps to heavy with its dependancies and localized help rpm to stand on the live CD...) If gimp may not be provided, hugin is nevertheless such a specific software that you may use its place to provide something else (freeing 10 MB by suppressing hugin and libpano and libpano-tools) Hope it will help to improve...
Re: [Mageia-dev] push java-1.7.0-openjdk
On Sat, Apr 21, 2012 at 2:03 PM, Guillaume Rousse wrote: > Le 21/04/2012 13:44, D.Morgan a écrit : > >>> Thanks for taking care of the tomcats too. tomcat5 just needs patched >>> for the >>> last two CVEs, and it'll be good to go. >>> >> >> yes as told i will do :) tomcat5 is the first on my todo ;) > > Do we really need to have 3 different tomcat versions in the distribution > (5, 6 and 7) given the relatively high maintainance cost ? I'd rather drop > tomcat 5 than continue to have it on the list of blocker bugs before every > release. this is planned for mga3 when we will have ported all packages needing tomcat5 to use a newer version.
Re: [Mageia-dev] push java-1.7.0-openjdk
Le 21/04/2012 13:44, D.Morgan a écrit : Thanks for taking care of the tomcats too. tomcat5 just needs patched for the last two CVEs, and it'll be good to go. yes as told i will do :) tomcat5 is the first on my todo ;) Do we really need to have 3 different tomcat versions in the distribution (5, 6 and 7) given the relatively high maintainance cost ? I'd rather drop tomcat 5 than continue to have it on the list of blocker bugs before every release. -- The only thing more accurate than incoming enemy fire is incoming friendly fire -- Murphy's Military Laws n°15
[Mageia-dev] Freeze push: squirrelsh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, can someone push squirrelsh? - From 1.2.5 to 1.2.6: - - it fixes the not respected ldflags at build time - - it removes forced abi at build time - - it's the current stable release Regards - -- Matteo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPkp5cAAoJED3LowjDDWbN0j0H/jlKWJxSARmmdFuyyMTMSO/l GL15GdfMcX9Yuz3YPecG7TB7udoOG+FWydGZAceQ4fjVw83eQb3ZAmZsI7exXUGU rVgTYpiiJ38oCoASN/DB9igqsL51QJT4YL4Emi/suOWyVhCT4uppKDlV16Z/3AmG U/UEYYSLQhYs+MDZjZc+Sc8tVinULc/S+lIUG17ARjRqDuib0ZHFHm/nZK9ROkbl T1WN42nVkusglnJ8G98w+/cJqAaLXuVpF83Ym43wjeB8h02N1+YD8EUqhBM8WbB0 HqMTgB5x2O8cIRMnzY5CnwAvCcn1IXNk1aw5dExw8HDob/rKPmEUuDkTxb560dc= =dK+D -END PGP SIGNATURE-
Re: [Mageia-dev] push java-1.7.0-openjdk
On Fri, Apr 20, 2012 at 8:49 PM, David Walser wrote: > D.Morgan writes: >> > The build failed: >> > > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120419125106.boklm.valstar.19528 >> > >> > What a strange error. >> > >> >> don't worry i already fixed this. > > Thanks. Nice job. > > Thanks for taking care of the tomcats too. tomcat5 just needs patched for the > last two CVEs, and it'll be good to go. > yes as told i will do :) tomcat5 is the first on my todo ;)
Re: [Mageia-dev] Freeze push: openttd-opengfx
Le 21/04/2012 09:58, Jani Välimaa a écrit : On 19.04.2012 20:34, Zézinho wrote: Em 19-04-2012 19:32, Jani Välimaa escreveu: Please push openttd-opengfx. It's nothing serious, just a graphics package for openttd game and new release mainly fixes some issues reported to upstream. http://ftp.snt.utwente.nl/pub/games/openttd/binaries/extra/opengfx/0.4.4/changelog.txt This fixes text display in french, very important bug ;-) Ping? submitted -- http://mageia.org
Re: [Mageia-dev] Freeze push: openttd-opengfx
On 19.04.2012 20:34, Zézinho wrote: > Em 19-04-2012 19:32, Jani Välimaa escreveu: >> Please push openttd-opengfx. >> >> It's nothing serious, just a graphics package for openttd game and new >> release mainly fixes some issues reported to upstream. >> >> http://ftp.snt.utwente.nl/pub/games/openttd/binaries/extra/opengfx/0.4.4/changelog.txt >> > > This fixes text display in french, very important bug ;-) Ping?
Re: [Mageia-dev] Urpmi locks and Beta 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20/04/12 20:04, Thierry Vignaud wrote: > On 20 April 2012 21:50, Anne Wilson wrote: >> It looks as though locks are not released after any urpmi >> activity. Is anyone else experiencing this? > > They are unless you kill it while installing I realised afterwards the urpmi is hanging - not sure why. I tried killing the locks, I tried a re-start, but whether with gui or command-line, it was never getting a connection to the mirror - last night, that is. At one point I left it trying for 90 minutes, without success. This morning it is working again. Either there is a problem in handling mirror unavailability or something else was blocking and eventually timed out. 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/ iEYEARECAAYFAk+SaXoACgkQj93fyh4cnBdpAQCeLYTHQqF3/mbf1E8PbTzsoFic F/AAn37OfxVThMYb5HsAdy3zdQF6OwkB =DA0O -END PGP SIGNATURE-
Re: [Mageia-dev] chromium browser packages
20.04.2012 17:06, Thierry Vignaud kirjutas: On 20 April 2012 16:02, D.Morgan wrote: I do notice chromium-browser packages were not updated since january 21. Is it possible to include a more up to date chromium browser release? According to http://www.chromium.org/developers/calendar, the current stable release is 18.0.1025.162 (and current beta version is 19.0.1084.30), mageia beta 3 includes 17.0.963.65 version. as done for mga1 i think we should now obsolete beta and unstable and only update stable wdyt ? stable should only obsolete beta& unstable whose versions are lower than stable one. Maybe we should obsolete all chromes on stable release? So long we are providing only unsecure versions and have users complaining about extensions that warn about old version. Seriously, if we can't keep it up-to-date we should not release it. Browsers are most used software nowdays and we are failing to update most popular ones :(. Maybe we should lower the count to maintain? Or maybe we should lower system deps and use included libraries to make updating of those packages easier? -- Sander
