Bug 28546 - rss for https://advisories.mageia.org is too big
Summary: rss for https://advisories.mageia.org is too big
Status: NEW
Alias: None
Product: Websites
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-07 00:02 CET by katnatek
Modified: 2021-03-07 20:03 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description katnatek 2021-03-07 00:02:30 CET
Description of problem:

In blogdrake.net we use to include the rss for security advisories, only recently i noticed that have a year without updating, i try to update from site admin tools but it give me

"The feed from Mageia Security seems to be broken, because of error "No memory" on line 343244."

The sysadmin of blogdrake did investigation about this with this result

The file fetched from https://advisories.mageia.org/advisories.rss, have more of 16 MB and contain more than 300k lines.

Version-Release number of selected component (if applicable):


How reproducible:

I don't know if this could be reproducible
Comment 1 katnatek 2021-03-07 00:05:20 CET
Forgot to comment that by the moment solve the issue by parsing the rss
Comment 2 Manuel Hiebel 2021-03-07 12:10:59 CET
see https://bugs.mageia.org/show_bug.cgi?id=28495

as a quick workaroud you can use specifig RSS release page like:
https://advisories.mageia.org/8.rss
https://advisories.mageia.org/7.rss

Assignee: atelier-bugs => sysadmin-bugs

Comment 3 katnatek 2021-03-07 20:03:49 CET
(In reply to Manuel Hiebel from comment #2)
> see https://bugs.mageia.org/show_bug.cgi?id=28495
> 
> as a quick workaroud you can use specifig RSS release page like:
> https://advisories.mageia.org/8.rss
> https://advisories.mageia.org/7.rss

Interesting to know, by the moment we keep the custom parsing at less until mga 7 reach EOL

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28495


Note You need to log in before you can comment on or make changes to this bug.