[Mageia-dev] apache-mod_nss
Oden: You packaged apache-mod_nss on Mandriva long ago and I imported it into cauldron A couple of questions: Why did you convert libmodnss.so to mod_nss.so Then in /etc/httpd/modules.d/40_mod_nss.conf you add +LoadModule nss_module modules/libmodnss.so Now there is no such thing as libmodnss.so I am just trying to understand this. -- Best regards Thomas Spuhler
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
Hi Olivier, *, On Fri, Nov 2, 2012 at 12:05 AM, Olivier Blin wrote: > Christian Lohmaier writes: >> On Thu, Nov 1, 2012 at 1:56 PM, Wolfgang Bornath >> wrote: >>> [...] >>> After reading all arguments again I must confess that I changed my >>> opinion: Being consequent and following our road we need a >>> /tainted-free and a /tainted-nonfree branch. >> >> I still think this would be a very user-*un*friendly way to handle it. >> > [...] >> Much better would then be to create an "ugly" repo (in the spirit of >> gstreamer) that contains the "doesn't fit into the other repos" stuff. > > That's just a naming issue then, are you just suggesting to rename the > "tainted-nonfree" repository proposal as "ugly"? No - my point was that I think a split of tainted into tainted-free and tainted-nonfree is pointless and not user-friendly. I only want one repository for the "problematic" stuff. Not naming it "tainted" is just because what ends up there is not only stuff that really is tainted, but also packages that just depend on tainted ones. > If we go for the "tainted + nonfree" way, its definition should be that > it contains packages that: > (1) are both tainted and not free software > or > (2) packages having a hard requirement on packages from (1) See - and that from my POV is pointless. so the tainted+nonfree contains a happy mixture of tainted and non-tainted, all variants of free to tainted-nonfree. I just don't see the point in splitting "tainted" repo that way (other than that bureaucratic thing that I as a user think is superfluous) ciao Christian
Re: [Mageia-dev] Distrib-coffee big failure of the century
On 01/11/12 20:51, Barry Jackson wrote:
See how it goes :)
Last update - honest - added proper file lock as the existing method was
flakey - it's finished and I'm leaving it alone now :)
Attached and also here:-
http://paste.kde.org/588158/12522135/
#!/bin/bash
# ~/cronsync by barjac
# Run with e.g. crontab:- 30 * * * *$HOME/cronsync
# Set using crontab -e
###
# List of mirrors in preference order to use:-
mymirrors=( \
"rsync://distrib-coffee.ipsl.jussieu.fr:/pub/linux/Mageia/distrib" \
"rsync://ftp.LinuxCabal.org/Mageia/distrib" \
"rsync://fr2.rpmfind.net/linux/mageia/distrib" \
"rsync://ftp.acc.umu.se/mirror/mageia/distrib" \
"rsync://mirrors.kernel.org:/mirrors/mageia/distrib" \
"rsync://mageia.c3sl.ufpr.br/mageia/distrib" \
)
# Set limit for loss of # of files on server before it is skipped
allowdropfiles=100
###
# Personal config:-
myexcludes="--exclude=debug --exclude=SRPMS --exclude=barjac"
mydestination="/zmrepo/pub/linux/Mageia/"
###
# Set minimum files for first run only
[[ -f .cronsync ]] || echo "14" > $HOME/.cronsync
# Get minimum file count for mirror (set at allowdropfiles files less than the
last actual file count)
minfiles=$(cat .cronsync)
((actualfiles = $minfiles + $allowdropfiles))
# Function to output formatted date
dte()
{
echo -n $(date +%d/%m/%Y-%H:%M)
}
# Check a mirror
chk_mirror()
{
echo "Checking $1 ..."
rsync -rlptgoDhHSn \
--stats \
--delete-after \
--delete-excluded \
--protect-args \
$myexcludes \
"$1" \
"$mydestination" > $lockdir/cronsync_tmp_output
status=$?
files=$(cat $lockdir/cronsync_tmp_output | grep "Number of files:" | cut -d' '
-f4 )
[[ $files -lt $minfiles ]] && echo "$(dte): Only $files/$actualfiles files in
$1" | tee -a $HOME/cronsync_error.log
[[ $status > 0 ]] && echo "$(dte): Error: $status while checking $1" | tee -a
$HOME/cronsync_error.log
([[ $status = 0 ]] && [[ $files -gt $minfiles ]]) || return 1
# Save new minimum file count
((minfiles = $files - $allowdropfiles))
echo $minfiles > $HOME/.cronsync
return 0
}
# Loop through mirror list checking until one succeeds
find_good_mirror()
{
for mirr in ${mymirrors[@]}; do
chk_mirror $mirr && { echo "Found good mirror - $mirr"; return 0; }
done
echo "$(dte): Can't find a good mirror - aborting" | tee -a
$HOME/cronsync_error.log
return 1
}
### Main routine starts here
# Avoid running two instances concurrently
lockdir=/tmp/cronsync.lock
if mkdir "$lockdir"; then
trap 'rm -rf "$lockdir"' 0
# Find a good mirror from the list (with files in it)
find_good_mirror || exit 1
# Live run with --max-delete set to 1000 just in case ;)
echo "Syncing from $mirr ..."
rsync -rlptgoDhHS \
--progress \
--stats \
--delete-after \
--max-delete=1000 \
--delete-excluded \
--protect-args \
$myexcludes \
"$mirr" \
"$mydestination" | tee $HOME/cronsync_last.log
status=${PIPESTATUS[0]}
[[ $status = 0 ]] || { echo "$(dte): Live run rsync error: $status" >>
$HOME/cronsync_error.log; exit 1; }
echo "Update complete"
else
echo "$(dte): cronsync already running or stale lock - skipping update - check
/tmp/cronsync.lock" >> $HOME/cronsync_error.log
exit 0
fi
### End of cronsync
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
Christian Lohmaier writes: > Hi Wolfgang, *, > > On Thu, Nov 1, 2012 at 1:56 PM, Wolfgang Bornath > wrote: >> [...] >> After reading all arguments again I must confess that I changed my >> opinion: Being consequent and following our road we need a >> /tainted-free and a /tainted-nonfree branch. > > I still think this would be a very user-*un*friendly way to handle it. > > You cannot put packages that itself is "free", but depends on > "tainted&nonfree" packages into the "free" repo, since the core repos > need to be self-contained. [...] > Much better would then be to create an "ugly" repo (in the spirit of > gstreamer) that contains the "doesn't fit into the other repos" stuff. That's just a naming issue then, are you just suggesting to rename the "tainted-nonfree" repository proposal as "ugly"? This crossed my mind too, but the name is less understandable by users not necessarily familiar with the gstreamer naming. If we go for the "tainted + nonfree" way, its definition should be that it contains packages that: (1) are both tainted and not free software or (2) packages having a hard requirement on packages from (1) -- Olivier Blin - blino
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
2012/11/1 Christian Lohmaier : > Hi Wolfgang, *, > > On Thu, Nov 1, 2012 at 1:56 PM, Wolfgang Bornath > wrote: >> [...] >> After reading all arguments again I must confess that I changed my >> opinion: Being consequent and following our road we need a >> /tainted-free and a /tainted-nonfree branch. > > I still think this would be a very user-*un*friendly way to handle it. > > You cannot put packages that itself is "free", but depends on > "tainted&nonfree" packages into the "free" repo, since the core repos > need to be self-contained. > > The natural approach would then be to put that package into the same > repo as the packages that fulfill the requirement. > > If now you have two tainted repositories, one "free" and one > "non-free", you would put the "free with dependencies" package into > the tainted-free repo. But it itself isn't tainted, so actually > wouldn't belong in there. But even when you have tainted-free enabled, > and you try to install the package, you need to enable the > tainted-nonfree one. > Or you put it into tainted-nonfree to keep the repos more > self-contained, but then the distinction is rendered useless, as > packages end up there for completely different reasons. > > And if you have to enable both tainted variants anyway, there is no > point in having them separate in the first place other than to please > some bureaucratic nitpicking. > > So by creating a tainted-nonfree repo that only a handful of packages > actually belong into anyway, you create a situation of non-satisfiable > dependencies that make the distinction pointless from a user-POV. > > Much better would then be to create an "ugly" repo (in the spirit of > gstreamer) that contains the "doesn't fit into the other repos" stuff. > > AFAIK only multimedia related stuff falls into tainted-nonfree. And it > is either you want to use it or not. If you want to use it, the user > doesn't care whether it is free or nonfree (by whatever definition, > there isn't the one-and-only definition that everyone agrees with > anyway). You only might care about whether it is tainted or not (and > many don't give a damn about software patents even where they could > apply in theory). It is not like you have a chance in most of these > cases. Either you use a "100% free but sucks" implementation, or you > use the "tainted and possibly "nonfree", but working just fine" one. Taking what you wrote into account there is no chance for a solution which also honors the division between free, non-free and tainted, at least non of the propositions in this thread would work. Because as you described the problem is not with each software but rather with its requirements (free software needing a non-free or tainted library to run or offer all its features). So what can we do? What do users want in such cases? First they do not want crippled packages. If they decide to have mplayer they want the whole thing, not a free variant which lacks features. They'd rather not want mplayer at all. Answering to this there may be a rather pragmatic but also drastic and even provocative solution: Stop offering software in core which need non-free and/or tainted libraries to give all its features. This software should not be offered in 2 or even 3 variants but only in one full version, residing in an "ugly" (or whatever you want to call it) repository. Yes, there may be people who would like to use mplayer without non-free or tainted libraries - but are there really? To my experience they either use the full blown package or another software. This solution may not hold against theoretical arguments but I think it's pretty much the practical way, for users as for packagers. And it will motivate people to search for free solutions where possible. -- wobo
Re: [Mageia-dev] Distrib-coffee big failure of the century
On 01/11/12 19:58, Johnny A. Solbu wrote: Why do you have both «--delete-after» and « --delete»? The last one is redundant, and should be dropped. :-)= Thanks, I missed the "(which is implied)" in the man pages. There was a useful file error (fixed now) in distrib-coffee after it completed syncing that threw up another small error reporting bug in the script which I have fixed here: http://paste.kde.org/588050/02691135/ See how it goes :)
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
Hi Wolfgang, *, On Thu, Nov 1, 2012 at 1:56 PM, Wolfgang Bornath wrote: > [...] > After reading all arguments again I must confess that I changed my > opinion: Being consequent and following our road we need a > /tainted-free and a /tainted-nonfree branch. I still think this would be a very user-*un*friendly way to handle it. You cannot put packages that itself is "free", but depends on "tainted&nonfree" packages into the "free" repo, since the core repos need to be self-contained. The natural approach would then be to put that package into the same repo as the packages that fulfill the requirement. If now you have two tainted repositories, one "free" and one "non-free", you would put the "free with dependencies" package into the tainted-free repo. But it itself isn't tainted, so actually wouldn't belong in there. But even when you have tainted-free enabled, and you try to install the package, you need to enable the tainted-nonfree one. Or you put it into tainted-nonfree to keep the repos more self-contained, but then the distinction is rendered useless, as packages end up there for completely different reasons. And if you have to enable both tainted variants anyway, there is no point in having them separate in the first place other than to please some bureaucratic nitpicking. So by creating a tainted-nonfree repo that only a handful of packages actually belong into anyway, you create a situation of non-satisfiable dependencies that make the distinction pointless from a user-POV. Much better would then be to create an "ugly" repo (in the spirit of gstreamer) that contains the "doesn't fit into the other repos" stuff. AFAIK only multimedia related stuff falls into tainted-nonfree. And it is either you want to use it or not. If you want to use it, the user doesn't care whether it is free or nonfree (by whatever definition, there isn't the one-and-only definition that everyone agrees with anyway). You only might care about whether it is tainted or not (and many don't give a damn about software patents even where they could apply in theory). It is not like you have a chance in most of these cases. Either you use a "100% free but sucks" implementation, or you use the "tainted and possibly "nonfree", but working just fine" one. ciao Christian
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
PhilippeDidier a écrit : > Christiaan Welvaart a écrit : >> On Thu, 1 Nov 2012, PhilippeDidier wrote: >> >>> Christiaan Welvaart a écrit : On Wed, 31 Oct 2012, PhilippeDidier wrote: > I don't know actually how to create *.aac files or *.mp4 files with > Mageia... if you help me I will be happy... ffmpeg -i foo.mp3 -strict -2 -codec:a aac -format adts foo.aac But AFAIK this uses the ffmpeg internal aac codec which isn't very good. -codec:a libvo_aacenc produces garbage, no idea why About arista: someone decided to use the internal ffmpeg lib from gstreamer-ffmpeg for gstreamer0.10-ffmpeg which broke arista. Now arista must be ported to gstreamer1.0 . >> >>> You can understand, now, if you need to create aac or mpa or mp4 files : >>> that faac works >>> that softwares built with it work too >>> that nothing inside Mageia work (libvo_aacenc is really bad quality when >>> it doesn't produce garbages) >> >> It is a problem with the .aac file format combined with this codec. It >> works fine with bitrate 192kbit/s just not with anything lower. The >> codec also works with any bitrate when output to mp4 (aka quicktime >> movie) files. Or are you saying you do not like the audio quality of >> this codec? >> >>> What do you propose then ? >> >> Try it yourself and complain to ffmpeg developers if something you need >> doesn't work. >> >> There is now also fdk-aac which is supposed to be good. It has a special >> license that is somewhat similar to the GPL, may be compatible or not. >> >> It is not so clear : http://opencore-amr.git.sourceforge.net/git/gitweb.cgi?p=opencore-amr/fdk-aac;a=blob;f=NOTICE >> Christiaan >> > Yes fdk-aac replaces now vo-aacenc ! > I'm trying to build a package for fdk-aac-0.1.0. ;) > > I did it ... Proposed a spec file and a patch see bugzilla bug 7951 It may now be used for building ffmpeg (ready for this) vlc (soon) not yet for mplayer nor avidemux :(
Re: [Mageia-dev] Distrib-coffee big failure of the century
On Thursday 01 November 2012 15:24, Barry Jackson wrote: > I fixed a bug and cleaned up some clunky bash, so use this:- > http://paste.kde.org/587864/51779286/ Why do you have both «--delete-after» and « --delete»? The last one is redundant, and should be dropped. :-)= > It's half way there :) :-)= -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
Christiaan Welvaart a écrit : > On Thu, 1 Nov 2012, PhilippeDidier wrote: > >> Christiaan Welvaart a écrit : >>> On Wed, 31 Oct 2012, PhilippeDidier wrote: >>> I don't know actually how to create *.aac files or *.mp4 files with Mageia... if you help me I will be happy... >>> >>> ffmpeg -i foo.mp3 -strict -2 -codec:a aac -format adts foo.aac >>> >>> But AFAIK this uses the ffmpeg internal aac codec which isn't very good. >>> -codec:a libvo_aacenc produces garbage, no idea why >>> >>> About arista: someone decided to use the internal ffmpeg lib from >>> gstreamer-ffmpeg for gstreamer0.10-ffmpeg which broke arista. Now arista >>> must be ported to gstreamer1.0 . > >> You can understand, now, if you need to create aac or mpa or mp4 files : >> that faac works >> that softwares built with it work too >> that nothing inside Mageia work (libvo_aacenc is really bad quality when >> it doesn't produce garbages) > > It is a problem with the .aac file format combined with this codec. It > works fine with bitrate 192kbit/s just not with anything lower. The > codec also works with any bitrate when output to mp4 (aka quicktime > movie) files. Or are you saying you do not like the audio quality of > this codec? > >> What do you propose then ? > > Try it yourself and complain to ffmpeg developers if something you need > doesn't work. > > There is now also fdk-aac which is supposed to be good. It has a special > license that is somewhat similar to the GPL, may be compatible or not. > > > Christiaan > Yes fdk-aac replaces now vo-aacenc ! I'm trying to build a package for fdk-aac-0.1.0. ;)
[Mageia-dev] What's happening?
I'm confident that a lot of people would like to see the possibility to clone the idea of OpenSuse Studio, but I wonder if anyone here would start to make it happen. Read my suggestion-report at the bottom of this page here: https://wiki.mageia.org/en/Mageia_Ideas_Page
Re: [Mageia-dev] Distrib-coffee big failure of the century
I fixed a bug and cleaned up some clunky bash, so use this:- http://paste.kde.org/587864/51779286/ It's half way there :) From ~/cronsync_error.log :- 01/11/2012-14:05: Only 79199/141855 files in rsync://distrib-coffee.ipsl.jussieu.fr:/pub/linux/Mageia/distrib
Re: [Mageia-dev] rehashing the faac issue
andre999 a écrit : > Johnny A. Solbu a écrit : >> On Tuesday 30 October 2012 09:37, Malo wrote: >>> - there is only faac, so why bother? (fuelling the first reason) >> >> There is also another side to this, that we either haven't talked >> about or doesn't know about. We are a Free software community, that >> includes some nonfree software. (And therefore doesn't qualify as a >> Free Software community according to some, but that's another >> debate.) A part of beeing a Free software community is that we have a >> preference as to what kind of software we are willing to work with. >> That also means that there are software we are not willing to work >> with. >> >> We could decide that «patented nonfree software» doesn't belong in >> our distribution. >> > That has been our temporary decision, to the best of my knowledge always > to be reviewed later. > But as we can see, many users want certain packages in this category, so > the topic keeps getting raised. > For myself, with a very strong preference for open source, I'm very > willing to accommodate those with a preference for certain non-free > software. > As well, there will always be proprietory software, particularly for > niche situations, which is not necessarily bad. > After all good ideas in proprietory software, which focuses on solving > real-world needs, can inspire a lot of good free software. > The choice is between 3 options : A) Let Faac off ;) and stay without allowing to work on some multimedia files until an opensource sofware really works (that's the way it goes since Mageia exists) hoping that a third party repo provides what Mageia users need when they are not strict opensource users (nevermind to know if they are a majority or a minority). Ordinary users must know that the third repo exists and how to use it (not for beginners :( ) B) the most simple for admins and QA if we allow the presence of non strictly free software in tainted (needing to modify the Mageia policy => that's a Mageia Board decision ! not only a packager vote. ) if the strict opensource users can discriminate strictly opensource and non strictly opensource packages 1) in the tainted repo : we may have faac (explicitely informing that it's build upon a non free piece of code) we may provide handbrake and cinelerra that absolutely need faac (explicitely informing that they have the same problem as faac because they are built upon it) 2) If we can have two versions with different names in the same repo we can provide vlc-tainted (as it is now, allowing to "update" from the core repo's same version ) and beside it vlc-tainted-faaced or vlc-twisted or whatever working suffix (informing that it is not strictly opensource, and allowing to update from the core and from the tainted version) same for avidemux gstreamer audiokonverter arista and so on It is simple for ordinary users or beginners: the faac versioned is automatically chosen Strict opensource users know what to do if they want purity ! C) More heavy for admin and QA : create a non-free-tainted repo (and update backport subrepos) Always need to add a special suffix for vlc, avidemux... built with faac option in this repo, to "update" them from core and tainted version : - strict opensource users may not allow this repo... and it is simple for them - need to inform ordinary users to allow these repos and why (a little complex for beginners) Philippe
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kernel-tmb-3.6.5-3.mga3
Charles A Edwards skrev 1.11.2012 15:29: On Thu, 1 Nov 2012 13:03:13 +0100 (CET) tmb wrote: Name: kernel-tmb Relocations: (not relocatable) Version : 3.6.5 Vendor: Mageia.Org Release : 3.mga3Build Date: Thu Nov 1 12:18:15 2012 Install Date: (not installed) Build Host: ecosse.mageia.org Group : System/Kernel and hardwareSource RPM: (none) Size: 70264111 License: GPLv2 Signature : (none) Packager: tmb URL : http://www.kernel.org This release boots without issue Thanks Great :) -- Thomas
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release kernel-tmb-3.6.5-3.mga3
On Thu, 1 Nov 2012 13:03:13 +0100 (CET) tmb wrote: > Name: kernel-tmb Relocations: (not > relocatable) Version : 3.6.5 Vendor: > Mageia.Org Release : 3.mga3Build Date: > Thu Nov 1 12:18:15 2012 Install Date: (not installed) > Build Host: ecosse.mageia.org Group : System/Kernel and > hardwareSource RPM: (none) Size: > 70264111 License: GPLv2 Signature : (none) > Packager: tmb > URL : http://www.kernel.org This release boots without issue Thanks Charles -- "I shall expect a chemical cure for psychopathic behavior by 10 A.M. tomorrow, or I'll have your guts for spaghetti." -- a comic panel by Cotham -- Mageia release 3 (Cauldron) for x86_64$ On SuperSizehttp://www.eslrahc.com Registered Linux user #182463 3.6.5-tmb-server-3.mga3 x86_64 -- signature.asc Description: PGP signature
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
On Thu, 1 Nov 2012, PhilippeDidier wrote: Christiaan Welvaart a écrit : On Wed, 31 Oct 2012, PhilippeDidier wrote: I don't know actually how to create *.aac files or *.mp4 files with Mageia... if you help me I will be happy... ffmpeg -i foo.mp3 -strict -2 -codec:a aac -format adts foo.aac But AFAIK this uses the ffmpeg internal aac codec which isn't very good. -codec:a libvo_aacenc produces garbage, no idea why About arista: someone decided to use the internal ffmpeg lib from gstreamer-ffmpeg for gstreamer0.10-ffmpeg which broke arista. Now arista must be ported to gstreamer1.0 . You can understand, now, if you need to create aac or mpa or mp4 files : that faac works that softwares built with it work too that nothing inside Mageia work (libvo_aacenc is really bad quality when it doesn't produce garbages) It is a problem with the .aac file format combined with this codec. It works fine with bitrate 192kbit/s just not with anything lower. The codec also works with any bitrate when output to mp4 (aka quicktime movie) files. Or are you saying you do not like the audio quality of this codec? What do you propose then ? Try it yourself and complain to ffmpeg developers if something you need doesn't work. There is now also fdk-aac which is supposed to be good. It has a special license that is somewhat similar to the GPL, may be compatible or not. Christiaan
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
2012/11/1 PhilippeDidier : > Christiaan Welvaart a écrit : >> On Wed, 31 Oct 2012, PhilippeDidier wrote: >> >>> I don't know actually how to create *.aac files or *.mp4 files with >>> Mageia... if you help me I will be happy... >> >> ffmpeg -i foo.mp3 -strict -2 -codec:a aac -format adts foo.aac >> >> But AFAIK this uses the ffmpeg internal aac codec which isn't very good. >> -codec:a libvo_aacenc produces garbage, no idea why >> >> About arista: someone decided to use the internal ffmpeg lib from >> gstreamer-ffmpeg for gstreamer0.10-ffmpeg which broke arista. Now arista >> must be ported to gstreamer1.0 . >> >> >> Christiaan >> > So ... > You can understand, now, if you need to create aac or mpa or mp4 files : > that faac works > that softwares built with it work too > that nothing inside Mageia work (libvo_aacenc is really bad quality when > it doesn't produce garbages) > that we have been waiting since Mageia exists for an hypthetic GPL > alternative to faac > that to satisfy exclusive gpl software policy in tainted repo we are stuck > > What do you propose then ? After reading all arguments again I must confess that I changed my opinion: Being consequent and following our road we need a /tainted-free and a /tainted-nonfree branch. I apologise for my harsh words about the whole matter, the repeated discussion changed my mind. -- wobo
Re: [Mageia-dev] cinelerra/audiokonverter/arista (war Re: rehashing the faac issue)
Christiaan Welvaart a écrit : > On Wed, 31 Oct 2012, PhilippeDidier wrote: > >> I don't know actually how to create *.aac files or *.mp4 files with >> Mageia... if you help me I will be happy... > > ffmpeg -i foo.mp3 -strict -2 -codec:a aac -format adts foo.aac > > But AFAIK this uses the ffmpeg internal aac codec which isn't very good. > -codec:a libvo_aacenc produces garbage, no idea why > > About arista: someone decided to use the internal ffmpeg lib from > gstreamer-ffmpeg for gstreamer0.10-ffmpeg which broke arista. Now arista > must be ported to gstreamer1.0 . > > > Christiaan > So ... You can understand, now, if you need to create aac or mpa or mp4 files : that faac works that softwares built with it work too that nothing inside Mageia work (libvo_aacenc is really bad quality when it doesn't produce garbages) that we have been waiting since Mageia exists for an hypthetic GPL alternative to faac that to satisfy exclusive gpl software policy in tainted repo we are stuck What do you propose then ? philippe
Re: [Mageia-dev] Distrib-coffee big failure of the century
On 31/10/12 22:53, Johnny A. Solbu wrote: On Wednesday 31 October 2012 23:29, Barry Jackson wrote: I wrote the attached script. It checks several mirrors until it finds one that has the normal number of files and does not fail for any other reason. If you feel inclined to use it please feel free to suggest any improvements. The script was caught in one of my spam and attachment protection cript, Anomy. One of the first lines was mangled. So if you could repost that second line, I'd be gratefull. === #!/bin/sh echo DEFANGED.266 exit === Oh dear :( It's here:- http://paste.kde.org/587408/13517591/ (Switch to 'raw code' view before copy/pasting)
