Re: Fwd: Re: vlc-2.0.7

2013-07-14 Thread John Pilkington 

On 14/07/13 16:48, Yasha Karant wrote:



John,

Although vlc 2.0.7 is the current stable production release from vlc, it
is not the same from the rpmfusion respository, for which 2.0.6 is
stable.  I avoid (if at all possible) any "testing", pre-production, or
beta releases on any production machine.  My experience has been that
introducing a "testing" release from many of these repositories also
gets "testing" versions of core libraries and other functionalities,
some of which truly are not ready for "prime time" -- vlc 2.0.7 may be
production, but some other library release version that is being used
with the repository release, but which otherwise is not required for the
application in question, also is so mandated but only by the repository.

Sometimes, functionality requires the installation of testing software
on a production machine -- particularly if the "stable" release does not
support some otherwise Microsoft-only hardware (the USA has found
Microsoft to be a monopoly, but has forced no meaningful remedies,
unlike the EU for which at least some parts of the monopoly have been
broken through either enforced compatibility or reverse engineered "open
systems" workarounds for which Microsoft effectively cannot sue the
provider within the EU).

Thus, I stayed with 2.0.6 that (presumably) is a large improvement over
the 1.x vlc I had been using.

Thanks again.

Yasha Karant

OK.  I'm not conscious of all the constraints you may have, and 
obviously stability is desirable.  My use of kde-unstable was largely 
unplanned. I temporarily lost my LVM configuration and IIRC it got 
installed during or shortly after my attempts to recover.  I have found 
it much easier to use and less glitch prone than what I had before.  And 
I use the elrepo kernel to get support for my DVB-T2 tv-tuner: my 
attempts to build the driver with the standard kernel and the linuxtv 
script all failed.


I hope your new vlc installation does what you want.

John

Re: Fwd: Re: vlc-2.0.7

2013-07-14 Thread Yasha Karant 

On 07/14/2013 01:52 AM, John Pilkington wrote:

On 14/07/13 07:19, Yasha Karant wrote:

On 07/13/2013 01:14 AM, John Pilkington wrote:

On 13/07/13 08:15, Yasha Karant wrote:

On 07/12/2013 05:38 PM, Todd And Margo Chester wrote:

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux
application
environment is not polymorphic with encapsulation, one cannot have
both
versions of some such dependency installed.


Hi Yasha,

It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T


Hi Todd,

My understanding is that your procedure can result in system
instability
because of the lack of polymorphism and encapsulation.  If one uses
repositories other than those from SL6 or from those repositories that
claim the use thereof will not introduce stock (SL6x)
incompatibilities,
then getting an application that requires such incompatible RPMs may
cause problems.  The solution of erasing the conflicting RPM and
presumably loading a replacement RPM that is not part of the stock
compatible distribution can "break" other applications that are
dependent upon such RPMs.

Building from a SRPM probably will not solve the problem because the
source RPM presumably requires the same RPMs (or SRPMs) that either do
not exist for stock SL6x or conflict with stock SL6x RPMs.  Again --
are
there any SL6x compatible source packages or installable RPMs that
supply the functionalities that I had to disable in building the
current
production vlc application from source?

Yasha Karant


I have vlc 2.0.7 installed on my SL6 i686 laptop.  It's from rpmfusion,
which has, I understand, stricter policies on compliance than ATrpms.  I
don't know what, if any, restrictions were applied in the build, and I
haven't tried it on many file formats, but it works well for me.  Have
you tried/considered it?

Perhaps I should add that I'm also using an elrepo kernel and
kde-unstable.

Here's the 64-bit version. extras, devel are there too.

http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/vlc-2.0.7-1.el6.x86_64.rpm




John P


I installed the rpmfusion repository, found vlc 2.0.6, and allowed the
GUI add/remove software to proceed.  vlc 2.0.6 now is installed on my
IA-32 laptop; when I get to the office, I will proceed with the same for
X86-64.

Are you aware if this vlc includes all needed codecs, some of which
evidently only can be installed from EU sources?

Otherwise, the rpmfusion repository seems to provide all of the needed
dependencies.  (Note from the rpmfusion instructions:  You need to
enable EPEL on RHEL 5 & 6 or compatible distributions like CentOS before
you enable RPM Fusion for EL.)

Thank you for the reference.

Yasha Karant



I may be mistaken, but I think vlc uses its own codecs.  On my Fedora 17
box there's  a folder /usr/lib64/vlc/plugins/codec/, installed from
vlc-core.   See eg Yum-extender, Package Filelist.

I thought you wanted 2.0.7?  Note that that is in the testing repo.
Enabling that should give a mirrorlist.

mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-testing-$releasever&arch=$basearch


HTH

John P


John,

Although vlc 2.0.7 is the current stable production release from vlc, it 
is not the same from the rpmfusion respository, for which 2.0.6 is 
stable.  I avoid (if at all possible) any "testing", pre-production, or 
beta releases on any production machine.  My experience has been that 
introducing a "testing" release from many of these repositories also 
gets "testing" versions of core libraries and other functionalities, 
some of which truly are not ready for "prime time" -- vlc 2.0.7 may be 
production, but some other library release version that is being used 
with the repository release, but which otherwise is not required for the 
application in question, also is so mandated but only by the repository.


Sometimes, functionality requires the installation of testing software 
on a production machine -- particularly if the "stable" release does not 
support some otherwise Microsoft-only hardware (the USA has found 
Microsoft to be a monopoly, but has forced no meaningful remedies, 
unlike the EU for which at least some parts of the monopoly have been 
broken through either enforced compatibility or reverse engineered "open 
systems" workarounds for which Microsoft effectively cannot sue the 
provider within the EU).


Thus, I stayed with 2.0.6 that (presumably) is a large improvement over 
the 1.x vlc I had been using.


Thanks again.

Yasha Karan

Re: Fwd: Re: vlc-2.0.7

2013-07-14 Thread John Pilkington 

On 14/07/13 07:19, Yasha Karant wrote:

On 07/13/2013 01:14 AM, John Pilkington wrote:

On 13/07/13 08:15, Yasha Karant wrote:

On 07/12/2013 05:38 PM, Todd And Margo Chester wrote:

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux
application
environment is not polymorphic with encapsulation, one cannot have
both
versions of some such dependency installed.


Hi Yasha,

It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T


Hi Todd,

My understanding is that your procedure can result in system instability
because of the lack of polymorphism and encapsulation.  If one uses
repositories other than those from SL6 or from those repositories that
claim the use thereof will not introduce stock (SL6x) incompatibilities,
then getting an application that requires such incompatible RPMs may
cause problems.  The solution of erasing the conflicting RPM and
presumably loading a replacement RPM that is not part of the stock
compatible distribution can "break" other applications that are
dependent upon such RPMs.

Building from a SRPM probably will not solve the problem because the
source RPM presumably requires the same RPMs (or SRPMs) that either do
not exist for stock SL6x or conflict with stock SL6x RPMs.  Again -- are
there any SL6x compatible source packages or installable RPMs that
supply the functionalities that I had to disable in building the current
production vlc application from source?

Yasha Karant


I have vlc 2.0.7 installed on my SL6 i686 laptop.  It's from rpmfusion,
which has, I understand, stricter policies on compliance than ATrpms.  I
don't know what, if any, restrictions were applied in the build, and I
haven't tried it on many file formats, but it works well for me.  Have
you tried/considered it?

Perhaps I should add that I'm also using an elrepo kernel and
kde-unstable.

Here's the 64-bit version. extras, devel are there too.

http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/vlc-2.0.7-1.el6.x86_64.rpm



John P


I installed the rpmfusion repository, found vlc 2.0.6, and allowed the
GUI add/remove software to proceed.  vlc 2.0.6 now is installed on my
IA-32 laptop; when I get to the office, I will proceed with the same for
X86-64.

Are you aware if this vlc includes all needed codecs, some of which
evidently only can be installed from EU sources?

Otherwise, the rpmfusion repository seems to provide all of the needed
dependencies.  (Note from the rpmfusion instructions:  You need to
enable EPEL on RHEL 5 & 6 or compatible distributions like CentOS before
you enable RPM Fusion for EL.)

Thank you for the reference.

Yasha Karant



I may be mistaken, but I think vlc uses its own codecs.  On my Fedora 17 
box there's  a folder /usr/lib64/vlc/plugins/codec/, installed from 
vlc-core.   See eg Yum-extender, Package Filelist.


