- What are the changes to Add-support-for-forcing-modules-installation.patch? That patch already existed, and the debdiff here completely changes it. A lot of it just seems to be reformatting, but the diff-of-diff makes it really hard to see what changed and whether that was intended.
- This also changes the already existing apport_python3.patch. There's also an awful amount of noise, but one effective change:
+- for directory in "$dkms_tree/$1/$2/"${3:-+([0-9]).*}/${4:-*}; do
++ for directory in "$dkms_tree/$1/$2/"${3:-[0-9].*}/${4:-*}; do
which is adjusting the py3 port for the new 0003-Add_BUILD_DEPENDS_configuration_option.patch. Thus the new patches in this debdiff need to be applied *before* at least apport_python3.patch, otherwise the patch dependencies are the wrong way around.
Have these been submitted upstream anywhere, as they are rather intrusive? Thanks!
Asked on IRC, but didn't get a response:
- What are the changes to Add-support- for-forcing- modules- installation. patch? That patch already existed, and the debdiff here completely changes it. A lot of it just seems to be reformatting, but the diff-of-diff makes it really hard to see what changed and whether that was intended.
- This also changes the already existing apport_ python3. patch. There's also an awful amount of noise, but one effective change:
+- for directory in "$dkms_ tree/$1/ $2/"${3: -+([0-9] ).*}/${ 4:-*}; do tree/$1/ $2/"${3: -[0-9]. *}/${4: -*}; do
++ for directory in "$dkms_
which is adjusting the py3 port for the new 0003-Add_ BUILD_DEPENDS_ configuration_ option. patch. Thus the new patches in this debdiff need to be applied *before* at least apport_ python3. patch, otherwise the patch dependencies are the wrong way around.
Have these been submitted upstream anywhere, as they are rather intrusive? Thanks!