Re: [Mageia-dev] virtuoso-t (nepomuk?) takes too much memory (and CPU)
On Monday 30 January 2012 12:48:18 Maarten Vanraes wrote : [...] is this fixable? looking at those bug reports, it looks like this has been going on for a while now... Well until upstream fix it i guess we're stuck with it :/ [...] disabling this desktop search does not have effect on the kmail? i would guess not from how you put it, but i'm just asking for confirmation here :-) If you disable desktop search it won't work in kmail. Also i'm not sure if it's fixed but if i'm not wrong the « disable kmail index » functionnality does not work (even if it's supposed to be disable it's going to work...) Regards, -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] crond was not set to start
'Twas brillig, and Olav Vitters at 29/01/12 20:34 did gyre and gimble: Yeah. Various services were broken after systemd switch. I enabled the broken ones. Have been using systemd for a few months at least. Suddenly crond broke. I wonder if it suddenly got a native system unit rather than going via sysvinit compatibility? That would have this kind of behaviour (assuming it didn't break after the initial switch to systemd). This is one of the cases I'm going to have to look at in the rpm-helper scripts, but it should be doable. 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] stardict 3.0.3
Hello! W dniu 30.01.2012 14:33, Funda Wang pisze: Personally, i'm in favour of dropping it, due to what is said in its homepage: StarDict hasn't seen any active development for many years Well it's worth to consider importing goldentict too, but I'm against dropping stardict - it's actually alive and people keep porting it to GTK3. https://code.google.com/p/stardict-3/updates/list 2012/1/30 Kamil Rytarowskin...@gmx.com: Hello! Thanks for fixing stardict! I had problems with mirrors and temporarely wasn't able to fix the glib.h headers locally.
[Mageia-dev] sudo security update
Hello, If you are using sudo on Mageia 1 or Cauldron, don't forget to update the package to the latest version available in updates (1.8.0-5.mga1) or Cauldron (sudo-1.8.3p2-1.mga2). It fix this vulnerability which can allow a user to run arbitrary commands as root : http://www.sudo.ws/sudo/alerts/sudo_debug.html
[Mageia-dev] RFC Package Naming Policy
Dear all,
Following some recent mix-up, some possible ambiguity was found in the
current policy with respect to package naming (as seen in
https://wiki.mageia.org/en/Packaging_guidelines#Package_Naming).
--
So currently it is written:
«* Name should be the upstream name of the software project, always
lowercase.
* When the package name is different to the project name, you should
define and use %{upstream_name} macro to refer to the original project
name within the spec
* ''Dash '-' must be used as the delimiter for name parts.''
* ''Do NOT use an underscore '_', a plus '+', or a period '.' as a
delimiter.''
* The spec file should be named using the %{name}.spec scheme, i.e. the
name of the package should be used as the name for the spec.»
I propose to change it to the following:
«* The base package names (used for svn and src.rpm) should be the
upstream name of the software project, always lowercase. Upstream names
can contain digits, '+', '_' or '.', but no other special characters.
Really exceptionally, uppercase letters can be allowed if there is
proper justification or historical reasons.
* Package names that are built by Mageia packagers from the upstream
name by adding suffixes should always use '-' as delimiter (e.g.
foo-devel or foo-plugins as derived from the foo package). All '_' and
'+' in package names must come from upstream naming! The '.' in package
names should only come upstream or standard versioning schemes.
* The spec file should be named using the %{name}.spec scheme, i.e. the
name of the source package and svn directory should be used as the name
for the spec.»
-
Some of you may notice that the newly drafted policy allows upper-case
letters in packages as an exception (when justified). This is to follow
the current practice (which is not following the current policy, where
we have packages like R-base).
I don't want to raise a heated discussion (there was an inconclusive
discussion a long time ago on cooker [*]) about enforcing an all
lower-case policy. Not sure a consensus can be reached today, but
lower-casing package names should be the default for 99% of the packages
in Mageia.
Any comments? Is it indeed clearer this way? Any other conditions on
package names we should add?
Best regards,
--
Malo
[*] http://lists.mandriva.com/cooker/2006-03/msg03396.php
Re: [Mageia-dev] RFC Package Naming Policy
On 12/01/30 18:24 +, Pierre-Malo Deniélou wrote: Some of you may notice that the newly drafted policy allows upper-case letters in packages as an exception (when justified). This is to follow the current practice (which is not following the current policy, where we have packages like R-base). I don't want to raise a heated discussion (there was an inconclusive discussion a long time ago on cooker [*]) about enforcing an all lower-case policy. Not sure a consensus can be reached today, but lower-casing package names should be the default for 99% of the packages in Mageia. except it cannot be. perl module Foo::Bar is shipped in package perl-Foo-Bar since quite a lot of time, per policy. so the ~2500 perl packages are almost all using some upper-case, which make your 99% figure totally wrong (2500 / 1 = ~25% using upper case) note that perl packages shipping an application or a script useful on their own do follow the policy and are called eg perlbrew, nopaste, grok, etc. sorry to disappoint you, jérôme
Re: [Mageia-dev] virtuoso-t (nepomuk?) takes too much memory (and CPU)
Op maandag 30 januari 2012 14:50:11 schreef Balcaen John: On Monday 30 January 2012 12:48:18 Maarten Vanraes wrote : [...] is this fixable? looking at those bug reports, it looks like this has been going on for a while now... Well until upstream fix it i guess we're stuck with it :/ Well, thanks for the info at least... disabling this desktop search does not have effect on the kmail? i would guess not from how you put it, but i'm just asking for confirmation here :-) If you disable desktop search it won't work in kmail. Also i'm not sure if it's fixed but if i'm not wrong the « disable kmail index » functionnality does not work (even if it's supposed to be disable it's going to work...) /me facepalms...
Re: [Mageia-dev] stardict 3.0.3
Le 30/01/2012 17:55, Kamil Rytarowski a écrit : Hello! W dniu 30.01.2012 14:33, Funda Wang pisze: Personally, i'm in favour of dropping it, due to what is said in its homepage: StarDict hasn't seen any active development for many years Well it's worth to consider importing goldentict too, but I'm against dropping stardict - it's actually alive and people keep porting it to GTK3. https://code.google.com/p/stardict-3/updates/list Hi What about asking his (her) opinion to the maintainer *before* upgrading it to the new version ? + kamilkamil - new versdion 3.0.3 - disable all patches, they seem merged - update URL - update SOURCE ** As the maintainer, it was to me to take the decision to upgrade or propose something else for mageia. You have the right to ask me what I want to do with it and to expose your opinion. But next time, ask the maintainer before ! There was no bugreport open for stardict, so no emergency to touch this package. And in case you are no aware of the fact we have a database for maintainership : mgarepo maintdb getpackage_name do the trick. Claire
Re: [Mageia-dev] stardict 3.0.3
Le lundi 30 janvier 2012 à 20:53 +0100, Claire Revillet a écrit : Le 30/01/2012 17:55, Kamil Rytarowski a écrit : Hello! W dniu 30.01.2012 14:33, Funda Wang pisze: Personally, i'm in favour of dropping it, due to what is said in its homepage: StarDict hasn't seen any active development for many years Well it's worth to consider importing goldentict too, but I'm against dropping stardict - it's actually alive and people keep porting it to GTK3. https://code.google.com/p/stardict-3/updates/list Hi What about asking his (her) opinion to the maintainer *before* upgrading it to the new version ? + kamilkamil - new versdion 3.0.3 - disable all patches, they seem merged - update URL - update SOURCE ** As the maintainer, it was to me to take the decision to upgrade or propose something else for mageia. So as the maintainer, can you explain to us why you did not warn us of the copyright problem that we can see since 07/2011 on http://stardict.sourceforge.net/ -- Michael Scherer
Re: [Mageia-dev] stardict 3.0.3
W dniu 30.01.2012 20:53, Claire Revillet pisze: Le 30/01/2012 17:55, Kamil Rytarowski a écrit : Hello! W dniu 30.01.2012 14:33, Funda Wang pisze: Personally, i'm in favour of dropping it, due to what is said in its homepage: StarDict hasn't seen any active development for many years Well it's worth to consider importing goldentict too, but I'm against dropping stardict - it's actually alive and people keep porting it to GTK3. https://code.google.com/p/stardict-3/updates/list Hi What about asking his (her) opinion to the maintainer *before* upgrading it to the new version ? + kamilkamil - new versdion 3.0.3 - disable all patches, they seem merged - update URL - update SOURCE ** As the maintainer, it was to me to take the decision to upgrade or propose something else for mageia. Hi Claire! I keep updating URLs and SOURCEs - the initial bug-request was there https://bugs.mageia.org/show_bug.cgi?id=3035 (I have reviewed initially 2,500 source-packages). You have the right to ask me what I want to do with it and to expose your opinion. But next time, ask the maintainer before ! There was no bugreport open for stardict, so no emergency to touch this package. And in case you are no aware of the fact we have a database for maintainership : mgarepo maintdb getpackage_name do the trick. I was informed that this mostly means that you are responsible for decisions what to do in future with a package, and you are ready to be assigned in a bug-request etc. So what do you think about the future of StarDICT? I was looking at the projects and I'm a little bit affraid of the licenses and patents. For example GoldenDict is said to support Babylon - and this can be problematic with patents. Have you reviewed the dicts if they are legally used? Claire
Re: [Mageia-dev] virtuoso-t (nepomuk?) takes too much memory (and CPU)
On Monday 30 January 2012 20:14:47 Maarten Vanraes wrote : [...] /me facepalms... You can read this thread if you want http://lists.kde.org/?l=kde-pimm=132769144326703w=2 Regards, -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] RFC Package Naming Policy
On 30 January 2012 20:15, Jerome Quelin jque...@gmail.com wrote: Some of you may notice that the newly drafted policy allows upper-case letters in packages as an exception (when justified). This is to follow the current practice (which is not following the current policy, where we have packages like R-base). I don't want to raise a heated discussion (there was an inconclusive discussion a long time ago on cooker [*]) about enforcing an all lower-case policy. Not sure a consensus can be reached today, but lower-casing package names should be the default for 99% of the packages in Mageia. except it cannot be. perl module Foo::Bar is shipped in package perl-Foo-Bar since quite a lot of time, per policy. so the ~2500 perl packages are almost all using some upper-case, which make your 99% figure totally wrong (2500 / 1 = ~25% using upper case) note that perl packages shipping an application or a script useful on their own do follow the policy and are called eg perlbrew, nopaste, grok, etc. Well, the low case names policy did was a policy for years. We slowly killed most upcase names over the years, perl being an exception. I think we should enforce it modulo perl
Re: [Mageia-dev] stardict 3.0.3
I keep updating URLs and SOURCEs - the initial bug-request was there https://bugs.mageia.org/show_bug.cgi?id=3035 (I have reviewed initially 2,500 source-packages). 1) stardict does not appear in the list 2) why maintainers are not been contacted for all those problems ? So what do you think about the future of StarDICT? I was looking at the projects and I'm a little bit affraid of the licenses and patents. For example GoldenDict is said to support Babylon - and this can be problematic with patents. For me StarDict is a dead project and I was looking for a successor. There is no information on the copyright infringement and the tarball that can be downloaded on the new site are exactly the same as the old ones ! So the first possibility is: there was truly a copyright problem and there is still (this may be proved in the future if the copyright owner ask to close again the project) ; second possibility: there was no copyright problem (but a more obscure one), but, still, the project is not very active. So if GoldenDict present, at this time, no license or patent problem and is actively developed : it can be a better choice. Import freeze for mageia 2 will be in march, so I think we have a little time to think about it to choose the best solution for mageia 2 and test it (bugs...) before release. Let's take the week for discussion. you reviewed the dicts if they are legally used? I checked for almost all dict : they are GPL or Creative Commons Attribution-ShareAlike Licence (V3.0). Just 1 as to be modified (quick-deu-eng) or simply removed. I'll do that in the week. I think url information may not be good, but I did not see the point of rebuilding 200 packages just for that (taking into account the fact that dictionaries are not code : they do not evolve). Claire
Re: [Mageia-dev] stardict 3.0.3
Le 30/01/2012 22:31, Claire Revillet a écrit : I keep updating URLs and SOURCEs - the initial bug-request was there https://bugs.mageia.org/show_bug.cgi?id=3035 (I have reviewed initially 2,500 source-packages). 1) stardict does not appear in the list 2) why maintainers are not been contacted for all those problems ? 3) if your point was just to fix bad URLs, why upgrading ? Claire
Re: [Mageia-dev] stardict 3.0.3
2012/1/31 Claire Revillet gren...@zarb.org: For me StarDict is a dead project and I was looking for a successor. There is no information on the copyright infringement and the tarball that can be downloaded on the new site are exactly the same as the old ones ! So the first possibility is: there was truly a copyright problem and there is still (this may be proved in the future if the copyright owner ask to close again the project) ; second possibility: there was no copyright problem (but a more obscure one), but, still, the project is not very active. I think there is no copyright problem with the stardict the program itself, only the data files (dictionaries). But the author has been missing for half a year: http://goldendict.org/forum/viewtopic.php?f=4t=1109
Re: [Mageia-dev] stardict 3.0.3
Le 30/01/2012 22:50, Funda Wang a écrit : 2012/1/31 Claire Revilletgren...@zarb.org: For me StarDict is a dead project and I was looking for a successor. There is no information on the copyright infringement and the tarball that can be downloaded on the new site are exactly the same as the old ones ! So the first possibility is: there was truly a copyright problem and there is still (this may be proved in the future if the copyright owner ask to close again the project) ; second possibility: there was no copyright problem (but a more obscure one), but, still, the project is not very active. I think there is no copyright problem with the stardict the program itself, only the data files (dictionaries). But the author has been missing for half a year: http://goldendict.org/forum/viewtopic.php?f=4t=1109 It's also what I think : no really copyright pb with the code (and yes, I had seen link :\ ). I don't think the problem is with the dict, because the pages with all the dict are still there : http://abloz.com/huzheng/stardict-dic/ (and easy to find). So, for me, dict are okay. But if the new dev is not really active, it is a good time to change the software for the distribution.
[Mageia-dev] Servers downtime scheduled from Feb. 1 to 2 for maintenance
Hello everyone, some Mageia servers will be down from Wednesday Feb. 1st to Thursday Feb. 2nd for maintenance. Particularly, the following services will be unavailable: - our LDAP/user identity db, - build system, - Bugzilla, - all mailing-lists hosted on ml.mageia.org, - Wiki, - forums. So... not all, but, a lot of what you use here! The exact hours of interruption are not known, so expect no availability for those 2 full days. Blog (where an equivalent warning will be posted), Web site, mailing-lists (and archives) will not be down. In the meantime, in our Marseille data center, 4 of our sysadmin team (dams, boklm, rtp and misc in this case) will do nothing less than: - upgrade servers to Mageia 1, - replace broken HDD, - add SSD in build nodes, - install our ARM build system, - install a dedicated server for backups, - install a dedicated server for QA and packagers. All hardware purchased thanks to what Mageia.Org received from so many donators (http://mageia.org/en/thank-you/ again). This is quite a short notice, we apologize for this. Thank you for your comprehension (and please spread the info to your list/team if relevant).
Re: [Mageia-dev] stardict 3.0.3
Le lundi 30 janvier 2012 à 22:56 +0100, Claire Revillet a écrit : Le 30/01/2012 22:50, Funda Wang a écrit : 2012/1/31 Claire Revilletgren...@zarb.org: For me StarDict is a dead project and I was looking for a successor. There is no information on the copyright infringement and the tarball that can be downloaded on the new site are exactly the same as the old ones ! So the first possibility is: there was truly a copyright problem and there is still (this may be proved in the future if the copyright owner ask to close again the project) ; second possibility: there was no copyright problem (but a more obscure one), but, still, the project is not very active. I think there is no copyright problem with the stardict the program itself, only the data files (dictionaries). But the author has been missing for half a year: http://goldendict.org/forum/viewtopic.php?f=4t=1109 It's also what I think : no really copyright pb with the code (and yes, I had seen link :\ ). Unfortunately, that's not really the opinion of the sourceforge lawyers. I assume that since you didn't warn us of a problem during the 6 months that you at least took the initiative as a maintainer to contact sourceforge.net, and that you received a answer letting you safely to dismiss their analysis. So can you share the answer, and/or the analysis ? Because I think that if we have a special treatement for patents and DMCA despites having legal protections ( safe harbor laws in the USAs, for example ) for mirrors, we should at least be as vigilant for copyright violation when there is no such provision and much stricter laws ( per various treaty ), as we all know given the current events. -- Michael Scherer
