https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-05-19T15:53:59ZPulpDebian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=709932021-05-19T15:53:59Zquba42
<ul></ul><p>This is very much a valid feature request, but I cannot say if and when we will work on it.
It is not currently on our road map (which could change in the future).</p>
<p>Contributions are of course welcome. If anyone is interested in working on this feel free to contact me for some starting help.</p>
<p>See also: <a href="https://github.com/pulp/pulp_deb/blob/a3ee34bbca15af4472ee180fcd05314a72e19272/pulp_deb/app/tasks/synchronizing.py#L510" class="external">https://github.com/pulp/pulp_deb/blob/a3ee34bbca15af4472ee180fcd05314a72e19272/pulp_deb/app/tasks/synchronizing.py#L510</a></p> Debian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=710312021-05-19T17:45:24Zmarkawr
<ul></ul><p>Thanks <a class="user active" href="https://pulp.plan.io/users/14167">quba42</a>. Definitely no expectation here to get the feature without doing the work. Myself and a possibly a few colleagues will have to learn how to get a development env setup and start to contribute code. Being new to Pulp it would be useful to have a bit of hand holding and patience as we navigate the process of contributing code and having it made available in a future update of the plugin. I will start by ensuring we are subscribed to the right lists etc., if there any other resources for Pulp n00bs please feel free to share.</p> Debian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=713672021-05-26T07:42:30Zquba42
<ul></ul><p>markawr wrote:</p>
<blockquote>
<p>Myself and a possibly a few colleagues will have to learn how to get a development env setup and start to contribute code. Being new to Pulp it would be useful to have a bit of hand holding and patience as we navigate the process of contributing code and having it made available in a future update of the plugin. I will start by ensuring we are subscribed to the right lists etc., if there any other resources for Pulp n00bs please feel free to share.</p>
</blockquote>
<p>I have this idea kicking around my head of writing exactly such a guide (how to enter the project). I have a lot of local notes by myself for myself that I could rework and share in some form. The first thing to set up is indeed a development environment. The pulp_installer repo [1] includes a set of development VMs that can be run locally using vagrant + libvirt. I believe the README file in the repo includes some instructions on setting those up. The pulpcore documentation includes some general points on contributing [2] as well as a plugin writer's guide [3]. There are two mailing lists (pulp-list, and pulp-dev) referenced here [4]. Most in person help can be obtained on the freenode IRC channel, which also maintains a matrix bridge. (Though I believe that is currently in flux due to a hostile corporate takeover of freenode).</p>
<p>[1] <a href="https://github.com/pulp/pulp_installer" class="external">https://github.com/pulp/pulp_installer</a></p>
<p>[2] <a href="https://docs.pulpproject.org/pulpcore/contributing/index.html" class="external">https://docs.pulpproject.org/pulpcore/contributing/index.html</a></p>
<p>[3] <a href="https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide" class="external">https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide</a></p>
<p>[4] <a href="https://pulpproject.org/get_involved/" class="external">https://pulpproject.org/get_involved/</a></p>
<p>You can email me at "quirinp at atix dot de", since this ticket is probably not the best place to continue this exchange. I am sure I can provide an interactive video conference/screen share session at some point as well, perhaps once you hit the first road block in setting up or using the development environment.</p> Debian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=713912021-05-26T14:39:59Zquba42
<ul><li><strong>Sprint/Milestone</strong> set to <i>Wishlist</i></li></ul> Debian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=719362021-06-15T00:26:48Zpulpbot
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>POST</i></li></ul><p>PR: <a href="https://github.com/pulp/pulp_deb/pull/295" class="external">https://github.com/pulp/pulp_deb/pull/295</a></p> Debian Support - Issue #8775: Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)https://pulp.plan.io/issues/8775?journal_id=781892022-01-04T10:58:41Zpulpbot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/78189/diff?detail_id=78875">diff</a>)</li><li><strong>Status</strong> changed from <i>POST</i> to <i>CLOSED - DUPLICATE</i></li></ul>