From akrherz at iastate.edu Mon Nov 9 19:37:48 2009 From: akrherz at iastate.edu (daryl herzmann) Date: Mon, 9 Nov 2009 13:37:48 -0600 (CST) Subject: [rhn-users] Re: RHN Hosted web session expires too quickly In-Reply-To: References: Message-ID: Well howdy again, If anybody is still curious about this, the public bugzilla tracking this issue can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=482748 daryl On Wed, 16 Sep 2009, daryl herzmann wrote: > Well howdy again, > > In case anybody was curious to reproduce this, here are the challenging > steps: > > 1) Locate a stop watch. It need not be a fancy one, my 1980s vintage > Casio wristwatch was up for the task. > 2) Log into RHN (be sure to have all the "Your RHN" modules disabled so > that your login does not time out). > 3) Start the stopwatch! > 4) Surf the RHN website. Check out how it took RHN a week to schedule > RHEL5.4 . Look at all of your systems and think warm thoughts about > how all of your information about your open source systems are stored > by Red Hat in a proprietary database. > ----> you are logged out in between your feverish clicking. Yell: "Boom!" > 5) Look at your stopwatch, it will say somewhere around 16 minutes and 45 > seconds. > > Enjoy! > > daryl > > On Thu, 10 Sep 2009, daryl herzmann wrote: > >> Well howdy there! >> >> I am a RHN hosted user that is getting very frustrated with having my web >> session timeout after what seems to be only a few minutes of inactivity >> (perhaps 5-15 minutes worth). It was a much longer period prior to a few >> months ago. >> >> I asked redhat support and got this response: >> >> "We would like inform you that, times out session for RHN is not >> configurable and we can not change it." >> >> Well that is not cool. Does anybody know of a setting or something that I >> can do to work around this? >> >> thanks, >> daryl > -- /** * Daryl Herzmann * Assistant Scientist -- Iowa Environmental Mesonet * http://mesonet.agron.iastate.edu */ From inode0 at gmail.com Mon Nov 9 19:40:19 2009 From: inode0 at gmail.com (inode0) Date: Mon, 9 Nov 2009 13:40:19 -0600 Subject: [rhn-users] Re: RHN Hosted web session expires too quickly In-Reply-To: References: Message-ID: On Mon, Nov 9, 2009 at 1:37 PM, daryl herzmann wrote: > Well howdy again, > > If anybody is still curious about this, the public bugzilla tracking this > issue can be found here: > > ?https://bugzilla.redhat.com/show_bug.cgi?id=482748 And now we have an infinite support loop formed between the two! John From bda20 at cam.ac.uk Mon Nov 9 19:41:00 2009 From: bda20 at cam.ac.uk (Ben) Date: Mon, 9 Nov 2009 19:41:00 +0000 (GMT) Subject: [rhn-users] Re: RHN Hosted web session expires too quickly In-Reply-To: References: Message-ID: On Mon, 9 Nov 2009, daryl herzmann wrote: > Well howdy again, > > If anybody is still curious about this, the public bugzilla tracking this > issue can be found here: > > https://bugzilla.redhat.com/show_bug.cgi?id=482748 Yes indeed. I've been following this BZ for some time. Given the paucity of updates I didn't think it was worth getting added to the CC: list before today. Now... now I think I have... hope? Ben -- Unix Support, MISD, University of Cambridge, England Plugger of wire, typer of keyboard, imparter of Clue Life Is Short. It's All Good. From mmeier at us.ibm.com Mon Nov 9 21:06:26 2009 From: mmeier at us.ibm.com (Maria Meier) Date: Mon, 9 Nov 2009 16:06:26 -0500 Subject: [rhn-users] AUTO: Maria Meier is out of the office (returning 11/16/2009) Message-ID: I am out of the office until 11/16/2009. I will respond to your message when I return on Monday, 11/16/2009 Note: This is an automated response to your message ",[rhn-users] Re: RHN Hosted web session expires too quickly" sent on 11/9/09 14:37:48. This is the only notification you will receive while this person is away. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dburbano at uniandes.edu.co Wed Nov 18 20:42:25 2009 From: dburbano at uniandes.edu.co (Daniel Alberto Burbano Sefair) Date: Wed, 18 Nov 2009 15:42:25 -0500 Subject: [rhn-users] warning and error Message-ID: <004a01ca688f$a45052e0$ecf0f8a0$@edu.co> Hello, Any idea about these errors or warning that I see in the message logs? We use RH 5.1 --------------------- Automount Begin ------------------------ **Unmatched Entries** lookup_read_master: lookup(nisplus): couldn't locat nis+ table auto.master: 3 Time(s) ---------------------- Automount End ------------------------- --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present end_request: I/O error, dev hda, sector ...: 10 Time(s) ---------------------- Kernel End ------------------------- Daniel Alberto Burbano Sefair Ingeniero Profesional Direcci?n de Tecnolog?as de Informaci?n Universidad de los Andes dburbano at uniandes.edu.co Tel.: [571] 339 4949/99 Ext.: 4702 Bogot?, Colombia -------------- next part -------------- An HTML attachment was scrubbed... URL: From felmasper at gmail.com Tue Nov 24 16:48:24 2009 From: felmasper at gmail.com (Felipe Massia) Date: Tue, 24 Nov 2009 14:48:24 -0200 Subject: [rhn-users] Re: RHN Hosted web session expires too quickly In-Reply-To: References: Message-ID: <7e727d5c0911240848u64b0d972i9c706a505f81d4ba@mail.gmail.com> This should be easy to fix technically. Are they trying to make people BUY Satellite? -- Felipe On Mon, Nov 9, 2009 at 17:41, Ben wrote: > On Mon, 9 Nov 2009, daryl herzmann wrote: > > Well howdy again, >> >> If anybody is still curious about this, the public bugzilla tracking this >> issue can be found here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=482748 >> > > Yes indeed. I've been following this BZ for some time. Given the paucity > of updates I didn't think it was worth getting added to the CC: list before > today. Now... now I think I have... hope? > > > Ben > -- > Unix Support, MISD, University of Cambridge, England > Plugger of wire, typer of keyboard, imparter of Clue > Life Is Short. It's All Good. > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sstone at pinecove.com Tue Nov 24 17:45:39 2009 From: sstone at pinecove.com (Seth Stone) Date: Tue, 24 Nov 2009 11:45:39 -0600 Subject: [rhn-users] Stay on minor release Message-ID: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems are automatically transitioned to the next minor release of the OS. For example, if I install 5.3 and run ?yum update? I will be migrated to 5.4. Is there any way to designate that you want to update only to the currently installed minor release? I?m trying to keep some test servers in sync with systems at our hosting provider that use a satellite RHN server that I can?t access from my test servers. I appreciate your response. Thanks, Seth Stone -------------- next part -------------- An HTML attachment was scrubbed... URL: From RJM002 at shsu.edu Tue Nov 24 18:02:48 2009 From: RJM002 at shsu.edu (Marti, Robert) Date: Tue, 24 Nov 2009 12:02:48 -0600 Subject: [rhn-users] Stay on minor release In-Reply-To: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> References: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> Message-ID: <8FAC1E47484E43469AA28DBF35C955E4A49B0D93AF@EXMBX.SHSU.EDU> Short answer, no it is not possible. Longer answer, Red Hat has some kind of entitlement that you can lock in a point release and not go past it, but it is NOT cheap. Rob Marti -----Original Message----- From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] On Behalf Of Seth Stone Sent: Tuesday, November 24, 2009 11:46 AM To: rhn-users at redhat.com Subject: [rhn-users] Stay on minor release I've noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems are automatically transitioned to the next minor release of the OS. For example, if I install 5.3 and run "yum update" I will be migrated to 5.4. Is there any way to designate that you want to update only to the currently installed minor release? I'm trying to keep some test servers in sync with systems at our hosting provider that use a satellite RHN server that I can't access from my test servers. I appreciate your response. Thanks, Seth Stone From bperkins at redhat.com Tue Nov 24 18:07:52 2009 From: bperkins at redhat.com (Brandon Perkins) Date: Tue, 24 Nov 2009 13:07:52 -0500 Subject: [rhn-users] Stay on minor release In-Reply-To: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> References: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> Message-ID: <4B0C20F8.5070307@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Seth Stone wrote: > I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems are automatically transitioned to the next minor release of the OS. For example, if I install 5.3 and run ?yum update? I will be migrated to 5.4. Is there any way to designate that you want to update only to the currently installed minor release? > > I?m trying to keep some test servers in sync with systems at our hosting provider that use a satellite RHN server that I can?t access from my test servers. > > I appreciate your response. > > Thanks, > Seth Stone > > > ------------------------------------------------------------------------ > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users By default, there is no mechanism to lock on to a particular X.Y release. However, you may be interested in looking at Extended Update Support: http://press.redhat.com/2008/12/18/red-hat-increases-service-levels-and-reduces-costs-for-customers-with-extended-update-support/ This would get you where you need to be and is fully supported with RHN Hosted and Satellite. Thanks. Brandon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iD8DBQFLDCD4hwQhj8l1t/cRAoMtAJ0fI3Su59PkGchPqqtsXRzScOWnRgCdHE9W a3/dXdI3kPbX5EY6Iwv8Fjw= =Mq+q -----END PGP SIGNATURE----- From sstone at pinecove.com Tue Nov 24 18:12:59 2009 From: sstone at pinecove.com (Seth Stone) Date: Tue, 24 Nov 2009 12:12:59 -0600 Subject: [rhn-users] Stay on minor release Message-ID: Thanks for the input everyone. In our situation it wouldn't be worth any extra cost to get this feature, but I'm glad to know I'm not missing something simple that would allow it to work. -----Original Message----- From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] On Behalf Of Brandon Perkins Sent: Tuesday, November 24, 2009 12:08 PM To: Discussions about Red Hat Network (rhn.redhat.com) Subject: Re: [rhn-users] Stay on minor release -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Seth Stone wrote: > I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems are automatically transitioned to the next minor release of the OS. For example, if I install 5.3 and run ?yum update? I will be migrated to 5.4. Is there any way to designate that you want to update only to the currently installed minor release? > > I?m trying to keep some test servers in sync with systems at our hosting provider that use a satellite RHN server that I can?t access from my test servers. > > I appreciate your response. > > Thanks, > Seth Stone > > > ------------------------------------------------------------------------ > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users By default, there is no mechanism to lock on to a particular X.Y release. However, you may be interested in looking at Extended Update Support: http://press.redhat.com/2008/12/18/red-hat-increases-service-levels-and-reduces-costs-for-customers-with-extended-update-support/ This would get you where you need to be and is fully supported with RHN Hosted and Satellite. Thanks. Brandon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/ iD8DBQFLDCD4hwQhj8l1t/cRAoMtAJ0fI3Su59PkGchPqqtsXRzScOWnRgCdHE9W a3/dXdI3kPbX5EY6Iwv8Fjw= =Mq+q -----END PGP SIGNATURE----- _______________________________________________ rhn-users mailing list rhn-users at redhat.com https://www.redhat.com/mailman/listinfo/rhn-users From felmasper at gmail.com Tue Nov 24 18:58:20 2009 From: felmasper at gmail.com (Felipe Massia) Date: Tue, 24 Nov 2009 16:58:20 -0200 Subject: [rhn-users] Stay on minor release In-Reply-To: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> References: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> Message-ID: <7e727d5c0911241058i2bc04feek26494659aad8f57e@mail.gmail.com> I think it's not feasible (financially?) to keep all minor versions up to date, it would be a maintainer's nightmare. Also, most people won't need to keep a system frozen at an exact minor release (except for the case I point out below). I think that's why Red Hat supports major versions only. This means that when a bug comes out, they need to fix only the latest versions of a package (one per major version). The problem is when a third party says "my product was validated to work with RHEL 5.1" but they've already released 5.4. And now, should I keep my system frozen at 5.1 or update it to 5.4+? Before continuing, let me quote http://www.redhat.com/security/updates/errata/: The Red Hat Enterprise Linux Life Cycle is designed to reduce the level of > change within each major release over time increasing predictability and > decreasing maintenance costs. > and also: During the entire Life Cycle, Red Hat makes commercially reasonable efforts > to maintain binary compatibility for the core runtime environment across all > minor releases and asynchronous errata (possible exceptions include critical > security issues). > So Red Hat does not *guarantee* 5.4 will behave the exact same way as a 5.1. Well, thinking about that, it's kind of impossible, isn't it? When they fix a bug, the behaviour is inevitably changed. So there's a best effort to minimize change, but they simply can't say there'll be no change at all. Back to the third party product validation issue, I believe saying it works for 5.1 is the same as saying it works for version 5, releases 1 and above. Some companies may refuse to give support to a system where the minor release is different. But isn't it obvious that an operating system must be updated? I guess minor releases are only a way to identify media releases (ISOs, CDs and DVDs). Also, a detail you may have missed: when you do "yum update" on a 5.3 you don't go exactly to 5.4, you go somewhere between 5.4 and 5.5. The only guaranteed way to go to a minor version (exactly) is installing from ISOs. -- Felipe On Tue, Nov 24, 2009 at 15:45, Seth Stone wrote: > I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my > systems are automatically transitioned to the next minor release of the OS. > For example, if I install 5.3 and run ?yum update? I will be migrated to > 5.4. Is there any way to designate that you want to update only to the > currently installed minor release? > > > > I?m trying to keep some test servers in sync with systems at our hosting > provider that use a satellite RHN server that I can?t access from my test > servers. > > > > I appreciate your response. > > > > Thanks, > > Seth Stone > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sstone at pinecove.com Tue Nov 24 19:46:14 2009 From: sstone at pinecove.com (Seth Stone) Date: Tue, 24 Nov 2009 13:46:14 -0600 Subject: [rhn-users] Stay on minor release Message-ID: This is kind of an side question: What event actually causes /etc/redhat-release to be updated? Is it once you get all the packages for a certain release or is there just a key package that causes the increment? From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] On Behalf Of Felipe Massia Sent: Tuesday, November 24, 2009 12:58 PM To: Discussions about Red Hat Network (rhn.redhat.com) Subject: Re: [rhn-users] Stay on minor release I think it's not feasible (financially?) to keep all minor versions up to date, it would be a maintainer's nightmare. Also, most people won't need to keep a system frozen at an exact minor release (except for the case I point out below). I think that's why Red Hat supports major versions only. This means that when a bug comes out, they need to fix only the latest versions of a package (one per major version). The problem is when a third party says "my product was validated to work with RHEL 5.1" but they've already released 5.4. And now, should I keep my system frozen at 5.1 or update it to 5.4+? Before continuing, let me quote http://www.redhat.com/security/updates/errata/: The Red Hat Enterprise Linux Life Cycle is designed to reduce the level of change within each major release over time increasing predictability and decreasing maintenance costs. and also: During the entire Life Cycle, Red Hat makes commercially reasonable efforts to maintain binary compatibility for the core runtime environment across all minor releases and asynchronous errata (possible exceptions include critical security issues). So Red Hat does not *guarantee* 5.4 will behave the exact same way as a 5.1. Well, thinking about that, it's kind of impossible, isn't it? When they fix a bug, the behaviour is inevitably changed. So there's a best effort to minimize change, but they simply can't say there'll be no change at all. Back to the third party product validation issue, I believe saying it works for 5.1 is the same as saying it works for version 5, releases 1 and above. Some companies may refuse to give support to a system where the minor release is different. But isn't it obvious that an operating system must be updated? I guess minor releases are only a way to identify media releases (ISOs, CDs and DVDs). Also, a detail you may have missed: when you do "yum update" on a 5.3 you don't go exactly to 5.4, you go somewhere between 5.4 and 5.5. The only guaranteed way to go to a minor version (exactly) is installing from ISOs. -- Felipe On Tue, Nov 24, 2009 at 15:45, Seth Stone wrote: I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems are automatically transitioned to the next minor release of the OS. For example, if I install 5.3 and run ?yum update? I will be migrated to 5.4. Is there any way to designate that you want to update only to the currently installed minor release? I?m trying to keep some test servers in sync with systems at our hosting provider that use a satellite RHN server that I can?t access from my test servers. I appreciate your response. Thanks, Seth Stone _______________________________________________ rhn-users mailing list rhn-users at redhat.com https://www.redhat.com/mailman/listinfo/rhn-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From felmasper at gmail.com Tue Nov 24 20:00:54 2009 From: felmasper at gmail.com (Felipe Massia) Date: Tue, 24 Nov 2009 18:00:54 -0200 Subject: [rhn-users] Stay on minor release In-Reply-To: References: Message-ID: <7e727d5c0911241200x24eb732enbea60175f1b9f9e@mail.gmail.com> What's the difference? What really defines your system is 5.x or 5.y? The redhat-release file in /etc or the set of packages you have installed? I believe it's the set of packages. Although some scripts check for a string in /etc/redhat-release, in fact this is a way of telling if the set of packages you have installed is compatible with the product being installed and prevent installation issues. Some programs are dumb and check for "5.x" string instead of only "5". In this case, one could overwrite the redhat-release to satisfy the script. -- Felipe On Tue, Nov 24, 2009 at 17:46, Seth Stone wrote: > This is kind of an side question: What event actually causes > /etc/redhat-release to be updated? Is it once you get all the packages for > a certain release or is there just a key package that causes the increment? > > > > *From:* rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com] > *On Behalf Of *Felipe Massia > *Sent:* Tuesday, November 24, 2009 12:58 PM > > *To:* Discussions about Red Hat Network (rhn.redhat.com) > *Subject:* Re: [rhn-users] Stay on minor release > > > > I think it's not feasible (financially?) to keep all minor versions up to > date, it would be a maintainer's nightmare. Also, most people won't need to > keep a system frozen at an exact minor release (except for the case I point > out below). I think that's why Red Hat supports major versions only. This > means that when a bug comes out, they need to fix only the latest versions > of a package (one per major version). > > > The problem is when a third party says "my product was validated to work > with RHEL 5.1" but they've already released 5.4. And now, should I keep my > system frozen at 5.1 or update it to 5.4+? Before continuing, let me quote > http://www.redhat.com/security/updates/errata/: > > The Red Hat Enterprise Linux Life Cycle is designed to reduce the level of > change within each major release over time increasing predictability and > decreasing maintenance costs. > > > and also: > > During the entire Life Cycle, Red Hat makes commercially reasonable efforts > to maintain binary compatibility for the core runtime environment across all > minor releases and asynchronous errata (possible exceptions include critical > security issues). > > > So Red Hat does not *guarantee* 5.4 will behave the exact same way as a > 5.1. Well, thinking about that, it's kind of impossible, isn't it? When they > fix a bug, the behaviour is inevitably changed. So there's a best effort to > minimize change, but they simply can't say there'll be no change at all. > > Back to the third party product validation issue, I believe saying it works > for 5.1 is the same as saying it works for version 5, releases 1 and above. > Some companies may refuse to give support to a system where the minor > release is different. But isn't it obvious that an operating system must be > updated? > > I guess minor releases are only a way to identify media releases (ISOs, CDs > and DVDs). > > Also, a detail you may have missed: when you do "yum update" on a 5.3 you > don't go exactly to 5.4, you go somewhere between 5.4 and 5.5. The only > guaranteed way to go to a minor version (exactly) is installing from ISOs. > -- > Felipe > > On Tue, Nov 24, 2009 at 15:45, Seth Stone wrote: > > I?ve noticed that with both up2date in RHEL 4 and yum in RHEL 5 my systems > are automatically transitioned to the next minor release of the OS. For > example, if I install 5.3 and run ?yum update? I will be migrated to 5.4. > Is there any way to designate that you want to update only to the currently > installed minor release? > > > > I?m trying to keep some test servers in sync with systems at our hosting > provider that use a satellite RHN server that I can?t access from my test > servers. > > > > I appreciate your response. > > > > Thanks, > > Seth Stone > > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users > > > > _______________________________________________ > rhn-users mailing list > rhn-users at redhat.com > https://www.redhat.com/mailman/listinfo/rhn-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Wed Nov 25 10:58:33 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 25 Nov 2009 11:58:33 +0100 Subject: [rhn-users] Stay on minor release In-Reply-To: <7e727d5c0911241058i2bc04feek26494659aad8f57e@mail.gmail.com> References: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> <7e727d5c0911241058i2bc04feek26494659aad8f57e@mail.gmail.com> Message-ID: <4B0D0DD9.9060205@kanarip.com> On 11/24/2009 07:58 PM, Felipe Massia wrote: > Also, a detail you may have missed: when you do "yum update" on a 5.3 > you don't go exactly to 5.4, you go somewhere between 5.4 and 5.5. The > only guaranteed way to go to a minor version (exactly) is installing > from ISOs. > That's not entirely true, although obviously 5.5 would include the same security- and bug-fixes released for point releases prior to 5.5. The minor releases are also the point in time where Red Hat may upgrade a certain piece of software, and may be including (backports of) drivers for new hardware, or new kernel features (KVM anyone?). One example of the inclusion of upgrades to a piece of software is the inclusion of a more recent version of Firefox in a point release (I believe it was 5.2). It's not like updating 5.4 before 5.5 is released brings you closer to 5.5 if you look at it from the perspective of how 5.5 as a whole may change compared to 5.4. We (the Fedora Project Extra Packages for Enterprise Linux[1] packagers) have seen similar things happen nearly every point release of RHEL so far. Packages that were part of EPEL may, given a point release, all of a sudden be part of RHEL and packages that were part of RHEL may be dropped from the distribution. Kind regards, -- Jeroen From kanarip at kanarip.com Wed Nov 25 11:02:15 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 25 Nov 2009 12:02:15 +0100 Subject: [rhn-users] Stay on minor release In-Reply-To: <4B0D0DD9.9060205@kanarip.com> References: <42070922-a1ee-4300-80d7-50f35ec62bc9@pinecove.com> <7e727d5c0911241058i2bc04feek26494659aad8f57e@mail.gmail.com> <4B0D0DD9.9060205@kanarip.com> Message-ID: <4B0D0EB7.9060400@kanarip.com> On 11/25/2009 11:58 AM, Jeroen van Meeuwen wrote: > We (the Fedora Project Extra Packages for Enterprise Linux[1] packagers) > have seen similar things happen nearly every point release of RHEL so > far. Packages that were part of EPEL may, given a point release, all of > a sudden be part of RHEL and packages that were part of RHEL may be > dropped from the distribution. > I forgot to add the reference to EPEL here: [1] http://fedoraproject.org/wiki/EPEL -- Jeroen