-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:
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
-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/
-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
-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
-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
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
-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
-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
-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?
-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
-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,
-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
-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
-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
-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.
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?
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
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
-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:
-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
-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
-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/
-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
-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
-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
-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)
-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/$_;
-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
-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
-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
-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.pl
-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
-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.
Let's have fun :p
Please patch kdegraphics. So that we could also have fun
using digikam :p
Angelo
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
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.
-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
-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
-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
-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
-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
-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
-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
-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
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
-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
-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
-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
-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
-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
-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:
-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
-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)
-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.
-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 -
-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
-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
-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
-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
-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
-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
-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
-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
-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,
-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
-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
-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
-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.
-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
-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
-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
-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
-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,
-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
-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
-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
-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:
-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
-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
-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:
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
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
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
-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
-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
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
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
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,
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?
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
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
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:
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
-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
-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
-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
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
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.
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
1 - 100 of 270 matches
Mail list logo
