| *** lcastell has joined #starlingx | 00:00 | |
| *** lcastell has quit IRC | 00:04 | |
| *** irclogbot_2 has quit IRC | 02:26 | |
| dtroyer | gitea updated, https://opendev.org/starlingx/integ/ is looking normal again. As a bonus we also now have git blame! https://opendev.org/starlingx/integ/blame/branch/master/tox.ini | 02:28 |
|---|---|---|
| *** irclogbot_3 has joined #starlingx | 02:30 | |
| bwensley | That is awesome - it is great to have blame again. | 11:42 |
| *** ijolliffe has joined #starlingx | 12:35 | |
| *** marosales has joined #starlingx | 13:47 | |
| *** cristoph has joined #starlingx | 14:11 | |
| sgw | Morning all | 14:14 |
| marosales | morning o/ | 14:14 |
| *** boxiang has joined #starlingx | 15:43 | |
| *** lcastell has joined #starlingx | 15:53 | |
| *** boxiang has quit IRC | 16:01 | |
| sgw | dirk: hello, you available at this late hour? I am wondering about the usage of "Subprojects" in the Clode:StarlingX project, for instance for each of the StarlingX "flock" projects/repos, there are about 8 of them, should they be subprojects? | 16:33 |
| dirk | sgw: late? its still early | 16:33 |
| sgw | dirk: hi! I want to structure the project before starting to accept the packages. if you remember there are about 90 packages in the 8 or so flock repos. | 16:34 |
| sgw | dirk: also, I need a hint on where to add the %tis_patch_ver macro setting, I found it in the _buildconfig_<DISTRO> file, but when I tried to edit the file directly it reset | 16:38 |
| dirk | sgw: I would keep it all in one project | 16:39 |
| dirk | I would only create subprojects if there are a) distinct maintainerships (different ownership) or different lifecycle of the packages (e.g. one set of packages is going to be shared accross other things) | 16:40 |
| sgw | Found osc meta prjconf, I think that's the right place | 16:40 |
| dirk | yes, about the other question that is osc meta prjconf | 16:40 |
| dirk | I think it is in the home:dirkmueller:branches:home:saul... project that we elaborated together | 16:40 |
| sgw | right, I found it there, just forgot how to edit it temporarily! | 16:41 |
| dirk | sgw: my understanding is that all of the 90 packages would be maintained "together", so for StarlingX:2.0+1 potentialyl "all" of them will change | 16:41 |
| sgw | vacations will do that ;-)! | 16:41 |
| dirk | osc meta prjconf -e | 16:41 |
| dirk | if you have a cluster of packages that are going to be always shared accross several releases (e.g. all updated together, all changes should propagate to all other streams) then ther eis a good reason for putting them into the parent project or into a subproject that is called "shared" or similar and inherited/linked into the others | 16:42 |
| sgw | dirk: more dumb setup questions, how can I rename a package in my home:saulwold, so I can create a new version if it to send an osc submitreq to the Cloud:StarlingX project? | 16:53 |
| sgw | Do I have to have all the packages populated in the Cloud:StarlingX project first? | 16:54 |
| *** xe1gyq has joined #starlingx | 17:12 | |
| dirk | sgw: renaming is not implemented, you can copy it into a new name using osc copypac, but it will loose the previous commit history | 17:13 |
| dirk | sgw: if its just for submitting, you can submit into a new name as a parameter of osc sr. | 17:13 |
| dirk | like for example "osc $homeproj $oldname $destinatenproj $newname" | 17:14 |
| dirk | sorry, "osc sr ..." | 17:14 |
| dirk | sgw: no, a submitrequest can create a package as well as update an existing one | 17:14 |
| dirk | sgw: submitrequest is actually nothing else than osc copypac with a review/accept/decline workflow attached. the underlying behavior is the same | 17:15 |
| dirk | so if you're not looking for a peer review you can do copypac as well | 17:15 |
| sgw | dirk, great thanks, I am going to play around with some workflow submission | 17:18 |
| dirk | sgw: sure, ping me when there is a point in time when I should take a look. I'm going to be around for some time today | 17:32 |
| sgw | dirk, I think I just approved my own first submission! | 17:36 |
| sgw | marosales: could you try to submit a request for one of your packages? the command will look like this: osc sr home:saulwold fm-common Cloud:StarlingX:2.0 fm-common | 17:38 |
| marosales | sgw sure, let me try that | 17:43 |
| sgw | marosales: I am working on the rest of fault | 17:46 |
| marosales | @sgw I sent a couple of PRs | 18:02 |
| sgw | marosales: thanks, will look at them shortly, working on the rest of fault first | 18:03 |
| sgw | marosales: did you use linkpac to create the second nfv package? If we do that, we can then share the same tarball for the related projects as they are then linked. | 18:51 |
| sgw | dirk: if your still around, why don't I see my own submissions? | 19:23 |
| *** dschoeffm has joined #starlingx | 19:33 | |
| marosales | no, I provided each one with its tarball | 19:37 |
| marosales | sgw: let me check how linkpac works, are you using that for fault in Cloud:StarlingX ? | 19:38 |
| sgw | Yes, that's what I did for fault | 19:39 |
| sgw | also we want to create .xz instaed of gz | 19:39 |
| *** dschoeffm has quit IRC | 19:39 | |
| *** dschoeffm has joined #starlingx | 19:40 | |
| marosales | okay, let me apply the changes and re-send the PRs | 19:40 |
| sgw | marosales: osc linkpac <src project> <src package> <dest project> <dest package> src and dest projects can be the same, then you osc checkout <dest project> <dest package> and osc mv old.spec new.spec. Since you probably alredy have a "dest package" it can be named anything to preserve the old code, then copy the correct specfile into the linked package. Let me know if this makes sense | 19:42 |
| sgw | I can try and give you a script if you want | 19:42 |
| sgw | marosales: Thinking about this furhter, you may want to commit the first nfv project with the tarball and then linkpac from the Cloud:StarlingX:2.0 project as the source | 19:51 |
| marosales | sgw: I used linkpac first (src being nfv and dest being nova-proxy-api), and then removed the tarball from nova-proxy-api, and it looks like this in my personal OBS | 19:53 |
| marosales | https://build.opensuse.org/package/show/home:marcelarosalesj/nova-api-proxy | 19:53 |
| marosales | https://build.opensuse.org/package/show/home:marcelarosalesj/nfv | 19:53 |
| marosales | nova project has the nfv.spec linked too | 19:54 |
| sgw | marosales: I think that works also, you will need to remove the nfv,spec | 19:55 |
| sgw | BTW, are you trying to fix as many warnings as you can, I know we can't fix them all right now without source changes | 19:56 |
| *** ijolliffe has quit IRC | 20:05 | |
| *** ericho has quit IRC | 20:06 | |
| marosales | we're mainly focusing on errors, if possible we send them to upstream projects | 20:14 |
| sgw | Right, there are some "low hanging" warnings also. | 20:26 |
| sgw | and yes sending the fixes upstream is correct! | 20:27 |
| *** ericho has joined #starlingx | 20:28 | |
| *** dschoeffm has quit IRC | 20:29 | |
| marosales | I'll say my team next time we do a packaging session, so we can check those low hanging warning. We're also planning to run spec-cleaner next time | 20:33 |
| marosales | sgw: for the linkpac, do you know how to remove unwanted files from the linked package? I'm not seeing how to remove the nfv.spec from nova-api-proxy | 20:34 |
| sgw | marosales: should be osc rm <fiie name> | 20:35 |
| sgw | and then an osc add any the files, followed by an osc commit | 20:36 |
| sgw | osc status will tell you info | 20:36 |
| marosales | I was only seeing that file in OBS, not in my local package. I just had it removed by adding it to the _link file | 20:37 |
| marosales | I'm not sure we're following the same process though https://build.opensuse.org/package/show/home:marcelarosalesj/nova-api-proxy?expand=0 | 20:37 |
| sgw | have you commit your local version to the the remote with osc commit? | 20:43 |
| marosales | yes, I used osc commit to push the _link file with this <delete name="nfv.spec" /> | 20:44 |
| sgw | I did not edit a link file or anything like that. | 20:48 |
| sgw | Not sure if you have it setup correctly. Maybe provde an update nfv package and I will pull that in, then you can use paclink from that. | 20:49 |
| marosales | interesting, your derived packages have the _link file with the <delete tag, seems it was autogenerated | 20:54 |
| marosales | yes, let me send the nfv and then we see | 20:54 |
| ericho | Hi, i'm getting this error in a duplex virtual when I run ceph osd tree: | 21:02 |
| ericho | unable to get monitor info from DNS SRV with service name: ceph-mon | 21:02 |
| sgw | Hmm, I am not seeing a _link file in my local version or in the repo, where do you see a _link file | 21:02 |
| ericho | and no ceph process are running. | 21:02 |
| ericho | does anyone knows what is the correct command to launch ceph? | 21:03 |
| marosales | sgw: here https://build.opensuse.org/package/view_file/home:saulwold/snmp-ext/_link?expand=0 , on your snmp-ext package you should see a link named "(show unmerged sources)", if you click it you'll see the _link | 21:08 |
| marosales | I just re-sent the NFV package | 21:09 |
| sgw | marosales: hmm, I see it now, I guess I need to merge from the GUI, it did not get carried over to the new packages that I pushed just now. | 21:25 |
| sgw | might be something we need to understand better | 21:25 |
| marosales | yes | 21:32 |
| marosales | brb | 21:34 |
| *** cristoph has quit IRC | 22:04 | |
| *** lcastell has quit IRC | 22:44 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!