Thursday, 2016-09-22

openstackgerritThomas Goirand proposed openstack/deb-heat: Merge tag '7.0.0_rc1' into debian/newton  https://review.openstack.org/37458607:48
openstackgerritThomas Goirand proposed openstack/deb-keystone: Merge tag '10.0.0_rc1' into debian/newton  https://review.openstack.org/37458807:51
openstackgerritThomas Goirand proposed openstack/deb-manila: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37459207:54
openstackgerritThomas Goirand proposed openstack/deb-mistral: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37459307:55
openstackgerritThomas Goirand proposed openstack/deb-neutron: Merge tag '9.0.0_rc1' into debian/newton  https://review.openstack.org/37459607:58
tlbrzigo, could you please push master-dfsg branch here https://anonscm.debian.org/cgit/pkg-javascript/libjs-tv4.git/ ?08:02
zigotlbr: Hi.08:02
tlbrhi!08:02
zigotlbr: Can't you push it?!?08:02
zigoI don't get it.08:02
tlbrzigo, it isn't there anymore =\08:02
zigotlbr: I don't have it.08:02
zigotlbr: I only took the debian/unstable branch.08:03
zigotlbr: Thorsten rejected libjs-tv4.08:03
zigoplease mention all licenses/copyright information in your debian/copyright.08:03
zigoFor example libjs-tv4-1.2.7+dfsg1/component.json mentions MIT,08:03
zigolibjs-tv4-1.2.7+dfsg1/try/ace/theme-tomorrow.js and others are under BSD3,08:03
zigolibjs-tv4-1.2.7+dfsg1/try/ace/mode-rdoc.js and others are under AGPL-308:03
tlbrthat is why i'm working on it08:03
zigoOk.08:04
zigotlbr: Let me know.08:04
zigotlbr: FYI, I'm pushing RC1 for all packages.08:04
zigoProbably you saw it already...08:05
tlbryep08:05
zigotlbr: We're stuck with Horizon until libjs-tv4 enters unstable, I guess, right?08:05
tlbrnot sure08:06
zigotlbr: BTW, you shouldn't merge 10.0.0.0rc1, you should retag that as 10.0.0_rc1, push that tag to gerrit, and merge that tag.08:06
tlbryou mean remove tag 10.0.0.0rc1 and replace it with 10.0.0_rc1 ?08:07
zigoYou can't remove tags, we don't have gerrit rights for that.08:07
zigoBut you can do:08:07
tlbri mean remove it locally08:07
zigogit tag -s 10.0.0_rc1 10.0.0.0rc108:07
zigogit push gerrit --tags08:07
tlbrthat is actually what i did08:08
zigoThat's what I've been doing all the way ...08:08
tlbrwithout pushing tags..08:08
zigoWell, here, you've merged the wrong tag, no?08:08
zigohttps://review.openstack.org/#/c/374435/08:08
zigoI don't think it makes a difference though.08:08
zigoSince you're core in the team, you can push (signed only) tags to Gerrit.08:08
tlbrok08:09
openstackgerritThomas Goirand proposed openstack/deb-nova: Merge tag '14.0.0_rc1' into debian/newton  https://review.openstack.org/37460808:15
openstackgerritThomas Goirand proposed openstack/deb-openstack-trove: Merge tag '6.0.0_rc1' into debian/newton  https://review.openstack.org/37460908:18
openstackgerritThomas Goirand proposed openstack/deb-sahara: Merge tag '5.0.0_rc1' into debian/newton  https://review.openstack.org/37461008:22
openstackgerritThomas Goirand proposed openstack/deb-senlin: Merge tag '2.0.0_rc1' into debian/newton  https://review.openstack.org/37461108:25
zigoOk, done for all packages we could.08:29
openstackgerritThomas Goirand proposed openstack/deb-zaqar: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37461508:29
zigoJust Horizon still missing...08:29
zigoI'll make sushis waiting for the CI ! :008:29
zigotlbr: I'm still stuck with python-pandas taking more than 1h30 to build, but hopefully the timeout is now 120 (the patch in project-config was merged) and it will go through.08:32
zigoThen we can build gnocchi.08:32
zigoEvertyhing else is kind of under control! :)08:32
zigotlbr: Are you soon done with libjs-tv4?08:55
tlbrsoon soon08:55
*** yatinkarel has quit IRC08:58
*** ig0r_ has joined #openstack-pkg09:22
tlbrzigo, i've pushed the changes10:43
*** zigo has quit IRC11:54
*** zigo has joined #openstack-pkg11:58
*** zigo is now known as Guest8360111:59
*** Guest83601 has quit IRC12:03
*** zigo_ has joined #openstack-pkg12:12
*** zigo_ has quit IRC12:17
*** zigo_ has joined #openstack-pkg12:18
*** zigo_ has quit IRC12:48
*** zigo_ has joined #openstack-pkg12:51
*** zigo_ is now known as zigo15:14
openstackgerritThomas Goirand proposed openstack/deb-sahara: Merge tag '5.0.0_rc1' into debian/newton  https://review.openstack.org/37461015:21
openstackgerritThomas Goirand proposed openstack/deb-nova: Merge tag '14.0.0_rc1' into debian/newton  https://review.openstack.org/37460815:23
zigotlbr: I wonder if we shouldn't reprocude all of the AGPL in tv4's debian/copyright.15:30
tlbrzigo, not sure, i guess what i did should be enough. May be Thorsten just greped by license word ?15:33
zigotlbr: For sure he has tools to do that, yeah.15:33
zigotlbr: I'm adding the full of the AGPL license in debian/copyright right now.15:33
zigoit wont take long.15:34
tlbrzigo, we should not do that!15:34
tlbrI've checked how other do that15:34
zigotlbr: Why not?15:34
zigotlbr: What others do isn't relevant.15:34
tlbrzigo, please check https://www.gnu.org/licenses/agpl-3.0.en.html15:34
tlbr"How to Apply These Terms to Your New Programs" section15:34
zigoThe only case where we shoulnd't put the whole license is when it's available in /usr/share/common-license.15:35
zigo"You should have received a copy of the GNU Affero General Public License" ...15:35
zigoI never saw a package rejected because it contained TOO MUCH license text.15:35
zigoI did see some rejected, because NOT ENOUGH.15:36
zigoSo better be safe.15:36
zigoIt would have been easier to just remove that folder entirely...15:36
tlbryes, easier but I'm not sure if it is the right thing to do in this case15:37
zigoI'm convinced it is.15:38
tlbrso we should remove it?15:38
zigoRemove what? The folder?15:41
zigoWe that was a possibility yes.15:41
tlbrthe folder, yep15:41
zigoNow, we've gone into another direction, so let's finish this way.15:41
tlbroh, so you agree that we should leave as is15:41
tlbrok15:41
zigoWe have 2 choices: either copy the full of the AGPL in debian/copyright, or get rid of that file ... :P15:42
zigoThe less you package, the less troubles ...15:43
zigoSure, it's nice to have as much as possible.15:43
zigoBut I'm not sure if it was really necessary in this case.15:43
tlbrok :)15:46
zigotlbr: Uploaded.15:47
tlbrzigo, thanks15:47
zigotlbr: Can you validat all the RC1 patches?16:21
tlbrzigo, in all projects ?16:21
zigotlbr: Yup.16:22
tlbrzigo, ok16:23
zigodeb-barbican, deb-ceilometer, deb-designate, deb-glance, deb-heat, deb-keystone, deb-manila, deb-mistral, deb-neutron, deb-nova, deb-openstack-trove, deb-sahara, deb-senlin, deb-zaqar16:23
tlbrok, i'll check it16:24
*** zigo has quit IRC16:41
*** zul has quit IRC16:44
*** zul has joined #openstack-pkg16:45
*** zigo has joined #openstack-pkg16:51
*** zigo is now known as Guest1865616:52
*** Guest18656 has quit IRC16:56
*** zigo_ has joined #openstack-pkg16:59
*** zigo_ has quit IRC17:07
*** zigo_ has joined #openstack-pkg17:11
zigo_tlbr: Thorsten (the FTP master that rejected) confirmed:17:30
zigo_<ta> zigo: yes, everything not in /usr/share/common-licenses must be in debian/copyright17:30
tlbrzigo_, ok, i agree with that. My only concern was whether we should put all the Licence text17:30
zigo_That was a reply about that very question.17:31
zigo_tlbr: Should I self-approve my rc1 merge patches? :)17:32
tlbrzigo_, sec, I'll check it17:36
zigo_Also, any idea how we can add onovy as core?17:37
zigo_I'm skeaming through the doc ...17:37
onovyi think i know how17:37
onovyyou need to send review to one repo17:37
tlbrzigo_, I've added onovy17:38
tlbrzigo_, https://review.openstack.org/#/admin/groups/1136,members17:38
zigo_How did you do that?17:38
zigo_Oh ok.17:38
zigo_Good ! :)17:38
onovyah17:38
tlbr:)17:38
zigo_onovy: Feel free to update Alembic! :)17:38
onovywhat about gerrit/acls/openstack/<projectname>.config17:39
onovyhttps://github.com/openstack-infra/project-config/blob/master/gerrit/acls/openstack/deb-packaging.config17:39
onovygot it. group :)(17:39
onovytlbr: zigo_: thanks17:40
tlbrnp :)17:40
zigo_onovy: Did you read how merge commiit work?17:40
onovyno17:40
onovygit merge + git review?17:40
zigo_onovy: https://wiki.openstack.org/wiki/DEB-packaging#Releasing_a_new_upstream_release_package17:40
onovyso merge commit will edit changelog?17:41
zigo_onovy: The point is, your merge commit must also include the packaging change for the new release.17:41
onovyso only one commit, ok17:41
zigo_Yup.17:41
zigo_Which makes a lot of sense, IMO.17:41
zigo_Since every commit must continue to make the package build.17:41
onovyyep17:42
onovygit tag 0.8.8 rel_0_8_817:42
onovythis is same?17:42
onovyand git push gerrit --tags?17:43
zigo_onovy: Almost!17:43
zigo_onovy: Gerrit will only accept signed tags, so you got to: git tag -s 0.8.8 rel_0_8_817:43
zigo_git push gerrit --tags17:43
zigo_Let me add this to the wiki...17:43
onovycool17:44
onovydislike: changing b-d/d with same commit as "new upstream release"17:46
openstackgerritOndřej Nový proposed openstack/deb-alembic: Merge tag '0.8.8' into debian/newton  https://review.openstack.org/37499717:47
onovyzigo_: anyone review?17:48
onovy:)17:48
zigo_onovy: Not until the package is built successfully ! :)17:48
onovyyou can do +2+A17:48
onovyit will not merge if not built17:48
onovyif you do +2+A now, jenkins will finish first round, will add +1, than +0, final round, +2, merge17:49
onovyif first or second round fails, it will not merge at all17:49
onovyso it's safe to add +2+A for 'looks good changes' and forgot17:49
openstackgerritMerged openstack/deb-manila: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37459217:51
zigo_tlbr: Missing +2s: https://review.openstack.org/374610 https://review.openstack.org/37459317:59
onovyzigo_: we are creating new jessie chroot for every jenkins jobs?18:02
zigo_onovy: For the moment, yes.18:02
onovyhuh, ok18:03
zigo_onovy: We need to add an "sbuild" element to dib to fix that.18:03
openstackgerritMerged openstack/deb-zaqar: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37461518:03
zigo_onovy: I tried, and failed so far.18:03
onovywhat is "dib"?18:03
openstackgerritMerged openstack/deb-barbican: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37439818:03
zigo_onovy: diskimage-builder.18:04
zigo_onovy: https://github.com/openstack-infra/project-config/blob/master/tools/build-image.sh <--- The script from infra to build all of the images daily.18:04
onovybtw: i think we can do merge commit with dch and second commit with b-d/d changes. first commit will not build, but follow up will. so you will send two reviews, both with +2+A18:04
zigo_onovy: The other issue is that infra is maintaining a useless Debian mirror using reprepro. It's useless because not signed ...18:04
zigo_Then sbuild-createchroot cannot use it.18:05
zigo_They need to switch to a real ftp-sync script.18:05
openstackgerritMerged openstack/deb-senlin: Merge tag '2.0.0_rc1' into debian/newton  https://review.openstack.org/37461118:05
zigo_onovy: I think it's best to just keep stuff in a single commit.18:05
onovyor modern varnish18:05
onovyzigo_: i make git commit history a bit noisy18:05
onovyit18:06
onovyi like 'as small commit as possible'18:06
openstackgerritMerged openstack/deb-glance: Merge tag '13.0.0_rc1' into debian/newton  https://review.openstack.org/37440318:06
openstackgerritMerged openstack/deb-ceilometer: Merge tag '7.0.0_rc1' into debian/newton  https://review.openstack.org/37440018:06
openstackgerritMerged openstack/deb-designate: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37440118:06
onovyzigo_: alembic_0.8.8-1+66~bpo8+1_all.deb // that name is correct?18:08
onovy+66 commits?18:08
zigo_onovy: Yes.18:08
zigo_onovy: This includes commits from upstream.18:08
zigo_It will be reseted once you tag the debian release.18:08
onovyah, strange18:08
onovyah, ok18:08
zigo_Not an issue, really.18:08
onovyundo: strange ; got it now18:08
zigo_That's just a counter ...18:08
zigo_Please make sure you only tag debian/1.2.3 when you upload to Debian.18:08
onovymaybe it should be ~6618:09
zigo_Both would work ...18:09
* zigo_ has a dinner break18:09
zigo_ttyl18:09
onovybecause after i tag, i will became 0.8.8-1 which is << 0.8.8-1+6618:09
*** ig0r_ has quit IRC18:09
zigo_onovy: After you tag, you've just uploaded, so the next commit *MUST* include a dch -i18:09
onovyyep18:10
zigo_So that's fine, next version will be higher ... :P18:10
zigo_read the wiki18:10
onovybut package from infra before tag will be higher18:10
onovyhey i understand it :)18:10
onovyjust think about it18:10
zigo_I need to help for the dinner, or my wife will kill me18:10
zigo_ttyl18:10
onovyok :) i will wrote it here, reply later18:10
onovyinfra built 0.8.8-1+66~bpo... package now18:11
onovyafter i tag, it will built 0.8.8-118:11
onovy0.8.8-1 << 0.8.8-1+66~bpo... which is WRONG18:11
onovyit's wrong because 0.8.8-1 is newer package than 0.8.8-1+66~bpo...18:11
openstackgerritMerged openstack/deb-openstack-trove: Merge tag '6.0.0_rc1' into debian/newton  https://review.openstack.org/37460918:12
onovyso if we publish not tagged packages from infra...18:12
onovyso if you are saying. first commit after upload will bump version, it's logical to use ~ not +18:13
onovybecause first commit after upload is saying target version, and every commit after is before target version18:13
openstackgerritMerged openstack/deb-alembic: Merge tag '0.8.8' into debian/newton  https://review.openstack.org/37499718:14
openstackgerritMerged openstack/deb-heat: Merge tag '7.0.0_rc1' into debian/newton  https://review.openstack.org/37458618:18
openstackgerritMerged openstack/deb-nova: Merge tag '14.0.0_rc1' into debian/newton  https://review.openstack.org/37460818:18
openstackgerritMerged openstack/deb-neutron: Merge tag '9.0.0_rc1' into debian/newton  https://review.openstack.org/37459618:22
openstackgerritMerged openstack/deb-mistral: Merge tag '3.0.0_rc1' into debian/newton  https://review.openstack.org/37459318:29
openstackgerritOndřej Nový proposed openstack/deb-alembic: releasing package alembic version 0.8.8-1  https://review.openstack.org/37505818:50
openstackgerritMerged openstack/deb-alembic: releasing package alembic version 0.8.8-1  https://review.openstack.org/37505819:09
zigo_onovy: The thing that you don't get is that, once you've built 0.8.8-1+66~bpo... then you tag it, there can *NEVER* be any 0.8,8-1 build, the next commit should fix the changelog and do a 0.8.8-2.19:28
zigo_So it's in fact a good thing that it's not publishing something we don't want.19:28
onovyhey i really get it19:28
onovybut still thing we should use ~19:29
zigo_It's unfortunately too late to do so.19:29
zigo_If we do, then any build will be broken.19:29
onovyeverything can be changes :]19:29
zigo_Maybe we can do that for Ocata ...19:29
onovy*changed19:29
zigo_Yeah, but not for Newton.19:29
onovyso lets plan it for ocata19:29
zigo_This can be the first thing we do in Ocata.19:29
onovynewton will be released soon19:29
zigo_Yup.19:29
onovybut i have different problem now :)19:30
zigo_And it can live within deb-openstack-pkg-tools in the debian/ocata branch.19:30
onovydeb-swift repo already exists19:30
*** zigo_ is now known as zigo19:30
onovyand i want to sync it with swift from alioth19:30
zigoHow is this a problem?19:30
onovyi need to add debian/mitaka branch + sync debian/newton branch19:30
onovyi can't push19:31
onovyand i can't edit last commit (because it's signed tag)19:31
onovyexactly it's not problem, i only don't know how19:32
zigoYou can't just push.19:32
zigoYou have to do it through a commit.19:32
onovyso create dummy commit with change-id + git review?19:32
zigoJust rm the debian folder, copy what you have in Alioth, and commit that.19:32
onovyi don't want to lose history19:33
zigoNo choice ...19:33
onovyhey19:33
zigoYou'll only loose a little bit of history (ie: the last commits).19:33
zigoOtherwise, you can just commit every patch one by one.19:33
onovyreally don't want this19:33
zigoBut that's very annoying to do ...19:33
onovyhey, that's broke19:33
onovyn19:33
onovylet's found better solution19:34
zigo:P19:34
onovyfor example remove that repo19:34
onovyand import it again19:34
zigoThe other solution would be to ask a gerrit admin to do the push for you.19:34
zigoYou can ask in #openstack-infra.19:34
onovyyou told me: remeber what changes you did and we will sync it later19:34
onovyyou didn't say i will lose commit history for this changes19:34
zigoOh, I understand... you don't have a debian/newton branch on Alioth, do you?19:34
onovyi have19:34
onovyi need to add debian/mitaka (it's not in gerrit now) and sync debian/newton from alioth19:35
zigoHum...19:35
onovythan i can move my work to gerrit19:35
zigoWhy do you need a debian/mitaka branch on Gerrit?19:35
onovybecause i'm still developing debian/mitaka19:35
zigoContinue debian/mitaka on Alioth.19:36
onovyand how can i cherry-pick/merge from two differents repos19:36
zigoThat's the general plan.19:36
onovy(simply)19:36
zigogit format-patch is your friend? :)19:36
onovyno.19:36
onovy(SIMPLY)19:36
onovyif we can't add debian/mitaka branch to gerrit, let's postpone swift migration after newton release19:36
zigoI really think your best bet here is to discuss this in #openstack-infra.19:37
zigoYou can, I don't think that's a problem.19:37
onovyif plan is to not add mitaka branches, let's postpone it. it's simplest solution19:37
zigoThough it's going to be difficult for us to do it.19:37
onovyand than ask os infras to ff it19:37
zigoThat was *MY* plan.19:37
onovyi'm fine with it19:37
zigoYou're free to do differently if you like.19:38
zigoWe can ask guys from #openstack-infra what's best way to re-import the deb-swift repo.19:38
zigoMaybe that's best way indeed, considering what you just wrote.19:38
zigoShould I ask for you?19:38
onovyjobs will not work for debian/mitaka correctly i guess19:38
onovymmnt :) let's talk about it here first19:38
zigoHum...19:38
zigoI didn't think about that.19:38
onovywe have "per branch" repos in infra?19:39
zigoI know it's possible to do no job at all for a specific branch if we need to.19:39
zigoNo.19:39
zigoSingle repo, multiple branch.19:39
onovyhmm19:39
zigoI was planning to ask to open debian/mitaka branches for everything after the release.19:40
onovy?19:40
zigoBut we can have different setup for different branches.19:40
onovyopen mitaka branches after newton release?19:40
zigoIn theory, we can add branch by ourselves.19:40
zigoJust using the gerrit web interface.19:40
zigoSorry...19:40
zigoOcata after newton release.19:40
onovyah19:40
onovyquestion:19:40
onovynewton swift needs newton python-eventlet19:41
onovywe have single repo19:41
zigoRight.19:41
onovyafter we open ocata branch and i upload python-event to ocata branch19:41
onovyi can't change newton swift19:41
onovybecause it will use ocata eventlet19:41
zigoNo.19:41
zigoRepos are per openstack release.19:41
onovy-> per branch :)19:41
zigoYup.19:41
zigoBut we don't have a Mitaka repo in infra.19:41
onovyonovy | we have "per branch" repos in infra? zigo | No.19:42
zigoAh, sorry ! :)19:42
zigorepo = deb repo or repo = git repo19:42
zigoThat's confusing ! :)19:42
zigoWe have a single repo for git...19:42
onovymy fault19:42
zigoMultiple for openstack releases.19:42
onovysingle git repo, git branches, multiple debian repo, one for every git branch19:42
onovyright?19:43
zigoAfter we're done with Newton, there's 2 things that will need to happen: 1/ create 2 a new deb repo for Ocata, importing all Newton packages 2/ make all new debian/ocata branches in Git.19:43
zigoRight.19:43
onovycool19:43
onovyso back to my problem19:43
onovylet's wait for newton release19:43
onovyi will upload newton swift to unstable than19:44
onovyand move to gerrit19:44
onovyand forgot about mitaka branch19:44
zigoWell, considering swift, the release will be in a few days...19:44
onovyyep. that's reason why i will wait19:44
zigoJohn Dickinson wrote that on his channel.19:44
zigoOk, got it.19:44
onovyit's simpler for me19:44
zigoThen you'll stop maintaining Swift for mitaka, right?19:44
onovyyep19:45
zigook19:45
onovyno reason to maintain it19:45
zigoAgree.19:45
onovywhat about jessie-bpo branches?19:45
zigoI was also thinking: what will we do with jessie-backports ...19:45
onovyhey? :)19:45
zigo:)19:45
zigoNewton will be in stretch.19:45
zigoI don't see why we should do any effort maintaining Mitaka.19:45
zigoOr rather: it's too much a burden for me.19:45
onovyyep19:46
zigoBPO FTP masters will hate us though ...19:46
onovythey hate us every 6 mons19:46
onovyso who cares?19:46
zigoRight! :)19:46
onovyjessie-backports should be last stable19:46
onovy->newton after newton release19:46
zigoWhat we could do is continue to maintain for *very serious* security issue until Stretch is out.19:46
onovystable=openstack stable19:46
zigoDo you think we should upload Newton to jessie-bpo ?19:47
onovyyep19:47
zigoThen it's going to be in both Stretch, and jessie-bpo ...19:47
onovyas last openstack version for jessie i think19:47
onovyyep19:47
zigoHow long are we suppose to maintain Newton in jessie-bpo then?19:48
zigoOne year after Stretch is released?19:48
onovyit's simple19:48
onovywe will maintain it for strech19:48
zigoI really don't plan on doing LTS stuff with OpenStack.19:48
onovyso why not upload SAME package to j-bpo19:48
zigoRight.19:48
zigoThat's not much of a work.19:48
onovyso as long as jessie exists19:48
onovywhich is < strech exists19:48
zigoAlso, people upgrading from jessie-bpo to stretch, it's nice, because they only upgrade the underlying OS, and OpenStack stays on the same version.19:48
zigoSo that's a very nice upgrade path.19:49
onovy"same" version19:49
onovy1-1~bpo.. -> 1-119:49
zigoWell, same without ~bpo ... :)19:49
onovybut it will be almost same package19:49
onovy*package content19:49
zigoRight.19:49
zigoSo, it will upgrade, but config for openstack for example wont need to be touched.19:49
onovyyep19:50
zigoOk, good we have a plan, I'm very happy we discussed that ! :)19:50
onovywhich is cool19:50
onovyand we can't upload ocata to j-bpo19:50
onovybecause we can't upload it to strech19:50
onovyso fixed :)19:50
zigoRight.19:50
zigoAlso, .... BIKESHED ?!? :)19:50
zigoHopefully, this will happen one day.19:50
onovy:]19:51
zigoonovy: https://review.openstack.org/374610 <--- +2a please?19:52
zigoonovy: Oh, there's one thing that doesn't work on your "maintain swift in Newton only after the release"19:53
zigoonovy: I need swift to be able to do Tempest stuff ...19:53
onovywhen?19:53
zigoonovy: You mean, when will I start the tempest validation?19:53
onovyyep19:53
zigoonovy: Next week maybe?19:53
onovyand can you downloiad swift from experimental?19:54
zigoNo.19:54
zigoCan't.19:54
zigoIt's Jessie + what's in infra.19:54
onovyhmm, what about python-mock package?19:54
zigoI plan to write this tempest validation suite as a gating job too...19:54
onovy2.0 version is only in experimental and it's maintainted in DPMT19:54
zigoThe issue is that if we download it from experimental (and rebuild it), then it's going to be on 2 repository: jessie-newton and jessie-newton-backports...19:55
zigoI don't want this.19:55
onovythat's not the answer :)19:55
onovythere always be packages like python-mock19:55
zigoonovy: https://github.com/openstack/deb-auto-backports/blob/debian/newton/packages-list#L7519:56
zigoThat's where it comes from.19:56
zigoSo yes, technically, we can do a backport by just adding "swift" in the package list.19:56
onovyadd swift and you are done :)19:56
zigoThough that's really not what we want to do.19:56
zigoBecause once it's in the jessie-newton-backports repo, it can't go away.19:56
onovyi'm sure i can migrate swift to gerrit during next week19:57
onovyif we can ff that repo19:57
zigoonovy: Oh, by the way, have you seen that? https://github.com/openstack/deb-auto-backports/blob/debian/newton/packages-list#L12219:57
onovyonly with debian/newton branch19:57
onovyhuh, strange19:57
zigoI had to hack A LOT, to just download from official jessie-bpo, because webkit2gtk needs more resources than infra VMs can provide.19:57
zigoIt needs more than 8GB of RAM !!!19:57
onovy:)19:58
onovyblame gcc19:58
zigoHere, it crashed when linking ... :P20:02
zigoonovy: Anyway, back to Swift, do you do a lot of cherry-pick from Mitaka ?20:03
onovyyep20:03
onovymy flow is:20:03
onovy1. fix bug in mitaka20:03
onovy2. upload to unstable20:03
onovy3. merge to newton20:03
onovy4. upload to experimental20:03
onovyso exactly i'm merging not cherry-picking it20:03
onovyhttp://metadata.ftp-master.debian.org/changelogs//main/s/swift/swift_2.9.0-2_changelog20:04
onovy  * Rebased on 2.7.0-{7..10}20:04
onovyit's typical for me. i found something in our dev/test in swift mitaka j-bpo20:05
onovyi fix it in mitaka, because i need it for production20:05
onovyand i can't wait to newton release20:05
onovyfor example: swift (2.7.0-10) unstable; urgency=medium20:05
onovythis was bug found just before we wanted to go to production20:06
onovyand it's really strange bug20:06
* onovy have an idea20:09
onovyi can add commits to gerrit repo by merge commit20:09
onovyso if i create merge commit for old+new repo, i can git review it20:09
onovygit merge --no-ff old_repo/HEAD inside new repo20:10
onovyzigo: what do you think?20:10
zigoYou can't do that, it wont work.20:11
onovywhy?20:11
zigoGerrit wont accept it.20:11
zigoGerrit only accept merge commits for branches it already maintains.20:12
onovygerrit is accepting it now for upstream commits20:12
onovyah...20:12
onovydamn20:12
zigoWhich is why every deb-* repo have a track-upstream option.20:12
zigoWhat we could do however, would be a "track-upstream" option that would get stuff from Alioth...20:12
zigoBut then how would we make it build?20:13
onovyi will ask @ infra20:13
zigoI don't think we have a workflow here ...20:13
zigoonovy: The main issue is having a debian/newton branch of Swift so we can test the rest, right?20:14
zigoonovy: Why don't we just push one, and build swift once, just for our tests?20:14
zigoYou can sync from alioth later on ...20:14
zigoDon't you think?20:14
zigoI mean, just something barely useable is enough for us to do tempest things ...20:14
zigoLet's just do that !20:15
onovyi'm lost20:15
onovyi don't want 'barely useable' i want to fix it :)20:15
onovyi asked in @infra20:15
onovyi need to sync alioth swift -> alioth deb-swift20:15
openstackgerritThomas Goirand proposed openstack/deb-swift: Add a .gitreview file  https://review.openstack.org/37508820:16
zigoThat's possible, really ! :)20:16
zigoBut that's not the issue we're having.20:16
zigoLet's first see if swift builds! :P20:16
zigoOh, btw, to be able to build for jessie-bpo, we'll have the issue that we need to add extend-diff-ignore = ".gitreview" in debian/source/options of all packages.20:17
zigoNot a very big deal though ...20:18
onovyalembic builds fine without it20:18
zigoThat's because I did a hack in deb-openstack-pkg-tools20:19
zigoonovy: https://github.com/openstack/deb-openstack-pkg-tools/blob/debian/newton/build-tools/pkgos-infra-install-sbuild#L24620:20
zigo:P20:20
onovyso it's fixed20:21
onovynot needed to add it to exetend-diff-ignore, right?20:21
zigoonovy: Official jessie-bpo doesn't have the fix.20:21
onovyi'm lost again20:21
zigoonovy: So, to upload stuff prepared in infra to jessie-bpo, we'll have to add the extended-diff-ignore.20:21
onovybefore migration to os infra, this problem doesn't exists20:21
zigoThe issue is in libdpkg-perl ...20:22
zigoonovy: Ok, let me explain ...20:22
onovyi can build any package for jessie-bpo locally20:22
onovyyep, thanks :)20:22
zigoonovy: In every deb-* gerrit repo, we need a .gitreview to point at the correct place, you agree with that, right?20:22
onovyyep20:22
zigoonovy: Now, for deb-nova, this clashes with the .gitreview file of upstream nova gerrit repo: we have a diff with the upstream .gitreview file.20:23
openstackgerritMerged openstack/deb-sahara: Merge tag '5.0.0_rc1' into debian/newton  https://review.openstack.org/37461020:23
onovyah, got it20:23
zigoonovy: In Sid/Stretch, that's not a problem, because libdpkg-perl automatically ignores it.20:23
zigoIn Jessie, libdpkg-perl is older ...20:23
zigoonovy: So, I've patched it in deb-opentsack-pkg-tools so that we don't need to bother.20:23
zigoonovy: Though for an upload in official jessie-bpo, we'll have to manually add the extended-diff-ignore stuff in debian/source/options20:24
zigoThat's easy to automate though...20:24
zigoonovy: FYI, I opened a bug against dpkg to fix that, and the dpkg maintainer refused saying that this is a behavior change that he doesn't want to introduce in stable.20:25
zigoI can agree with this view, even if that's very annoying for us.20:25
onovybtw: i didn't change .gitreview in alembic repo20:25
onovywhich is wrong20:25
zigoonovy: I did that before, which is why ...20:26
onovydid that for all repos?20:26
zigoonovy: Editing the .gitreview was the commit I used to trigger builds, so yes.20:26
zigoI have hundreds of "Add a .gitreview file" types of commits ! :)20:26
onovyhttps://github.com/openstack/deb-swift/commits/debian/newton20:27
onovy404 not found ;)20:27
onovyzigo: from infra: don't merge anything to deb-swift20:30
onovyand they can ff it manually20:30
onovyso don't a20:32
onovy+A20:32
zigoonovy: https://github.com/openstack/deb-swift/commits/debian/newton <--- This isn't leading me to a 404 ...20:39
onovyyep, it's not HTTP 40420:40
onovyit was joke. i can't found commit for .gitreview20:40
zigoonovy: Well, I haven't done it for swift (yet).20:40
onovyso don't do it now20:40
onovyi will wait for infra20:41
zigoonovy: Why?20:41
onovybecause i need ff-only20:41
onovyyou can commit it into alioth20:41
zigoonovy: Why is it so important that you have the full commit history?20:41
onovybut not into gerrit20:41
onovyit's important for me20:41
onovyi like to use git blame20:41
zigoonovy: Well, I want to have a build in infra !!!20:41
onovyif you +A any commit, it's not possible to merge it with my changes20:42
zigoThere's no other way, unfortunately.20:42
onovyit's20:42
onovywait.20:42
onovyfew hours/days20:42
zigoRight.20:42
onovyinfra will ff it20:42
zigoUntil Swift for Newton is ready, right?20:42
zigoOh ok.20:42
zigoI thought they wouldn't ! :)20:42
onovyno, earlier20:42
zigoGot it.20:42
onovyearlier... maybe. swift will be released tomorrow20:42
onovyand i want to release it throu gerrit20:43
zigo:)20:44
onovyi ff-ed deb-swift in alioth20:44
onovyhttps://anonscm.debian.org/cgit/openstack/deb-swift.git20:44
onovyso i only need to ff gerrit now20:44
onovythan we can continue20:44
zigoonovy: BTW, now that we have all of the RC1 built and available on infra, we need to build them and upload to experimental ...20:47
zigoonovy: Do you have time for it? :)20:47
onovydon't build it20:47
onovyonly upload it20:47
zigoonovy: You mean source-only uploads?20:47
zigo:P20:48
zigoI really think that's dangerous.20:48
zigoAnd that we should build to make sure all unit tests passing in Sid too.20:48
onovyit's not20:48
onovy(dangerous)20:48
onovyif used correctly, it's perfect20:48
onovyi'm using almost only source-only20:48
zigoWell, the source-only upload, right.20:48
zigoBut we should still check that unit tests are passing.20:48
onovyyep, there could be inconsitency between infra and deb20:49
zigoHopefully, we'll have a (non voting?) check job with a Sid sbuild chroot in infra ...20:49
onovyhopefully we will have gate for debian upload?20:49
zigoLOL ! :)20:50
onovythink out of the box20:50
zigoI'm not sure the FTP masters will like the idea ...20:50
onovyof course you can't give anyone PGP keys20:50
onovyand ftp masters will not like this idea20:50
zigoI've been thinking about that, yes...20:50
onovybut we can found solution somewhere in middle20:50
zigoThis will only be possible once we have reprocuded OpenStack infra within a DSA machine.20:50
onovyinfra will prepare it, you will sign it, and upload it20:51
onovybut with source-only is this all useless20:51
onovywe should gate TAGS for sid schroot20:51
onovyif jenkins ack, i can upload it source-only20:51
zigo!= jenkins20:51
openstackzigo: Error: "=" is not a valid command.20:51
zigoJenkins is *GONE* ! :)20:51
zigo!help20:52
openstackzigo: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin.20:52
onovyjenkins = openstack infra20:52
openstackgerritMerged openstack/deb-auto-backports: Build pandas needed by gnocchi  https://review.openstack.org/37302120:52
onovyfrom now :)20:52
zigoYEAH !!!20:52
zigoPANDAS GOT IN !!! :P20:52
zigoLet's wait another 2 hours until the package is built ...20:52
zigoonovy: I had to increase the deb-auto-backports timeout from 1h30 to 2h to make it happen ... :)20:52
onovy:]20:53
zigoSo, another 2 hours of POST commit job, and it will be in the jessie-newton-backports repo.20:53
zigoThen, I can build Gnocchi ...20:53
onovy2 hours for python code...20:53
zigoThat's mostly C code.20:54
zigo(in a Python module)20:54
zigoLot's of unit tests, you know ...20:54
zigoThe Sphinx doc takes also forever to build.20:54
zigoGosh ... :(20:56
zigohttp://logs.openstack.org/36/36b8f73bc5d5b4546d45ff971cb9f620ffffbdea/post/pkgdeb-publish-auto-backports/57bd4f4/console.html20:56
zigo:/20:56
zigoSo, from now on: forbidden to attempt any other backport until pandas is in.20:56
openstackgerritThomas Goirand proposed openstack/deb-auto-backports: Dumb commit to re-attempt pandas build  https://review.openstack.org/37510820:57
onovymaybe you could be more robust in build script20:57
onovyand try apt-get more than onetime20:57
onovywhy you didn't just write "recheck"20:58
zigoonovy: The same issue could happen when doing the sbuild-createchroot20:58
zigoOr any apt-get during the build...20:58
onovyi know, it's not ideal20:58
zigoonovy: The thing that broke is the POST job, not the check or the gate.20:58
onovyah20:58
zigoonovy: What's broken is that we're still using zuul 2.5, and not 3... :(20:58
zigoWith zuul 3, we wouldn't need to build 3 times.20:59
zigoonovy: BTW, you can install python-git-os-job (from sid...), it's quite useful.21:00
onovyhmm21:00
zigo# cat /usr/bin/goj21:00
zigo#!/bin/sh21:00
zigogit-os-job $@ $(git log | head -n 1 | awk '{print $2}')21:00
zigo:P21:00
onovyehm21:01
onovygit os-job HEAD?21:01
onovyi want to look to last commit, right?21:01
zigoNo, because I want it to do it in my current branch.21:01
zigoOh, that works too ...21:02
onovygit osb-job debian/newton21:02
* zigo hides with shame ...21:02
onovybut i think HEAD works too21:02
zigoIt does.21:02
onovybecause HEAD is per-branch21:02
zigoonovy: BTW, will you be in Barcelona?21:03
onovyyep, you already asked me21:03
onovyme+3 coworkers21:03
zigoI thought I did, indeed, but forgot.21:03
zigoNice.21:03
onovybarcelona is cheap for us21:04
onovybtw: do you know mirantis bought tcp cloud from cz?21:04
onovyyou are colleage with fpytloun :)21:04
onovygn21:08
zigoonovy: Of course I know ...21:14
zigoonovy: I knew about it a way before the general announcement ! :)21:14
*** zul has quit IRC21:36
*** strigazi has quit IRC21:37
*** onovy has quit IRC21:37
*** IgorYozhikov has quit IRC21:37
*** themill has quit IRC21:37
*** beisner has quit IRC21:37
*** adreznec has quit IRC21:37
*** IgorYozhikov has joined #openstack-pkg21:38
*** themill has joined #openstack-pkg21:38
*** beisner has joined #openstack-pkg21:40
*** adreznec has joined #openstack-pkg21:40
*** zul has joined #openstack-pkg21:40
*** strigazi has joined #openstack-pkg21:40
*** onovy has joined #openstack-pkg21:41
openstackgerritMerged openstack/deb-keystone: Merge tag '10.0.0_rc1' into debian/newton  https://review.openstack.org/37458822:15
openstackgerritThomas Goirand proposed openstack/deb-python-ironic-lib: Add a .gitreview file  https://review.openstack.org/37514322:31
openstackgerritThomas Goirand proposed openstack/deb-heat: Add python-aodhclient (>= 0.5.0) b-d  https://review.openstack.org/37514922:39
openstackgerritThomas Goirand proposed openstack/deb-heat: Add python-aodhclient (>= 0.5.0) b-d  https://review.openstack.org/37514922:40

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!