Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7721 - Package directories for releases

Attached to Project: Arch Linux
Opened by Erwin Van de Velde (evdvelde) - Wednesday, 01 August 2007, 13:24 GMT
Last edited by Aaron Griffin (phrakture) - Thursday, 09 August 2007, 06:25 GMT
Task Type Support Request
Category Web Sites
Status Closed
Assigned To Dale Blount (dale)
Jason Chu (jason)
Tobias Powalowski (tpowa)
Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I post this under the Packages: Current category but it is valid for the other Packages categories as well.

Since 0.8 there seem to be no more separate directories for packages from a release, which is sometimes annoying: I work with disk images which I cannot change everyday since they are deployed on a testbed. If I update I can break tests from users and if I do not update and one of them needs a specific package which is not yet installed, he may be facing a huge update just to get that one installed. Is it possible to make a frozen package tree somewhere again for e.g. the last two releases?
This task depends upon

Closed by  Aaron Griffin (phrakture)
Thursday, 09 August 2007, 06:25 GMT
Reason for closing:  Won't implement
Comment by Aaron Griffin (phrakture) - Friday, 03 August 2007, 17:09 GMT
If you mean the "release" directory, I'm pretty sure it was never stable, was it? I thought it was just a symlink to current. I might be mistaken.

As a side note, you could always snag the full iso and unpack it, right?
Comment by Roman Kyrylych (Romashka) - Friday, 03 August 2007, 17:27 GMT
AFAIR we had "release" snapshot directories before 0.7.1 (IIRC)
0.8 (and 0.7.2?) didn't have a snapshot of packages at the moment of release in another directory.

I've finally found that old thread: http://archlinux.org/pipermail/arch-dev-public/2007-May/000742.html
and read it again.
It seems that this FR can be closed as "Won't implement", assuming that we're going to provide full DVD ISOs with repo snapshots (at the time of ISO release) in near furure.

Comment by Erwin Van de Velde (evdvelde) - Friday, 03 August 2007, 18:51 GMT
I think it is easier to have online repositories to refer to instead of DVD's, since I do not want to put the DVD in every machine where I want to add a package. It should be as easy as using the correct directories on the mirrors in pacman imho. Why would you not provide this? Is it a disk space issue on the mirrors? I really have to be able to keep repositories for the machines in the testbed stable for a period of two months or so, otherwise I have a lot of unhappy users...
Comment by Aaron Griffin (phrakture) - Friday, 03 August 2007, 20:01 GMT
It's not a disk space issue, it's a complexity and philosophy issue. Not only are we providing old packages, but we'd run into a Debian-esque situation where security fixes would need to be applied and things of that nature.

In addition, I don't understand why you'd have to dump the DVD on every machine? You can make a custom repo on one machine, and let all of the other machines use it - in essence providing the same exact functionality, just managed by you.

I guess I don't understand why a "stable" repo, for use by one (or a handful) of people needs to be managed by us. If your needs are restrictive like that, shouldn't you be managing the repository yourself?

Loading...