January 29, 20251 yr 16 minutes ago, ljm42 said: Hi folks, we are using a new method to distribute bug fixes, with the goal of getting the fixes out to you faster. See the new "Patches" section of the release notes for details: https://docs.unraid.net/unraid-os/release-notes/7.0.0/#patches Patch install fails. Quote Installing /boot/config/plugins/unraid.patch/7.0.0/20250128204439-pr271.patch... patching file emhttp/plugins/dynamix.vm.manager/templates/Custom.form.php Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 2 out of 2 hunks ignored -- saving rejects to file emhttp/plugins/dynamix.vm.manager/templates/Custom.form.php.rej patching file emhttp/plugins/dynamix/include/FileTree.php Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file emhttp/plugins/dynamix/include/FileTree.php.rej patching file emhttp/plugins/dynamix/include/ShareList.php Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file emhttp/plugins/dynamix/include/ShareList.php.rej patching file emhttp/plugins/dynamix/scripts/diagnostics Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file emhttp/plugins/dynamix/scripts/diagnostics.rej patching file sbin/mover Hunk #1 FAILED at 72. 1 out of 1 hunk FAILED -- saving rejects to file sbin/mover.rej Failed to install patch 20250128204439-pr271.patch Aborting brunnhilde-diagnostics-20250129-1844.zip
January 29, 20251 yr I split this off to a new thread so we can do some back and forth. Thank you for the diagnostics and the details from the install. The good news is that should not have any adverse effects on your system, the bad news is that you don't have the updates. Would you be open to rebooting? That will get everything back to default. Depending on whether the patches are on your flash drive, they will either automatically be reapplied or you can go to Tools > Unraid Patch to install them. I'd appreciate seeing another diagnostics after that if you don't mind.
January 30, 20251 yr Solution Oh I see, you have the mover tuning plugin. It has already modified the mover script so when this installs it throws an error message about that one file. The rest of the patches installed fine, it is safe to ignore this. Need to see if there is a better way of handling issues from files that were modified by plugins
January 30, 20251 yr Author 14 hours ago, ljm42 said: Need to see if there is a better way of handling issues from files that were modified by plugins Yes, I’m sure I won’t be the only one to see this issue.
January 30, 20251 yr Author Will the patch tool continue to try and fail to install this patch when there are other patches to install?
January 30, 20251 yr same issue 1 out of 1 hunk ignored -- saving rejects to file emhttp/plugins/dynamix/scripts/diagnostics.rej patching file sbin/mover Hunk #1 FAILED at 72. 1 out of 1 hunk FAILED -- saving rejects to file sbin/mover.rej
January 30, 20251 yr 3 minutes ago, updawg said: same issue 1 out of 1 hunk ignored -- saving rejects to file emhttp/plugins/dynamix/scripts/diagnostics.rej patching file sbin/mover Hunk #1 FAILED at 72. 1 out of 1 hunk FAILED -- saving rejects to file sbin/mover.rej That one is expected if you have mover tuning installed, the patch plugin explains that. the thread above is people having trouble installing patches on files that should be valid, but are still failing. What happens is the mover tuning plugin has renamed mover to mover.old and put its own script in place with the name 'mover' so that the scheduler calls the new script. The plugin wont patch it because it knows it's the wrong file, but doesn’t know why (I suspect they will update the patcher to look for mover.old as a failover and patch that). you could uninstall mover tuning, run the patch, then re-install (the correct version) of mover tuning or ignore it if you don’t need to run the old mover manually at all.
January 31, 20251 yr It may be expected, but having the patch not marked as complete, and instead aborted to where it looks like I need to apply it again, I think is bad practice. Edited January 31, 20251 yr by updawg
January 31, 20251 yr Author 24 minutes ago, updawg said: It may be expected, but having the patch not marked as complete, and instead aborted to where it looks like I need to apply it again, I think is bad practice. I think that’s why they are looking into making changes. On 1/29/2025 at 7:12 PM, ljm42 said: Need to see if there is a better way of handling issues from files that were modified by plugins
January 31, 20251 yr 1 hour ago, wgstarks said: I think that’s why they are looking into making changes. I came searching and saw your post so I thought I'd tag on feedback that it confused me as well.
February 1, 20251 yr This screen never updates or goes away. I also have the mover pluggin, so maybe this is why?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.