Hi,
My FreeBSD machine's port collections are updated, checked etc via the portsnap, portaudit and portmaster. If there's any new updates to my installed ports, they will be found by a daily portmaster -L and an email sent to me if there's any.
So, today I had two updates available:
Super. I go root and normally I would just issue [cmd=]portmaster -a[/cmd] and things would pretty much take care of themselves. But not today.
portmaster goes into what seems to be a loop when trying to update p5-libwww:
For each loop, another " >> p5-libwww-5.837" is added to the already long list seen above. I have really absolutely no clue as to what causes this. I have tried rerunning all that I could think of; portsnap update, portmaster. When I terminate the loop, I get an equally long list of build/install processes being terminated ("===>>> Build/Install for www/p5-libwww exiting due to signal").
I'm a bit puzzled as why it suddenly breaks. Have any of you seen this behaviour?
Best regards,
Klaus
My FreeBSD machine's port collections are updated, checked etc via the portsnap, portaudit and portmaster. If there's any new updates to my installed ports, they will be found by a daily portmaster -L and an email sent to me if there's any.
So, today I had two updates available:
Code:
===>>> New version available: en-freebsd-doc-20110710
===>>> New version available: p5-libwww-6.02
Super. I go root and normally I would just issue [cmd=]portmaster -a[/cmd] and things would pretty much take care of themselves. But not today.
portmaster goes into what seems to be a loop when trying to update p5-libwww:
Code:
===>>> Launching child to update p5-libwww-5.837 to p5-libwww-6.02
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-
5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >>
p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837 >> p5-libwww-5.837
For each loop, another " >> p5-libwww-5.837" is added to the already long list seen above. I have really absolutely no clue as to what causes this. I have tried rerunning all that I could think of; portsnap update, portmaster. When I terminate the loop, I get an equally long list of build/install processes being terminated ("===>>> Build/Install for www/p5-libwww exiting due to signal").
I'm a bit puzzled as why it suddenly breaks. Have any of you seen this behaviour?
Best regards,
Klaus