Cristian Le

> 1. How about naming it depends_on? Just for the sound of it :) My naming game is very weak so full :+1: on any name changes > 2. I...

Since the `propose_downstream` and `pull_from_upstream` only run on release triggers, we can only use static values for `Release:`, because `Version:` will always be updated. The question is then what should...

> But I cannot find a nice way to open a second pull-request from a Packit's fork. Maybe it's not possible in the UI, but could it be achieved in...

/packit test --identifier smoke

I am letting it run without any changes to get a benchmark of the timings at first. - Original: ~1h - Build-only: ~45min

> > Why is NDEBUG removed by default? > > I've laid out my reasoning here: [#3172 (comment)](https://github.com/cp2k/cp2k/pull/3172#issuecomment-1861632676) Note that it should not be done at a `CMAKE_C_FLAGS` level because...

What are the plans for the `Makefile`? I want to drop the custom `FindLibSPG.cmake` and `spglib_f08.F` in favor of upstream interface. I can do the former without affecting `Makefile`, but...

It seems getting the tests to run properly within the spec file is a gamble because you don't have control over the number of CPU cores to use. With testing-farm...

> > Are the tests intended to be used by normal users or only devs and packagers? > > The tests are only for validating binaries. They don't need to...

> The problem is that cp2k use assert statements for checking the validity of functions parameters That is fine as long as cp2k distinguishes between: - `assert` a check for...