Re: [Mageia-dev] Help needed with kmediafactory, redmine and oar
Hi. I have managed to build kmediafactory with additional fedora patches. Corrects desktop file validation: kmediafactory-0.8.1-fdr-desktop_validate.patch Fixes build ffmeg libraries in CMake.lst (and eliminates compiling error: kmediafactory-0.8.1-fdr-FindFFmpeg.patch 2013/3/29 Johnny A. Solbu coo...@solbu.net kmediafactory and redmine doesn't build, and I can't figure out how to fix it. Can someone take a look at them? oar have a missing dependency, ruby-dbi. ruby-dbi is in svn but not on mirrors. It is is it simply forgotten to submit? It builds fine on iurt. -- Johnny A. Solbu PGP key ID: 0xFA687324 kmediafactory.spec Description: Binary data kmediafactory-0.8.1-fdr-desktop_validate.patch Description: Binary data kmediafactory-0.8.1-fdr-FindFFmpeg.patch Description: Binary data
[Mageia-dev] Please push dbus-java
Hi. I'm trying to package zemberek. One of it's dependency is dbus-java package. I can see that it is in svn but not pushed. If it is because of libmatthew-java package problem, libmatthew-java is fixed and pushed. Thanks.
Re: [Mageia-dev] Still looking for a mentor.
2013/3/14 Nicolas Lécureuil nicolas.lecure...@free.fr Le jeudi 14 mars 2013 12:57:44 atilla ontas a écrit : Hi. I'm afraid i won't find a mentor. I already doing stuff with rpm packages and maintaining an unofficial repository at my site. ( depo.tarakbumba.com) So, no one wants mentor to me? Hello, what you can do is to open a bugreport with one spec file so we will be able to review it inside. I can take a look. Thank you for quick reply. I didn't notice at wkik that a bug report should be filed. Should i file bugreport for a package request? If so i have already one; https://bugs.mageia.org/show_bug.cgi?id=9222 Though i did not paste .spec file there. Adding to that report ASAP.
[Mageia-dev] Package request with src.rpms
Hi there. I merely working on zemberek and its dependencies for Mageia Cauldron. As a Turkish sporen guy; i'd like to see zemberek in repositories. Zemberek is a natural language processing library for Turkic languages (Turkish, Azerbaijanin, Turkmen etc.), It is written in java. Altough its development stalled since 2010; it is still working on Magea, Also zemberek is the only true Turkish spell checking app. Aspell-tr won't do right corrections. Zemberek needs apache-mina 1.8, libmatthew-java, slfj4 and dbus-java packages to run. While it won't work apache-mina package in official repositores; i decided to apache-mina-1.1.7 in zemberek-server package; also i patched libmatthew-java due to bug#9002https://bugs.mageia.org/show_bug.cgi?id=9002. Also i hava made package for Al-Anvar, a Holy Qur'an study tool. So, if you mind to inspect, review and add to repositories those apps it will be awesome. I'm willing to be a packager but have little time to work on packages due to my job and familiy, AItough i can not attend weekly meetings most of time, still is it possible? May i find a mentor?
Re: [Mageia-dev] Package request with src.rpms
Oops... Forgot to mention packages url: http: depo.tarakbumba.bugs3.com/Mageia/3/SRPMS 2013/2/19 atilla ontas tarakbu...@gmail.com Hi there. I merely working on zemberek and its dependencies for Mageia Cauldron. As a Turkish sporen guy; i'd like to see zemberek in repositories. Zemberek is a natural language processing library for Turkic languages (Turkish, Azerbaijanin, Turkmen etc.), It is written in java. Altough its development stalled since 2010; it is still working on Magea, Also zemberek is the only true Turkish spell checking app. Aspell-tr won't do right corrections. Zemberek needs apache-mina 1.8, libmatthew-java, slfj4 and dbus-java packages to run. While it won't work apache-mina package in official repositores; i decided to apache-mina-1.1.7 in zemberek-server package; also i patched libmatthew-java due to bug#9002https://bugs.mageia.org/show_bug.cgi?id=9002. Also i hava made package for Al-Anvar, a Holy Qur'an study tool. So, if you mind to inspect, review and add to repositories those apps it will be awesome. I'm willing to be a packager but have little time to work on packages due to my job and familiy, AItough i can not attend weekly meetings most of time, still is it possible? May i find a mentor?
Re: [Mageia-dev] Update of backport, policy proposal
2011/6/26 Wolfgang Bornath molc...@googlemail.com: A short reality check from userside: If foo-1.0 is in Mageia 1 and foo-1.1 is released upstream - foo-1.1 will likely be integrated in Cauldron very soon after - users will request to have foo-1.1 in Mageia 1 - if Mageia will not provide it then there will soon be local repositories where local packagers will do a backport for their friends. This may not be what Mageia backport policy will allow but we can not avoid people doing and using this, no matter how many warning signs we will publish. This has to be taken into account here. When a policy is found it has to be communicated very well, especially if that policy means that the user can not have foo-1.1 in his stable Mageia 1. This is important because former Mandriva users were used to get almost all new versions backported, if not officially then in 3rd party repos like MIB or MUD. -- wobo Hi. I'm following this threat from the very beginning. While reading, i feel i'm reading a Mandriva Cooker mailing list posts. As a community distro, why Mageia developers still think like a Mandriva employee? Why backports and why so many policies, like a commercial enterprise distro? I mean, Mageia do not have paid developers to work on packages all the time. Also Mageia do not have so many packagers like Fedora or Ubuntu, So, why make so many things so hard? As wobo mentioned, people like latest and greatest software. I think, except a few users will use unofficial 3rd party repos to get latest software. While i was maintaining MVT (Mandriva Turkiye) repository, our users asked for GNOME 2.32 while Mandriva have GNOME 2.30 on official release. Personally i always hate the backports structure and policy. It confuses minds. Why Mageia need a backports repo, i really do not understand. Stability and bug free releases are of course a must. But it needs developers dedicated to work, almost paid developers. If a software do not related with core system, like vlc, it should included updates repo. Let upstream fix bugs and security issues. If a packager catchs a bug he should send a patch to upstream and wait for a new release. Otherwise, it is not packaging it is coding, which many potential packgers will avoid to contribute. Look at Debian and Arch Linux who haven't any paid developers but community distros. Stable Debian releases provide software from a century ago for the sake of stability. Arch provides latest software including core system and occaionally have breakages. I think Mageia should be between two of them. Release latest software in updates for non core system and libs, keep core system stable. Remove this backports thingy. My 2 cents...
[Mageia-dev] Suggestion-Locales management for One (or Live) Cd releases
I don't know if this proposal is even mentioned before. It's hard to catch in all these posts. I think the main probem with Mandriva One releases was lack of space. It will still a problem for Mageia Live CD releases. Also, it is very cofusing for Mandriva/Mageia newbies to determine which iso image contains their native language support and i'm sure it brings more effort to maintain so many one cd isos and waste of server/mirror space. I propose to implement an Ubuntu like, install time or in live enviroment language packs installing. How this should work? It is obvious which packages included in Live cd. When creating an iso (draklive?) livecd creation tool strips all locale files except english ones and create seperate packages per locale. These packages, ie. mageia-one-kde4-locale-tr includes all locale files corresponding with included apps/packages in mageia-one-kde4.iso. When user boots with live cd (mageia-one?) a dialog appears and asks which locale he/she would use with live environment. Then if it detects internet connection, downloads this mageia-one specific package (mageia-one-kde4-locale-tr.rpm for Turkish locale in mageia-one-kde4) and adds tr locale /etc/rpm/macros file. So, there will be only one live cd image on mirrors per DE, there will be room for apps in live cd iso, people will not confused for localized isos. What do you think?
Re: [Mageia-dev] Suggestion-Locales management for One (or Live) Cd releases
2010/10/25 Ahmad Samir ahmadsamir3...@gmail.com: And if there's no active internet connection at installation time? Ahmad Samir Well, they will use live environment in english after installation and install corresponding package like normal package installation. That's all. The situation in my proposal with no internet is same as the locales do not have supported in live cd releases. i.e. Azerbaijani. If someone needs full locale or packages support it already have to install from Free dvd release. Don't they? 2010/10/25 Thorsten van Lil tv...@gmx.de: -Ursprüngliche Nachricht- Von: mageia-dev-boun...@mageia.org [mailto:mageia-dev-boun...@mageia.org] Im Auftrag von atilla ontas I propose to implement an Ubuntu like, install time or in live enviroment language packs installing. How this should work? What do you think? As I installed Ubuntu last weekend myself, I want to mention my POV to that mechanism. It's hard for those who doesn't want or can't connect to the internet during installation, but for those may the One be the wrong installation method. The bigger problem in the current state of the ubuntu installation process is, that you have to enter the passphrase for a wireless connection with the wrong keyboard layout. After that you where prompted to enter a key for the gnome keyring and it wasn't clear at that time which keyboard layout is used. Also in the end of the installation where you have to enter a password for the user. So, if Mageia wants to offer an similar method, we need to take care of that. Regards, Thorsten Wireless connections are mostly issues in free dvd releases too. People have to enable non-free repository and install wireless drivers on most cases. Also, misconfiguration of keyboard layout is a serious problem than having native language support, you must find right key kombination to setup and use root password. So, i can' t agree with this issue, it is not related just with my proposal but with entire system. I think my proposal have much more pros than cons.
Re: [Mageia-dev] Suggestion-Locales management for One (or Live) Cd releases
2010/10/25 Wolfgang Bornath molc...@googlemail.com: That's not true. In all of those distros language selection comes first in installation. I installed Ubuntu 10.10 from the normal live cd without internet connection and language selection came first. Same with openSUSE. I strongly recommend to keep language selection on the first step, no matter which way of installation you chose. That's not what i mean wobo. Those distros do not provide localized isos, not OpenSuse-Gnome-europas-americas1.iso. OpenSuse installs i.e. turkish locale packages after installation (and it even can't provide Traditional Turkish F keyboard layout. in any meanings with yast) Also, i do not mean to languge selection comes later. Pls, read carefully my previous posts and try to understand what i want to mean. If we will release a Mandriva One like live cd then my proposal's whole concept is: 1- User boots with mageiaone 2- User selects keyboard layout; Mandriva One's grub configuration is capable for that. 3- Live cd starts to loading ram 3- A dialog popup appears and asks if he/she wans to select language 4- If an active internet connection detected notifies users that selected languge will downloaded from net otherwise user use live system in English. After DE starts an if an active connection is present, installs user's selection of language files while installing on hard disk. I want to make an attention, If a language doesn't included in Mandriva One release; user will not have any native language support for outside of DE applications when he/she install to harddisk Simply, ie. Azerbaijani user *must* install other packages than DE installed within live cd again to have Azerbaijani support. Because /etc/rpm/macros file do no let other language files other than it includes. :)
Re: [Mageia-dev] How will be the realese cycle?
Hi. If you interested, Mandriva Turkiye Community poll ended about release cycle. Here are the results: *Exactly as Mandriva, 6 months release cycle 18.2% *Like OpenSuse, 8-9 months release cycle 13.6% *One release a year 31.8% * 6 months cycle for core, rolling release model other for other software 4.5% * Rolling release 31.8%
Re: [Mageia-dev] Talk of Browsers
2010/10/1 Wolfgang Bornath molc...@googlemail.com: 2010/10/1 Thierry Vignaud thierry.vign...@gmail.com: On 1 October 2010 10:44, Wolfgang Bornath molc...@googlemail.com wrote: Which extionsion a user wants to instaall should be left to the user's decision. Make the install easy but do not install any extensions by default. I've never used those extensions, except the developper bar. Somebody told me to install Adblock and whatever, I did and FF became unstable but not one second faster. Maybe because I do not visit many sites with large ads and all that bling-bling stuff. Anyhow, as a rule do not add any stuff by default that the user ought to decide for himself, this is not Windows. We should not tell the user what he wants to do. Then we shouldn't install neither firefox nor konqueror at all since that's a choice that the user ought to decide for himself... C'mon, a browser is not the same as a browser extension. Of course there must be defaults. But installing browser extensions by default is too much default IMHO. Same as with mail clients. You should set a mail client by default but you should not add any extensions to this client by default. wobo Please do not make any extension as default. Even do not paxckage extensions. A user should decide which extension he/she uses. Also, i don't understand why extensions packaged. Day by day extensions updated on upstream. So, packages left behind current versions. Btw, i noticed that Firefox installed in /usr/share/firefox-release-number. I don't know how buildsystem works but when ff updated all extensions must be updated for new install dir. Doesn't this behaviour brings extra workload?
Re: [Mageia-dev] What do you think about create a Mageia Welcome Center?
2010/9/30 Robert Xu rob...@gmail.com: On Sep 30, 2010, at 5:23, Michael Scherer m...@zarb.org wrote: Le mercredi 29 septembre 2010 à 20:53 -0400, Ireneusz Gierlach a écrit : I just hope there won't be a survey when you first install, because if you have no internet it doesn't let you do anything. You have to like go to console and do not cool stuff. I guess as long as it is not invasive it will be fine. Then we need to fix it so it cope with no internet access, not disable it. Maybe the first time connected to the internet the survey should appear? -- later, Robert Xu Why we' re talking about a survey? Do we need this? We are not a company and think about customer happiness. I thought this thread is about a informational and/or assistance application for newbies. If we' re talking about a Welcome Center, we should decide if it is only an informative html page or an assistance to configure basic things or both. ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev
Re: [Mageia-dev] What do you think about create a Mageia Welcome Center?
2010/9/30 Wolfgang Bornath molc...@googlemail.com: Agreed. Surveys are a nuisance anyway. 1. A large part of survey participants do not tell the truth. 2. A large part of users do not participate so you will not get any real information anyway. 3. If something is wrong with the project, the distribution, user satisfaction or whatever you will know it by user postings in the forums earlier than by surveys. So, at the end of the day, What do you get by surveys to take away? More work to implement and to read them, that's all. I mean what wobo has written. Besides, forum posts are more effective way to track users opinions about distro and applications. I always hated this survey thing on Mandriva. Also it feels something like a registration to a propierty application or validate a windows install. Many users in Mandriva Turkiye community asked me if they *must* fill survey and register their e-mails. Most of them were new to GNU Linux. I think we should decide if we will implement a Welcome Center/Kaptan to distro and if it is an informative screen or basic configuration tool or both for newbies. I' m not interested in filling the blanks on a survey. Also a survey would be introduced in main web site. Any interested user should fill it. ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev
Re: [Mageia-dev] What do you think about create a Mageia Welcome Center?
2010/9/29 Marek Laane b...@smail.ee: 2010/9/29 Juan Luis Baptiste juan.bapti...@gmail.com On Wed, Sep 29, 2010 at 5:12 AM, atilla ontas tarakbu...@gmail.com wrote: I suggest to look at Pardus Linux's Kaptan tool. It shows up to assist desktop/system configuration to new user. Such as from network setup to icon theme. Tough it is only KDE app. Wow, this kaptan app looks really really nice, if someone wants to take a look at some screenshots of it (and Pardus in general) see this link: http://www.dedoimedo.com/computers/pardus.html Also the installer looks pretty nice too. I remember something like Kaptan was used in KDE many-many years ago (KDE2 probably?) -- Juancho ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev May be there was a Kaptan like app before. But Kaptan written from stratch for Pardus, not fork of another app. ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev
Re: [Mageia-dev] What do you think about create a Mageia WelcomeCenter?
2010/9/29 Gustavo Giampaoli giampaoli.gust...@gmail.com: I found both aproaches really atractive and useful. Kaptan looks very intuitive, easy and centralize most (if not all) the most common and basic settings that a person with basic knowledge could need after the first boot. However, wobo's aproach is also important. What happends if Kaptan-like-tool hangs in the first boot and close? That's where info page will be really really useful. This is an extreme example, but I think I presents the idea well. A newbie will be almost naked and screaming without to know where to go for help. But, if Kaptan-like-tool doesn't hang and works fine, it's always important to let people know where they have to go if anything goes wrong or where to meet other user. You never know when a user could become an important contributor. Cheers! Gustavo Giampaoli (aka tavillo1980) ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev Main problem with Kaptan is that being a KDE tool. Otherwise, freezing on first boot should not a problem. We can set a default configuration for this purpose and user changes this configuration according to his/her taste via Kaptan. So if it s***ks on first screen then nothing to worry about. Also, an information page can be implemented as a first tab to Kaptan like i see in mockups in this thread. I' m not a programmer but i think implementing those should be easy. Main problem is like i said, porting Kaptan to GTK code. ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev
Re: [Mageia-dev] What do you think about create a Mageia WelcomeCenter?
2010/9/29 André Machado afmach...@dcemail.com: I'd say that Gustavo is right on this one. What do we really want : a setup/configuration tool to help newbies or a welcome page to help newbies recognized what the different apps in linux are for? Maybe both: we can start showing a page with information and put it an Advanced options button what leads to other page with setup/configuration tools. But: place setup/configurations tools in Mageia Welcome Center won't does not become redundant MCC? Or maybe Mageia Welcome center should be a part of MCC? ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev Welcome Center or Kaptan should more desktop/application assistance tool and not replace MCC. This tool should be limited to network connection and screen resolution configuration on system level. But should i.e. change theme, icons, default web browser setting etc. ___ Mageia-dev mailing list Mageia-dev@mageia.org https://www.mageia.org/mailman/listinfo/mageia-dev
