Re: Updating texlive-base with portupgrade fails (sort of)
On 8/25/2013 2:39 PM, Carmel wrote: > Using "portupgrade-devel-20130718,3" installed from the ports system, > attempting to update "texlive-base" always ends like this: > > ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400 > (consumed 00:11:57) > ---> Updating dependency info > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > ---> Upgrade of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:28 -0400 > (consumed 00:12:00) > ---> Session ended at: Sun, 25 Aug 2013 15:25:28 -0400 (consumed 00:12:19) > /usr/local/lib/ruby/site_ruby/1.9/pkgtools/pkgtools.rb:828: stack level too > deep (SystemStackError) > > I have attempted to reboot the system and then start the update > process; however it doesn't make any difference. Even though it appears > as if the port has been updated, when I run "pkgdb -aFv", I am greeted > with this: > > [...] > Checking texlive-base-20120701_7 > Checking texlive-full-20120701 > Stale dependency: texlive-full-20120701 -> texlive-base-20120701_8 > (print/texlive-base): > Disclose depends for texlive-full-20120701 > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > Fixed. (-> texlive-base-20120701_7) > [...] > > This is the only package that "portupgrade" seems to be chocking on. I > used "portupgrade" to initially install the complete "texlive" package, > so I am not sure why it is suddenly have problems. > I've just updated ports-mgmt/portupgrade-devel with a fix. Please give it a try and let me know. Version 20130916,3. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Updating texlive-base with portupgrade fails (sort of)
2013/8/25 Carmel : > Using "portupgrade-devel-20130718,3" installed from the ports system, > attempting to update "texlive-base" always ends like this: > > ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400 > (consumed 00:11:57) > ---> Updating dependency info > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > ---> Upgrade of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:28 -0400 > (consumed 00:12:00) > ---> Session ended at: Sun, 25 Aug 2013 15:25:28 -0400 (consumed 00:12:19) > /usr/local/lib/ruby/site_ruby/1.9/pkgtools/pkgtools.rb:828: stack level too > deep (SystemStackError) > > I have attempted to reboot the system and then start the update > process; however it doesn't make any difference. Even though it appears > as if the port has been updated, when I run "pkgdb -aFv", I am greeted > with this: > > [...] > Checking texlive-base-20120701_7 > Checking texlive-full-20120701 > Stale dependency: texlive-full-20120701 -> texlive-base-20120701_8 > (print/texlive-base): > Disclose depends for texlive-full-20120701 > ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS > Fixed. (-> texlive-base-20120701_7) > [...] > > This is the only package that "portupgrade" seems to be chocking on. I > used "portupgrade" to initially install the complete "texlive" package, > so I am not sure why it is suddenly have problems. > > -- > Carmel > carmel...@hotmail.com > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I don't understand why people try to "reboot" to fix problems, if it does not work now it will probably not after a reboot :-). Anyway, the problem seems to be located in portupgrade. I would encourage you to switch to ports-mgmt/portmaster as portupgrade is being less popular and less supported now. Cheers, -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Updating texlive-base with portupgrade fails (sort of)
Using "portupgrade-devel-20130718,3" installed from the ports system, attempting to update "texlive-base" always ends like this: ---> Build of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:25 -0400 (consumed 00:11:57) ---> Updating dependency info ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS ---> Upgrade of print/texlive-base ended at: Sun, 25 Aug 2013 15:25:28 -0400 (consumed 00:12:00) ---> Session ended at: Sun, 25 Aug 2013 15:25:28 -0400 (consumed 00:12:19) /usr/local/lib/ruby/site_ruby/1.9/pkgtools/pkgtools.rb:828: stack level too deep (SystemStackError) I have attempted to reboot the system and then start the update process; however it doesn't make any difference. Even though it appears as if the port has been updated, when I run "pkgdb -aFv", I am greeted with this: [...] Checking texlive-base-20120701_7 Checking texlive-full-20120701 Stale dependency: texlive-full-20120701 -> texlive-base-20120701_8 (print/texlive-base): Disclose depends for texlive-full-20120701 ---> Modifying /var/db/pkg/texlive-full-20120701/+CONTENTS Fixed. (-> texlive-base-20120701_7) [...] This is the only package that "portupgrade" seems to be chocking on. I used "portupgrade" to initially install the complete "texlive" package, so I am not sure why it is suddenly have problems. -- Carmel carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade -fpv devel/bzr fails with po/sv.po:193:13: invalid multibyte sequence
Hi, Is gettext 0.18.3 less forgiving than previous versions? Or are some of the translations encoded wrong? I even tried twice to forcefully upgrade everything depending on converters/libiconv, e.g. portupgrade -fprv converters/libiconv, but that didn't make a difference. Is there anything I can do, or should I wait until the translators catches up? running build_mo creating bzrlib/locale creating bzrlib/locale/my creating bzrlib/locale/my/LC_MESSAGES Compile: po/my.po -> bzrlib/locale/my/LC_MESSAGES/bzr.mo msgfmt -o bzrlib/locale/my/LC_MESSAGES/bzr.mo po/my.po creating bzrlib/locale/en_GB creating bzrlib/locale/en_GB/LC_MESSAGES Compile: po/en_GB.po -> bzrlib/locale/en_GB/LC_MESSAGES/bzr.mo msgfmt -o bzrlib/locale/en_GB/LC_MESSAGES/bzr.mo po/en_GB.po creating bzrlib/locale/sv creating bzrlib/locale/sv/LC_MESSAGES Compile: po/sv.po -> bzrlib/locale/sv/LC_MESSAGES/bzr.mo msgfmt -o bzrlib/locale/sv/LC_MESSAGES/bzr.mo po/sv.po po/sv.po:193:13: invalid multibyte sequence po/sv.po:193:14: invalid multibyte sequence po/sv.po:220:12: invalid multibyte sequence po/sv.po:220:13: invalid multibyte sequence po/sv.po:220:35: invalid multibyte sequence po/sv.po:220:36: invalid multibyte sequence po/sv.po:220:43: invalid multibyte sequence po/sv.po:220:44: invalid multibyte sequence po/sv.po:220:62: invalid multibyte sequence po/sv.po:220:63: invalid multibyte sequence po/sv.po:229:23: invalid multibyte sequence po/sv.po:229:24: invalid multibyte sequence po/sv.po:233:37: invalid multibyte sequence po/sv.po:233:38: invalid multibyte sequence po/sv.po:233:44: invalid multibyte sequence po/sv.po:233:45: invalid multibyte sequence po/sv.po:233:53: invalid multibyte sequence po/sv.po:233:54: invalid multibyte sequence po/sv.po:233:58: invalid multibyte sequence po/sv.po:233:59: invalid multibyte sequence msgfmt: too many errors, aborting error: command 'msgfmt' failed with exit status 1 *** [do-build] Error code 1 Stop in /usr/ports/devel/bzr. *** [build] Error code 1 Stop in /usr/ports/devel/bzr. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130729-96692-18p61og env UPGRADE_TOOL=portupgrade UPGRADE_PORT=bzr-2.5.1 UPGRADE_PORT_VER=2.5.1 make DEPENDS_TARGET=package ** Fix the problem and try again. ---> Build of devel/bzr ended at: Mon, 29 Jul 2013 12:09:28 +0200 (consumed 00:01:25) ---> Upgrade of devel/bzr ended at: Mon, 29 Jul 2013 12:09:28 +0200 (consumed 00:01:25) ---> ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! devel/bzr (bzr-2.5.1) (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ---> Session ended at: Mon, 29 Jul 2013 12:09:28 +0200 (consumed 00:01:27) -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkgng - Symlinks created by portupgrade?
On Fri, 11 Jan 2013 15:50:56 +, Matthew Seaman wrote:
> On 11/01/2013 15:18, Walter Hurry wrote:
>> On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote:
>>
>>> Thank you yet again, Matthew. As always, you are a fount of knowledge.
>>>
>>> The guidance on LATEST_LINK has helped a great deal. I still have a
>>> further question or two though; I shall follow up within a day or two.
>>
>> Just one further question: Is there a reason why 'pkg create' doesn't
>> generate synonyms this way, even when the output directory is set to
>> /usr/
>> ports/packages/All?
>
> Yes. 'pkg create' may be used to create arbitrary packages outside the
> context of ports, so it doesn't want to assume the LATEST_LINK layout.
> (All you need is an appropriate MANIFEST file... or a previously
> installed package on your system.)
>
> Like I said, for the purpose of generating a pkgng repo, this whole
> question of directory structure is pretty much immaterial: pkgng doesn't
> care. Any sort of directory structure containing .txz package tarballs
> will do. (Usually putting all the pkgs together in one big directory is
> what happens.)
>
> The LATEST_LINK layout is aimed at people logging into a ftp server and
> hunting through the directory tree for the packages they want. Most
> pkgng repos won't let you login like that, nor will all of them
> necessarily let you get a directory listing, other than the data you can
> extract from repo.sqlite.
>
> As for special casing things when writing to ${PORTSDIR}/packages/All --
> no one has seen fit to write the code to do that. If you think this
> sort of functionality would be useful, well, we always like to get pull
> requests. I would point out though that there is already perfectly good
> code in bsd.port.mk et al to do this sort of thing, which you can access
> by 'make package'.
>
Thanks for the comprehensive explanation, Matthew. It's no big deal; I
was just curious. Yes, I was aware that pkg repo ignores symlinks - it
says so in 'man pkg-repo'.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkgng - Symlinks created by portupgrade?
On 11/01/2013 15:18, Walter Hurry wrote:
> On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote:
>
>> Thank you yet again, Matthew. As always, you are a fount of knowledge.
>>
>> The guidance on LATEST_LINK has helped a great deal. I still have a
>> further question or two though; I shall follow up within a day or two.
>
> Just one further question: Is there a reason why 'pkg create' doesn't
> generate synonyms this way, even when the output directory is set to /usr/
> ports/packages/All?
Yes. 'pkg create' may be used to create arbitrary packages outside the
context of ports, so it doesn't want to assume the LATEST_LINK layout.
(All you need is an appropriate MANIFEST file... or a previously
installed package on your system.)
Like I said, for the purpose of generating a pkgng repo, this whole
question of directory structure is pretty much immaterial: pkgng doesn't
care. Any sort of directory structure containing .txz package tarballs
will do. (Usually putting all the pkgs together in one big directory is
what happens.)
The LATEST_LINK layout is aimed at people logging into a ftp server and
hunting through the directory tree for the packages they want. Most
pkgng repos won't let you login like that, nor will all of them
necessarily let you get a directory listing, other than the data you can
extract from repo.sqlite.
As for special casing things when writing to ${PORTSDIR}/packages/All --
no one has seen fit to write the code to do that. If you think this
sort of functionality would be useful, well, we always like to get pull
requests. I would point out though that there is already perfectly good
code in bsd.port.mk et al to do this sort of thing, which you can access
by 'make package'.
Cheers,
Matthew
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkgng - Symlinks created by portupgrade?
On Thu, 10 Jan 2013 01:50:34 +, Walter Hurry wrote: > Thank you yet again, Matthew. As always, you are a fount of knowledge. > > The guidance on LATEST_LINK has helped a great deal. I still have a > further question or two though; I shall follow up within a day or two. Just one further question: Is there a reason why 'pkg create' doesn't generate synonyms this way, even when the output directory is set to /usr/ ports/packages/All? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkgng - Symlinks created by portupgrade?
On Wed, 09 Jan 2013 18:54:35 +, Matthew Seaman wrote: > On 09/01/2013 18:31, Walter Hurry wrote: >> I am using pkgng. >> >> When I issue 'portupgrade -p', after build and installation, >> it builds a new package, as advertised. This (by default) is put into >> /usr/ ports/packages/All. >> >> At the same time, it installs a set of symlinks; one for each relevant >> port category, plus one in /usr/ports/packages/Latest. >> >> It is the naming of this last in which I am interested. Sometimes the >> symlink seems to bear the name (absent the version) of the package, and >> sometimes the name of the port (plus '.txz', of course). >> >> Two questions: >> >> 1) Does anyone know the logic used to derive the name of the symlink? >> >> 2) Would it be considered a breach of etiquette to email the port >> maintainer (bdrewery) and ask, or is this regarded as acceptable? >> >> 'man portupgrade' doesn't seem to shed any light on this, and I am >> unaware of where to seek other documentation. > > The layout of /usr/ports/packages is actually down to the ports system > directly and not in the control of any add on software like portupgrade, > portmaster or pkgng. > > The files under /usr/ports/packages/Latest are named according to the > LATEST_LINK variable in each port. It's meant to be unique per-port, > but falls somewhat short. Various ports have NO_LATEST_LINK set which > suppresses creating that link. Thank you yet again, Matthew. As always, you are a fount of knowledge. The guidance on LATEST_LINK has helped a great deal. I still have a further question or two though; I shall follow up within a day or two. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkgng - Symlinks created by portupgrade?
On 09/01/2013 18:31, Walter Hurry wrote: > I am using pkgng. > > When I issue 'portupgrade -p', after build and installation, it > builds a new package, as advertised. This (by default) is put into /usr/ > ports/packages/All. > > At the same time, it installs a set of symlinks; one for each relevant > port category, plus one in /usr/ports/packages/Latest. > > It is the naming of this last in which I am interested. Sometimes the > symlink seems to bear the name (absent the version) of the package, and > sometimes the name of the port (plus '.txz', of course). > > Two questions: > > 1) Does anyone know the logic used to derive the name of the symlink? > > 2) Would it be considered a breach of etiquette to email the port > maintainer (bdrewery) and ask, or is this regarded as acceptable? > > 'man portupgrade' doesn't seem to shed any light on this, and I am > unaware of where to seek other documentation. The layout of /usr/ports/packages is actually down to the ports system directly and not in the control of any add on software like portupgrade, portmaster or pkgng. The files under /usr/ports/packages/Latest are named according to the LATEST_LINK variable in each port. It's meant to be unique per-port, but falls somewhat short. Various ports have NO_LATEST_LINK set which suppresses creating that link. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
pkgng - Symlinks created by portupgrade?
I am using pkgng. When I issue 'portupgrade -p', after build and installation, it builds a new package, as advertised. This (by default) is put into /usr/ ports/packages/All. At the same time, it installs a set of symlinks; one for each relevant port category, plus one in /usr/ports/packages/Latest. It is the naming of this last in which I am interested. Sometimes the symlink seems to bear the name (absent the version) of the package, and sometimes the name of the port (plus '.txz', of course). Two questions: 1) Does anyone know the logic used to derive the name of the symlink? 2) Would it be considered a breach of etiquette to email the port maintainer (bdrewery) and ask, or is this regarded as acceptable? 'man portupgrade' doesn't seem to shed any light on this, and I am unaware of where to seek other documentation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 04:27 PM, Patrick Lamaiziere wrote: pkg is able to make packages upgrade by itself. I think the good way to update with packages is "pkg updgrade" then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. Understood. Thanks. I'll look into that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Got it. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Le Sat, 27 Oct 2012 21:22:32 +0300, Alexander Kapshuk a écrit : > Having done all of the above, I ran portupgrade to update all the > pkgs that needed upgrading on my system, and got the message below: > root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' > USING PKGNG > Packages are not yet suported. Use pkg(8) directly. > > That doesn't sound like portupgrade supports pkgng, or did I misread > the message in the UPDATING file? pkg is able to make packages upgrade by itself. I think the good way to update with packages is "pkg updgrade" then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 2:16 AM, Alexander Kapshuk wrote: > On 10/28/2012 03:00 AM, Bryan Drewery wrote: >> PKGNG is a replacement for the pkg_* tools that record package data in >> /var/db/pkg. >> >> It also allows for binary package upgrades. >> >> If you are wanting to use pkgng for binary packages, there's no need to >> use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. >> > Understood. Thanks. > > For some reason I thought I could use the PKGNG tool set together with > portupgrade the same way the pkg_* tools are used. pkgng obsoletes portupgrade -P and pkg_add -r. Even if portupgrade -P did have pkg support, it would not work right because of different OPTIONS/dependencies, and the desync between your local ports tree and the remote package server's versions. You can use 'pkg install' to replace 'portupgrade -P' right now, and just not use -P if you want to use the port. But it will not go smoothly. Picking one of the other is best. (Ports or packages) If you're managing multiple servers with packages, I recommend checking out ports-mgmt/poudriere (http://fossil.etoilebsd.net/poudriere) as it will build the binary packages to create your own remote pkgng repository. poudriere+pkgng really do obsolete portupgrade all together. > > Is there a straightforward way to go back to using the pkg_* tools in 9.1? If you have not installed, upgraded, or deinstalled anything, yes. You can cp all of the package dirs from /var/db/pkg.bak into /var/db/pkg, and remove WITH_PKGNG from /etc/make.conf and then run pkgdb -fu again. > > Thanks. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 03:00 AM, Bryan Drewery wrote: PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. Understood. Thanks. For some reason I thought I could use the PKGNG tool set together with portupgrade the same way the pkg_* tools are used. Is there a straightforward way to go back to using the pkg_* tools in 9.1? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/27/2012 1:22 PM, Alexander Kapshuk wrote: > Quick question about portupgrade's support for pkgng. > > The /usr/ports/UPDATING says: > 20121015: > AFFECTS: users of ports-mgmt/portupgrade > AUTHOR: bdrew...@freebsd.org > > Portupgrade now supports pkgng. To use pkgng, enable it in your > make.conf, > and convert your databases. > > This is optional and not currently required. > > # make -C /usr/ports/ports-mgmt/pkg install clean > # echo 'WITH_PKGNG=yes' >> /etc/make.conf > # pkg2ng > # pkgdb -fu > > Having done all of the above, I ran portupgrade to update all the pkgs > that needed upgrading on my system, and got the message below: > root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' > USING PKGNG > Packages are not yet suported. Use pkg(8) directly. > > That doesn't sound like portupgrade supports pkgng, or did I misread the > message in the UPDATING file? PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. > > box0=; uname -a > FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 > 17:11:45 UTC 2012 > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > Thanks. > > Alexander Kapshuk. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Fwd: re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
If my reading the code snippet below is right, portupgrade-2.4.10.2 does not support pkgng yet if pkgdb has been converted for use with pkgng using pkg2ng. /usr/ports/ports-mgmt/portupgrade/work/pkgtools-2.4.10.2/bin/portupgrade:561,565 # FIXME: pkgng if $use_packages && $pkgdb.with_pkgng? STDERR.puts "Packages are not yet suported. Use pkg(8) directly." return 0 end Original Message Subject: re: Portupgrade now supports pkgng [/usr/ports/UPDATING] Date: Sat, 27 Oct 2012 21:22:32 +0300 From: Alexander Kapshuk To: freebsd-questions@freebsd.org Quick question about portupgrade's support for pkgng. The /usr/ports/UPDATING says: 20121015: AFFECTS: users of ports-mgmt/portupgrade AUTHOR: bdrew...@freebsd.org Portupgrade now supports pkgng. To use pkgng, enable it in your make.conf, and convert your databases. This is optional and not currently required. # make -C /usr/ports/ports-mgmt/pkg install clean # echo 'WITH_PKGNG=yes' >> /etc/make.conf # pkg2ng # pkgdb -fu Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Quick question about portupgrade's support for pkgng. The /usr/ports/UPDATING says: 20121015: AFFECTS: users of ports-mgmt/portupgrade AUTHOR: bdrew...@freebsd.org Portupgrade now supports pkgng. To use pkgng, enable it in your make.conf, and convert your databases. This is optional and not currently required. # make -C /usr/ports/ports-mgmt/pkg install clean # echo 'WITH_PKGNG=yes' >> /etc/make.conf # pkg2ng # pkgdb -fu Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: boinc_gui missing after portupgrade
Thanks for your help Robert it is working again, odd how it has to be started form /var/db/boinc ! also noticed that "boinc_cmd" has changed it name to "boinccmd" and as for "boincmgr", I found that you need to run "boinccmd" from the /var/db/boinc folder as well, to do a manual update regards, David Whytcross - Original Message - From: "Robert Huff" To: Sent: Saturday, August 04, 2012 4:08 AM Subject: boinc_gui missing after portupgrade Robert Huff writes: > I am now missing boinc_gui from /usr/local/bin > > any ideas as to how to get it back ? I believe the literal answer is "downgrade". :-( The more useful answer is "it has been replaced by 'boincmgr'". hich, unfortunately, does not seem to pick up project/task information from the previous version. Further information: It does pick up the current porject/task information if you start it in the boinc directory (e.g. /var/db/boinc). Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
boinc_gui missing after portupgrade
Robert Huff writes: > > I am now missing boinc_gui from /usr/local/bin > > > > any ideas as to how to get it back ? > > I believe the literal answer is "downgrade". :-( > The more useful answer is "it has been replaced by > 'boincmgr'". hich, unfortunately, does not seem to pick up > project/task information from the previous version. Further information: It does pick up the current porject/task information if you start it in the boinc directory (e.g. /var/db/boinc). Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
boinc_gui missing after portupgrade
David Whytcross writes: > I just performed a portupgrade on 9.0-RELEASE to the > boinc-setathome-enhanced port, which took boinc-client from > boinc-client-6.4.5_7 to boinc-client-7.0.25_4 > > I am now missing boinc_gui from /usr/local/bin > > any ideas as to how to get it back ? I believe the literal answer is "downgrade". :-( The more useful answer is "it has been replaced by 'boincmgr'". hich, unfortunately, does not seem to pick up project/task information from the previous version. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
boinc_gui missing after portupgrade
Hi guys, I just performed a portupgrade on 9.0-RELEASE to the boinc-setathome-enhanced port, which took boinc-client from boinc-client-6.4.5_7 to boinc-client-7.0.25_4 I am now missing boinc_gui from /usr/local/bin any ideas as to how to get it back ? Dave Whytcross ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On Mon, 25 Jun 2012 00:53:50 -0700 (PDT) Dan Mahoney, System Admin wrote: > Hey there, > > I'm presently in the process of trying to do a portupgrade from > rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. > > Already, I've encountered several annoyances due to ABI changes, such > as the libtool2.4 fun. With normal portupgrade, this forces you to > go fix the dependent port. I don't know what you mean by that > Finally, I just applied -r, which should update all dependent > packages, but it seems to upgrade them unconditionally. That's because the revisions numbers will have been bumped, it's nothing to do with portupgrade. > Ergo, I've since built a new version of perl, a new verion of python, > rebuilt every perl module on the system, am presently rebuilding > apache22, and I'm sure the system will turn around and require me to > rebuild postgres real soon. > > You would think there's an option to portupgrade that says "don't > upgrade every single package I've got, Firstly it doesn't. Secondly no one is forcing you to do this, if you want to go through the ports and work out which need an update and which don't then portupgrade will let you do that. > but if somewhere in the > dependency chain I need a newer version of a thing, then do it." > > Am I just missing it in the manpages, or does such a thing really not > exist? > > -Dan > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 2012-06-25 11:47, John Levine wrote: You would think there's an option to portupgrade that says "don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it." The problem is that the versioning in the ports system doesn't distinguish between upgrades that present interface changes and upgrades that are just nits, new features, or minor bug fixes. Port makefiles can contain version dependency info, e.g., this port needs at least version N.M of package X, but few of them do. This has bitten me in the past with PHP and pcre. In fact, PHP5 won't work with old versions of pcre, but the PHP port maintainer refuses to put in version dependency info, because he thinks that every port should be up to date all the time. There's also the issue of things like Perl modules - most of them will just work, even with a newer version of perl, but a few have sections that need to be compiled against perl itself. So if you update the Perl port, you need to at least recompile those. (I'm simplifying a bit.) But there is no good way to mark in general which ports will 'just work' with an updated dependency, and which care what version of the dependency was installed when they were compiled. This is separate from versioned dependencies: Again to use Perl modules as an example, DBI for instance is will work with any version of perl since 5.8 or so - but if you change which version of perl you are using you'll need to recompile and reinstall. Rebuilding everything is a bit overkill, but it beats missing one that needed to be rebuilt. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
>You would think there's an option to portupgrade that says "don't upgrade >every single package I've got, but if somewhere in the dependency chain I >need a newer version of a thing, then do it." The problem is that the versioning in the ports system doesn't distinguish between upgrades that present interface changes and upgrades that are just nits, new features, or minor bug fixes. Port makefiles can contain version dependency info, e.g., this port needs at least version N.M of package X, but few of them do. This has bitten me in the past with PHP and pcre. In fact, PHP5 won't work with old versions of pcre, but the PHP port maintainer refuses to put in version dependency info, because he thinks that every port should be up to date all the time. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 06/25/12 09:53, Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. "-r" will upgrade all dependent ports *if* a newer version is available. "-rf" will upgrade all dependent ports unconditionally. You would think there's an option to portupgrade that says "don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it." I'm not sure what you mean. I guess you waned "portupgrade -R rt", which will upgrade all ports rt is depending on. HTH. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 06/25/12 10:40, Andrea Venturoli wrote: On 06/25/12 09:53, Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. "-r" will upgrade all dependent ports *if* a newer version is available. "-rf" will upgrade all dependent ports unconditionally. You would think there's an option to portupgrade that says "don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it." I'm not sure what you mean. I guess you waned "portupgrade -R rt", which will upgrade all ports rt ^ wanted is depending on. HTH. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 25/06/2012 08:53, Dan Mahoney, System Admin wrote: > I'm presently in the process of trying to do a portupgrade from rt-3.8.8 > to 3.8.13. By all estimations, this is a minor bump. > > Already, I've encountered several annoyances due to ABI changes, such as > the libtool2.4 fun. With normal portupgrade, this forces you to go fix > the dependent port. > > Finally, I just applied -r, which should update all dependent packages, > but it seems to upgrade them unconditionally. > > Ergo, I've since built a new version of perl, a new verion of python, > rebuilt every perl module on the system, am presently rebuilding > apache22, and I'm sure the system will turn around and require me to > rebuild postgres real soon. > > You would think there's an option to portupgrade that says "don't > upgrade every single package I've got, but if somewhere in the > dependency chain I need a newer version of a thing, then do it." > > Am I just missing it in the manpages, or does such a thing really not > exist? It has been many years since I used portupgrade with any regularity, and many of those neurones have been recycled. However, I do recall that: portupgrade -a should update all out-of-date ports on your system. portupgrade -r pkgname should update pkgname (if out of date) and all packages that depend on pkgname. portupgrade -R pkgname should update everything that pkgname depends on plus pkgname (if out of date). 'portupgrade -R' sounds like what you want. I believe that the meaning of the -r and -R flags in portupgrade is reversed from pkg_info(1) which is annoyingly inconsistent. Nowadays I usually use portmaster, where: portmaster pkgname works equivalently to 'portupgrade -R pkgname' except that portmaster /always/ reinstalls pkgname even if it is up to date. ie. the standard default action of portmaster is to do exactly what you want. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 6/25/12 9:53 AM, Dan Mahoney, System Admin wrote: > Hey there, > > I'm presently in the process of trying to do a portupgrade from rt-3.8.8 > to 3.8.13. By all estimations, this is a minor bump. > > Already, I've encountered several annoyances due to ABI changes, such as > the libtool2.4 fun. With normal portupgrade, this forces you to go fix > the dependent port. > > Finally, I just applied -r, which should update all dependent packages, > but it seems to upgrade them unconditionally. > > Ergo, I've since built a new version of perl, a new verion of python, > rebuilt every perl module on the system, am presently rebuilding > apache22, and I'm sure the system will turn around and require me to > rebuild postgres real soon. > > You would think there's an option to portupgrade that says "don't > upgrade every single package I've got, but if somewhere in the > dependency chain I need a newer version of a thing, then do it." > > Am I just missing it in the manpages, or does such a thing really not > exist? > > -Dan > We've been happily using portmanager for ages, it does just that :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade -- is there a way to only build and update ports that actually NEED it?
Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. Ergo, I've since built a new version of perl, a new verion of python, rebuilt every perl module on the system, am presently rebuilding apache22, and I'm sure the system will turn around and require me to rebuild postgres real soon. You would think there's an option to portupgrade that says "don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it." Am I just missing it in the manpages, or does such a thing really not exist? -Dan -- "You recreate the stars in the sky with cows?" -Furrball, March 7 2005, on Katamari Damacy Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with portupgrade libreoffice
On Sat, 09 Jun 2012 20:46:49 +, Walter Hurry wrote: > On Sat, 09 Jun 2012 18:12:25 +0100, Dave Morgan wrote: > >> On 09/06/12 at 04:41P, Walter Hurry wrote: >>> FreeBSD 9 on x86_64. >>> >>> I am in the process of doing a portupgrade on libreoffice (from 3.4.4 >>> to 3.5.2.5). During the build it has (so far) errored out 4 times, in >>> the following modules: >>> >>> vcl framework sfx2 tail_build >>> >>> Each time, it told me to go into the subdirectory, do a gmake clean >>> and a gmake -r there, then return to the top level and rerun make. >>> >>> This I duly did, but to my surprise, each time I ran the gmake -r, it >>> completed successfully. >>> >>> When the top-level make finally succeeds, I intend simply to rerun the >>> portupgrade, on the theory that seeing everything already made, it >>> will just do the uninstall/reinstall, sort out the dependencies and so >>> forth. >>> >>> Q1) Is this a sensible approach? >>> >>> Q2) Has anyone else seen this? What is going on? >> >> There is a thread in the forums which recommends removing boost-libs >> and boost-jam, building libreoffice then reinstalling them. >> >> I did this and it worked for me. > > Thanks. I'll try that and report back. Yes, that did the trick. It zoomed through! Very many thanks. I'll need to keep an eye on the forum, methinks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with portupgrade libreoffice
On Sat, 09 Jun 2012 18:12:25 +0100, Dave Morgan wrote: > On 09/06/12 at 04:41P, Walter Hurry wrote: >> FreeBSD 9 on x86_64. >> >> I am in the process of doing a portupgrade on libreoffice (from 3.4.4 >> to 3.5.2.5). During the build it has (so far) errored out 4 times, in >> the following modules: >> >> vcl framework sfx2 tail_build >> >> Each time, it told me to go into the subdirectory, do a gmake clean and >> a gmake -r there, then return to the top level and rerun make. >> >> This I duly did, but to my surprise, each time I ran the gmake -r, it >> completed successfully. >> >> When the top-level make finally succeeds, I intend simply to rerun the >> portupgrade, on the theory that seeing everything already made, it will >> just do the uninstall/reinstall, sort out the dependencies and so >> forth. >> >> Q1) Is this a sensible approach? >> >> Q2) Has anyone else seen this? What is going on? > > There is a thread in the forums which recommends removing boost-libs and > boost-jam, building libreoffice then reinstalling them. > > I did this and it worked for me. Thanks. I'll try that and report back. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with portupgrade libreoffice
On 09/06/12 at 04:41P, Walter Hurry wrote: > FreeBSD 9 on x86_64. > > I am in the process of doing a portupgrade on libreoffice (from 3.4.4 to > 3.5.2.5). During the build it has (so far) errored out 4 times, in the > following modules: > > vcl > framework > sfx2 > tail_build > > Each time, it told me to go into the subdirectory, do a gmake clean and a > gmake -r there, then return to the top level and rerun make. > > This I duly did, but to my surprise, each time I ran the gmake -r, it > completed successfully. > > When the top-level make finally succeeds, I intend simply to rerun the > portupgrade, on the theory that seeing everything already made, it will > just do the uninstall/reinstall, sort out the dependencies and so forth. > > Q1) Is this a sensible approach? > > Q2) Has anyone else seen this? What is going on? > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" There is a thread in the forums which recommends removing boost-libs and boost-jam, building libreoffice then reinstalling them. I did this and it worked for me. -- Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problems with portupgrade libreoffice
FreeBSD 9 on x86_64. I am in the process of doing a portupgrade on libreoffice (from 3.4.4 to 3.5.2.5). During the build it has (so far) errored out 4 times, in the following modules: vcl framework sfx2 tail_build Each time, it told me to go into the subdirectory, do a gmake clean and a gmake -r there, then return to the top level and rerun make. This I duly did, but to my surprise, each time I ran the gmake -r, it completed successfully. When the top-level make finally succeeds, I intend simply to rerun the portupgrade, on the theory that seeing everything already made, it will just do the uninstall/reinstall, sort out the dependencies and so forth. Q1) Is this a sensible approach? Q2) Has anyone else seen this? What is going on? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade ... doesn't
On 25 May 2012 12:10, Gary Aitken wrote: > Has to be something stupid: > > 347 /usr/ports#pkg_version -v | grep updating > p5-XML-Twig-3.39 < needs updating (port has 3.40) > > 348 /usr/ports#portupgrade -Rv P5-XML-Twig > ---> Session started at: Fri, 25 May 2012 10:03:54 -0600 > [Exclude up-to-date packages done] > ** None has been installed or upgraded. > ---> Session ended at: Fri, 25 May 2012 10:03:54 -0600 (consumed 00:00:00) > > 350 /usr/ports#pkg_info | grep p5-XML-Twig > p5-XML-Twig-3.39 Process huge XML documents by chunks via a tree > interface > > hints? Do pkg_version -vl"<" & pkg_version -vIl"<" give different results? (note that's an uppercase "i" followed by a lowercase "L" in case your screen font makes it hard to tell) I believe portupgrade uses the INDEX-* files to determine, whereas pkg_version uses the /usr/ports/*/*/distinfo file (unless -I is provided). -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade ... doesn't
Has to be something stupid: 347 /usr/ports#pkg_version -v | grep updating p5-XML-Twig-3.39< needs updating (port has 3.40) 348 /usr/ports#portupgrade -Rv P5-XML-Twig ---> Session started at: Fri, 25 May 2012 10:03:54 -0600 [Exclude up-to-date packages done] ** None has been installed or upgraded. ---> Session ended at: Fri, 25 May 2012 10:03:54 -0600 (consumed 00:00:00) 350 /usr/ports#pkg_info | grep p5-XML-Twig p5-XML-Twig-3.39Process huge XML documents by chunks via a tree interface hints? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: p5-XML-SAX and portupgrade
On 2012-05-14 10:16, n dhert wrote: There is an update of p5-XML-SAX in the ports, /usr/ports/UPDATING says: 20120512: AFFECTS: users of textproc/p5-XML-SAX AUTHOR: cr...@freebsd.org p5-XML-SAX (X-S) was split into p5-XML-SAX-Base (X-S-B) and p5-XML-SAX for version 0.99. Since X-S-B now installs some files formerly installed by X-S the package for X-S must be deinstalled before updating X-S. # pkg_delete -fx p5-XML-SAX # portmaster textproc/p5-XML-SAX (users of pkgng can substitute pkg_delete with pkg delete) But what is the instruction for users of portupgrade ? Susbstitude "portmaster" with "portupgrade" is my guess. Armin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
p5-XML-SAX and portupgrade
There is an update of p5-XML-SAX in the ports, /usr/ports/UPDATING says: 20120512: AFFECTS: users of textproc/p5-XML-SAX AUTHOR: cr...@freebsd.org p5-XML-SAX (X-S) was split into p5-XML-SAX-Base (X-S-B) and p5-XML-SAX for version 0.99. Since X-S-B now installs some files formerly installed by X-S the package for X-S must be deinstalled before updating X-S. # pkg_delete -fx p5-XML-SAX # portmaster textproc/p5-XML-SAX (users of pkgng can substitute pkg_delete with pkg delete) But what is the instruction for users of portupgrade ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade -cfa status while executing
On Sunday 29 April 2012, dgmm wrote: > When running portupgrade -cfa, is there any way to find out where it's up > to and/ot what is still in the queue to be re-built? Oops. It was obvious really. ls /var/db/pkg -htU ...is good enough for my needs. -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade -cfa status while executing
When running portupgrade -cfa, is there any way to find out where it's up to and/ot what is still in the queue to be re-built? -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade
n dhert wrote: > Today, my nightly run of portsnap informed me there is un update for: > # pkg_version -vIL= > portupgrade-2.4.9.3.2 < needs updating (index has 2.4.9.3_1,2) > > Since there is no special entry in /usr/ports/UPDATING about the > portupgrade update, > I started my weekly > # portupgrade -yaRrpb > > this gives: > ... > ---> Upgrade of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 > 08:37:14 +0 > 200 > ---> Upgrading 'portupgrade-2.4.9.3,2' to 'portupgrade-2.4.9.3_1,2' > (ports-mgmt > /portupgrade) > ---> Build of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 > 08:37:14 +020 > 0 > ---> Building '/usr/ports/ports-mgmt/portupgrade' > ===> Cleaning for portupgrade-2.4.9.3_1,2^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > ===> Extracting for portupgrade-2.4.9.3_1,2^M > => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M > ===> Refetch for 1 more times files: pkgtools-2.4.9.3.tar.bz2 ^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > => pkgtools-2.4.9.3.tar.bz2 doesn't seem to exist in > /usr/ports/distfiles/.^M > => Attempting to fetch > http://heanet.dl.sourceforge.net/project/portupgrade/pkgt > ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M > fetch: > http://heanet.dl.sourceforge.net/project/portupgrade/pkgtools/2.4.9.3/pkg > tools-2.4.9.3.tar.bz2: Moved Temporarily^M > it does 5 more at other places, then > => Attempting to fetch > http://freefr.dl.sourceforge.net/project/portupgrade/pkgt > ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M > fetch: pkgtools-2.4.9.3.tar.bz2: local file (79394 bytes) is longer than > remote > file (79377 bytes)^M > ... > then 10 more 'Attempting to fetch' with Moved temporarily > then > => Attempting to fetch > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgtool > s-2.4.9.3.tar.bz2^M > ===> License BSD accepted by the user^M > ===> Found saved configuration for portupgrade-2.4.6,2^M > => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M > ===> Giving up on fetching files: pkgtools-2.4.9.3.tar.bz2 ^M > Make sure the Makefile and distinfo file > (/usr/ports/ports-mgmt/portupgrade/dist > info)^M > are up to date. If you are absolutely sure you want to override this^M > check, type "make NO_CHECKSUM=yes [other args]".^M > *** Error code 1^M > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > *** Error code 1^M > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > *** Error code 1^M > ^M > Stop in /usr/ports/ports-mgmt/portupgrade.^M > ---> Build of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 > +0200 > (consumed 00:00:30) > ---> Upgrade of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 > 08:37:45 +020 > 0 (consumed 00:00:30) > > What's this problem with pkgtools ??? > I have a > $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 > -rw-r--r-- 1 root wheel 79394 Aug 23 2011 > /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 > but no 2.4.9.3_1,2 version > > And, strange: if I try > http://www.freebsd.org/ports, Search for pkgtools in All > it finds nothing ??? Isn't that package described ?? Search for portupgrade instead. > What's going on here and how to solve it ?? I just did this upgrade utilizing portupgrade 2 days ago - 04/20/12 03:34 and did not experience any trouble. However, I noticed the name of the file that was downloaded here was: pkgtools-pkgtools-b99f3ce.tar.gz. This file was 98949 bytes in size. Today I have csup'd my ports tree and did a make fetch for this port and it downloaded a file of the same name as you have described. This file is 79377 bytes in size. I did a make for the port and it again built without error. Sounds like something was out of sync at the time you tried this. Try refreshing your ports again and see if it has been fixed. Also consider the possibility that the mirror you were using wasn't completely up to date. Either the mirror will have caught up since then, or try another mirror. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade
On 23/04/2012 17:13, n dhert wrote: Today, my nightly run of portsnap informed me there is un update for: # pkg_version -vIL= portupgrade-2.4.9.3.2< needs updating (index has 2.4.9.3_1,2) => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M ===> Giving up on fetching files: pkgtools-2.4.9.3.tar.bz2 ^M Make sure the Makefile and distinfo file (/usr/ports/ports-mgmt/portupgrade/dist info)^M are up to date. If you are absolutely sure you want to override this^M check, type "make NO_CHECKSUM=yes [other args]".^M *** Error code 1^M What's this problem with pkgtools ??? I have a $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 -rw-r--r-- 1 root wheel 79394 Aug 23 2011 /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 but no 2.4.9.3_1,2 version And, strange: if I try http://www.freebsd.org/ports, Search for pkgtools in All it finds nothing ??? Isn't that package described ?? What's going on here and how to solve it ?? The issue would appear to be the recent update was messed up. You are getting an error as the distfile you have has a different md5sum than what was saved to the port files. pkgtools is the name of the project, even though the sourceforge project name and the port name is portupgrade. On github it is pkgtools. I would guess the port name was chosen to prevent conflicts with pkg_* named tools in the base system. I would wait for the maintainer to sort things out. Currently you can download a tar.gz from github or a tar.bz from sourceforge both identified as 2.4.9.3 but there is some file differences between them. As this is a new maintainer just taken over the port about a week ago you may want to email them or submit a pr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
upgrade of portupgrade
Today, my nightly run of portsnap informed me there is un update for: # pkg_version -vIL= portupgrade-2.4.9.3.2 < needs updating (index has 2.4.9.3_1,2) Since there is no special entry in /usr/ports/UPDATING about the portupgrade update, I started my weekly # portupgrade -yaRrpb this gives: ... ---> Upgrade of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 08:37:14 +0 200 ---> Upgrading 'portupgrade-2.4.9.3,2' to 'portupgrade-2.4.9.3_1,2' (ports-mgmt /portupgrade) ---> Build of ports-mgmt/portupgrade started at: Mon, 23 Apr 2012 08:37:14 +020 0 ---> Building '/usr/ports/ports-mgmt/portupgrade' ===> Cleaning for portupgrade-2.4.9.3_1,2^M ===> License BSD accepted by the user^M ===> Found saved configuration for portupgrade-2.4.6,2^M ===> Extracting for portupgrade-2.4.9.3_1,2^M => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M ===> Refetch for 1 more times files: pkgtools-2.4.9.3.tar.bz2 ^M ===> License BSD accepted by the user^M ===> Found saved configuration for portupgrade-2.4.6,2^M => pkgtools-2.4.9.3.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.^M => Attempting to fetch http://heanet.dl.sourceforge.net/project/portupgrade/pkgt ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M fetch: http://heanet.dl.sourceforge.net/project/portupgrade/pkgtools/2.4.9.3/pkg tools-2.4.9.3.tar.bz2: Moved Temporarily^M it does 5 more at other places, then => Attempting to fetch http://freefr.dl.sourceforge.net/project/portupgrade/pkgt ools/2.4.9.3/pkgtools-2.4.9.3.tar.bz2^M fetch: pkgtools-2.4.9.3.tar.bz2: local file (79394 bytes) is longer than remote file (79377 bytes)^M ... then 10 more 'Attempting to fetch' with Moved temporarily then => Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgtool s-2.4.9.3.tar.bz2^M ===> License BSD accepted by the user^M ===> Found saved configuration for portupgrade-2.4.6,2^M => SHA256 Checksum mismatch for pkgtools-2.4.9.3.tar.bz2.^M ===> Giving up on fetching files: pkgtools-2.4.9.3.tar.bz2 ^M Make sure the Makefile and distinfo file (/usr/ports/ports-mgmt/portupgrade/dist info)^M are up to date. If you are absolutely sure you want to override this^M check, type "make NO_CHECKSUM=yes [other args]".^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M *** Error code 1^M ^M Stop in /usr/ports/ports-mgmt/portupgrade.^M ---> Build of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 +0200 (consumed 00:00:30) ---> Upgrade of ports-mgmt/portupgrade ended at: Mon, 23 Apr 2012 08:37:45 +020 0 (consumed 00:00:30) What's this problem with pkgtools ??? I have a $ ls -la /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 -rw-r--r-- 1 root wheel 79394 Aug 23 2011 /usr/ports/distfiles/pkgtools-2.4.9.3.tar.bz2 but no 2.4.9.3_1,2 version And, strange: if I try http://www.freebsd.org/ports, Search for pkgtools in All it finds nothing ??? Isn't that package described ?? What's going on here and how to solve it ?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade not preserving shared libs as documented?
On Wed, 11 Apr 2012 02:52:56 -0700 Cstdenis wrote: > Portupgrade man page says "By default, portupgrade preserves shared > libraries on uninstallation for safety." > > I ran i in the form of: portupgrade -b pcre > > Now /usr/local/lib/libpcre.so.0 does not exist anymore, only the new > /usr/local/lib/libpcre.so.1 is there. It backs them up under the compat directory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade not preserving shared libs as documented?
Portupgrade man page says "By default, portupgrade preserves shared libraries on uninstallation for safety." I ran i in the form of: portupgrade -b pcre Now /usr/local/lib/libpcre.so.0 does not exist anymore, only the new /usr/local/lib/libpcre.so.1 is there. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Major version changes using portupgrade?
On 04/12/2011 20:07, Matthew Pounsett wrote: > On 2011/12/04, at 14:13, Matthew Seaman wrote: > >> > 4) Now for the updating bit. I'm going to use portmaster's '-o' >> > functionality to swap out the postgresql versions. (portupgrade >> > has very similar functionality if you prefer that.) postgresql >> > is trickier than most, because there have to be both -server and >> > -client ports to deal with. I also have postgresql-contrib-9.0.5 >> > installed, which isn't critical but needs similar treatment. >> > Everything depends on the -client port, so we start with that: >> > >> ># portmaster -o databases/postgresql91-client \ >> > postgresql-client-9.0.5 >> ># portmaster -o databases/postgresql91-server \ >> > postgresql-server-9.0.5_1 >> ># portmaster -o databases/postgresql91-contrib \ >> > postgresql-contrib-9.0.5 > This is the problem bit. The -o doesn't work with the ones I'm > dealing with because of conflicts between 8.4 and 9.1. 9.1 *won't > even build*. If you can find a way to get around that, then you can > make life even easier for yourself by doing a recursive build of all > of the things that depend on the client. It's getting around the > conflict that I'm trying to figure out... the rest is handled. Not a problem with portmaster(1) -- it automatically adds DISABLE_CONFLICTS to the make environment if you're using the '-o' flag. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Major version changes using portupgrade?
On 2011/12/02, at 05:19, Matthew Pounsett wrote: > I was expecting the following to work: > sudo portupgrade -rf -o databases/postgresql91-client > databases/postgresql84-client > > However, I'm running into a problem where the ports makefiles, and by > extension portupgrade, are detecting that the two packages conflict, and so > the 9.1 client won't even build[1]. Thanks to those who tried to help. After poking around in the Mk files A LOT, I eventually stumbled upon a solution. Not sure if this is "right" or not, but it worked: > sudo portupgrade -M DISABLE_CONFLICTS=1 -rf -o databases/postgresql91-client > databases/postgresql84-client Surprisingly, despite the -f, none of the dependencies were rebuilt.. I got warnings like this instead, for every dependency: ---> Skipping 'databases/postgresql91-client' (apache-2.2.21) because it has already done However, the +REQUIRED_BY file was still rebuilt properly for the 9.1 client, so I can now easily go through and do dependency rebuilds as necessary. Cheers, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Major version changes using portupgrade?
On 2011/12/04, at 14:13, Matthew Seaman wrote: > 4) Now for the updating bit. I'm going to use portmaster's '-o' > functionality to swap out the postgresql versions. (portupgrade > has very similar functionality if you prefer that.) postgresql > is trickier than most, because there have to be both -server and > -client ports to deal with. I also have postgresql-contrib-9.0.5 > installed, which isn't critical but needs similar treatment. > Everything depends on the -client port, so we start with that: > ># portmaster -o databases/postgresql91-client \ > postgresql-client-9.0.5 > # portmaster -o databases/postgresql91-server \ > postgresql-server-9.0.5_1 > # portmaster -o databases/postgresql91-contrib \ > postgresql-contrib-9.0.5 This is the problem bit. The -o doesn't work with the ones I'm dealing with because of conflicts between 8.4 and 9.1. 9.1 *won't even build*. If you can find a way to get around that, then you can make life even easier for yourself by doing a recursive build of all of the things that depend on the client. It's getting around the conflict that I'm trying to figure out... the rest is handled. And by the way, if you're not already doing a recursive build then you can do the server upgrade more simply.. there are no dependencies attached to the server (normally) so you can just pkg_delete it and install 9.1. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Major version changes using portupgrade?
On 04/12/2011 17:16, Matthew Pounsett wrote: > On 2011/12/04, at 02:29, Sergio Tam wrote: > >>> >> ===> postgresql-client-9.1.1_1 conflicts with installed package(s): >>> >> postgresql-client-8.4.8 >>> >> >>> >> They will not build together. >>> >> Please remove them first with pkg_delete(1). <pay >>> >> attention here >>> >> *** Error code 1 >> > >> > >> > postgresql-client-8.4.8 >> > >> > make deinstall > That's the ports makefiles talking, isn't it? In order to do that > deinstall I need to also remove all of the things that depend on > it... portupgrade is supposed to help me do the in-place upgrade > without removing everything else first. > > Even if I forced the deinstall without letting the dependencies get > in the way, wouldn't that break the dependency registration > (+REQUIRED_BY) for all of those packages in the future? Yes. I've been planning a very similar update -- postgresql 9.0 to 9.1 -- and what I've come up with so far is this: 0) Backup *everything* 1) Stop postgresql daemon and any services that depend on postgresql 2) Move the postgresql data directory aside: # mv ~pgsql/data ~pgsql/data-9.0.5 3) Optional. If you have WITH_PGSQL_VER defined in /etc/make.conf, or similar update it at this point. Or delete it -- ports will pick up the new version automatically once you've updated to it. 4) Now for the updating bit. I'm going to use portmaster's '-o' functionality to swap out the postgresql versions. (portupgrade has very similar functionality if you prefer that.) postgresql is trickier than most, because there have to be both -server and -client ports to deal with. I also have postgresql-contrib-9.0.5 installed, which isn't critical but needs similar treatment. Everything depends on the -client port, so we start with that: # portmaster -o databases/postgresql91-client \ postgresql-client-9.0.5 # portmaster -o databases/postgresql91-server \ postgresql-server-9.0.5_1 # portmaster -o databases/postgresql91-contrib \ postgresql-contrib-9.0.5 5) Now rebuild everything that depends on the new postgresql client port. Use '-x' and '-R' to avoid rebuilding the ports already updated # portmaster -R -r postgresql-client-9.1.1_1 \ -x postgresql-server-9.1.1_1 -x postgresql-contrib-9.1.1_1 6) Re-init the postgresql cluster # su - pgsql % mkdir ~/data % initdb -D ~/data -E utf8 --locale C (or use the rc.d script) % vi ~/data/postgresql.conf(etc...) 7) Restart the postgresql database # /usr/local/etc/rc.d/postgresql start 8) Reload databases from backup. Restart all dependent services. 9) ??? 10) Profit! This does require an appreciable period of system downtime, but as that's fine for my purposes, I haven't put any effort into thinking about how to minimize that. A good thing to do if downtime is a big deal for you would be to build updated packages of everything postgresql related off-line and use portmaster's '-P' package mode to install them. Similarly, make backup packages of everything you're updating (pkg_create -b pkgname) so if you need to back everything out you can just swap those packages back in rather than doing a full-scale recovery from backup. Using this method for a very big database is not amazingly practical -- in that case, using pg_upgrade(8) would probably be preferable, but that's not going to entirely simple given the constraints of the ports system. You'll need to have both the previous and target versions of the postgresql-client and postgresql-contrib installed simultaneously, but those ports all conflict with each other. You'll also need to have two separate data directories -- the original one and one for the new version. The default layout on Linux nowadays includes the postgresql major version in the data directory path and in the names of most conflicting applications, but this capability hasn't come to the ports yet. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Major version changes using portupgrade?
On 2011/12/04, at 02:29, Sergio Tam wrote: >> ===> postgresql-client-9.1.1_1 conflicts with installed package(s): >> postgresql-client-8.4.8 >> >> They will not build together. >> Please remove them first with pkg_delete(1). <pay >> attention here >> *** Error code 1 > > > postgresql-client-8.4.8 > > make deinstall That's the ports makefiles talking, isn't it? In order to do that deinstall I need to also remove all of the things that depend on it... portupgrade is supposed to help me do the in-place upgrade without removing everything else first. Even if I forced the deinstall without letting the dependencies get in the way, wouldn't that break the dependency registration (+REQUIRED_BY) for all of those packages in the future? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Major version changes using portupgrade?
2011/12/2 Matthew Pounsett : > > I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've > dumped the db and uninstalled the postgres-server port, and I'd like to use > portupgrade to handle the client upgrade, since it has a number of > dependencies that probably should be recompiled against the new client libs > (and I'd like to keep the package's +REQUIRED_BY file properly updated > anyway). > > I was expecting the following to work: > sudo portupgrade -rf -o databases/postgresql91-client > databases/postgresql84-client > > However, I'm running into a problem where the ports makefiles, and by > extension portupgrade, are detecting that the two packages conflict, and so > the 9.1 client won't even build[1]. > > This seems to be the sort of situation described by the -o example in the > portupgrade man page, but I haven't been able to figure out how to make it > work. Does anyone have any suggestions? > > Thanks! > > -- > > [1] > [Updating the pkgdb in /var/db/pkg ... - 140 packages > found (-1 +0) (...) done] > ---> Upgrading 'postgresql-client-8.4.8' to 'postgresql-client-9.1.1_1' > (databases/postgresql91-client) > ---> Building '/usr/ports/databases/postgresql91-client' > ===> Cleaning for postgresql-client-9.1.1_1 > cd /usr/ports/databases/postgresql91-client && make config; > > ===> postgresql-client-9.1.1_1 conflicts with installed package(s): > postgresql-client-8.4.8 > > They install files into the same place. > You may want to stop build with Ctrl + C. > ===> Vulnerability check disabled, database not found > ===> License check disabled, port has not defined LICENSE > ===> Found saved configuration for postgresql-client-9.1.1_1 > => postgresql-9.1.1.tar.bz2 doesn't seem to exist in > /usr/ports/distfiles/postgresql. > => Attempting to fetch > ftp://ftp.se.postgresql.org/pub/databases/relational/postgresql/source/v9.1.1/postgresql-9.1.1.tar.bz2 > postgresql-9.1.1.tar.bz2 100% of 14 MB 1349 kBps 00m00s > > ===> postgresql-client-9.1.1_1 conflicts with installed package(s): > postgresql-client-8.4.8 > > They will not build together. > Please remove them first with pkg_delete(1). <pay > attention here > *** Error code 1 postgresql-client-8.4.8 make deinstall Tip. always run portaudit -F first. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Major version changes using portupgrade?
I'm trying to do a major version upgrade of postgres from 8.4 to 9.1. I've dumped the db and uninstalled the postgres-server port, and I'd like to use portupgrade to handle the client upgrade, since it has a number of dependencies that probably should be recompiled against the new client libs (and I'd like to keep the package's +REQUIRED_BY file properly updated anyway). I was expecting the following to work: sudo portupgrade -rf -o databases/postgresql91-client databases/postgresql84-client However, I'm running into a problem where the ports makefiles, and by extension portupgrade, are detecting that the two packages conflict, and so the 9.1 client won't even build[1]. This seems to be the sort of situation described by the -o example in the portupgrade man page, but I haven't been able to figure out how to make it work. Does anyone have any suggestions? Thanks! -- [1] [Updating the pkgdb in /var/db/pkg ... - 140 packages found (-1 +0) (...) done] ---> Upgrading 'postgresql-client-8.4.8' to 'postgresql-client-9.1.1_1' (databases/postgresql91-client) ---> Building '/usr/ports/databases/postgresql91-client' ===> Cleaning for postgresql-client-9.1.1_1 cd /usr/ports/databases/postgresql91-client && make config; ===> postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They install files into the same place. You may want to stop build with Ctrl + C. ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE ===> Found saved configuration for postgresql-client-9.1.1_1 => postgresql-9.1.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/postgresql. => Attempting to fetch ftp://ftp.se.postgresql.org/pub/databases/relational/postgresql/source/v9.1.1/postgresql-9.1.1.tar.bz2 postgresql-9.1.1.tar.bz2 100% of 14 MB 1349 kBps 00m00s ===> postgresql-client-9.1.1_1 conflicts with installed package(s): postgresql-client-8.4.8 They will not build together. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. *** Error code 1 Stop in /usr/ports/databases/postgresql91-client. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20111202-57604-1bstor4-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=postgresql-client-8.4.8 UPGRADE_PORT_VER=8.4.8 make ** Fix the problem and try again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade -P does not 'su'?
Hello. I'd like to install a port with 'portinstall -P' from a non-root user and it requires an obvious dependency I already have built to be reused. But portinstall doesn't seem to brace it into the 'su root -c': $ portinstall -vpP devel/p5-Test-Class [..] ---> Installing 'p5-Module-Build-0.3800_1' from a package ---> Installation of p5-Module-Build-0.3800_1 started at: Mon, 07 Nov 2011 15:57:56 +0400 ---> Installing the new version via the package lib/perl5/5.14.1/man/man3/inc::latest.3.gz: Can't create 'lib/perl5/5.14.1/man/man3/inc::latest.3.gz': Permission denied [..] ** Command failed [exit code 2]: /usr/bin/script -qa /tmp/portinstall2007-84470-1midf4x-0 /usr/bin/env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-Module-Build-0.3800_1 UPGRADE_PORT_VER=0.3800_1 /usr/sbin/pkg_add -f /usr/ports/packages/All/p5-Module-Build-0.3800_1.tbz It does use to be all ok with 'pkg_delete ... make install' sequence though. Any clues? ps. Same goes here about copying the obsoleted shared libraries to /usr/local/lib/compat/pkg -- Peter Vereshagin (http://vereshagin.org) pgp: A0E26627 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: portupgrade 2.4.9.3
On Wed, 2011-08-24 at 11:20 +, o...@aloha.com wrote: > I too am stuck in ruby-portupgrade swamp :-) > > After a fresh install of FreeBSD 8.2 I built potupgrade, then did a > portsnap and a portupgrade -a, in preparation to install Gnome2. When it > stopped I followed the instructions in UPDATING, but when I try to > upgrade portupgrade it fails because it cannot find the first server > listed and the only other one, ftp.freebsd.org, does not have pkgtools- > 2.4.9.3.tar.bz2. I verified by manual ftp connection. > > Do I just wait for ftp.freebsd.org to sync, or does someone need to do > something? > > Thanks for all that you do!! > For the record, this was fixed by Thursday, by Friday I had Gnome Power Tools and Gnome Office up and running. -- Gary Dunn, Honolulu Open Slate Project http://openslate.org http://www.facebook.com/garydunn808 http://e9erust.blogspot.com Twitter @garydunn808 Sent from Slate001 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
portupgrade 2.4.9.3
I too am stuck in ruby-portupgrade swamp :-) After a fresh install of FreeBSD 8.2 I built potupgrade, then did a portsnap and a portupgrade -a, in preparation to install Gnome2. When it stopped I followed the instructions in UPDATING, but when I try to upgrade portupgrade it fails because it cannot find the first server listed and the only other one, ftp.freebsd.org, does not have pkgtools- 2.4.9.3.tar.bz2. I verified by manual ftp connection. Do I just wait for ftp.freebsd.org to sync, or does someone need to do something? Thanks for all that you do!! Gary Dunn Honolulu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade to 2.4.9,2
On 08/23/11 11:11, Stanislav Sedov wrote: Are you sure you have the latest one (2.4.9.2_2,2). If not, you can grab it from here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portupgrade/ (the page has a small "download as a tarball" link at the bottom). You are right: I had just "csupped", and saw a portupgrade update, but it was not _2. Probably it.cvsup.freebsd.org is a little behind :-) Let me know if it works! For pkgdb, so far, so fine. I'm still getting "stack level too deep" (see other post), but this is not on all boxes and I'm investigating it. Thanks a lot. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade to 2.4.9,2
This ruby+portupgrade upgrade seems to be quite a mess. My systems fetch new ports tree nightly and I upgrade during the day when I have some spare time. So, this morning my systems had the new ruby versions and the UPDATING instruction, but not the new portupgrade port version (not that it had helped, but anyway). So, portupgrade -fr lang/ruby18 failed. Right now, I've got one system (the less critical one) upgraded with the latest and portupgrade is still failing. The other I backed down to ruby18 and portupgrade-2.4.8_1,2 and that works. Information from the upgraded system: # pkg_info -Ia | egrep 'ruby|portupgrade' portupgrade-2.4.9.2_2,2 FreeBSD ports/packages administration and management tool s ruby-1.9.2.290,1 An object-oriented interpreted scripting language ruby19-bdb-0.6.6 Ruby interface to Sleepycat's Berkeley DB revision 2 or lat Here's an example failure output. I get the same errors whatever port I try to upgrade.. # portupgrade -f portupgrade-2.4.9.2_2,2 ---> Session started at: Tue, 23 Aug 2011 11:10:02 +0200 ---> ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! ports-mgmt/portupgrade (portupgrade-2.4.9.2_2,2) (can't modify frozen string) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ---> Saving the results to '/var/log/portupgrade.results' ** Failed to save the results: undefined method `install_data' for # ---> Session ended at: Tue, 23 Aug 2011 11:10:08 +0200 (consumed 00:00:05) Regards, Andréas On Tue, 23 Aug 2011 11:00:48 +0200, Andrea Venturoli wrote: > On 08/23/11 09:58, Stanislav Sedov wrote: > >> On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturoli mentioned: >> >>> On 08/21/11 08:26, n dhert wrote: >>> >>>> I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2< needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: >>> I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for # >> Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. > > Not really. > > I tried "portupgrade -R portupgrade", but still had a messed-up system. > Since I don't use Ruby for much and had only portupgrade and libchk > using it, I wiped them all and reinstalled portupgrade from scratch. > This also reinstalled ruby. > I'm still getting "undefined method `map'..." when I run pkgdb, however. > >> # pkg_info -r portupgrade* Information for portupgrade-2.4.9.2,2: Depends on: Dependency: libyaml-0.1.4_1 Dependency: openssl-1.0.0_5 Dependency: pkg-config-0.25_1 Dependency: libffi-3.0.9 Dependency: ruby-1.9.2.290,1 > Sorry for the inconvinences! > > You're welcome, I appreciate your work and help. > > bye & Thanks > av. > ___ > freebsd-questions@free> freebsd.org/mailman/listinfo > tions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org [2]" Links: -- [1] mailto:m...@netfence.it [2] mailto:freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade to 2.4.9,2
On Tue, 23 Aug 2011 11:00:48 +0200 Andrea Venturoli mentioned: > On 08/23/11 09:58, Stanislav Sedov wrote: > > On Sun, 21 Aug 2011 15:18:28 +0200 > > Andrea Venturoli mentioned: > > > >> On 08/21/11 08:26, n dhert wrote: > >>> I did a portupgrade on a freebsd 8.2-RELEASE > >>> of the portupgrade program itself > >>> portupgrade-2.4.8_1,2< needs updating (index has 2.4.9,2) > >>> (that upgraded also ruby to 1.9: > >> > >> I did the same on some boxes and I'm having a lot of troubles too... > >> > >> # pkgdb -L > >> Look for lost dependencies: > >> undefined method `map' for # > >> > > > > Hi! > > > > Can you, please, try the portupgrade version from the ports? > > It should fix those issues. > > Not really. > > I tried "portupgrade -R portupgrade", but still had a messed-up system. > Since I don't use Ruby for much and had only portupgrade and libchk > using it, I wiped them all and reinstalled portupgrade from scratch. > This also reinstalled ruby. > I'm still getting "undefined method `map'..." when I run pkgdb, however. > Hi! Are you sure you have the latest one (2.4.9.2_2,2). If not, you can grab it from here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portupgrade/ (the page has a small "download as a tarball" link at the bottom). Let me know if it works! Thanks! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgpIFzfzVWD0P.pgp Description: PGP signature
Re: upgrade of portupgrade to 2.4.9,2
On 08/23/11 09:58, Stanislav Sedov wrote: On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturoli mentioned: On 08/21/11 08:26, n dhert wrote: I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2< needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: I did the same on some boxes and I'm having a lot of troubles too... # pkgdb -L Look for lost dependencies: undefined method `map' for # Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Not really. I tried "portupgrade -R portupgrade", but still had a messed-up system. Since I don't use Ruby for much and had only portupgrade and libchk using it, I wiped them all and reinstalled portupgrade from scratch. This also reinstalled ruby. I'm still getting "undefined method `map'..." when I run pkgdb, however. # pkg_info -r portupgrade\* Information for portupgrade-2.4.9.2,2: Depends on: Dependency: libyaml-0.1.4_1 Dependency: openssl-1.0.0_5 Dependency: pkg-config-0.25_1 Dependency: libffi-3.0.9 Dependency: ruby-1.9.2.290,1 Sorry for the inconvinences! You're welcome, I appreciate your work and help. bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade of portupgrade to 2.4.9,2
On Sun, 21 Aug 2011 15:18:28 +0200 Andrea Venturoli mentioned: > On 08/21/11 08:26, n dhert wrote: > > I did a portupgrade on a freebsd 8.2-RELEASE > > of the portupgrade program itself > > portupgrade-2.4.8_1,2<needs updating (index has 2.4.9,2) > > (that upgraded also ruby to 1.9: > > I did the same on some boxes and I'm having a lot of troubles too... > > # pkgdb -L > Look for lost dependencies: > undefined method `map' for # > Hi! Can you, please, try the portupgrade version from the ports? It should fix those issues. Sorry for the inconvinences! -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments pgp0hdEIsQdvG.pgp Description: PGP signature
Re: upgrade of portupgrade to 2.4.9,2
On 08/21/11 08:26, n dhert wrote:
I did a portupgrade on a freebsd 8.2-RELEASE
of the portupgrade program itself
portupgrade-2.4.8_1,2<needs updating (index has 2.4.9,2)
(that upgraded also ruby to 1.9:
I did the same on some boxes and I'm having a lot of troubles too...
# pkgdb -L
Look for lost dependencies:
undefined method `map' for #
# libchk
/usr/local/sbin/libchk:96: formal argument cannot be a global variable
|$strict|
^
/usr/local/sbin/libchk:100: formal argument cannot be a global variable
|$detailed|
^
# portupgrade -Rf libchk
[Gathering depends for sysutils/libchk ... done]
[Exclude up-to-date packages . done]
---> Reinstalling 'libchk-1.10.1' (sysutils/libchk)
---> Building '/usr/ports/sysutils/libchk'
===> Cleaning for libchk-1.10.1
===> License check disabled, port has not defined LICENSE
===> Extracting for libchk-1.10.1
=> SHA256 Checksum OK for libchk-1.10.1.tar.bz2.
===> libchk-1.10.1 depends on file: /usr/local/bin/ruby19 - found
===> Patching for libchk-1.10.1
===> libchk-1.10.1 depends on file: /usr/local/bin/ruby19 - found
===> libchk-1.10.1 depends on file: /usr/local/bin/ruby19 - found
===> Configuring for libchk-1.10.1
===> Building for libchk-1.10.1
Warning: Object directory not changed from original
/usr/ports/sysutils/libchk/work/libchk-1.10.1
gzip -cn libchk.1 > libchk.1.gz
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'libchk-1.10.1'
[Updating the pkgdb in /var/db/pkg ... - 361 packages
found (-1 +0) (...) done]
---> Installing the new version via the port
===> Installing for libchk-1.10.1
===> libchk-1.10.1 depends on file: /usr/local/bin/ruby19 - found
===> Generating temporary packing list
install -o root -g wheel -m 555 libchk.rb /usr/local/sbin/libchk
install -o root -g wheel -m 444 libchk.1.gz /usr/local/man/man1
===> Registering installation for libchk-1.10.1
===> Cleaning for libchk-1.10.1
---> Cleaning out obsolete shared libraries
[Updating the pkgdb in /var/db/pkg ... - 362 packages
found (-0 +1) . done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
- ["ruby-1.9.2.290,1"] (["ruby-1.9.2.290,1"]: 1.9.2.290,1"]:
Not in due form: '[_][,]'.)
- ["openssl-1.0.0_5"] (["openssl-1.0.0_5"]: 1.0.0_5"]: Not in
due form: '[_][,]'.)
- ["libyaml-0.1.4_1"] (["libyaml-0.1.4_1"]: 0.1.4_1"]: Not in
due form: '[_][,]'.)
- ["perl-5.8.9_5"] (["perl-5.8.9_5"]: 5.8.9_5"]: Not in due
form: '[_][,]'.)
- ["makedepend-1.0.3,1"] (["makedepend-1.0.3,1"]: 1.0.3,1"]:
Not in due form: '[_][,]'.)
- ["pkg-config-0.25_1"] (["pkg-config-0.25_1"]: 0.25_1"]: Not
in due form: '[_][,]'.)
- ["libiconv-1.13.1_1"] (["libiconv-1.13.1_1"]: 1.13.1_1"]: Not
in due form: '[_][,]'.)
- ["m4-1.4.16,1"] (["m4-1.4.16,1"]: 1.4.16,1"]: Not in due
form: '[_][,]'.)
- ["p5-Locale-gettext-1.05_3"] (["p5-Locale-gettext-1.05_3"]:
1.05_3"]: Not in due form: '[_][,]'.)
(I think the ignored packages should have been reinstalled... however
this was only a try at fixing the previous error).
I also issued "portsdb -uU" *after* the portupgrade update, but to no avail.
bye
av.
P.S. This is on 7.3/amd64 and 8.1/i386.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
upgrade of portupgrade to 2.4.9,2
I did a portupgrade on a freebsd 8.2-RELEASE of the portupgrade program itself portupgrade-2.4.8_1,2 < needs updating (index has 2.4.9,2) (that upgraded also ruby to 1.9: ... ===> Cleaning for ruby-1.9.2.290,1 ===> Cleaning for ruby19-bdb-0.6.6 ===> Cleaning for libffi-3.0.9 ===> Cleaning for libyaml-0.1.4_1 ===> Cleaning for portupgrade-2.4.9,2 ) After the portupgrade finished, I did # pkgdb -F ---> Checking the package registry database Duplicated origin: databases/ruby-bdb - ruby18-bdb-0.6.6 ruby19-bdb-0.6.6 Unregister any of them? [no] yes Unregister ruby18-bdb-0.6.6 keeping the installed files intact? [no] yes -> ruby19-bdb-0.6.6 is kept. --> Saving the ruby18-bdb-0.6.6's +CONTENTS file as /var/db/pkg/ruby19-bdb-0.6 .6/+CONTENTS.ruby18-bdb-0.6.6 --> Unregistering ruby18-bdb-0.6.6 --> Done. [Updating the pkgdb in /var/db/pkg ... - 70 packages found (- 1 +0) (...) done] Stale dependency: portupgrade-2.4.9,2 -> ruby18-bdb-0.6.6 (databases/ruby-bdb): undefined method `map' for # # pkgdb -F ---> Checking the package registry database Stale dependency: portupgrade-2.4.9,2 -> ruby18-bdb-0.6.6 (databases/ruby-bdb): undefined method `map' for # So it seems portupgrade does not use ruby 1.9, but I already unregistered it How to un-unregister that, or how to make portugprade use ruby 1.9 ? There's nothing in /usr/ports/UPDATING about that.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On 10/07/2011 14:02, Jerry wrote: On Sun, 10 Jul 2011 00:35:28 -0400 b. f. articulated: This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. Reading through the archives, several years worth, it appears that this is one of the most frequently asked questions. Many users, both new (obviously) and some not so new get confused as to what is the proper tag to use for each branch; ie "Stable" "Current", etc.Maybe there should be some way to make it easier to understand. For example: I was one of them until I discovered that googling "FreeBSD tags" leads straight to http://www.freebsd.org/doc/handbook/cvs-tags.html Eg RELENG_8 The line of development for FreeBSD-8.X, also known as FreeBSD 8-STABLE RELENG_8_2 The release branch for FreeBSD-8.2, used only for security advisories and other critical fixes. ... RELENG_8_2_0_RELEASE FreeBSD 8.2 Release Chris 8.2-RELEASE: original release of code sans any updates, etc. 8.2-STABLE: released version plus security updates 8.2-CURRENT: All updates, security& otherwise to the original version ?-CURRENT: The absolute latest release of FreeBSD irregardless of what version it is. Anyway, it is just a suggestion. In any case I think it might be easier for some to comprehend. Anything that eliminates confusion is a plus. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
> On Sun, 10 Jul 2011 00:35:28 -0400 > > b. f. articulated: > > This is the tag that you would use on src collections to update your > > base system sources (usually in /usr/src) to 8-STABLE. You would use > > RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for > > 8.2-RELEASE, and so on. > > Reading through the archives, several years worth, it appears that this > is one of the most frequently asked questions. Many users, both new > (obviously) and some not so new get confused as to what is the proper > tag to use for each branch; ie "Stable" "Current", etc.Maybe there > should be some way to make it easier to understand. For example: > > 8.2-RELEASE: original release of code sans any updates, etc. > > 8.2-STABLE: released version plus security updates > > 8.2-CURRENT: All updates, security & otherwise to the original version > > ?-CURRENT: The absolute latest release of FreeBSD irregardless of what > version it is. > > Anyway, it is just a suggestion. In any case I think it might be easier > for some to comprehend. Anything that eliminates confusion is a plus. I have 34 years experience as a Data Systems technician, system admin, developer, and tech writer, yet I till won't claim I know everything, so please don't flame me. Constructive, polite criticism is welcome. I began my career before Unix or MicroSucks even existed. It is a misnomer to attach a release number to current or stable. CURRENT is called HEAD in source code control vernacular. CURRENT's "number" is transient. It is often incorrectly referred to as 9. Please refrain from such usage. It is technically incorrect and confuses users who have no knowledge of source code control. Same goes for STABLE. In my opinion, the real confusion is in ascertaining what you SHOULD be using. If you want to run FreeBSD, KDE, gnome, etc., as a PRODUCTION machine, yo should NOT be using CURRENT or STABLE. You should be installing a RELEASE on a TEST machine, verify that ALL your user applications have no showstopper anomales, and DEPLOY the release AFTER testing has given you a great dela of confidence in the software. You should JUMP from a release to the next release, using the testing and deployment mentioned. You WILL get security updates if you track a release, such as 8.2. But again, don't just update your sources and deploy. TEST it on a test machine, before exposing your end users to it. This is referred to as PROFESSIONALISM. The ONLY people that should be tracking STABLE or CURRENT are the people who DON'T need their hand held for system administration. If you violate this protocol, you will be taking developers time away from development to TRAIN you in system admin. PLEASE don't. Hope this helps and if it offends you, please take the time to think about it before you flame me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sun, 10 Jul 2011 00:35:28 -0400 b. f. articulated: > This is the tag that you would use on src collections to update your > base system sources (usually in /usr/src) to 8-STABLE. You would use > RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for > 8.2-RELEASE, and so on. Reading through the archives, several years worth, it appears that this is one of the most frequently asked questions. Many users, both new (obviously) and some not so new get confused as to what is the proper tag to use for each branch; ie "Stable" "Current", etc.Maybe there should be some way to make it easier to understand. For example: 8.2-RELEASE: original release of code sans any updates, etc. 8.2-STABLE: released version plus security updates 8.2-CURRENT: All updates, security & otherwise to the original version ?-CURRENT: The absolute latest release of FreeBSD irregardless of what version it is. Anyway, it is just a suggestion. In any case I think it might be easier for some to comprehend. Anything that eliminates confusion is a plus. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the "Reply-To" header. http://www.catb.org/~esr/faqs/smart-questions.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On 7/10/11, b. f. wrote: > On 7/9/11, Thomas D. Dean wrote: >> On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: > You could cheat, and neither upgrade your base system nor make the > changes I mentioned in my last message, but instead fool portupgrade > into thinking that you have a newer base system, by setting UNAME_R to Sorry, that should be "UNAME_r", with a lower-case "r", above. But, as I wrote, using that workaround is probably not a good idea. > something like "8.2-STABLE" in your environment when you call > portupgrade, but you are bound to run into problems eventually by > lying in that way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On 7/9/11, Thomas D. Dean wrote: > On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: > >> occasionally trip over problems that will require intervention. (Note >> that in the section of the csup file that you reproduced in an earlier >> message, 'release-cvs' should be 'release=cvs'.) > > The '-' was a typo on my part. The machine I used for email is not the > machine I am updating. > > I am updating that machine, now. The supfile contains > *default release=cvs tag=RELENG_8 > > This should track 8-stable. Correct? This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. But src tags are not the same as ports tags. That is why they have separate example supfiles for the base system sources, and for ports. And that is also why they have the prominent warning in the base system example supfiles: ### # # DANGER! WARNING! LOOK OUT! VORSICHT! # # If you add any of the ports or doc collections to this file, be sure to # specify them with a "tag" value set to ".", like this: # # ports-all tag=. # doc-all tag=. # # If you leave out the "tag=." portion, CVSup will delete all of # the files in your ports or doc tree. That is because the ports and doc # collections do not use the same tags as the main part of the FreeBSD # source tree. # ### As far as I know, the ports collection has no tags for any stable branches, only tags made at the time of releases. So for ports, if you are running 8.2-RELEASE, you have three choices: (1) use RELEASE_8_2_0 if you want to stick with a snapshot of the ports tree taken at the time of the release, or (2) use "." if you want up-to-date ports, or (3) choose a specific snapshot of ports via date= instead of tag= (for details, see, for example, the csup(1) manpage.) > > After the build finishes, portupgrade should fetch from 8-stable. I'm not sure what you mean here. As I wrote before, you need to make some additional changes to ensure that portupgrade uses 8-stable packages if you have an 8.2-RELEASE base system. Just having a up-to-date ports tree and index isn't sufficient. However, if you replace your 8.2-RELEASE base system with a newer 8.2-STABLE or 8-STABLE base system, then portupgrade should fetch the 8-stable packages by default, without any additional changes. You could cheat, and neither upgrade your base system nor make the changes I mentioned in my last message, but instead fool portupgrade into thinking that you have a newer base system, by setting UNAME_R to something like "8.2-STABLE" in your environment when you call portupgrade, but you are bound to run into problems eventually by lying in that way. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: > occasionally trip over problems that will require intervention. (Note > that in the section of the csup file that you reproduced in an earlier > message, 'release-cvs' should be 'release=cvs'.) The '-' was a typo on my part. The machine I used for email is not the machine I am updating. I am updating that machine, now. The supfile contains *default release=cvs tag=RELENG_8 This should track 8-stable. Correct? After the build finishes, portupgrade should fetch from 8-stable. A slow, remote machine... tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
Thomas D. Dean wrote:
...
> For the most recent try, I have
>
> ...
> # OS_PATCHLEVEL: "" "-p8"
> # OS_PLATFORM:"i386" "amd64"
> # OS_PKGBRANCH: "7-current" "6.1-release"
> OS_RELEASE="8-STABLE"
> OS_BRANCH="STABLE"
> OS_PKGBRANCH="8-stable"
The comments above were not intended as an invitation to try to define
these constants here, but merely describe typical values that the
constants may have. The constants are computed from parsing your
'uname -rm' output in $LOCALBASE/$RUBY_SITELIBDIR/pkgtools.rb (usually
/usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb), so you cannot set them
in pkgtools.conf. They were only mentioned so that users would know
that they were available for defining other procedures and variables
(for an example, see below).
>
> # Useful predefined functions:
> #
> # localbase()
> #Returns LOCALBASE.
> ...
>
> But, portupgrade still tries to fetch from 8.2-release.
If you are running 8.2-RELEASE, and yet wish to obtain "8-stable"
packages (which are actually built on recent versions of 8.1-STABLE,
with recent versions of the ports tree), then set PKG_SITES
appropriately in pkgtools.conf. In this case, I think (untested) that
you could substitute
sprintf('%s/pub/FreeBSD/ports/%s/packages-%s-stable/',
ENV['PACKAGEROOT'] || 'ftp://ftp.FreeBSD.org', OS_PLATFORM, OS_MAJOR)
for the default
pkg_site_mirror(root)
in PKG_SITES. (It might be better to upgrade your base system to
8-STABLE, in which case the defaults will be correct without any need
for these changes, and other problems will also be fixed).
>
> If I want to use binary ports it looks like I need to zap the ports tree
> and recreate it with portsnap.
This should not be necessary. You should be able to use any method to
update the tree (anonymous cvs, csup/cvsup, portsnap, http/ftp, rsync,
ctm, etc.). Of course, if your tree and index file do not correspond
to the version of the binary packages that you want to use, you will
occasionally trip over problems that will require intervention. (Note
that in the section of the csup file that you reproduced in an earlier
message, 'release-cvs' should be 'release=cvs'.)
PKG_SITES will only be used by the ports-mgmt/portupgrade scripts; if
you want to use pkg_add(1) manually, and obtain the 8-stable packages,
then you should define PACKAGESITE in your environment, or provide a
full URL. The ports-mgmt/portupgrade scripts also respect
PACKAGESITE, which will override PACKAGEROOT and PKG_SITES in those
scripts.
b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 21:45 +0200, Polytropon wrote: > > If I understood everything correctly, CVS (csup) and portsnap > do both follow "the one tree" which gets frequently updated, > and by the tag specified above you'll always get the current > version of the tree. Getting older versions (e. g. the RELEASE > tree) involves specifying a different tag, or loading it from > the installation media directly. > > The difference is that changes in the ports tree are reflected > much faster in the CVS method than in the portsnap approach, > which may "lag" a bit. However, portsnap seems to work faster > and to perform better than CVS. It's also worth mentioning that > it seems to fit better to the "building cycle" of the -stable > ports to become precompiled packages (that you request using > the -PP parameter, similar to the use of pkg_add -r in case of > installation instead of update). > > But if you require the most recent ports tree, using CVS seems > to be the better method. As you're updating binary, but with > using the ports tree (portupgrade relies on that, pkg_add for > example doesn't), you should make sure to always have the > current version if you follow the stable OS branch. > I have always built ports from the source. I decided to try binary ports for things I have not modified. I cannot seem to get portupgrade to use the definitions I set in etc/pkgtools.conf. For the most recent try, I have ... # OS_PATCHLEVEL: "" "-p8" # OS_PLATFORM:"i386" "amd64" # OS_PKGBRANCH: "7-current" "6.1-release" OS_RELEASE="8-STABLE" OS_BRANCH="STABLE" OS_PKGBRANCH="8-stable" # Useful predefined functions: # # localbase() #Returns LOCALBASE. ... But, portupgrade still tries to fetch from 8.2-release. If I want to use binary ports it looks like I need to zap the ports tree and recreate it with portsnap. tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 09 Jul 2011 12:32:12 -0700, Thomas D. Dean wrote: > On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote: > > Sorry to answer my own post. > > The packages that are out-of-date on the system I was updating are in > relationship to 8.2-release. > > A couple days ago, I cvsup'd the port tree with > *default release-cvs tag=. > ports-all > > Today, > portsnap fetch extract > ... > portsnap fetch update > ... > portupgrade -PPRva > > Does the portsnap update the port tree relative to 8.2-release or > 8-stable? Or, did cvsup get ports from 8-stable? > > Looks like 8-stable. > > 8-stablem4-1.4.16,1.tbz > 8.2-release m4-1.4.15,1.tbz > > Anyway, I can get there from here If I understood everything correctly, CVS (csup) and portsnap do both follow "the one tree" which gets frequently updated, and by the tag specified above you'll always get the current version of the tree. Getting older versions (e. g. the RELEASE tree) involves specifying a different tag, or loading it from the installation media directly. The difference is that changes in the ports tree are reflected much faster in the CVS method than in the portsnap approach, which may "lag" a bit. However, portsnap seems to work faster and to perform better than CVS. It's also worth mentioning that it seems to fit better to the "building cycle" of the -stable ports to become precompiled packages (that you request using the -PP parameter, similar to the use of pkg_add -r in case of installation instead of update). But if you require the most recent ports tree, using CVS seems to be the better method. As you're updating binary, but with using the ports tree (portupgrade relies on that, pkg_add for example doesn't), you should make sure to always have the current version if you follow the stable OS branch. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote: Sorry to answer my own post. The packages that are out-of-date on the system I was updating are in relationship to 8.2-release. A couple days ago, I cvsup'd the port tree with *default release-cvs tag=. ports-all Today, portsnap fetch extract ... portsnap fetch update ... portupgrade -PPRva Does the portsnap update the port tree relative to 8.2-release or 8-stable? Or, did cvsup get ports from 8-stable? Looks like 8-stable. 8-stablem4-1.4.16,1.tbz 8.2-release m4-1.4.15,1.tbz Anyway, I can get there from here Thanks. tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 20:47 +0200, Polytropon wrote: > On Sat, 09 Jul 2011 11:33:00 -0700, Thomas D. Dean wrote: > > > /usr/bin/fetch -v > > 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' > > looking up ftp.FreeBSD.org > > connecting to ftp.FreeBSD.org:21 > > fetch: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: > > File unavailable (e.g., file not found, no access) > > It's quite simple if you investigate the content of the FTP server. :-) > > Doesn't work: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz > > Works: > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz > > Just change "packages-8-STABLE" to "packages-8-stable" and try again. > > > Yes. My error. I did not completely remove 8.2-RELEASE when I edited pkgtools.conf the 2nd time. I introduced this error when I typed the fetch command. Sorry. My original problem still exists: portupgrade fails with any out-of-date package. I should have sent the console output the first time... I restored pkgtools.conf to the original version, from the initial installation. Here is the output of the portupgrade attempt: > uname -a FreeBSD toshiba.tddhome 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > portupgrade --version portupgrade 2.4.8 > portupgrade -PPv m4 ---> Session started at: Sat, 09 Jul 2011 11:55:55 -0700 ---> Checking for the latest package of 'devel/m4' ---> Found a package of 'devel/m4': /usr/ports/packages/All/m4-1.4.15,1.tbz (m4-1.4.15,1) ---> Fetching the package(s) for 'm4-1.4.16,1' (devel/m4) ---> Fetching m4-1.4.16,1 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org//pub/FreeBSD/ports/i386/packages-8.2-release/ ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.txz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.txz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.txz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.txz ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tgz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tgz ** Failed to fetch m4-1.4.16,1 ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! m4-1.4.16,1 (fetch error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ---> Fetching the latest package(s) for 'm4' (devel/m4) ---> Fetching m4 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org//pub/FreeBSD/ports/i386/packages-8.2-release/ ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgradeyQuqTSRB/m4.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/Latest/m4.tbz' /var/tmp/portupgradeyQuqTSRB/m4.tbz 100% of 185 kB 144 kBps ---> Downloaded as m4.tbz ---> Identifying the package /var/tmp/portupgradeyQuqTSRB/m4.tbz ---> Saved as /usr/ports/packages/All/m4-1.4.15,1.tbz ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) + m4@ ---> Packages processed: 1 done, 0 ignored, 0 skipped and 0 failed ---> Found a package of 'devel/m4': /usr/ports/packages/All/m4-1.4.15,1.tbz (m4-1.4.15,1) ---> Located a package version 1.4.15,1 (/usr/ports/packages/All/m4-1.4.15,1.tbz) ---> ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! devel/m4 (m4-1.4.15,1)(package not found) ---> Packa
Re: Portupgrade Package Question
On Sat, 09 Jul 2011 11:33:00 -0700, Thomas D. Dean wrote: > > /usr/bin/fetch -v > 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' > looking up ftp.FreeBSD.org > connecting to ftp.FreeBSD.org:21 > fetch: > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: > File unavailable (e.g., file not found, no access) It's quite simple if you investigate the content of the FTP server. :-) Doesn't work: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz Works: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz Just change "packages-8-STABLE" to "packages-8-stable" and try again. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 14:15 -0400, Chris Brennan wrote: > On 7/9/2011 1:14 PM, Thomas D. Dean wrote: > > As root, I attempted to use > > portupgrade -PPRv m4 > > which attempted to access > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz > > but failed - File unavailable (e.g. file not found, no access) > > > > I changed etc/pkgtools.conf > > OS_PKGBRANCH="8-STABLE" > > and > > portupgrade -PPRv m4 > > which attempted to access > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz > > failed with the same message. > > > > I can ftp either file. > > > > I get the same error with any out-of-date port. > > > > What am I doing wrong? > > > Have you made sure you updated ports? 'portsnap fetch extract' should be > sufficient. > > Sorry, I did not reply to the list. Yes, I did update ports. > /usr/bin/fetch -v 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' looking up ftp.FreeBSD.org connecting to ftp.FreeBSD.org:21 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: File unavailable (e.g., file not found, no access) tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Portupgrade Package Question
On 7/9/2011 1:14 PM, Thomas D. Dean wrote: > As root, I attempted to use > portupgrade -PPRv m4 > which attempted to access > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz > but failed - File unavailable (e.g. file not found, no access) > > I changed etc/pkgtools.conf >OS_PKGBRANCH="8-STABLE" > and > portupgrade -PPRv m4 > which attempted to access > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz > failed with the same message. > > I can ftp either file. > > I get the same error with any out-of-date port. > > What am I doing wrong? Have you made sure you updated ports? 'portsnap fetch extract' should be sufficient. -- > Chris Brennan > -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? > http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ > GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) signature.asc Description: OpenPGP digital signature
Portupgrade Package Question
As root, I attempted to use portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz but failed - File unavailable (e.g. file not found, no access) I changed etc/pkgtools.conf OS_PKGBRANCH="8-STABLE" and portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz failed with the same message. I can ftp either file. I get the same error with any out-of-date port. What am I doing wrong? tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Trying To Do A portupgrade On 8-Stable
On 6/28/2011 2:46 PM, Frank Shute said this: > On Tue, Jun 28, 2011 at 01:37:22PM -0500, Tim Daneliuk wrote: >> >> ... and the gstreamer upgrade blows up because of this: >> >> /usr/local/bin/g-ir-scanner: not found >> >> >> Ideas? > > On my machine: > > $ pkg_info -W /usr/local/bin/g-ir-scanner > /usr/local/bin/g-ir-scanner was installed by package > gobject-introspection-0.9.12_1 > > So I suggest you do: > > # portupgrade -fv gobject-introspection > > > Regards, > That did it, thanks! -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Trying To Do A portupgrade On 8-Stable
On Tue, Jun 28, 2011 at 01:37:22PM -0500, Tim Daneliuk wrote: > > ... and the gstreamer upgrade blows up because of this: > > /usr/local/bin/g-ir-scanner: not found > > > Ideas? On my machine: $ pkg_info -W /usr/local/bin/g-ir-scanner /usr/local/bin/g-ir-scanner was installed by package gobject-introspection-0.9.12_1 So I suggest you do: # portupgrade -fv gobject-introspection Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Trying To Do A portupgrade On 8-Stable
... and the gstreamer upgrade blows up because of this: /usr/local/bin/g-ir-scanner: not found Ideas? -- Tim Daneliuk tun...@tundraware.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?(SOLVED)
> startx command not found :(, no bash > ran > # pkg_add -r bash > # pkg_add -r xfce4 > > did not succeed, now ran to ports > # cd /usr/ports/x11-wm/xfce4 > # make install clean > > and am stuck here. Hopefully this gets me back on my feet. > Otherwise, it has been a big exercise :) and definitely I will learn > from it. Thank you all for input/advice/comments & suggestions. I am back on my feet with new xfce 4.8 now installing via ports sed -i 's/openoffice/libreoffice/g' will take a while but I am back in business. Sorry for the noise and for for shooting myself in the foot. The learning the removing and stuff like MasterCard commercials : ``Priceless``! Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, May 6, 2011 at 9:59 PM, Antonio Olivares wrote: > On Fri, May 6, 2011 at 8:43 PM, Warren Block wrote: >> On Fri, 6 May 2011, Antonio Olivares wrote: >>> >>> On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares >>> >>> Sorry for TOP POSTING :(, but do I run >>> # portmaster -a -f -D >>> >>> and do an in place update of all ports? >>> is this the recommended way or nuking and rebuilding? >> >> After the attempt to install every port, I'd remove all, update the ports >> tree, and install only the needed ports. Right now you may have many >> installed that are not just unneeded but unwanted. >> > > I am following the advice given in man portmaster: > > > Using portmaster to do a complete reinstallation of all your ports: > 1. portmaster --list-origins > ~/installed-port-list > > Print only the ports that have available updates. This can be used as an > alias in your shell. Be sure to fix the line wrapping appropriately. > portmaster -L | > egrep -B1 '(ew|ort) version|Aborting|installed|dependencies| > IGNORE|marked|Reason:|MOVED|deleted|exist|update' | grep -v '^--' > > 2. Update your ports tree > 3. portmaster -ty --clean-distfiles > 4. portmaster --check-port-dbdir > 5. portmaster -Faf > 6. pkg_delete -a > 7. rm -rf /usr/local/lib/compat/pkg > 8. Back up any files in /usr/local you wish to save, > such as configuration files in /usr/local/etc > 9. Manually check /usr/local and /var/db/pkg > to make sure that they are really empty > 10. Re-install portmaster > 11. portmaster `cat ~/installed-port-list` > > > Mostly everything is step 11 :) Will come back hopefully with a fully > updated machine. > > Regards, > > Antonio > startx command not found :(, no bash ran # pkg_add -r bash # pkg_add -r xfce4 did not succeed, now ran to ports # cd /usr/ports/x11-wm/xfce4 # make install clean and am stuck here. Hopefully this gets me back on my feet. Otherwise, it has been a big exercise :) and definitely I will learn from it. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, May 6, 2011 at 8:43 PM, Warren Block wrote: > On Fri, 6 May 2011, Antonio Olivares wrote: >> >> On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares >> >> Sorry for TOP POSTING :(, but do I run >> # portmaster -a -f -D >> >> and do an in place update of all ports? >> is this the recommended way or nuking and rebuilding? > > After the attempt to install every port, I'd remove all, update the ports > tree, and install only the needed ports. Right now you may have many > installed that are not just unneeded but unwanted. > I am following the advice given in man portmaster: Using portmaster to do a complete reinstallation of all your ports: 1. portmaster --list-origins > ~/installed-port-list Print only the ports that have available updates. This can be used as an alias in your shell. Be sure to fix the line wrapping appropriately. portmaster -L | egrep -B1 '(ew|ort) version|Aborting|installed|dependencies| IGNORE|marked|Reason:|MOVED|deleted|exist|update' | grep -v '^--' 2. Update your ports tree 3. portmaster -ty --clean-distfiles 4. portmaster --check-port-dbdir 5. portmaster -Faf 6. pkg_delete -a 7. rm -rf /usr/local/lib/compat/pkg 8. Back up any files in /usr/local you wish to save, such as configuration files in /usr/local/etc 9. Manually check /usr/local and /var/db/pkg to make sure that they are really empty 10. Re-install portmaster 11. portmaster `cat ~/installed-port-list` Mostly everything is step 11 :) Will come back hopefully with a fully updated machine. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, 6 May 2011, Antonio Olivares wrote: On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares Sorry for TOP POSTING :(, but do I run # portmaster -a -f -D and do an in place update of all ports? is this the recommended way or nuking and rebuilding? After the attempt to install every port, I'd remove all, update the ports tree, and install only the needed ports. Right now you may have many installed that are not just unneeded but unwanted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, 6 May 2011 13:57:01 -0500, Antonio Olivares wrote: > Sorry for TOP POSTING :(, but do I run > # portmaster -a -f -D > > and do an in place update of all ports? > is this the recommended way or nuking and rebuilding? In case you did already remove all installed ports, you need to install them (portinstall command). You can do a port upgrade only for ports that are installed, as the system doesn't keep a "which ports have been installed before they got removed" database automatically. You need to use portmaster, the "make install" framework or pkg_add -r to install the ports you want to have on your system. I hope I did understand your statement correctly. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, May 6, 2011 at 1:52 PM, Antonio Olivares wrote: > Warren, > > Sorry to ask, but what does one run after we run > # portmaster -na > > I have cleared all questions and am ready to update, what magical > command will do it? > > Thanks, > > Antonio > > On Fri, May 6, 2011 at 12:54 PM, Warren Block wrote: >> On Fri, 6 May 2011, Polytropon wrote: >> >>> Maybe it's much better if you utilize the ports infra- >>> structure. >>> >>> # cd /var/db/pkg >>> # pkg_delete -fad >>> >>> or >>> >>> # pkg_delete -f * >> >> These are both equivalent to >> # pkg_delete -a >> > Sorry for TOP POSTING :(, but do I run # portmaster -a -f -D and do an in place update of all ports? is this the recommended way or nuking and rebuilding? Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
Warren, Sorry to ask, but what does one run after we run # portmaster -na I have cleared all questions and am ready to update, what magical command will do it? Thanks, Antonio On Fri, May 6, 2011 at 12:54 PM, Warren Block wrote: > On Fri, 6 May 2011, Polytropon wrote: > >> Maybe it's much better if you utilize the ports infra- >> structure. >> >> # cd /var/db/pkg >> # pkg_delete -fad >> >> or >> >> # pkg_delete -f * > > These are both equivalent to > # pkg_delete -a > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, 6 May 2011, Polytropon wrote: Maybe it's much better if you utilize the ports infra- structure. # cd /var/db/pkg # pkg_delete -fad or # pkg_delete -f * These are both equivalent to # pkg_delete -a ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, May 6, 2011 at 12:09 PM, Polytropon wrote: > On Fri, 6 May 2011 11:36:07 -0500, Antonio Olivares > wrote: >> This is what I am running now ATM >> >> # cd /usr/ports/ >> # make clean build deinstall install >> >> Will it install all the ports? or only the ones that are installed? > > Oh, I've never tried that... "install all ports"... I even > doubt this is possible. > > If you want to intendedly deinstall all _except_ the OS > software, you can do this: > > # cd /usr/local > # rm -rf * > # mtree < /etc/mtree/BSD.local.dist > > It's worth mentioning that this is a very hard method. > Maybe it's much better if you utilize the ports infra- > structure. > > # cd /var/db/pkg > # pkg_delete -fad > > or > > # pkg_delete -f * > > This should remove all ports in a clean way. You can also > remove stuff from /usr/ports/distfiles and /usr/ports/packages. > > Then make sure you have updated your ports tree. In case > you also want an OS update, do it _now_ (i. e. prior to > dealing with ports). > > In case you keep using portupgrade (and therefore portinstall), > maybe in combination with pkg_add -r if you prefer - like > me :-) - installing binary packages, make sure that you > run BEFORE and AFTER each "big step", just to be sure > > # pkgdb -aF > > This keeps portinstall's own database in sync with what > you are doing on your system with other tools. Oh, and you > can _still_ use "make install" like installations directly > from the ports tree - no problem. > > Another "secret": Start with installing one of the bigger > software packages you need, as this will pull in many of > the dependencies, and you don't have to install those > first, by hand. If you want to compile, use gmencoder > for example, and select all options you need (remember > to do "make config-recursive" before "make install"). > > Sometimes, you'll find it's easier to begin with a new > software installation from scratch. Maybe this is a good > moment to do so. :-) > > And a sidenote: > > If you intend to use the packages you've build on a > different system (to install them there), use "make package", > or much easier with portupgrade or portinstall: use > the -p option. This will place precompiled (haha) > binary packages in /usr/ports/packages that you can > transfer to another system and install with them > with pkg_add there - VERY handy solution! > > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > I am trying out portmaster. Have stuck with command # portmaster -na > /tmp/portorder.txt but it is hanging there. Will go to lunch before doing anything. Then ready to proceed. Thanks, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, May 6, 2011 at 12:14 PM, Warren Block wrote: > On Fri, 6 May 2011, Antonio Olivares wrote: > >> This is what I am running now ATM >> >> # cd /usr/ports/ >> # make clean build deinstall install >> >> Will it install all the ports? or only the ones that are installed? > > It's going to try to install all 22,000 ports. That won't succeed due to > conflicts, but it may take a while to get there. Stopped it with CTRL+C and > > Quicker overall would be to read the Handbook ports chapter. You may also > find my Upgrading FreeBSD Ports article helpful: > > http://www.wonkity.com/~wblock/docs/html/portupgrade.html > Have run the suggested commands # portsnap fetch extract # portsnap fetch install the ports tree is updated. Now portmaster was not installed, installed it # cd /usr/ports/ports-mgmt/ # make install clean now I am running /usr/local/sbin/portmaster -L --index-only | egrep 'total install|versions|New version' and see the packages that need updating, but to update I am running: # portmaster -na > /tmp/portorder.txt and will get back after this is done to see how to proceed. Thanks, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, 6 May 2011, Antonio Olivares wrote: This is what I am running now ATM # cd /usr/ports/ # make clean build deinstall install Will it install all the ports? or only the ones that are installed? It's going to try to install all 22,000 ports. That won't succeed due to conflicts, but it may take a while to get there. Quicker overall would be to read the Handbook ports chapter. You may also find my Upgrading FreeBSD Ports article helpful: http://www.wonkity.com/~wblock/docs/html/portupgrade.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Fri, 6 May 2011 11:36:07 -0500, Antonio Olivares wrote: > This is what I am running now ATM > > # cd /usr/ports/ > # make clean build deinstall install > > Will it install all the ports? or only the ones that are installed? Oh, I've never tried that... "install all ports"... I even doubt this is possible. If you want to intendedly deinstall all _except_ the OS software, you can do this: # cd /usr/local # rm -rf * # mtree < /etc/mtree/BSD.local.dist It's worth mentioning that this is a very hard method. Maybe it's much better if you utilize the ports infra- structure. # cd /var/db/pkg # pkg_delete -fad or # pkg_delete -f * This should remove all ports in a clean way. You can also remove stuff from /usr/ports/distfiles and /usr/ports/packages. Then make sure you have updated your ports tree. In case you also want an OS update, do it _now_ (i. e. prior to dealing with ports). In case you keep using portupgrade (and therefore portinstall), maybe in combination with pkg_add -r if you prefer - like me :-) - installing binary packages, make sure that you run BEFORE and AFTER each "big step", just to be sure # pkgdb -aF This keeps portinstall's own database in sync with what you are doing on your system with other tools. Oh, and you can _still_ use "make install" like installations directly from the ports tree - no problem. Another "secret": Start with installing one of the bigger software packages you need, as this will pull in many of the dependencies, and you don't have to install those first, by hand. If you want to compile, use gmencoder for example, and select all options you need (remember to do "make config-recursive" before "make install"). Sometimes, you'll find it's easier to begin with a new software installation from scratch. Maybe this is a good moment to do so. :-) And a sidenote: If you intend to use the packages you've build on a different system (to install them there), use "make package", or much easier with portupgrade or portinstall: use the -p option. This will place precompiled (haha) binary packages in /usr/ports/packages that you can transfer to another system and install with them with pkg_add there - VERY handy solution! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, May 5, 2011 at 8:37 PM, Warren Block wrote: > On Thu, 5 May 2011, Antonio Olivares wrote: > >> Dear all, >> >> I was running FreeBSD 8.1 and am in the process of updating it >> following advice in handbook: >> >> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html >> >> ran >> # freebsd-update fetch >> # freebsd-update install >> >> # portupgrade -af >> >> # freebsd-update -r 8.2-RELEASE upgrade >> >> then >> >> # freebsd-update install >> >> Tried to do this: >> # portupgrade -f ruby >> # rm /var/db/pkg/pkgdb.db >> # portupgrade -f ruby18-bdb >> # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db >> # portupgrade -af >> >> Did not work correctly[too many customizations] and Tried again > > portupgrade is written in Ruby and uses ruby-bdb, so this may not work. -f > is of questionable value. Why not just cd to the port directories, and > 'make clean build deinstall install'? This is what I am running now ATM # cd /usr/ports/ # make clean build deinstall install Will it install all the ports? or only the ones that are installed? > >> # freebsd-update install >> >> and had nothing more to do :( >> >> I had many packages that need to be updated so I am running : >> >> # portupgrade -arRp > > -a is equivalent to -arR. And that's building packages, which is not > necessary unless you want to copy them to another machine. > >> will this prompt me for customizations? > > Options menus? Yes, the ports will ask on their own. If you use the -c or > -C options, portupgrade will do all of them at the start of the process. > Thanks, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
> Any suggestions to start over and get this done in a more efficient > manner. Thinking of nuking OpenOffice Done:) grullahighschool# cd openoffice.org-3 grullahighschool# ls Makefiledistinfofiles pkg-descr pkg-plist grullahighschool# make deinstall ===> Deinstalling for editors/openoffice.org-3 ===> Deinstalling openoffice.org-3.2.1 grullahighschool# > and installing LibreOffice. > Will do that now and then when that is done. > > Regards, > > Antonio > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, May 5, 2011 at 8:04 PM, Frank Shute wrote: > On Thu, May 05, 2011 at 05:50:28PM -0500, Antonio Olivares wrote: >> >> Dear all, >> >> I was running FreeBSD 8.1 and am in the process of updating it >> following advice in handbook: >> >> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html >> >> ran >> # freebsd-update fetch >> # freebsd-update install >> >> # portupgrade -af >> >> # freebsd-update -r 8.2-RELEASE upgrade >> >> then >> >> # freebsd-update install >> >> Tried to do this: >> # portupgrade -f ruby >> # rm /var/db/pkg/pkgdb.db >> # portupgrade -f ruby18-bdb >> # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db >> # portupgrade -af >> >> Did not work correctly[too many customizations] and Tried again >> >> # freebsd-update install >> >> and had nothing more to do :( >> >> I had many packages that need to be updated so I am running : >> >> # portupgrade -arRp >> >> will this prompt me for customizations? > > Yes it will. I usually use the -C flag of portupgrade when I'm > updating ports. This flag prompts you with all the options screens > before it does the update. That way you're not left with the upgrade > hanging half way through whilst it waits for you to configure the > options. > > As Polytropon says you can use the --batch flag if you know that you > don't want to change the default options. > >> >> Thanks in advance/advice/suggestions. I am taking the plunge a little >> further. Before I just installed and left it alone :( [except for a >> few packages that I wanted and ran/installed via ports ], now I am >> trying to learn more and setup the firewall. I set up the simple >> example setup by Polytropon and most is working. My freebsd version >> has moved to FreeBSD 8.2 >> >> >> >> [olivares@grullahighschool /usr/home/olivares]$ uname -a >> FreeBSD grullahighschool.rgccisd.org 8.2-RELEASE FreeBSD 8.2-RELEASE >> #0: Thu Feb 17 02:41:51 UTC 2011 >> r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >> >> >> Regards, >> >> Antonio > > Regards, > > -- > > Frank > > Contact info: http://www.shute.org.uk/misc/contact.html > > > I am *stuck*, here's what I get at the end: ** Listing the failed packages (-:ignored / *:skipped / !:failed) - devel/automake110 (marked as IGNORE) - devel/libltdl22 (marked as IGNORE) - net/samba3 (marked as IGNORE) ! devel/qt4-moc (qt4-moc-4.6.3) (bad C++ code) ! devel/qt4-uic (qt4-uic-4.6.3) (bad C++ code) ! devel/qt4-rcc (qt4-rcc-4.6.3) (bad C++ code) ! audio/faad (faad2-2.7_2,1)(unknown build error) ! x11-fonts/libFS (libFS-1.0.2) (unknown build error) ! net/openldap24-client (openldap-client-2.4.23)(unknown build error) ! security/libntlm (libntlm-1.1)(unknown build error) ! devel/libsigc++20 (libsigc++-2.2.7) (unknown build error) ! x11/babl (babl-0.1.2) (unknown build error) ! devel/gettext (gettext-0.18_1)(unknown build error) * misc/help2man (help2man-1.38.2_1) * net-p2p/libtorrent (libtorrent-0.12.6_1) * misc/iso-codes (iso-codes-3.17) * devel/popt (popt-1.14_1) ! graphics/OpenEXR (OpenEXR-1.6.1_2)(unknown build error) * devel/yasm (yasm-1.0.1_1) ! audio/libogg (libogg-1.2.0,4) (unknown build error) * security/libgpg-error (libgpg-error-1.8) * security/gnupg1 (gnupg-1.4.10_2) ! net/xmlrpc-c-devel (xmlrpc-c-devel-1.22.2)(unknown build error) * devel/glib20 (glib-2.24.1_1) * security/libgcrypt (libgcrypt-1.4.5_1) * ftp/wget (wget-1.12_1) * graphics/libexif (libexif-0.6.18_1) * devel/qt4-corelib (qt4-corelib-4.6.3) * audio/libvorbis (libvorbis-1.3.1,3) * textproc/aspell (aspell-0.60.6_3) ! x11/libSM (libSM-1.1.1_1,1) (unknown build error) * textproc/qt4-xml (qt4-xml-4.6.3) ! x11/pixman (pixman-0.16.6)(unknown build error) * textproc/libxslt (libxslt-1.1.26_1) * textproc/openjade (openjade-1.3.3p1_1) * graphics/libgphoto2 (libgphoto2-2.4.9.1) ! devel/orc (orc-0.4.6) (unknown build error) * security/gnutls (gnutls-2.8.6_1) * lang/gawk (gawk-3.1.7_1) * devel/gmake (gmake-3.81_4) * net/qt4-network (qt4-network-4.6.3) ! print/freetype2 (freetype2-2.3.12)(unknown build error) * x11-fonts/mkfontscale (mkfontscale-1.0.7) * net-p2p/rtorrent (rtorrent-0.8.6_1) * devel/gio-fam-backend (gio-fam-backend-2.2
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, May 5, 2011 at 8:04 PM, Frank Shute wrote: > On Thu, May 05, 2011 at 05:50:28PM -0500, Antonio Olivares wrote: >> >> Dear all, >> >> I was running FreeBSD 8.1 and am in the process of updating it >> following advice in handbook: >> >> http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html >> >> ran >> # freebsd-update fetch >> # freebsd-update install >> >> # portupgrade -af >> >> # freebsd-update -r 8.2-RELEASE upgrade >> >> then >> >> # freebsd-update install >> >> Tried to do this: >> # portupgrade -f ruby >> # rm /var/db/pkg/pkgdb.db >> # portupgrade -f ruby18-bdb >> # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db >> # portupgrade -af >> >> Did not work correctly[too many customizations] and Tried again >> >> # freebsd-update install >> >> and had nothing more to do :( >> >> I had many packages that need to be updated so I am running : >> >> # portupgrade -arRp >> >> will this prompt me for customizations? > > Yes it will. I usually use the -C flag of portupgrade when I'm > updating ports. This flag prompts you with all the options screens > before it does the update. That way you're not left with the upgrade > hanging half way through whilst it waits for you to configure the > options. > > As Polytropon says you can use the --batch flag if you know that you > don't want to change the default options. > So I should have used the -C/c flag like # portupgrade -CarRp before or after? I have encountered a few prompts :( and not done yet. But will continue to do this till it finishes. Thanks, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, 5 May 2011, Antonio Olivares wrote: Dear all, I was running FreeBSD 8.1 and am in the process of updating it following advice in handbook: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html ran # freebsd-update fetch # freebsd-update install # portupgrade -af # freebsd-update -r 8.2-RELEASE upgrade then # freebsd-update install Tried to do this: # portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # portupgrade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # portupgrade -af Did not work correctly[too many customizations] and Tried again portupgrade is written in Ruby and uses ruby-bdb, so this may not work. -f is of questionable value. Why not just cd to the port directories, and 'make clean build deinstall install'? # freebsd-update install and had nothing more to do :( I had many packages that need to be updated so I am running : # portupgrade -arRp -a is equivalent to -arR. And that's building packages, which is not necessary unless you want to copy them to another machine. will this prompt me for customizations? Options menus? Yes, the ports will ask on their own. If you use the -c or -C options, portupgrade will do all of them at the start of the process. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, 5 May 2011, Chris Brennan wrote: something to keep in mind portmaster does the same thing and all of portupgrades switches work with portmaster, portmaster doesn't have the same switches as portupgrade. Or, being more precise, it has some of the same option flags, but they mean something completely different. For example, -R. the only significant difference is that portmaster will run through and prompt you for all of the 'make config' options first and then go about it's business unattended from that point on... The -c or -C options for portupgrade do that, but they aren't on by default. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, May 05, 2011 at 05:50:28PM -0500, Antonio Olivares wrote: > > Dear all, > > I was running FreeBSD 8.1 and am in the process of updating it > following advice in handbook: > > http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > > ran > # freebsd-update fetch > # freebsd-update install > > # portupgrade -af > > # freebsd-update -r 8.2-RELEASE upgrade > > then > > # freebsd-update install > > Tried to do this: > # portupgrade -f ruby > # rm /var/db/pkg/pkgdb.db > # portupgrade -f ruby18-bdb > # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db > # portupgrade -af > > Did not work correctly[too many customizations] and Tried again > > # freebsd-update install > > and had nothing more to do :( > > I had many packages that need to be updated so I am running : > > # portupgrade -arRp > > will this prompt me for customizations? Yes it will. I usually use the -C flag of portupgrade when I'm updating ports. This flag prompts you with all the options screens before it does the update. That way you're not left with the upgrade hanging half way through whilst it waits for you to configure the options. As Polytropon says you can use the --batch flag if you know that you don't want to change the default options. > > Thanks in advance/advice/suggestions. I am taking the plunge a little > further. Before I just installed and left it alone :( [except for a > few packages that I wanted and ran/installed via ports ], now I am > trying to learn more and setup the firewall. I set up the simple > example setup by Polytropon and most is working. My freebsd version > has moved to FreeBSD 8.2 > > > > [olivares@grullahighschool /usr/home/olivares]$ uname -a > FreeBSD grullahighschool.rgccisd.org 8.2-RELEASE FreeBSD 8.2-RELEASE > #0: Thu Feb 17 02:41:51 UTC 2011 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > Regards, > > Antonio Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpqLhHuOp63u.pgp Description: PGP signature
Re: Does running ``# portupgrade -arRp '' prompt for options or updates everything without prompts?
On Thu, 5 May 2011 19:27:03 -0500, Antonio Olivares
wrote:
> Now, another question. I was thinking about this. Should I have
> popped in a dvd and just used it to upgrade?
I've never tried that, but it _should_ be possible to
"overwrite" an existing installation (e. g. 8.1) with
the files of the newer one (e. g. 8.2); however I would
consider this a bad approach.
> Should I have run
> # make buildworld
> or some magical command(s) that will build the system against newer
> binaries and newer ports so that the system works better and
> optimized?
Depends. If you want to follow -RELEASE _and_ you do
not need a custom kernel, use freebsd-upgrade to use
the binary way. If you _intendedly_ want to use source
based updates to use -STABLE (or even -CURRENT) and (or)
you need a custom kernel that requires compiling, using
the source is the better way.
Personally, I do both. On servers for example, I upgrade
the binary way on -RELEASE, then rebuild the ports (after
upgrading the ports tree, of course). On my testing system
that I use to try out "bleeding edge" software and where
I also want a custom kernel (due to some specific hardware),
I use the source Luke.
> I have limited experience using FreeBSD :(, have used it on and off
> since release 5.3 with KDE 3.4/3.5 series. I installed it and had
> dialup at home tried to get the ltmodem port working, but did not
> succeed :(, and I left it as pristine as it was.
I have also started using FreeBSD with dialup (real PPP with
modem), but this one was a regular serial one which worked
out of the box - not as the crap usually assembled into "modern"
laptops...
> I also got a
> BSDLiveCD : by Scott Ullrich:
>
> http://livebsd.com/
There's also FreeSBIE, one of the famous FreeBSD live system
CDs (which I traditionally use for diagnostics and test).
> \begin{quote}
> Inception
> LiveBSD was founded by Scott Ullrich and Chris Buechler in January
> 2004. It started its life as an open source project, modifying
> FreeSBIE scripts to build FreeBSD-based live CD's. A name was decided
> on, and the domain registered on February 28, 2004. The first LiveBSD
> Desktop CD was released at that time, a KDE desktop live CD based on
> FreeBSD 5.2, built using modified FreeSBIE scripts.
> \end{quote}
Sounds interesting, thanks for mentioning it!
> I really liked it and used it at school. However the project died/was
> unsupported, it appears FreeSBIE has not had much love either.
You can build your own live system CD if needed - there are
excellent tools for that. So once you got a system configured
the way you want, you can follow this idea and make a "portable
system" from that.
> So far it has not prompted me for any configurations. Had done that
> for two/three days with the previous command:
>
> # portupgrade -af
This will stop on any point a configuration is needed.
> Then
> # freebsd-update install
Shouldn't you upgrade the system PRIOR TO the ports?
The order is recommended as system -> ports tree -> ports.
> but the ports/packages were still for old 8.1 release :(,
Yes, as you've updated them on 8.1, and THEN you got the
system to 8.2.
> now I have
> updated ports tree with
> # portsnap fetch
> # portsnap extract
> and
> # portsnap install
That's correct.
Just as a sidenote: There is another way to upgrade the ports
tree, the "traditional one" from the days before portsnap:
Step 1: Add this to /etc/make.conf:
SUP_UPDATE= yes
SUP=/usr/bin/csup
SUPFLAGS= -g -L 2
SUPHOST=cvsup.freebsd.org
PORTSSUPFILE= /etc/sup/ports.sup
Step 2: Create /etc/sup/ports.sup:
*default host=cvsup.freebsd.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
*default compress
ports-all
Note: You can use a different cvsup host and can also exclude
port categories from being updated (e. g. for languages you
do not use, or kinds of programs you are not interested in).
See /usr/share/examples/cvsup/ports-supfile for more details,
it's very well documented (here: in comments).
Step 3: Perform the update
# cd /usr/ports
# make update
Now you have a _current_ ports tree.
Note: A similar method works for the system sources. Add
SUPFILE=/etc/sup/stable.sup
to /etc/make.conf and create /etc/sup/stable.sup like this:
*default host=cvsup.freebsd.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_8
*default delete use-rel-suffix
*default compress
src-all
This will give you 8-CURRENT. Use "tag=RELENG_8.0" for 8.0-pX
(security branch, just as fr