I thought you wanted 2.0.7?  Note that that is in the testing repo. 
Enabling that should give a mirrorlist.


mirrorlist=http://mirrors.rpmfusion.org/mirrorlist?repo=free-fedora-updates-testing-$releasever&arch=$basearch

HTH

John P

Re: Fwd: Re: vlc-2.0.7

2013-07-13 Thread Yasha Karant 

On 07/13/2013 01:14 AM, John Pilkington wrote:

On 13/07/13 08:15, Yasha Karant wrote:

On 07/12/2013 05:38 PM, Todd And Margo Chester wrote:

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux
application
environment is not polymorphic with encapsulation, one cannot have both
versions of some such dependency installed.


Hi Yasha,

It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T


Hi Todd,

My understanding is that your procedure can result in system instability
because of the lack of polymorphism and encapsulation.  If one uses
repositories other than those from SL6 or from those repositories that
claim the use thereof will not introduce stock (SL6x) incompatibilities,
then getting an application that requires such incompatible RPMs may
cause problems.  The solution of erasing the conflicting RPM and
presumably loading a replacement RPM that is not part of the stock
compatible distribution can "break" other applications that are
dependent upon such RPMs.

Building from a SRPM probably will not solve the problem because the
source RPM presumably requires the same RPMs (or SRPMs) that either do
not exist for stock SL6x or conflict with stock SL6x RPMs.  Again -- are
there any SL6x compatible source packages or installable RPMs that
supply the functionalities that I had to disable in building the current
production vlc application from source?

Yasha Karant


I have vlc 2.0.7 installed on my SL6 i686 laptop.  It's from rpmfusion,
which has, I understand, stricter policies on compliance than ATrpms.  I
don't know what, if any, restrictions were applied in the build, and I
haven't tried it on many file formats, but it works well for me.  Have
you tried/considered it?

Perhaps I should add that I'm also using an elrepo kernel and kde-unstable.

Here's the 64-bit version. extras, devel are there too.

http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/vlc-2.0.7-1.el6.x86_64.rpm


John P


I installed the rpmfusion repository, found vlc 2.0.6, and allowed the 
GUI add/remove software to proceed.  vlc 2.0.6 now is installed on my 
IA-32 laptop; when I get to the office, I will proceed with the same for 
X86-64.


Are you aware if this vlc includes all needed codecs, some of which 
evidently only can be installed from EU sources?


Otherwise, the rpmfusion repository seems to provide all of the needed 
dependencies.  (Note from the rpmfusion instructions:  You need to 
enable EPEL on RHEL 5 & 6 or compatible distributions like CentOS before 
you enable RPM Fusion for EL.)


Thank you for the reference.

Yasha Karant

Re: Fwd: Re: vlc-2.0.7

2013-07-13 Thread John Pilkington 

On 13/07/13 08:15, Yasha Karant wrote:

On 07/12/2013 05:38 PM, Todd And Margo Chester wrote:

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux application
environment is not polymorphic with encapsulation, one cannot have both
versions of some such dependency installed.


Hi Yasha,

It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T


Hi Todd,

My understanding is that your procedure can result in system instability
because of the lack of polymorphism and encapsulation.  If one uses
repositories other than those from SL6 or from those repositories that
claim the use thereof will not introduce stock (SL6x) incompatibilities,
then getting an application that requires such incompatible RPMs may
cause problems.  The solution of erasing the conflicting RPM and
presumably loading a replacement RPM that is not part of the stock
compatible distribution can "break" other applications that are
dependent upon such RPMs.

Building from a SRPM probably will not solve the problem because the
source RPM presumably requires the same RPMs (or SRPMs) that either do
not exist for stock SL6x or conflict with stock SL6x RPMs.  Again -- are
there any SL6x compatible source packages or installable RPMs that
supply the functionalities that I had to disable in building the current
production vlc application from source?

Yasha Karant

I have vlc 2.0.7 installed on my SL6 i686 laptop.  It's from rpmfusion, 
which has, I understand, stricter policies on compliance than ATrpms.  I 
don't know what, if any, restrictions were applied in the build, and I 
haven't tried it on many file formats, but it works well for me.  Have 
you tried/considered it?


