Re: [Mageia-dev] Update to boost-1.53 ? (libyui fixing)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anyway atm only who is working on AdminPanel should really use libyui in mageia, so i can always provide a fixing later if i find problems. I made a different patch and sent to libyui devs, that approved it: https://github.com/libyui/libyui/commit/cfcc3d472db6a43a7a8d5edc0187026c9fabe370 Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFirlgACgkQqEs9DA4DquDA7wCgnBApTELWmqNoG0KxqcSPucFa GPQAn13AEInwq1W/kAlKJ/kYMY3/HIz8 =EEw2 -END PGP SIGNATURE-
Re: [Mageia-dev] Update to boost-1.53 ? (libyui fixing)
Il 06/04/2013 19:09, Barry Jackson ha scritto: On 05/04/13 00:08, Barry Jackson wrote: On 04/04/13 14:24, Angelo Naselli wrote: Barry i cannot test this now, but if i understood correctly the problem and talking to libyui developer this patch should work. Can you test it and tell me if it's ok please? Thanks Angelo I'll try it tomorrow - been out most of the day. Nope it still fails with the patch: http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/core/release/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130406163948.log Attached patch definitely fixes the compile problem, but I'm not sure it's ok from the point of view of who uses libyui. I will ask for this fixing to libyui developers, because if i include boost/config/select_compiler_config.hpp it works in mga2 not in mga3, so also the compiler seems to use cxx11, and that means libyui should probably fix the ImplPtr implementation, also for back compatibility. Anyway atm only who is working on AdminPanel should really use libyui in mageia, so i can always provide a fixing later if i find problems. I haven't committed anything at the moment, so you can take this as a good patch and decide later if going on or not. Angelo diff --git a/src/ImplPtr.h b/src/ImplPtr.h index be1cea9..fb0c43c 100644 --- a/src/ImplPtr.h +++ b/src/ImplPtr.h @@ -25,6 +25,9 @@ #ifndef ImplPtr_h #define ImplPtr_h +//#include boost/config/select_compiler_config.hpp +#define BOOST_NO_CXX11_EXPLICIT_CONVERSION_OPERATORS + #include boost/noncopyable.hpp #include boost/scoped_ptr.hpp
[Mageia-dev] Please push kdbg 2.5.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's a bug fixing release: http://freecode.com/projects/kdbg/releases/353512 Thanks in advance Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFhnUYACgkQqEs9DA4DquDaBQCeKkWmJL09B8BciGrRCVIoK/ra J+EAn10UCTIlWdplcfSeCPCme3GOyWxW =v5td -END PGP SIGNATURE-
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 06/04/2013 19:09, Barry Jackson ha scritto:
On 05/04/13 00:08, Barry Jackson wrote:
On 04/04/13 14:24, Angelo Naselli wrote:
Barry i cannot test this now, but if i understood correctly the
problem and talking to libyui developer this patch should
work.
Can you test it and tell me if it's ok please?
Thanks Angelo
I'll try it tomorrow - been out most of the day.
Nope it still fails with the patch:
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/core/release/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130406163948.log
Unfortunately my cauldron VM is broken and I'm trying to fix it,
so i cannot be of help.
But could you check this patch instead, I just explicit used the get()
method to get the pointer, instead of the cast operator?
Thanks
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlFgauwACgkQqEs9DA4DquATQgCfSWYzPuD3D48rIS1jkcIhTYsu
RvAAoIpjhhUdWPpjtU1frQ7NScvMVCo8
=SVCy
-END PGP SIGNATURE-
diff --git a/src/YApplication.cc b/src/YApplication.cc
index 337fa36..aee8d5e 100644
--- a/src/YApplication.cc
+++ b/src/YApplication.cc
@@ -60,7 +60,7 @@ struct YApplicationPrivate
YApplication::YApplication()
: priv( new YApplicationPrivate() )
{
-YUI_CHECK_NEW( priv );
+YUI_CHECK_NEW( priv.get() );
priv-iconLoader = new YIconLoader();
YCommandLine cmdLine; // Retrieve command line args from /proc/pid/cmdline
if ( cmdLine.argc() 0 )
null_pnt_chk.patch.sig
Description: PGP signature
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, The problem is in this build log:-
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log
I have builds of boost-1.53 in here
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/media/extra/release/
and
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/i586/media/extra/release/
media-info is up to date.
Thanks, Barry
Barry i cannot test this now, but if i understood correctly the problem
and talking to libyui developer this patch should work.
Can you test it and tell me if it's ok please?
Thanks
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlFdfxIACgkQqEs9DA4DquBWiACgkPTPxVHaUcWxEVAmyrZ2FzGN
x94AoI6W7dDPTBJ5SEAGf7YH1NhL3cMt
=xU47
-END PGP SIGNATURE-
diff --git a/src/YUIException.h b/src/YUIException.h
index f0dcb21..91ee5a0 100644
--- a/src/YUIException.h
+++ b/src/YUIException.h
@@ -147,7 +147,7 @@ class YWidget;
#define YUI_CHECK_NEW( PTR )\
do \
{ \
- if ( ! (PTR) ) \
+ if ( (PTR == 0) ) \
{ \
YUI_THROW( YUIOutOfMemoryException() ); \
} \
@@ -162,7 +162,7 @@ class YWidget;
#define YUI_CHECK_PTR( PTR )\
do \
{ \
- if ( ! (PTR) ) \
+ if ( (PTR == 0) ) \
{ \
YUI_THROW( YUINullPointerException() ); \
} \
Re: [Mageia-dev] Update to boost-1.53 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 04/04/2013 17:29, Olivier Blin ha scritto: Angelo Naselli anase...@linux.it writes: Hi, The problem is in this build log:- http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/libyui-2.42.4-0.git20130107.3.mga3.src.rpm/build.0.20130328124443.log Barry i cannot test this now, but if i understood correctly the problem and talking to libyui developer this patch should work. Can you test it and tell me if it's ok please? Hi, It does not seem your patch will fix this build issue, there is no error in YUIException.h Well the line /home/baz/rpmbuild/BUILD/libyui-2.42.4-623354b/src/YApplication.cc:63:5 is YUI_CHECK_NEW( priv ); and the definition of YUI_CHECK_NEW is in YUIException.h. But probably that does not fixing no match for 'operator! because it probably doesn't work for != or == either. It's just a try, as suggested by libyui developers. Unfortunately as i said i cannot test it here because i don't have cauldron :/ Did you try the one I already mentionned in this thread earlier? Quoting below: We could backport this in boost 1.53 to fix libyui: https://svn.boost.org/trac/boost/changeset/82103 See https://svn.boost.org/trac/boost/ticket/7809 (libyui is built with -std=c++0x) No, for the same reason as above, sorry. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFdoM0ACgkQqEs9DA4DquDfPgCcD8EsstuOfHBUB5+AH8Yx5CVU r4MAnRYwGXF2tn+tkxI7WDqt/X44O5tA =AmXL -END PGP SIGNATURE-
Re: [Mageia-dev] Update to boost-1.53 ?
Il 02/04/2013 02:31, Barry Jackson ha scritto: So now only libyui remains. Oops, i've just saw it now sorry. What is the issue? I could try to work on it tonight at home should i build boost locally first or it's on some mirrors? Angelo
Re: [Mageia-dev] Freeze Push: Virtualbox 4.2.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 19/03/2013 10:30, Robert Fox ha scritto: Minor update: VirtualBox 4.2.10 (release 2013-03-15) Have you enabled gsoap to use phpVirtualBox by any chance? Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFIQ+YACgkQqEs9DA4DquAPdQCdFgnRV9kWn7otoGjEqVnS72Ze mmoAniKfW/tLUE7R29RuHL58YVxIjtNJ =jGQj -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 05/02/2013 10:22, Sander Lepik ha scritto: 14.01.2013 22:50, Angelo Naselli kirjutas: Il 12/01/2013 20:26, Angelo Naselli ha scritto: Please push gsoap. I tried to have it before freeze time, but a nasty error blocked me, now it's fixed thanks to barjac. tmb can you please go on with virtualbox to fix this bug also: https://bugs.mageia.org/show_bug.cgi?id=7021? Thanks, Angelo Ping I don't see new version here :) You did some changes but didn't change version. Well, you also didn't bump release :P It should be ok tmd did it: anaselli :v gsoap Sophie anaselli: 2.7.17-1.mga1 // core-release (Mga, 2, i586), core-release (Mga, 1, i586) anaselli :v gsoap -v cauldron Sophie anaselli: 2.8.12-2.mga3 // core-release (Mga, cauldron, i586) Maybe we should ping tmb for virtualbox... if it is not built against new gsoap yet... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlERYFsACgkQqEs9DA4DquBaUQCfT6dzlC3vyzAyc8cVtRAkg86j 1JEAoIc1uUy11AhkU9ELwGRP7cxU16OQ =FCDi -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 No need, I just haven't had time to write systemd service files for it yet... (I know there is a sysvinit script available, but as we are nuking that stuff, I'm not sure I want to add it...) Thomas for vboxwebsrv? Follow link can help? https://wiki.archlinux.org/index.php/PhpVirtualBox#Configuration Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlERYjcACgkQqEs9DA4DquA/7ACgprV4vsXuSw70D3SOXM9RUks4 FzYAoJaigus4xw9BpRQgvxdeJbjYAQ28 =Hcpl -END PGP SIGNATURE-
Re: [Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/01/2013 20:26, Angelo Naselli ha scritto: Please push gsoap. I tried to have it before freeze time, but a nasty error blocked me, now it's fixed thanks to barjac. tmb can you please go on with virtualbox to fix this bug also: https://bugs.mageia.org/show_bug.cgi?id=7021? Thanks, Angelo Ping -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlD0b50ACgkQqEs9DA4DquBBHwCgjOB14ixgczOnmSqLRJgQTVlb aYAAoLXCEE4/n1eVbbzZp6D4G0uLoFlO =5e0e -END PGP SIGNATURE-
[Mageia-dev] Freeze push gsoap (needed to build virtualbox vboxwebsrv)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please push gsoap. I tried to have it before freeze time, but a nasty error blocked me, now it's fixed thanks to barjac. tmb can you please go on with virtualbox to fix this bug also: https://bugs.mageia.org/show_bug.cgi?id=7021? Thanks, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDxuOwACgkQqEs9DA4DquD6HACggT07mlB6oz78cc8r2uw83zEa sEYAoIoDhbqM8vHDQa+h62nybziQVQCu =kEPO -END PGP SIGNATURE-
Re: [Mageia-dev] Frequent freezes in M2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 04/01/2013 02:37, Pierre Jarillon ha scritto: How to disable it? How a standard user can know the name of the service ? It is hidden in the kde center manager. I never use it. I don't need it. I dare to say that! IIRC it's in the same nepomuk/strigi icon under systemsettings, first tab, basic settings. But I'm almost sure there is other things to be disable as well, ALT-F2 settings and there you should find something related to nepomuk. If an advanced user wants nepomuk, he knows that it exists and then he is able to activate it. Well i think it's right the contrary unfortunately instead. Most applications, as mikala said, use it and so it cannot be removed easily. Nepomuk is a gas-works. Too much complicated. Too much difficult to repair. Unsuitable with laptops and old machines. It must not be activated by default. I'm not sure you're confusing akonadi with nepomuk. As far as i know, Nepomuk is more a resource eater than a complicated thing to be used, it should help to find anything in the system (more your home) thanks to its indexing. But of course if, by default, it indexes everything directories that change and change (like imap accounts, browser cache etc) need to be indexed and indexed, that means that we can burn a SSD in a very short time :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDmqQUACgkQqEs9DA4DquBOhwCfevUqHxOOZ8c9+Lpd4cFTreC3 RAIAn3QmgVX7P5jsJqtU+sT3dTUtJq8X =4gB3 -END PGP SIGNATURE-
Re: [Mageia-dev] Frequent freezes in M2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 03/01/2013 11:41, Anne Wilson ha scritto: On 03/01/13 10:35, Guillaume Rousse wrote: Le 03/01/2013 11:30, Anne Wilson a écrit : imho: nepomuk is a beast and uses too much memory. Like many people, I don't see any advantage. What prevents you from uninstalling it ? The fact that so much in KDE is tied to it. Again and again the developers tell us that we must not. I've just disable it, and in some case changed the indexing area to my Documents and photos only. Since i use imap (and thunderbird now) i avoided indexing mails... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDlkZ8ACgkQqEs9DA4DquCBbgCfcgQgfn4GYmHY/d8XhXTSi1vE BwEAn07iUFIIxDT5Gs6MTMQO574i7+vY =8tP0 -END PGP SIGNATURE-
Re: [Mageia-dev] Frequent freezes in M2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Which is already the case in mageia 2 for the live cd at least. However nepomuk is more more intricated in KDE so we'll probably won't be able to do it for mga4 for sure eventually mga3. The good news is that nepomuk received an hudge work (which is going to land with kde 4.10 rc2 ). Maybe we could change the indexing directories to Documents instead of all the home... If you want to index also download for instance you can do by yourself... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDlkrkACgkQqEs9DA4DquBozACgq9D/q5urgXZilBR4Rkxo51xB 9GUAn0ISqPWKI3mvBIywJ/+THMvfooh+ =lcvz -END PGP SIGNATURE-
Re: [Mageia-dev] Frequent freezes in M2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The ideal would be to be able to define the areas to be indexed, just as you do in a music player or a backup app. It is, as far as i know. Open system settings, go to nepomuk-strigi settings and choose desktop query tab. You can see File indexing. There in the right part a link to Customize index folders... allows to choose which directories have to be indexed, iirc the whole home is selected by default. Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDl648ACgkQqEs9DA4DquCjzgCeJNAytc57HTCWYj8RU0FFORAm tHMAoLkC5jmf1dslK8ohNfEx/BiSx6Ah =4LdP -END PGP SIGNATURE-
Re: [Mageia-dev] KDE SC 4.10 Beta1
Il 22/11/2012 22:13, Balcaen John ha scritto: Regarding digikam , the conflict with /usr/share/applications/kde4/kipiplugins.desktop has been fixed upstream fwang did push it today. Can i close the bug then?
Re: [Mageia-dev] Mga3 - Beta1 soft freeze in Cauldron
Il 07/12/2012 03:39, Thomas Backlund ha scritto: Hi, So Cauldron is now in soft freeze for Mga3 - beta1 release I thought it were done after Christmas :( I have some changes i haven't committed because in testing and not final at home (livecd-creator and sankore), i don't think they breaks anything, but i cannot give my availability for sure before Christmas... sorry. Angelo
Re: [Mageia-dev] Mga3 - Beta1 soft freeze in Cauldron
This soft freeze is only enforced by mail to try and avoid big changes in cauldron until beta1 is out (~1 week) to make life easier for iso builders in case we need to redo / update some packages... Ah sorry :) Thanks for explanation. Angelo
[Mageia-dev] urpmi --download-all --no-clean does not work any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, last night i realized i cannot use -or at least i believe- urpmi cached any more. I'm trying to update and fix livecd-tools but the above problem breaks some livecd-creator functionality... I opened a bug report for that: https://bugs.mageia.org/show_bug.cgi?id=8272 In which is clear that urpm::init_cache_dir has been removed from urpm.pl: Undefined subroutine urpm::init_cache_dir called at /usr/lib/perl5/vendor_perl/5.16.2/urpm/main_loop.pm line 101, STDIN line 2. help and manual are showing --download-all --no-clean, so i'd expect they work. Any help here? Thanks in advance. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7NrsACgkQqEs9DA4DquCKqQCfUzaU6Nuhsh6pLBw91nfExk8I nmsAn0ubX+IpCs/z8jn8MV5J9d15I5Zk =LuKh -END PGP SIGNATURE-
[Mageia-dev] sankore versioning (and naming) problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Sankore [1] has recently changed the name in Open-Sankore. Moreover i have a historical mistake i made e.g. the version is not 3.1 but 3.1 is part of its name, while real version is inside of its project (2.0 beta 10 at the moment). Now i'd like to fix it up, but i need some suggestions in how to work. Should i change the project to open-sankore and obsoleting the old one? (is that enough?) Or should i leave it as it is by now and add en epoch to remove 3.1? Any other suggestion? TIA, Angelo [1] https://github.com/Sankore/Sankore-3.1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7VdYACgkQqEs9DA4DquA/DgCcC15lIdsinUPHRyeDT+RYJzPU 49gAnAwVMHejJO9FynAdPOxCkuceL1TT =UcIt -END PGP SIGNATURE-
Re: [Mageia-dev] sankore versioning (and naming) problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/12/2012 14:59, Kamil Rytarowski ha scritto: svn mv over package name, spec name, Name tag, misc directory Add Provides: oldpackage-name and Obsoletes: oldpackage-name No need to add/bump Epoch. But I'm not sure that changing the name to open sankore is right, since the haven't changed the tarball name... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7YMIACgkQqEs9DA4DquCoIwCdEQfdgdo3KDCQsVmRKLCbUFWt tUoAn2LJOsP6k026BMlyz8fclT6MdUDR =oWNP -END PGP SIGNATURE-
Re: [Mageia-dev] urpmi --download-all --no-clean does not work any more
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I opened a bug report for that: https://bugs.mageia.org/show_bug.cgi?id=8272 Fixed tv, thanks Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlC7ra0ACgkQqEs9DA4DquBi4wCfSXlLzdUYOTVP4tONmrdQPnKh DSsAn3BrGQDqnpCbRTKQw/MidpN4+DoF =dxzD -END PGP SIGNATURE-
Re: [Mageia-dev] digikam updates problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Installation failed:file /usr/share/kde4/servicetypes/kipiplugin.desktop from install of kipi-plugins-1:3.0.0-0.rc.1.mga3.noarch conflicts with file from package kipi-common-2:4.9.2-1.mga3.noarch Can someone remove it from testing? it was a wrong submittion imo, and since we cannot have new libkipi we also cannot build libkipi without conflicting to the official kde graphics one. What do I do now? If you wanted to test hplip just select it alone:) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCkEWEACgkQqEs9DA4DquAvqACguV4uwuvW3vpyaCIK78BI2Dho CSQAoLskCqpHwKjsMH7DxHcf5XsbR07H =KGsZ -END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6435] Added a first log viewer module.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guillaume,
Il 12/11/2012 09:44, Guillaume Rousse ha scritto:
Le 11/11/2012 19:13, r...@mageia.org a écrit :
+package LogViewer; + +use strict; +use POSIX;
never load the POSIX module this way. Either import it without
importing any symbol in your namespace, either import just the
symbols you need. See POSIX(3pm) for details.
I thought it wasn't the right way, i just forgot to fix it.
This module is not completed yet, but feel free to work on it or
to any other module you want to port.
My basic idea was to show how an easy task like showing log could
work in qt, ncurses and gtk without changing the core code.
Again I'm not a perl developer and neither i'm pretending to be,
what i'm trying to, is porting some old programs to new layout,
but if that hurts someone's feeling i can stop working on it
and do some in c++ for what i need.
Funny from here:
[..]
+$::isWizard = 1;
ugly syntax.
[..]
+#- check services +my ) . Data::Dumper-Dump([ $service ],
[qw(*services)]) . q( +foreach (split(':', $options{SERVICES}))
{ +next unless $services{$_}; +$r .= Service $_
($services{$_} is not running)\\n unless -e
/var/lock/subsys/$_; +}
You shouldn't leave debugging statement in your code. Moreover, I
doubt this is syntactically correct. Do you use Test::Compile to
check your code compiles correctly ?
the above code is all from old logdrake, all commented and not
runnable, because i haven't imported yet :p
Cheers,
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlCgymsACgkQqEs9DA4DquDSBACggCiaEKouQ1s2wAFJHFmt1WBF
1joAoKFatBVmuK3ERVolx6B15XclNUtl
=qlDj
-END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6435] Added a first log viewer module.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/11/2012 10:06, Guillaume Rousse ha scritto:
I forgot this one...
Le 11/11/2012 19:13, r...@mageia.org a écrit :
+## Append a custom string to log view adding date +sub logText
{ +my ($st) = @_; +my $string = chomp_(`LC_ALL=C date
'+%Y %b %d %T'`) . . $st . \n; +# `` return non utf8
and concat of non utf8 utf8 is non utf8: +
c::set_tagged_utf8($string); + +# log given text +
$logView-appendLines($string); +}
It is especially ugly to call external date binary, whereas perl
has everything needed as builtin functions for this. See time
related functions in perlfunc(1), and POSIX::strftime in
POSIX(3pm) if you need a simple formation function.
Ok so you're offering yourself to rewrite all without leaving
any old code in new implementation :D
Anyway I understand what you mean, and i agree i will fix it asap.
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlCgy5sACgkQqEs9DA4DquDZ6ACeKl3WUjETSj6tFCXhTC9xox7W
BiQAn1sDo7GNTIdl7IgQu3q3UFrd/M3Y
=NCMa
-END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6435] Added a first log viewer module.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/11/2012 09:44, Guillaume Rousse ha scritto: Do you use Test::Compile to check your code compiles correctly Interesting, can you point me in how to use it? Thanks Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCgyBcACgkQqEs9DA4DquDTAQCguRf0pLX7hVyMVmCk4ojrIpiR LyIAnAp/bvAGZ4nllt/CnDAIfGulPNEy =B9ED -END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6435] Added a first log viewer module.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+#- check services +my ) . Data::Dumper-Dump([ $service ],
[qw(*services)]) . q( +foreach (split(':', $options{SERVICES}))
{ +next unless $services{$_}; +$r .= Service $_
($services{$_} is not running)\\n unless -e
/var/lock/subsys/$_; +}
You shouldn't leave debugging statement in your code. Moreover, I
doubt this is syntactically correct. Do you use Test::Compile to
check your code compiles correctly ?
Also /var/log/subsys is almost dead under systemd anyway. It's
still used by a few legacy initscripts that systemd calls, but I'm
not sure where this is going.
Ehm the above code is the draklog one, and it was use to create a
wizard to setup mail alert.
It's not implemented yet, in the new log viewer so any new input can be
added now.
Also, if you are implementing a new log viewer module, is this
going to use the systemd journal rather than implementing it's own
complex logic for parsing compressed text files? I've not looked at
the code, but it would be *awesome* if this is what was happening
:)
It's very easy to use the journal APIs (either by linking the
library, using python bindings - not sure if there are external
perl bindings yet, but I wouldn't be surprised if there are - or
simply calling journalctl on the command line and parsing the
result. It offers an easy to parse JSON format so even going via
this route should be trivial if official bindings do not exist).
You can get all logs between certain dates and for particular
services with ease, without having to look in the right file or
grep for the right binary. i.e. all the building blocks are in
place for you :)
I read your comment in draklog bug, i have taken a note and i will
ask you to explain it better to me, since i'm not very familiar with
all this stuff.
About binding, well libyui allows also to use python and ruby,
so rewriting my rubbish - quoting Steven :p - to re-implementing
another rubbish in python it could be possible and easy :D
Anyway, Col ehm you could help in this project...
...we will be very happy :D
Cheers,
Angelo (who continues trying involve people :D)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlCg5xAACgkQqEs9DA4DquCx1QCeN8xtJ06uUohpR0WpHzqYbbfI
xoAAn0KHEx34+MHXlr7J+hS6Jp4EGqCD
=aDG5
-END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6435] Added a first log viewer module.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/11/2012 12:49, Guillaume Rousse ha scritto: Le 12/11/2012 10:57, Angelo Naselli a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/11/2012 09:44, Guillaume Rousse ha scritto: Do you use Test::Compile to check your code compiles correctly Interesting, can you point me in how to use it? Basically, that's just a way to automatize of multiple use_ok() statements, when you have lots of perl modules. You can check module documentation on CPAN here: http://search.cpan.org/~egiles/Test-Compile-0.22/ And if you want a real-world usage (with lot of project-specific noise), check there: https://github.com/fusinv/fusioninventory-agent/blob/2.2.x/t/01compile.t I'll give it a look when i'm less tired... thanks. In the mean while i hope to have cleaned a little bit the submitted code. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlChb2AACgkQqEs9DA4DquBCRQCgjjaT5Noik2AHckM6J8T/M+l9 SsoAnA2GIiO3MNbS9oyJ7vU5Vf7dSwZk =JO/Z -END PGP SIGNATURE-
Re: [Mageia-dev] Admin Panel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Official announcement! \o/ We still need to do a fair bit on the core of Admin Panel I'd like to add a more scalable solution to load modules, so that modules are able to be added without the need to change core configuration, i will work on it asap. Anyway, I hope my contribution amounts to something eventually, and please feel free to join in. Yes i do believe modules are the biggest work, and we need skilled people here to port old things in. I think it's hard to port all, a lot of gtk hard-coded stuff is in our drak* code. So far i think, it would have been hard even adding qt to interactive... - From my point of view i'd like to add a thing to previous discussion (the one followed by the commits), I think we are an open community and as a community we are going on as big team, I haven't worked to this project because old tools were bad, just to try to give something more -in the hope is also better- to our distro. So every comment is *more than* welcome, but we need to be constructive, just saying this or that is bad it does not help and frustrate people work. In my personal opinion, I think we had some inter-personal problems in the recent past, and I strongly do not want to loose enthusiastic contributors... And now a little addition to the design, as said we use libyui, that project is open source and I'm contributing by adding what is missed or does not work for our purpose, so when someone is going to work on modules he can also help in contributing in libyui to make it very good for our aim... Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCaQrMACgkQqEs9DA4DquC4awCgrZyHjYI1UlJYG9mSFmQAh6d/ DE8AnRJ0BChlIUnxxFw97sk/Z3TUCOBC =E2V1 -END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6416] Initial commit of Admin Panel.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks Guillaume to have started reviewing the code :) As said I'm not a perl developer, so any help change and what else is appreciated. Now all is in our svn, so I, well we all, do hope in increasing contribution to make our little toy a real product. I won't comment perl adjustment since i just cutpaste some code to get my things running i'm leaving this aim to who in the group is more perl active :) +#Copyright 2012 Matteo Pasotti +# +#This file is part of mcc2 +# +#mcc2 is free software: you can redistribute it and/or modify +#it under the terms of the GNU General Public License as published by +#the Free Software Foundation, either version 2 of the License, or +#(at your option) any later version. +# +#mcc2 is distributed in the hope that it will be useful, +#but WITHOUT ANY WARRANTY; without even the implied warranty of +#MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +#GNU General Public License for more details. +# +#You should have received a copy of the GNU General Public License +#along with mcc2. If not, see http://www.gnu.org/licenses/. I'm not convinced of the interest of repeating license and copyright information in every single file, whereas a single top-level README file would be enough. Well isn't it required by gnu and common way of using gpl in programming? But perhaps i see your point the bigger is a scripting file the more disk space is using. I'm convinced tough than using a shared top-level namespace, for instance AdminPanel or Mageia::AdminPanel, would be a better idea to express the idea than this module is a part of a software, than a loose comment such as This file is part of mcc2. package Mageia::AdminPanel::Auth; Using a namespace could be a good idea, as said this is a simple toy at the moment. I'm not sure using Mageia though is right as well, it's been thought as a general purpose admin panel at the moment... BTW, your indentation isn't consistent between various files. well, ehm I think it's my fault, i use kde editor and i don't like tab. Is there any policy for that? I mean tab=8, tab as a tab and not space etc? Or we can use ours one and for all? Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCZJLYACgkQqEs9DA4DquDTCACfc1o+7lu/SwfXuMWn51MtSt4X u5UAnRehfRZUAkF94g03OirhxYsWMfC6 =wo6L -END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6418] using yui::YCommandLine only for all, at the moment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 06/11/2012 15:09, Guillaume Rousse ha scritto: Le 06/11/2012 14:28, r...@mageia.org a écrit : Modified: AdminPanel/trunk/apanel.pl === - --- AdminPanel/trunk/apanel.pl2012-11-06 13:22:23 UTC (rev 6417) +++ AdminPanel/trunk/apanel.pl2012-11-06 13:28:57 UTC (rev 6418) @@ -22,17 +22,14 @@ use diagnostics; use FindBin; use lib $FindBin::RealBin; -use Getopt::Long; use Auth; use MainDisplay; use yui; Why do you need FindBin, instead of a proper installation procedure ? I guess you ain't commenting my commit here :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCZJeIACgkQqEs9DA4DquDJ7QCgu9y3xL3CEcPlzbQbnFYJ002V Y6IAoJRDMkGI2YlHc77NH5tNTXiOK+fM =ExTS -END PGP SIGNATURE-
Re: [Mageia-dev] [soft-commits] [6416] Initial commit of Admin Panel.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 06/11/2012 20:55, Guillaume Rousse ha scritto: Come on, you really think someone will sue you because running your code crashed his system, and you have to be that safe ? It's a pain to have to skip multiple lines of legal bullshit before reaching the code, and you'll need to update a gazillion files in just a few monthes because we'll change year. Good point, can we have a policy for that? So that all of that we produce in mageia is going to be under the same philosophy... I cannot follow the meeting in the next hour but it's a good point to discuss i believe. In the mean while i changed (an i'm going to commit) the indentation now, if i'm not mistaken in something, should be all the same tabstop=4 shiftwidth=4 expandtab hope that is not going to be wrong for anyone :) Cheers, Angelo (who's waiting for any contributions in adding modules) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCZb30ACgkQqEs9DA4DquB2SACeKCAm+AYwgmnQMEGXeNgaoS5s 6GEAn0zlWuc8/YHdRatZhdCB7TIOAdce =a1/p -END PGP SIGNATURE-
Re: [Mageia-dev] Welcome Götz!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 22/10/2012 23:15, Olivier Blin ha scritto: Hi, After uncountable years as a packager and maintainer in the Mandriva Linux distribution, providing a huge number of impeccable contributions, Götz Waschk is now joining us as a Mageia packager. Please welcome him aboard! Awesome! Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlCGSaQACgkQqEs9DA4DquBX1gCdER3K7PAd29OLMle+sccEWR1q SF0AmQGaX7nZRE5tTFcmIR8uV2GtozYO =hKW/ -END PGP SIGNATURE-
Re: [Mageia-dev] Update to KDE SC 4.9.2
Let's have fun :p Please patch kdegraphics. So that we could also have fun using digikam :p Angelo
Re: [Mageia-dev] Update to KDE SC 4.9.2
Il 14/10/2012 23:17, John Balcaen ha scritto: Hello, Since alpha 2 is out i'm now going to push KDE SC 4.9.2 on cauldron There's also at least 2 regressions : - for kopete , the otr support will be not build since it does not support the last version of otr pushed a few days ago. - for kalzium, since facile was not rebuild against new ocaml the equation solver won't work. I'll also push later telepathy-kde 0.5.1 too Does it contain new libkipi (for digikam 3.0.0 from gsoc 2012) in kdegraphics? The digikam problem found for desktop file conflict, is not upstream, it has just been added by using internal kdegraphics building. Cheers, Angelo
Re: [Mageia-dev] Update to KDE SC 4.9.2
no new libkipi will be provided with kde 4.10 ( so the 21st november ). So how can we handle it? we need to decide which one to ship in the mean while, or we cannot use last digikam and co.
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'd like to recall next point: 1/ What should we call it ?? I have been using mcc2 as a working name, however I'm not convinced this is the right approach. I will soon be uploading the code (been using my own svn repo up till now), and it would be good to start with the name it will stick with. Should the name relate to Mageia?, or should it be more generic? It's very important, after that we can start sharing the code in our repository (as soon as tuxta has been granted to commit :) ) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBpSQAACgkQqEs9DA4DquC0GwCfRbD66sEaUu5krjYE7xShrIc4 nHYAnjEb6gwGz6E5Zgj7Abn0hjbmRrsA =w2yV -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 01/10/2012 10:53, Steven Tucker ha scritto: 6. Mageia Control Center -- mcc -- until it replaces the existing one - mcc2 or mcc-new or mcc-libyui I think that one it should be used as a link anyway after, so that old users like me can start the panel from console in the old way :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBpYT8ACgkQqEs9DA4DquAMjgCbBKGaDQ8dwHMW34eqVOj4+2JT zfAAn30WuFPlug24D/2ND/MTXmuhFkTw =azDe -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pardon me for jumping in although I'm not a developer. I agree that for the time being (as long as the old mcc is in the repos) a different name is unavoidable, even if it's just mcc2. But when a switch to the new version this new version should inherit the name Mageia Control Center/Centre. The main reason for that: This unique type of configuration mall has been one feature which has been regarded as one of the most valued of Mandake/Mandriva/Mageia in all reviews and all comments about the distribution. Over 10 years it has been a recognized landmark for these distributions. As such it should remain under the same name. The name will neither make it more difficult nor more easy for other distributions to use it (as has been said in this thread), we also have tools or whatever adopted from other distributions (like Fedora) and they are still carrying their name, even with fedora as prefix. Good point, but as a developer i could say we can make it configurable. I mean a generic panel can have the name into its configuration file and shown on title, while to run it a script called mcc can run generic_panel -c mcc.conf for instance, we can also fix that as default forcing mageia behaviour :) Said that we're using libyui, that is a work in progress abstraction for the Suse Yast panel, so we're not reinvent the wheel :) Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBpYvgACgkQqEs9DA4DquC+cwCfVLbciOqfinwPQcNgpnBTHdZc MUIAoLO6Nx95I4fcGpeBA9QF8UJfJfb5 =etxn -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 01/10/2012 11:48, Wolfgang Bornath ha scritto: May be I misunderstand this sentence, but the new mcc will not carry any yastish ingredients or behavior? (From SuSE 4.4.1 on until today YaST has always been one outstanding reason for me to not use SuSE) Well the libyui should not have been related to yast only - From git repository: libYUI libYUI is a library written entirely in C++ to provide an abstraction layer for Qt, GTK and ncurses UI frameworks. This means that a single code in YUI can be used to produce outputs using any of the 3 UI frameworks listed above. This library was (and still is) used to create the YaST2 User Interface. So the answer is no, but since it is work in progress, something could not work as expected yet... Said that i'd expect a pro-positive approach to this thread, we're an open community and things change in the hope they improve in a better way. I recall that this project is explained and approved here: https://wiki.mageia.org/en/Feature:UiAbstraction4mcc Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBpfMEACgkQqEs9DA4DquB8sQCgrQ2/ucCmqPaeJGwhz4niRFYQ e1UAoItYuQGhDC1GiuazQYj6vIxVYsV3 =BEWv -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 01/10/2012 14:18, Wolfgang Bornath ha scritto: @Angelo: My question was not a sign of negative approach, it's only that YaST is one of those words which make me shiver! :) And mine was not referred to you only I just used your mail to say that ;) What i meant is that Steven has worked on this project and Matteo and me helped him in some little tasks, so we are not suppose to approve the project again, just ask how to go on... Certainly it's not ready yet and we hope people will help either in developing or in ideas, bug hunting, module porting, etc. to build a good alternative to what we're using today in the hope that it could be so good to replace it also :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBpjK0ACgkQqEs9DA4DquDT6wCfQwt+htatwapWqg2/Pstdq3rj wNYAnA7OGUFJAelHbhG047z0iYStyxaZ =DOnN -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please use Gobject Introspection so that we could have both gtk2 and gtk3 version. Sample code on display_help here: http://svnweb.mageia.org/soft/drakx/trunk/perl-install/standalone/display_help_gtk3 As for qt version, I don't think you could deal perl and qml+qtscript at the same time. They are very different. As said we're using libyui[1] as abstraction to get ncurses, gtk and qt layouts. Angelo [1] https://gitorious.org/libyui -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBoBBsACgkQqEs9DA4DquDkhQCfcebJYAh5W6Hv5AkpRhK2E3NE rBoAnjivDnXIn8F6Rm6P9T0PJwI8NIKS =VV0S -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 29/09/2012 21:56, Olav Vitters ha scritto: Suggest to figure out language is most preferred by the potential contributors, keeping in mind how much contributions they'd likely do. If that choice is not Perl, keep in mind that development will probably take way more time. Well libyui allows to use perl, python and ruby iirc as script languages, but also C++. I think C++ could be accepted since api breackage is seen only after a rebuilt, abi breackage is another story, but they should be only due to libyui issues... I think perl is mandatory for historical reasons and to get some code reused i hope. Then any contribution is welcome and if no one can maintain the code it will be removed as i think happens today for any packages ;)... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBoBZsACgkQqEs9DA4DquDNRQCbBw0xNkZIVn68PMMcJyis+xTf YkIAn3H6RePV946ksnV3QTt1Jn3S4n8T =/Z2k -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nicolas, i don't see the point of this rewrite. This have not been discussed a lot but i think that this is a lack of time. For me the prior thing to do would be to write a interactive::qt for mcc using perl-qt4 or perl-kde4 As you know i followed both ways, and i wasn't alone, i did it with the help of Matteo (aka pasmatt). The task you suggested was not that easy, we shared some code Matteo wrote, but we could not reach any qt/kde working interfaces. If you think that is the right way, and that was discussed time ago in Mandriva also, why has no one reached the goal? I think because it's not easy, code has been written to work for gtk in mind for the most... I think that if you want to write it in an other language this is more because you have not saw that all our code is linked so you will double the code base, the code to maintain, the possible bugs, etc etc. No that is not true, we don't want to use another language we just considered to have also plugins written in other languages. They could be run as a single applications maybe, and also inside new mcc. you will upload it where ? you can use a github repo i think to make it public. That is a possibility, yes. But if its goal is to be just a *mageia* control center, well... why not to have it in *our* repository? yes but our libraries are in perl too don't forget this ( libDrakX ). In general i am not a big fan of mixing languages. and only perl is, at the moment. Big goal is to get our things integrated. But what we can re-use is in next goal, and i do hope help of other contributors here... As mcc is in gplv2+ i think you have to stick with this licence ( not 100% sure ) I think that's right, in such a case we won't have any problem in (re)using existing software. libyui has been choosen w/o real discussions, i don't want you to loose you time if at final we don't choose it. That is not true. https://wiki.mageia.org/en/Feature:UiAbstraction4mcc (This page was last modified on 27 June 2012, at 22:22.) What i recall clear is that this task was proposed a lot of time in past, but nobody did it... Why blocking who started working on it? better work would be to fix existing one and add new interactive::qt ( or qt4 ). And seeing the != between qt4 and qt5 the port to qt5 will be a 'piece of cake'. you know i tried and i also tried to be helped by someone of our community, but as we're all busy in real life and we cannot do all, and we focus on what we can really do, i think Steven has chosen a right approach. He always said it's not for mga3 most luckily mga4 ;) Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBoDZMACgkQqEs9DA4DquAYWQCcCgFK/zLx/EKlkZ07/lXVQPHi Ec8AmwZBQCCVCvMbZVF75U/OUZhd7spe =HkL/ -END PGP SIGNATURE-
Re: [Mageia-dev] The shiny new Control Center
Well, the core is a full rewrite, so potentially it could be licensed any way I choose. The modules however are planned to reuse code to save time and so they would have to respect the existing licenses. When asking about licensing, I am referring to the core, not modules. Well, modules could have license problems in some cases... so the choice for the core is itself important i believe. Angelo
Re: [Mageia-dev] The shiny new Control Center
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 30/09/2012 20:03, nicolas vigier ha scritto: On Sun, 30 Sep 2012, Steven Tucker wrote: you will upload it where ? you can use a github repo i think to make it public. Currently I am using a university server with svn and Redmine, and I am completely happy with it. I was going to move it to the mageia repo so that people could see the program as it progresses, and perhaps even contribute if they feel motivated to do so. If anyone is interested they can let me know and I'll create them an account, Angelo and Matteo already have full access. I think it would be a good idea to have it on Mageia svn. Well to be honest that has been already discussed via irc, and it seems to be as you said a good thing, the real question is how to call it :) I've thought for a while to generic control center, but I think developers and packagers are not very happy to manage the name conflicting with gcc :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBoi9wACgkQqEs9DA4DquCDlwCfQFZQ40JMW8LjI6jcm6JO0gaC cPIAnjmfMYb7H60p+O3DR43fQ+Xlk7Ka =0AWm -END PGP SIGNATURE-
Re: [Mageia-dev] autogen.sh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 19/09/2012 10:55, Oden Eriksson ha scritto: Hello people. Someone was wondering why i added autogen.sh in libxslt. There is a reason for this after long time maintaining open source softwares. See it as a last known good way of using the autopoo stuff as done upstream. If autoreconf - fi should ever fail in libxslt use the provided autogen.sh file. These files tends to disappear or be moved to the upstream release managers private hard drive only, or something like that. It's simply wise to keep autogen.sh for ourselves for reference. If you don't need to use it, fine, but keep it. I'm not against on having stuff that simplify our life in building packages, but i have a question what does autogen.sh that does not work with the standard sequence (more or less always the same)?: libtoolize aclocal automake --add-missing autoconf Just wonder... Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBa3J4ACgkQqEs9DA4DquAqEQCeK3H5KHMEzOS6qooWMn8puYI6 028Anj4jlWlO4l2suPdtQOwAHl8r8k5I =44Mc -END PGP SIGNATURE-
Re: [Mageia-dev] unity on mageia
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 14/09/2012 21:03, Damian Ivanov ha scritto: There actually only the unity packages needed to be compile against it (which is no problem compile only these programs against this patched gtk3 with a separate OBS project for unity :) ) hmm but if not statically linked you need to have both libraries installed the patched and the official ones... I meant if wouldn't be possible to install gtk+2 with ubuntu patches inside a different prefix (like /opt/gtk+... or your preferred one) and only compile applications that need that patches against that special gtk+ version ;) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBThxYACgkQqEs9DA4DquDgPQCgir9vco2tsc3LrbVVf+uHFJpZ nkkAoKd6KE8S2oFvLpCbqPb79Z2vCdJN =N7xi -END PGP SIGNATURE-
Re: [Mageia-dev] unity on mageia
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 13/09/2012 14:08, Damian Ivanov ha scritto: I am not talking yet about getting unity included in Mageia, but to have the repo that is available for openSUSE and Fedora users available for Mageia too. Add repo == Update == install unity You mean using opensuse build system? As far as i can say adding the availability to build also mageia packages could be a good thing. As far as user concerned though, using different repositories that are not officials could be dangerous. I'd prefer to have contributor in mageia instead... That does not mean that you can't go on and maybe contribute to mageia as well after... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBSNPcACgkQqEs9DA4DquAitgCfZmSjC12LB6P6go3E20Q+Pw/y 9Y0AoLDmH+qEx66dXItH4z08rDQSVFqJ =xNbL -END PGP SIGNATURE-
Re: [Mageia-dev] unity on mageia
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it should be even more safe than directly in the distribution. 4 distri maintainers watching the same sources and patches and one place. all that glitters is not gold... It's very hard to have a unique spec file, rpm macros, package names, etc are often if not always different, but i see some good things following libyui project... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBSP30ACgkQqEs9DA4DquCImACgko5rvGzGT8YnIxfGzGx7MPqG VPQAn0kndcDNYYRN6ksUfrl1clhLhv3G =UN/p -END PGP SIGNATURE-
Re: [Mageia-dev] [alpha 1]HP Deskjet-F4280 All-in-one
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/09/2012 09:57, Thierry Vignaud ha scritto: It may be obvious for the maintainer but not for other packagers. but other packagers are very often -if not always- maintainers of other packages ;) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBQTiMACgkQqEs9DA4DquC86gCffCjRAJvnrTtRvIWtba6uA3L7 ACoAn3d+nOc/u9flKXJ866udKEWKJ/IA =ScsX -END PGP SIGNATURE-
Re: [Mageia-dev] [alpha 1]HP Deskjet-F4280 All-in-one
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 11/09/2012 14:55, David Walser ha scritto: Good to know we can look to Fedora in the future for fixes, since mdv seems to be all but dead now. Well we've done it (looking at Fedora's fixings, as well as upstream), since mga1 really... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBPSg4ACgkQqEs9DA4DquCJIQCgmHA6MQ6LOep6+/CHgF+2klKH uHUAnR6lLbtk9igusWZ4UMkirbn7jb8q =sZe0 -END PGP SIGNATURE-
Re: [Mageia-dev] Cauldron display broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 i had to boot again with the vga monitor pluuged and set the output to my notebook display again. After that it booted ok. And i didn't use mcc, but just krandrtray settings Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBG99YACgkQqEs9DA4DquBYGwCgmjuaYIIuPtEuJDp1yqATFPKc VfEAnRTzgLMondrMSisdCjyBWfqEx6kF =aMcZ -END PGP SIGNATURE-
Re: [Mageia-dev] Cauldron display broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 03/09/2012 19:40, Anne Wilson ha scritto: For some reason it refuses to forget the VGA setting. In MCC it tells me that there is no VGA screen output active, yet the screen image clearly shows a ghost-like VGA image underneath the LVDS1 image. Is there any way I can get this back to a workable situation? hmm just a shoot in the dark, i experienced a similar problem in mga2, i think it was related to kde and its settings because i had to boot again with the vga monitor pluuged and set the output to my notebook display again. After that it booted ok. HTH, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBG9uwACgkQqEs9DA4DquB96QCeKoaQYz02pHa3bFBu+i6M5Y6y iUgAoI9gM4rpRE1u4hHMnoByYq7HliSv =nalr -END PGP SIGNATURE-
Re: [Mageia-dev] [RFC] kdelibs4-devel and cmake macros
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/09/2012 01:46, Balcaen John ha scritto: I guess he's talking about the .cmake macros available in /usr/share/apps/cmake/modules/ yep :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBDDs0ACgkQqEs9DA4DquD6yQCfdHO6t3JZffXI+8rcDdb5Eb31 MV0AnirWPbC1JHB2nROMYHySJUlYU/C0 =XvS3 -END PGP SIGNATURE-
[Mageia-dev] [RFC] kdelibs4-devel and cmake macros
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I recently had to work with some cmake macros and i found that they were already on the system installing kdelibs4-devel. I am a KDE user and developer so it's not a big problem for me, but some colleagues are not. Now isn't be possible to have a kdelibs4-cmake-macros package? I think that can be useful for those who don't want to install a lot of kde developer packages and get benefit by using already developed macros. WDYT? Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBCAUsACgkQqEs9DA4DquD1rQCfdfcIvzpT33dkZy2Bm3gBsnay A5UAoKv/Vdl+HngbLHTuwMXQOu4Arur4 =Wn6h -END PGP SIGNATURE-
Re: [Mageia-dev] [RFC] kdelibs4-devel and cmake macros
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 01/09/2012 16:48, Colin Guthrie ha scritto: This doesn't sound like a good reason to me. Surely any porting work you'll be doing you'll want to push upstream. Would upstream be happy adding a dependency on KDE macros? I wouldn't expect so. Thus the approach you've taken just now seems like a good one. Good point. But the real good approach in my opinion is that kde team should send upstream -to cmake- their macros. I don't like to reinvent the wheel, and moreover what happens as soon as someone develops a library for developers and need the same dependencies as in KDE applications (SQLite, SANE, SIP, RUby,...)? Two FindXXX.cmake on the system. I'm not sure it's good reason as well :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBCX6YACgkQqEs9DA4DquDH4ACgrUnCYKEZqO8YalLdufCLJt5M UFwAoJz1ZQqEE3VtYcNdQFLyRdVzXZoY =tWvW -END PGP SIGNATURE-
Re: [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 13/08/2012 14:23, Maurice Batey ha scritto: But I can't move over from Mandriva (KDE 4.5.2) to Mageia until KMail's Find Messages is back to normal. I'm not sure but finding messages should managed by nepomuk now (another thing that on my amd X6 takes 95% of cpu for indexing :/ ) and as far as i know it works... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAo8v0ACgkQqEs9DA4DquCWcwCdGUGZmgLPoBSFP04nXaTPW0sk GlsAni+oinRvzqvppDRF/hbY5A5D6R7v =hTip -END PGP SIGNATURE-
Re: [Mageia-dev] madwifi-source package ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 13/08/2012 12:54, Guillaume Rousse ha scritto: We have a madwifi-source package, which seems to be used as a build dependency only from wpa_supplicant package. Mandriva used to also have a madwifi package which wasn't imported. Given than madwifi support currently prevent wpa_supplication 1.0 to build (conflicting types declaration for ‘u_int64_t'), and than we seems to be perfectly happy without madwifi driver package in the distribution, is it reasonable to consider than: - we no longer need the 'madwifi-source' package ? - madwifi support in wpa_supplication isn't needed anymore ? Well I have an old dlink card that used madwifi and that i'm not using any more at the moment, I could try it again -when back from holidays- with the free driver and see if i have any problems and eventually going back on this subject. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlApDXEACgkQqEs9DA4DquAORgCfe3FotK6fpppBCxmPSRDO1ARf t1kAnRAOCtwCyJVksitlL6Qs0J4NV2Lk =k9EJ -END PGP SIGNATURE-
Re: [Mageia-dev] madwifi-source package ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 13/08/2012 16:23, Guillaume Rousse ha scritto: Le 13/08/2012 16:21, Angelo Naselli a écrit : Well I have an old dlink card that used madwifi and that i'm not using any more at the moment, I could try it again -when back from holidays- with the free driver and see if i have any problems and eventually going back on this subject. The point is: what other alternative do you have, as we don't seem to have any madwifi driver package in the distribution ? Well as said i'm not using it any more, so i hadn't noticed that :) I always built drivers by myself in past, iirc it has not been always available in mandrake repositories just in the recent past... The point is also if we have any other users needing it and, can we support all old hardware? I'd like that, but i think it's not always possible by our resources... am I wrong? Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlApDxEACgkQqEs9DA4DquDQDACeOwK9dSOdNKI/89srYsjfdBq+ naMAn2mcu5bdelDptIWbU9KZdfc1hzzx =QpMJ -END PGP SIGNATURE-
Re: [Mageia-dev] File location in mono packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/08/2012 10:28, Bersuit Vera ha scritto:
Hi Nico: rpmlint says warning: hardcoded-library-path in% {_prefix}
/ lib
A library path is hardcoded to one of the Following paths: / lib, /
usr / lib. It
Hmm are you sure? I'm not. They are noarch for the most, and
for any lib64 you add, (using %libdir) you also need to patch
Makfiles co...
Maybe we can consider a different solution for the future,
but i don't think patching all to get rid of rpmlint is
the best one...
My 2? cents
Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAney4ACgkQqEs9DA4DquBLiwCgqP8/BxMmimSGoWJjQOrUutlM
AXYAn1QEylhnLPmqmb8KaH2IZcDzsMV5
=yAQI
-END PGP SIGNATURE-
Re: [Mageia-dev] File location in mono packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 12/08/2012 11:45, Angelo Naselli ha scritto:
Il 12/08/2012 10:28, Bersuit Vera ha scritto:
Hi Nico: rpmlint says warning: hardcoded-library-path in%
{_prefix} / lib
A library path is hardcoded to one of the Following paths: / lib,
/ usr / lib. It
Sorry I missed this line in replying:
Should Be Replaced by something like /% {_lib} or% {_libdir}.
Hmm are you sure? I'm not. They are noarch for the most, and for
any lib64 you add, (using %libdir) you also need to patch Makfiles
co...
Maybe we can consider a different solution for the future, but i
don't think patching all to get rid of rpmlint is the best one...
My 2? cents Angelo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAne5EACgkQqEs9DA4DquAnYACggjNd03kw0GBJ/Prqpv+AVbzX
9d8AoKkP23pScTbYiC1I/nsM/+Jwlyet
=p+tt
-END PGP SIGNATURE-
Re: [Mageia-dev] Mass rebuild?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 11/08/2012 19:25, Sander Lepik ha scritto: Alpha 1 is getting closer and closer but still no rebuild. AFAIK we should have all major packages in for now. So what is stopping mass rebuild? :) Even if there won't be any mass rebuild before alpha 1, can maintainers please check their packages from this list: http://check.mageia.org/cauldron/dependencies.html - some may need just a rebuild. I will take care of my packages as soon as I'm back home from holidays, if no mass rebuilding is done. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAngdAACgkQqEs9DA4DquCTnQCfV3T5zQYhz+CRRLUOxiezaSAo 8XQAn1TLCPId5Ih/l6qaKX1zAVzPfhAG =7gS4 -END PGP SIGNATURE-
Re: [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 12/08/2012 20:12, Balcaen John ha scritto: Well it's working better with kdepim 4.9.x (not perfect thought) kmail 1 was not perfect, but worked well for the most (or at least for what i used), kmail 2 is a disaster :D. You know i tried to stay, but loosing mails, not working filters, multiple imap and pop accounts mess, always on line with errors if use in a notebook off-line... I could not use it at work... so i had to test a migration to thunderbird, and i did it at home first :) Anyway I'm ready to see if a way-back is possible... let's see ;) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAoCSYACgkQqEs9DA4DquBpcQCfSBdLUGwTzmaY9tsPuUuKA4RZ CGIAniRCy5a9+5gUdVcMJZWlzc021uU8 =Uw9X -END PGP SIGNATURE-
Re: [Mageia-dev] ANNOUNCE: The /usr move cometh! ---- Instructions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 23/07/2012 11:49, Thierry Vignaud ha scritto: On 22 July 2012 03:36, Thomas Backlund t...@mageia.org wrote: after you have installed the latest dracut, regenerated the initrd, booted with rw rd.convert, and the system is up again, just do a second urpmi --auto-update and it will install the rest of the rpms that now depend on the /usr move. What about chroots? If I understood correctly you have to install new rpm (for stable is in update/testing) i had to in mga2, to use iurt for cauldron as well. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlANH4oACgkQqEs9DA4DquCJKwCgrVd7a2SDjrUtjmx90rdb4BnV ZqsAn114cv0wqfoArCuU3oyZ1I2bjJIU =JZFW -END PGP SIGNATURE-
Re: [Mageia-dev] ANNOUNCE: The /usr move cometh! ---- Instructions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hmm, filesystem rpm won't install anymore so you won't be able to update your cauldron anymore Yes exactly. [...] It's two very simple manual steps which I do not think is beyond the skill set of anyone running cauldron, nor does it take much time. So if someone is on vacation now, has to install all from scratch? Can that(those) package(s) remain(s) available for a while or in e different repo to allow lazy people like me to update all their vm or real machine that maybe are not in the same place? :) Thanks, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAMGMgACgkQqEs9DA4DquD3YgCgnS8Sg8djzTbfpIsxtiFbKb+j QEcAn2RQtfXRX2QQu2A15IbhbBSqpHwj =5Q/Z -END PGP SIGNATURE-
Re: [Mageia-dev] Tonight's meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 18/07/2012 14:35, Anne Nicolas ha scritto: Hi there A short meeting tonight, here are the topics - Finalize Mageia 3 features - Avoid orphan commits in svn As usual feel free to propose more topics. Cheers Sorry i can't attend the meeting tonight. About the feature i'm involving in, we've started worked (well tuxta actually) on it, i'm porting libyui. Maybe if needed we can talk about it next meeting or by mail. Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAG4oAACgkQqEs9DA4DquAP+gCdGPqbG4TQCgpp/YFyCrLJ691o +5UAoLRbd3LU9PmcTJQ9UW3uiPvDGnrp =xmsf -END PGP SIGNATURE-
Re: [Mageia-dev] gphoto update for MGA2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thoughts? I'm always in favor of those updates that make our life better :) In this case we can also consider that mga2 is pretty young and that hardware would not be supported until mga3... so yes for me. Let's do all the needed tests and go. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/4HRcACgkQqEs9DA4DquBywACgidaZQejbGlXrzM7eX+ckJqPj pEoAnjYWpgXgFZjkYsF0Hd2LowryCrpp =urA+ -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I think MCC2 should just be seen as an experiment until there is enough done that it actually looks like a usable tool. Even the planning is just a fuzzy idea, no concrete plans yet. I think this should be considered as valid. I'm in favor to have a branch that could be delivered as an alternative to mcc in mga3 if we reach the goal to have a stable and not complete moving. So not a replacement but a way to the future. In the mean while i'm looking for the alternative proposal as well that could be helpful in any case. About coding, Steven if you have in mind what you want as ui, we can ask for the svn branch and start sharing the task. I cannot say i have 24h a day free, more likely some a week (at night for the most) but what i want to say is you're not alone and the project is big. About libYui, i got in touch with the main developer, and told me there is a IRC channel #libyui and git project on github is very active at the moment, they are very happy to get feedback and patches from other distros, (they also moved to cmake) but the next milestone is after yast will be fully adapted to libyui. So we could consider to have git version of libyui to have all up to date and fixed. WDYT? Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/2m6sACgkQqEs9DA4DquDgXgCeKm+r5cb9DCp5m0L1zG/f4eQa FSQAoLmbxdrbOleww0gj9EHmzPFBYXJR =Cu/5 -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Il 05/07/2012 10:59, Marja van Waes ha scritto: On 28/06/2012 00:02, Angelo Naselli wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm back to this subject, because, as you probably know, the proposal[1] has been accepted snip and has to be merged with mine[3] and discussed a bit to understand what we have to do and who can help. [1] https://wiki.mageia.org/en/Feature:UiAbstraction4mcc [3] https://wiki.mageia.org/en/Feature:DrakXtoolsReview Hi, Documentation team is planning to write the currently missing help for MCC and all the tools in it. We don't have a clue whether the above feature proposals, if implemented, will make a difference to what we have to do, and if so: what difference. As far as link [3] is concerned the idea is to add qt4 and maybe kde4 front-end to mcc also, so nothing should change either on functionality or on options/programs positions, just the availability to have a more kde friendly look. About link[1] the idea is not mine I'd leave Steven talking about it better. As far as I understood functionalities should not change and the hope is that either the mcc look for the most, but that depends imo on how the interface will be implemented and how we will able to add what we have now, since i believe we can't re-write all... Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/18TsACgkQqEs9DA4DquBdYQCgt3Br62AUTlMx/GKpFFjjpho0 j64AoLFDbnqSukxM7HzoEWc4O9yHL9qd =0PH4 -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Il 02/07/2012 04:24, Steven Tucker ha scritto: I have had a play with libYui that is in Cauldron, so using C++, to create a window and buttons. Ready to get going on the real code, but waiting on the Perl bindings to hit Cauldron. A little question here, libyui on sourceforge seems to be stopped at release 2.21.1 -about one year ago- and OpenSouse ships 2.21.4 but they call it as yast2-XXX, git repository does not have any way to build from source but using y2tool, i have a opensouse vm, so i could try to start from there, but is that the right way to move? I mean every time we have a new version we should have an opnesuse machine, or better we should understand if libyui is dead? Maybe forking a y2tool? I'm a bit confused Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/xhMgACgkQqEs9DA4DquALfACglNsXofdxsIzBSlwbcpzaUu+y 9X8AnRzWN8SDj9o6sz/04dXU7yC374uL =T4Rw -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/07/2012 13:23, Angelo Naselli ha scritto: Hi, Il 02/07/2012 04:24, Steven Tucker ha scritto: I have had a play with libYui that is in Cauldron, so using C++, to create a window and buttons. Ready to get going on the real code, but waiting on the Perl bindings to hit Cauldron. A little question here, libyui on sourceforge seems to be stopped at release 2.21.1 -about one year ago- and OpenSouse ships 2.21.4 but they call it as yast2-XXX, git repository does not have any way to build from source but using y2tool, i have a opensouse vm, so i could try to start from there, but is that the right way to move? I mean every time we have a new version we should have an opnesuse machine, or better we should understand if libyui is dead? Maybe forking a y2tool? I'm a bit confused Maybe i was to quick... on github they are using cmake... i'll investigate a little bit better... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/xkKIACgkQqEs9DA4DquCBCQCglhDrNHgsaI3uhWd4K12HO9Tg XlYAoLSghcrBZj2n+RO92+VD+UAoKrUm =wchq -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/07/2012 16:09, nicolas vigier ha scritto: It seems their intent is to make this library completly independent of Suse technologies : http://nbprashanth.wordpress.com/2011/08/18/libyui-ported/ So it should build on non-OpenSUSE machine, and if it's not the case you can probably ask them for help. And their git repositories on github seems to have the latest versions tagged : https://github.com/libyui Yes Nicolas, i so github, master is not builtable yet at least not all and not for me at the moment, i'm trying to get in touch with developers... At the moment we built an old version of libyui-ncurses, at least we can start working on the project :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/xxKAACgkQqEs9DA4DquB7iACgpmKMlNxnXclMUdELhvck0Ltp ljoAoLFWx7y4RadM+g6ixSMY5itTrnnn =R3cF -END PGP SIGNATURE-
Re: [Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 02/07/2012 10:09, Matteo ha scritto: Hi all, I had no much time to work on the perl binding for libyui during the past week. I was working on the libyui-ncurses package (-qt and -gtk are already available and working) but I encountered some difficulties and now Angelo is helping me so I can start to port libyui bindings. Regards And they've been uploaded. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/x/y8ACgkQqEs9DA4DquDCrACgpQ9b1QhN20f8csFoKPcUEmH/ zSIAoJuNdo1zb0gQiM9HOXXjwjZQ/LWI =83yd -END PGP SIGNATURE-
Re: [Mageia-dev] Backports Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 28/06/2012 04:00, Johnny A. Solbu ha scritto: No, it is Not obvious. It is called Backports for a reason. It is software that is not part of the release, and is to be treated as experimental/beta software, as it could wery well break your system if you don't know what you are doing. This is *not* obvious as well. It's not written anywhere that should be experimental, with beta/alpha programs A backport is just something that is not part of the release, yes, but also that should not be get through update. There's no reasons to talk about backports in fedora probably, since all goes to update for the most, our policy says (or will do) what can (and what can't) go to backports. Said that, backports have been approved last night meeting, let's talk about bp subject again in case of problems (that of course we won't have since we're very good at :D ) Cheers, Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/sFMYACgkQqEs9DA4DquBjQQCdEc0gSDF5eRvSVQ8iV1U8RnA/ BFAAn1IaPt75SVVCcNarlHYEK0t9EU63 =0vqO -END PGP SIGNATURE-
Re: [Mageia-dev] Backports Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/06/2012 10:23, Thomas Backlund ha scritto: It's not supposed to be flagged as an update repo as that would make it upgrade all packages it find in the system with matching backports packages. Why not? Just let the user to decide, who does want it, just enable it. Who wants cherry-peeking it just enable the bp repo and disable it after. The real problem is how to make people understanding that a bp has been released as bug or security fixing of an already backported package... No problems if you enable bp as updates, while you have problems if you cherry-peek a package... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/q2U8ACgkQqEs9DA4DquCFawCdHTQXC0L4cxQCgEo8a1relOyc ZEIAnibkaY/4PAlvpHmfsKCyu2LECDzZ =pf4G -END PGP SIGNATURE-
Re: [Mageia-dev] Backports Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/06/2012 10:23, Thomas Backlund ha scritto: And there will still be some advisory notifying people of new backports, just like we do for security and bugfix updates now. This could solve my last :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/q2aUACgkQqEs9DA4DquAOtQCeOhh3fe50vUIXtJvZT8BU/EpR +XsAoJnQTSCYSJ6vOQKhXdZ2NViCnXkb =0tRa -END PGP SIGNATURE-
Re: [Mageia-dev] Backports Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/06/2012 12:46, Thomas Backlund ha scritto: I would favour tagging backports as update repos, so that in the event of a newer backport for security or bug fixes, that it will be automatically presented with other updates. No. as the update applet currently works it would show the backport as an update even if you dont have an earlier backport installed, defeating the purpose of having separate /updates vs /backports hmm, only if it is enabled as update by default. Again, let the user decide, he knows if he wants all the backports (and updated) or just cherry-peeked | Enable | Update |Type | | X||Backport | or | Enable | Update |Type | | X|X |Backport | Usually Update is blocked, but once it was clickable by User I know we can change it by editing configuration files, I propose to let the user enable again it at least for backports... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/rCFcACgkQqEs9DA4DquBHuACgn5YzqworNBED2KzOJBt5MDrm T7YAn1bRhX29i1d9CwXCbi3RaU1Vuzzt =0qjS -END PGP SIGNATURE-
Re: [Mageia-dev] Backports Summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/06/2012 15:41, nicolas vigier ha scritto: There is no guaranty that requirements of version 14 mga1 backports are all available in mageia 2. If it is linked with libsomething.so.1, but mageia 2 only has libsomething.so.2, then there is a problem. Our library policy allows both libraries on the system, so even if not upgradable well the system should continue working anyway... Or upgrading, packages will be removed cause of their dependencies... Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/rHwwACgkQqEs9DA4DquCDMQCfc6LXmgO4N9LnCMeO+uabJNAL 8JcAnRKPU6PUhu4jl6k7SY5FMqqv93e7 =j6EP -END PGP SIGNATURE-
[Mageia-dev] UiAbstraction4mcc feature proposal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm back to this subject, because, as you probably know, the proposal[1] has been accepted[2] and has to be merged with mine[3] and discussed a bit to understand what we have to do and who can help. Il 13/06/2012 14:35, Steven Tucker ha scritto: This proposal may be a bit different to the several others you have seen in that a lot of the heavy lifting has already been done. The Ui layer is provided by libYui and friends, and the logic is already there in mcc. With the perl bindings to libYui the effort is no where near as large as a rewrite, which I imagine the several other proposals were. I would prefer it all to be written in C++, but that would be more work than adapting the current perl code, so you see it's not just pie in the sky, I have actually put some thought into it. In a first read i understood the idea was to provide a new gui abstraction layer, and you told me the suggested libYui library is written in C++ with some script bindings (one for all perl) and since I'm not a perl programmer and i know C++ and QT (something on GTk also) i could help. So should i assume you want to rewrite all? Steven, can you please point me and other potential contributors to your plans? Planning is also needed to our proposal to be definitely accepted :) I don't have a lot of spare time, but i will help as much as possible. Matteo Pasotti is adding libyui to mageia repository so we could start using it, I do also believe he's going to help us as well :) Let's start this new adventure... Cheers, Angelo [1] https://wiki.mageia.org/en/Feature:UiAbstraction4mcc [2] https://wiki.mageia.org/en/FeatureMageia3_Review [3] https://wiki.mageia.org/en/Feature:DrakXtoolsReview -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/rgusACgkQqEs9DA4DquAJcQCgnYoldmMq1+EdON9q3DhXazVe pi0An0UUHGGMnJ+X33UVmwi92AHgXM1u =wdCu -END PGP SIGNATURE-
Re: [Mageia-dev] mgarepo, svn and working from external debian server
venerdì 22 giugno 2012 alle 05:03, Johnny A. Solbu ha scritto: As someone who have a limited uplink bandwith and originally planed to work on a package which have almost a gigabyte of sources, I thought that maybe I can circumvent this by using my external Debian server to upload the huge sources, so as to avoid using a hole day of uploading using mgarepo. Silly question, can't you add a mageia vm there? I believe you need to test also what you're working on... so I checked out the package on Debian using svn co, but the sources wasn't checked out. Another silly thing, mgarepo is based on python, maybe you can try to import that in debian... Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Skype 4.0 for Linux - Package request
I think this would be worth a backport to mga2 - a lot of people will look for it and most don't have a clue how to get stuff from Cauldron and that it is safe to do so (mixing Cauldron and stable being bad idea in general). Backports are not open yet, they should be soon, at the end of our discussion, next meeting i hope... In any case i believe a bugzilla request should be filled. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Skype 4.0 for Linux - Package request
venerdì 15 giugno 2012 alle 14:45, Sander Lepik ha scritto: But for that you have to get the rpm manually from cauldron's repo. it's a noarch, and could be installed easily, but you will have a mga3 package in your mga1 or mga2 distro Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Skype 4.0 for Linux - Package request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, it's only the tag in name (mga3) that changes. Nothing else. In this case yes, but other folks who don't know the package might not know that and, buoyed by the success of installing this package may be tempted to install others which might not go so smoothly etc. etc. Yes that was exactly what i meant :) Better to do it clearly if we can. Better clearly do it cleanly :-) I backported by myself into mga1, and works, i will try it as well into mga2, but the right thing to do is that someone officially asks for it into bugzilla, then let's see what maintainer and our policy can do :) Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/bcs0ACgkQqEs9DA4DquBNjgCggqCPFou6mND+DjvuBzJOJgPN dWAAnilUxFrtiOVCGrmx7wcy2DXxyMxB =928z -END PGP SIGNATURE-
Re: [Mageia-dev] Skype 4.0 for Linux - Package request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 15/06/2012 19:56, Sander Lepik ha scritto: 15.06.2012 20:43, Claire Robinson kirjutas: Shouldn't this be a normal update to get-skype rather than a backport? That's why i said what maintainer and our policy can do :D So long there is no reason to do that. 2.0.0.35 is still available and has no know secuirty issues. But it's also a proprietary sofware in which we are not always able to know that... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/bevgACgkQqEs9DA4DquAd/gCfT7Y5FjbscrCbGIxEb/Wa9Tw0 df8An2ZBuCoOGJB20c4kxOvOfRNvLiti =dQKz -END PGP SIGNATURE-
Re: [Mageia-dev] QA bugs for MGA1 and MGA2
Hi, This is just a follow up email after the packagers meeting on behalf of QA. Last night meeting i haven't thought to a feature i have heard but that i don't know and i seem not to find in our bugzilla (maybe it has to be enabled?) e.g. the bug clone functionality. Could that be useful and cover our needs? IIUC it clones a bug from a starting point, the cloner must change the version affected and what is different between the two bugs, but the link to the father is anyway in the history of the bug. In such a way QA can follow the story of the single bug (closing it for the right version if needed), and the packager can avoid doing cutpaste for the most... Just a thought. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Backports policy clarification (and discussion)
mercoledì 13 giugno 2012 alle 00:53, nicolas vigier ha scritto: We are talking about backports, not updates, so we don't care about versionning policy of updates. And backports can have higher version than 'release' repository of next version, that's what this thread is about. ??? The policy should be the *same*, otherwise you won't have an upgradable system, something is in bp for n-1 could be: a) in core for n b) in update for n c) in bp for n In any of them it should be upgradable, so why shouldn't we follow the versioning policy for updates, since a bp for mageia n-1 *is* an upgrade/update in mageia n? ennael could we add a point in tonight meeting? i seem we talked a lot and reached no decisions... Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Proposed Feature:UiAbstraction4mcc
mercoledì 13 giugno 2012 alle 13:59, Steven Tucker ha scritto: MCC is great, and I would love to be able to admin using it regardless of whether I am using text interface or gtk/qt. The interface is completely different in curses than gtk interfaces. Curses version is a second rate citizen, and Gui is all GTK. A lot of the tools are not available in curses interface, for instance, I don't see a way to install software or managing repositories. It would be nice to have qt version as well as gtk (not a major issue, but would be nice) Well a proposal[1] to work on it -porting to qt- is already added by me, I'm not a perl programmer so it's hard for me to do the most, but i'm trying to get helped by other people (i got one positive answer at the moment)... I'm open to discuss :) [1] https://wiki.mageia.org/en/Feature:DrakXtoolsReview signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Backports policy clarification (and discussion)
martedì 12 giugno 2012 alle 08:25, blind Pete ha scritto: Some packages annoyingly have two current versions. When that happens it seems perfectly reasonable to just pick one, but if anyone is ambitious enough to try two at once, this would be a mechanism to handle it. Are you serious? Here it's not only a pakcage issue, what you're proposing to change package contents :/ foo-1.0.mga1 - (core) - /bin/foo foo-1.2.mga1 - (backports) - /bin/foo they can't be installed togheter, and changing package names would not solve this issue, but add packagers problems like conflict or obsoleting and upgradability issues /me is confused signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Backports policy clarification (and discussion)
martedì 12 giugno 2012 alle 09:30, blind Pete ha scritto: What happens to a system running mga1 plus updates when you attempt to update it? Would the old ISOs be withdrawn? Who does that? the only way to get a new iso is to release a new distro version (even Major.Minor). BTW, maybe exX is not into ISO and there isn't a problem ;) Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Proposed Feature:Backports_update_applet
martedì 12 giugno 2012 alle 07:36, blind Pete ha scritto: There are a couple of ways to do that. The simplest that I can think of is to split backports into backports and backports update. Allow cherry picking from backports and apply backports update automatically. IMO an easy management is having only one repository, e.g. just backports. Official release exits without backports, so backports are a special update, any fixing/security/new version update needed here can override the previous backported package itself, so only last version on backport is available. Is that correct? well thinking of installing the previous version in case of problem, i'd say no. But since backports are officially maintained a problem seen by an user means a problem that has to be fixed and the fixing released. In this case i'd say yes, it's correct. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] [Mageia-discuss] Accessibility in Mageia
martedì 12 giugno 2012 alle 08:14, Marja van Waes ha scritto: On 12-06-12 04:13, Patricia Fraser wrote: Hi folks, I'd like to propose a new feature for Mageia 3 - an accessible install with access tools on from startup. The feature proposal is here: https://wiki.mageia.org/en/Accessibility This feature will depend on people being interested in joining in the effort - if that's you, add your name on that page somewhere, so we can see whether to go ahead. Cheers, Just read this is about making it easier for blind people - and people with other needs - to use Mageia. Great! Thanks a lot, Trish :) I think it's a good task, but accessibility is not just a gnome-task, it should be a mageia task, since there are also kde users, maybe some lighter desktop ones for old computers... etc. Angelo signature.asc Description: This is a digitally signed message part.
[Mageia-dev] Feature:DrakXtoolsReview
See https://wiki.mageia.org/en/Feature:DrakXtoolsReview I started to have a look at the code with the help of blino and ALI3N, I'm not a perl programmer though so it's very hard to me. I'm trying to involve other people i know, in the case they do, i -or they- could get the ownership. Certainly i cannot be the only one, since i believe it's not an easy task for me. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Backports policy clarification (and discussion)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 09/06/2012 12:39, Thomas Backlund ha scritto: OK. To backport from Cauldron to mga1, we have to backport from Cauldron to mga2, (bumping the revision in cauldron to ensure that is is higher), then backport from mga2 to mga1, ensuring that the revision is lower in mga1 than in mga2.(e.g. revision x.1 in cauldron, x.0.1 in mga2, x.0.0.1 in mga1) Pretty straight forward. Not needed as 1.mgaX 1.mga3 1.mga2 1.mga1 IIUC the only problem is when in the above situation we have 1.1.mga1 for any reasons (bug fixing for instance, maybe not needed in any mgaX mga1). I believe in that situation who makes the bug-fixing has to work on other back-ports/updates because in mgaX mga1 that package could be in core and not in bp. ANgelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/To1UACgkQqEs9DA4DquCUaACZAbWbqiAWkJ+XYZNXgop/jKz4 IukAoLhCfKvT488tdSia/L/c5HM3gy1N =CRDk -END PGP SIGNATURE-
Re: [Mageia-dev] Backports policy clarification (and discussion)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 09/06/2012 20:38, Sander Lepik ha scritto: I see backports as the way to get some new stuff from cauldron before cauldron is fully stable. There is no point to backport from cauldron to n-2 (mga1 at the moment). If the user wants so much newer stuff s/he better upgrade to latest stable. There could be no point now -and maybe for you-, but it could be in future or for sombody who does not want to update to mga2 yet (kmail2, akonadi, kwallet issues) and want to get some leaf packages for his/her needs (firefox, mondevelop, ...). If we allow bp, and i'm in favor of that, we must consider all the possible cases, and must be able to upgrade to next mgaX without issues due to bp imho. Cherry-picking for me means that i can upgrade some packages from backports and then disable the repo. After that i'm still able to upgrade to fully stable next release (w/o backports). I understood that also, and it should work exactly as we are using XXX_testing for some packages, if bp is approved must work as expected and allow either upgrade or disabling bp. Angelo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/TpUoACgkQqEs9DA4DquAScQCgjj/0Q+vVQsh5otO60oP+nvpo WC8AnjCPUJi0BaJvDJ6R2+GQhZRS36dY =/ukV -END PGP SIGNATURE-
Re: [Mageia-dev] Proposed Feature:Backports_update_applet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 09/06/2012 22:53, andre999 ha scritto: - Just marking all backport repos as update repos is almost enough to solve the problem, in terms of the tools installing the backports. Great idea ! We just have to tweak the tools so that a backport is only installed as an update of a backport. e.g. as update repository. great, at least someone got my point, i think i have said that in the beginning of this thread or the related one for mgaupdate... - using bp in the file name is nice and short, and definitively marks it as a backport for the tools, and for the user once installed. (I would put it in the revision field.) I like this approach, as it doesn't matter from where the package is installed; it will always be recognized as a backport. I'm not a rpm macro guru, but i think we should change mkrel for that and we should also manage bpmga1, bpmga2, etc. So I can't see why, since a bpmgaX package could always be uploaded without respecting any upgradable rules... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/Tu74ACgkQqEs9DA4DquCBkACbBkHUqbBw9LK+VZeodz8FXDXl +PQAn3hPA4DNcnaFiTDIVNAnCRuvL79E =yhli -END PGP SIGNATURE-
Re: [Mageia-dev] Backports policy clarification (and discussion)
venerdì 8 giugno 2012 alle 10:51, Samuel Verschelde ha scritto: And what about security issues and bugs to those backports? It will use more packager ressource to patch backports than to provide newer versions, won't it? Well if a new version is out it can be backported, a patch is needed otherwise. But it all depends on what package has been backported of course. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Backports policy clarification (and discussion)
If there is security issue then you have to fix it on cauldron too (usually with new version, so you can backport it to stable version). At least before release. And after backports are closed you can upgrade to latest stable version (for example mga3) and get patched version this way. I don't see the problem here. Well I can't see how we can close a bp since we say we give 9 months of supporting version. If we support bp, we also need to provides fixing at least. But i got your point, it's a kind o release freeze for bp for the mga n-2. Angelo signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] Proposed Feature:Backports_update_applet
venerdì 8 giugno 2012 alle 12:49, Sander Lepik ha scritto: Well, backports are not quite the same as tainted or nonfree or core. They are more like the updates folder of those repos. Yes but once you've enabled tehm, they should work as they were official repos, so why having two tools for that? Just wonder... Angelo signature.asc Description: This is a digitally signed message part.
