9.2.0 inv install does not create core.conf or logging.conf on installation

[lamestllama]

Describe the bug
9.2.0 does not create core.conf or logging.conf on installation

To Reproduce
Steps to reproduce the behavior:
Install 9.2.0 without pre existing core.conf or logging.conf

Expected behavior
previously these files where created at installation this works with both 9.1.0 and 9.0.3

Desktop (please complete the following information):

• OS: Ubuntu Ubuntu 22.04.5 LTS
• CORE Version 9.2.0

[bharnden]

Just to make sure you are looking in the right place, you are looking at /opt/core/etc?

[FamousPond]

Yes I am getting the same bug. Older versions of cp (GNU coreutils 8.32) don't allow for arguments with --update.

[bharnden]

I see, but that's also using the inv install aspect? The hope is to push using the package like approach. Ideally no need to use this method.

[FamousPond]

Sorry for the multiple pull requests. Technical difficulties.

There are no packages for arm so I need to use inv install method.

[lamestllama]

Yes

…

On 13 Feb 2025, at 10:43 AM, bharnden ***@***.***> wrote: Just to make sure you are looking in the right place, you are looking at /opt/core/etc? — Reply to this email directly, view it on GitHub <#906 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACXEMRBOWAW7FXW4KFMQLL2PPPTLAVCNFSM6AAAAABXA2DTC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJVGEZTGMZUGI>. You are receiving this because you authored the thread.

[bharnden]

Sorry for the multiple pull requests. Technical difficulties.

There are no packages for arm so I need to use inv install method.

There is no expectation currently for working in an arm based environment. I would personally avoid that path altogether.

[lamestllama]

There is no expectation currently for working in an arm based environment. I would personally avoid that path altogether.

I and more recently Famouspond have been using an arm based linux for the last two years. Its unavoidable for us.

[lamestllama]

To clarify currently using arm64 on Apple silicon

[bharnden]

Has everything including EMANE been working for you in this environment otherwise? just curious.

Will look to revert or find a better solution.

[lamestllama]

Yes, everything including EMANE has been working for us. We build quite large networks automagically including adding a lot of services and protocols. So the move from 9.0.3 to 9.1.0 gave us a huge performance fail. We have a fork with a fix for this problem we are testing at the moment. If it works out famouspond will send you a pull request.

…

On 14 Feb 2025, at 10:35 AM, bharnden ***@***.***> wrote: bharnden left a comment (coreemu/core#906) Has everything including EMANE been working for you in this environment otherwise? just curious. Will look to revert or find a better solution. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. <#906 (comment)> <https://github.com/notifications/unsubscribe-auth/AACXEMRH76AME4BNNJIGVG32PUXLFAVCNFSM6AAAAABXA2DTC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXHE3DCMJWGY> bharnden left a comment (coreemu/core#906) <#906 (comment)> Has everything including EMANE been working for you in this environment otherwise? just curious. Will look to revert or find a better solution. — Reply to this email directly, view it on GitHub <#906 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACXEMRH76AME4BNNJIGVG32PUXLFAVCNFSM6AAAAABXA2DTC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXHE3DCMJWGY>. You are receiving this because you authored the thread.