On Apr 22, 2015, at 7:40 AM, Mojca Miklavec wrote:
> Maybe I need to explain a bit more.
>
> I have a sparse SVN checkout configured as:
> file:///Users/me/app/macports/trunk/dports [nosync]
>
> I used [nosync] because I'm often bitten by failures during svn
> updates when my local changes
On Wed, Apr 22, 2015 at 12:14 PM, Mihai Moldovan wrote:
> On 22.04.2015 12:00 PM, Mojca Miklavec wrote:
>> Thanks again and sorry for the noise,
>
> No, not noise. Let me explain why.
>
>
>> Hm. Interesting.
>>
>> Thank you, it seems that running portindex solved the problem indeed.
>> I now got a
On 22.04.2015 12:28 PM, René J.V. Bertin wrote:
> On Wednesday April 22 2015 12:14:09 Mihai Moldovan wrote:
>> The portindex is generated on the rsync machine, which is running Linux. If
>> doing funky stuff that happens to abort Portfile parsing ungracefully (like
>> not wrapping sysctl stuff in
On Wednesday April 22 2015 12:14:09 Mihai Moldovan wrote:
> The portindex is generated on the rsync machine, which is running Linux. If
> doing funky stuff that happens to abort Portfile parsing ungracefully (like
> not wrapping sysctl stuff in "catch"), the index will be stale for these
> port
On 22.04.2015 12:00 PM, Mojca Miklavec wrote:
> Thanks again and sorry for the noise,
No, not noise. Let me explain why.
> Hm. Interesting.
>
> Thank you, it seems that running portindex solved the problem indeed.
> I now got a long list of outdated ports.
That's interesting indeed.
> I didn
On Wed, Apr 22, 2015 at 11:10 AM, Mihai Moldovan wrote:
> On 22.04.2015 09:00 AM, Mojca Miklavec wrote:
>> MacPorts is behaving a bit weird. It doesn't report some outdated
>> ports and as a consequence doesn't upgrade them. I need some clues
>> about where I could look to diagnose the source of th
On 22.04.2015 09:00 AM, Mojca Miklavec wrote:
> MacPorts is behaving a bit weird. It doesn't report some outdated
> ports and as a consequence doesn't upgrade them. I need some clues
> about where I could look to diagnose the source of the problem.
>
>> port installed texlive-bin
> The following p
On Wednesday April 22 2015 09:05:08 Marko Käning wrote:
>thanks so much for raising this issue. I was puzzled myself yesterday
>that I seemed to have some weird behaviour with outdated ports…
>
>Same symptoms here! :(
I've seen similar things happen (with my own "base" that was last selfupdated
Hi Mojca,
On 22 Apr 2015, at 09:00 , Mojca Miklavec wrote:
> MacPorts is behaving a bit weird. It doesn't report some outdated
> ports and as a consequence doesn't upgrade them. I need some clues
> about where I could look to diagnose the source of the problem.
thanks so much for raising this
Hello,
MacPorts is behaving a bit weird. It doesn't report some outdated
ports and as a consequence doesn't upgrade them. I need some clues
about where I could look to diagnose the source of the problem.
> port installed texlive-bin
The following ports are currently installed:
texlive-bin @2014
10 matches
Mail list logo