Fabrice quiere que te unas a su red en jobandtalent
Title: Jobandtalent mail Regístrate Fabrice Coutadeur te ha invitado a unirte a jobandtalent Somos una red de empleo que te ayuda a encontrar las mejores ofertas y contactos profesionales Aceptar invitación Si el botón no funciona, copia y pega este link en tu navegador: Companies hiring right now Estás recibiendo este email porque uno de tus amigos te ha invitado a registrarte en jobandtalent.com (Calle Eloy Gonzalo 27, 3º centro, 28010, Madrid) If you would like to unsubscribe and stop receiving these emails click here. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] ardour3/master: Pass env variables to waf
On Tue, Sep 24, 2013 at 9:26 PM, Jaromír Mikeš mira.mi...@gmail.com wrote: 2013/9/24 Felipe Sateler fsate...@debian.org On Tue, Sep 24, 2013 at 5:01 PM, Jaromír Mikeš mira.mi...@gmail.com wrote: 2013/9/24 Felipe Sateler fsate...@debian.org On Tue, Sep 24, 2013 at 11:33 AM, fsate...@users.alioth.debian.org Pass env variables to waf For some reason this works for LDFLAGS but not CFLAGS or CXXFLAGS. Any ideas on why waf decides to ignore them? They are supposed to work... I've encountered this problem when tried fix hardening too :( Maybe we can try update waf-light from 1.6.11 (Feb 2012) to current 1.7.13, but reading waf upstream changelog I can't find nothing related to this issue. Can you try updating the waf-light script and seeing if *FLAGS are respected? Having some troubles updating waf-light :( CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-z,relro /tmp/buildd/ardour3-3.4~dfsg/waf-light -v --destdir=/tmp/buildd/ardour3-3.4~dfsg/debian/tmp configure --lv2 --lxvst --freedesktop --configdir=/etc/ --noconfirm --prefix=/usr/ --no-phone-home --dist-target=x86_64 Waf: The wscript in '/tmp/buildd/ardour3-3.4~dfsg' is unreadable Traceback (most recent call last): File /tmp/buildd/ardour3-3.4~dfsg/waflib/Scripting.py, line 121, in waf_entry_point set_main_module(Context.run_dir + os.sep + Context.WSCRIPT_FILE) File /tmp/buildd/ardour3-3.4~dfsg/waflib/Scripting.py, line 163, in set_main_module Context.g_module = Context.load_module(file_path) File /tmp/buildd/ardour3-3.4~dfsg/waflib/Context.py, line 565, in load_module exec(compile(code, path, 'exec'), module.__dict__) File /tmp/buildd/ardour3-3.4~dfsg/wscript, line 2, in module from waflib.extras import autowaf as autowaf ImportError: cannot import name autowaf Your patch for some reason doesn't have the autowaf module: % lsdiff debian/patches/waf.patch | grep autowaf b/waflib/extras/autowaf.py % lsdiff ~/Downloads/waf.patch | grep autowaf % It seems to be the only missing file, though. % diff old.lsdiff new.lsdiff --- old.lsdiff 2013-09-25 09:09:30.0 -0300 +++ new.lsdiff 2013-09-25 09:08:45.0 -0300 @@ -5,7 +5,6 @@ waflib/Configure.py waflib/Context.py waflib/Errors.py -waflib/extras/autowaf.py waflib/extras/doxygen.py waflib/extras/__init__.py waflib/extras/misc.py I tried copying the file from the older patch. The build works, but we still don't get C*FLAGS. I think contacting upstream would be helpful. Can you or Adrian please ask them about this? They probably have more waf experience than us. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
FFmpeg and libav
Dear Debian maintainers, I'm a contributor on the GPAC multimedia project. I'm writing to you because we spend more and more time trying to keep our project compatible with both FFmpeg and libav. This is not sustainable. We would need you to provide both FFmpeg and libav as separate packages in Debian. However the libraries/headers in the packages have the same names. AFAIU this makes our request impossible to fulfill. What I see is: most of the work seems to be done at the libav side. However FFmpeg works better: it is more stable, the maintainers are more reactive, the APIs are more stable and consistent. This fork causes duplicated work (VLC, MPlayer, GStreamer, GPAC). I think it would be a good idea not to involve project contributors in this ego war and let them choose whichever is best for their projects. Note that it was not an issue until the last year because they were still fairly compatible. The Debian package maintainers also seem to have kept this issue away by installing old libav versions. As projects evolve, we need new features from FFmpeg/libav. Thus keeping an old libav is not sustainable either. Does anyone has an idea to improve the situation? Keep up with the good work, Romain ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: FFmpeg and libav
Hi Romain, (please mention if you are not subscribed to the list and need copy of replies - normal for Debian lists is to post only to list) Quoting Romain Bouqueau (2013-09-25 14:23:46) I'm a contributor on the GPAC multimedia project. I'm writing to you because we spend more and more time trying to keep our project compatible with both FFmpeg and libav. This is not sustainable. I understand your pain. We would need you to provide both FFmpeg and libav as separate packages in Debian. However the libraries/headers in the packages have the same names. AFAIU this makes our request impossible to fulfill. Not impossible, but very difficult: Those actually doing the work in Debian consider it too much work for too little gain. What I see is: most of the work seems to be done at the libav side. However FFmpeg works better: it is more stable, the maintainers are more reactive, the APIs are more stable and consistent. Above seems subjective. It will help the discussion tremendously if is supported by some factual non-biased comparison. This fork causes duplicated work (VLC, MPlayer, GStreamer, GPAC). I think it would be a good idea not to involve project contributors in this ego war and let them choose whichever is best for their projects. Above is judgemental. Please avoid that to keep discussion productive. Note that it was not an issue until the last year because they were still fairly compatible. The Debian package maintainers also seem to have kept this issue away by installing old libav versions. Above seems misguided. If you compare released code then beware that what Debian calls stable others might call too boring, and what others call stable Debian might call testing or unstable. Here is an overview of both how long-term and how bleeding edge Debian is regarding libav: http://packages.qa.debian.org/liba/libav.html Does anyone has an idea to improve the situation? We need to first agree that there is a situation that needs improving. As my comments above indicate, I think your input - though no doubt good intended - does not help establish such agreement. Kind regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: FFmpeg and libav
On Wed, Sep 25, 2013 at 2:23 PM, Romain Bouqueau romain.bouqueau@gmail.com wrote: Dear Debian maintainers, I'm a contributor on the GPAC multimedia project. I'm writing to you because we spend more and more time trying to keep our project compatible with both FFmpeg and libav. This is not sustainable. We would need you to provide both FFmpeg and libav as separate packages in Debian. However the libraries/headers in the packages have the same names. AFAIU this makes our request impossible to fulfill. What I see is: most of the work seems to be done at the libav side. However FFmpeg works better: it is more stable, the maintainers are more reactive, the APIs are more stable and consistent. This fork causes duplicated work (VLC, MPlayer, GStreamer, GPAC). I think it would be a good idea not to involve project contributors in this ego war and let them choose whichever is best for their projects. Note that it was not an issue until the last year because they were still fairly compatible. The Debian package maintainers also seem to have kept this issue away by installing old libav versions. As projects evolve, we need new features from FFmpeg/libav. Thus keeping an old libav is not sustainable either. Does anyone has an idea to improve the situation? Sorry for the terse answer, but I'm currently in the middle of relocating from Europe to the US. My advise would be to focus on Libav, as FFmpeg closely tracks upstream, and claims to ensures API/ABI compatibility. Michael Niedermayer offered repeatedly in the past to merge every development of Libav into FFmpeg, so that should solve your struggle for good. Feel free to drop by in #libav-devel if you find some API that is hard to use or otherwise difficult. There are many nice guys that are happy listen to your concerns! Best, Reinhard -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Ardour3 waf build sysẗem and *FLAGS
Hi Paul, we have some issue with Ardour3 packaging and waf build system in new versions of debhelper we are passing extra CFLAGS CXXFLAGS and LDFLAGS. As we succeeded with LDFLAGS we didn't with CFLAGS and CXXFAGS. By documentation waf should accept standard variables, but it doesn't in our case. http://code.google.com/p/waf/wiki/EnvironmentVariables You are for sure much more experienced with waf so maybe you can know some solution for our problem. best regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
I don't have any advice for you, sorry. I've never tried to do this. Our wscript files don't do anything to reset or ignore the environment. On Wed, Sep 25, 2013 at 11:09 AM, Jaromír Mikeš mira.mi...@gmail.comwrote: Hi Paul, we have some issue with Ardour3 packaging and waf build system in new versions of debhelper we are passing extra CFLAGS CXXFLAGS and LDFLAGS. As we succeeded with LDFLAGS we didn't with CFLAGS and CXXFAGS. By documentation waf should accept standard variables, but it doesn't in our case. http://code.google.com/p/waf/wiki/EnvironmentVariables You are for sure much more experienced with waf so maybe you can know some solution for our problem. best regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
2013/9/25 Paul Davis p...@linuxaudiosystems.com I don't have any advice for you, sorry. I've never tried to do this. Our wscript files don't do anything to reset or ignore the environment. Thank you Paul I will try contact waf developers. regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
Hi Thomas, we have some issue with Ardour3 packaging and waf build system In new versions of debhelper we are passing extra CFLAGS CXXFLAGS and LDFLAGS. As we succeeded with LDFLAGS we didn't with CFLAGS and CXXFAGS. By documentation waf should accept standard variables, but it doesn't in our case. http://code.google.com/p/waf/wiki/EnvironmentVariables Any solution for our problem? best regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
Waf by default does accept CFLAGS and CXXFLAGS, and in all versions. There might be something in the Ardour3 project preventing that. Do you have any url for the source code and in particular for the wscript file? Thomas On Wed, Sep 25, 2013 at 5:54 PM, Jaromír Mikeš mira.mi...@gmail.com wrote: Hi Thomas, we have some issue with Ardour3 packaging and waf build system In new versions of debhelper we are passing extra CFLAGS CXXFLAGS and LDFLAGS. As we succeeded with LDFLAGS we didn't with CFLAGS and CXXFAGS. By documentation waf should accept standard variables, but it doesn't in our case. http://code.google.com/p/waf/wiki/EnvironmentVariables Any solution for our problem? best regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
ita found the issue the default build for ardour is a debug build. this overrides the env settings for CFLAGS and CXXFLAGS. build with --optimize and your env settings will be used. --p On Wed, Sep 25, 2013 at 11:48 AM, Jaromír Mikeš mira.mi...@gmail.comwrote: 2013/9/25 Paul Davis p...@linuxaudiosystems.com I don't have any advice for you, sorry. I've never tried to do this. Our wscript files don't do anything to reset or ignore the environment. Thank you Paul I will try contact waf developers. regards mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
Hi Thomas, On Wed, Sep 25, 2013 at 1:42 PM, Thomas Nagy tnagy1...@gmail.com wrote: Waf by default does accept CFLAGS and CXXFLAGS, and in all versions. There might be something in the Ardour3 project preventing that. Do you have any url for the source code and in particular for the wscript file? Here is the wscript file[1] Paul Davis[2] noted that --optimize seems to enable waf to pick up the C*FLAGS variables. Is this intended behavior, or possibly something in the wscript is triggering this? [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/ardour3.git;a=blob;f=wscript; [2] https://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2013-September/034475.html -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
On Wed, Sep 25, 2013 at 9:03 PM, Felipe Sateler wrote: Hi Thomas, On Wed, Sep 25, 2013 at 1:42 PM, Thomas Nagy tnagy1...@gmail.com wrote: Waf by default does accept CFLAGS and CXXFLAGS, and in all versions. There might be something in the Ardour3 project preventing that. Do you have any url for the source code and in particular for the wscript file? Here is the wscript file[1] Paul Davis[2] noted that --optimize seems to enable waf to pick up the C*FLAGS variables. Is this intended behavior, or possibly something in the wscript is triggering this? The Ardour wscript file loads an Ardour helper module called autowaf.py. This module will force specific CFLAGS/CXXFLAGS in the default build. If I am not mistaken, the default build is intended as a debug build and will enforce its own flags. This is therefore an Ardour-specific trap, and you almost certainly want to configure Ardour with --optimize for packaging purposes. Regards, Thomas ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Ardour3 waf build sysẗem and *FLAGS
On Wed, Sep 25, 2013 at 4:21 PM, Thomas Nagy tnagy1...@gmail.com wrote: On Wed, Sep 25, 2013 at 9:03 PM, Felipe Sateler wrote: Hi Thomas, On Wed, Sep 25, 2013 at 1:42 PM, Thomas Nagy tnagy1...@gmail.com wrote: Waf by default does accept CFLAGS and CXXFLAGS, and in all versions. There might be something in the Ardour3 project preventing that. Do you have any url for the source code and in particular for the wscript file? Here is the wscript file[1] Paul Davis[2] noted that --optimize seems to enable waf to pick up the C*FLAGS variables. Is this intended behavior, or possibly something in the wscript is triggering this? The Ardour wscript file loads an Ardour helper module called autowaf.py. This module will force specific CFLAGS/CXXFLAGS in the default build. If I am not mistaken, the default build is intended as a debug build and will enforce its own flags. This is therefore an Ardour-specific trap, and you almost certainly want to configure Ardour with --optimize for packaging purposes. Great, thanks for the investigation! -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Advertise on Google | Yahoo | MSN | Bing | Facebook | Linked in with Global Advertising Media
Global Advertising Media Private Limited – Digital Marketing Company (Internet Advertising, Website Design / Development and Website Marketing Company) Promote your business using various tools like SEO PPC (Pay-Per-Click) Ad campaign on Google | Yahoo | MSN | Bing | Facebook | Linked in and many more popular search engines and social media sites. www.globaladvertisingmedia.com Google Adwords: Sponsored Links Ads eg: Pay Per Click Advertisement Need Professional Help Setting Up Your AdWords A/C? Contact Us Now! Www.GlobalAdvertisingMedia.Com We are delighted to offer you a marketing tool that has worked for customers internationally as well as domestically and is now being brought to you by Global Advertising Media. We are promoting your website through various keywords on www.google.com. About Google: Google is the world’s largest search engine with 80% of the world’s internet users, using Google. While in India, we have over 25 million unique users and 83% of them use Google. About Google AdWords: The latest and effective search-marketing tool that we were speaking of is Google AdWords, more and more small to medium-sized businesses are seeing great results with online advertising. When you advertise with Google, ads for your business show up next to the natural search results. In this way, Google AdWords ads connect you with potential customers precisely when they’re looking for the products and services you offer. Benefits to Company: 1. Relevance: Your ads are triggered by specific keywords or serch words you choose. 2. Reach: You can choose exactly where you want your ads to appear. 3. Value: You pay only when a potential customer clicks on your ad and visits your website. 4. Feedback: We provide you reports regularly to update you on the progress of your ads. 5. Control: Adwords gives you full control over your spending. You decide your daily or monthly budget, and you can adjust it whenever you want 6. Google Network Partners: Your ad appears on following Google search content partners like indiamart.com, sulekha.com, naukri.com, timesofindia.com, mid-day.com, moneycontrol.com etc.. We have shared the advertising plan created for you, based on our study of your website and inputs provided by you. The investment required to be made by you for the year. Call – 09324850002 or Email @ enqu...@globaladvertisingmedia.com (Ask for Proposal Quotation). We look forward to build a long term and mutually beneficial business relationship. OUR SERVICES: 1. Google Adwords | Yahoo Search Marketing Ads | MSN Ads | Bing Ads - Pay Per Click 2. Facebook Ads | Linked in Ads 3. SEO – Search Engine Optimisation 3. Web Design Re-design 4. Web Hosting Domain Registration 5. Google Analytic 6. Google Apps 7. Banner Advertisement and many more.. Regards, Global Advertising Media Private Limted Suraj Saroj Helpline No.: 9892994104 / 9324850002 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
