Summary: | GLEP 42 News-Item-Format 2.0 needs to be implemented | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ulrich Müller <ulm> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | floppym |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=581096 https://bugs.gentoo.org/show_bug.cgi?id=658272 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 290038, 604854 |
Description
Ulrich Müller
2016-03-14 11:23:56 UTC
> - Content-Type: Don't require this header in format 2.*
If I read GLEP 42, in format 2.0 this is not only no longer required, but even no longer allowed.
(In reply to Chí-Thanh Christopher Nguyễn from comment #1) > > - Content-Type: Don't require this header in format 2.* > > If I read GLEP 42, in format 2.0 this is not only no longer required, but > even no longer allowed. Yes and no, since Portage must ignore any unrecognised header (like Content-Type in format 2.0): "[...] tools handling these news items must ignore any unrecognised header." https://wiki.gentoo.org/wiki/GLEP:42#News_Item_Files It's kind of a moot point; the portage code never checked Content-Type in the first place. In the master branch: https://gitweb.gentoo.org/proj/portage.git/commit/?id=0cb7426796b2fb082f9176b7b08d08b21b5c86bb https://gitweb.gentoo.org/proj/portage.git/commit/?id=67fcbccd1b60b599e4e5dcc97f2959164ba6a7eb https://gitweb.gentoo.org/proj/portage.git/commit/?id=216297a9a7e91e48b74ef796b6642fd8c15085fc Fixed in portage-2.3.3. |