Perhaps I should add that I'm also using an elrepo kernel and kde-unstable.

Here's the 64-bit version. extras, devel are there too.

http://download1.rpmfusion.org/free/el/updates/testing/6/x86_64/vlc-2.0.7-1.el6.x86_64.rpm

John P

Re: Fwd: Re: vlc-2.0.7

2013-07-13 Thread Yasha Karant 

On 07/12/2013 05:38 PM, Todd And Margo Chester wrote:

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux application
environment is not polymorphic with encapsulation, one cannot have both
versions of some such dependency installed.


Hi Yasha,

It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T


Hi Todd,

My understanding is that your procedure can result in system instability 
because of the lack of polymorphism and encapsulation.  If one uses 
repositories other than those from SL6 or from those repositories that 
claim the use thereof will not introduce stock (SL6x) incompatibilities, 
then getting an application that requires such incompatible RPMs may 
cause problems.  The solution of erasing the conflicting RPM and 
presumably loading a replacement RPM that is not part of the stock 
compatible distribution can "break" other applications that are 
dependent upon such RPMs.


Building from a SRPM probably will not solve the problem because the 
source RPM presumably requires the same RPMs (or SRPMs) that either do 
not exist for stock SL6x or conflict with stock SL6x RPMs.  Again -- are 
there any SL6x compatible source packages or installable RPMs that 
supply the functionalities that I had to disable in building the current 
production vlc application from source?


Yasha Karant

Re: Fwd: Re: vlc-2.0.7

2013-07-12 Thread Todd And Margo Chester 

On 07/12/2013 01:05 PM, Yasha Karant wrote:

The issue is that the application would not pass configure without
disabling these options.  I have tried the various pre-built RPMs for
vlc that have been mentioned, but all the ones that I have found have
dependencies that cause conflicts with other versions of the same
dependency (typically, some .so package).  Because the linux application
environment is not polymorphic with encapsulation, one cannot have both
versions of some such dependency installed.


Hi Yasha,

   It was a total pain in the butt the first few times
through.  I had to do a lot of "rpm -e xxx" and waiting
until yum would finally stop bitching.

   I did get there eventually and haven't had a problem
since.  Stick to it and you will get there too.

-T

Re: Fwd: Re: vlc-2.0.7

2013-07-12 Thread Nico Kadel-Garcia 
On Fri, Jul 12, 2013 at 4:05 PM, Yasha Karant  wrote:
> The issue is that the application would not pass configure without disabling
> these options.  I have tried the various pre-built RPMs for vlc that have
> been mentioned, but all the ones that I have found have dependencies that
> cause conflicts with other versions of the same dependency (typically, some
> .so package).  Because the linux application environment is not polymorphic
> with encapsulation, one cannot have both versions of some such dependency
> installed.

*Start* from the SRPM. and evaluate the SRPM compliments for
components that may conflict.


> I do have a version of vlc that does run but for which I do not have an RPM;
> by copying that binary, its libraries, and its support directory tree from
> machine to machine, we have a functional but rather old vlc.
>
> Hence, I am looking for a set of RPMs or a set of source code
> applications/libraries that will build under SL6x to allow me not to
> required that these codecs be disabled.

All the published SRPM's build under SL 6. You're leaving out the part
here about "does not conflict with other components from other
repositories", and that's the part that's biting you.

What winds up conflicting? And can you simply use vlc on a host
without those  conflicting components?

> As I supplied the list, does anyone have the information to allow me to
> address the above?  Presumably, once built, I can repackage the lot as a
> tar.gz file or even a non-stock RPM for EL6x .  Obviously, I could do this
> for the crippled (disabled codecs) version of vlc-2.0.7 that I currently
> have built.  Also presumably, once this issue is addressed for vlc-2.0.7, it
> will stay addressed until vlc-3 must be built.
>
> Yasha Karant

>>
>>
>

Re: Fwd: Re: vlc-2.0.7

2013-07-12 Thread Yasha Karant 
The issue is that the application would not pass configure without 
disabling these options.  I have tried the various pre-built RPMs for 
vlc that have been mentioned, but all the ones that I have found have 
dependencies that cause conflicts with other versions of the same 
dependency (typically, some .so package).  Because the linux application 
environment is not polymorphic with encapsulation, one cannot have both 
versions of some such dependency installed.


