Your message dated Tue, 19 Mar 2024 14:16:33 -0700
with message-id <874jd1ylam.fsf@wireframe>
and subject line Re: Bug#1061298: u-boot: refresh patches
has caused the Debian Bug report #1061298,
regarding u-boot: refresh patches
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1061298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061298
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: u-boot
Severity: minor
Tags: patch
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I've quilt-refreshed patches in u-boot 2024.01+dfsg-1 to apply them without
fuzzyness.
Please find, ahem, a patch for that attached. :) (I'm not sure, if it is a
correct method to propose a fix, though, or you could just run quilt refresh
yourself)
Best,
Andrey
0001-quilt-refresh-patches.patch
Description: application/mbox
--- End Message ---
--- Begin Message ---
On 2024-01-23, Лухнов Андрей Олегович wrote:
> It happened so, that I applied patches one by one and observed following info:
...
> Applying patch debian/patches/rockchip/rockchip-inno-usb.patch
> patching file drivers/phy/rockchip/phy-rockchip-inno-usb2.c
> Hunk #1 succeeded at 64 (offset 2 lines).
> Hunk #2 succeeded at 108 (offset 14 lines).
> Hunk #3 succeeded at 126 (offset 14 lines).
> Hunk #4 succeeded at 142 (offset 14 lines).
> Hunk #5 succeeded at 168 (offset 14 lines).
> Hunk #6 succeeded at 312 (offset 82 lines).
> ```
>
> So, I decided to issue `quilt refresh` for each patch, that has such reports.
>
> I'm not a seasoned Debian maintainer, so sorry for the noise if those actions
> are unneeded. :)
>
> I understand that patches still apply well, but they are already "not
> perfectly in place". So, it appears, the policy is to wait till they are not
> applicable with `--fuzz=0`.
> Understood. Thank you for the clarification!
Yeah, I would rather wait till it is an actual issue! Marking as done.
live well,
vagrant
signature.asc
Description: PGP signature
--- End Message ---
