Solved Portmaster broke?

[rewtkid]

I just started using FreeBSD again and chose portmaster. I have only been using it for a few days now so if I'm doing this wrong I apologize, I did read the man page. I usually go in /usr/ports and portsnap fetch update, and then in any directory I run portmaster -a. Anyway this is what I get today after I ran portsnap fetch update.

root@bsd:/ # portmaster -a
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/python.mk
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/compiler.mk
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/objc.mk
make: Fatal errors encountered -- cannot continuemake: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/python.mk
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/compiler.mk
make: "/usr/ports/Mk/bsd.port.mk" line 1471: Cannot open /usr/ports/Mk/Uses/objc.mk
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Unknown modifier ':'
make: Fatal errors encountered -- cannot continueeval: make:: not found
export: make:: bad variable name
root@bsd:/ #

Is this something I did? or is it a temp problem with ports?

this is my custom freebsd.conf in repos. I am just using latest, and a server near me.

FreeBSD: {
#  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
   url: "pkg+http://pkg0.nyi.freebsd.org/FreeBSD:12:amd64/latest",

  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

I think it's just a temp error with ports but I want to be sure its not me being a complete tool.

 

[talsamon]

Do you have something in /etc/make.conf? Maybe, somewhere is a (wrong) ":" too much, if you have edited a file with vi (e.g. the vi-commands like ":wq"

 

[SirDice]

What version of FreeBSD?

I just started using bsd again and chose portmaster.

I would suggest starting with packages instead.

I usually go in /usr/ports and portsnap fetch update

portsnap(8) works from any directory, you don't need to change to /usr/ports for it to work.

and then in any directory I run portmaster -a.

This doesn't do what you think it does. portmaster -a updates already installed ports.

this is my custom freebsd.conf in repos.

That's not used when building from ports, it's only for pkg(8).

The errors you're getting are usually caused by trying a recent ports tree on an unsupported version. Which brings me back to my first question, what version of FreeBSD?

 

[rewtkid]

Hi thank you for those answers. I am on 12-release. Sorry I had a very busy day today and wasnt at my machine. A record three doctor appointments in one day. I ran portsnap fetch again now and portmaster is working. I think it was a temporary mistake in their tree and they fixed it. But at least now i have a better way of using these tools thanks to you guys.

 

[rewtkid]

Do you have something in /etc/make.conf? Maybe, somewhere is a (wrong) ":" too much, if you have edited a file with vi (e.g. the vi-commands like ":wq"

Thats what I thought initially and went there immediately before posting but no it seems it was a glitch in their end that they have now fixed.

 

[rewtkid]

What version of FreeBSD?


I would suggest starting with packages insteads.

I like having the option to configure and my machine is an i7 so compiling isnt a problem. Keeps me and the machine busy.


portsnap(8) works from any directory, you don't need to change to /usr/ports for it to work.


good to know.


This doesn't do what you think it does. portmaster -a updates already installed ports.

I worded it wrong, i did know that part.


That's not used when building from ports, it's only for pkg(8).

The errors you're getting are usually caused by trying a recent ports tree on an unsupported version. Which brings me back to my first question, what version of FreeBSD?

Seems not in this case its fixed, but at least I know where to look if it happens again thanks!