Date: Fri, 11 Jul 2003 15:02:49 -0700 (PDT) From: Aaron Levin <alevin@bepress.com> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@FreeBSD.org Subject: Re: problem with new /usr/ports/archivers/rpm checkin Message-ID: <20030711145857.X68125-100000@raider.bepress.com> In-Reply-To: <20030711215502.GA55456@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> It's more likely to be related to a recent bsd.port.mk commit that > works on new releases but not on old. yes i just tried rebuilding the port from the system that had built it fine and i get the same result (marked as broken). > No, about 5 years ago some people used to produce "upgrade packages" > that allowed old releases to use the current ports collection by > replacing necessary parts of the base system, but these were > discontinued due to lack of volunteers from the community to develop > and test the upgrade packages. > > > do you suggest that users not cvsup their ports collection if they > > don't have the most current release? > > Yes. great thanks for this. i don't want to waste your time further, but i am running a 4.6.2 system with linux_base6 and i need to go to the latest linux_base (linux 7). i already have this built and tested on a test machine. looking at the install, it appears that i can simply tar up my good /usr/compat/linux directory from the test machine and replace the existing /usr/compat/linux directory on my production machine and everything will to work. i have tested doing this on a different machine, but i would like your opinion. do you suggest i don't do this? all systems are 4.6.2. thanks again for all your help! i really appreciate it and am always impressed by the FreeBSD's support team. -Aaron Levin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030711145857.X68125-100000>