On Sun, 9 Dec 2012, Remy CLOUARD wrote:
> On Sat, Dec 08, 2012 at 02:43:47PM +0100, tux99-...@uridium.org wrote:
> > Hi,
> > If you are curious to see what can be done with the MIDI::ALSA Perl
> > module have a look at a program I wrote with it:
> > http://w
On Sat, 8 Dec 2012, Shlomi Fish wrote:
>
> I now packaged your perl-MIDI-ALSA for Mageia Linux 3/Cauldron after some
> Mageiaisation of the .spec file. Thanks!
That's great, thanks!
> If you wish to return the favour you can package Freecell Solver
> ( http://fc-solve.shlomifish.org/ ) for Fedor
Hi,
Thanks to Peter Billam there is now a Perl module that gives Perl
complete access to the ALSA MIDI library therefore allowing to easily
create programs in Perl that inteface with MIDI capable synthesizers.
I have packaged up this Perl module for Centos 6 and I think it should
be straightfor
On Sun, 11 Mar 2012 tux99-...@uridium.org wrote:
>
> On Fri, 9 Mar 2012 tux99-...@uridium.org wrote:
>
> > On Fri, 9 Mar 2012, Thomas Backlund wrote:
> >
> > > tux99-...@uridium.org skrev 8.3.2012 02:18:
> > > >
> > > > Hi,
> > >
On Fri, 16 Mar 2012, Sander Lepik wrote:
> 16.03.2012 03:07, tux99-...@uridium.org kirjutas:
> > On Thu, 15 Mar 2012, Anne nicolas wrote:
> >
> >> Hi there
> >>
> >> Beta 2 is available now for tests. Here is the announcement:
> >> http://blo
pected more interest in getting Mageia to work on them.
Therefore I say it again, I'm available to do any reasonable tests you
want me to do or provide any logs you need to get this solved (see my
previous mails for details I already provided so far).
Regards,
tux99
On Mon, 12 Mar 2012, zezinho wrote:
> Le lundi 12 mars 2012 00:38:00, tux99-...@uridium.org a �crit :
> > Sorry ignore the previous pastebins, those were without "vga=795" on the
> > kernel line, here are the correct ones:
> >
>
> Please, maybe this could g
On Sun, 11 Mar 2012 tux99-...@uridium.org wrote:
> On Fri, 9 Mar 2012 tux99-...@uridium.org wrote:
>
> > On Fri, 9 Mar 2012, Thomas Backlund wrote:
> >
> > > tux99-...@uridium.org skrev 8.3.2012 02:18:
> > > >
> > > > Hi,
> > > >
On Fri, 9 Mar 2012 tux99-...@uridium.org wrote:
> On Fri, 9 Mar 2012, Thomas Backlund wrote:
>
> > tux99-...@uridium.org skrev 8.3.2012 02:18:
> > >
> > > Hi,
> > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it
> > > woul
On Fri, 9 Mar 2012, Thomas Backlund wrote:
> tux99-...@uridium.org skrev 8.3.2012 02:18:
> >
> > Hi,
> > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it
> > would have framebuffer support for the GMA 3600, but the attached
> > monitor goes in
On Thu, 8 Mar 2012, Colin Guthrie wrote:
> 'Twas brillig, and tux99-...@uridium.org at 08/03/12 02:00 did gyre and
> gimble:
> > On Thu, 8 Mar 2012 tux99-...@uridium.org wrote:
> >
> >>
> >> Hi,
> >> I just tried Mageia 2 beta 1 on a In
On Wed, 7 Mar 2012, David W. Hodgins wrote:
> On Wed, 07 Mar 2012 21:00:38 -0500, wrote:
>
> > On Thu, 8 Mar 2012 tux99-...@uridium.org wrote:
> >
> >>
> >> Hi,
> >> I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it
> >>
On Thu, 8 Mar 2012 tux99-...@uridium.org wrote:
>
> Hi,
> I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it
> would have framebuffer support for the GMA 3600, but the attached
> monitor goes into standby (no signal) as soon as the frame buffer gets
> act
3.3 kernel
for the GMA 3600 so in theory it should work.
Are you aware of this issue or should I do a bug report?
Has anyone else tested a GMA 3600 (the GPU that's in all Cedar Trail
Atom cpus) with Mageia so far?
Regards,
tux99
I thought the core build of freetype2 already has the bytecode interpreter
enabled (since the patent expired).
Why is there still a need for a tainted version?
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Is there any specific reason (regressions, incompatibilites?) why Mageia
(and Mandriva) still ships dkms 2.0.19 even though 2.1.1.2 is the latest
upstream release, or is it simply because nobody has updated the package?
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
IMHO there should be an exception for tainted since the fact that the build
system can't build dual target packages[1] yet, is blocking the submission
of many packages that depend on these. I saw the build system issue has
been elevated to "release-blocker", IMHO it should be also freeze delaying
Quote: You-Cheng Hsieh wrote on Fri, 29 April 2011 03:59
> 2011/4/29 Tux99 :
> > There is an easy to follow step by step user-contributed tutorial
> > on how to use mandriva-seed in Windows on my website.
> > It was writte
There is an easy to follow step by step user-contributed tutorial on how to
use mandriva-seed in Windows on my website.
It was written for Mandriva 2009.1 but I guess it should be usable for
Mageia too.
See here (in the right-hand column):
http://www.linuxtech.net/news/mandriva_linux_2009.1_sprin
Quote: Oliver Burger wrote on Mon, 28 March 2011 10:17
> What about packages, we need twice, once in core, once in
> tainted (media player come to mind)?
> Will the buildsystem be able to create both out of one single
> src.rpm? If not, how else to do it?
Does anyone know what the status of the
Quote: Oliver Burger wrote on Sun, 27 March 2011 17:40
> By the way: I know, Debian are just a small group of "ultra-orthodox
> software fanatics", but that's exactly, what they are doing...
I'm aware that Debian does this now. While I don't think that all (or even
most) Debian supporters are
Quote: Wolfgang Bornath wrote on Sun, 27 March 2011 17:11
> Do you really think it will help to find a consent calling people who
> do not share your opinion "ultra-orthodox software fanatics"?
Why? An 'orthodox' is a person who follows his beliefs very very strictly,
'fanatic' has a similar m
Quote: Frank Griffin wrote on Sun, 27 March 2011 15:03
> On 03/26/2011 08:58 PM, Tux99 wrote:
> >
> > And why should all of us suffer the hassle of a DVD + a CD (how
> > would that
> > work for all those that use USB-sticks, do they now need two
> > sticks?
>
Quote: Frank Griffin wrote on Sun, 27 March 2011 00:34
> For you to complain that because you have minimal network access, the
> rest of the Mageia community should bend over backwards to avoid your
> having to swap a few CDs during install is a pretty hollow argument, in
>
> my opinion.
And
Quote: Colin Guthrie wrote on Fri, 25 March 2011 14:36
> It was Donald Knuth who said "Premature optimization is the root of
> all
> evil", and the same can be said of "Speculative Packaging" IMO!
Actually you just made my point here, excluding qt3-devel out of 'neatness'
is quite clearly prema
Quote: Robert Xu wrote on Fri, 25 March 2011 13:53
> Hi,
>
> Based on all this conversation here, it is clear that we have gotten
> off topic.
> My suggestion would be to make a separate repository for Trinity.
> Beware, we also updated Qt to
Quote: John Balcaen wrote on Fri, 25 March 2011 13:27
> > As I said earlier in this thread I have of course already rebuilt
> > the qt3
> > package on my box and started working on the TDE packages (thanks
> > to work
> > done by Tim for Mandriva it's far easier for me now).
> >
> So we can now
Quote: Colin Guthrie wrote on Fri, 25 March 2011 12:43
> "Freedom" is in no way restricted. I see absolutely no problem with
> compiling a qt3 package yourself with the -devel package enabled if
> you
> want to use it.
But isn't one of the reasons for participating in a community distro,
wanti
Quote: tux99 wrote on Fri, 25 March 2011 12:47
> Quote: Balcaen John wrote on Fri, 25 March 2011 12:30
> >
> > As as already said earlier, if you want to compile TDE, you can
> > also compile
> > qt3 with devel ena
Quote: Balcaen John wrote on Fri, 25 March 2011 12:30
>
> As as already said earlier, if you want to compile TDE, you can also
> compile
> qt3 with devel enable because you 'll need to *patch* qt3 to be able to
>
> compile TDE >=3.5.12 cf
> http://www.trinitydesktop.org/wiki/bin/view/Developer
Quote: nicolas vigier wrote on Fri, 25 March 2011 12:08
> Because we want to be sure that nothing is built on this library.
So you are arbitrarily making life harder to people like Xavier and
myself.
> And you still didn't explain why you want it, if it's not to build
> software based on it.
Quote: rdalverny wrote on Fri, 25 March 2011 11:56
> A choice is arbitrary, always. It always says no
> to something. Implying that this would "restrict freedoms of users"
> would be laughable at best, offensive at worst, especially since this
> is an open source project.
You seem to be confusi
Quote: nicolas vigier wrote on Fri, 25 March 2011 11:50
> > Having a qt3-devel packages does not automatically imply having
> > packages
> > based on it in the official repos.
>
> Why do you want to have a qt3-devel package on the official repos, if
> it's not to have other packages based on it
Quote: nicolas vigier wrote on Fri, 25 March 2011 11:20
> The COMPELLING reason has already been said. It's because we don't
> want
> to have software built on a deprecated library in the repository.
That is not a compelling reason as Xavier's post showed for example.
Having a qt3-devel packag
Quote: rdalverny wrote on Fri, 25 March 2011 10:53
> You can't force a maintainer to do something you want and that she
> judges not right for her set of packages.
We seem to be having a communication issue. Where did I force a maintainer
to do anything?
I asked if there is any COMPELLING reas
Quote: xi wrote on Fri, 25 March 2011 10:32
> As always, please don't drop too fast the packages that you find
> useless. There are still some users like me who may use QT3.
>
> I still use some "not so common" applications (eg tools for electronic)
>
> which needs QT3 and it is always much m
Quote: rdalverny wrote on Fri, 25 March 2011 10:30
> Wait. What you seem to forget is that this is not only about rights
> but too about duties. The "freedom" above comes from people that take
> their time to craft and package things, so they are verily in their
> right and duty to make choices
Quote: Oliver Burger wrote on Fri, 25 March 2011 10:21
> A community distro is first and formost about community. Every time one
> of your
> ideas, suggestions, questions is answered by anyone with a "no" you
> begin to
> blame "a few of the core members", no matter how many people said no
> a
Quote: yves wrote on Fri, 25 March 2011 09:42
> Hi,
> QT4 is released since 2005, about... 6 years ?
> So, why is it usefull to maintain a package that "becomes" depreciated
> ?
You are missing the point. QT3 is already part of Mageia and it w
Quote: andr55 wrote on Fri, 25 March 2011 01:29
> My though was essentially that firmware is so close to hardware that
> its
> actual free/non-free status shouldn't apply - we should treat it like
> (almost) part of the hardware.
I agree with that. After all nobody (apart from R. Stallmann) q
Quote: Dexter Morgan wrote on Fri, 25 March 2011 09:15
> > Is there any compelling reason why we cannot reenable qt3-devel in
> > the qt3
> > source package that is ALREADY part of Mageia?
> >
> > If not then I want to reenable it.
>
> Work on TDE on your side first, we won't reenable this old,
Ok, can we get back on topic?
Is there any compelling reason why we cannot reenable qt3-devel in the qt3
source package that is ALREADY part of Mageia?
If not then I want to reenable it.
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: rdalverny wrote on Thu, 24 March 2011 14:45
> On Thu, Mar 24, 2011 at 14:39, Frank Griffin
> wrote:
> > On 03/24/2011 05:14 AM, Tux99 wrote:
> >>
> >> Can you (or anyone) tell us when the build system wil
Quote: Balcaen John wrote on Thu, 10 March 2011 17:41
>
> Le Thursday 10 March 2011 12:19:52, Tux99 a écrit :
> > The same question also applies to mplayer, which I just noticed
> > also
> > doesn't include codecs like h.264 and aac.
> For the moment there'
Quote: Oliver Burger wrote on Thu, 24 March 2011 08:53
>
> Am Donnerstag 24 März 2011, 08:23:18 schrieb Tux99:
> > I think this thread is starting to derail from a simple technical
> > question
> > limted to a specific issue (reenabling qt-dev) to an ideological
> >
I think this thread is starting to derail from a simple technical question
limted to a specific issue (reenabling qt-dev) to an ideological argument
based greatly on fear and paranoia.
Adding TrinityDE to Mageia, like adding any bigger software, is a gradual
step by step process.
I don't think
Quote: Balcaen John wrote on Wed, 23 March 2011 22:05
> But as i said before (like others), you should first try to build it
> locally,
> check it's working, intergrate nicely for menu,kdm then we'll start
> thinking
> about providing an alternative repository.
It goes without saying that I
Quote: Anne nicolas wrote on Wed, 23 March 2011 20:47
>
> As explained by some guys before, we do not want to have both KDE3 and
> 4 in repository. This has been a big pain to make them live together
> for some months (even if it looks "easy") and it has been a pain to
> clean repository.
I know
Quote: nicolas vigier wrote on Wed, 23 March 2011 19:22
> On Wed, 23 Mar 2011, Robert Xu wrote:
>
> >
> > And I hate to double post, but I do know that the %configure_kde3
> > macro should point to /opt/kde3... :)
>
> So that means that all
Quote: Robert Xu wrote on Wed, 23 March 2011 16:09
> Trinity Qt4 support is experimental, you can see it in
> SVN.trinitydesktop.org
I'm aware of that, that's why I said we need qt3-devel re-enabled in the
QT3 package.
I don't want to build the current version with experimental QT4 support.
>
Did last week's meeting not happen?
There are no logs for it:
http://meetbot.mageia.org/mageia-dev/2011/
Unfortunately I can never participate at 20h UTC, but I do like to read the
logs afterwards.
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: tux99 wrote on Wed, 23 March 2011 13:18
>
> Version 3.5.12 was just released a couple of weeks ago:
> http://www.trinitydesktop.org/releases.php
Actually I confused the date :) the current version was released last
October.
Anyway that doesn't change the fact that QT4 su
Quote: Balcaen John wrote on Wed, 23 March 2011 11:37
> > Can we please reenable the qt3-devel package as it's
> > required to build the TrinityDE (www.trinitydesktop.org)
> Did you rebuild qt3 locally & the whole trinityDE with sucess ?
Yes I just rebuilt qt3 locally with -devel with the inten
I noticed there is no qt-devel rpm in mageia.
I looked into this further and noticed the following comment in the
changelog of qt3:
Revision 45543 - (view) (download) (annotate) - [select for diffs]
Modified Mon Jan 31 23:32:27 2011 UTC (7 weeks, 1 day ago) by stewb
Original Path: cauldron/qt3
Quote: Samuel Verschelde wrote on Thu, 17 March 2011 09:14
> Well, that would be a real solution if we really wanted to flag those
> packages
> both as tainted and as non-free, as some people give more importance to
> the
> fact that it is tainted and others to the fact that it is non-free.
A
Quote: Thierry Vignaud wrote on Thu, 17 March 2011 11:01
> On 17 March 2011 09:15, Tux99 wrote:
> >> >> Mikala is John Balcaen (original poster)
> >> >
> >> > Ah ok thanks, people using sometimes
Quote: Thierry Vignaud wrote on Thu, 17 March 2011 08:49
> On 17 March 2011 08:18, Tux99 wrote:
> >> Mikala is John Balcaen (original poster)
> >
> > Ah ok thanks, people using sometimes real names and sometimes
Quote: Maarten Vanraes wrote on Thu, 17 March 2011 07:56
> Mikala is John Balcaen (original poster)
Ah ok thanks, people using sometimes real names and sometimes aliases is
quite confusing...
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: Balcaen John wrote on Thu, 17 March 2011 03:16
> from the link i pasted ealier it seems we can simply rebuild most of
> them
> without hal support.
> The idea is to simply to do as much as possible to *not* link apps to
> hal not
> to drop hal from mageia.
As long as functionality of
Quote: Ahmad Samir wrote on Thu, 17 March 2011 03:28
>
> On 17 March 2011 04:08, Tux99 wrote:
> >
> > You mean simply drop Gnome, Gimp, Gphoto, XFburn, Nut, etc. and
> > probably
> > not being able to build some other apps that aren't in the Mageia
>
You mean simply drop Gnome, Gimp, Gphoto, XFburn, Nut, etc. and probably
not being able to build some other apps that aren't in the Mageia repos
yet and might require HAL?
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
I thought there aren't supposed to be any major changes in Mageia 1?
Removing HAL seem like a major change to me.
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
André, I agree with you, we never should have had the separation of
'tainted' (and I argued that in the early days too) but that decision was
made a long time ago and is not up for debate here.
With regards to open source but not FOSS, there are many types of licenses
that source code can come wi
Quote: Michael Scherer wrote on Tue, 15 March 2011 21:30
> Le mardi 15 mars 2011 à 20:34 +0100, Tux99 a écrit :
> >
> > Quote: Michael Scherer wrote on Tue, 15 March 2011 20:21
> >
> > > Because some people
Quote: Michael Scherer wrote on Tue, 15 March 2011 20:21
> Because some people do not care about patents and using tainted stuff,
> but do care about free licenses and do care about what it bring to
> them.
>
> I do. Stormi do ( or seems to do ). And I think that given we decided
> to
> split P
Quote: Maurice Batey wrote on Tue, 15 March 2011 18:54
> On Tue, 15 Mar 2011 16:37:13 +0100, Tux99 wrote:
>
> > so we are 2 in favor of dropping firefox.
> >
> > Now that would help a lot to get Mageia great reviews..
> If the mix is legit, then we just move to non-free, and warn mirrors
> that both non-free and tainted can cause troubles.
Why do you think that would be a better solution than putting it into
tainted (where it belongs for dependencies) and marking tainted as being
for ALL tainted packages (reg
Quote: Michael Scherer wrote on Tue, 15 March 2011 14:26
> Good, so we are 2 in favor of dropping firefox.
Now that would help a lot to get Mageia great reviews...
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: Michael Scherer wrote on Tue, 15 March 2011 11:28
> > amrnb-7.0.0.2-2plf2011.0.src.rpm
> > amrwb-7.0.0.3-2plf2011.0.src.rpm
>
> This one is interesting, because the whole code is free in the
> tarball,
> as this download the code from the internet at compile time. The
> resulting code is
To add some examples of 'tainted+non-free' packages (that also include
source code) I just came across in plf free (plf doesn't seem to be too
strict about their free/non-free subdivision):
amrnb-7.0.0.2-2plf2011.0.src.rpm
amrwb-7.0.0.3-2plf2011.0.src.rpm
faac-1.28-3plf2011.0.src.rpm
Where will
I was looking at Mandriva non-free SRPM directory since Mageia doesn't have
much in non-free yet.
I haven't actually counted if the majority has source or not, so you might
be right, but we are digressing here because like I said in the first post
the question here in this thread is about a packa
Quote: Michael Scherer wrote on Tue, 15 March 2011 00:18
> Usually, people who do write non-free softwares on Linux ( like Adobe
> for flashplayer, Oracle for Java, etc ) are also those that do
> commercial business around it, and also pay the patent holder for
> usage,
> as seen when accepting
Quote: Michael Scherer wrote on Mon, 14 March 2011 21:49
> Le dimanche 13 mars 2011 à 21:09 +0100, Samuel Verschelde a écrit :
> > Le dimanche 13 mars 2011 21:01:15, Thomas Backlund a écrit :
> > > sön 2011-03-13 klockan 21:55 +0200 skrev Tux99:
> > > > During the
Quote: Anssi Hannula wrote on Mon, 14 March 2011 00:35
>
> On 14.03.2011 01:01, Tux99 wrote:
> >
> > Personally I also think 'tainted' would be the better choice than
> > 'non-free' since potential patent issues are a more serious concern
> >
Personally I also think 'tainted' would be the better choice than
'non-free' since potential patent issues are a more serious concern than a
non-FOSS license, but tbh I think both choices are far from ideal, I
believe the only really clean solution would be to create a
'tainted+non-free' repo jus
During the review with my mentor Anssi of one of the packages I'm working
on, the question came up what the appropriate repository for a package is
that's both non-free (open source but not a FOSS license) and tainted
(contains sw. that is covered by patents in some parts of the world).
Should a
Quote: Ahmad Samir wrote on Sat, 12 March 2011 21:16
>
> But you can't install 'wine' and 'wine64' at the same time.
True I didn't even realise that there is also a 'wine' package in addition
to 'wine64' and 'wine32'.
'wine32' seems to contain all that's needed to run win32 apps (at least I
ha
Geeqie is almost dead too these days (on the ML all initial devs recently
said they don't have time anymore to dedicate to it, also s.o. else seems
to have cloned the code to github and is working on it separately so
currently there are several svn/git versions floating around), personally
I'm no
Quote: Samuel Verschelde wrote on Sat, 12 March 2011 12:35
> Then isn't the problem that wine and wine64 can't be both installed ?
> And
> isn't there a way to allow that ?
but they can be, or at least the current Mageia packages allow it:
$ rpm -qa|grep wine
wine64-1.3.15-1.mga1
wine-gecko-1
I just downloaded the latest Seamonkey 2.0.12 SRPM from Mandriva cooker and
rebuilt it on my Mageia VM and it built flawlessly, I only had to remove
all the obsolete "%if %mdkversion" sections, but all dependecies are
available in Mageia.
So technically importing Seamonkey into Mageia seems strai
Quote: nicolas vigier wrote on Fri, 11 March 2011 00:39
> So maybe we need to request permission, as explained in the
> "Modifications" section.
I think you are right and I think it might be rather urgent given that
Firefox is already in on the mirrors and in the alpha1 isos.
--
Mageia ML For
Quote: jamagallon wrote on Thu, 10 March 2011 23:38
> All desktops have their own 'standard' or 'official' media players.
> I will talk about gnome, you can translate it to kde, for which I have
> no idea of which will be the equivalents.
The 'offical' DE players are not necessarily the best ch
Quote: Christiaan Welvaart wrote on Thu, 10 March 2011 23:26
> On Thu, 10 Mar 2011, nicolas vigier wrote:
>
> > On Thu, 10 Mar 2011, Christiaan Welvaart wrote:
> >
> >> Unfortunately the seamonkey name and logos are trademarked and the
> licen
Quote: Thierry Vignaud wrote on Thu, 10 March 2011 16:38
> Indeed but that shouldn't block alpha2
Agreed
> And "old" Gravis is supposed to have better quality that quite a lot
> sound cards
Very true, that why I'm still keeping it (it's a shame I can't use it in
modern PCs anymore :( ).
--
M
Quote: Thierry Vignaud wrote on Thu, 10 March 2011 16:21
> But ISApnp cards cannot be inserted in modern machines for ~8 years.
> Dunno until what years ISA sound chips got still implemented on
> motherboards.
> At least, I haven't seen any request for ISA support for 4-5 years.
I still have an
The same question also applies to mplayer, which I just noticed also
doesn't include codecs like h.264 and aac.
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
I noticed the gstreamer codecs included in Mageia so far are lacking all
the codecs that in Mandriva are in plf, such as h.264, aac, etc.
I'm aware that even in Mageia we still keep these separate in 'tainted',
but I would have thought that the 'tainted' packages would be built at the
same time
Per Øyvind, please learn the art of brevity, the more you go on and on the
less people will read your writings...
(no offense intended, but someone had to tell you)
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: Maarten Vanraes wrote on Wed, 09 March 2011 01:06
> you can if you want to, i noticed it's not imported into svn yet.
>
> you 're a novice packager too, right? take care of the importing steps:
> and
> talk to your mentor before actually doing the import.
>
> some stuff needs to be che
Quote: Michael Scherer wrote on Tue, 08 March 2011 22:28
> totem use gstreamer.
Oh really? since when? I remember to have used it with xine backend.
Well, like I said I use xine-ui (primarily for DVDs), totem would have been
my second choice but probably not anymore with gstreamer.
BTW, is an
Quote: Maarten Vanraes wrote on Mon, 07 March 2011 20:28
> imho, there is just no good one except xine-ui, but the upstream
> support is
> dwindling for it, and their own toolkitted stuff just doesn't look good
>
> anymore.
>
> i was thinking, even though i use kde, maybe gxine would be ok.
Quote: Maarten Vanraes wrote on Fri, 04 March 2011 19:15
>
> to be honest, i reread this thread a few times, and i have no idea... i
>
> clarified my point, but i donno why i was making such a point in the
> first
> place, cause it doesn't seem to make any sense...
Hmmm, it's Friday evening,
Quote: Wolfgang Bornath wrote on Fri, 04 March 2011 15:49
> Our mailserver (catering to @mandrivauser.de) does not
> show such figures. The percentage of our mailserver shows
> 56.16% accepted, 43.84 rejected. Of these accepted mails
> our spam filter shows 20% spam (average). Accordingly the
>
I would suggest 'gqview', my favourite photo viewer and organizer.
--
Mageia ML Forum Gateway: http://mageia.linuxtech.net/forum/
Quote: Wolfgang Bornath wrote on Fri, 04 March 2011 13:57
> My experience of the last 3 years shows that the spam I get is very
> low.
> Spam escaping Google's spam filter is around 3-4 per week.
> Spam in Google's spam folder is between 15-25 per day, but that does
> not bother me anyway.
Well
Quote: Wolfgang Bornath wrote on Fri, 04 March 2011 13:36
> Why? Don't you know how to use filters in your mail client? I guess you
> do know.
> I have an inbox for each mailing list, my mail client (actually google
> mail) stores each mail from all those lists in its own box.
It has got nothin
Quote: Oliver Burger wrote on Fri, 04 March 2011 13:19
>
> Which is in my opinion is unneccessary and a bit unfriendly to your
> communication partners. I use the same mail address, the same nickname
>
> and the same real name everywhere so people have a chance of
> recognising me.
And you ca
Quote: Wolfgang Bornath wrote on Fri, 04 March 2011 13:13
>
> Subscribing to lists hosted on Mageia is done with the mail address
> given in identity.mageia.org.
>
Ok I see, I haven't subscribed to any of those yet so I didn't know that.
But that's again IMHO not a good idea, we should be able
Quote: Oliver Burger wrote on Fri, 04 March 2011 12:30
> Tux99 schrieb am 2011-03-04
> > Forgot to add:
> > the primary email address in the mageia-identity db should only be
> > used for communication between mageia
Forgot to add:
the primary email address in the mageia-identity db should only be used for
communication between mageia systems and the user, like bugtrack
notifications, forum notifications, etc. It should not be displayed or
made available to the public anywhere.
--
Mageia ML Forum Gateway: h
1 - 100 of 193 matches
Mail list logo
