Debian build

[stokito]

The debian/rules was lack of "catch all" rule so make clean was failed because there is no clean target in the Makefile. I fixed that.

Basically the rules file is intended to change something in the build of the original package. But here we have an own native package so the rules should be empty with the only catch all target.

Later (maybe) I'l send another PR that will remove the override_dh_install target and use instead Makefile or debian/install or even maybe that it would be possible with Maven assembly plugin. Will check.

Other commits reduce warnings and makes a build log more clear

CC @akrherz

[akrherz]

Thanks @stokito , could you kindly cherry pick #2531 here, so to see things in action?

[stokito]

No, it don't work that simply :( It depends on to be runned from sources. I also had a similar problem when runned locally and can't remember now how I bypassed it. I'll check in 6 hours

[akrherz]

tar -xf distribution/target/dist/distribution-artifact.tar

will extract into your cwd and not into that dist folder. -C may be of usage

[stokito]

Could you please fix that command? I can't see what is going inside, the ls output is useless.
Except of the CI job the deb build should be totally fine

[akrherz]

@stokito my suggestion for easier debugging is to add this step to the workflow prior to the step that fails

      - name: Setup upterm session
        uses: lhotari/action-upterm@v1
        with:
          limit-access-to-actor: true 

watch the build logs and when it gets to that step, the SSH command you need to run will be shown and you can ssh in and manually debug what is happening within CI at that step.

[stokito]

My guess was that the artifact contains a tar file that additionally needs to be extracted. But maybe that's not a case here.  As a temporary solution I can drop the commit with the github action so that we can merge it and at least check it the bamboo. 20 сент. 2024 г. 16:03:46 daryl herzmann ***@***.***>:

…

@stokito[https://github.com/stokito] my suggestion for easier debugging is to add this step to the workflow prior to the step that fails - name: Setup upterm session uses: ***@***.*** with: limit-access-to-actor: true watch the build logs and when it gets to that step, the SSH command you need to run will be shown and you can ssh in and manually debug what is happening within CI at that step. — Reply to this email directly, view it on GitHub[#2532 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AADFODWL5RPNNBL3SKONYCTZXQMLDAVCNFSM6AAAAABOPLN436VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTGY4TAMZXGY]. You are receiving this because you were mentioned. [Отслеживающее изображение][https://github.com/notifications/beacon/AADFODWRBRFMMU4NHJKESALZXQMLDA5CNFSM6AAAAABOPLN436WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUM4MGYQ.gif]

[akrherz]

I'll take a hack at this PR now and see how far I can get, thanks for all this effort so far!

[akrherz]

sweet, now for the epic dread of having this fail in bamboo for some strange reason

[github-actions]

Successfully created backport PR for 4.9:

• [Backport 4.9] Debian build #2533