Debian Patches
Status for swugenerator/0.5-5
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-fix-correct-PKCS-11-mechanism-usage-in-signing-comma.patch | fix: correct PKCS#11 mechanism usage in signing command Fix an issue where the pkcs11-tool was invoked with an empty mechanism due to a space after `-m ` flag. This caused signing to fail with the error "Unknown PKCS11 mechanism". So, remove space after `-m` to fix PKCS#11 mechanism error as below. ['-m ', 'SHA256-RSA-PKCS'] ['-m', 'SHA256-RSA-PKCS'] The mechanism should now correctly set to `SHA256-RSA-PKCS`. |
Pratik Manvar <pratik.manvar@ifm.com> | not-needed | upstream | 2025-07-30 | |
| 0002-fix-add-missing-decrypted-size-entry.patch | fix: add missing `decrypted-size` entry The decrypted-size field is required when flashing encrypted images to the MTD partition on NOR flash. This attribute is also required to handle the UBI Volumes. Due to a limit in the Linux kernel API for UBI volumes, the size reserved to be written on disk should be declared before actually writing anything. |
Pratik Manvar <pratik.manvar@ifm.com> | not-needed | upstream | 2025-07-30 | |
| 0003-Extend-PKCS-11-support-to-handle-optional-slot-and-i.patch | Extend PKCS#11 support to handle optional slot and id parameters The PKCS11 signing option uses `pkcs11-tool` for archive signing. This tool supports additional argunments such as `--slot` and `--id` along with `--module` and `--pin`. This commit enhance the PKCS#11 signing to support up to five parameters: - PIN argument remains mandatory. - Add the slot and id as optional parameters along with module. The new format for the signing option is: `PKCS11,<pin>[,<module>,<slot>,<id>]` |
Pratik Manvar <pratik.manvar@ifm.com> | not-needed | upstream | 2025-07-30 | |
| 0004-generator-Set-decompressed-size.patch | generator: Set decompressed-size Compressed images require this property to be set. |
Ernestas Kulik <ernestas.k@iconn-networks.com> | not-needed | upstream | 2025-08-06 | |
| 0005-Revert-Handle-multiple-configuration-files.patch | Revert "Handle multiple configuration files" This reverts commit af6f21260b85c0c3c5c779d04d0ca5c6bc169c42. After discussion on ML, this feature can be done in other way by using the include directive of libconfig. A config file could be created in this way: variables : { @include "file1" @include "file2" ..... } The commit breaks how the paramters are passed making them dependent of the order in which the command line args are specified. |
Stefano Babic <stefano.babic@swupdate.org> | not-needed | upstream | 2025-09-18 | |
| 0006-Add-a-sign-subcommand-to-sign-an-existing-swu-file.patch | [PATCH] Add a sign subcommand to sign an existing swu file With this feature the signing of the swu file can be done in a second call after the generation, because signing could require a different environment. Refactor SWUFile supporting read and write Change SWUFile close to add_trailer as it is not closing but writing |
INgo Rah <ingo.rah@linutronix.de> | not-needed | upstream | 2025-10-07 | |
| 0007-swu_file-Renumber-cpio-inodes-to-support-64-bit-file.patch | [PATCH] swu_file: Renumber cpio inodes to support 64 bit file systems The cpio newc header format reserves an 8 byte hex string for inodes, where "ffffffff" is the max value. Until now, we took the inode from the original file system, checked if within 32 bit range and exited with error if not. This is safe, but doesn't support file systems like XFS that use 64 bit inodes. 64 bit inodes obviously can't be represented in a newc header directly. However, we can get some ideas to handle the situation from GNU cpio. Their strategy is - default: silently truncate inodes to 32 bit, - with -W truncate: truncate and print warning message, - with --renumber-inodes: create artificial inode numbers to use up the full 32 bit space. The approach picked here is similar to "--renumber-indoes", but simplified. As long as swupdate doesn't preserve hardlinks, there's no need to maintain per-hardlink sets. Counting up is enough. been enough to fix the issue. Though, the counter makes the 32 bit limitation obvious to future developers that may wish to add hard link support. |
Tobias Deiminger <tobias.deiminger@linutronix.de> | yes | 2025-11-13 |
All known versions for source package 'swugenerator'
- 0.5-5 (forky, sid)
- 0.5-2~bpo13+1 (trixie-backports)
- 0.4-1 (trixie)
- 0.3-1~bpo12+1 (bookworm-backports)
- 0.2-1 (bookworm)
