On Sun, Apr 8, 2018 at 7:49 PM, stan <stanl-fedorauser@xxxxxxxxxxx> wrote: > On Sun, 08 Apr 2018 14:35:35 +0200 > Björn 'besser82' Esser <besser82@xxxxxxxxxxxxxxxxx> wrote: > >> Same file conflict happens with regular build of `kernel-core-4.17.0- >> 0.rc0.git4.1.fc29` from/in recent Rawhide. The conflict existed before: # rpm -qf /usr/share/licenses/kernel-core/COPYING kernel-core-4.15.13-300.fc27.x86_64 kernel-core-4.15.15-300.fc27.x86_64 AFAICT the files were identical, but the content changed between f27: d7810fab7487fb0aad327b76f1be7cd7 /usr/share/licenses/kernel-core/COPYING and f29: bbea815ee2795b2f4230826c0c6b8814 ./usr/share/licenses/kernel-core/COPYING (in fact the file is completely different). This can be traced to upstream's commit "COPYING: use the new text with points to the license files" from 2018-03-23: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/COPYING?id=bf02d491237eea10290bd379bf7fc8c37ac6c3b4 > That makes it sound like there is an issue with the spec file for git > 4.1. I'm not familiar enough with packaging to know why this happens, > but I see this file conflict error fairly regularly with other > packages. I don't know what the fix is, though I've seen it repaired. > > Should I open a ticket against the kernel, or is this thread in > the kernel mailing list enough? Please file a bug with the above information. _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
