On Nov 8, 2016, at 2:56 PM, Johannes Kastl wrote:
> Then, building vlc fails with the following:
>> checking for mad.h... yes checking for mad_bit_init in -lmad...
>> yes checking for libavutil variant... ffmpeg checking for
>> AVCODEC... yes configure: error: libavutil versions 55 and later
>> a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
On 12.11.16 10:14 Ryan Schmidt wrote:
> https://trac.macports.org/ticket/50697
Thanks Ryan, and also for marking my bug report as a duplicate.
Funny thing is, I did search for existing bugs, and found none related
:
https://trac.macports.
On 2016-11-12 11:25, Johannes Kastl wrote:
> Searching for lowercase vlc gives one result, UPPERCASE VLC gives
> some more.
>
> Is this intended behaviour? I just had a look and the port really is
> named VLC, but installing it via "port install vlc" works. I would
> propose ignoring case during t
On 2016-11-12 14:39, Rainer Müller wrote:
> No it is not intended behavior. Matching with the preferred "contains"
> mode already ignores case:
>
> https://trac.macports.org/query?status=accepted&status=assigned&status
> =new&status=reopened&port=VLC&col=id&col=summary&col=port&col=status&c
> ol=o
Hi *,
On Sat, Nov 12, 2016 at 04:19:44PM +0100, Clemens Lang wrote:
>
> https://github.com/macports/macports-base/commit/30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
> commit 30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
> Author: Clemens Lang
> AuthorDate: Sun Nov 6 18:11:49 2016 +0100
>
>
> On Nov 12, 2016, at 9:33 AM, Clemens Lang wrote:
>
> Hi *,
>
> On Sat, Nov 12, 2016 at 04:19:44PM +0100, Clemens Lang wrote:
>>
>> https://github.com/macports/macports-base/commit/30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
>
>> commit 30c27d5d3ad169ffa5f55465cf9663dbd1ff7537
>> Author: Clem
> On Nov 12, 2016, at 10:58 AM, Rainer Müller
> wrote:
>
> Rainer Müller (raimue) pushed a commit to branch master
> in repository macports-ports.
>
>
> https://github.com/macports/macports-ports/commit/d320be827a477bb18acbdca1d9e7ab55e3434ba0
>
> The following commit(s) were added to refs/h
On 2016-11-12 18:22, Ryan Schmidt wrote:
> Forgot to add this patchfile?
>
>
> $ sudo port install man
> ---> Computing dependencies for man
> ---> Fetching archive for man
> ---> Attempting to fetch man-1.6g_1+xcode.darwin_15.x86_64.tbz2 from
> https://packages.macports.org/man
> ---> Fetch
Folks,
I have a private version of the llvm-3.9/Portfile (I just narrowed down the
targets to PowerPC and X86 rather than build everyone of them which squanders
time). But now I can’t git pull —rebase, I get an error message.
Of course I have no intention to commit that private patch. How can I
On 2016-11-12, at 9:39 AM, Vincent Habchi wrote:
> Folks,
>
> I have a private version of the llvm-3.9/Portfile (I just narrowed down the
> targets to PowerPC and X86 rather than build everyone of them which squanders
> time). But now I can’t git pull —rebase, I get an error message.
>
> Of
On 2016-11-12 17:39, Ryan Schmidt wrote:
> Many of the changes in 2.3.5 are to deal with the GitHub transition, so I
> would be in favor of releasing this change now as well.
https://github.com/macports/macports-base/blob/release-2.3/ChangeLog
That would be only the warning on 'port sync' for us
On 2016-11-12 18:39, Vincent Habchi wrote:
> I have a private version of the llvm-3.9/Portfile (I just narrowed
> down the targets to PowerPC and X86 rather than build everyone of
> them which squanders time). But now I can’t git pull —rebase, I get
> an error message.
>
> Of course I have no inten
On Sat, Nov 12, 2016 at 12:39 PM, Vincent Habchi wrote:
> I have a private version of the llvm-3.9/Portfile (I just narrowed down
> the targets to PowerPC and X86 rather than build everyone of them which
> squanders time). But now I can’t git pull —rebase, I get an error message.
>
> Of course I
> You can commit it, and in fact probably should. What you don't want to do is
> *push* that commit.
>
> If your git is new enough, you can enable auto-stashing so your change is
> saved across the rebase.
>
> git config --local --bool rebase.autostash true
>
> If not, you can do it manual
> On Nov 12, 2016, at 12:44 PM, Rainer Müller wrote:
>
>> On 2016-11-12 17:39, Ryan Schmidt wrote:
>>
>> Perhaps it should more properly be called 2.4, but since our master
>> is in no fix state to be branched for 2.4 at this time and we are
>> still figuring out our release process on GitHub, i
> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez wrote:
>
>> On Nov 12, 2016, at 12:44 PM, Rainer Müller wrote:
>>
>>> On 2016-11-12 17:39, Ryan Schmidt wrote:
>>>
>>> Perhaps it should more properly be called 2.4, but since our master
>>> is in no fix state to be branched for 2.4 at this ti
> On Nov 12, 2016, at 3:50 PM, Ryan Schmidt wrote:
>
> One consequence that occurs to me is that people using master
> currently have version 2.3.99. If we branch 2.4 from 2.3, then when
> those users run selfupdate they would be "upgraded" to 2.4 which
> doesn't contain all the features they had
On 2016-11-12 21:50, Ryan Schmidt wrote:
>
>> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez
>> wrote:
>>
>>> On Nov 12, 2016, at 12:44 PM, Rainer Müller
>>> wrote:
>>>
>>> master is definitely not in a state to be released, but the
>>> roadmap should be discussed separately. Changing the main
> On Nov 12, 2016, at 3:23 PM, Rainer Müller wrote:
>
> On 2016-11-12 21:50, Ryan Schmidt wrote:
>>
>>> On Nov 12, 2016, at 2:03 PM, Lawrence Velázquez
>>> wrote:
>>>
On Nov 12, 2016, at 12:44 PM, Rainer Müller
wrote:
master is definitely not in a state to be released, b
19 matches
Mail list logo
