This script is one of the most frustrating things ever
written.
I made a fresh install (from CD) of 6.0R. In the install
I added gnome2, sudo, and bash. That's it. Gnome came up fine.
bash is great, sudo works.
Now, since gnome 2.12 is out, I want to upgrade to that.
Seems resonable.
http://www.freebsd.org/gnome tells us not to use portupgrade
to upgrade gnome2. The upgrades get out of order.
Ok fine, use gnome-upgrade.sh. And keep trying it says.
I've run it better than a dozen times, now. It's still trying.
All day, I turn and look at it periodically, resolve whatever
problem it seems to be having and start it up again.
1 time it said that it was successful! Woo Hoo! Wait, 2 times,
it just finished...
However it lies. What it's done is removed gnome completely.
The problem seems to lie in that downloads fail and so I get
a bunch of files in /usr/ports/distfiles that are not valid.
Using good old ftp, I grab the file needed and either build the
port and install or restart gnome-upgrade.sh
I'm now assuming that since all gnome has been wiped off the
disk, that the thing to do is build/install the port directly.
Starting that up, I seem to be having the same downloading difficulties.
--
______ Paul T. Root
/ _ \ 1977 MGB
/ /|| \\
||\/ || _ |
|| || ||
\ ||__//
\______/
On Wednesday 09 November 2005 13:46, Paul T. Root wrote:> This script is one of the most frustrating things ever > written. > > I made a fresh install (from CD) of 6.0R. In the install > I added gnome2, sudo, and bash. That's it. Gnome came up fine. > bash is great, sudo works. > > Now, since gnome 2.12 is out, I want to upgrade to that. > Seems resonable. > > http://www.freebsd.org/gnome tells us not to use portupgrade > to upgrade gnome2. The upgrades get out of order. > > Ok fine, use gnome-upgrade.sh. And keep trying it says. > > I've run it better than a dozen times, now. It's still trying. > All day, I turn and look at it periodically, resolve whatever > problem it seems to be having and start it up again. > > 1 time it said that it was successful! Woo Hoo! Wait, 2 times, > it just finished... > > However it lies. What it's done is removed gnome completely. > > > The problem seems to lie in that downloads fail and so I get > a bunch of files in /usr/ports/distfiles that are not valid. > Using good old ftp, I grab the file needed and either build the > port and install or restart gnome-upgrade.sh > > I'm now assuming that since all gnome has been wiped off the > disk, that the thing to do is build/install the port directly. > Starting that up, I seem to be having the same downloading difficulties.As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. -Mike
On Wednesday 09 November 2005 18:26, Paul Root wrote:> Michael C. Shultz wrote: > > *********************** > > This message has been scanned by the InterScan for CSC-SSM and found to > > be free of known security risks. ***********-*********** > > port and install or restart gnome-upgrade.sh > > >> I'm now assuming that since all gnome has been wiped off the > >> disk, that the thing to do is build/install the port directly. > >> Starting that up, I seem to be having the same downloading difficulties. > > > > As an alternative to gnome-upgrade.sh you may want to consider > > using sysutils/portmanager, all you need do is run > > > > portmanager x11/gnome2 > > > > It'll do the upgrade no problem, tested it twice now myself. > > Interesting. The web page said specifically don't do portupgrade.I didn't say portupgrade, it is sysutils/portmanager> > My main problem is it's having trouble downloading, I think. I'm > not sure why. We found problems on our Pix (actually the new > ASA firewall) and the port the machine is on. We were getting half > duplex, but those are all fixed now. Curiously, command line ftp > never has a problem downloading, it's fetch (I think it's using fetch), > that can't seem to download.While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed stable@freebsd.org from the return address as it is a dupe of freebsd-stable@freebsd.org.
On Thursday 10 November 2005 09:42, Paul T. Root wrote:> I moved the machine to a DSL line here, and am running > portmanager. It seems to be working. > > We're going to investigate issues with this beta Cisco > ASA machine.I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first "portmanager -v". If any problems arise I am more than happy to work with you in solving them quickly. -Mike> > Michael C. Shultz wrote: > > *********************** > > This message has been scanned by the InterScan for CSC-SSM and found to > > be free of known security risks. ***********-*********** > > > > On Wednesday 09 November 2005 18:26, Paul Root wrote: > >>Michael C. Shultz wrote: > >>>*********************** > >>>This message has been scanned by the InterScan for CSC-SSM and found to > >>>be free of known security risks. ***********-*********** > >> > >>port and install or restart gnome-upgrade.sh > >> > >>>>I'm now assuming that since all gnome has been wiped off the > >>>>disk, that the thing to do is build/install the port directly. > >>>>Starting that up, I seem to be having the same downloading > >>>> difficulties. > >>> > >>>As an alternative to gnome-upgrade.sh you may want to consider > >>>using sysutils/portmanager, all you need do is run > >>> > >>>portmanager x11/gnome2 > >>> > >>>It'll do the upgrade no problem, tested it twice now myself. > >> > >>Interesting. The web page said specifically don't do portupgrade. > > > > I didn't say portupgrade, it is sysutils/portmanager > > > >>My main problem is it's having trouble downloading, I think. I'm > >>not sure why. We found problems on our Pix (actually the new > >>ASA firewall) and the port the machine is on. We were getting half > >>duplex, but those are all fixed now. Curiously, command line ftp > >>never has a problem downloading, it's fetch (I think it's using fetch), > >>that can't seem to download. > > > > While your problem has nothing to do with gnome-upgrade.sh, portmanager > > is designed to automatically pickup from where it left off, so stopping > > and starting isn't a problem, and it won't remove a port until its > > replacement is successfully built so if the port didn't fetch you won't > > lose anything, portmanager will just move on to the next port that can be > > upgraded, it is very fail safe. > > > > -Mike > > > > Note: I removed stable@freebsd.org from the return address as it is a > > dupe of freebsd-stable@freebsd.org.
On Friday 11 November 2005 01:43, Jan Grant wrote:> Hope you don't mind me taking you up on your offer to someone else :-) - > this is more of a feature request from a portupgrade user who'd like to > migrate. > > On Thu, 10 Nov 2005, Michael C. Shultz wrote: > > On Thursday 10 November 2005 09:42, Paul T. Root wrote: > > > I moved the machine to a DSL line here, and am running > > > portmanager. It seems to be working. > > > > > > We're going to investigate issues with this beta Cisco > > > ASA machine. > > > > I am very interested at how things go with your upgrade, > > please keep me informed. Just to let you know, the current > > version of portmanager is 0.3.3_2 if anything goes wrong check > > that first "portmanager -v". If any problems arise I am more > > than happy to work with you in solving them quickly. > > I've been very interested in portmanager, but I'm facing a large > migration task because I've come from a portupgrade environment (and the > pain of migrating to portupgrade was bad enough :-) ) > > Ideally I'd like to be able to manage my portupgrade rules and derive > portmanager rules directly (at least for an interim period). There are a > couple of things which stop me shifting over (which I'd like to do, > since portupgrade still requires manual intervention too often). Note I > don't have what I'd describe as a _complex_ portupgrade configuration, > just a _large_ one. > > Firstly: unfortunately I believe that the wildcard-matching facility > available in pkgtools.conf isn't available in portmanager (I can't tell > from the man page or the sample, but it looks like that's not the case). > > My pkgtools.conf has hundreds(! - busy workstation) of entries along > these lines - some entries apply to several ports, and the portupgrade > toolset just basically uses the union of all matching rules: > > [[[ > '*/*' => 'BATCH=yes', > '*/kde*' => 'WITH_KDE_DEBUG=yes', > 'databases/p5-DBI' => 'WITH_PROXY=yes', > 'deskutils/kdepim3' => 'WITH_KPILOT=yes', > 'devel/gnomevfs2' => 'WITH_X11=yes', > 'devel/sdl12' => 'WITH_X11=yes', > 'devel/subversion' => 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes > WITHOUT_BDB=yes', ]]] > > ... and so on; so deskutils/kdepim3 gets built with > BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes > but more importantly, any future kde packages also get > WITH_KDE_DEBUG=yes automatically. > > It'd be convenient if portmanager supported the same wildcard > ability (it'd make the script to migrate settings from pkgtools.conf to > portmanager much more straightforward). > > The second issue is the AFTERINSTALL feature of pkgtools.conf; although > I make much less use of this, it's really handy to be able to specify > things like: > > [[[ > AFTERINSTALL = { > 'www/jakarta-tomcat5' => 'chmod a-x > /usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc > } > ]]] > > which let me encapsulate common small tweaks, post-installation. > > Do you have any suggestions about either of these? Lacking CFT at the > moment or I'd dive into the source.Port build options are covered in man portmanager(1). You didn't provide an example where wild cards are used so I'm not sure what you mean there. Here is how to handle this one:> AFTERINSTALL = { > 'www/jakarta-tomcat5' => 'chmod a-x > /usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc > }from portmanager(1) setting up pm-020.conf # # STOP/START these programs if they are updated # # Stop command will be run after program is built, before # old installed version is removed # # Start command will be run after rebuilt program is # installed and successfully registerd # # note: # must have leading "/" in /{category}/{port dir} # anything after /{category}/{port dir} is run as # a sh shell command # #STOP|/mail/postfix /usr/local/sbin/postfix stop| #START|/mail/postfix /usr/local/sbin/postfix start| In your case you would do this: STOP| www/jakarta-tomcat5 /usr/local/etc/rc.d/020.jakarta-tomcat*.sh| Stopping/starting is a new feature just introduced in 0.3.3_3. -Mike
On Friday 11 November 2005 09:04, Lowell Gilbert wrote:> "Michael C. Shultz" <ringworm01@gmail.com> writes: > > On Friday 11 November 2005 08:32, Lowell Gilbert wrote: > > > "Michael C. Shultz" <ringworm01@gmail.com> writes: > > > > Works good, just one thing, portmanager has no dependencies, like to > > > > keep it that way. > > > > > > It's not necessary to consider that an issue: this functionality is > > > really only useful to someone who has had portupgrade installed > > > anyway. > > > > I just thought of that, thanks for confirming :) > > Yeah, my secret of success in programming is to not fool myself into > making things more complicated than I need to do. > > You could even leave the script out of the port completely, and just > include a URL to it in the pkg-message...Simple, quick and painless :) If users want to simply convert that is the way to go. I also had in mind a knob like this: WITH_PORTUPGRADE_CONF if selected then portupgrade's settings are just added to portmanager's each time portmanager is run so if folks want to experiment with each program settings don't get lost. -Mike