Project

Profile

Help

Issue #8775

Add support "Source" indices and source level packages (*.orig.tar.gz, *.debian.tar.xz, *.dsc)

Added by markawr 4 months ago. Updated 3 months ago.

Status:
POST
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
05/18/2021
Due date:
06/18/2021
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The Debian Repository Format (https://wiki.debian.org/DebianRepository/Format) allows for "Sources" indices allowing source level packages to exist alongside deb packages. This allows for 'deb-src' lines to be included in a system's sources.list or equivalent files and allows a user to use 'apt-get source <package_name>' to then inspect a package's source, make modifications and use tools such as pbuilder to build a custom version of a package.

The current Pulp Deb plugin does not handle "Source" indices and using generic_content is not really viable.

Having the Pulp Debian plugin support "sources" indices and source level packages would be a welcome addition to the plugin.

(I have reviewed past work items and didn't see previous requests or discussions on this topic, hopefully I didn't miss anything. I am willing to contribute as needed along with some colleagues but want to gauge first if this support would be accepted and desired by folks maintaining this plugin)

History

#1 Updated by quba42 4 months ago

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).

Contributions are of course welcome. If anyone is interested in working on this feel free to contact me for some starting help.

See also: https://github.com/pulp/pulp_deb/blob/a3ee34bbca15af4472ee180fcd05314a72e19272/pulp_deb/app/tasks/synchronizing.py#L510

#2 Updated by markawr 4 months ago

Thanks @quba42. 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.

#3 Updated by quba42 4 months ago

markawr wrote:

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.

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).

[1] https://github.com/pulp/pulp_installer

[2] https://docs.pulpproject.org/pulpcore/contributing/index.html

[3] https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide

[4] https://pulpproject.org/get_involved/

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.

#4 Updated by quba42 4 months ago

  • Sprint/Milestone set to Wishlist

#5 Updated by pulpbot 3 months ago

  • Status changed from NEW to POST

Please register to edit this issue

Also available in: Atom PDF