#50741 closed update (fixed)
openssh 7.2p1 release
Reported by: | danielluke (Daniel J. Luke) | Owned by: | Ionic (Mihai Moldovan) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ||
Port: | openssh |
Description
This ticket is to track updating the openssh port to 7.2p1 (released today). With just changing the version and checksums, the build fails with the launchd.patch not applying. I'm sure the other patches will need updating as well.
Change History (7)
comment:1 Changed 9 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 9 years ago by danielluke (Daniel J. Luke)
looks like freebsd has an updated hpn patch.
comment:3 Changed 9 years ago by Ionic (Mihai Moldovan)
Owner: | changed from macports-tickets@… to ionic@… |
---|---|
Status: | new → assigned |
Type: | defect → update |
Assigning myself.
comment:4 Changed 9 years ago by Ionic (Mihai Moldovan)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Updated in r146143.
comment:5 Changed 9 years ago by danielluke (Daniel J. Luke)
What are you using to rebase those patches (you seem to be able to do it pretty quickly), so I'm sure you're doing something better than I would and I'd like to learn :)
comment:6 Changed 9 years ago by Ionic (Mihai Moldovan)
It isn't quick at all. The whole procedure took me about 10 hours straight.
The only "trick" to speed it up is using quilt
for patch management, so that pushing, popping and updating/refreshing patches takes less time.
Other than that, it's sadly mostly looking at diffs of Fedora, Debian and FreeBSD patches (if available) and compiling to see if it works. Ideally, each hunk would need to be looked at manually to make sure the context still fits, as sometimes patch applies hunk with fuzziness to different places than originally intended. Fortunately, at least for the launchd patch, that also lead to a compile failure, but I fear the day it compiles fine with code at a wrong location.
comment:7 Changed 9 years ago by danielluke (Daniel J. Luke)
Ok, that's how I was going to try to do it - you're just more willing to dedicate 10 hours to it than I seem to be. The amount of effort required to update our patches is the main reason keeping me from being willing to take maintainership of this port.
has duplicate #50750