Florian Festi
Florian Festi
We welcome an automatic way to add these sort of dependencies automatically without packagers needing to care. I don't have a deeper insight or strong opinion whether these ELF entries...
No, refactoring does not help here. This is a general problem: Those debuginfo packages' existence depends on the content of their associated sub package. The content does not exist until...
In the end we have to accept we can't get a correct list and we have to decide whether the list errs on to many or too little packages or...
While the code looks ok, I wonder if there is a better way to do this? We should be able to add the debuginfo generation into `%__spec_install_pre`. This was not...
Ok, the longer I look at this from up close the more head ache I get. May be lets leave this as is....
It's quite possible that this is a bug. Can you still please verify that these files are not owned by another package by running `rpm -qf /usr/bin/strip`? Thanks!
[Pass arg2 (albeit -1) to transaction triggers too](https://github.com/rpm-software-management/rpm/pull/3018/commits/9a069b03ba6e51790aed5c19163e1b8658c1e71b) should talk about "file triggers" in the commit message.
This can probably be done as a plugin nowadays.
List of things to talk about: - Upstream tarball + patches to see what are the packager's changes - SRPM has all needed to rebuild the package on its "home"...
I agree, may be just a few sentences per item or may be even only one and the link to the rest of the manual for details.