On Mar 11, 2018, at 21:53, Bill Cole wrote:
> On 10 Mar 2018, at 18:47 (-0500), db wrote:
>
>> Btw, how can I change the two-week period for the warning. I couldn't find
>> an option in macports.conf, either to change the period or to suppress it
>> altogether.
>
> port reclaim --disable-remi
On 10 Mar 2018, at 18:47 (-0500), db wrote:
Btw, how can I change the two-week period for the warning. I couldn't
find an option in macports.conf, either to change the period or to
suppress it altogether.
port reclaim --disable-reminders
That puts the word 'disabled' into /opt/local/var/macp
On 11 Mar 2018, at 04:01, Ryan Schmidt wrote:
> On Mar 10, 2018, at 17:47, db wrote:
>> Btw, how can I change the two-week period for the warning. I couldn't find
>> an option in macports.conf, either to change the period or to suppress it
>> altogether.
> I don't think we offer any options to c
On Mar 10, 2018, at 17:47, db wrote:
> Btw, how can I change the two-week period for the warning. I couldn't find an
> option in macports.conf, either to change the period or to suppress it
> altogether.
I don't think we offer any options to configure that. We want users to stay up
to date; w
On 10 Mar 2018, at 23:15, Clemens Lang wrote:
>
> https://github.com/macports/macports-ports/blob/master/sysutils/bash-completion/files/port
> so if you have time you could try modifying it to drop stderr into nirvana
> and submit a pull request for that.
Ok, I'll have to take a closer look, a
On Sat, Mar 10, 2018 at 09:24:27PM +0100, db wrote:
> On 10 Mar 2018, at 20:05, Ryan Schmidt wrote:
> > Are your port definitions in fact more than two weeks old?
>
> Yes, but I'd expect the warning after I actually ran the command.
Unfortunately that happens because the bash completion executes
On Mar 10, 2018, at 14:24, db wrote:
> On 10 Mar 2018, at 20:05, Ryan Schmidt wrote:
>> Are your port definitions in fact more than two weeks old?
>
> Yes, but I'd expect the warning after I actually ran the command.
When you press tab, the bash completion code runs. Looking at the contents of
On 10 Mar 2018, at 20:05, Ryan Schmidt wrote:
> Are your port definitions in fact more than two weeks old?
Yes, but I'd expect the warning after I actually ran the command.
On Mar 10, 2018, at 12:18, db wrote:
>
> bash-completion for port outputs stderr on pressing tab, right before it
> completes a word, on certain actions like contents.
>
> $ port contents bash-complWarning: port definitions are more than two weeks
> old, consider updating them by running 'port
bash-completion for port outputs stderr on pressing tab, right before it
completes a word, on certain actions like contents.
$ port contents bash-complWarning: port definitions are more than two weeks
old, consider updating them by running 'port selfupdate'.
etion
Can anyone reproduce it?
10 matches
Mail list logo
