Ports Collection support for your FreeBSD version has ended, and no ports are

bagas

Active Member

Reaction score: 2
Messages: 148

Hello.
Updated ports.
Code:
# portsnap fetch extract update

I start updating the ports.
Code:
# portupgrade -arR

Each port has this problem.
How to be !?
Code:
--->  Upgrading 'py27-docutils-0.14' to 'py27-docutils-0.14_1' (textproc/py-docutils)
--->  Building '/usr/ports/textproc/py-docutils'
===>  Cleaning for py27-docutils-0.14_1
===>  Cleaning for py36-docutils-0.14_1
/!\ ERROR: /!\

Ports Collection support for your FreeBSD version has ended, and no ports are
guaranteed to build on this system. Please upgrade to a supported release.

No support will be provided if you silence this message by defining
ALLOW_UNSUPPORTED_SYSTEM.

*** Error code 1

Stop.
make[1]: stopped in /usr/ports/textproc/py-docutils

Code:
# uname -rms
FreeBSD 11.0-RELEASE-p15 amd64
 

ShelLuser

Son of Beastie

Reaction score: 1,829
Messages: 3,621

Other than that you might want to use portsnap fetch update or portsnap fetch extract but not both, that's really defeating the whole point. update is used so that you don't have to extract the entire ports collection again, which saves time.

But yeah, always keep an eye out for the currently supported releases and their expiration date. See this link.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 9,504
Messages: 34,294

All .0 versions have expired around three months after the release of a .1 version.

But note that the support schedule has changed for 11.0 and onward. Now only the latest minor version will be supported. So when 11.2 will eventually be released 11.1 will expire three months later.
 

marino

Daemon

Reaction score: 446
Messages: 1,091

Hello.
I start updating the ports.
Code:
# portupgrade -arR

Each port has this problem.
How to be !?

I am surprised nobody has mentioned that portupgrade no longer works with ports since FLAVORS came in. That's the major reason for "how can it be?".
 

paulj

New Member


Messages: 10

]"I am surprised nobody has mentioned that portupgrade no longer works with ports since FLAVORS came in. That's the major reason for "how can it be?".

I am unable to install anything lately using ports. I tried building synth and got:

Code:
"Ports Collection support for your FreeBSD version has ended, and no ports are
guaranteed to build on this system. Please upgrade to a supported release."


My system is running 11.1 p5
 

marino

Daemon

Reaction score: 446
Messages: 1,091

I'm not sure what your point is. The message seems self-explanatory.
This has nothing to do with flavors or synth or anything.
 

paulj

New Member


Messages: 10

Well, I'm a newbie, so it isn't self explanatory to me.

Why isn't release 11.1 p5 supported is the question I'm asking, is the Ports system broken on my install or what?

There are newer versions of software I have installed (using the pkg system) in the ports tree, but I can't build or install them. I'm just trying to figure out why.
 

marino

Daemon

Reaction score: 446
Messages: 1,091

actually looking at the version, 11.1 p5 should be supported. It's newer than what i have.
Are you using a stock version of ports?
 

paulj

New Member


Messages: 10

I installed the Ports tree using:
# portsnap fetch
# portsnap extract


then before I attempt a build I use:
# portsnap update

make fails with the message in my post.

I'm wondering if upgrading a package I'm running from it's web interface instead of thru Ports has messed up the system somehow
 

marino

Daemon

Reaction score: 446
Messages: 1,091

you're not building inside a jail are you? e.g. outdated poudriere jail?
 

paulj

New Member


Messages: 10

I'm building in a jail under Nas4Free. It's a vanilla jail running three programs. One I was able to update internally. The other two no luck.

I've built packages previously in this jail, just not the last couple months.

Edit

The jail returns the same release info as the base system.
 

marino

Daemon

Reaction score: 446
Messages: 1,091

you are getting that "release info" from uname?
If so, you're just looking at the base system, not the jail. (uname reads the running kernel)
I suspect your jail needs updating.
 

paulj

New Member


Messages: 10

I thought I did, thru the NAS4Free web interface.

It reports the jail as updated.

How would I check to verify if the jail updated from command line?

Edit:

Or, update from the command line.
 

marino

Daemon

Reaction score: 446
Messages: 1,091

right, if you are getting info from uname, you have to ignore it. That's what I meant (in other words, DON'T use uname)
I don't know anything about nas4free, so I can't here there, sorry.
 

paulj

New Member


Messages: 10

I think NAS4Free is a pared-down version of FreeBSD. The jail I'm running is a full version I assume but we know about assume…

Well, it turns out Nas4Free has an option to download the ports tree from within it's web interface. Maybe it's different than the FreeBSD ports tree, so I've opted to overwrite the current tree with this one. Maybe…
 

paulj

New Member


Messages: 10

I appreciate the warning, I've tried to find help in the NAS4Free forums but this is a new problem.

I previously built packages in this jail without these troubles, so I thought it might be a FreeBSD problem. Others here are getting the same error (maybe for different reasons though).
 

paulj

New Member


Messages: 10

Just an FYI. Updating the ports tree from within Nas4Free didn't help. Will continue the search for answers…
 

hedwards

Active Member

Reaction score: 23
Messages: 217

Your jail is probably out dated. Use freebsd-version(1), not uname(1).
Possibly, I suppose that it could also be some sort of corruption. I've noticed that the ports right now seem to use versions that don't match with what's installed for 11.1R as well as the message.

Which is something the OP should probably look at if the version is what it's supposed to be.

I hadn't thought about using, freebsd-version in my investigations of my similar problem. Thanks for that hint.
 
Top