Merge ~ahasenack/ubuntu/+source/frr:jammy-frr-logging into ubuntu/+source/frr:ubuntu/jammy-devel
Proposed by
Andreas Hasenack
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | git-ubuntu bot | ||||
Approved revision: | not available | ||||
Merged at revision: | b8261bc2e94f74190c136e20965bddad6b46e726 | ||||
Proposed branch: | ~ahasenack/ubuntu/+source/frr:jammy-frr-logging | ||||
Merge into: | ubuntu/+source/frr:ubuntu/jammy-devel | ||||
Diff against target: |
72 lines (+33/-2) 3 files modified
debian/changelog (+8/-0) debian/frr.logrotate (+1/-1) debian/frr.postinst (+24/-1) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
git-ubuntu bot | Approve | ||
Bryce Harrington (community) | Approve | ||
Canonical Server Reporter | Pending | ||
Review via email: mp+427172@code.launchpad.net |
Description of the change
SRU of the kinetic fix[1]
The linked bug[2] has the SRU template filled out and contains a test case.
1. https:/
2. https:/
To post a comment you must log in.
Confirmed this is the same exact changes as landed for kinetic (https:/ /code.launchpad .net/~ahasenack /ubuntu/ +source/ frr/+git/ frr/+merge/ 424952).
I checked if the egrep->grep -E change might be worth including, but I gather the deprecation warning is new and doesn't appear to affect jammy or earlier.
The SRU text looks very thorough and specific. I especially like the thought you give to Where Problems May Occur. Regarding the concern about breaking users who fixed logging in some bespoke fashion, I'd suggest such a type of user would also both have the skills to re/un-fix, and the awareness that their system is non-standard and thus liable to require further attention during upgrade.
Anyway, all looks great, no suggested changes. +1