Merge ~bryce/ubuntu/+source/mako:fix-lp1990446-kinetic into ubuntu/+source/mako:ubuntu/kinetic-devel
Proposed by
Bryce Harrington
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | e2dc97ad61463c963281089750c71305cc9a6d56 | ||||
Proposed branch: | ~bryce/ubuntu/+source/mako:fix-lp1990446-kinetic | ||||
Merge into: | ubuntu/+source/mako:ubuntu/kinetic-devel | ||||
Diff against target: |
52 lines (+32/-0) 3 files modified
debian/changelog (+7/-0) debian/patches/fix_exceptions_test.patch (+24/-0) debian/patches/series (+1/-0) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Christian Ehrhardt (community) | Approve | ||
Canonical Server Reporter | Pending | ||
git-ubuntu import | Pending | ||
Review via email: mp+430261@code.staging.launchpad.net |
Description of the change
Fix for a FTBFS in the kinetic rebuild.
PPA: https:/
To post a comment you must log in.
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
Thanks Bryce,
test builds look fine, you went the extra effort to find Debian bug, isolate the fix from the patch and all that.
+1 to get this resolved in kinetic
And by knowing the Debian sync will fix it there also is no follow up needed.
If you want to have a nit-pick then it is that (since you changed or actually reduced the patch) I think we usually would use
Origin: backport, ...
instead of
Origin: upstream, ...
And in the patch description you could say something like "isolated the test fixes from an upstream commit to just solve the current FTBFS in Ubuntu. The next sync from Debian will resolve it in 23.10."
But that is not really important here, it is up to you if you want to amend that before an upload.