I do have a version of vlc that does run but for which I do not have an 
RPM; by copying that binary, its libraries, and its support directory 
tree from machine to machine, we have a functional but rather old vlc.


Hence, I am looking for a set of RPMs or a set of source code 
applications/libraries that will build under SL6x to allow me not to 
required that these codecs be disabled.


As I supplied the list, does anyone have the information to allow me to 
address the above?  Presumably, once built, I can repackage the lot as a 
tar.gz file or even a non-stock RPM for EL6x .  Obviously, I could do 
this for the crippled (disabled codecs) version of vlc-2.0.7 that I 
currently have built.  Also presumably, once this issue is addressed for 
vlc-2.0.7, it will stay addressed until vlc-3 must be built.


Yasha Karant

On 07/12/2013 12:55 PM, Todd And Margo Chester wrote:

Hi brother,

you disabled many codecs while configuring the  vlc...
--disable-avcodec --disable-swscale --disable-postproc

avc codec are most important with postprocessing filters.. these thing
are also disabled.. try torebuilding the same without disabling such
options

On Fri, Jul 12, 2013 at 8:34 AM, Todd And Margo Chester
mailto:toddandma...@gmail.com>> wrote:

 On 07/11/2013 05:49 PM, Yasha Karant wrote:

 Under X86-64 SL6x, I have successfully built vlc-2.0.7 from
 source with
 the configure command:

./configure --disable-lua --disable-mad --disable-avcodec
 --disable-swscale --disable-postproc --disable-a52

 the resulting vlc does run , but cannot open many types of files,
 including files of extension webm

 Does anyone know either which RPMs or which files/libraries that
 need to
 built from source will address the above shortcomings,
 irrespective of
 the geographical location from which these must be downloaded?

 Yasha Karant


 Hi Yasha,

 I just use the RPM from atrpms and the following script.
 First time through, change "upgrade" to "install".

 -T


 #!/bin/bash

 Cmd="yum --disablerepo=* --enablerepo=atrpms* upgrade vlc"
 echo "$Cmd"
 su root -c "$Cmd"

Fwd: Re: vlc-2.0.7

2013-07-12 Thread Todd And Margo Chester 

Hi brother,

you disabled many codecs while configuring the  vlc...
--disable-avcodec --disable-swscale --disable-postproc

avc codec are most important with postprocessing filters.. these thing
are also disabled.. try torebuilding the same without disabling such
options

On Fri, Jul 12, 2013 at 8:34 AM, Todd And Margo Chester
mailto:toddandma...@gmail.com>> wrote:

On 07/11/2013 05:49 PM, Yasha Karant wrote:

Under X86-64 SL6x, I have successfully built vlc-2.0.7 from
source with
the configure command:

   ./configure --disable-lua --disable-mad --disable-avcodec
--disable-swscale --disable-postproc --disable-a52

the resulting vlc does run , but cannot open many types of files,
including files of extension webm

Does anyone know either which RPMs or which files/libraries that
need to
built from source will address the above shortcomings,
irrespective of
the geographical location from which these must be downloaded?

Yasha Karant


Hi Yasha,

I just use the RPM from atrpms and the following script.
First time through, change "upgrade" to "install".

-T


#!/bin/bash

Cmd="yum --disablerepo=* --enablerepo=atrpms* upgrade vlc"
echo "$Cmd"
su root -c "$Cmd"




--







Thanks & Regards,
Pritam Khedekar | Sr. Engineer - Technical,
Vistaas Digital Media Pvt. Ltd. | Mumbai
Tel: + 91 90 22 25 54 20
Web: www.vistaas.com  | www.divineindia.com

-
Note: This communication contains information which is confidential and
may also be legally privileged. It is intended only for the use of
authorized persons. If you are not an intended recipient, or have
received the message in error, you are not authorized to read, copy,
disseminate, distribute or use the Electronic Mail or any attachment in
any way. Please notify the sender by return E-Mail or over the telephone
and delete this e-mail. The sender endeavors to exclude viruses from all
communications, but it remains the obligation of the recipient to check
any mail & attachments for viruses.

*~~ *Those who do not remember the past are condemned to repeat it.* ~~*