Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-06 Thread Bigby James 
On 12/06, Florian Pritz wrote:
> On 05.12.2014 22:32, Bigby James wrote:

Thanks for clearing that up. Wasn't sure exactly what the development flow was
there.

-- 
"A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Florian Pritz 
On 05.12.2014 22:32, Bigby James wrote:
> Isn't this something that would get fixed on release? That is, wouldn't the
> version of mpv in [community] be rebuilt upon the release of the new ffmpeg
> version to [extra]? 

We have [staging]/[community-staging] for rebuilds and
[testing]/[community-testing] is supposed to be usable and properly
linked. Packages can be there for multiple reasons including being a new
version of a [core] package and the maintainer being careful/expecting
issues.

That said all issues with [testing] (and [community-testing]) should be
reported so they don't hit stable in that state. Also please follow
arch-dev-public if you use [testing] to see if the maintainer already
posted about known issues there. (not the case here)

Also please try to quote less. Refer to

for more info.



signature.asc
Description: OpenPGP digital signature

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Karol Blazewicz 
On Fri, Dec 5, 2014 at 11:57 PM, Karol Blazewicz
 wrote:
> Since Florian Fritz is a dev

It's Florian _P_ritz. Sorry for the typo and the noise.

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Karol Blazewicz 
On Fri, Dec 5, 2014 at 10:32 PM, Bigby James  wrote:
> Isn't this something that would get fixed on release? That is, wouldn't the
> version of mpv in [community] be rebuilt upon the release of the new ffmpeg
> version to [extra]? [community] packages are just one small step above the 
> AUR,
> while [testing] only contains individual, official packages awaiting release,
> not a package plus everything that depends on it.. As I understand it, this 
> sort
> of thing is inevitable and invariable when using [testing]. I'd say contact 
> the
> TU responsible for the package and ask what the normal procedure for this is
> before filing a bug report.[1] If you already filed one, it might be worth
> contacting the maintainer just to see what standard practice is in these
> situations.
>
> [1]: https://www.archlinux.org/packages/community/x86_64/mpv/

Since Florian Fritz is a dev, I trust him to know what he's talking about.
https://www.archlinux.org/people/developers/#bluewind
https://lists.archlinux.org/pipermail/arch-general/2014-December/037920.html

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Bigby James 
On 12/05, Savya wrote:
> I was running mpv from the terminal today, and I got an unexpected
> message:
> 
> "Warning: mpv was compiled against a different version of ffmpeg than
> the shared library it is linked against. This can expose subtle ABI
> compatibility issues and can lead to misbehaviour and crashes."
> 
> Installed versions of packages:
> 
> [testing]/ffmpeg: 1:2.5-1
> [community]/mpv: 0.7.1-1
> 
> I would request (if possible, of course), that mpv in community be
> compiled against the version of ffmpeg in [testing] and put in the
> [community-testing] repo whenever ffmpeg is in [testing].
> 
> Thanks!
> 
> -- 
> Cheers!
> Savya

Isn't this something that would get fixed on release? That is, wouldn't the
version of mpv in [community] be rebuilt upon the release of the new ffmpeg
version to [extra]? [community] packages are just one small step above the AUR,
while [testing] only contains individual, official packages awaiting release,
not a package plus everything that depends on it.. As I understand it, this sort
of thing is inevitable and invariable when using [testing]. I'd say contact the
TU responsible for the package and ask what the normal procedure for this is
before filing a bug report.[1] If you already filed one, it might be worth
contacting the maintainer just to see what standard practice is in these
situations.

[1]: https://www.archlinux.org/packages/community/x86_64/mpv/

-- 
"A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools." - Douglas Adams

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Karol Blazewicz 
On Fri, Dec 5, 2014 at 12:29 PM, Florian Pritz  wrote:
> On 05.12.2014 05:23, Savya wrote:
>> I would request (if possible, of course), that mpv in community be
>> compiled against the version of ffmpeg in [testing] and put in the
>> [community-testing] repo whenever ffmpeg is in [testing].
>
> Please create a bug report if there is none yet.
>

Reported: https://bugs.archlinux.org/task/43019

Re: [arch-general] mpv in [community] compiled against different version of ffmpeg than in [testing]

2014-12-05 Thread Florian Pritz 
On 05.12.2014 05:23, Savya wrote:
> I would request (if possible, of course), that mpv in community be
> compiled against the version of ffmpeg in [testing] and put in the
> [community-testing] repo whenever ffmpeg is in [testing].

Please create a bug report if there is none yet.



signature.asc
Description: OpenPGP digital signature