I ran out of time looking into Smash. I may be able to try working on those in the week of June 26-30.
If you can point me to some tools for recording the demo, I might be able to work on one for the July 6, during the same week. It may also be helpful if someone else is willing to do the demo - it's not hugely entertaining to watch one upload a .deb file, publish the repo etc. On Tue, Jun 13, 2017 at 9:09 AM, Brian Bouterse <bbout...@redhat.com> wrote: > This is great! Thanks @misa. It looks like pulp_deb is ready to be > included in 2.14! > > As an aside, I talked w/ @ichimonji10 yesterday who can help guide a pulp > smash contribution. If we had pulp_smash tests for pulp_deb, they would run > nightly against core to ensure compatibility and correctness of the > pulp_deb workflow/codepaths. > > As a second aside, is there any way we could have a community demo of this > prior to the launch of 2.14. The two demo dates prior to the GA of 2.14 are > June 15th and July 6th. We can take either pre-recorded standalone videos > or a live demo. > > Thanks again, > Brian > > On Mon, Jun 12, 2017 at 9:29 PM, Mihai Ibanescu <mihai.ibane...@gmail.com> > wrote: > >> Testing on a pulp server with >> pulp-server-2.14.0-0.1.alpha.git.18878.518e345.fc24.noarch >> (and its friends): >> >> pulp-admin deb repo create --repo-id test-1-deb >> pulp-admin deb repo uploads deb --repo-id test-1-deb -f >> nscd_2.24-7ubuntu2_amd64.deb >> pulp-admin deb repo publish run --repo-id test-1-deb >> >> Confirmed a debian repo got created. >> >> URL=https://my-server.example.com/pulp/deb/test-1-deb/ >> pulp-admin deb repo create --repo-id test-2-deb --feed $URL >> --verify-feed-ssl false --relative-url top/test-2-deb >> pulp-admin deb repo sync run --repo-id test-2-deb >> >> Conformed a repo got created. >> >> pulp-admin deb repo delete --repo-id test-1-deb >> pulp-admin deb repo delete --repo-id test-2-deb >> >> >> I call that a success! :-) >> >> >> On Mon, Jun 12, 2017 at 1:08 PM, Brian Bouterse <bbout...@redhat.com> >> wrote: >> >>> Great. For now, we're just doing scratch builds to ensure things can be >>> built without issue. Whatever version is merged when the 2.14 beta goes to >>> be made[0] (tentatively July 5) is what will ship with 2.14 unless you tell >>> us otherwise. >>> >>> Thanks Mihai! >>> >>> [0]: https://pulp.plan.io/projects/pulp/wiki/2140_Release_Status >>> >>> On Mon, Jun 12, 2017 at 12:37 PM, Mihai Ibanescu < >>> mihai.ibane...@gmail.com> wrote: >>> >>>> As of now, 1.5.1 is what I am expecting. >>>> >>>> However, there are some very good contributions as PRs in the pipe, and >>>> if I were to merge them they would probably result in 1.6. >>>> >>>> Mihai >>>> >>>> On Mon, Jun 12, 2017 at 11:01 AM, Brian Bouterse <bbout...@redhat.com> >>>> wrote: >>>> >>>>> Mihai, I'm interested to hear how the testing goes between pulp_deb >>>>> and the master branch of core (what will become 2.14). Also I want to >>>>> check >>>>> in on the version number. Do you expect pulp_deb to be released as version >>>>> 1.5.1? That is what is currently in the spec file. >>>>> >>>>> Thanks for all the testing and contribution! >>>>> Brian >>>>> >>>>> >>>>> >>>>> On Mon, Jun 12, 2017 at 10:04 AM, Ina Panova <ipan...@redhat.com> >>>>> wrote: >>>>> >>>>>> Mihai, >>>>>> >>>>>> both of the Tasks are added to the sprint, so they will be worked on >>>>>> asap. >>>>>> >>>>>> >>>>>> >>>>>> -------- >>>>>> Regards, >>>>>> >>>>>> Ina Panova >>>>>> Software Engineer| Pulp| Red Hat Inc. >>>>>> >>>>>> "Do not go where the path may lead, >>>>>> go instead where there is no path and leave a trail." >>>>>> >>>>>> On Thu, Jun 8, 2017 at 3:53 PM, Mihai Ibanescu < >>>>>> mihai.ibane...@gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> We have had discussions on the IRC channel about adding pulp-deb >>>>>>> (debian support for pulp) in 2.14. >>>>>>> >>>>>>> I have filed this: >>>>>>> >>>>>>> https://pulp.plan.io/issues/2802 >>>>>>> >>>>>>> The unit tests pass against the master branch. I am in the process >>>>>>> of installing a server from master to validate that things do indeed >>>>>>> work >>>>>>> as expected. >>>>>>> >>>>>>> I believe we need consensus that we should do it, and figure out >>>>>>> what needs to be done and who will do that. At the very least, >>>>>>> python-debpkgr would need to be packaged as an rpm and included in the >>>>>>> yum >>>>>>> repo (subtask https://pulp.plan.io/issues/2803) >>>>>>> >>>>>>> Thank you! >>>>>>> Mihai >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pulp-dev mailing list >>>>>>> Pulp-dev@redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pulp-dev mailing list >>>>>> Pulp-dev@redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>>>> >>>>>> >>>>> >>>> >>> >> >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev