[Pulp-dev] Including the pulp-deb plugin in pulp 2.14

Brian Bouterse bbouters at redhat.com
Mon Jun 12 17:08:10 UTC 2017


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.ibanescu at 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 <bbouters at 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 <ipanova at 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.ibanescu at 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 at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170612/7e98ad51/attachment.htm>


More information about the Pulp-dev mailing list