Merge ~darinmiller/ka:master into ka:master
| Status: | Merged |
|---|---|
| Merged at revision: | 8dd04806023e464efa97301fa5a4f94ef497bb6d |
| Proposed branch: | ~darinmiller/ka:master |
| Merge into: | ka:master |
| Diff against target: |
186 lines (+22/-21) 7 files modified
do-all (+5/-5) get-kci-tarball (+1/-1) ka-update-metadata (+2/-2) kubuntu-create-sru-branches (+1/-1) staging-upload (+9/-9) ubuntu-archive-upload (+2/-2) uploadsource (+2/-1) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jose Manuel Santamaria Lema | 2017-03-07 | Approve on 2017-03-10 | |
|
Review via email:
|
|||
Description of the Change
santa_requested a code cleanup-replacing manually built path strings in the ka python scripts with the os.path.join function.
The following grep commands were performed to find scripts with manual path builds:
- grep "\'/\'" *
- grep "\"/\"" *
The following scripts were modified:
modified: do-all
modified: get-kci-tarball
modified: ka-update-metadata
modified: kubuntu-
modified: staging-upload
modified: ubuntu-
modified: uploadsource
PLEASE double check my edits that I did not extend a path build beyond the parameter in which the path was built. i.e. some functions were passing manually built paths in the function invocation. Since I do not know how or may not have the privilege to run these scripts...
THESE EDITS ARE UNTESTED!
Hi,
since we needed to add a new feature to do-all I have just merged into master the proposed changes, they seem to work fine so far. If anything, we could fix it later.
Thanks for the patch Darin.

Hi Darin,
I have just read the diff and it seems mostly ok, I plan to use KA with these changes for a while to check everything works as expected. Since you mention that you may or may not have permissions to test the changes yourself, let's see one by one.
do-all:
This command iterates over several directories executing the command given, so if you have a set of clones created with git-clone-all you should be able to test a "do-all ls" against that set of clones.
get-kci-tarball: plasma/ apps packaging you should be able to execute this and get an orig tarball in the build-area directory. The tarball is created using KDE's git anonymously, so you shouldn't need any kind of privilege to test it.
This program creates a 'fake' kci tarball when executed from a particular clone, so inside any clone of frameworks/
ka-update-metadata: plasma/ apps backport we don't have right now or something like that. We could arrange this by IRC. This way you will get more familiar with our KA scriptery.
This is something we use to execute when providing a new release (see the README.ng) to test this maybe we could mentor you to do something real, like any frameworks/
uploadsource: plasma/ apps to any of your ppas like this:
This one is just an optional program from KA meant to be a small wrapper around dput/dupload. If I'm not mistaken, you could test it uploading any package from frameworks/
uploadsource -t <your_ppa>
kubuntu- create- sru-branches, staging-upload, ubuntu- archive- upload: all/do- all/gbp- * and friends after the "Slice" operation[1]. I would drop the changes on these, since what I'm planning to do is writing a mail to kubuntu-devel mailing list notifying that I'm going to move them to an "attic/" directory as part of the "Fir Tree" operation[2]. This way it would be easier to
These ones are the old ugly monolithic scripts which we replaced by UNIX-like git-clone-
know if a script is obsolete or not without removing it completely just in case we want to recycle any code in them.
[1]https:/ /phabricator. kde.org/ w/kubuntu/ black-operation s/slice/ /phabricator. kde.org/ w/kubuntu/ black-operation s/fir-tree/
[2]https:/