Project

Profile

Help

Task #2480

closed

Document how to deal with RPM encoding issues.

Added by semyers over 5 years ago. Updated about 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Pulp 2
Sprint:
Quarter:

Description

In #1903, there was some back-and-forth about how to deal with encoding issues. Specifically, the question came down to whether or not Pulp is responsible for enforcing the correct encodings of spec file fields. RPM spec fields should be encoded as UTF-8, but it's not clear what Pulp should do in the case where an RPM doesn't follow that guidance. After a long discussion, our conclusion is that Pulp should not be more restrictive than the most common tool that it's trying to emulate. In the case of distributing RPMs, that tool is createrepo_c.

So, for this task, we need to document the RPM encoding policy, cite sources, and provide examples. As far as where the documentation can live, I think it would be fine somewhere in the RPM plugin's docs, such as the technical reference section: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/index.html

Actions #1

Updated by bmbouter about 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #2

Updated by bmbouter about 3 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #3

Updated by bmbouter about 3 years ago

  • Tags Pulp 2 added
Actions #4

Updated by bmbouter about 2 years ago

  • Category deleted (23)
  • Tags Documentation added

Also available in: Atom PDF