On Mon, 22 Dec 2014 11:36:01 +0000, susejunky wrote:
> Dear Community,
>
> for many years i am using the Videolan-Repository
> “http://download.videolan.org/pub/videolan/vlc/SuSE/nn.m”.
>
> Since the end of last week i can’t access it anymore. Using
> http://www.videolan.org/vlc/download-suse.html does not help either and
> under http://download.videolan.org/ i cannot find a directory “pub”.
>
> Is that a common problem and does anyone have more information?
>
> Thanks for your help and best regards
>
> susejunky
>
> PS:
> I know that nearly all packages of the VLC-Repo can be found in the
> Packman-Repository as well.
I saw a report today that this has been fixed now.
On Mon, 22 Dec 2014 23:13:38 +0000, Jim Henderson wrote:
> On Mon, 22 Dec 2014 11:36:01 +0000, susejunky wrote:
>
>> Dear Community,
>>
>> for many years i am using the Videolan-Repository
>> “http://download.videolan.org/pub/videolan/vlc/SuSE/nn.m”.
>>
>> Since the end of last week i can’t access it anymore. Using
>> http://www.videolan.org/vlc/download-suse.html does not help either and
>> under http://download.videolan.org/ i cannot find a directory “pub”.
>>
>> Is that a common problem and does anyone have more information?
>>
>> Thanks for your help and best regards
>>
>> susejunky
>>
>> PS:
>> I know that nearly all packages of the VLC-Repo can be found in the
>> Packman-Repository as well.
>
> I saw a report today that this has been fixed now.
Also, just for future reference - the VideoLAN repository is not
maintained by the openSUSE project, and they have their own forums -
questions like this are best asked of them directly rather than asking
here.
I saw that there were a couple threads on their own forums, which
answered the question for me.
On 2014-12-22 15:36, wolfi323 wrote:
>
> susejunky;2684597 Wrote:
>> Because it’s (sometimes) more up to date ?
>>
> No it isn’t.
> Both the vlc packages on Packman and the vlc packages in the VLC repo
> are just links to the vlc package on OBS:
> https://build.opensuse.org/package/show/multimedia:libs/vlc
>
> All changes there are propagated to Packman and the VLC repo at the same
> time.
I don’t know, but I’m sure the SUSE lawyers would grumble at that.
I was told that the packman packagers are the same people that at
openSUSE, but they use different “configure” options, because openSUSE
can not include all the codecs for legal reasons.
If the situation has changed, I’m very surprised. :-?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On Tue 23 Dec 2014 12:15:08 AM CST, Carlos E. R. wrote:
On 2014-12-22 15:36, wolfi323 wrote:
>
> susejunky;2684597 Wrote:
>> Because it’s (sometimes) more up to date ?
>>
> No it isn’t.
> Both the vlc packages on Packman and the vlc packages in the VLC repo
> are just links to the vlc package on OBS:
> Show multimedia:libs / vlc - openSUSE Build Service
>
> All changes there are propagated to Packman and the VLC repo at the
> same time.
I don’t know, but I’m sure the SUSE lawyers would grumble at that.
I was told that the packman packagers are the same people that at
openSUSE, but they use different “configure” options, because openSUSE
can not include all the codecs for legal reasons.
If the situation has changed, I’m very surprised. :-?
Hi
Both packman and videolan have their own open build service instance,
packages are pulled to either instance via the api, then built on the
instance to each (packman/videolan) requirements.
Seems easier to maintain one package then add bcond flags to the spec
file so depending where it’s ‘pulled’ to sets the requirements.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
> Hi
> Both packman and videolan have their own open build service instance,
> packages are pulled to either instance via the api, then built on the
> instance to each (packman/videolan) requirements.
AHHH!
> Seems easier to maintain one package then add bcond flags to the spec
> file so depending where it’s ‘pulled’ to sets the requirements.
I understand now.
Thus the resulting package is different, but they only need to maintain
“one”. COOL!
However, it also means that if the “top” buildservice breaks, all break >:-P
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)