| *** pradk has quit IRC | 00:03 | |
| *** paragan has quit IRC | 01:14 | |
| *** paragan has joined #openstack-rpm-packaging | 03:00 | |
| *** chandankumar has joined #openstack-rpm-packaging | 07:22 | |
| *** pcaruana has joined #openstack-rpm-packaging | 08:05 | |
| *** jpena has joined #openstack-rpm-packaging | 08:27 | |
| *** mpavone has joined #openstack-rpm-packaging | 08:39 | |
| openstackgerrit | Igor Yozhikov proposed openstack/rpm-packaging: Add initial spec file for oslo.config https://review.openstack.org/270493 | 09:00 |
|---|---|---|
| openstackgerrit | Igor Yozhikov proposed openstack/rpm-packaging: Add initial spec file for oslo.context https://review.openstack.org/270795 | 09:09 |
| *** paragan has quit IRC | 09:32 | |
| kun_huang | btw how to automatically install dependencies from zypper, just like yum-builddep | 09:36 |
| *** apevec has joined #openstack-rpm-packaging | 09:50 | |
| *** apevec has joined #openstack-rpm-packaging | 09:50 | |
| IgorYozhikov | kun_huang: I do not know actually how to do it right. can suggest this: while read pkg; do zypper install $pkg; done < <(rpmspec --query --buildrequires ../oslo.config.spec | cut -d' ' -f1) | 09:51 |
| IgorYozhikov | dirk, toabctl i have a question about this build - https://build.opensuse.org/package/live_build_log/home:suse-cloud-ci:rpm-packaging-openstack-0300dfbee8c6d2af59054794a0cc68d566431776/python-oslo.config/openSUSE_Tumbleweed/x86_64 | 09:52 |
| *** apevec has left #openstack-rpm-packaging | 09:53 | |
| IgorYozhikov | Am I right that debtcollector doesn't has wrapt as dependecy(Ruquires) - ImportError: No module named wrapt | 09:54 |
| IgorYozhikov | dependency absence leads to CI failures :( | 09:55 |
| IgorYozhikov | https://review.openstack.org/#/c/270493/ | 09:56 |
| *** derekh has joined #openstack-rpm-packaging | 09:56 | |
| kun_huang | IgorYozhikov: thanks trying | 09:56 |
| IgorYozhikov | to fix CI suggesting 2 ways: 1) fix runtime dependencies in debtcollector package or 2) add %bcond_with test. | 10:00 |
| *** openstackgerrit has quit IRC | 10:02 | |
| *** openstackgerrit has joined #openstack-rpm-packaging | 10:03 | |
| toabctl | IgorYozhikov: looks like oslo.config doesn't have a BuildRequires for debtcollector or wrapt | 10:10 |
| toabctl | IgorYozhikov: debtcollector has a Requires for wrapt | 10:10 |
| openstackgerrit | Igor Yozhikov proposed openstack/rpm-packaging: Add initial spec file for oslo.config https://review.openstack.org/270493 | 10:17 |
| IgorYozhikov | toabctl: moved debtcollector upper to the main BuildRequires | 10:18 |
| *** paragan has joined #openstack-rpm-packaging | 10:43 | |
| *** ihrachys has joined #openstack-rpm-packaging | 11:08 | |
| IgorYozhikov | toabctl: please take a look into SUSE CI results for https://review.openstack.org/#/c/270795/, to be frank - foe me they looks weird :/ | 11:12 |
| *** ihrachys has quit IRC | 11:16 | |
| *** ihrachys has joined #openstack-rpm-packaging | 11:16 | |
| *** mpavone_ has joined #openstack-rpm-packaging | 11:32 | |
| *** ihrachys has quit IRC | 11:32 | |
| *** mpavone has quit IRC | 11:36 | |
| openstackgerrit | Dirk Mueller proposed openstack/rpm-packaging: Update oslosphinx to 4.3.0 https://review.openstack.org/281792 | 12:00 |
| toabctl | IgorYozhikov: looks like it's a build timeout. the build finished sucessful afaics | 12:19 |
| IgorYozhikov | toabctl: next movements? | 12:20 |
| IgorYozhikov | recheck doesn't work | 12:21 |
| IgorYozhikov | or merge with red CI? | 12:21 |
| toabctl | IgorYozhikov: why does recheck not work? | 12:22 |
| IgorYozhikov | may be it takes long time - that is why i think so | 12:22 |
| IgorYozhikov | so, just add post recheck, right? | 12:22 |
| dirk | IgorYozhikov: there is something wrong with the build service right now, it takes forever | 12:45 |
| dirk | I"m about to raise the timeout | 12:45 |
| IgorYozhikov | i c | 12:48 |
| *** chandankumar has quit IRC | 13:16 | |
| *** chandankumar has joined #openstack-rpm-packaging | 13:23 | |
| *** jpena is now known as jpena|lunch | 13:44 | |
| dirk | hi everyone | 14:02 |
| dirk | number80: toabctl IgorYozhikov ping | 14:02 |
| dirk | mivanov: ping | 14:03 |
| toabctl | pong | 14:03 |
| mivanov | pong | 14:03 |
| IgorYozhikov | here | 14:03 |
| IgorYozhikov | o/ | 14:03 |
| number80 | pong | 14:03 |
| dirk | #startmeeting RPM Packaging Weekly Meeting | 14:04 |
| openstack | Meeting started Thu Feb 18 14:04:10 2016 UTC and is due to finish in 60 minutes. The chair is dirk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:04 |
| dirk | hey number80 | 14:04 |
| openstack | The meeting name has been set to 'rpm_packaging_weekly_meeting' | 14:04 |
| dirk | do we have agenda items for today? | 14:04 |
| IgorYozhikov | dirk: I think yes | 14:04 |
| IgorYozhikov | according to etherpad | 14:04 |
| number80 | important ones I see | 14:05 |
| dirk | anything missing? | 14:06 |
| number80 | IgorYozhikov just added the epoch topic so I'm good with the agenda | 14:07 |
| number80 | ah maybe it was you | 14:07 |
| dirk | #topic toabctl: versions of proposed specs. looks like we are submitting older versions. What's our goal? Gettting packages for Mitaka? | 14:08 |
| dirk | toabctl? | 14:08 |
| dirk | I think the confusion is because we originally said we'd aim for finishing openstackclient with liberty release | 14:09 |
| IgorYozhikov | dirk: I added previous versions because they could be tested against already built packages | 14:09 |
| dirk | which didn't happen | 14:09 |
| toabctl | ah. yes. I recognized that a lot of the proposed specs are using outdated versions. | 14:09 |
| IgorYozhikov | 4 now I'm ok with Mitaka versions | 14:09 |
| toabctl | and I created an overview for mitaka | 14:09 |
| toabctl | #link http://toabctl.de/openstack/rpm-packaging-status.html | 14:09 |
| dirk | any concerns objections from anyone to go with mitaka specs ? | 14:09 |
| IgorYozhikov | & I've to update all my commits with corresponding to Mitaka SW versions | 14:09 |
| toabctl | this shows our current versions and the versions fromhttps://github.com/openstack/releases/tree/master/deliverables/mitaka | 14:10 |
| toabctl | IgorYozhikov: I justed wanted to discuss what we want for this cycle. and having something for mitaka would be cool imo :) | 14:10 |
| dirk | ok, sounds like agreement, number80 ? | 14:11 |
| IgorYozhikov | toabctl: agree | 14:11 |
| number80 | amen to Mitaka but it will be painful | 14:11 |
| toabctl | number80: why? | 14:11 |
| toabctl | number80: to early? | 14:11 |
| IgorYozhikov | number80: pain due not stable code, reqs and spec | 14:11 |
| IgorYozhikov | right? | 14:11 |
| number80 | considering delorean stats, we have packaging changes every week | 14:11 |
| number80 | IgorYozhikov: yes | 14:11 |
| number80 | but I agree that Mitaka should be our goal (so my formal +1) | 14:12 |
| IgorYozhikov | o/ +1 | 14:12 |
| dirk | #agreed packaging spec files should aim mitaka release deliverable versions | 14:12 |
| dirk | #topic created status page: http://toabctl.de/openstack/rpm-packaging-status.html | 14:13 |
| toabctl | ah. well. I mentioned that already :) | 14:13 |
| dirk | I think we mostly covered that already.. any questions about it? | 14:13 |
| dirk | first of all of course thanks to toabctl for generating it :) | 14:13 |
| toabctl | if wanted, I can propose the code to rpm-packaging-tools. | 14:13 |
| toabctl | it will be updated every 2 hours. | 14:13 |
| number80 | yes, that's very useful | 14:14 |
| number80 | that and IgorYozhikov spreadsheet will help to coordinate | 14:14 |
| IgorYozhikov | I need to update my spreadsheet with current status :) | 14:15 |
| dirk | toabctl: sounds like a good idea (proposing to packaging tools) | 14:15 |
| toabctl | if I find time, I'll add a extra column with "currently in review" | 14:15 |
| toabctl | ok. I'll do that | 14:15 |
| IgorYozhikov | remind the link https://docs.google.com/spreadsheets/d/1d5j0UxkkAm2lfGtfbvcC3zszkLTqxv-PJ7US6AHxL-s/edit#gid=0 | 14:15 |
| dirk | I was having the crazy idea to publish it as docs from the rpm-packaging repo but thats for some other time.. | 14:15 |
| toabctl | #action toabctl proposes rpm-packaging-status.py to rpm-packaging-tools repo | 14:16 |
| number80 | https://docs.google.com/spreadsheets/d/1d5j0UxkkAm2lfGtfbvcC3zszkLTqxv-PJ7US6AHxL-s/edit#gid=0 | 14:16 |
| number80 | (just add the link in meetbot logs) | 14:16 |
| toabctl | here are the meetbot commands: https://wiki.debian.org/MeetBot | 14:16 |
| dirk | #link https://docs.google.com/spreadsheets/d/1d5j0UxkkAm2lfGtfbvcC3zszkLTqxv-PJ7US6AHxL-s/edit#gid=0 | 14:17 |
| dirk | #topic move agenda/minutes links to wiki? | 14:17 |
| dirk | imho yes for minutes | 14:17 |
| toabctl | so currently we are using the etherpad but other projects use the wiki. and with the wiki we have history and nobody can just delete content without haveing a "backup" | 14:18 |
| IgorYozhikov | just to use the same approach as the rest of OS projects - agree | 14:18 |
| toabctl | so I like the etherpad because it's simple to add things but having history is imo important | 14:18 |
| number80 | yyes | 14:19 |
| IgorYozhikov | toabctl: + visibility for community members who are use to use OS wiki | 14:19 |
| toabctl | so what about using https://wiki.openstack.org/wiki/Rpm-packaging/Meetings ? | 14:19 |
| toabctl | IgorYozhikov: yes | 14:20 |
| dirk | toabctl: can do.. I"ll take a look how other projects do this | 14:20 |
| toabctl | dirk: so you don't want to use it for the agenda? just for minutes? | 14:20 |
| dirk | well I definitely agree that wiki makes sense to clean up our slightly messy etherpad | 14:21 |
| dirk | so I'd use it to put the links on the meeting logs and action items | 14:22 |
| dirk | regarding agenda collection - which often happens ad hoc, I'd find the etherpad simpler | 14:22 |
| dirk | but I don't have a strong opinion either way | 14:22 |
| toabctl | ok. also fine for me. | 14:22 |
| dirk | I agree that we've been slacking a bit on this and moving to wiki has advantages | 14:22 |
| toabctl | let's start with using it for general info (meeting time, ...) and colection minutes and AIs | 14:23 |
| toabctl | s/collection/collecting/ | 14:23 |
| dirk | sounds good to me | 14:24 |
| IgorYozhikov | AIs -> tracking progress | issues | 14:24 |
| IgorYozhikov | good | 14:24 |
| dirk | any concerns, objections? | 14:24 |
| dirk | #agreed AI and meeting logs move to wiki page https://wiki.openstack.org/wiki/Rpm-packaging/Meetings | 14:25 |
| *** apevec has joined #openstack-rpm-packaging | 14:26 | |
| dirk | #topic move meeting to official meeting place: https://review.openstack.org/#/c/279950/ | 14:26 |
| dirk | first of all, adding it to the meeting ical is a good idea, thanks | 14:26 |
| dirk | the slight downside is that the meeting rooms are booked at our usual meeting time | 14:27 |
| dirk | so we'd have to move to a different week day or different time | 14:27 |
| toabctl | and you can't add our room as meeting room | 14:27 |
| dirk | different time would be one hour earlier on thursdays | 14:27 |
| dirk | different day would also be possible, e.g. fridays same time works for me , or an hour later | 14:27 |
| dirk | so I guess there are two things to this | 14:27 |
| dirk | a) moving to one of the official meeting rooms for the meeting | 14:28 |
| dirk | and b) if we do so, adjust to the different scheduling | 14:28 |
| dirk | what do you think? | 14:28 |
| toabctl | so the current proposal would be Thursday, 1 pm UTC | 14:28 |
| toabctl | in #openstack-meeting-alt | 14:28 |
| number80 | not a big change | 14:28 |
| number80 | +1 | 14:28 |
| IgorYozhikov | most of projects using os meeteng | meeting-alt | 14:28 |
| toabctl | +1 | 14:29 |
| number80 | visibility is important | 14:29 |
| IgorYozhikov | yep +1 | 14:29 |
| toabctl | so I proposed the change already: https://review.openstack.org/#/c/279950/3 (with workflow -1 to first discuss it here) | 14:29 |
| dirk | number80: IgorYozhikov :, ok then please +1 the review | 14:29 |
| toabctl | and I'll remove the workflow-1 | 14:29 |
| dirk | #agreed meeting will move an hour earlier and to openstack-meeting-alt | 14:29 |
| IgorYozhikov | a lot of dev folks attends meetings at os meeting | meeting-alt | 14:29 |
| IgorYozhikov | dirk: done | 14:30 |
| dirk | moving an hour earlier might even makethe meeting attendable for kun_huang I guess | 14:30 |
| dirk | thanks | 14:31 |
| dirk | #topic handling of Epoch versions | 14:31 |
| dirk | and now the fun topic :) | 14:31 |
| number80 | tough one | 14:31 |
| toabctl | :) | 14:31 |
| number80 | I think we need to have some kind of database to store such things | 14:31 |
| number80 | handling that in spec will be hell | 14:32 |
| IgorYozhikov | yes, I want to be clear here too | 14:32 |
| dirk | I am wondering if we ever manage to agree to one epoch version accross all distros | 14:32 |
| number80 | dirk: considering fedora experience, impossible | 14:32 |
| dirk | if we can, then it would be rather simple - we add a filter that removes the epochs for suse and all others stay on a common epoch | 14:32 |
| IgorYozhikov | dirk: it might be ok in case of installation from scratch | 14:32 |
| IgorYozhikov | without update from previous version | 14:33 |
| toabctl | number80: with database, you mean a db per distro? | 14:33 |
| IgorYozhikov | if we are speaking only about OS related packages | 14:33 |
| dirk | yeah, well suse's distro upgrade allows version downgrades :) | 14:33 |
| apevec | this is about https://review.openstack.org/281196 ? | 14:33 |
| toabctl | hi apevec | 14:33 |
| apevec | dirk, so suse always has Epoch: 0 ? | 14:34 |
| dirk | apevec: sort of, yes, sorry for not summarizing | 14:34 |
| dirk | we discussed that over the last few days already | 14:34 |
| apevec | what do you do in case of upstream changing versioning | 14:34 |
| dirk | let me summarize a bit | 14:34 |
| apevec | yes please | 14:34 |
| dirk | suse currently has the (imho slightly stupid) policy of not allowing epochs in distro packages | 14:34 |
| dirk | which means epoch: fields will be stripped during checkin process from the spec file. so with other words it is always epoch 0 | 14:35 |
| dirk | a switch of the code stream (distro upgrade) allows version downgrades, so it is not a major issue for us | 14:35 |
| dirk | within a maintained products no epochs and no version downgrades are allowed | 14:35 |
| dirk | so in case when upstream breaks versioning, we either delay the upgrade to the next release (where downgrade is allowed) or we invent a fake version number (very rarely) | 14:36 |
| dirk | in the openstack case, the version change to semver was not an issue since it came aligned with a product switch | 14:36 |
| dirk | so we just accept the downgrade and don't worrry about it | 14:36 |
| dirk | and going forward in theory this will not ever happen anymore (famous last words..) | 14:37 |
| dirk | it seems both rhel and mirantis have introduced epochs to handle upgrades due to the semver change | 14:37 |
| IgorYozhikov | dirk: yes | 14:37 |
| dirk | number80: so we'd need a distro specific yaml that renderspec has to read and add to the spec file ? | 14:38 |
| dirk | and we annotate version numbers with a filter that introduces the epochs? | 14:38 |
| IgorYozhikov | you are right here - epoch used to handle upgrade-ability | 14:38 |
| dirk | because there are two aspecits. the epoch: field in the .spec file and the epoch specifiers in dependencies | 14:38 |
| dirk | e.g. requires: foo >= epoch:version-release | 14:38 |
| toabctl | dirk: having a per-distro yaml with key-values (package name -> epoch) could be enough I guess. and then using that in renderspec | 14:39 |
| dirk | we'd have to do something like | 14:39 |
| number80 | dirk: yes | 14:39 |
| IgorYozhikov | ic - so we need to handle this in renderspec | 14:39 |
| dirk | well, unless we agree to not use epochs | 14:39 |
| dirk | :-) | 14:39 |
| IgorYozhikov | by cutting off epoch from reqs versions | 14:39 |
| toabctl | well - we need the key/value store per disto and that needs to be in rpm-packaging imo. this will change with new releases | 14:40 |
| dirk | its not only cutting off, but also adding the epochs to the deps | 14:40 |
| number80 | dirk: I wouldn't be against it but reality wants us to have them around :( | 14:40 |
| IgorYozhikov | dirk: 4 example - Requires: {{ 'oslo.config' | py2pkg }} >= 2:3.4.0 | 14:41 |
| IgorYozhikov | for SUSE - Requires: {{ 'oslo.config' | py2pkg }} >= 0:3.4.0 | 14:41 |
| dirk | right | 14:41 |
| IgorYozhikov | nope? | 14:41 |
| dirk | yes | 14:41 |
| toabctl | would be more like Requires: {{ 'oslo.config' | py2pkg }} >= {{ 3.4.0|epoch }} | 14:42 |
| IgorYozhikov | so, suggesting to add filter for that | 14:42 |
| dirk | but when I understood number80 correctly it is not "2" everywhere but the "2" depends on the distro | 14:42 |
| dirk | toabctl: doesn't work | 14:42 |
| toabctl | and epoch looks what distro you want to render and scans the file with the packagename->epoch mapping | 14:42 |
| toabctl | dirk: why? | 14:42 |
| dirk | toabctl: epoch filter needs to know the package name | 14:42 |
| toabctl | dirk: ah. right | 14:42 |
| IgorYozhikov | {{ 'oslo.config' | py2pkg }} >= {{ 2 | epoch }}:3.4.0 | 14:42 |
| dirk | so you'd have to do something like {{ 3.4.0|epoch('oslo.config') }} | 14:43 |
| toabctl | then maybe another filter with 2 params, pkgname and version. | 14:43 |
| IgorYozhikov | with current implementation might work | 14:43 |
| dirk | which makes it fsckingly ugly | 14:43 |
| apevec | yeah that's too ugly | 14:43 |
| dirk | IgorYozhikov: well, are you saying we can agree on a common epch? | 14:43 |
| number80 | or having a smarter filter | 14:43 |
| toabctl | number80: yes | 14:44 |
| IgorYozhikov | smart filter requires DB | 14:44 |
| number80 | IgorYozhikov: exactly | 14:44 |
| IgorYozhikov | agree on smart filter | 14:44 |
| dirk | yaml is the openstack db ;-) | 14:44 |
| number80 | yaml is fine with me :) | 14:44 |
| IgorYozhikov | +1 | 14:44 |
| *** pradk has joined #openstack-rpm-packaging | 14:44 | |
| dirk | number80: but is it really going to be package specific? | 14:45 |
| dirk | number80: or can we do something like | 14:45 |
| IgorYozhikov | we need to elaborate data format | 14:45 |
| dirk | {{ "3.4.0" | epoch("oslo_version_break_2015.1") }} | 14:45 |
| number80 | dirk: it could be global | 14:45 |
| dirk | and then oslo_version_break_2015.1 is mapped to epoch 2 for rhel, and 3 for mirantis (as an example) | 14:46 |
| number80 | jruzicka has experience in such databases, so I'd have him helping us | 14:46 |
| dirk | so the lookup key is not the package name, but some identifier that we agree on.. | 14:46 |
| dirk | we could also make it then | 14:46 |
| number80 | *nods* | 14:47 |
| dirk | {{ "oslo2015:3.4.0" | epochfilter }} | 14:47 |
| dirk | and then oslo2015: would be replaced by 2: for one distro and "" for suse | 14:47 |
| toabctl | hm. that looks ugly | 14:47 |
| dirk | is | 14:49 |
| IgorYozhikov | may be use current OS release - like oslo:mitaka:3.4.0 | 14:49 |
| IgorYozhikov | may be use current OS release - like oslo.config:mitaka:3.4.0 | 14:49 |
| dirk | {{ "oslo:3.4.0" | evr }} better ? | 14:49 |
| IgorYozhikov | oslo - to common name, how filter will know what exactly should be processed | 14:50 |
| toabctl | what about {{ oslo.messagging|myfilter('3.4.0') }} | 14:50 |
| dirk | well, the idea is that you'd use a common epoch version for all "oslo" packages | 14:50 |
| toabctl | and then the filter handles the epoch and pypkg naming conversion foo | 14:50 |
| IgorYozhikov | even when it is not necessary? | 14:50 |
| *** jpena|lunch is now known as jpena | 14:50 | |
| dirk | IgorYozhikov: yes | 14:51 |
| IgorYozhikov | not sure that add epoch to whole oslo namespace is a good idea...I need to think more on this | 14:51 |
| toabctl | dirk: what's the advantage? not having a "big" db file? | 14:52 |
| dirk | toabctl: it looks a bit redundant to me, since we'll have oslo.messaging mentioned before already | 14:52 |
| toabctl | dirk: my idea is to give the filter just another argument (the version) | 14:52 |
| dirk | toabctl: I understand, but the complete line will look lik ethis in your example | 14:53 |
| IgorYozhikov | can we connect two filters? 1 with name - second with epoch | 14:53 |
| dirk | Requires: {{ "oslo.messaging" | py2pkg }} >= {{ "oslo.messagging" |myfilter('3.4.0') }} | 14:53 |
| number80 | I think we need a PoC first so we could discuss on a better basis | 14:53 |
| toabctl | dirk: more like : BuildRequires: {{ 'oslotest' | py2pkg('1.10.0', '>=') }} | 14:54 |
| toabctl | number80: +1 | 14:54 |
| IgorYozhikov | toabctl: this one could work | 14:54 |
| IgorYozhikov | number80: +1 | 14:54 |
| IgorYozhikov | PoC | 14:54 |
| dirk | who takes the action item? | 14:55 |
| toabctl | I'm interessted but not sure if I can do that before next week | 14:55 |
| toabctl | with next week I mean before our next meeting :) | 14:55 |
| dirk | I think we have a week, we have plenty of specfiles to review/merge before epochs become a major obstacle | 14:55 |
| toabctl | yeah | 14:55 |
| IgorYozhikov | toabctl: who is knows python may be | 14:56 |
| number80 | *nods* | 14:56 |
| dirk | toabctl: ok, slightly less ugly than what I understood, thanks for the explanation | 14:56 |
| dirk | ideally I'd have something like BuildRequires: {{ buildrequires[i] }} and that just expands automatically to the right thing (maybe from a separate yaml file) | 14:57 |
| dirk | anyway, we agree to postpone | 14:57 |
| dirk | #agreed decision postponed until a better PoC is available that covers all aspects | 14:57 |
| dirk | #action toabctl come up with prototype | 14:57 |
| dirk | ok, that wasn't so painful, thanks a lot for the engagement! | 14:58 |
| dirk | I'm fairly happy with the progress on the reviews lately, keep rocking! | 14:58 |
| toabctl | +1 | 14:58 |
| IgorYozhikov | dirk: let's do some CR 4 now? | 14:58 |
| dirk | any last words? otherwise one hour earlier next week in openstack-meeting-alt! | 14:58 |
| dirk | IgorYozhikov: I have to jump on something else at the top of the hour I"m sorry. but I'll check out the current state later today | 14:59 |
| number80 | btw, I won't be around next week due to personal matters | 14:59 |
| dirk | IgorYozhikov: I sent another PR this morning that should unblock others | 14:59 |
| IgorYozhikov | https://review.openstack.org/#/c/281792/? | 14:59 |
| dirk | IgorYozhikov: feel free to ping me on irc on anzthing that needs my review/merge | 14:59 |
| IgorYozhikov | dirk: sure | 14:59 |
| IgorYozhikov | https://review.openstack.org/#/c/270795/ - this one you mentioned earlier | 15:00 |
| dirk | IgorYozhikov: ah, good point. did we agree to list versions on buildrequires? we didn"t do that so far Iirc | 15:00 |
| IgorYozhikov | dirk: yes, lower caps usage | 15:01 |
| dirk | IgorYozhikov: fixed the review | 15:03 |
| IgorYozhikov | dirk, toabctl - will recheck-suse helps with CI became green? | 15:03 |
| toabctl | IgorYozhikov: it should at least retrigger a build. but we currently have only one worker so that's maybe a bit slow... | 15:04 |
| dirk | IgorYozhikov: yes. | 15:04 |
| dirk | IgorYozhikov: its just that the build times are a bit slow right now.. will look into that (needs assistance from a colleague) | 15:04 |
| IgorYozhikov | ok, going to retrigger oslo.context | 15:04 |
| dirk | currently the SUSE CI thing is not really voting yet (probably something we should change at some point) | 15:05 |
| dirk | anyway | 15:05 |
| dirk | #endmeeting | 15:05 |
| openstack | Meeting ended Thu Feb 18 15:05:14 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:05 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/rpm_packaging_weekly_meeting/2016/rpm_packaging_weekly_meeting.2016-02-18-14.04.html | 15:05 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/rpm_packaging_weekly_meeting/2016/rpm_packaging_weekly_meeting.2016-02-18-14.04.txt | 15:05 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/rpm_packaging_weekly_meeting/2016/rpm_packaging_weekly_meeting.2016-02-18-14.04.log.html | 15:05 |
| IgorYozhikov | c u later, thanx | 15:05 |
| *** apevec has left #openstack-rpm-packaging | 15:34 | |
| *** chandankumar has quit IRC | 15:36 | |
| openstackgerrit | Thomas Bechtold proposed openstack/renderspec: Add basic test infrastructure https://review.openstack.org/281925 | 16:04 |
| *** chandankumar has joined #openstack-rpm-packaging | 16:09 | |
| *** pcaruana has quit IRC | 16:15 | |
| *** paragan has quit IRC | 16:18 | |
| *** paragan has joined #openstack-rpm-packaging | 16:20 | |
| *** paragan has joined #openstack-rpm-packaging | 16:20 | |
| *** chandankumar has quit IRC | 16:38 | |
| toabctl | IgorYozhikov: dirk , number80 https://review.openstack.org/#/c/281925/ | 16:50 |
| IgorYozhikov | toabctl: will take a look soon | 17:10 |
| *** mivanov has quit IRC | 17:13 | |
| *** chandankumar has joined #openstack-rpm-packaging | 17:22 | |
| *** derekh has quit IRC | 18:16 | |
| *** chandankumar has quit IRC | 18:24 | |
| *** jpena has quit IRC | 18:34 | |
| *** mpavone_ has quit IRC | 19:04 | |
| *** ChanServ sets mode: +o dirk | 19:18 | |
| *** dirk changes topic to "https://etherpad.openstack.org/p/openstack-rpm-packaging - Next Meeting February 25th 1:00 PM UTC" | 19:19 | |
| *** paragan_ has joined #openstack-rpm-packaging | 20:10 | |
| *** paragan_ has joined #openstack-rpm-packaging | 20:10 | |
| *** paragan has quit IRC | 20:12 | |
| *** tlbr_ has quit IRC | 20:12 | |
| *** tlbr has joined #openstack-rpm-packaging | 20:12 | |
| *** paragan__ has joined #openstack-rpm-packaging | 21:15 | |
| *** paragan_ has quit IRC | 21:16 | |
| *** rbowen has quit IRC | 23:22 | |
| *** openstackgerrit has quit IRC | 23:47 | |
| *** openstackgerrit_ is now known as openstackgerrit | 23:47 | |
| *** openstackgerrit_ has joined #openstack-rpm-packaging | 23:47 | |
| *** openstackgerrit_ is now known as openstackgerrit | 23:48 | |
| *** openstackgerrit_ has joined #openstack-rpm-packaging | 23:49 | |
| *** openstackgerrit_ has quit IRC | 23:55 | |
| *** openstackgerrit_ has joined #openstack-rpm-packaging | 23:56 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!