Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday
On Tue 09 Apr 2013 23:07:38 CEST, Juergen Harms wrote: On 04/09/2013 11:03 AM, Christiaan Welvaart wrote: ... cross-avr-gcc ... The current package has the same rpmlint warnings so you don't need to fix this right now INHO. The hardlinks are only a problem when /usr/bin is on a different filesystem than /usr. I see there are still packages being pushed - if I manage tomorrow to submit a new cross-avr-gcc, would that still have a chance to get pushed before the freeze? would be nice if Mageia-3 contains a properly working avr cross compiler - and would reduce the count of packages that dont build. (no need to upgrade the avr-binutils package from 2.20 to 2.23 to satisfy that dependency: cross-avr-gcc seems to build and work correctly with cross-avr-binutils-2.20 which is presently in cauldron). If you test that your updated package works ok, and argue it well, it will be pushed. -- Malo
[Mageia-dev] freeze push: ocaml-rss 2.1.0
We currently have a weird intermediary git version. Here is the final 2.1.0, which works better with our stog and future versions. Only stog depends on it (I will ask for a freeze push in a moment). Thanks, -- Malo
[Mageia-dev] freeze push: stog-0.8
Our current version does not work properly. With the updated ocaml-rss-2.1.0, stog-0.8 works well. Nothing depends on it. Thanks, -- Malo
[Mageia-dev] freeze push: hevea 2.06
This is actually two mostly bug fix releases. we currently have 2.04:
version 2.06
* Two bugs reported by Michael Ernst fixed *
- Some spaces dissapeared in toc's FIX - add braces around macro
expansion in subst_expn
- Spurious '_' outside of math mode warnings when \label{..._...}
occurs in section titles FIX - add \@getprint around
\sec@id@attr in \@doaddtoc [latexcommon.hva] and \cuthere
[html/hevea.hva].
version 2.05
- Promote to official release
version 2.04+dev2
- Correct esponja bug for windows : in windows you cannot
remove a file when it is still open !
version 2.04+dev1
- patch by C Deleuze for a few fixes in info mode.
Thanks,
--
Malo
[Mageia-dev] freeze push: gprolog 1.4.3
This is a mostly bug fix release. We currently have 1.4.2. Nothing depends on it. Change in GNU Prolog version 1.4.3: * add new C foreign interface functions converting term to/from C strings * modify top-level banner to show 32/64 bits, compile date, C compiler name * modify Linedit: fix Prolog prompt when Linedit is not activated * modify linedit: accept gui=silent in env var LINEDIT (does not warn if the windows gui DLL is not found) * fixes for Windows 8 (i686 and x86_64) with MSVS 2012, mingw64 gcc 4.5.3 * add Prolog flags address_bits, compiled_at, c_cc, c_cflags, c_ldflags * fix a bug in the FD solver (option backtracks in fd_labeling) * improve the FD solver (better propagation for reified constraints at labeling) * improve the FD solver (add labeling option: value_method(bisect)) * improve the FD solver (avoid some cases of C stack overflow, improved fd_domain/3) * fix a bug in the FD solver (regression bug in 1.4.2) * add PlULong to gprolog.h and PlThrow(ball) to C foreign interface Thanks, -- Malo
[Mageia-dev] freeze push: vowpal-wabbit 7.2
Vowpal-wabbit is a machine learning computational tool. We currently have 7.1. Nothing depends on it, and it was not in Mageia 2. I don't have a changelog (it's a huge git commit dump) to show, but it works and allows to drop the patches we used and were upstreamed. Thanks, -- Malo
[Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Hi all, There will be a packagers meeting tonight at 20h UTC as usual. Only one topic: - Release critical bugs: review and status Please all attend for progress to be made on these bugs. Reminder: https://bugs.mageia.org/buglist.cgi?bug_status=NEWbug_status=UNCONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDbug_status=VERIFIEDpriority=release_blockerproduct=Mageiaquery_format=advancedversion=Cauldronorder=assigned_to%2Cbug_id%20DESCquery_based_on=release_blockerlist_id=2442 Cheers, -- Malo
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
On 26/03/13 13:58, Pascal Terjan wrote: On Tue, Mar 26, 2013 at 1:44 PM, Pierre-Malo Deniélou pierre-malo.denie...@rhul.ac.uk wrote: Hi all, There will be a packagers meeting tonight at 20h UTC as usual. Only one topic: - Release critical bugs: review and status Please all attend for progress to be made on these bugs. Reminder: https://bugs.mageia.org/buglist.cgi?bug_status=NEWbug_status=UNCONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDbug_status=VERIFIEDpriority=release_blockerproduct=Mageiaquery_format=advancedversion=Cauldronorder=assigned_to%2Cbug_id%20DESCquery_based_on=release_blockerlist_id=2442 Can we also discuss what to do about http://check.mageia.org/cauldron/dependencies.html ? Should a thread be started for each to decide what to do about it? Bugs open? Good idea. Any of those packages that doesn't get fixed will be dropped (as it can not be installed anyway) We should discuss it. Maybe also we can mention the packages which have not been built recently (failed mass rebuild). Can you post a list? Ok. New list of topics: - Uninstallable packages: http://check.mageia.org/cauldron/dependencies.html - Packages which failed rebuild - Release critical bugs: review and status Cheers, -- Malo
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Minutes of the meeting for people who couldn't attend: http://meetbot.mageia.org/mageia-dev/2013/mageia-dev.2013-03-26-20.03.html -- Malo
[Mageia-dev] Reminder: Release freeze on the 7th April
Dear fellow packagers, Please work on your packages quickly, as release freeze is coming soon. After that, only packaging bug fixes will be accepted, but no more new versions of software. https://wiki.mageia.org/en/Mageia_3_development Thanks, -- Malo
[Mageia-dev] freeze push: burgerspace 1.9.2
This is a bug fix release: 2013-02-25: Version 1.9.2 released Slot selection when loading or saving games can now be done with up and down keys, to accommodate keyboard layouts where digits are shifted. Fixed bug where program crashed when saving game where player sprite was absent. Saved format version changed, but version 1 format can still be loaded. Added #include unistd.h to src/RemoteServer.cpp to resolve a compilation error related to close(1) under GCC 4.7. Fixed default UDP port displayed by ./configure --help. Thanks, -- Malo
[Mageia-dev] freeze push: hevea 2.04
This is actually two mostly bug fix releases. we currently have 2.02
version 2.04
- added \addto command to augment macros
- partial implementation of cleveref
- implemented hyperef \autoref
- added hidden labeltype package to specify label types in .haux
files
- implemented global options
version 2.03+dev
- Change in \label management: if \label{lbl} occurs in the argument
of a sectionning command (a.k.a section title),
then the tag lbl will be used as the id
of the enclosing h... element in html output.
A specific warning is introduced to flag multiple occurences
of \label in section titles.
version 2.03
- Correct \addcontentsline so as to avoid any style, in .haux
and make \@addcontentsline armoured (useless?)
Thanks,
--
Malo
[Mageia-dev] freeze push: rabbitmq-server 3.0.4
This is actually two bug fix releases (including a security fix). We currently have 3.0.4. Release: RabbitMQ 3.0.4 federation plugin - bug fixes 25483 prevent x-received-from header from leaking upstream credentials Release: RabbitMQ 3.0.3 server -- bug fixes 25457 fix connection failure to start reading again in rare circumstances when coming out of flow control 25419 ensure invocation of rabbitmqctl stop_app during server startup on a fresh node does not leave a corrupted Mnesia schema 25448 ensure messages expire immediately when reaching the head of a queue after basic.get 25456 ensure parameters and policies for a vhost are removed with that vhost 25465 do not log spurious errors for connections that close very early 25443 ensure rabbitmqctl forget_cluster_node removes durable queue records for unmirrored queues on the forgotten node 25435 declare dependency on xmerl in rabbit application management plugin - bug fixes 25472 clean up connection and channel records from nodes that have crashed 25432 do not show 404 errors when rabbitmq_federation_management is installed and rabbitmq_federation is not mqtt plugin --- bug fixes 25469 ensure the reader process hibernates when idle Thanks, -- Malo
[Mageia-dev] Easy Bugs to fix for Mageia 3
Dear all, Anne is already posting the list of current release critical bugs for Mageia 3. They are our priority. However, for some of us who do not have the expertise to help much for these bugs, besides testing possible fixes, and for our current apprentices, I remind you that there is a list of easy bugs to fix: https://bugs.mageia.org/buglist.cgi?cmdtype=doremremaction=runnamedcmd=Junior_jobsharer_id=81list_id=1765 They are called Junior_jobs as the fix is only an added Require, a fixed URL, etc. But these sometimes are a big annoyance for our users. So, please have a look at some of these 111 bugs when you feel like resting your mind from the release critical ones. Cheers, -- Malo
Re: [Mageia-dev] Team election results
On Sat 16 Mar 2013 12:06:40 GMT, Anne Nicolas wrote: Hi there Many thanks for taking some time to vote. Here are the results: https://epoll.mageia.org/vote/V9abIopH So new packagers representatives are: - pierre-malo denielou (aka malo) - philippe makowski (aka philippem) - anne nicolas (aka ennael) Welcome on board guys! Now I'm taking 2 months vacation :) (joking) Next packagers meeting will be on 19th of march. Thanks Anne, and thanks everyone for their votes. Cheers, -- Malo
Re: [Mageia-dev] Team elections
Hi everyone, Since there seems to be an overall low motivation to have candidates, I wish to propose myself as one of the 3 packaging team leaders. The aim for my application is that I want to improve and develop the mentoring process. I am ready to take responsibilities with respect to that. Note that I want to work and help on the mentoring process irrespectively of the team leaders choice. The reasoning behind my application is that it might be better to have some team leaders that have an aim (and take some responsibilities), than some who are just designated by default. Anyway, as we all know, free software projects work by do-ocraty, where the people who decide are the people who do something, quite independently of the election of any team leader :-). Some words about who I am: I'm a French man living in London, UK, where I work as a University lecturer in Computer Science. It means that I am quite time-constrained from October to March, and more free of my schedule from April to September. I am not an old-time Mandriva packager (Although I am a long time user): I joined Mageia in its early phases and went through the mentoring process. I now maintain a lot of the OCaml stack as well as random packages (overall 150ish packages). I also was the one annoying everyone with the RPM group changes. If I may help my fellow packagers with some pluses and minuses of my application: + recent member, fresh eye on Mageia without much Mandriva heritage - less experienced packager, + focus on mentoring - would work on mentoring even if not elected + lives in UK (a bit of diversity) - French (weak diversity, we don't want too many French team leaders) Cheers, -- Malo
Re: [Mageia-dev] Freeze push: stog
Le 22/02/13 23:51,Guillaume Rousse nous adresse ces quelques mots : Le 22/02/2013 19:19, Malo a écrit : Hello, Please submit stog-0.7.0. Build failure: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130222183213.guillomovitch.valstar.4971/log It should be ok now to try again. Thanks, -- Malo
Re: [Mageia-dev] Freeze push: stog
Le 23/02/13 20:59,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 22/02/13 23:51,Guillaume Rousse nous adresse ces quelques mots : Le 22/02/2013 19:19, Malo a écrit : Hello, Please submit stog-0.7.0. Build failure: http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130222183213.guillomovitch.valstar.4971/log It should be ok now to try again. Thanks, Thanks Guillaume, but you were too fast :-). The last submission was still using the unfixed ocaml-config-file-1.1-2.mga3 Cheers, -- Malo
[Mageia-dev] Freeze push: stog
Hello, Please submit stog-0.7.0. stog is a static website generator written in OCaml. Nothing depends on it in Mageia. Since stog is still under heavy development, it's better if we can ship the latest version. We currently have version 0.5, and the improvements in the cache system would be welcome for Mageia 3. Here is the detailed changelog: 0.7.0 [2013-02-13]: mod: split (un)install target into (un)install-lib and (un)install-bin, add: -I and -package options to stog-ocaml-session, add: new scripts mk-stog, mk-stog.byte, mk-stog-ocaml-session to create custom stog and stog-ocaml-session, add: option --stog-ocaml-session to stog, to indicate the program used to evaluate ocaml code, fix META file, add: support for authors in the RSS feed. Thanks to Gabriel Scherer, mod: use ocamlfind to compile. 0.6.1 [2013-01-17]: Fix version number META file and remove Pcre useless dependency in Makefile and META. 0.6 [2013-01-16]: mod: do not write the config file if it already exists, add: elements node handles reverse=false attribute not to reverse order of elements (which is default, i.e. the more recent first), mod: better cache system, using dependencies of each element on other elements and files; also handles the stog environment used to compute elements in cache, so that a change in the stog environment will make all elements recomputed (for example when language changes), add: a rule using a file or another element must add a dependency from the computed element to the element or file it depends on, using Stog_plug.add_dep, add: include now handles a depend=false attribute, to prevent adding a dependency of the element on the included file, add: --depcut option, used when getting cached elements, to use only one level of dependency between elements; this is useful for example in case the site has a menubar, leading to having almost all elements depending on almost all elements. Thanks, -- Malo
Re: [Mageia-dev] About bug 6676
On 20/02/13 23:25, Juan Luis Baptiste wrote: On Wed, Feb 20, 2013 at 5:11 PM, zezinholists.jjo...@free.fr wrote: http://wiki.debian.org/Games/Suggested#World_of_Padman says that game engine is open-source, so it should not go to non-free! Yeah but AFAIK the game data isn't free, that's why fedora doesn't include it and uses the autodownloader (I'll double check this) . Anyway, that's not the point here. :) it's more if everyone is okay on including the game complete wether it's on core or non free, instead of reusing the ioq3 engine. I would say that packages which autodownload non-free material should be in nonfree (like get-skype). For the same reason that free packages which Require a package in nonfree should be in nonfree. As for World of Padman, if it works well in Mageia, is redistributable, and there is someone to maintain it, I see no reason not to import it. Cheers, -- Malo
Re: [Mageia-dev] About bug 6676
On 21/02/13 12:12, Dan Fandrich wrote: On Thu, Feb 21, 2013 at 12:02:13PM +, Pierre-Malo Deniélou wrote: I would say that packages which autodownload non-free material should be in nonfree (like get-skype). For the same reason that free packages which Require a package in nonfree should be in nonfree. But what happens when free content becomes available so that the non-free download is no longer required? This is unlikely in the case of Skype, but has happened with other games engines in the past. If it becomes free, we push the newer version to the free repository. Fairly simple :-). Cheers, -- Malo
[Mageia-dev] Freeze push: rabbitmq-server 3.0.2
Dear all, Can someone push rabbitmq-server-3.0.2? 3.0.2 is a bug fix release. We have 3.0.1 currently. Thanks. -- Malo
[Mageia-dev] Freeze push: dblatex-0.3.4
Dear all, Can someone push dblatex-0.3.4? It's been out for some time (last June) and is in Fedora/Debian. The changelog is quit small: - Improve the verbatim block display to be able to scale the block width to the page width. - Improve the hyphenation of the inlined literal elements with a dblatex specific hyphenation algorithm. - Add the parameter parameterhyphenation.format/parameter to specify the inlined format types that must be hyphenated. It replaces the more limited parameter parametermonoseq.hyphenation/parameter. - Add the parameter parameterexample.float.type/parameter to give the possibility to have sgmltagexample/sgmltag elements not floating. The attribute 'floatstyle' is also taken into account. - A number of bug fixes. It builds fine and executes fine on my machine. Thanks. -- Malo
[Mageia-dev] Freeze push: googlecl-0.9.14
Dear all, Can someone push googlecl-0.9.14? It's a command line tool to interact with google services (like blogger, docs, calendar, etc.). This release is mostly bug fixes. === version 0.9.14 r550 through 621 Bugfixes: * Fixed bug in command line parsing, added message if Discovery can't be used. * Remove bogus attempt to delete credentials that broke discovery with google-api-python-client-1.0beta4. * Fixes gdata bug introduced in 2.0.15 by using the constant string referred to in all gdata versions after 2.0.4 in place of the changing variable names. * Fixes problem with uploading docs. Added resumable uploader support. Docs can now be uploaded with gdata versions 2.0.10, 2.0.12, 2.0.13 and 2.0.14. Some files (.txt, for example) can still be uploaded with versions 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, but not all file types. Better error messages for users trying to upload to Google Docs with unsupported gdata versions. * Fixes docs uploads for 2.0.15 and 2.0.16. This has been tested and works for gdata 2.0.0 through 2.0.4 as well as 2.0.12 through 2.0.16. * Thanks to jim.lawton for pointing out the rename of DocList to ResourceFeed. `google docs list` now works for me on python gdata 2.0.12-2.0.17. * Thanks Mitya57 for pointing out this bug in downloading non-translated filetypes with python gdata 2.0.15 and later. * Fixed bug in command line parsing, added message if Discovery can't be used. * Fixed interactive bug * Fixed bug with getting more than 500 blog posts. * Fixed a problem with --date parameter for creating a new calendar entry * Fixed bug with multiple empty lines when getting blogger document. Enhancements: * Added Discovery support. * Made the authorization message a little tidier and more clear. * Adding the gdata downloader and installer scripts. * Docs list, edit, upload, get all work for me now with python gdata 2.0.12 through 2.0.17. * Added info on ImportError caused by missing gdata library. * Added Discovery support * Documentation update. === Thanks. -- Malo
Re: [Mageia-dev] Status note
On 26/01/13 05:58, Joseph Wang wrote: I've been avoiding checking anything into the tree so as not to interfere with the Mageia 3 release. But I've been quite busy at working on various projects to be checked in as so as Cauldron opens up. Most of them involve somewhat more than packaging since I've been sending patches upstream The things that I've been working on are: 1) Cinnamon environment. I not only have a cinnamon environment working on my local box, but I've also created a set of packages that pull in all of the latest cinnamon themes, applets, and desklets. 2) Games: I'm tracking development for raceintospace, golly and leocad. I've also got a local package of freeorion. 3) Astronomy/Visualization: I've created packages for the top astronomy programs on sourceforge. These have either eye candy or are professional tools or both. The things that I've packaged are virtualmoonatlas, aladin, ds9 and a ton of astronomy related python scripts. I've also worked on a drop in replacement for pgplot based on plplot and a Pypi - rpm script. I also have a local package of elmerfem working. I was going to work on paraview, and there are some install issues, and I'd like to work on ds9 first. I also have mesa working so if anyone wants to simulate a star, let me know. The problem with mesa is that theorists work mainly with source, so I've been trying to figure out the best way of packaging mesa to allow for tweaking. 4) opengl for ATI: I was working a while ago trying to get the open source GPU/glamor drivers working on the newest AMD card, but that doesn't seem that useful since AMD doesn't seem interesting in this. There are some bits and pieces in my dev box that might be useful if someone else is working on this. I'm also interested in taking requests. If there is some game or astronomy related package that you'd like to get packaged let me know. Hi Joseph, Thanks for your work! May I suggest you look at the new package requests on bugzilla? https://bugs.mageia.org/buglist.cgi?cmdtype=doremremaction=runnamedcmd=new%20package%20requestsharer_id=1 There are almost 500 of them :-). Cheers, -- Malo
Re: [Mageia-dev] Status note
On 26/01/13 09:58, Kamil Rytarowski wrote: On 26.01.2013 09:55, Mustafa Muhammad wrote: PeaZip http://sourceforge.net/projects/peazip is great but it have issues with 74-bit Linux. 7-zip File Manager is also great but I think it is Windows only. Hopefully you (or anybody interested) can bring these to Linux. I am against including peazip to core/. It's unportable 32-bit Pascal code. PCLOS is packaging that as a binary blob. I agree with Kamil here. I tried to package it, but it's programmed in really unfriendly way. https://bugs.mageia.org/show_bug.cgi?id=1636 It's in svn, if anyone wants to play with it, but I won't spent more time on it. Cheers, -- Malo
Re: [Mageia-dev] Freeze push: texstudio 2.5.2
Le 20/01/13 20:12,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 17/01/13 15:21,Pierre-Malo Deniélou nous adresse ces quelques mots : On 16/01/13 00:45, Pierre-Malo Deniélou wrote: Please push texstudio, which I updated to version 2.5.2. Upstream says that it is a bug fix release. ping? I forgot to copy-paste the changelog: · new %BEGIN_FOLD ... %END_FOLD comment to mark arbitrary regions as foldable · add support to display CJK and Cyrillic in PDF viewer · increased maximum possible tab width to 32 · fix basic input method support · fix crash when saving as an already open file · fix viewer might change size because of long status messages · changed shortcuts for next/prev document to Ctrl+PgDown/Up · several small corrections ping? It does not affect any other package and fixes some internationalisation related issues. ping? -- Malo
Re: [Mageia-dev] Freeze push: texstudio 2.5.2
Le 17/01/13 15:21,Pierre-Malo Deniélou nous adresse ces quelques mots : On 16/01/13 00:45, Pierre-Malo Deniélou wrote: Please push texstudio, which I updated to version 2.5.2. Upstream says that it is a bug fix release. ping? I forgot to copy-paste the changelog: · new %BEGIN_FOLD ... %END_FOLD comment to mark arbitrary regions as foldable · add support to display CJK and Cyrillic in PDF viewer · increased maximum possible tab width to 32 · fix basic input method support · fix crash when saving as an already open file · fix viewer might change size because of long status messages · changed shortcuts for next/prev document to Ctrl+PgDown/Up · several small corrections ping? It does not affect any other package and fixes some internationalisation related issues. -- Malo
[Mageia-dev] [RPM Groups] Final Final change for Mageia 3
Dear Packagers, I lay before you a last (I promise) change for the rpm groups. It affect packages currently in System, and it is done so that there is no cost in terms of new strings (since we are in freeze). - System/Configuration/Boot and Init renamed as System/Boot and Init - System/Configuration/Hardware disappears - System/Configuration/Networking renamed as System/Networking - System/Configuration/Other disappears - System/Configuration/Packaging renamed as System/Packaging - System/Configuration/Printing disappears For the groups that are disappearing, the packages can be easily spread among the System subgroups: - System/Base - System/Boot and Init - System/Cluster - System/Configuration - System/Fonts - System/Internationalization - System/Kernel and hardware - System/Libraries - System/Networking - System/Packaging - System/Printing - System/Servers - System/X11 I remind you that the policy is at: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups Thanks a lot ! -- Malo
Re: [Mageia-dev] Freeze push: texstudio 2.5.2
On 16/01/13 00:45, Pierre-Malo Deniélou wrote: Please push texstudio, which I updated to version 2.5.2. Upstream says that it is a bug fix release. ping? I forgot to copy-paste the changelog: · new %BEGIN_FOLD ... %END_FOLD comment to mark arbitrary regions as foldable · add support to display CJK and Cyrillic in PDF viewer · increased maximum possible tab width to 32 · fix basic input method support · fix crash when saving as an already open file · fix viewer might change size because of long status messages · changed shortcuts for next/prev document to Ctrl+PgDown/Up · several small corrections -- Malo
Re: [Mageia-dev] Package Group Selection in Install borked ?
On 16/01/13 14:27, Frank Griffin wrote: I seem to remember a bug report go by which had something to do with not offering package groups during Package Selection that aren't actually on the install media, and that Thierry reported it fixed. That may be related to what I'm seeing. I just tried a fresh network install against a local copy of cauldron that was just synced, and when I choose Custom Desktop and get to Package Group Selection, the only groups shown under Workstation are Game Station, Internet Station, Console Tools, Multimedia Statio, Configuration, and Documentation. Under Server, there is only Firewall/Router. Under Graphical Environment, there is only LXDE Desktop and Other Graphical Desktops. Any idea what's goin on ? I don't think the other categories got wrapped into these, because checking them all only gives me a total size of 4864 instead of the usual 8000-9000 value. It is probably linked to the RPM group change. Sorry. I can patch http://svnweb.mageia.org/soft/rpmdrake/trunk/Rpmdrake/icon.pm?revision=6429view=markup if tv does not beat me to it. Best, -- Malo
Re: [Mageia-dev] Package Group Selection in Install borked ?
On 16/01/13 15:05, Frank Griffin wrote: On 01/16/2013 09:51 AM, Pierre-Malo Deniélou wrote: It is probably linked to the RPM group change. Sorry. I can patch http://svnweb.mageia.org/soft/rpmdrake/trunk/Rpmdrake/icon.pm?revision=6429view=markup if tv does not beat me to it. Best, OK, can you let me know what new package(s) to look for when I rsync ? Well, it'll be in a new rpmdrake and maybe new installer, because there is more than just the file mentioned above to modify. Best, -- Malo
[Mageia-dev] Freeze push: texstudio 2.5.2
Please push texstudio, which I updated to version 2.5.2. Upstream says that it is a bug fix release. -- Malo
[Mageia-dev] Freeze push: sir 2.5.1
Please push sir, which I updated to version 2.5.1. I has some bug fixes and a few new features that we want and that are not too risky to put in for Mageia 3 (since nothing depends on sir). I tested the install and usability. Complete Changelog: - relative path bug-fix - project moved to CMake - Conditional compilation: disable or enable metadata support - Settings and DetailsBrowser classes added - Image width and height line edit replaced by spin box - faster selection using Exiv2 image size detection if it’s available - bugfix: delete selected items from list in ConvertDialog - now delete all selected items - shared data manipulation methods moved to SharedInformation; - save and enabled fields in MetadataUtils::Metadata removed - now used Settings fields - DetailsOptions namespace moved to separated file - widgets moved to separated directory - option and selection dialogs splited to few widgets for more flexibility - remove temporary files at end of session - width of SVG images render in DetailsBrowser patch - drop event improved - myQTreeWidget renamed to TreeWidget, some code moved from ConvertDialog - external columns into tree view like size (px,K/MiB) added - new options group box “File list” and header view context menu for TreeWidget settings - converting from SVG bug when dest size is more than default size fixed - keep aspect ratio added to settings - English translation added, Polish translation updated - many files moved from resource file to another files -- Malo
[Mageia-dev] freeze-push: ocaml-pgocaml
Currently we have version 1.7. Today was released a bug-fix-only release 1.7.1. Please push it. -- Malo
[Mageia-dev] [RPM Groups] Final change for Mageia 3 done
Dear Packagers, As a final amendment to the RPM group policy for Mageia 3, the following changes were made yesterday: - creation of Games/Simulation - Graphics/Editors renamed as Graphics/Editors and Converters - Graphics/Other renamed as Graphics/Utilities - Office/Other renamed as Office/Utilities - removal of Sound/Visualization - creation of Video/Television The renames will be handled by scripts, so do not worry about them. However, feel free to use the two new groups: Games/Simulation and Video/Television. I remind you that the policy is at: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups Thanks a lot ! -- Malo
Re: [Mageia-dev] problem with %_smp_mflags in Cauldron
Le 06/01/13 13:19,philippe makowski nous adresse ces quelques mots :
Hi,
I have a build fail in Cauldron
(http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/log/python-cairo-1.10.0-3.mga3.src.rpm/build.0.20130104032637.log)
because %python3_waf is resolved as /usr/bin/waf-3.3 build -l12 -j12
and I don't understand why
we have in /etc/rpm/macros.d/waf-python3.macros :
%python3_waf %__python3_waf build %_smp_mflags
and
%__python3_waf%{_bindir}/waf-%{python3_version}
so why getting /usr/bin/waf-3.3 build -l12 -j12
instead of /usr/bin/waf-3.3 build -j12
from where come this -l that is not supported by waf (waf-3.3: error:
no such option: -l)
I believe the answer is in how the autobuild is done:
http://fasmz.org/~pterjan/blog/?date=20130103#p01
The parameters are not exactly the same as the ones on the build system.
Cheers,
--
Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 2 (Reposted in new thread)
Le 06/01/13 16:21,Barry Jackson nous adresse ces quelques mots : On 05/01/13 22:48, Pierre-Malo Deniélou wrote: Any remarks? Suggestions? Cheers, I have been plodding along updating what I can, but it's slow as many need patching to fix build failures. Yes, thanks a lot! Also there are many KDE packages which I have avoided touching, as KDE maintainers tend to get upset when packages are interfered with. Could some process be adopted where KDE packages may be updated and a nominated KDE reviewer be notified to push them and help speed things up a bit? I think for KDE devs, if you just tell them beforehand what you want to do, then they can just tell you to go ahead. I think they don't like if you just modify without telling them first, as they seem to use svn to plan ahead quite regularly, and you better not submit the packages yourself since the version in svn is usually ahead of cauldron. They told me for example that I can go ahead and change in svn the groups of several kde games packages (although I haven't got to do that yet, but maybe you can have a go if you want). KDE devs are touchy because they need a lot of planning and sync to be able to serve us the various RC on the day they are released ;-). Cheers, -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 2 (Reposted in new thread)
Le 05/01/13 22:48,Pierre-Malo Deniélou nous adresse ces quelques mots : Last but not least, it has been reported that some of the groups were not adapted, therefore slowing down the movement, since no one knows where to put the packages. I'm taking notes about possible minor changes that could be implemented quickly (through simple scripting): - creation of Games/Simulation - Graphics/Editors renamed as Graphics/Editors and Converters - Graphics/Other renamed as Graphics/Utilities - Office/Other renamed as Office/Utilities - creation of Sound/Composition - removal of Sound/Visualisation - creation of Video/Television I think it's a bit too late to do that before Beta 2 (although since these changes do not affect anything but the presentation in rpmdrake, it's safe to do it at any time), but I wish to hear other possible suggestions (someone suggested to have a System/Sound for sound systems, like alsa or pulseaudio). Any remarks? Suggestions? After discussion on IRC, it seems Sound/Composition is not necessary and would conflict with Midi a lot. Other opinions? Cheers, -- Malo
Re: [Mageia-dev] RPM group change before Beta 2
Le 06/01/13 23:09,Joseph Wang nous adresse ces quelques mots : A lot of the packages seem to be broken because AM_CONFIG_HEADER(config.h) needs to be replaced with AC_CONFIG_HEADERS([config.h]) 1) I can go through and put in a sed command in the specs that does the conversion, and e-mail the maintainers. If I check in a change into the mgarepo does the build happen automatically or is some other intervention needed? 2) If we do this, is there a fast way of doing a grep of the logs to see what packages are failing because of this issue? It seems to be affecting a lot of packages. Hi Joseph, Everyone is aware, and many people (esp. cjw) have been patching the configure.ac files. Maybe you should follow what is going on at http://pkgsubmit.mageia.org/ or subscribe to the changelog mailing-list (which tells you of every package that is updated on Mageia): that will tell you what people are currently doing :-). Cheers, -- Malo BTW the subject of the mail is wrong.
Re: [Mageia-dev] RPM group change before Beta 2
Le 06/01/13 23:22,Joseph Wang nous adresse ces quelques mots : Sure thing. I can start patching some of the rpms that aren't haven't been done yet. However, I was wondering if I can do that with just subversion commit privileges or do I need to be able to submit build requests to do this? To patch, you do not need to submit. But it's good practice to contact the maintainer when you do that: IRC is a fast way to do that. Cheers, -- Malo
Re: [Mageia-dev] Packages backlog
Le 06/01/13 23:03,Joseph Wang nous adresse ces quelques mots : [...] vstar I just looked at vstar. I have several remarks or comments: - there is a typo in the URL - Usually it's better not to have a weird downloading script in SOURCES for svn revisions, but to put it as a comment in the SPEC file. - BTW, why can't you use the stable version instead of the svn release? There is a very recent one at http://sourceforge.net/projects/vstar/files/2.14.2/ If you use that one, you can just put as Source0 the sourceforge URL to the archive - your desktop file does not mention an icon, which makes for an blank entry in the menu. If you fix these things, I happy to submit it. Cheers, -- Malo
Re: [Mageia-dev] Packages backlog
Le 06/01/13 23:03,Joseph Wang nous adresse ces quelques mots : [...] nightfall I just submitted nightfall, but it'll probably fail due to missing BuildRequires. Please fix. Cheers, -- Malo
Re: [Mageia-dev] Packages backlog
Le 06/01/13 23:03,Joseph Wang nous adresse ces quelques mots : There's a backlog of about 32 packages that I've packaged, but haven't been built since I don't have build privileges, and I'm adding new packages at the rate of five or six a week. I was wondering what can be done to reduce that backlog. If necessary, we can wait until after the release to add them, but there are some packages (mostly games like raceintospace or nice eye candy like virtualmoon) that might be worth getting into Mageia 3. quantlib gretl python-pyp2rpm leocad leocad-data python-cgen python-codepy python-opencl python-opengl-demo python-pip python-py python-test python-tools nightfall vstar python-h5py cython python-yt vassal virtualmoon virtualmoon-data python-flexmock python-atpy python-aplpy python-cosmocalc python-voeventlib raceintospace cinnamon (update, not for mageia 3) plplot (update) golly aladin vtk Finally, I saw that several of these packages were imported from Fedora. That's great, but it's good practice to clean a bit the spec of these packages after import. We have some slightly different policy (like no %clean section, ... etc). Thanks for your packages, -- Malo
[Mageia-dev] Revert ghc to previous stable version
Dear all, I pushed ghc-7.6.1 a bit too soon, and I know realise that having the stable 7.4.2 version is better for Mageia 3. Can the sysadm team remove ghc-7.6.1, ghc-doc-7.6.1 and ghc-prof-7.6.1 from the mirrors and replace it with the mga2 version (7.0.4)? I will then revert the svn and update to 7.4.2. Thanks, -- Malo
[Mageia-dev] [RPM Groups] RPM group change before Beta 2
Dear packagers, A lot of progress has happened on the RPM group move. Thanks a lot. However there is still a bit to do before the release happens. The main categories that need still to be changed are: Obsolete group | number of remaining packages Books/Computer books 2 Books/Howtos 2 Books/Other26 Graphics 116 Office 86 Sound 104 Video 224 Total = 560 (which represents only 18% of the packages that had to change group: the 81% have already been dealt with. Yeah us!) For these 560 packages, it is mostly about sending them to the different subgroups mentioned in the policy: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups However, several hundreds of these packages have not been moved because they do not build. So it's the opportunity to look at the rebuild effort that pterjan started at http://pkgsubmit.mageia.org/autobuild/ Last but not least, it has been reported that some of the groups were not adapted, therefore slowing down the movement, since no one knows where to put the packages. I'm taking notes about possible minor changes that could be implemented quickly (through simple scripting): - creation of Games/Simulation - Graphics/Editors renamed as Graphics/Editors and Converters - Graphics/Other renamed as Graphics/Utilities - Office/Other renamed as Office/Utilities - creation of Sound/Composition - removal of Sound/Visualisation - creation of Video/Television I think it's a bit too late to do that before Beta 2 (although since these changes do not affect anything but the presentation in rpmdrake, it's safe to do it at any time), but I wish to hear other possible suggestions (someone suggested to have a System/Sound for sound systems, like alsa or pulseaudio). Any remarks? Suggestions? Cheers, -- Malo
[Mageia-dev] [RPM Groups] RPM group change before Beta 2 (Reposted in new thread)
(Reposted in new thread, sorry) Dear packagers, A lot of progress has happened on the RPM group move. Thanks a lot. However there is still a bit to do before the release happens. The main categories that need still to be changed are: Obsolete group | number of remaining packages Books/Computer books 2 Books/Howtos 2 Books/Other26 Graphics 116 Office 86 Sound 104 Video 224 Total = 560 (which represents only 18% of the packages that had to change group: the 81% have already been dealt with. Yeah us!) For these 560 packages, it is mostly about sending them to the different subgroups mentioned in the policy: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups However, several hundreds of these packages have not been moved because they do not build. So it's the opportunity to look at the rebuild effort that pterjan started at http://pkgsubmit.mageia.org/autobuild/ Last but not least, it has been reported that some of the groups were not adapted, therefore slowing down the movement, since no one knows where to put the packages. I'm taking notes about possible minor changes that could be implemented quickly (through simple scripting): - creation of Games/Simulation - Graphics/Editors renamed as Graphics/Editors and Converters - Graphics/Other renamed as Graphics/Utilities - Office/Other renamed as Office/Utilities - creation of Sound/Composition - removal of Sound/Visualisation - creation of Video/Television I think it's a bit too late to do that before Beta 2 (although since these changes do not affect anything but the presentation in rpmdrake, it's safe to do it at any time), but I wish to hear other possible suggestions (someone suggested to have a System/Sound for sound systems, like alsa or pulseaudio). Any remarks? Suggestions? Cheers, -- Malo
Re: [Mageia-dev] Rebuild failed on i586 for @334667:drakx-installer-stage2-15.15-1.mga3.src.rpm
On 26/12/12 02:14, Pascal Terjan wrote: On Tue, Dec 25, 2012 at 2:28 PM, Christiaan Welvaart c...@daneel.dyndns.org wrote: Maybe the problem is that ghc provides libffi.so.6()(64bit) so it gets selected instead of lib64ffi6. I fixed ghc package by making it use system libffi (patches from fedora) as this was breaking other packages Sorry about that, the ghc package got submitted a bit too soon and without much testing ... (and I'm not so sure that this version is the appropriate one to use) Any help with Haskell is welcome by the way :-) Cheers, -- Malo
Re: [Mageia-dev] Python packaging policy
On 13/12/12 06:53, Joseph Wang wrote:
Looking over this page:
https://wiki.mageia.org/en/Python_policy
* I'd like to add a rule (which is followed by current packages) that
the prefix py should
generally be removed from a package name. For example pyopencl should be called
python-opencl. This is the current convention for packages in mageia.
I think it's too strong. There will necessarily be exceptions, like pypes.
For the package names, I can give you my experience as ocaml packager.
Our policy is roughly the same as for python:
- executables keep their upstream names (ex. js_of_ocaml, camlp5, ...)
- libraries take the 'ocaml-' prefix followed by the upstream name as
much as possible (since these upstream names are known). It leads to
packages like ocaml-ocamlgraph or ocaml-ocamlnet since ocamlgraph and
ocamlnet are well-known libs in the community. However when the library
is just a wrapper for a well-known C library, we drop extra ocaml
prefixes or suffixes (ex: upstream sqlite3-ocaml becomes ocaml-sqlite3).
So overall, no policy should be too strict: the need for uniformity
should not make it too hard for users!
* Also for grouping. I'd like to add a rule that Development/Python
is intended for packages
which provide general development libraries for python, and if the
library fits into an obvious
other category (i.e. python routines for cosmology calculations) those
should go into the
other category.
I don't really agree. The current group policy is the following:
- if it's an application/data - in the corresponding group.
- if it's a library for development - in Development/%{the language}.
- if it's a library not meant for anyone to install independently
- in System/Libraries.
I'm not sure users would find a benefit to have python for cosmology in
the Astronomy section and python for Maths in the Maths section and so on.
What I would encourage you to do however is to create a cosmology wiki
page that describes all the cosmology-features of Mageia.
Best,
--
Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
On 07/12/12 00:29, Johnny A. Solbu wrote: On Thursday 6. December 2012 22.51, Pierre-Malo Deniélou wrote: Today, the number of remaining packages is 749. Thanks. How do you get that number? Is it a process we can use to check our own packages? What about incorporating something like this on check.mageia.org? You can have a look in rpmdrake, or here: http://mageia.madb.org/group/list/release/cauldron Cheers, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release CardManager-1-3.mga3
Le 07/12/12 22:27,dmorgan nous adresse ces quelques mots : Name: CardManager Relocations: (not relocatable) Version : 1 Vendor: Mageia.Org Release : 3.mga3Build Date: Fri Dec 7 23:27:14 2012 Install Date: (not installed) Build Host: jonund.mageia.org Group : Development/Java Source RPM: (none) Size: 306150 License: BSD Signature : (none) Packager: dmorgan dmorgan URL : http://cardmanager.wz.cz/ Summary : Java application to allows you to play any, especially collectible, card game Description : This is free, open source multiplatform (java) application which allows you to play ANY card game. The game is designed especially to play collectible card games like Magic the Gathering or Doomtrooper over network. To play those games you need to own (scanned) images of card, which are not part of this package. Some can be easily downloadable from internet, but be aware of copyrights. The default deck and background is free of copyright Also please feel free to add your own backgrounds to ~/CardManager/data/backgrounds and of course enhance collection under ~/CardManager/collection dmorgan dmorgan 1-3.mga3: + Revision: 327971 - Build with java 7 Maybe in Games/Cards instead, no? Cheers, -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 03/12/12 22:49,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 02/12/12 13:40,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 01/12/12 02:30,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 29/11/12 11:04,Malo nous adresse ces quelques mots : On 27/11/12 23:02, Pierre-Malo Deniélou wrote: Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! This morning, 1182 are left. Tonight, only 1103 remain, thanks notably to Olav. Let's pass under 1000 by tomorrow night! Thanks to the effort of many, the number of remaining packages is now of 972. Many remain in Video. Today's number is 847. It looks good, but still many in Office or Video need to move. Keep at it!! Today, the number of remaining packages is 749. Thanks. A little more effort is required! If you have packages in Graphics or Office, please move them to the appropriate subgroup. Thanks! -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 02/12/12 13:40,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 01/12/12 02:30,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 29/11/12 11:04,Malo nous adresse ces quelques mots : On 27/11/12 23:02, Pierre-Malo Deniélou wrote: Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! This morning, 1182 are left. Tonight, only 1103 remain, thanks notably to Olav. Let's pass under 1000 by tomorrow night! Thanks to the effort of many, the number of remaining packages is now of 972. Many remain in Video. Today's number is 847. It looks good, but still many in Office or Video need to move. Keep at it!! Thanks a lot for your help, -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 01/12/12 02:30,Pierre-Malo Deniélou nous adresse ces quelques mots : Le 29/11/12 11:04,Malo nous adresse ces quelques mots : On 27/11/12 23:02, Pierre-Malo Deniélou wrote: Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! This morning, 1182 are left. Tonight, only 1103 remain, thanks notably to Olav. Let's pass under 1000 by tomorrow night! Thanks to the effort of many, the number of remaining packages is now of 972. Many remain in Video. Please keep fixing! Thanks! -- Malo
Re: [Mageia-dev] Mageia 1 EOL.
Le 02/12/12 14:23,Stan Thomas nous adresse ces quelques mots : I'd be interested in doing some backports to Mageia 1 to keep it going a little longer; Firefox and Thunderbird would be my main focus. I've always thought I should learn how to build packages for a Linux distro. Are there any documents you can point me at? Anyone want to mentor me for this? Not for this, but if you want to work on Mageia 3, or on QA for Mageia 2, please join! https://wiki.mageia.org/en/Becoming_a_Mageia_Packager https://wiki.mageia.org/en/QA_Team -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 29/11/12 11:04,Malo nous adresse ces quelques mots : On 27/11/12 23:02, Pierre-Malo Deniélou wrote: Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! This morning, 1182 are left. Tonight, only 1103 remain, thanks notably to Olav. Let's pass under 1000 by tomorrow night! Cheers, -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
On 27/11/12 23:02, Pierre-Malo Deniélou wrote: Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! This morning, 1182 are left. Keep it going! Reminder: packages in Books/Computer books 15 Books/Howtos 2 Books/Other26 Graphics 276 Office 122 Sound 313 Video 428 should be changed to new groups. -- Malo
Re: [Mageia-dev] cauldron state, and dependencies handling
Le 28/11/12 21:17,Florent Monnier nous adresse ces quelques mots : 2012/11/28, Thierry Vignaud thierry.vign...@gmail.com: On 28 November 2012 21:35, Florent Monnier monnier.flor...@gmail.com wrote: but maybe rpm is my friend and I'm just not aware of it. Is there an rpm command line option to get the list of the dependents of a given lib? eg for glibc-devel: urpmf --requires glibc-devel Now you may have to look for 'pkgconfig(foobar)' too. eg: urpmf --requires --literal 'pkgconfig(glibc)' It seems it don't work for ocaml libs, there's not xtmpl in the results: $ urpmf --requires ocaml-xmlm ocaml-xmlm-devel:ocaml-xmlm[== 1.0.2-1.mga2] ocaml-xmlm:ocaml $ urpmf --requires --literal 'pkgconfig(ocaml-xmlm)' (Those in BuildRequire, not only Require) just add and enable source media prior to running above commands. could you give a wiki link that explains how to do this? with a search I found: urpmi.update --no-ignore Core Updates Testing but nothing with the name Sources in it. But I think it's just better to look at what actually use those libs (if not statically linked), aka for LLVM: urpmf --requires libLLVM-3.1.so urpmf --requires /usr/lib/ocaml/xmlm/* no xtmpl in the answer too You need to define a Source media for the SRPMS, then urpmf --requires ocaml --media Source would give you all packages with ocaml as BuildRequires -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 27/11/12 10:01,Olav Vitters nous adresse ces quelques mots : On Tue, Nov 27, 2012 at 04:58:19AM +0100, Remco Rijnders wrote: It would help if you have / could share a breakdown of the above, perhaps both per package and maintainer? Added such a command to mga-gnome script: mga-gnome group-owner Books/Computer books Books/Howtos \ Books/Other Graphics Office Sound Video See attached for the output. Output is per group, then on 1 line: owner / source package / (sub)packages Thanks Olav!!! :-) -- Malo
Re: [Mageia-dev] [ANN] [RFC] support for deltarpms in urpmi
On 27/11/12 21:56, zezinho wrote: - having urpmi select the right package o either deltarpm if there's one for installed_version - update_version path o or regular update package else Well, we should not provide both, or delta rpm is useless It's not useless, as it still limits the amount to be downloaded in most cases. It increases slightly the mirror size though. -- Malo
Re: [Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Le 26/11/12 17:34,Malo nous adresse ces quelques mots : Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Dear packagers, Some progress has happened on the RPM group move. Thanks a lot. However there is still a lot to do before the Beta 1 and the mass-rebuild. The main categories that need still to be changed are: Obsolete group | number of remaining packages Books/Computer books 21 Books/Howtos 2 Books/Other26 Graphics 296 Office 134 Sound 419 Video 440 Total = 1338 Today, 1273 remains to be changed. Thanks! Keep up the good work! -- Malo
Re: [Mageia-dev] Mageia-dev Digest, Vol 27, Issue 85
On 26/11/12 14:49, Joseph Wang wrote: I really don't think that cinnamon is ready for Mageia 3. There are some pretty major bugs in it, and it's not ready for prime time. It would be useful to keep it in the testing section, and then target it for Mageia 4. I do think it would be a good idea to at least start looking at alternatives to Gnome 3 since they are self-destructing, and I've been *extremely* impressed by cinnamon (minus two annoying bugs which I'm trying to fix). If you didn't know, it's pretty much the exact thing that was decided for Mageia: cinnamon is not ready yet. But submiting it to cauldron would include it in Mageia 3. Maybe for Mageia 4? Your work is nice and much appreciated. And I'd love to see more astrophysics packages in Mageia. It'd be great it you would come on IRC (at any time) and to the packager meetings on Tuesdays. That'd help with communication, because overall we're a bunch of nice people ;-). -- Malo
[Mageia-dev] [RPM Groups] Dealing with Books/*
Dear packagers, Some progress has happened on the RPM group move. Thanks a lot. However there is still a lot to do before the Beta 1 and the mass-rebuild. The main categories that need still to be changed are: Obsolete group | number of remaining packages Books/Computer books 21 Books/Howtos 2 Books/Other26 Graphics 296 Office 134 Sound 419 Video 440 Total = 1338 With more than 1338 packages left, and less than 100 maintainers, that means that everyone probably has several packages to fix :-P. For these packages, it is mostly about sending them to the different subgroups mentioned in the policy: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups I'll send more regular updates on the progress of this task. Meanwhile, please please fix! Thanks! -- Malo
[Mageia-dev] [RPM Groups] RPM group change before Beta 1 (fixed title)
Sorry for the wrong title ... On 26/11/12 17:30, Pierre-Malo Deniélou wrote: Dear packagers, Some progress has happened on the RPM group move. Thanks a lot. However there is still a lot to do before the Beta 1 and the mass-rebuild. The main categories that need still to be changed are: Obsolete group | number of remaining packages Books/Computer books 21 Books/Howtos 2 Books/Other26 Graphics 296 Office 134 Sound 419 Video 440 Total = 1338 With more than 1338 packages left, and less than 100 maintainers, that means that everyone probably has several packages to fix :-P. For these packages, it is mostly about sending them to the different subgroups mentioned in the policy: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups I'll send more regular updates on the progress of this task. Meanwhile, please please fix! Thanks! -- Malo
Re: [Mageia-dev] rabbitmq-server build failure
Le 25/11/12 16:04,Colin Guthrie nous adresse ces quelques mots : CC'ing maintainer Hi, Just fixing packaging for the above package and it fails to build. It tries to do various things with git to clone remote repos etc. (which won't work on the BS) which may b e to bplame. Either way, this needs fixed somehow. I added netcat as a BR as that seemed the first error (tho' was ringing alarm bells already), so it should perhaps be reverted if it was a red-herring. http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20121125155106.colin.valstar.5836/log/rabbitmq-server-2.8.5-2.mga3/build.0.20121125155203.log Hi Colin, Yes, I'm aware of that error. It was because of some strange version of eldap that they used. At that time, there was no obvious solution, so I just waited a bit. I'm just a bit swamped right now (until the end of next week) to fix it yet ... I'll try my best to fix it before beta 1 though. Cheers, -- Malo
Re: [Mageia-dev] On new rpm group
Le 15/11/12 22:47,Barry Jackson nous adresse ces quelques mots : On 15/11/12 22:10, Reinout van Schouwen wrote: Funda Wang schreef op vr 09-11-2012 om 16:50 [+0800]: Hello, I noticed that there are two rpm group named 'Geography' and 'Sciences/Geosciences'. Are there any differences? It would appear to me that geography is more concerned with the names and locations of places whereas geosciences is the quest for knowledge of the Earth's composition, rock layers, sediments etcetera. regards, I think the geosciences group was aimed at satnav, gps and mapping for example but I may be wrong - I recall some discussion on irc. That's the opposite ... Geography is for the satnav, gps and mapping softs, while Geoscience are for all geology, climate, oceanography related software. Cheers. -- Malo
Re: [Mageia-dev] rehashing the faac issue
On 30/10/12 07:58, andre999 wrote: Personnally, I would favour putting tainted or nonfree (or rather an abbreviated form, say [nf] or [tnt]) at the end of the main part of the package name. It's already the case ... nvidia-current-kernel-3.6.4-desktop-1.mga3-304.60-2.mga3.nonfree.x86_64.rpm -- Malo
Re: [Mageia-dev] rehashing the faac issue
On 30/10/12 08:20, Guillaume Rousse wrote: Le 30/10/2012 01:34, Frank Griffin a écrit : On 10/29/2012 06:20 PM, Olivier Blin wrote: I would prefer B: adding a nonfree-tainted repo (+ its updates/testing/backports/debug brothers). See https://bugs.mageia.org/show_bug.cgi?id=2833 for a list of packages needing faac. Yes, that's overkill, it will clutter the urpmi media config UI, but that's the only clean way we have. I guess a simple way to unclutter the drakrpm-edit-media UI would be to add a drop-down menu to select between Release + Updates (default and most commonly used media), Updates Testing, Backports (whenever it gets in), and Debug (for debug packages of all aforementioned groups). I don't know what's involved in this, but it is certainly the optimal solution. Creating a specific workflow (a new buildsystem queue, a new entry in package manager configuration, etc...) for a category of packages with a unique candidate is not precisely something I'd call 'optimal'. Unless in term of complexity. Morevoer, unless someone volonteers to actually implement it in our buildsystem, that's a purely hypothetical solution. I'd have to go with Guillaume on that one. The inclusion of faac came up a long time ago, and the simple logical answer is to created a tainted-non-free repos. However, the three problems with that solution are: - there is only a handful of people at Mageia who can do that, and none of them actually did it. - there is only faac, so why bother? (fuelling the first reason) - the reason that philippe mentioned: is having 3 versions of each multimedia package really worth it? ... Cheers, -- Malo
Re: [Mageia-dev] rehashing the faac issue
On 29/10/12 21:34, AL13N wrote: D. Change the definition of the Nonfree repository to open it to tainted software. No, because, as far as I understand, tainted might mean illegal in some countries, while non-free is legal everywhere (as it's redistributable). -- Malo
Re: [Mageia-dev] Fw: Changes in Categories in the XDG Desktop Menu Specification
Le 27/10/12 13:56,Jani Välimaa nous adresse ces quelques mots : Another FYI. I guess this one is more important. Thanks for the forward. How do we update our tools? I know youri checks the desktop categories on upload. I guess this is interesting as well in the context of the RPM group change. Cheers, -- Malo Begin forwarded message: Date: Wed, 24 Oct 2012 15:04:47 +0200 From: Stanislav Brabec sbra...@suse.cz To: x...@lists.freedesktop.org Cc: distributor-l...@gnome.org Subject: Changes in Categories in the XDG Desktop Menu Specification Hallo. I am pleased to announce changes in Categories in the Desktop Menu Specification[1] that incorporated changes and proposals collected in last years in XDG list or Bugzilla. Please update your utilities and distribution menus to accept these new Categories. [1] http://specifications.freedesktop.org/menu-spec/menu-spec-latest.html#main-category-registry List of changes that affect applications menu: 1) Science is now Main Category, not Additional Category. Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20186 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64034 If you had a common Edutainment menu, it could be now split to Education and Science. 2) Allowed Main Categories changed: 2.1) Science: All items allowed for Education before are now accepted for Science as well. Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20186 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64036 2.2) Monitor: Monitor is now accepted for System or Network. It was only System before. Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=49699 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64044 3) There are several new Additional Categories: 3.1) Spirituality: Religious and spiritual software, theology; allowed Main Categories: Education;Science;Utility;Game Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20192 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64038 3.2) Humanities: Software for philosophy, psychology and other humanities; allowed Main Categories: Education;Science Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20192 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64038 3.3) Maps: Sofware for viewing maps, navigation, mapping, GPS; allowed Main Categories: Graphics;Utility;Education;Science Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20187 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64042 3.4) Feed: RSS, podcast and other subscription based contents; allowed Main Categories: Network Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20197 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64045 3.5) NetworkService: A generic network service not listed elsewhere; allowed Main Categories: Network Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=20197 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64045 3.6) Shooter: Shooter game; allowed Main Categories: Game Bugzilla reference: https://bugs.freedesktop.org/show_bug.cgi?id=38553 Specification Patch: https://bugs.freedesktop.org/attachment.cgi?id=64043
Re: [Mageia-dev] rehashing the faac issue
Le 26/10/12 17:47,PhilippeDidier nous adresse ces quelques mots : Guillaume Rousse a écrit : unfortunately ... three weeks after the last post on this thread a long silence and there is nothing new in Mageia.. Sorry Philippe that we are not quick enough for you ... The packager team is overworked and short of people, so everyone prioritises their own work over minor issues like faac (although Guillaume is about so solve that issue soon). If you'd like to help, please join the packager team, we need help with maintaining the thousands of packages that are in Mageia and help in developing a great Mageia 3. -- Malo
Re: [Mageia-dev] Asia-Pacific packager newbie needs mentor
On 24/10/12 15:52, Joseph Wang wrote: Hi all, I have a number of packages that are ready to be reviewed for addition to cauldron, and I'd like to get a mentor to review them. The main problem is that I'm in Asia so it's going to be difficult for me to attend the IRC meeting at 3 a.m. :-( :-( Hi Joseph, Thanks for hanging around even if no one volunteered yet for being your mentor. So I'm looking to see how I can get a mentor. If there is some other time in which the IRC has people on it, I can meet then, or if someone can send me a personal e-mail letting me know where to upload things. IRC has people in it all the time. Mageia has contributors from all around the world, although there is more activity when it's the day in Europe. We have some people in Asia that can potentially mentor you. Otherwise, please hang around #mageia-mentoring and ping me there. I'm quite busy these days, and not really in your time zone. But if you come on IRC #mageia-mentoring during your afternoon/evening, we can start chatting a bit, and maybe review a couple of packages before finding you an official mentor, ok? (Note that this official mentor can be me from mid-November, when I have a bit more time) If other potential apprentices read that, please follow the same idea: come to the #mageia-mentoring channel and say hi to me or other random people in order to get you started. There is no point just waiting. Cheers, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release grsync-1.2.2-1.mga3
On 24/10/12 16:27, wally wrote: Name: grsync Relocations: (not relocatable) Version : 1.2.2 Vendor: Mageia.Org Release : 1.mga3Build Date: Wed Oct 24 17:25:12 2012 Install Date: (not installed) Build Host: jonund.mageia.org Group : File toolsSource RPM: (none) Size: 312202 License: GPLv2 Signature : (none) Packager: wallywally URL : http://www.opbyte.it/grsync/ Summary : A GTK GUI for rsync Description : Grsync is a GUI for rsync, the command line directory synchronization tool. While it can work with remote hosts, its focus is to synchronize local directories. wallywally 1.2.2-1.mga3: + Revision: 309669 - new version 1.2.2 Please change the group to Networking/File transfer, where rsync is. Thanks, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release bison-2.6.3-1.mga3
On 23/10/12 03:10, fwang wrote: Name: bisonRelocations: (not relocatable) Version : 2.6.3 Vendor: Mageia.Org Release : 1.mga3Build Date: Tue Oct 23 04:00:15 2012 Install Date: (not installed) Build Host: jonund.mageia.org Group : Development/Other Source RPM: (none) It should probably be either in Development/C or Development/Tools (if it's not C-specific). Development/Other should be for other programming languages. Size: 1747896 License: GPL Signature : (none) Packager: fwang fwang URL : http://www.gnu.org/software/bison/bison.html Summary : A GNU general-purpose parser generator Description : Bison is a general purpose parser generator which converts a grammar description for an LALR context-free grammar into a C program to parse that grammar. Bison can be used to develop a wide range of language parsers, from ones used in simple desk calculators to complex programming languages. Bison is upwardly compatible with Yacc, so any correctly written Yacc grammar should work with Bison without any changes. If you know Yacc, you shouldn't have any trouble using Bison (but you do need to be very proficient in C programming to be able to use Bison). Many programs use Bison as part of their build process. Bison is only needed on systems that are used for development. If your system will be used for C development, you should install Bison since it is used to build many C programs. fwang fwang 2.6.3-1.mga3: + Revision: 309399 - new version 2.6.3 Thanks, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kwallet-4.9.2-1.mga3
On 22/10/12 06:31, Nicolas Lécureuil wrote: That used to happen on release installs from iso on mdv (or maybe mdk ?) Which I found frustrating before I realised that, since deselecting everything in one group would deselect the packages involved from all other groups. But it was ok once I realised what was happening. (It would just be a good idea to warn users.) i don't understand He is mentioning the package selection tool found in the installer, which sorts packages based on their .desktop categories as far as I can tell (which mean that they can appear in several categories). -- Malo
Re: [Mageia-dev] [RPM Groups] Dealing with Books/*
Le 10/10/12 01:02,Pierre-Malo Deniélou nous adresse ces quelques mots : Dear packagers, Some progress has happened on the RPM group move. Thanks. However there is still a lot to do. Following up on some remarks, questions and bug reports (https://bugs.mageia.org/show_bug.cgi?id=7719). I think we should clarify what goes into Documentation (otherwise it becomes cluttered). I propose to exclude from Documentation any documentation that is development-targeted (e.g. javadoc, API documentation), and leave them in their Development/* group. The benefit is that it clears Documentation from long lists of API definitions that only advanced user might need. I will update https://wiki.mageia.org/en/RPM_groups_policy with a comment if no one objects. Cheers, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kremotecontrol-4.9.2-1.mga3
Le 16/10/12 03:50,andre999 nous adresse ces quelques mots : Balcaen John a écrit : Le lundi 15 octobre 2012 14:54:27 Marek Laane a écrit : [...] mikala mikala 4.9.2-1.mga3: + Revision: 301978 - Update tarball to KDE SC 4.9.2 - Fix group kremotecontrol in group Accessibility? hmm, really? ... We're of course open to suggestion... Its a front end for kde for an infrared interface. Note that an infrared is line-of-sight, so it is in proximity like a usb or parallel port, and not network-oriented like ethernet, in my view. Assuming that it is graphical, I would suggest that it goes into Graphical_desktop/KDE. Otherwise, it could be communications, but that seems to be more for passing information to and/or from independant devices, such as smartphones or fax machines. In any case, it would be useful to have a short description of the purpose of each rpm group I started writing some indications here: https://wiki.mageia.org/en/RPM_groups_policy Cheers, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release ocaml-4.00.1-1.mga3
On 14/10/12 14:25, John Balcaen wrote: 2012/10/5 blue_prawn buildsystem-dae...@mageia.org: Name: ocamlRelocations: (not relocatable) Version : 4.00.1Vendor: Mageia.Org Release : 1.mga3Build Date: Fri Oct 5 18:46:33 2012 Install Date: (not installed) Build Host: jonund.mageia.org Group : Development/OCaml Source RPM: (none) Size: 3345223 License: QPL with exceptions and LGPLv2 with exceptions Signature : (none) Packager: blue_prawn blue_prawn URL : http://caml.inria.fr Summary : The OCaml compiler and programming environment Description : OCaml is a high-level, strongly-typed, functional and object-oriented programming language from the ML family of languages. blue_prawn blue_prawn 4.00.1-1.mga3: + Revision: 302936 - update to last version 4.00.1 Could you have a look @ facile package because due to new ocaml it's going to prevent the build of kalzium ? I just patched facile to work with the new ocaml. You should be able to build kalzium now. Blue_prawn and I are in the middle of the ocaml-4.0 migration, sorry about that. Thanks for the notice, -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kwallet-4.9.2-1.mga3
On 15/10/12 17:34, Balcaen John wrote: Le lundi 15 octobre 2012 15:48:46 Marek Laane a écrit : [...] Again, is Networking/Remote access right group for Kwallet? Do you have a better group for this ? Security -- Malo
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kremotecontrol-4.9.2-1.mga3
On 15/10/12 17:36, Balcaen John wrote: Le lundi 15 octobre 2012 14:54:27 Marek Laane a écrit : [...] mikala mikala 4.9.2-1.mga3: + Revision: 301978 - Update tarball to KDE SC 4.9.2 - Fix group kremotecontrol in group Accessibility? hmm, really? ... We're of course open to suggestion... I've put some IR things in Communications/Serial It's not perfect, but might be ok while we find out all the troubled categories. Cheers, -- Malo
[Mageia-dev] [RPM Groups] Dealing with Books/*
-handbook neoclust:kreversi-handbook neoclust:krfb-handbook neoclust:kruler-handbook neoclust:kshisen-handbook neoclust:ksirk-handbook neoclust:ksnapshot-handbook neoclust:kspaceduel-handbook neoclust:ksquares-handbook neoclust:ksudoku-handbook neoclust:ksystemlog-handbook neoclust:ktimer-handbook neoclust:ktimetracker-handbook neoclust:ktnef-handbook neoclust:ktron-handbook neoclust:ktuberling-handbook neoclust:kubrick-handbook neoclust:kuser-handbook neoclust:kwallet-handbook neoclust:kwrite-handbook neoclust:lskat-handbook neoclust:okular-handbook neoclust:palapeli-handbook neoclust:sweeper-handbook nobody:atkmm-doc nobody:cogl-doc nobody:freetds-doc nobody:gconfmm2.6-doc nobody:glibmm2.4-doc nobody:gnome-vfsmm2.6-doc nobody:gtkmm2.4-doc nobody:gtkmm3.0-doc nobody:libglademm2.4-doc nobody:libgnomecanvasmm2.6-doc nobody:libgnomeuimm2.6-doc nobody:libpcap-doc nobody:libsigc++2.0-doc nobody:tracker-docs nobody:xerces-c-doc ovitters:gnome-devel-docs ovitters:gnome-user-docs shlomif:pangomm-doc spuhler:php-manual-en stormi:graphicsmagick-doc I'll send some other lists of packages to fix in a few days. Meanwhile, please fix! Thanks! -- Malo
Re: [Mageia-dev] Radeonsi/glamor and python packages
Le 07/10/12 05:47,Joseph Wang nous adresse ces quelques mots : I added my name to the wiki a few weeks ago. I haven't been contacted by anyone, yet. Would appreciate it if someone gets in touch with me. I have a queue of several other packages to add... It is volunteer-based, so it can take some time. Please come to #mageia-mentoring, you will find a mentor quicker. Cheers, -- Malo
Re: [Mageia-dev] Radeonsi/glamor and python packages
On 05/10/12 13:53, Joseph Wang wrote: Hi all, Hi Joseph! Been lurking for a while. Welcome! I've gotten the ATI open source drivers to work on my radeonsi with glamor https://bugs.mageia.org/show_bug.cgi?id=7717 I've also packaged some python packages https://bugs.mageia.org/show_bug.cgi?id=7515 https://bugs.mageia.org/show_bug.cgi?id=7517 There's also an uploaded patch that fixed lynx https://bugs.mageia.org/show_bug.cgi?id=7399 That's great! Thanks. But, maybe you should join our packager's team, and upload the packages yourself :-) Please consider our apprenticeship program: https://wiki.mageia.org/en/Becoming_a_Mageia_Packager Cheers, -- Malo
[Mageia-dev] [RPM Groups] Getting on with the change
Dear packagers, Thanks for starting to move your packages to the new RPM group hierarchy. There is however still lots to do. As a reminder, here is the policy: https://wiki.mageia.org/en/RPM_groups_policy#List_of_official_groups Please try to fit your packages into these categories. I take notes of the complaints I hear, so that for the next iteration (~Beta1 time), we can adjust the policy a tiny bit. Before that, can everyone get on with implementing the new RPM group policy, and especially: - Documentation group replaces the Books/* groups (still 490 packages), so please change the groups of all your doc subpackages to Documentation - Office (still 445 packages), Sound (749), Graphics (425) and Video (641) are split in the new policy, please start changing the groups to have a finer grain classification. Thanks! -- Malo
Re: [Mageia-dev] Final set of isos for Mageia 3
Le 02/10/12 16:58,Anne Nicolas nous adresse ces quelques mots : Hi there So as planned when starting discussion, here is the final set of isos that will be built for Mageia 3. We have listed all the proposals and explanations (from both this ML and forums) to find a list that would satisfy most of Mageia users. Here is the list (Thanks MrsB for doing it first :) ): 2 liveCDs: - GNOME 700M i586 - english only - Nonfree - KDE 700M i586 - english only - Nonfree These are mainly targetted for distribution during events or for Newspapers The target audience is not too little to justify the extra QA? Is it worth having them at all? (Note that I'm among the ones who still uses CDs, a CD-RW) If we keep them, we should show them as unimportant from a marketing point of view (i.e. last in the list of media). Otherwise the headlines will be Mageia gives up on internationalization for Mageia 3 or Mageia gives up on x86_64 for Mageia 3. The headlines should be Mageia turns to LiveDVDs for Mageia 3. 4 liveDVDs: - GNOME DVD i586 - all locales - Nonfree - GNOME DVD x86_64 - all locales - Nonfree - KDE DVD i586 - all locales - Nonfree - KDE DVD x86_64 - all locales - Nonfree These are now the main media then. Classic Installation ISOs - LXDE DualCD - all locales - Free only - DVD i586- all locales - Free/Nonfree - DVD x86_64 - all locales - Free/Nonfree DVDs will propose by default 100% free software installation. Users will be asked if he wants to use non free drivers. This is still to be done inside drakx installer and will not be available yet for alpha 2 release. My 2 cts. -- Malo
Re: [Mageia-dev] ANNOUNCE: RPM group Policy change taking effect
Le 29/09/12 13:37,Oliver Burger nous adresse ces quelques mots : Am 26.09.2012 23:00, schrieb Pierre-Malo Deniélou: Dear fellow packagers, In a few minutes, I will upload a new rpmlint-mageia-policy package that implements the new RPM group policy. Normally, packages that do not follow the new RPM groups will be rejected from the build system. I advise you to run rpmlint on your RPMs, SRPMs or spec files before submtting. The new RPM policy can be consulted at: https://wiki.mageia.org/en/RPM_groups_policySorry for cutting in late, but... There is a new group Geography for maps and gps related software... Now how to decide wether software is Sciences/Geosciences where the whole GIS stack is located right now or Geography? The whole GIS stack goes to Geography. Sciences/Geosciences is from now on only for Scientific software related to Geology and Environmental sciences. Cheers, -- Malo
Re: [Mageia-dev] RPM groups policy
Le 27/09/12 10:04,Colin Guthrie nous adresse ces quelques mots : Just ran into my first practical problem and would like your feedback. I'm guessing your email is just the first of a long list :-). The new RPM group will indeed cause some head scratching for many packages. PulseAudio packages used to just be in Sound group, but now I have to sub-categorise them as Sound/*. This is fine and I put everything in the Sound/Mixer category for now as this is one of the tasks PA does, mix your audio, but I get the feeling this group was more designed to represent graphical mixer UIs rather than infrastructure level stuff. RPM groups are for users, not necessarily technical users (technical users already know which packages interest them). So the main advice to find the category of a given package is: Where would it make sense for a user browsing through a list to find it? For PulseAudio, Sound/Mixer is fine. Should there be a group that represents this better? e.g. Sound/Plumbing System/Sound Plumbing/Sound Or Sound/PulseAudio ... :-P That's the Suse approach, but it does not work. It only multiplies the groups, with 3 or 4 subdivision depths (Amusements/Games/Strategy/Turn Based ...), with some groups only having a handful of packages. Many of the subdivisions make sense from a packaging point of view, but from a user point of view it makes browsing too precise. I personally think that groups are meant for the exploration by people who don't know what they are looking for. Or perhaps PA should just go in System/Base? No. It only drowns it in the crowd of completely unrelated packages. (I use the term Plumbing as this is quite common these days as an off shoot perhaps from the Linux Plumbers Conference where the various infrastructural bits of linux are discussed). Thoughts? No RPM group classification is perfect. There will always be a package that does not fit the classification. So we should stick to the best guess strategy for now. The new RPM group policy is not completely fixed, but I propose that everyone tries to stick with it until Beta 1, at which point we can review it and amend the most obvious problems. Cheers, -- Malo
Re: [Mageia-dev] RPM groups policy
Le 27/09/12 10:51,Pascal Terjan nous adresse ces quelques mots : On Thu, Sep 27, 2012 at 10:48 AM, Pierre-Malo Deniélou For PulseAudio, Sound/Mixer is fine. I don't agree If someone wants to install a mixer, pulesaudio in the list will probably confuse him As I was saying earlier, no group classification is perfect. In the situation you describe, having pulseaudio in System/Base would be even more confusing. But if you were to choose between Sound/Editors and Convertors, Sound/Midi, Sound/Mixers, Sound/Players, Sound/Utilities, Sound/Visualization, where would you look first? You know none fits perfectly, I know that as well, even less for pulseaudio-module-jack or pulseaudio-module-bluetooth. But before everyting was in Sound: so confusing is maximum. Now it becomes a bit (but only a bit) easier. That's the point. Or perhaps PA should just go in System/Base? No. It only drowns it in the crowd of completely unrelated packages. Do you expect someone to want to manually install pulseaudio after removing it, and search it in mixers? Yes. By the principle of Where else? :-) Cheers, -- Malo
[Mageia-dev] ANNOUNCE: RPM group Policy change taking effect
Dear fellow packagers, In a few minutes, I will upload a new rpmlint-mageia-policy package that implements the new RPM group policy. Normally, packages that do not follow the new RPM groups will be rejected from the build system. I advise you to run rpmlint on your RPMs, SRPMs or spec files before submtting. The new RPM policy can be consulted at: https://wiki.mageia.org/en/RPM_groups_policy In a nutshell, the changes are: - Remove Books/* - everything in Documentation - Add several Development/* to reduce Development/Other - Add Games/Shooter to reduce Games/Arcade and Games/Other - Split Office into Office/Dictionary, Office/Finance, ... - Split Sound into Sound/Editors and Convertors, Sound/Midi, ... - Split Video into Video/Editors and Convertors, Video/Players, ... - Split Graphics into Graphics/3D, Graphics/Editors, ... - Split Communications into Communications/Bluetooth, Communications/Fax, ... I will start collecting the list of packages that need to change group soon. I will write this list about what changes are urgent (current bugs) and what changes are necessary with respect to the new policy. So, all of us should feel free to start adapting our packages to the new policy :-). Cheers, -- Malo
Re: [Mageia-dev] RPM groups policy
Le 26/09/12 22:09,Charles A Edwards nous adresse ces quelques mots : On Tue, 25 Sep 2012 23:43:50 +0100 Pierre-Malo Deniélou wrote: Tonight, following the packagers meeting, we agreed on a new RPM group policy. The current policy is described at: http://wiki.mageia.org/en/RPM_groups_policy The new policy is presented at: http://wiki.mageia.org/en/Feature:RPMGroupRevamp What about xdg menu compliance? There is already a policy in place, and automated checks that enforce it. Everyone seems happy with it, so it does not change :-). https://wiki.mageia.org/en/Packaging_guidelines#Desktop_files However, if you feel that some packages are in the wrong menu category, it's a bug that you should report. Cheers, -- Malo
Re: [Mageia-dev] RPM groups policy
Le 26/09/12 22:42,Anssi Hannula nous adresse ces quelques mots : 27.09.2012 00:27, Charles A Edwards kirjoitti: On Wed, 26 Sep 2012 22:17:29 +0100 Pierre-Malo Deniélou wrote: The current policy is described at: http://wiki.mageia.org/en/RPM_groups_policy The new policy is presented at: http://wiki.mageia.org/en/Feature:RPMGroupRevamp What about xdg menu compliance? There is already a policy in place, and automated checks that enforce it. Everyone seems happy with it, so it does not change :-). Yes, but you will now be creating entries that Are Not registered categories RPM groups are not related to menu categories in any way. The RPM groups are seen only in rpmdrake (and smart and Mageia App Db), as far as I understand. And they are package-based. .desktop files (which are for menu entries) are for the desktop applications. So one package can have several .desktop files (for each application it contains) or none. They are in effect unrelated. There was however a proposal to base the new RPM groups on the freedektop standard for menu classification, but it seems not to be a possibility (mainly because packages applications). Cheers, -- Malo
Re: [Mageia-dev] RPM groups policy
Le 26/09/12 22:58,Charles A Edwards nous adresse ces quelques mots : On Thu, 27 Sep 2012 00:42:58 +0300 Anssi Hannula wrote: Yes, but you will now be creating entries that Are Not registered categories RPM groups are not related to menu categories in any way. I know the the rpm group is different. Are you saying that No packager will try to create or change a menu entry to reflect the new rpm groups? Exactly. Example: 'Alien arena' in Games/Shooter instead of Games/Other The RPM group of Alien arena will change to Games/Shooter, but its desktop file is not supposed to change. I understand your point, but there will always be mismatches between the two categories, since the two purposes are different. -- Malo
Re: [Mageia-dev] ANNOUNCE: RPM group Policy change taking effect
Le 26/09/12 22:00,Pierre-Malo Deniélou nous adresse ces quelques mots : Dear fellow packagers, In a few minutes, I will upload a new rpmlint-mageia-policy package that implements the new RPM group policy. Normally, packages that do not follow the new RPM groups will be rejected from the build system. I advise you to run rpmlint on your RPMs, SRPMs or spec files before submtting. Thanks to boklm the checks are now in place and the new policy takes effect. Cheers, -- Malo
Re: [Mageia-dev] Packagers meeting tonight
On 25/09/12 09:27, Anne Nicolas wrote: Hi there Before publishing topics, are there some to be listed you would think about ? Cheers Can we discuss the RPM group redesign feature? https://wiki.mageia.org/en/Feature:RPMGroupRevamp Cheers, -- Malo
[Mageia-dev] RPM groups policy
Dear packagers, Tonight, following the packagers meeting, we agreed on a new RPM group policy. The current policy is described at: http://wiki.mageia.org/en/RPM_groups_policy The new policy is presented at: http://wiki.mageia.org/en/Feature:RPMGroupRevamp This change in policy means that I will take the following actions by the end of the week: * update the wikipage http://wiki.mageia.org/en/RPM_groups_policy * patch rpmlint to refuse new packages that do not follow the new policy (I will send another email to -dev just before submitting the new rpmlint). * create a bug report tracking the packages that need to change group. * mail -dev about the packages that are currently in wrong groups (even with respect to the current policy) so that their maintainers can take proper action within 2 weeks. After that, I will change the groups myself * mail -dev about the packages that are correct with respect to current policy but need to be updated to respect the new policy. For these packages, the deadline will be beta1 (12/12) to complete the changes, which means that I will start doing the moves by myself by Alpha 3 (06/11). I will mail -dev at each step on the way, so don't worry too much now. I hope the new RPM groups will make it easier for everyone to find packages in rpmdrake and other tools. It will be a bit annoying for every packager, but it's a good opportunity to revisit many package specs before mga3 and make Mageia better. Cheers, -- Malo
Re: [Mageia-dev] need some help to build a linuxsampler.rpm
Le 22/09/12 01:45,PhilippeDidier nous adresse ces quelques mots : You need to add -lpthread to the linker options... -- Thomas Thanks Thomas ... I use a very simple spec file in which these parts were working for Mandriva : %prep %setup -q -n %name-%version %build %configure2_5x %make %install make DESTDIR=%buildroot install I don't know where to add this option I thought it was done by %configure (I can see the option -pthread in the CXXFLAGS of the different makefiles) I tried to add CXXFLAGS=-lpthread in the spec but it didn't change anything ... the linker flags use the LDFLAGS variable. -- Malo
Re: [Mageia-dev] need some help to build a linuxsampler.rpm
Le 22/09/12 14:26,PhilippeDidier nous adresse ces quelques mots : Thanks a lot Pierre-Malo ! I only modified this %build %configure2_5x %make LDFLAGS=-lpthread And it works now !! But I don't understand why I have to add this for Mageia2 when it is not needed for Mandriva ... Is there something badly configured on my system ? Is it a package problem in glibc-2.14.1-8.mga2 or in glibc-devel ? Does it reveal a Mageia's bug ? It reveals that before the --as-needed option was activated by default, which led to some problems: https://wiki.mageia.org/en/Overlinking_issues_in_packaging So --as-needed is no longer used, but the underlinking happens ;-) https://wiki.mageia.org/en/Underlinking_issues_in_packaging Anyway, this is not a bug, just the consequence of different choices made for the distrib between Mandriva and Mageia. Cheers, -- Malo
Re: [Mageia-dev] Weekly meetings
Le 22/09/12 16:05,Anne Nicolas nous adresse ces quelques mots : Le 22/09/2012 16:24, Angelo Naselli a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 18/09/2012 21:04, Anne Nicolas ha scritto: Hi there Due to personal constraints, I will not be able to organize meetings on wednesday anymore. So either somebody does it or we can move it to tuesday, same hour. Comments ? I usually can attend if I'm at home during the working days, so one day or another it's the same for me. When a decision is taken can you send an official email please, and if the day changed also update the calendar? (that is my real reminder :) ) Thanks Sorry last week was *very* busy. So we will have our weekly meeting on Tuesday, 19hUTC So next one is on 25th. Cheers Can someone update the calendar? http://www.mageia.org/en/calendar/ Thanks, -- Malo
Re: [Mageia-dev] Rebuilds needed ?
On 18/09/12 18:10, Frank Griffin wrote: Some requested packages cannot be installed: jarjar-1.0-5.mga3.noarch (in order to keep jarjar-maven2-plugin-1.0-4.mga1.noarch) lib64mount1-2.22-4.mga3.x86_64 (in order to keep util-linux-2.21.2-3.mga3.x86_64) util-linux-2.22-4.mga3.x86_64 (in order to keep nspluginwrapper-i386-1.4.4-1.mga2.x86_64) Continue installation anyway? (Y/n) ...for several days now (i. e. not mirror lag). http://check.mageia.org/cauldron/dependencies.html Tells you all the packages that cannot be installed in the current Cauldron. for example, nspluginwrapper, mediawiki, eclipse or razorqt, ... Cheers, -- Malo
Re: [Mageia-dev] Weekly meetings
Le 18/09/12 20:04,Anne Nicolas nous adresse ces quelques mots : Hi there Due to personal constraints, I will not be able to organize meetings on wednesday anymore. So either somebody does it or we can move it to tuesday, same hour. Comments ? We can move it starting next week and have someone fill for you (guillomovitch? coling? tmb?) tomorrow. Cheers, -- Malo
