Merge lp://staging/~elementary-os/ubuntu/utopic/lsb/upstream-information into lp://staging/ubuntu/utopic/lsb
Status: | Rejected |
---|---|
Rejected by: | Colin Watson |
Proposed branch: | lp://staging/~elementary-os/ubuntu/utopic/lsb/upstream-information |
Merge into: | lp://staging/ubuntu/utopic/lsb |
Diff against target: |
128 lines (+25/-14) 3 files modified
lsb_release (+5/-2) lsb_release.1 (+6/-1) lsb_release.py (+14/-11) |
To merge this branch: | bzr merge lp://staging/~elementary-os/ubuntu/utopic/lsb/upstream-information |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Disapprove | ||
Review via email: mp+231704@code.staging.launchpad.net |
Description of the change
Add "-u, --upstream" key to lsb_release command and "Upstream=
This greatly simplifies release version/codename handling in derived distros for third parties.
This patch originates from JoliCloud (https:/
Depends on https:/
Unmerged revisions
- 91. By Sergey "Shnatsel" Davidoff
-
document -u, --upstream in the manpage
- 90. By Sergey "Shnatsel" Davidoff
-
Applied JoliCloud patch adding '-u, --upstream to' the lsb_release command and 'Upstream=True to Python module' that read /etc/upstream-
release/ lsb-release instead of /etc/lsb-release
To me it sounds like something which should be implemented upstream. Do you think you can file a bug here? https:/ /lsbbugs. linuxfoundation .org/enter_ bug.cgi
Judging from https:/ /lsbbugs. linuxfoundation .org/buglist. cgi?query_ format= specific& order=relevance +desc&bug_ status= __open_ _&product= &content= lsb_release you could file the bug on Product: Specification - Component: Core-generic.