Re: Strange directory ownership in RPM database

2024-07-10 Thread Christoph Karl via devel
Hi! Thank you for the clarification. How about two different packages which do not depend on each other having both files/directories below /xyz/? I assume in this case co-ownership of /xyz/ should be used? Is this rule general valid or are there exceptions? Icon sizes: https://bugzilla.redhat.

Strange directory ownership in RPM database

2024-07-10 Thread Christoph Karl via devel
Hi! I have written and also tried to solve https://bugzilla.redhat.com/show_bug.cgi?id=2293749 but I am somehow stuck. I reinstalled a fresh rawhide (from Fedora-Everything-netinst-x86_64-Rawhide-20240709.n.0.iso) but I still get the following: RPM does not know about this directory: $ rpm -qf

Cleanup missing directories in RPM database

2024-06-07 Thread Christoph Karl via devel
Hi, as a follow-up to my attempt to clean up missing directories in RPM database, the following questions arose: Who should own the directories for "non-standard" icon sizes? Is there a defined set of standard sizes? Please see also BZ#2284088: How should this be solved? Thank you for any sup

Re: Files missing in RPM database

2024-05-01 Thread Christoph Karl via devel
Hi! Am 01.05.24 um 19:58 schrieb Jens-Ulrik Petersen: On Thu, May 2, 2024 at 1:21 AM Christoph Karl via devel < devel@lists.fedoraproject.org> wrote: I tried to find out which files on my upgraded fc40 installation are not installed via dnf/rpm. The list is surprisingly long. Perha

Files missing in RPM database

2024-05-01 Thread Christoph Karl via devel
Hi! I tried to find out which files on my upgraded fc40 installation are not installed via dnf/rpm. The list is surprisingly long. Main reasons are symlinks and directories not defined in the spec file. A quick check shows that this is also the case with a fresh installation. I see three reason

Re: Switching XZ for ZSTD?

2024-04-04 Thread Christoph Karl via devel
Hi! +1 The sequence must be: measure -> think -> act. Not: act (in panic) -> think (oh, that ist not the correct way, or even worse: oh, this is the way the attacker wants us to go.) measure (we have a weakness) Best regards Christoph Am 04.04.24 um 20:11 schrieb Leon Fauster via devel: One

Re: Three steps we could take to make supply chain attacks a bit harder

2024-03-31 Thread Christoph Karl via devel
+1 Am 01.04.24 um 06:31 schrieb Scott Schmit: One approach: 1. do the build 2. do the install 3. generate the RPMs 4. quarantine the RPMs so they're safe from modification - I believe this could be done via SELinux policy - there are probably other mechanisms 5. run the tests - for S