On 3/21/2013 8:42 AM, Peter Olsson wrote: > On Thu, Mar 21, 2013 at 07:17:12AM -0500, Bryan Drewery wrote: >> On 3/21/2013 5:21 AM, Peter Olsson wrote: >>> On Thu, Mar 21, 2013 at 10:49:29AM +0100, Baptiste Daroussin wrote: >>>> On Thu, Mar 21, 2013 at 03:06:43PM +0530, Vikas Mahajan wrote: >>>>> On 21 March 2013 13:26, Baptiste Daroussin <b...@freebsd.org> wrote: >>>>> >>>>>> Try replacing the ports-mgmt/pkg/files/patch-Makefile by this one: >>>>>> http://people.freebsd.org/~bapt/patch-Makefile >>>>> There was no file named patch-Makefile. I created new file with contents >>>>> as >>>>> given by you, but still getting same error. >>>>> >>>>>> And tell me if it works. >>>>>> >>>>>> But please notice that 7.x is EOLed 28 feb, more and more the ports tree >>>>> will >>>>>> get incompatible, and if we want to follow the direction for FreeBSD 10 >>>>> (replace >>>>>> our make by bmake) we will need to a day or another break totally >>>>> compatibility >>>>>> with 7. >>>>>> >>>>>> Consider upgrading your boxes. >>>>> I repeated same steps on March 13th on some other box and everything >>>>> works. >>>>> Introduction of new dialog created problem. Steps, I followed to get >>>>> latest >>>>> ports: >>>>> # portsnap fetch >>>>> # mv /usr/ports /usr/ports_old >>>>> # portsnap extract >>>>> >>>>> >>>>> -- >>>>> Regards >>>>> >>>>> Vikas Mahajan >>>> >>>> I just tested on a 7.x it works out of the box. I don't know what is >>>> happening >>>> on your system. or maybe portsnap for unknown reason is giving a wrong old >>>> version. >>>> >>>> regards, >>>> Bapt >>> >>> I get the sqrt error while trying to install dialog4ports on >>> all my servers that are still running 7.4. I try installing >> >> 7.4 is EOL. If you want to continue using it you will need to use >> RELEASE_7_EOL. head is not supported. > > I know that, and I don't care about this error in > my servers. They are scheduled for upgrade to 8 or 9. > I just replied to Bapt's comment that he got it to work > in 7.x, because I had seen the same problem as Vikas. > I should have made this clear in my reply. > >>> And, for the record, I'm really pi**ed off about the way that >>> this clear POLA violation was introduced without mention in >>> ports UPDATING. I ran portmaster upgrades in several servers >>> (7.4, 8.3 and 9.0) yesterday, and all of them just skipped >>> every config dialog with this error: >>> env: /usr/local/bin/dialog4ports: No such file or directory >> >> UPDATING is for *manual port changes needed for upgrading*. This *was* >> documented in CHANGES which is for ports infrastructure updates. >> >> It's not fair to call a bug a POLA violation. It should be fixed now. > > So this env problem was just a bug in portmaster? > Ok, I didn't know that, I thought it was a general > problem with dialog4ports. Then I'm sorry I called > it a POLA violation.
The problems with it building and missing should both be fixed now. Those were bugs with the dialog4ports support. > > However I still think that this change in the ports > environment could have justified a mention in UPDATING, > since CHANGES is aimed at developers and committers, not > ordinary users like myself. That's a fair point. I'll add an entry. > > Peter Olsson > -- Regards, Bryan Drewery bdrewery@freenode/EFNet
signature.asc
Description: OpenPGP digital signature