Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
Op donderdag 5 juli 2012 20:34:08 schreef David Walser: AL13N wrote: this is a good point: BTW, a missing dependency should not be considered a blocking issue as it can be easily fixed by the end user. Especially for a security update, as he probably already done it. also, not sure, but it seems the tester was unawere of perl-CGI-Fast being not really required (i think). still, IRC meeting yesterday seemed to conclude that security or major bug updates cannot be majorly delayed by bugs, it is however ok, to ask packager to do a quick fix for something at the same time. still, for this issue, it seems also that there was a month delay due to not setting assigned back. or even setting NEEDINFO. Incorrect. There was a month delay because the packager who first submitted it to QA failed to provide an update for Mageia 2. That person also failed to make any comment whatsoever, while being aware that questions had been raised. Let me be clear, I know we're all busy, and I don't expect things to be fixed right away all the time. However, we need to communicate. Even if you don't have time to fix something, if you know there are issues, and you have some input to give on it, give it. I really don't appreciate being ignored for a month, and then when someone else tries to help, all of sudden you (not you Maarten) finally speak up and complain about what has been done. i do understand, however, as i said, even though QA might be ignored, i think QA still would have to validate it, when QA reads this and sees no response, imho :-( . also, i notice that noone seemed to have pointed out the tester that in fact that dependency isn't required. But it is used by the default configuration, so a suggests is appropriate. Our packages should be functional out of the box. iiuc, the qa team member says it's required, and not suggested, and noone from packaging team thought about mentioning that it should be a suggests. (of course, i didn't know this, but suspected it) i also see that some sentences look harsh to one of both sides here. (or at least to me). Yes, that is true. Both sides could tone it down, and it is really not appropriate to have that kind of argument in public on Bugzilla (IMO).
Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
Op donderdag 5 juli 2012 23:52:39 schreef Claire Robinson: On 05/07/12 23:34, nicolas vigier wrote: On Thu, 05 Jul 2012, Claire Robinson wrote: These recent attacks are causing even more work for us, which again helps nobody, and diverts our attention away from where it is really needed. Also I would point out that having to validate the same package several times obviously lessens the amount of time we can spend elsewhere, which compounds the problem. A disagreement is not an attack. With respect Nicolas, you're not on the receiving end. [...] allthough i see badly worded(possibly to look offensive) sentences, i don't think this is intentional, and more a problem of communication than something else. I often have the feeling that certain sentences from french people come accross as rude to me. I've come to understand that this is not the intention, but somehow related to how french sentences are built and how it's been translated to english.
Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
Am 06.07.2012 08:18, schrieb AL13N: Op donderdag 5 juli 2012 23:52:39 schreef Claire Robinson: With respect Nicolas, you're not on the receiving end. [...] allthough i see badly worded(possibly to look offensive) sentences, i don't think this is intentional, and more a problem of communication than something else. I often have the feeling that certain sentences from french people come accross as rude to me. I've come to understand that this is not the intention, but somehow related to how french sentences are built and how it's been translated to english. The same thing was pointed out to me by a native speaker (as MrsB is), when I wrote an answer that somehow was rather rude to the receiver. We have to keep in mind, that most of us are non native speakers and that all of us have slightly different cultures. So - although it may be hard - it would be good for the native speakers among us, not to put every word through a rudeness detector. I know the Brits are far more courteous then the Germans (and perhaps the French as well?), so let's go back to fixing bugs and not feeling hurt by people who might not even be rude from their point of view... Oliver -- Oliver Burger aka obgr_seneca Mageia contributor
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I think MCC2 should just be seen as an experiment until there is enough done that it actually looks like a usable tool. Even the planning is just a fuzzy idea, no concrete plans yet. I think this should be considered as valid. I'm in favor to have a branch that could be delivered as an alternative to mcc in mga3 if we reach the goal to have a stable and not complete moving. So not a replacement but a way to the future. In the mean while i'm looking for the alternative proposal as well that could be helpful in any case. About coding, Steven if you have in mind what you want as ui, we can ask for the svn branch and start sharing the task. I cannot say i have 24h a day free, more likely some a week (at night for the most) but what i want to say is you're not alone and the project is big. About libYui, i got in touch with the main developer, and told me there is a IRC channel #libyui and git project on github is very active at the moment, they are very happy to get feedback and patches from other distros, (they also moved to cmake) but the next milestone is after yast will be fully adapted to libyui. So we could consider to have git version of libyui to have all up to date and fixed. WDYT? Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/2m6sACgkQqEs9DA4DquDgXgCeKm+r5cb9DCp5m0L1zG/f4eQa FSQAoLmbxdrbOleww0gj9EHmzPFBYXJR =Cu/5 -END PGP SIGNATURE-
Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
On 06/07/12 07:56, Oliver Burger wrote: Am 06.07.2012 08:18, schrieb AL13N: Op donderdag 5 juli 2012 23:52:39 schreef Claire Robinson: With respect Nicolas, you're not on the receiving end. [...] allthough i see badly worded(possibly to look offensive) sentences, i don't think this is intentional, and more a problem of communication than something else. I often have the feeling that certain sentences from french people come accross as rude to me. I've come to understand that this is not the intention, but somehow related to how french sentences are built and how it's been translated to english. The same thing was pointed out to me by a native speaker (as MrsB is), when I wrote an answer that somehow was rather rude to the receiver. We have to keep in mind, that most of us are non native speakers and that all of us have slightly different cultures. So - although it may be hard - it would be good for the native speakers among us, not to put every word through a rudeness detector. I know the Brits are far more courteous then the Germans (and perhaps the French as well?), so let's go back to fixing bugs and not feeling hurt by people who might not even be rude from their point of view... Oliver This has nothing to do with being rude. As I said previously, this is being blown wildly out of proportion. In reality it centres around one packager and two bugs. In both these bugs the packager expected QA to validate updates where one was an xinetd service which expressly stated it was disabled by default but in actual fact was enabled and in the other a mailing list with a web interface which simply couldn't work in it's default configuration. What it being thrown at us is that we are unreasonably expecting every single little bug to be fixed without any common and need to make drastic changes to our policies. We attended the packager meeting on Wednesday to respond to this and discuss it. At the meeting it was agreed that we had not changed the way we have been doing things since day one and that the right way forward was to continue doing what we were doing, with both packagers and QA using common sense. The following day the same far fetched accusations are thrown at us again, now escalated to the ML, suggesting we caused a months delay and suggesting a solution to the accusation being we begin to 'rubber stamp' security updates regardless of if they actually work or not or an internet facing service which says it's disabled is actually not so. In both cases there were simple ways to fix them. In one it was just to alter the description (2 minutes) so it didn't say it was disabled and in the other it was either to add a suggest or alter the default configuration so it didn't require the missing suggest (2 minutes). We have to use common sense in QA and only ask that, to avoid all this unpleasantness in the future, common sense is used by the packager also. All this is a reaction to 4 minutes of additional work. That is not common sense to me. If we're expected to validate updates in the state these two bugs reached us then we may as well not be here at all. Claire
[Mageia-dev] Suggests for preload,readahead in task-gnome-minimal
task-gnome-minimal has the following: Suggests: preload Suggests: readahead IMO if something like that is needed, it should not belong in task-gnome-minimal, but something lowlevel like e.g. systemd. Even though these are just suggests, I still want to get rid of it. Any objections? -- Regards, Olav
Re: [Mageia-dev] Suggests for preload, readahead in task-gnome-minimal
06.07.2012 12:44, Olav Vitters kirjutas: task-gnome-minimal has the following: Suggests: preload Suggests: readahead IMO if something like that is needed, it should not belong in task-gnome-minimal, but something lowlevel like e.g. systemd. Even though these are just suggests, I still want to get rid of it. Any objections? Nop.. -- Sander
Re: [Mageia-dev] Suggests for preload, readahead in task-gnome-minimal
'Twas brillig, and Olav Vitters at 06/07/12 10:44 did gyre and gimble: task-gnome-minimal has the following: Suggests: preload Suggests: readahead IMO if something like that is needed, it should not belong in task-gnome-minimal, but something lowlevel like e.g. systemd. Even though these are just suggests, I still want to get rid of it. Any objections? Strangely enough I was thinking about the separate preload and readahead packages recently. I suspect the systemd-readahead stuff is where we want to consolidate. I was actually thinking of just dropping those other packages completely, but I've not fully read up on it yet. 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] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
On 06/07/12 07:56, Oliver Burger wrote: [...] This has nothing to do with being rude. IIUC, a small bit of it is related in 2 instances (from my pov): - QA team being ignored in their question - packager being doubted by QA team (in some or other forms, both of these can be seen as rude) for one more perceived rudeness, look below. As I said previously, this is being blown wildly out of proportion. very true In reality it centres around one packager and two bugs. In both these bugs the packager expected QA to validate updates where one was an xinetd service which expressly stated it was disabled by default but in actual fact was enabled and in the other a mailing list with a web interface which simply couldn't work in it's default configuration. What it being thrown at us is that we are unreasonably expecting every single little bug to be fixed without any common and need to make drastic changes to our policies. i did mention it would best for packagers (and i think it's in policy) that they would give reproducer tests for validation (perhaps it should be extended to getting the package working as well) We attended the packager meeting on Wednesday to respond to this and discuss it. At the meeting it was agreed that we had not changed the way we have been doing things since day one and that the right way forward was to continue doing what we were doing, with both packagers and QA using common sense. IIUC, not 100% the same, security updates should get pushed without delay even if there's an additional problem (unless regressions). The idea behind this, is that security updates are important for people who are already running it. and since they are running it, they aren't likely to have the problems that QA had. I have no trouble having contacting packager and ask for fix, but ultimately, for if for whatever reason the packager isn't there, i still think it should be pushed. The following day the same far fetched accusations are thrown at us again, now escalated to the ML, suggesting we caused a months delay and suggesting a solution to the accusation being we begin to 'rubber stamp' security updates regardless of if they actually work or not or an internet facing service which says it's disabled is actually not so. This is also perceived rudeness: - The packager's pov is that QA should have pushed it anyway. - personally, i'm not certain that this is the intention of the person who wrote it. The problem in this exact case, is that in fact, IMHO, the suggested modification, wasn't needed; allthough it might be better, it's ultimately not needed, because having a mailinglist, you need to configure alot of things anyway. and perhaps it's not even required to use CGI::Fast (depending on configuration). arguably it's perhaps better to have this as suggest. The packager's pov is that QA team was stating a undiscussable MUST that this dependency should be required (not suggested; which is better), while in effect, afterwards, it appears that this dependency is a separate and not even a major bug (easy workaround). But, QA team doesn't know alot about this. so i'm not speaking about faults here. Also packaging team must realize that QA team doesn't know alot about this. They are just doing what they think is right. but if packaging team says that this isn't really a major requirement for this security bug, then again, QA team should understand this too. In both cases there were simple ways to fix them. In one it was just to alter the description (2 minutes) so it didn't say it was disabled and in the other it was either to add a suggest or alter the default configuration so it didn't require the missing suggest (2 minutes). That is also true. We have to use common sense in QA and only ask that, to avoid all this unpleasantness in the future, common sense is used by the packager also. All this is a reaction to 4 minutes of additional work. That is not common sense to me. If we're expected to validate updates in the state these two bugs reached us then we may as well not be here at all. no offense meant, but in retrospect, it appears those new bugs in those 2 bug reports (to me) aren't that major at all. but I agree that it isn't easy to test, and thus packager should be accomodating that.
[Mageia-dev] Bugzilla mass assignee ping
Hi everyone, Later today there'll be a mass assignee ping for Bugzilla. Unfortunately, everyone in the cc of the bugs will receive the ping, too. The only bugs that'll be pinged are that * were assigned more than 2 weeks ago * where the assignee didn't do anything to the bug since more than two weeks ago * where the assignee didn't confirm the bug was assigned correctly by either setting status to ASSIGNED or by putting OK on the whiteboard and. Bugs that are assigned to QA or Bug Squad won't be pinged, nor will Reporter = Assignee ones. Enhancement requests and minor bugs won't be pinged either, nor will bugs that have the TRACKER or UPSTREAM keyword. If you're the assignee and you don't have a clue whether the bug was assigned correctly or not, please put NEEDHELP on the whiteboard. If you know it was *not* assigned correctly, please reassign to either the correct person or to Bug Squad, and explain. Set status to ASSIGNED or put OK on the whiteboard if you don't want to be pinged in the same bug for the same thing again. Cheers, marja
Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
Le 06/07/2012 13:19, AL13N a écrit : On 06/07/12 07:56, Oliver Burger wrote: [...] This has nothing to do with being rude. IIUC, a small bit of it is related in 2 instances (from my pov): - QA team being ignored in their question - packager being doubted by QA team (in some or other forms, both of these can be seen as rude) No, what is really rude for me is Claire's agressive reaction here, two times in a row. I don't ask for flowers and congratulations everytime I interact with anyone else asking for help, I'd just like avoid feeling assaulted for giving QA team too much work while volonteering to contribute fixing a stalled issue. Especially on a public media such as bugzilla. Now, as I've been advised to use common sense, I'll just shut up, instead of adding more fuel to the fire, and I'll try to select more wisely my personal involvement in the future. -- BOFH excuse #229: wrong polarity of neutron flow
Re: [Mageia-dev] Bugzilla mass assignee ping
On Fri, Jul 6, 2012 at 1:42 PM, Marja van Waes marj...@xs4all.nl wrote: Later today there'll be a mass assignee ping for Bugzilla. Couldn't we use another method than this? Like using Bugzilla's native whining feature, or an equivalent where each assignee only get notified of his assigned bugs in a single mail listing those?
Re: [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)
On 06/07/12 12:57, Guillaume Rousse wrote: Le 06/07/2012 13:19, AL13N a écrit : On 06/07/12 07:56, Oliver Burger wrote: [...] This has nothing to do with being rude. IIUC, a small bit of it is related in 2 instances (from my pov): - QA team being ignored in their question - packager being doubted by QA team (in some or other forms, both of these can be seen as rude) No, what is really rude for me is Claire's agressive reaction here, two times in a row. I don't ask for flowers and congratulations everytime I interact with anyone else asking for help, I'd just like avoid feeling assaulted for giving QA team too much work while volonteering to contribute fixing a stalled issue. Especially on a public media such as bugzilla. Now, as I've been advised to use common sense, I'll just shut up, instead of adding more fuel to the fire, and I'll try to select more wisely my personal involvement in the future. The stalled issue was actually a packaging issue Guillaume. We don't expect to be held responsible for those in QA or have to send flowers when they are resolved. Perhaps that is where this misunderstanding stems from. Claire
Re: [Mageia-dev] [Mageia-bugsquad] Bugzilla mass assignee ping
On 06/07/2012 13:59, Romain d'Alverny wrote: On Fri, Jul 6, 2012 at 1:42 PM, Marja van Waesmarj...@xs4all.nl wrote: Later today there'll be a mass assignee ping for Bugzilla. Couldn't we use another method than this? Like using Bugzilla's native whining feature, or an equivalent where each assignee only get notified of his assigned bugs in a single mail listing those? Yes, that would be a lot better. I understood that feature was disabled to solve bug 1932 https://bugs.mageia.org/show_bug.cgi?id=1932
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
On Fri, Jul 6, 2012 at 2:13 PM, Marja van Waes marj...@xs4all.nl wrote: On 06/07/2012 13:59, Romain d'Alverny wrote: On Fri, Jul 6, 2012 at 1:42 PM, Marja van Waesmarj...@xs4all.nl wrote: Later today there'll be a mass assignee ping for Bugzilla. Couldn't we use another method than this? Like using Bugzilla's native whining feature, or an equivalent where each assignee only get notified of his assigned bugs in a single mail listing those? Yes, that would be a lot better. I understood that feature was disabled to solve bug 1932 https://bugs.mageia.org/show_bug.cgi?id=1932 Ok, but there a daily reminder is nonsense. A monthly (or every 2 months) reminder of bugs fitting in your above query would sound sane, if it's sent only to the assignee. If not, then the whole mass ping itself should not be done either.
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
On 06/07/2012 14:22, Romain d'Alverny wrote: On Fri, Jul 6, 2012 at 2:13 PM, Marja van Waesmarj...@xs4all.nl wrote: On 06/07/2012 13:59, Romain d'Alverny wrote: On Fri, Jul 6, 2012 at 1:42 PM, Marja van Waesmarj...@xs4all.nl wrote: Later today there'll be a mass assignee ping for Bugzilla. Couldn't we use another method than this? Like using Bugzilla's native whining feature, or an equivalent where each assignee only get notified of his assigned bugs in a single mail listing those? Yes, that would be a lot better. I understood that feature was disabled to solve bug 1932 https://bugs.mageia.org/show_bug.cgi?id=1932 Ok, but there a daily reminder is nonsense. Maybe it works better in upgraded Bugzilla :) A monthly (or every 2 months) reminder of bugs fitting in your above query would sound sane, if it's sent only to the assignee. If not, then the whole mass ping itself should not be done either. Waiting one month to find out whether a bug was assigned correctly is too long, in my opinion, unless the assignee is busy gathering enough information to be able to tell. I think we should ping bug reports for which we haven't got a confirmation that the assignment was correct after two weeks, except when the assignee shows activity in the report. If the assignee thinks the bug was assigned correctly, he can put OK on the whiteboard or set status to ASSIGNED, and he won't show up in this search again, so he won't be pinged for this reason again.
Re: [Mageia-dev] Bugzilla mass assignee ping
On Fri, Jul 6, 2012 at 4:42 AM, Marja van Waes marj...@xs4all.nl wrote: Hi everyone, Later today there'll be a mass assignee ping for Bugzilla. Unfortunately, everyone in the cc of the bugs will receive the ping, too. The only bugs that'll be pinged are that * were assigned more than 2 weeks ago * where the assignee didn't do anything to the bug since more than two weeks ago * where the assignee didn't confirm the bug was assigned correctly by either setting status to ASSIGNED or by putting OK on the whiteboard and. Bugs that are assigned to QA or Bug Squad won't be pinged, nor will Reporter = Assignee ones. Enhancement requests and minor bugs won't be pinged either, nor will bugs that have the TRACKER or UPSTREAM keyword. If you're the assignee and you don't have a clue whether the bug was assigned correctly or not, please put NEEDHELP on the whiteboard. If you know it was *not* assigned correctly, please reassign to either the correct person or to Bug Squad, and explain. Set status to ASSIGNED or put OK on the whiteboard if you don't want to be pinged in the same bug for the same thing again. Not sure how useful it is. I have received 25 emails so far in today's ping (and they keep coming). Some of them because I am assignee, some because I am reporter, some I am in CC. I probably need to take action on few of them but I currently don't have time to check which ones so it is likely that I will end up ignoring them all...
Re: [Mageia-dev] Bugzilla mass assignee ping
On 06/07/2012 15:17, Pascal Terjan wrote: On Fri, Jul 6, 2012 at 4:42 AM, Marja van Waesmarj...@xs4all.nl wrote: Not sure how useful it is. I have received 25 emails so far in today's ping (and they keep coming). Some of them because I am assignee, some because I am reporter, some I am in CC. I probably need to take action on few of them but I currently don't have time to check which ones so it is likely that I will end up ignoring them all... We'll remind you and everybody else who hasn't got time now :) However, hopefully next time with mails that only the assignees will receive
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
(removed -discuss from the discussion) On Fri, Jul 6, 2012 at 2:48 PM, Marja van Waes marj...@xs4all.nl wrote: On 06/07/2012 14:22, Romain d'Alverny wrote: Maybe it works better in upgraded Bugzilla :) No, it works in the current setup. A monthly (or every 2 months) reminder of bugs fitting in your above query would sound sane, if it's sent only to the assignee. If not, then the whole mass ping itself should not be done either. Waiting one month to find out whether a bug was assigned correctly is too long, in my opinion, unless the assignee is busy gathering enough information to be able to tell. I think we should ping bug reports for which we haven't got a confirmation that the assignment was correct after two weeks, except when the assignee shows activity in the report. If the assignee thinks the bug was assigned correctly, he can put OK on the whiteboard or set status to ASSIGNED, and he won't show up in this search again, so he won't be pinged for this reason again. We can make a bi-monthly check that will only whine to the assignees, and not others. That makes at most (for the unlucky ones), two mails a month summarizing what they are assigned to and that it has not been checked out of the query. Shall we try that?
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
On 06/07/2012 16:49, Romain d'Alverny wrote: (removed -discuss from the discussion) On Fri, Jul 6, 2012 at 2:48 PM, Marja van Waesmarj...@xs4all.nl wrote: On 06/07/2012 14:22, Romain d'Alverny wrote: Maybe it works better in upgraded Bugzilla :) No, it works in the current setup. I think we should ping bug reports for which we haven't got a confirmation that the assignment was correct after two weeks, except when the assignee shows activity in the report. If the assignee thinks the bug was assigned correctly, he can put OK on the whiteboard or set status to ASSIGNED, and he won't show up in this search again, so he won't be pinged for this reason again. We can make a bi-monthly check that will only whine to the assignees, and not others. That makes at most (for the unlucky ones), two mails a month summarizing what they are assigned to and that it has not been checked out of the query. Shall we try that? Well, if you replace bi-monthly by twice a month (that seems to be what you mean), then: yes, please! Bi-monthly doesn't have a fixed meaning http://en.wiktionary.org/wiki/bi-monthly ;) Thanks a lot, Romain :)
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
Le vendredi 6 juillet 2012 17:46:16 Marja van Waes a écrit : On 06/07/2012 16:49, Romain d'Alverny wrote: (removed -discuss from the discussion) On Fri, Jul 6, 2012 at 2:48 PM, Marja van Waesmarj...@xs4all.nl wrote: On 06/07/2012 14:22, Romain d'Alverny wrote: Maybe it works better in upgraded Bugzilla :) No, it works in the current setup. I think we should ping bug reports for which we haven't got a confirmation that the assignment was correct after two weeks, except when the assignee shows activity in the report. If the assignee thinks the bug was assigned correctly, he can put OK on the whiteboard or set status to ASSIGNED, and he won't show up in this search again, so he won't be pinged for this reason again. We can make a bi-monthly check that will only whine to the assignees, and not others. That makes at most (for the unlucky ones), two mails a month summarizing what they are assigned to and that it has not been checked out of the query. Shall we try that? Well, if you replace bi-monthly by twice a month (that seems to be what you mean), then: yes, please! Bi-monthly doesn't have a fixed meaning http://en.wiktionary.org/wiki/bi-monthly ;) Thanks a lot, Romain :) Hi, Please continue these mass ping until the solution for filtering problems in kmail ... we will see if it is a good solution :p A+ Raph
[Mageia-dev] Changes in chromium
Hi, please report in from now chromium is broken ( compared to before ). I am patching to use system libs instead of bundled ones ( i do one by one ) regards; D.
Re: [Mageia-dev] Changes in chromium
Le vendredi 6 juillet 2012 18:04:57 D.Morgan a écrit : Hi, please report in from now chromium is broken ( compared to before ). I am patching to use system libs instead of bundled ones ( i do one by one ) regards; D. Hi, Maybe it explains what I read before ? In the sense that it is difficult to built packages for Chromium and so it is 'normal' that it is 'often outdated' in comparaison with Chrome ? A+ Raph
Re: [Mageia-dev] [Mageia-discuss] [Mageia-bugsquad] Bugzilla mass assignee ping
On Fri, Jul 6, 2012 at 5:46 PM, Marja van Waes marj...@xs4all.nl wrote: On 06/07/2012 16:49, Romain d'Alverny wrote: Shall we try that? Well, if you replace bi-monthly by twice a month (that seems to be what you mean), then: yes, please! Yes. Ok, test will go in a few minutes to all current assignees that have bugs matching your query (I had to duplicate it to my own account).
