#2250 assigned task

FTP Clean Up, Current and Past Releases RPM Archive

Reported by: Chris Johns Owned by: Needs Funding
Priority: normal Milestone: Indefinite
Component: unspecified Version: 4.10
Severity: major Keywords: ftp rpm cleanup
Cc: Blocked By:
Blocking:

Description

The FTP site contains a lot of broken files and junk and this needs to be cleaned up. The recent users list post about building using rpms shows we need to clean out broken files and move things for archive purposes to a suitable location.

This ticket also covers the issue of where to put the previous release RPM archive. These RPMs are valid and need to be archived. I am not sure we need to maintain yum repo level access any more and this needs to be discussed.

Change History (7)

comment:1 Changed on Feb 6, 2015 at 12:43:21 AM by Amar Takhar

We should probably create an ftp.archive.rtems.org for these files. Moving to /pub/archive doesn't work very well as it breaks URLS. Using a different hostname+IP allows someone to add a hosts entry or just change the hostname without worrying about the path.

If we don't care about users updating the path then /pub/archive/ makes the most sense.

comment:2 in reply to:  1 ; Changed on Feb 6, 2015 at 12:58:37 AM by Chris Johns

Replying to amar:

We should probably create an ftp.archive.rtems.org for these files. Moving to /pub/archive doesn't work very well as it breaks URLS. Using a different hostname+IP allows someone to add a hosts entry or just change the hostname without worrying about the path.

Good idea. How would this happen, say I wanted to move something ? Coping it off and back seems stilly.

comment:3 in reply to:  2 Changed on Feb 6, 2015 at 1:39:36 AM by Amar Takhar

Replying to chrisj:

Good idea. How would this happen, say I wanted to move something ? Coping it off and back seems stilly.

It would be on the same storage array so mv will work just fine. We need to create a wiki page that explains how to archive data. The archive will be perminiant meaning we're stuck with whatever we throw on there. Having some rules will be important. For example:

  • /pub/release/* -> /pub/archive/release/*
  • /pub/doc/* -> /pub/archive/doc/*

We don't plan on having many toplevel directories so layout shouldn't be too hard to figure out. I believe there was an email on this a while back I will create a wiki page using the details from there.

comment:4 Changed on Mar 3, 2015 at 5:56:11 PM by Amar Takhar

Milestone: 4.114.11.1

comment:5 Changed on Jan 26, 2017 at 7:16:00 AM by Sebastian Huber

Milestone: 4.11.14.11.2

comment:6 Changed on Feb 15, 2017 at 1:37:51 PM by Sebastian Huber

Milestone: 4.11.2Indefinite
Owner: set to Needs Funding
Status: newassigned

comment:7 Changed on Oct 10, 2017 at 6:12:28 AM by Sebastian Huber

Component: Otherunspecified
Note: See TracTickets for help on using tickets.