Solved 13.0 ports configuration issue

Argentum

Argentum

I have installed FreeBSD 13.0 from source code -
forums.freebsd.org

Solved - DRM is dead after 13-RC2 install

Hello! Performed an experiment with 13.0 RC2. Everything went well until the DRM needed to be reinstalled. Do you have any ideas how to proceed? The system is up and working, even my persistent L2ARC from former OpenZFS is there. But I can not build the DRM. Here is my log: bectl create...
forums.freebsd.org forums.freebsd.org

Now experimentally working with it and building some ports I have found that every make configresults with Segmentation fault (core dumped) and dialog4ports.core

Seems that dialog4ports(1) fails after each run. Also, it does not write the configuration and the dialog screen does not look good:

1616400191265.png


I have rebuilt the whole system, but the issue remains the same.

Any ideas?
 
SirDice said:
Note that RC3 has been released.
Click to expand...
Just building. I have:

gitup release -v 1
Code: 
# Host: git.freebsd.org
# Port: 443
# Repository: /src.git
# Target: /usr/src
# Have: 8f731a397ad4dc7b17622c0e69ac045f4a7b9d5b
# Want: 8f731a397ad4dc7b17622c0e69ac045f4a7b9d5b
# Branch: releng/13.0
 
diizzy said:
Have you rebuilt dialog4ports?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244204 ?
Click to expand...
I am building the whole source right now. Will take some time.

But the issue is probably not solved yet.

244204 – ports-mgmt/dialog4ports - Segmentation fault after upgrade to 13.x-currrent

bugs.freebsd.org bugs.freebsd.org

I have regularly downloaded the fresh source and not seen any commits in concern of this issue. Will keep an eye on it.
Does not hurt much. The ports are building with an existing or default configuration.

The whole idea of my personal test system is to get everything running before I upgrade my main system. I am not in hurry and I will not upgrade before the release anyway.
 
Argentum said:
Is there any guideline about using this bbcode?
Click to expand...
forums.freebsd.org

Formatting Guidelines

1. Please write as clearly as possible. Use English punctuation and capitalization, and avoid abbreviating things. This helps to improve the clarity of messages and make problems easier to solve. 2. Use BBCode formatting tags. As with punctuation, these tags make messages easier to read...
forums.freebsd.org forums.freebsd.org
 
SirDice said:
forums.freebsd.org

Formatting Guidelines

1. Please write as clearly as possible. Use English punctuation and capitalization, and avoid abbreviating things. This helps to improve the clarity of messages and make problems easier to solve. 2. Use BBCode formatting tags. As with punctuation, these tags make messages easier to read...
forums.freebsd.org forums.freebsd.org
Click to expand...
I have seen that and there is not a single word about ispoiler. I have also checked the bbcode help page.
 
Question:
Spoilers (not the inline spoilers) aren't mentioned either in the guidelines.

I have been using them more frequently in cases where, for example, long code, manual page excerpts etc, which are only of interest to few readers, can be "hidden" unless somebody actually is interested to see/read that stuff.
This has the advantage of keeping the posts "short", without need for much scrolling.

Good or bad practice?
 
I personally don't like them because it requires me to click on them to see what it is. So I often don't even look at it.
 
Argentum said:
But the issue is probably not solved yet.

244204 – ports-mgmt/dialog4ports - Segmentation fault after upgrade to 13.x-currrent

bugs.freebsd.org bugs.freebsd.org

I have regularly downloaded the fresh source and not seen any commits in concern of this issue. Will keep an eye on it.
Click to expand...
Rebuilt and installed the latest world and kernel. Now I have: FreeBSD Demo 13.0-RC3 FreeBSD 13.0-RC3 #2 8f731a397: Mon Mar 22 13:54:04 EET 2021 root@Demo:/usr/obj/usr/src/amd64.amd64/sys/ARGENTUM amd64

As expected, the dialog4ports issue remains.
 
Argentum said:
The bug has been reported, but seemingly not been fixed yet - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244204#c15
Click to expand...

I don't think PR 244204 has something to do with your situation. I'm running 13.0-RC3, installed from a installer image, ports-mgmt/dialog4ports installed from package. It's running fine, all configurations are saved, dialog window looks normal, environment is unmodified default. What is affecting your system it's affecting yours only.

I suggest you examine the .core file, start debugging there.
 
T-Daemon said:
I don't think PR 244204 has something to do with your situation. I'm running 13.0-RC3, installed from a installer image, ports-mgmt/dialog4ports installed from package. It's running fine, all configurations are saved, dialog window looks normal, environment is unmodified default. What is affecting your system it's affecting yours only.

I suggest you examine the .core file, start debugging there.
Click to expand...
Thank you! All good now. Ran portupgrade -f ports-mgmt/dialog4ports and the issue is solved.
 
T-Daemon said:
I'm running 13.0-RC3, installed from a installer image, ports-mgmt/dialog4ports installed from package. It's running fine, all configurations are saved, dialog window looks normal, environment is unmodified default. What is affecting your system it's affecting yours only.
Click to expand...
I have a recent 13-STABLE (updated last weekend) and several 13.0-RC2 and 13.0-RC3 installs. I don't have a problem with ports-mgmt/dialog4ports either. Never had actually (I have several 13 machines since BETA4).
 
You must log in or register to reply here.
Back
Top