Description of problem: checksum mismatch - patch-4.4-rc[12].xz Version-Release number of selected component (if applicable): kernel-4.4.0-0.rc[12].git0.1.fc24 How reproducible: 101% Steps to Reproduce: 1. compare checksum Actual results: checksum -mismatch- Expected results: checksum -match- Additional info: checksum mismatch - patch-4.4-rc[12].xz - UPSTREAM: kernel.org $ curl -s https://cdn.kernel.org/pub/linux/kernel/v4.x/testing/sha256sums.asc | grep 'patch-4.4-rc[12].xz' 3870efdb5dfdbcb17d5a233e8e9c69156609825a3fb344b8f0fcecb92646360d patch-4.4-rc1.xz 04a2fe6ce8711a01617e459d6908bfbd7715a0e4106fbd05372e12ba7ad03158 patch-4.4-rc2.xz - DOWNSTREAM: fedoraproject.org - 4.4-RC1: unused original upstream patch-4.4-rc1.xz - checksum match $ curl -s http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-4.4-rc1.xz/a0765e4d169afa64e9cdb6fea35cb728/patch-4.4-rc1.xz | sha256sum 3870efdb5dfdbcb17d5a233e8e9c69156609825a3fb344b8f0fcecb92646360d - - used altered downtream patch-4.4-rc1.xz - checksum mismatch $ curl -s http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-4.4-rc1.xz/67848ae7a0ca2695598d77c9ee576100/patch-4.4-rc1.xz | sha256sum 450b6734366b0f72ec6c34652ff8515d430117bcf714e85c00bff305c95fe873 - $ rpm2cpio https://kojipkgs.fedoraproject.org/packages/kernel/4.4.0/0.rc1.git0.1.fc24/src/kernel-4.4.0-0.rc1.git0.1.fc24.src.rpm | cpio --quiet -i --to-stdout patch-4.4-rc1.xz | sha256sum 450b6734366b0f72ec6c34652ff8515d430117bcf714e85c00bff305c95fe873 - - 4.4-RC2: used altered downtream patch-4.4-rc2.xz - checksum mismatch $ curl -s http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-4.4-rc2.xz/db11195bab1230374cd0ecc8e8ed1420/patch-4.4-rc2.xz | sha256sum 5d258b009fc59957c74f86216eee64741e705851a5f1213d249f9b4c2b6dec5e - $ rpm2cpio https://kojipkgs.fedoraproject.org/packages/kernel/4.4.0/0.rc2.git0.1.fc24/src/kernel-4.4.0-0.rc2.git0.1.fc24.src.rpm | cpio --quiet -i --to-stdout patch-4.4-rc2.xz | sha256sum 5d258b009fc59957c74f86216eee64741e705851a5f1213d249f9b4c2b6dec5e -
Miss Laura Abbott, comment?
This is intentional. We currently have to work around a limitation in patch which is triggered by the deletion of some old binary blobs in the current patch set. Modifying the patch before uploading is the only option.
Created attachment 1112415 [details] ft{1,3}000.img breaks build Have you communicated with the upstream folks apropos this problem?
I looked at what's up with this. Starting with Staging: Add support for Flarion OFDM usb and pcmcia devices https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/staging/ft1000?id=f7c1be0 and ending with staging: ft1000: remove obsolete driver https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/staging/ft1000?id=6512ede So this is no more with the mainline 4.4 However, why the firmwares in the first place are included in the kernel source? Is not this the right place for inclusion, http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git And this, why the application of the upstream patch works manually, but breaks within spec?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days