On Sat, 3 May 2008 13:35:10 -0400
Sahil Tandon [EMAIL PROTECTED] wrote:
Hi. I'm running FreeBSD 6.1. I have never had a problem with
portmanager until today. I was trying to update amavisd-new. When I
issued the upgrade command, portmanager started to update perl5.8.
Everything was going
* Gerard [EMAIL PROTECTED] [2008-05-03 14:47:56 -0400]:
On Sat, 3 May 2008 13:35:10 -0400
Sahil Tandon [EMAIL PROTECTED] wrote:
Hi. I'm running FreeBSD 6.1. I have never had a problem with
portmanager until today. I was trying to update amavisd-new. When I
issued the upgrade
I had (have?) several packages in the ports collection that needed
updating, and recently someone in the list was talking about using
portmanager -u to save on problems with updating; it doesn't touch the
ports database, it won't mess up the collection, it walks dependencies
automagically,
cali wrote:
The same thing happened to me. Not sure where it was stuck but I was
getting a distinct sense of deja-vu watching the output (I don't really
mean deja-vu but I can't think of a better way to say it). I left it for
30 hours, and then cancelled it. I'm going to try and run it again
On Jan 26, 2005, at 4:38 AM, cali wrote:
I had (have?) several packages in the ports collection that needed
updating, and recently someone in the list was talking about using
portmanager -u to save on problems with updating; it doesn't touch
the ports database, it won't mess up the collection,
On Tuesday 25 January 2005 07:07 am, Bart Silverstrim wrote:
I had (have?) several packages in the ports collection that needed
updating, and recently someone in the list was talking about using
portmanager -u to save on problems with updating; it doesn't touch
the ports database, it won't
On Wednesday 26 January 2005 05:38 am, Bart Silverstrim wrote:
On Jan 26, 2005, at 4:38 AM, cali wrote:
I had (have?) several packages in the ports collection that needed
updating, and recently someone in the list was talking about using
portmanager -u to save on problems with updating; it
On Jan 26, 2005, at 10:40 AM, Michael C. Shultz wrote:
Thanks Bart for your patience, this one required me to set up
XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports.
Perfectly understandable and I thank you for the efforts you're going
through to get portmanager updated so
On Wednesday 26 January 2005 05:38 am, Bart Silverstrim wrote:
On Jan 26, 2005, at 4:38 AM, cali wrote:
I had (have?) several packages in the ports collection that needed
updating, and recently someone in the list was talking about using
portmanager -u to save on problems with updating; it
On Wednesday 26 January 2005 07:49 am, you wrote:
On Jan 26, 2005, at 10:40 AM, Michael C. Shultz wrote:
Thanks Bart for your patience, this one required me to set up
XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports.
Perfectly understandable and I thank you for the efforts
On Wednesday 26 January 2005 08:27 am, you wrote:
On Jan 26, 2005, at 11:07 AM, Michael C. Shultz wrote:
That works on December 1st, I'm not certain about the current date
yet.
Further info, on December 1st /usr/ports/graphics/dri is the
correct dri
for XFree86-4. I have all of this
On Wednesday 26 January 2005 08:50 am, you wrote:
On Jan 26, 2005, at 11:36 AM, Michael C. Shultz wrote:
Bart, here is what I think will happen based on what I see here, I
think
it will get past XFree-4-servers ok, but the next program that
needs dri is going to bring the wrong one back
To keep everyone informed, here is how portmanager's looping problem
with XFree86 is going to be handled:
portmanager version 0.2.4_1
Adding three strikes checking. When make is run on a port
it gets 1 strike, if it's made a second time it gets 2 strikes and a
warning will be printed,
I'd like to report a similar problem with the linux_base system. My
box has been recompiling linux_base-rh-7.3 for 12 hours now! :-)
The three strikes method sounds like a good temporary fix to the
problem. Please let us know when you get it posted!
--
Alan Gerber
Michael C. Shultz wrote:
To
On Wednesday 26 January 2005 06:11 pm, Alan Gerber wrote:
I'd like to report a similar problem with the linux_base system. My
box has been recompiling linux_base-rh-7.3 for 12 hours now! :-)
The three strikes method sounds like a good temporary fix to the
problem. Please let us know when
I've submitted a PR for the interim fix to portmanager's looping problem
here is the link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=76739
If anyone is in a hurry I will be glad to send the patch as an email
attachment, all you need to do is create
a /usr/ports/sysutils/portmanager/files
16 matches
Mail list logo
