devel

devel@lists.centos.org

1 participants
4650 discussions

Metalinks for CentOS (all mirrors & checksums in one file)
by Anthony L. Bryan 16 Oct '06

16 Oct '06

Hi, Still seeing if you'd like to use metalinks for your ISO downloads. Metalinks contain mirror and p2p locations along with checksums and other metadata for faster and easier downloads. Downloads are distributed between mirrors and checksums are automatically verified when it finishes. Here's a good description: 'Metalink makes complex download pages obsolete by replacing long lists of download mirrors and BitTorrent trackers with a single .metalink file. As you might have already guessed, a .metalink file is a file that tells a download manager all the different ways it can download a file. The file itself takes the form of an open XML standard that can list an unlimited number of HTTP and FTP sources as well as BitTorrent trackers and ed2k and magnet links.' (http://www.downloadsquad.com/2006/08/28/metalinks-integrated-bittorrent-htt p-and-ftp-downloads/) There's a metalink for CentOS at http://www.metalinker.org/samples/CentOS-4.4-i386-LiveCD.iso.metalink if anyone wants to try it out. Here's what part of it looks like: <file name="CentOS-4.4-i386-LiveCD.iso"> <version>4.4</version> <verification> <hash type="md5">747c9e33a10fdbf5919d9fd188ab7d23</hash> </verification> <resources> <url type="http" preference="100">http://altruistic.lbl.gov/mirrors/centos/4.4/isos/i386/Cent OS-4.4-i386-LiveCD.iso</url> <url type="http" preference="100">http://centos.mirror.nac.net/4.4/isos/i386/CentOS-4.4-i386- LiveCD.iso</url> <url type="http" preference="100">http://dist1.800hosting.com/centos/4.4/isos/i386/CentOS-4.4 -i386-LiveCD.iso</url> <url type="http" location="us" preference="100">http://ftp.osuosl.org/pub/centos/4.4/isos/i386/CentOS-4.4-i 386-LiveCD.iso</url> </resources> Download clients are available for Unix, Mac, & Windows. aria2 RPMs for Red Hat Enterprise Linux 4 are at http://dries.ulyssis.org/rpm/packages/aria2/info.html OpenOffice.org and many Linux/BSD distributions are using metalink. Here's a few places: http://distribution.openoffice.org/p2p/magnet.html http://en.opensuse.org/Released_Version#Metalink http://desktopbsd.net/index.php?id=73 http://www.pcbsd.org/?p=download http://www.archlinux.org/download/ http://www.redwall-firewall.com/content/view/14/33/ http://yui.mine.nu/berry/edownload.php http://puppylinux.org/wikka/Puppy210 (( Anthony Bryan )) Metalink [ http://www.metalinker.org ]

2 1

Holger Daehre/SPOERLE ist außer Haus.
by Holger Daehre 15 Oct '06

15 Oct '06

Ich werde ab 02.10.2006 nicht im Büro sein. Ich kehre zurück am 30.10.2006. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

2 1

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 14 Oct '06

14 Oct '06

"JP" == Jim Perrin <jperrin(a)gmail.com> Jim, JP> This was discussed before implementation, in the -devel JP> channel on IRC. The full ramifications weren't felt JP> initially because it worked fine for stock centos. If JP> you'd like to participate in the discussions, you're JP> welcome to join the irc channel. Like, I suspect, most people using CentOS, I'm not paid to work on the OS, and I don't have time to hang out on IRC on the off chance that someone will bring up something that might completely screw up my systems down the road. To be frank, saying, ``Oh, we talked about that on IRC,'' is about as useful as saying, ``Jennie, Bob, and I talked about it over a drink at the Boo Bar.'' IRC is a great place to work out implementation details and maybe even do some thought experiments to imagine what the impact might be, but mailing lists are a much better place to have real discussions, especially when your changes might impact people outside the tiny circle of people who frequent the IRC channel. Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

9 14

RE: [CentOS-devel] Re: testing / qa process
by Alex Palenschat 13 Oct '06

13 Oct '06

> Instead of blocking on (lack-of) feedback, I'd suggest > considering something > like: > 1. Put pkgs in "testing" > 2. If no bugs reported after X days/weeks, move out of testing > > At least this way nothing gets perpetually stalled in testing. > > -- Rex > Just my 2 cents, but I have used some packages in the testing repo successfully. I certainly am not in a position to test them in a large production/enterprise environment and outside of the testing repo I try really hard to stay as vanilla as I can with my boxes. But I'm not certain what I can do except troll this list and say WorksForMe when somebody asks. I wouldn't guess that the signal-to-noise-ratio would be acceptable if everytime I successfully installed and used for a week package x that I post a new thread saying it worked. Perhaps you could find a method of requiring prospective users of the testing repo to subscribe to this mailing list. That way more users would see when a question/poll was asked in regards to a given package. Just an idea, Alex

2 1

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 12 Oct '06

12 Oct '06

"JN" == John Newbigin <jnewbigin(a)ict.swin.edu.au> JN> The easiest workaround I found was to add reposdir= JN> to your /etc/yum.conf [main] section. JN> This means you can't add other repos into that directory JN> but I don't normally do that anyway. Good if you don't, but if you wanted to, say, also use the RPMForge repositories, their package installs new .repo files into /etc/yum.repos.d. I'd imagine that most yumconf packages would do the same, as /etc/yum.repos.d is the standard location for those packages. Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

2 1

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 11 Oct '06

11 Oct '06

"KS" == Karanbir Singh <mail-lists(a)karan.org> KS> rm /etc/yum.repos.d/CentOS-Base.repo KS> touch /etc/yum.repos.d/CentOS-Base.repo KS> and the file wont get in the way anymore / anyless than it KS> did previously. That seems to work and I can easily add code to my setup script to do just that. It would be nice, however, if any future changes made by the CentOS team to the way fundamental aspects of the OS work were discussed before they're made, instead of making changes, breaking things, and then being abusive to everyone who has problems. Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

2 1

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 11 Oct '06

11 Oct '06

"KS" == Karanbir Singh <mail-lists(a)karan.org> KS> Just to do a recap to make sure we all understand the KS> position here. KS> There are 4 sorts of user cases, been addressed so far. [...] KS> did i miss someone ? Yes. 5. People who have replaced the centos-yumconf package (not just files in that package) with their own yumconf package that does not provide repository configuration files with the same names as the (old) centos-yumconf and the (current) centos-release package; i.e., CentOS-Base.repo. For those folks, the 4.4 redhat-release package plunks down a CentOS-Base.repo file. As my repo file is called HMC-Math-Base.repo, yum ignores my file and uses the new CentOS-Base.repo file instead for repository sections defined in both files. Adding ``enabled=0'' lines to the repository section in the CentOS-Base.repo file causes yum to complain about multiply defined repositories. Being able to replace the centos-yumconf package was a fairly low-key intervention that allowed me to maintain a pristine mirror of the upstream CentOS tree and do a basic install from that tree using a kickstart file, then, in a setup script run on first reboot, replace the centos-yumconf with my own, do updates, install local packages, and so forth. I'm not eager to have to rebuild the centos-release package for each update, so maybe the answer is to make my yumconf package supply CentOS-Base.repo and install it with the --force flag, but I preferred having a different name so that it would be obvious that we were using a local mirror. From my perspective, having the separate centos-yumconf preserves this behavior while remaining transparent to users who don't need to override repositories. Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

4 4

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 10 Oct '06

10 Oct '06

"JN" == John Newbigin <jnewbigin(a)ict.swin.edu.au> JN> The files /etc/yum.repos.d/* have moved from yumconf into JN> centos-release. I don't know if this is planned but the JN> net result is it broke my yum config (again) and unless JN> there is a good reason I don't know of, it seems broken. Note that I filed a bug about this issue: <http://bugs.centos.org/view.php?id=1486> Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

1 0

Re: [CentOS-devel] CentOS-4.4 yumconf
by C.M. Connelly 10 Oct '06

10 Oct '06

"JH" == Johnny Hughes <mailing-lists(a)hughesjr.com> JH> not specific to yum configs, but just config files for JH> updates in general. rhn sources file, yum config, etc. JH> In RHEL , the RHN files are included in redhat-release. That's arguable. The redhat-release package contains a file, /etc/sysconfig/rhn/sources, that sets up2date to use the default url. The comment there says ### The default RHN (using "default" as the url means use the one in the ### up2date config file). This is required. The actual sources are defined in the up2date config file, /etc/sysconfig/rhn/up2date, which is part of the up2date package. Yes, there is a sample line allowing up2date to use yum as its backend in the /etc/sysconfig/rhn/sources file, but it's commented out. Claire *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Claire Connelly cmc(a)math.hmc.edu Systems Administrator (909) 621-8754 Department of Mathematics Harvey Mudd College *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

1 0

Do not update packages without changelog please
by Milan Keršláger 09 Oct '06

09 Oct '06

Hi, I see that there are updates and no lines with reasons in the SPEC file (%chagelog). Please include changelog messages to allow track the changes and reasons for this (when something breaks for example). Also there are a tools for tracking changes in the updated system by emailing %changelog changes together with sw updates. Also there is almost no documentation even FC6 devel tree has a same package with a lot more docs: http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/os… There is still a question if the "stable" tree of CentOS 4 Extras should have latest and greatest package (in compare with FC4 or FC5 tree). -- Milan Kerslager E-mail: milan.kerslager(a)pslib.cz WWW: http://www.pslib.cz/ke/

4 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel