Re: # portmaster -r pixman fails with !#/bin/sh list too long
On Fri, Oct 4, 2013 at 12:09 PM, Warren Block wrote: > On Thu, 3 Oct 2013, Antonio Olivares wrote: > >> Have tried that, but it rebuilds pixman, but then X bombs out blurting >> out messages that libpixman.so is missing :( >> >> I have tried to remove print/texlive-scheme-full; removed it, but then >> run portmaster -R pixman, and portmaster -r pixman and the running of >> it stops with message that !#/bin/sh .. argument too long and comes up >> with texlive-?-?-_1 or similar. Have not been successful in >> fixing this issue. I have 2 machines working and 2 not working >> because of this. I am running out of ideas. Is there another way to >> fix this issue manually, i.e, going to /usr/ports/x11/pixman and >> rebuilding it there or have to go one by one? > > > Careful: -R has a different meaning with portmaster than it does with > portupgrade. It does not mean "recursive" like lowercase "-r". > > pkg_libchk from sysutils/bsdadminscripts can be used to detect installed > ports that depend on missing libraries. From that, it may be possible to > just give a list of all the ones that are missing pixman to portmaster. Dear all, It appears that using # portmaster -d -r pixman -x 'texlive-*-*' is doing the job :) I am keeping my fingers crossed and hope it comes through and succeeds! It stopped with libexo, but got that sorted out. Then stopped with mplayer*, but I am skipping it at this time. -x 'mplayer-*' and hope it succeeds, I'll then rebuild mplayer later if needed. Best 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Thu, 3 Oct 2013, Antonio Olivares wrote: Have tried that, but it rebuilds pixman, but then X bombs out blurting out messages that libpixman.so is missing :( I have tried to remove print/texlive-scheme-full; removed it, but then run portmaster -R pixman, and portmaster -r pixman and the running of it stops with message that !#/bin/sh .. argument too long and comes up with texlive-?-?-_1 or similar. Have not been successful in fixing this issue. I have 2 machines working and 2 not working because of this. I am running out of ideas. Is there another way to fix this issue manually, i.e, going to /usr/ports/x11/pixman and rebuilding it there or have to go one by one? Careful: -R has a different meaning with portmaster than it does with portupgrade. It does not mean "recursive" like lowercase "-r". pkg_libchk from sysutils/bsdadminscripts can be used to detect installed ports that depend on missing libraries. From that, it may be possible to just give a list of all the ones that are missing pixman to portmaster. ___ 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: Re: # portmaster -r pixman fails with !#/bin/sh list too long
On 10/03/2013 20:28, Antonio Olivares wrote: > Have tried that, but it rebuilds pixman, but then X bombs out blurting > out messages that libpixman.so is missing :( > > I have tried to remove print/texlive-scheme-full; removed it, but then > run portmaster -R pixman, and portmaster -r pixman and the running of > it stops with message that !#/bin/sh .. argument too long and comes up > with texlive-?-?-_1 or similar. Have not been successful in > fixing this issue. I have 2 machines working and 2 not working > because of this. I am running out of ideas. Is there another way to > fix this issue manually, i.e, going to /usr/ports/x11/pixman and > rebuilding it there or have to go one by one? Is it vital to use the texlive ports you get via portshaker or could you switch to TEX_DEFAULT=texlive and use the texlive 2012 from official ports (which has a few huge instead of many tiny packages)? (If you want to switch, remove everything starting with texlive, check out a fresh ports tree without portshaker, since there is at least one port with the same name, and install print/texlive-full and maybe print/texlive-docs.) Cheers, Jan Henrik ___ 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: # portmaster -r pixman fails with !#/bin/sh list too long
On Tue, Oct 1, 2013 at 8:46 AM, Lowell Gilbert
wrote:
> Antonio Olivares writes:
>
>> I tried your advice with the -R option, it worked, but for only pixman
>> the other ports that depend on it don't get rebuilt :(
>>
>> I try to use -x 'texlive-*' but it does not work :(
>> I get
>>
>> Could not execute shell
>> "/usr/ports/Mk/bsd.port.mk", line 1192: warning "/usr/bin/awk
>> '/^#define[[:blank:]]FreeBSD_version/ {print $3}
>> > /usr/local/sbin/portmaster: rm: Argument list too long
>>
>> and it justs sits there. Out of 3 machines only 1 is working because
>> I overlooked the pixman update entry in /usr/src/UPDATING :(
>>
>> Please advice me as to how to get the desktop working again on these
>> machines. I did not want to shoot myself in the foot but I did so :(
>
> Try the '-R' again; it may get a bit farther each time.
>
> You can always recover by removing some of the ports and reinstalling
> them after the remaining ports are updated. You're going to have to
> rebuild a huge number of ports anyway, so this is not very different
> from using portmaster on everything.
>
> Good luck.
Have tried that, but it rebuilds pixman, but then X bombs out blurting
out messages that libpixman.so is missing :(
I have tried to remove print/texlive-scheme-full; removed it, but then
run portmaster -R pixman, and portmaster -r pixman and the running of
it stops with message that !#/bin/sh .. argument too long and comes up
with texlive-?-?-_1 or similar. Have not been successful in
fixing this issue. I have 2 machines working and 2 not working
because of this. I am running out of ideas. Is there another way to
fix this issue manually, i.e, going to /usr/ports/x11/pixman and
rebuilding it there or have to go one by one?
Thanks for your advice and suggestions but I am not getting there :(
Best 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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares writes:
> I tried your advice with the -R option, it worked, but for only pixman
> the other ports that depend on it don't get rebuilt :(
>
> I try to use -x 'texlive-*' but it does not work :(
> I get
>
> Could not execute shell
> "/usr/ports/Mk/bsd.port.mk", line 1192: warning "/usr/bin/awk
> '/^#define[[:blank:]]FreeBSD_version/ {print $3}
> /usr/local/sbin/portmaster: rm: Argument list too long
>
> and it justs sits there. Out of 3 machines only 1 is working because
> I overlooked the pixman update entry in /usr/src/UPDATING :(
>
> Please advice me as to how to get the desktop working again on these
> machines. I did not want to shoot myself in the foot but I did so :(
Try the '-R' again; it may get a bit farther each time.
You can always recover by removing some of the ports and reinstalling
them after the remaining ports are updated. You're going to have to
rebuild a huge number of ports anyway, so this is not very different
from using portmaster on everything.
Good luck.
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Dear Sir,
I tried your advice with the -R option, it worked, but for only pixman
the other ports that depend on it don't get rebuilt :(
I try to use -x 'texlive-*' but it does not work :(
I get
Could not execute shell
"/usr/ports/Mk/bsd.port.mk", line 1192: warning "/usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
wrote:
> Antonio Olivares writes:
>
>> Dear folks,
>>
>> In updating ports I encounter above issue and cannot proceed.
>>
>> 20130929:
>> AFFECTS: users of x11/pixman
>> AUTHOR: zeis...@freebsd.org
>>
>> The library version of x11/pixman has changed, and portrevision has
>> been bumped in all dependent ports. If you have external software that
>> depends on pixman, this software needs to be recompiled.
>> To recompile all software dependent on pixman, run:
>>
>> # portmaster -r pixman
>> or
>> # portupgrade -rf pixman
>>
>> The messages are that a pkg texlive-ub* and that #!/bin/sh list
>> too long. I try to run
>> # portmaster -d -r pixman -x 'texlive-*'
>> but it still fails in the same place :(
>
> I continued with portmaster's "-R" option and got a lot further. You
> could try either that or the command line that portmaster suggests
> when it bails out.
>
>> I am using texlive-freebsd from Romain Tartiere's googlecode page in
>> case it is important. Please advice me so I can succeed to fix these
>> issue. I lost X because I failed to read the /usr/src/UPDATING advice
>> and then I realized that I overlooked this :(
>
> I don't think that texlive is relevant; if you continue the process
> instead of starting from scratch, you'll probably get farther.
>
> I'd prefer to actually debug the problem at its root, but it's the
> middle of the night and I don't seem to have enough brain cells awake
> to figure anything out.
>
> Good luck.
___
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: # portmaster -r pixman fails with !#/bin/sh list too long
Antonio Olivares writes: > Dear folks, > > In updating ports I encounter above issue and cannot proceed. > > 20130929: > AFFECTS: users of x11/pixman > AUTHOR: zeis...@freebsd.org > > The library version of x11/pixman has changed, and portrevision has > been bumped in all dependent ports. If you have external software that > depends on pixman, this software needs to be recompiled. > To recompile all software dependent on pixman, run: > > # portmaster -r pixman > or > # portupgrade -rf pixman > > The messages are that a pkg texlive-ub* and that #!/bin/sh list > too long. I try to run > # portmaster -d -r pixman -x 'texlive-*' > but it still fails in the same place :( I continued with portmaster's "-R" option and got a lot further. You could try either that or the command line that portmaster suggests when it bails out. > I am using texlive-freebsd from Romain Tartiere's googlecode page in > case it is important. Please advice me so I can succeed to fix these > issue. I lost X because I failed to read the /usr/src/UPDATING advice > and then I realized that I overlooked this :( I don't think that texlive is relevant; if you continue the process instead of starting from scratch, you'll probably get farther. I'd prefer to actually debug the problem at its root, but it's the middle of the night and I don't seem to have enough brain cells awake to figure anything out. Good luck. ___ 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: portmaster -- no execute command
On Wed, 17 Apr 2013 16:34:24 -0400, Jerry wrote: > Does portmaster have a "--noexecute" flag like portupgrade? > Specifically, I want to run the following command and see exactly what > would be updated / modified sans actually doing it. > > portmaster -o new_app old_app Is the -n option what you are looking for? >From "man portmaster": -n run through all steps, but do not make or install any ports This common flag seems to be allowed for installation via -o, according to the synopsis: portmaster [Common Flags] -o -- 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: Portmaster runs make config three times for some ports
On 9 February 2013 05:45, Mike Clarke wrote: > > I started off portmaster on a massive update on Thursday evening. Everything > started off OK and I kept responding to all the make config screens until they > were all finished and the compilation was well underway then went to bed and > left it to get on with it. > > The next morning I discovered that things had progressed as far as starting to > build en-apache-openoffice but it was sitting there with the config screen > again despite having already gone through make config earlier. I clicked on OK > and left it to get on with the compilation while I went away to get on with > other things with just occasional checks to make sure it was still running. > About 6 hours later when I checked it had completed the compilation and had > started to install en-apache-openoffice but was waiting yet again with the > config screen. > > Once again I clicked on OK and left things to continue. The job was still > running last night and I expected to find it completed by this morning but on > checking at 9:30 this morning I discovered that it had done the same thing > with py27-gobject and had been sitting there with the config screen since > shortly after midnight. > > Both openoffice and py27-gobject had gone through make config in the initial > stage (I've checked the log file) but for some reason make config was repeated > immediately before the compile and install stages. > > I invoked portmaster with: > > portmaster -r libffi -r boost-libs -r gnutls -r libtasn1 > > and these are the only options set in /usr/local/etc/portmaster.rc > > # Never search for stale distfiles to delete (-D) > DONT_SCRUB_DISTFILES=Dopt > # > # Do not prompt the user for failed backup package creation > PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package > > Any ideas how I can avoid this happening. > It's slow & painful, but run through once with -n, to set all of your config options, & then run it again with BATCH=YES set (though I don't know if it would be best to edit /etc/make.conf, set it in the environment, or pass it with -m) to avoid it asking 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"
Re: portmaster + unknown dependency problem
On 20.11.2012 20:47, Laszlo Nagy wrote: I have a 8.2-STABLE system. Last port upgrade was about a year ago. (I know, this is bad.) I was trying to update all ports, by following the UPDATING file. As it turned out, some ports has been deprecated/deleted. I have a problem in particular with the py-bittornado-core port. I do not need it. So I have deleted it: # pkg_info | grep bittornado # Clearly, it is not installed. However, when I write in this command: # portmaster -a Then I get this error: ===>>> The net-p2p/py-bittornado-core port has been deleted: Has expired: Depends on the deprecated wx 2.4 ===>>> Aborting update Well, here is the question: why does it want to build a port that does not even exist in the ports tree? It was really deleted, there is no such thing as /usr/ports/net-p2p/py-bittornado-core . I have also tried to do this: # portmaster -a -x py-bittornado-core but it has exactly the same problem. Is this a stale dependency to a nonexistent port? How can I overcome this problem? Thanks, Laszlo ___ 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" make "pkg_info | grep "*bittornado*" When it found this package, you can think about to delete it. When you have delete it or doesnt found it, make a "portmaster --check-depends" to solve depends. ___ 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: portmaster or ports (packaging) problem ?
uki gmail.com> writes: > > But theese are different packages (different names). since ports dont have > any equivalent of debian "provides" flag it is impossible to figure it out > in a safe way. I have never built a port/package, so I could be wrong here. This paragraph seems to contain means to specify a dependency and built it if needed: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-depend.html for example 5.8.3 BUILD_DEPENDS aside from its primary meaning as a requirement for building *this* port, it could be used indirectly to build and install a dependent port :-) and this offer means to specify a minimal version of a dependency: 5.8.8 Minimal Version of a Dependency My point is, the logic/infrastrucutre already exists, just adopt it to next level of port/package management. jb ___ 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: portmaster or ports (packaging) problem ?
But theese are different packages (different names). since ports dont have any equivalent of debian "provides" flag it is impossible to figure it out in a safe way. 09-11-2012 19:19, "jb" napisał(a): > Hi, > I hit a problem today during a system update. > > There were two libxul ports: > /usr/ports/www/libxul > /usr/ports/www/libxul19 > of which the last one was installed: > /var/db/pkg/libxul-1.9.2.28_1/ > > There was a port to update which died on error: > # portmaster icedtea-web > ... > ===>>> The dependency for www/libxul >seems to be handled by libxul-1.9.2.28_1 > ... > ===> Found libxul-1.9.2.28_1, but you need to upgrade to libxul>=10. > *** [build-depends] Error code 1 > ... > # > > So, I had to manually deinstall www/libxul19 and install www/libxul and try > again. > > # portmaster icedtea-web > ... > ===>>> The following actions will be taken if you choose to proceed: > Upgrade icedtea-web-1.3_1 to icedtea-web-1.3.1 > Install www/libxul > ... > # > > Is the portmaster to blame for not being smart enough and not taking steps > of deinstalling www/libxul19 and installing www/libxul in one step ? > jb > > > ___ > 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"
Re: portmaster options
jb gmail.com> writes: > ... I have doubts about these options use, so I filed a PR#: http://www.freebsd.org/cgi/query-pr.cgi?pr=172651 jb ___ 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: portmaster options
Polytropon edvax.de> writes: > ... > But this? > > # portmaster -L --index | egrep '(ew|ort) version|total install' > /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps > 00m00s > Terminated > > This is with --index and _no_ ports collection in the default > location (example quoted from your message)... > The above (aborted ?) entry did not create any /tmp die files - this will be obvious below. I repeated the procedure once again, with extra tests. [root@localhost ~]# mv /usr/ports /usr/ports-saved [root@localhost ~]# ls -al /tmp/d d-49774-index/ dbus-VVS2cduIFg dbus-cgVqiePRiB dbus-pt6vB9UUJ6 dbus-4inUXwgfJ4 dbus-Y2iXdHF5tz dbus-fsMikdzeLa dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-ZGcPBBe763 dbus-o2yUi7puUT dbus-vT3uAQQB6U dbus-FEJgZRlX7B dbus-ZmBHPDrpWD dbus-oVPu6XWzrw dbus-zrcvtjVO62 dbus-KPYiGOw8UL dbus-c36HAD5e3q dbus-paXxX0f1fy [root@localhost ~]# ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 15:35 .. [root@localhost ~]# find /tmp -name "*INDEX*" [root@localhost ~]# portmaster -L --index-only | egrep '(ew|ort) version|total install' /tmp/d-93752-index/INDEX-9.bz2100% of 1619 kB 185 kBps ===>>> New version available: smartmontools-5.43_1 ===>>> 618 total installed ports ===>>> 1 has a new version available # ls -al /tmp/d d-49774-index/ dbus-FEJgZRlX7B dbus-Y2iXdHF5tz dbus-c36HAD5e3q dbus-o2yUi7puUT dbus-pt6vB9UUJ6 dbus-zrcvtjVO62 dbus-4inUXwgfJ4 dbus-KPYiGOw8UL dbus-ZGcPBBe763 dbus-cgVqiePRiB dbus-oVPu6XWzrw dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-VVS2cduIFg dbus-ZmBHPDrpWD dbus-fsMikdzeLa dbus-paXxX0f1fy dbus-vT3uAQQB6U # ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 16:00 .. [root@localhost ~]# find /tmp -name "*INDEX*" /tmp/INDEX-9 /tmp/INDEX-9.bz2 [root@localhost ~]# ls -al /tmp/*INDEX* -rw-r--r-- 1 root wheel 26715339 Oct 12 16:00 /tmp/INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 /tmp/INDEX-9.bz2 [root@localhost ~]# portmaster -L --index | egrep '(ew|ort) version|total install' Terminated [root@localhost ~]# ls -al /tmp/d d-49774-index/ dbus-VVS2cduIFg dbus-cgVqiePRiB dbus-pt6vB9UUJ6 dbus-4inUXwgfJ4 dbus-Y2iXdHF5tz dbus-fsMikdzeLa dbus-u5N9XsFQwT dbus-DoADJZr2PE dbus-ZGcPBBe763 dbus-o2yUi7puUT dbus-vT3uAQQB6U dbus-FEJgZRlX7B dbus-ZmBHPDrpWD dbus-oVPu6XWzrw dbus-zrcvtjVO62 dbus-KPYiGOw8UL dbus-c36HAD5e3q dbus-paXxX0f1fy [root@localhost ~]# ls -al /tmp/d-49774-index/ total 8 drwx-- 2 jbwheel 512 Oct 7 00:19 . drwxrwxrwt 23 root wheel 2048 Oct 12 16:00 .. [root@localhost ~]# find /tmp -name "*INDEX*" /tmp/INDEX-9 /tmp/INDEX-9.bz2 [root@localhost ~]# ls -al /tmp/*INDEX* -rw-r--r-- 1 root wheel 26715339 Oct 12 16:00 /tmp/INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 /tmp/INDEX-9.bz2 [root@localhost ~]# rm /tmp/INDEX* [root@localhost ~]# find /tmp -name "*INDEX*" [root@localhost ~]# # portmaster -L --index | egrep '(ew|ort) version|total install' Terminated [root@localhost ~]# [root@localhost ~]# find /tmp -name "*INDEX*" [root@localhost ~]# jb ___ 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: portmaster options
On Fri, 12 Oct 2012 13:42:10 + (UTC), jb wrote: > RW googlemail.com> writes: > > > > > On Fri, 12 Oct 2012 04:35:43 + (UTC) > > jb wrote: > > > > > Hi, > > > what is the diff between > > > --index > > > and > > > --index-only > > > > From a *very* quick look, it appears that --index-only means don't use > > the the port-directory at all, so that the index file is downloaded > > into /tmp, and some checks and optimizations are skipped or done > > less efficiently. > > ... > > # ls -al /usr/ports/ > ... > -rw-r--r-- 1 root wheel 26881412 Oct 12 07:47 INDEX-7 > -rw-r--r-- 1 root wheel 26765446 Oct 12 07:47 INDEX-8 > -rw-r--r-- 1 root wheel 26715339 Oct 12 13:28 INDEX-9 > -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2 > ... > # > > # find /tmp -name "*INDEX*" > > # portmaster -L --index-only | egrep '(ew|ort) version|total install' > ===>>> New version available: smartmontools-5.43_1 > ===>>> 618 total installed ports > ===>>> 1 has a new version available > > # find /tmp -name "*INDEX*" > > Nope :-) But this? # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps 00m00s Terminated This is with --index and _no_ ports collection in the default location (example quoted from your message)... -- 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: portmaster options
RW googlemail.com> writes: > > On Fri, 12 Oct 2012 04:35:43 + (UTC) > jb wrote: > > > Hi, > > what is the diff between > > --index > > and > > --index-only > > From a *very* quick look, it appears that --index-only means don't use > the the port-directory at all, so that the index file is downloaded > into /tmp, and some checks and optimizations are skipped or done > less efficiently. > ... # ls -al /usr/ports/ ... -rw-r--r-- 1 root wheel 26881412 Oct 12 07:47 INDEX-7 -rw-r--r-- 1 root wheel 26765446 Oct 12 07:47 INDEX-8 -rw-r--r-- 1 root wheel 26715339 Oct 12 13:28 INDEX-9 -rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2 ... # # find /tmp -name "*INDEX*" # portmaster -L --index-only | egrep '(ew|ort) version|total install' ===>>> New version available: smartmontools-5.43_1 ===>>> 618 total installed ports ===>>> 1 has a new version available # find /tmp -name "*INDEX*" Nope :-) jb ___ 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: portmaster options
On Fri, 12 Oct 2012 04:35:43 + (UTC) jb wrote: > Hi, > what is the diff between > --index > and > --index-only >From a *very* quick look, it appears that --index-only means don't use the the port-directory at all, so that the index file is downloaded into /tmp, and some checks and optimizations are skipped or done less efficiently. ___ 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: portmaster options
Polytropon edvax.de> writes: > ... > > Well, yes, BUT they seem to be redundant (that's why I asked). > > > > # portmaster -L --index-only | egrep '(ew|ort) version|total install' > > ===>>> New version available: smartmontools-5.43_1 > > ===>>> 618 total installed ports > > ===>>> 1 has a new version available > > > > # portmaster -L --index | egrep '(ew|ort) version|total install' > > ===>>> New version available: smartmontools-5.43_1 > > ===>>> 618 total installed ports > > ===>>> 1 has a new version available > > # > > Did you test this with or _without_ an actually installed ports > collection? If you don't have one installed, --index probably > won't work. > # mv /usr/ports /usr/ports-saved # portmaster -L --index-only | egrep '(ew|ort) version|total install' /tmp/d-85964-index/INDEX-9.bz2100% of 1619 kB 185 kBps ===>>> New version available: smartmontools-5.43_1 ===>>> 618 total installed ports ===>>> 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' /tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps 00m00s Terminated # Well, the second entry outcome (with --index option) looks like a bug to me. jb ___ 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: portmaster options
On Fri, 12 Oct 2012 11:34:17 + (UTC), jb wrote: > Polytropon edvax.de> writes: > > > > > On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: > > > Hi, > > > what is the diff between > > > --index > > > and > > > --index-only > > ... > > --index > > use INDEX-[7-9] exclusively to check if a port is up to date > > ... > > --index-only > > do not try to use /usr/ports. For updating ports when no > > /usr/ports > > directory is present the -PP|--packages-only option is required. > > See > > the ENVIRONMENT section below for additional requirements. > > > > This means --index-only is to be used when using portmaster for > > binary installs without an installed ports collection. > > > > Well, yes, BUT they seem to be redundant (that's why I asked). > > # portmaster -L --index-only | egrep '(ew|ort) version|total install' > ===>>> New version available: smartmontools-5.43_1 > ===>>> 618 total installed ports > ===>>> 1 has a new version available > > # portmaster -L --index | egrep '(ew|ort) version|total install' > ===>>> New version available: smartmontools-5.43_1 > ===>>> 618 total installed ports > ===>>> 1 has a new version available > # Did you test this with or _without_ an actually installed ports collection? If you don't have one installed, --index probably won't work. -- 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: portmaster options
On 10/12/2012 01:57 PM, jb wrote: > jb gmail.com> writes: > >> ... >>> --index-only >>> do not try to use /usr/ports. For updating ports when no >>> /usr/ports >>> directory is present the -PP|--packages-only option is required. >>> See the ENVIRONMENT section below for additional requirements. >>> >> ... > And -PP|--packages-only option implies "index only" entry behavior, so there > is redundancy here as well. > > Does anybody know where this --index-only option really matter ? > jb > Well /usr/local/sbin/portmaster is a _big_ shell script You could read through it to find the answer to your question This e-mail message, including any attachment(s), is intended solely for the addressee or addressees. Any views or opinions presented herein are solely those of the author and do not necessarily represent those of OSE. If you are not the intended recipient of this communication please return this e-mail message and the attachment(s) to the sender and delete and destroy all copies. ___ 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: portmaster options
jb gmail.com> writes: > ... > > --index-only > > do not try to use /usr/ports. For updating ports when no > > /usr/ports > > directory is present the -PP|--packages-only option is required. > > See the ENVIRONMENT section below for additional requirements. > > > ... And -PP|--packages-only option implies "index only" entry behavior, so there is redundancy here as well. Does anybody know where this --index-only option really matter ? jb ___ 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: portmaster options
Polytropon edvax.de> writes: > > On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: > > Hi, > > what is the diff between > > --index > > and > > --index-only > ... > --index > use INDEX-[7-9] exclusively to check if a port is up to date > ... > --index-only > do not try to use /usr/ports. For updating ports when no /usr/ports > directory is present the -PP|--packages-only option is required. See > the ENVIRONMENT section below for additional requirements. > > This means --index-only is to be used when using portmaster for > binary installs without an installed ports collection. > Well, yes, BUT they seem to be redundant (that's why I asked). # portmaster -L --index-only | egrep '(ew|ort) version|total install' ===>>> New version available: smartmontools-5.43_1 ===>>> 618 total installed ports ===>>> 1 has a new version available # portmaster -L --index | egrep '(ew|ort) version|total install' ===>>> New version available: smartmontools-5.43_1 ===>>> 618 total installed ports ===>>> 1 has a new version available # ___ 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: portmaster options
On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote: > Hi, > what is the diff between > --index > and > --index-only According to "man portmaster" there are some options that control the behaviour regarding the use of INDEX: --no-index-fetch skip fetching the INDEX file --index use INDEX-[7-9] exclusively to check if a port is up to date --index-first use the INDEX for status, but double-check with the port --index-only do not try to use /usr/ports. For updating ports when no /usr/ports directory is present the -PP|--packages-only option is required. See the ENVIRONMENT section below for additional requirements. This means --index-only is to be used when using portmaster for binary installs without an installed ports collection. -- 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: portmaster backup package
On Mon, 8 Oct 2012 16:18:20 + (UTC), jb wrote: > Hi, > what to do with that backup package (-b option) after installation of new port > failed ? Install it with pkg_add? :-) -- 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: portmaster embarrassingly simple question (y- option)
On 03/07/2012 13:06, Bas Smeelen wrote:
> On 07/03/2012 12:29 PM, Jakub Lach wrote:
>> What option do I need to specify with -y to automatically answer those?
> -d
Add this to ${LOCALBASE}/etc/portmaster.rc
ALWAYS_SCRUB_DISTFILES=dopt
if that's something you're going to be doing all the time.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: portmaster embarrassingly simple question (y- option)
Now I see that I even used -d in my own portupdating wrapper, but forgot about it and it's meaning, embarrassing. -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723918.html Sent from the freebsd-questions mailing list archive at Nabble.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: portmaster embarrassingly simple question (y- option)
Excellent, I knew I was missing something simple. Thanks! -- View this message in context: http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723916.html Sent from the freebsd-questions mailing list archive at Nabble.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: portmaster embarrassingly simple question (y- option)
Hi Jakub, On Tue, Jul 3, 2012 at 12:45 PM, Dean E. Weimer wrote: > -d tells it to always delete old files without prompting. > > Thanks, > Dean Weimer > > On Jul 3, 2012, at 5:29 AM, Jakub Lach wrote: > > > ===>>> Starting check for runtime dependencies > > ===>>> Gathering dependency list for archivers/unzip from ports > > ===>>> No dependencies for archivers/unzip > > ===>>> Installing package > > > > ===>>> Installation of archivers/unzip (unzip-6.0_1) succeeded > > > > > > ===>>> Delete unzip60.tar.gz? y/n [n] > > > > What option do I need to specify with -y to automatically answer those? > > > > I've tried --clean-distfiles, --clean-packages but it's not it. > > > > It usually happens when doing portmaster --packages-build > > --delete-build-only > > build. > usually I use: portmaster -dbg -b create and keep a backup package of an installed port -g create a package of the new port -d always clean distfiles Best Regards Iqbal 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: portmaster embarrassingly simple question (y- option)
On 07/03/2012 12:29 PM, Jakub Lach wrote: ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for archivers/unzip from ports ===>>> No dependencies for archivers/unzip ===>>> Installing package ===>>> Installation of archivers/unzip (unzip-6.0_1) succeeded ===>>> Delete unzip60.tar.gz? y/n [n] What option do I need to specify with -y to automatically answer those? Hi -d I've tried --clean-distfiles, --clean-packages but it's not it. It usually happens when doing portmaster --packages-build --delete-build-only build. Disclaimer: http://www.ose.nl/email ___ 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: portmaster embarrassingly simple question (y- option)
-d tells it to always delete old files without prompting. Thanks, Dean Weimer On Jul 3, 2012, at 5:29 AM, Jakub Lach wrote: > ===>>> Starting check for runtime dependencies > ===>>> Gathering dependency list for archivers/unzip from ports > ===>>> No dependencies for archivers/unzip > ===>>> Installing package > > ===>>> Installation of archivers/unzip (unzip-6.0_1) succeeded > > > ===>>> Delete unzip60.tar.gz? y/n [n] > > What option do I need to specify with -y to automatically answer those? > > I've tried --clean-distfiles, --clean-packages but it's not it. > > It usually happens when doing portmaster --packages-build > --delete-build-only > build. > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878.html > Sent from the freebsd-questions mailing list archive at Nabble.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" ___ 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: Portmaster and update progress, suggestion.
On 06/06/2012 15:06, Doug Barton wrote:
> On 06/06/2012 09:11, Leslie Jensen wrote:
>> My initial wish for some information about the build progress is still
>> very much on the table.
>
> Try the attached patch.
Actually try this one instead. :)
--
This .signature sanitized for your protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf () {
+ case "$1" in *\>\>*) echo -e "\n\t${PM_PARENT_PORT}${1}" ;; esac
+
[ -n "$PM_NO_TERM_TITLE" ] && return
case "$TERM" in cons*) return ;; esac
@@ -2283,7 +2285,6 @@
deps=" (${dep_of_deps}/${num_of_deps})"
if [ -n "$PM_DEPTH" ]; then
- echo " ${PM_DEPTH}>> ${1#$pd/}"
term_printf " ${PM_DEPTH#* }>> ${1#$pd/}${deps}"
else
[ -n "$UPDATE_ALL" ] && term_printf " >> ${1#$pd/}${deps}"
@@ -2527,19 +2528,16 @@
safe_exit
elif [ -n "$PM_FIRST_PASS" -a -z "$PM_PACKAGES" ]; then
echo "===>>> Initial dependency check complete for $portdir"
- case "$PM_DEPTH" in *\>\>*) echo " $PM_DEPTH" ;; esac
else
echo "===>>> Dependency check complete for $portdir"
- case "$PM_DEPTH" in
- *\>\>*) echo " $PM_DEPTH" ;;
- *) if [ "$PM_PARENT_PORT" = All ]; then
- local deps
- deps=" (${dep_of_deps}/${num_of_deps})"
- term_printf " >> ${upg_port:-$portdir}${deps}"
- else
- term_printf
- fi ;;
- esac
+
+ if [ "$PM_PARENT_PORT" = All ]; then
+ local deps
+ deps=" (${dep_of_deps}/${num_of_deps})"
+ term_printf " >> ${upg_port:-$portdir}${deps}"
+ else
+ term_printf
+ fi
fi
} # dependency_check()
___
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: Portmaster and update progress, suggestion.
On 06/06/2012 09:11, Leslie Jensen wrote:
> My initial wish for some information about the build progress is still
> very much on the table.
Try the attached patch. It essentially adds the progress info that is
being put in the TERM title to the in-line printout of the dependency
trail that was already there.
Let me know what you think,
Doug
--
This .signature sanitized for your protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf () {
+ echo -e "\n\t${PM_PARENT_PORT}${1}"
+
[ -n "$PM_NO_TERM_TITLE" ] && return
case "$TERM" in cons*) return ;; esac
@@ -2283,7 +2285,7 @@
deps=" (${dep_of_deps}/${num_of_deps})"
if [ -n "$PM_DEPTH" ]; then
- echo " ${PM_DEPTH}>> ${1#$pd/}"
+ #echo " ${PM_DEPTH}>> ${1#$pd/}"
term_printf " ${PM_DEPTH#* }>> ${1#$pd/}${deps}"
else
[ -n "$UPDATE_ALL" ] && term_printf " >> ${1#$pd/}${deps}"
@@ -2623,7 +2625,7 @@
[ -z "$dep_of_deps" ] && dep_of_deps=0
export PM_PARENT_PORT num_of_deps dep_of_deps
- term_printf
+ #term_printf
}
if [ -n "$PM_URB" ]; then
@@ -2783,6 +2785,7 @@
numports=$(( $numports + 1 ))
init_term_printf "$port ${numports}/${numports}"
+ term_printf
($0 $ARGS $port) || update_failed=update_failed
. $IPC_SAVE
[ -n "$update_failed" ] && fail "Update for $port failed"
@@ -2825,6 +2828,7 @@
num=$(( $num + 1 ))
init_term_printf "$port ${num}/${numports}"
+ term_printf
($0 $ARGS $port) || update_failed=update_failed
. $IPC_SAVE
[ -n "$update_failed" ] && fail "Update for $port failed"
@@ -2978,6 +2982,7 @@
[ -n "$DI_FILES" ] && (read_distinfos)&
init_term_printf All
+ term_printf
ports_by_category
echo "===>>> Starting check of installed ports for available updates"
___
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: Portmaster and update progress, suggestion.
On Wed, 6 Jun 2012, Leslie Jensen wrote: Can the reason for me not getting the title to change be that I very often use screen when updating ports? Sure, the escape codes are interpreted by screen, not Terminal. There may be a way to pass them through. tmux has some options for that, but I haven't really tried them and have not used screen. ___ 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: Portmaster and update progress, suggestion.
2012-06-04 16:10, Leslie Jensen skrev: 2012-06-04 15:54, Warren Block skrev: % printf "\033];Funny Title\007" Works! ___ 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" Can the reason for me not getting the title to change be that I very often use screen when updating ports? I've tried different combinations and I'm only able to get the title when I work locally. Screen and ssh does not change the title. My initial wish for some information about the build progress is still very much on the table. Thanks /Leslie ___ 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: Portmaster and update progress, suggestion.
2012-06-04 15:54, Warren Block skrev: % printf "\033];Funny Title\007" Works! ___ 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: Portmaster and update progress, suggestion.
On Mon, 4 Jun 2012, Leslie Jensen wrote: 2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from "Terminal" Could be something in your prompt resetting it. Does % printf "\033];Funny Title\007" change the title? ___ 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: Portmaster and update progress, suggestion.
2012-06-04 10:14, Leslie Jensen skrev: 2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from "Terminal" /Leslie ___ 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" After a restart of xfce I've got the Title to change, but I can only see the initial command ie portmaster All. /Leslie ___ 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: Portmaster and update progress, suggestion.
2012-06-04 09:41, Doug Barton skrev: On 06/04/2012 00:35, Leslie Jensen wrote: I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug I've set that dynamic title should go before initial title. I've also tried the setting that it should replace initial title. None of the settings changes anything. I've no title at all apart from "Terminal" /Leslie ___ 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: Portmaster and update progress, suggestion.
On 06/04/2012 00:35, Leslie Jensen wrote: > I found that setting and changed it. That should do it then. Thanks to Warren for suggesting it. > I forgot to tell you that I'm working through an SSH connection and > maybe it's because of that I cannot see any title? Nope. Should work just fine for you, I've done thousands of portmaster upgrades over ssh. Let me know how it goes, Doug -- This .signature sanitized for your protection ___ 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: Portmaster and update progress, suggestion.
2012-06-03 18:18, Warren Block skrev: On Sun, 3 Jun 2012, Warren Block wrote: On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. Oh, and xfce's Terminal has a preferences setting that can prevent dynamically-set titles from being displayed. ___ 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 found that setting and changed it. I forgot to tell you that I'm working through an SSH connection and maybe it's because of that I cannot see any title? I'll test as soon as I've got the system up with X 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"
Re: Portmaster and update progress, suggestion.
On Sun, 3 Jun 2012, Warren Block wrote: On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. Oh, and xfce's Terminal has a preferences setting that can prevent dynamically-set titles from being displayed. ___ 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: Portmaster and update progress, suggestion.
On Sun, 3 Jun 2012, Leslie Jensen wrote: 2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? It's on by default. --no-term-title disables it, as does setting PM_NO_TERM_TITLE in portmaster.rc. ___ 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: Portmaster and update progress, suggestion.
2012-06-02 19:18, Doug Barton skrev: On 6/2/2012 8:09 AM, Leslie Jensen wrote: I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. hope this helps, Doug I'm running in XFCE4 terminal and the titlebar is empty here! So do I need to activate this function? Thanks /Leslie ___ 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: Portmaster and update progress, suggestion.
On 6/2/2012 8:09 AM, Leslie Jensen wrote: > I'm thinking about some kind of information on the build progress Portmaster already has that if you're building in a terminal window, look in the titlebar. I can take a look at printing that in line if you're not in a terminal window though. hope this helps, Doug -- This .signature sanitized for your protection ___ 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: Portmaster Fetch
On 28 May 2012 14:12, Silvio Siefke wrote: > Hello, > > is there a chance that portmaster can be only fetch all Source which need > update? > I mean make fetch-recursiv has helped in the ports collection, when i think > right, > but can portmaster that with all packages they need update? portmaster -F -- Eitan Adler ___ 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: Portmaster Fetch
On Mon, 28 May 2012 23:12:31 +0200, Silvio Siefke wrote: > Hello, > > is there a chance that portmaster can be only fetch all Source which need > update? > I mean make fetch-recursiv has helped in the ports collection, when i think > right, > but can portmaster that with all packages they need update? Is "portmaster -n" (run through all steps, but do not make or install any ports) what you need? Maybe see "man portmaster" for more details. -- 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: portmaster won't update libc.so.7
On 02.05.2012 14:59, Warren Block wrote: On Wed, 2 May 2012, Conrad J. Sabatier wrote: On Wed, 2 May 2012 10:03:44 -0400 Robert Huff wrote: Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) My first question as well. This is highly irregular. Some of the misc/compat ports install an old libc.so, but not in place of the real one. ___ 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" libc.so.7 is still current in 9.0, so none of the misc/compat ports should contain it, A quick search shows just that. #cd /usr/ports/misc #grep -H "libc.so" compat*/* compat4x/pkg-plist.freebsd5:%%LIBDIR%%/compat/libc.so.4 compat5x/Makefile:# NOTE: libc.so.5 is built with _PATH_LOCALE defined to compat5x/pkg-plist:@unexec chflags noschg %D/lib/compat/libc.so.5 compat5x/pkg-plist:lib/compat/libc.so.5 compat5x/pkg-plist:%%AMD64%%lib32/compat/libc.so.5 compat6x/pkg-plist.alpha:lib/compat/libc.so.6 compat6x/pkg-plist.amd64:lib/compat/libc.so.6 compat6x/pkg-plist.amd64:lib32/compat/libc.so.6 compat6x/pkg-plist.i386:lib/compat/libc.so.6 compat6x/pkg-plist.sparc64:lib/compat/libc.so.6 -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: portmaster won't update libc.so.7
On Wed, 2 May 2012, Conrad J. Sabatier wrote: On Wed, 2 May 2012 10:03:44 -0400 Robert Huff wrote: Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: When I run: portmaster -a --no-confirm I get the error Installing updates: chflags...///lib/libc.so.7: Operation not permitted Changing chflags (presumably schg, but I tried the others) doesn't appear to make any difference. I'm not running any servers in jails. Any ideas? No, but a question: what is any port doing playing games with part of the base system? (And which port is it?) My first question as well. This is highly irregular. Some of the misc/compat ports install an old libc.so, but not in place of the real one. ___ 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: portmaster won't update libc.so.7
On Wed, 2 May 2012 10:03:44 -0400 Robert Huff wrote: > > Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes: > > > When I run: > > > > portmaster -a --no-confirm > > > > I get the error > > > > Installing updates: chflags...///lib/libc.so.7: Operation not > > permitted > > Changing chflags (presumably schg, but I tried the others) doesn't > > appear to make any difference. > > > > I'm not running any servers in jails. > > > > Any ideas? > > No, but a question: what is any port doing playing games with > part of the base system? > (And which port is it?) > > > Robert huff My first question as well. This is highly irregular. -- Conrad J. Sabatier conr...@cox.net ___ 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: portmaster best practices
Volodymyr Kostyrko wrote: [dd] > > NO_BACKUP means don't create a temporary package when deleting > something. This is unsuitable for me as /usr/ports in my network is > distributed via NFS ro. I also share /usr/ports via NFS ro, but I have defined PACKAGES=/var/tmp/packages in portmaster.rc to store backups of deleted packages, just in case. [dd] -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: portmaster best practices
On Tue, Jan 24, 2012 at 03:49:05PM +0700, Victor Sudakov wrote: > > Generally I like to run 'portsnap fetch update' followed by 'portmaster -ai' > > (after reading /usr/ports/UPDATING) every week. This keeps the number of > > huge > > compilefests (like gettext updates :-() to a minimum. > > Has portmaster ever screwed things up for you? Not really. There have been occasions where some build fails and I have to re-start it. But that is hardly portmaster's fault. The biggest problem is that I have TeXLive installed instead of teTeX. So I have to patch the tex-related ports that I use after using portsnap but before using portmaster. > > For efficiency, I tend to keep one machine up-to-date in that way, > > and use rsync to then distribute the changes in /usr/local to my > > other machines. This only works for machines that are on the same > > major FreeBSD version and architecture, of course. > > That's interesting. Do you also rsync /var/db/pkg ? In the beginning I did, but I found that I didn't do much upgrading/installing on my other machines anyway, so I actually removed /var/db/[pkg|ports] on the other machines. And /usr/ports too. The other thing to sync are of course the configuration files because they tend to differ significantly from machine to machine. I keep git repositories for the config files of all my machines (and jails) on my main desktop (every machine its won repo), and use rsync to distribute them to the machine in question where they are installed locally using ssh. E.g, after the update from 8.2 to 9.0, once the main desktop was done, it was easy to do a 'git diff'on it's config files and see which changes needed to be applied to other machines as well. I do this manually since the files can be very different from machine to machine. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpM8xvVqQC1V.pgp Description: PGP signature
Re: portmaster best practices
Victor Sudakov wrote: If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Greatly depend on where am I. All my systems are staying up-to-date whereas when I'm visiting someones system I prefer to update only required pieces of software. Anyway if you tell portmaster to update port x it would try to update all ports it depends on. Does it often screw things up when updating dependencies (both ascending and descending ones)? Do you recommend to always update the ascending dependencies (portmaster -r) also? I never faced any problems updating ports with portmaster. Mostly because portmaster always backups old libraries to compat folder for me as stated in my configuration file: /usr/local/etc/portmaster.rc: NO_BACKUP=Bopt PM_VERBOSE=vopt SAVE_SHARED=wopt DONT_SCRUB_DISTFILES=Dopt NO_BACKUP means don't create a temporary package when deleting something. This is unsuitable for me as /usr/ports in my network is distributed via NFS ro. PM_VERBOSE increases detail level. SAVE_SHARED is a must, it tells portmaster to propagate deleted shared libraries to compat directory. This way updating any port to newer lib version will have no impact on ports requiring previous versions. DONT_SCRUB_DISTFILES also is redundant for me as /usr/ports is read only and I don't want to drop sources of python 2.5 when building python 2.7 as python2.5 is still needed for AppEngine for example. Personally I never use -r as anything that can be fixed with that one can be fixed with pkg_libchk and careful planning. The better way of debugging such problems for me is pkg_libchk from sysutils/bsdadminscripts. I use sysutils/libchk when I have to, but it is a tedious manual job I would like to avoid. They are almost the same except pkg_libchk doesn't depend on ruby and works in parallel better (for me). -- Sphinx of black quartz judge my vow. ___ 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: portmaster best practices
Roland Smith wrote: > > > > If portaudit shows that some installed packages have vulnerabilities, > > what do you usually do? > > It depends on the vulnerability and what the package does. I will de-install > it if I think that the vulnerability is critical for me and there is no > workaround. > > Look at freshports [http://www.freshports.org/commits.php] regularly to see if > updates for vulnerable packages are available. This is pretty obvious and I run portsnap from cron. > > Generally I like to run 'portsnap fetch update' followed by 'portmaster -ai' > (after reading /usr/ports/UPDATING) every week. This keeps the number of huge > compilefests (like gettext updates :-() to a minimum. Has portmaster ever screwed things up for you? > > For efficiency, I tend to keep one machine up-to-date in that way, > and use rsync to then distribute the changes in /usr/local to my > other machines. This only works for machines that are on the same > major FreeBSD version and architecture, of course. That's interesting. Do you also rsync /var/db/pkg ? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: portmaster best practices
Volodymyr Kostyrko wrote: > > > > If portaudit shows that some installed packages have vulnerabilities, > > what do you usually do? > > Greatly depend on where am I. All my systems are staying up-to-date > whereas when I'm visiting someones system I prefer to update only > required pieces of software. Anyway if you tell portmaster to update > port x it would try to update all ports it depends on. Does it often screw things up when updating dependencies (both ascending and descending ones)? Do you recommend to always update the ascending dependencies (portmaster -r) also? [dd] > The better way of debugging such problems for me is pkg_libchk from > sysutils/bsdadminscripts. I use sysutils/libchk when I have to, but it is a tedious manual job I would like to avoid. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: portmaster best practices
On Mon, Jan 23, 2012 at 05:32:33PM +0700, Victor Sudakov wrote: > Hello portmaster users, > > If portaudit shows that some installed packages have vulnerabilities, > what do you usually do? It depends on the vulnerability and what the package does. I will de-install it if I think that the vulnerability is critical for me and there is no workaround. Look at freshports [http://www.freshports.org/commits.php] regularly to see if updates for vulnerable packages are available. Generally I like to run 'portsnap fetch update' followed by 'portmaster -ai' (after reading /usr/ports/UPDATING) every week. This keeps the number of huge compilefests (like gettext updates :-() to a minimum. For efficiency, I tend to keep one machine up-to-date in that way, and use rsync to then distribute the changes in /usr/local to my other machines. This only works for machines that are on the same major FreeBSD version and architecture, of course. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpWzSSkojAqm.pgp Description: PGP signature
Re: portmaster best practices
On 23 January 2012 05:32, Victor Sudakov wrote: > Hello portmaster users, > > If portaudit shows that some installed packages have vulnerabilities, > what do you usually do? > > Do you upgrade only the vulnerable packages, or vulnerable packages > and dependent packages (portmaster -r), or perhaps all packages > (portmaster -a)? Or do you "pkg_delete -a" all packages first and then > reinstall from scratch (from `portmaster --list-origins` perhaps)? > > I am a bit uneasy about "portmaster -a" because, for example, in the > output below it intends to install a package which is already > installed: > > > pg01-sibptus# portmaster -n -a > ===>>> Gathering distinfo list for installed ports > > [dd] > Upgrade php5-ldap-5.3.5_1 to php5-ldap-5.3.9 > Install net/openldap24-sasl-client > Upgrade postgresql-server-9.0.1 to postgresql-server-9.0.6_3 > Upgrade tcl-8.5.9 to tcl-8.5.11 > Upgrade vim-7.3.81 to vim-7.3.121 > Install devel/gettext > > ===>>> Proceed? y/n [y] n > > ===>>> If you would like to upgrade or install some, but not > all of the above try adding '-i' to the command line. > pg01-sibptus# > pg01-sibptus# > pg01-sibptus# pkg_info -xo openldap > Information for openldap-sasl-client-2.4.24: > > Origin: > net/openldap24-client As I general rule, I don't run "portmaster -a" Variations on -r usually succeed (-R -r is quite useful), though if it pulls in too many very large dependencies (firefox, chrome, open- or libre-office, most anything KDE/QT), I'll sometimes remove those before starting a "portmaster -R -r" type of run. It does require more typing to hand-specify the ports to be upgraded, but I end up with far fewer "Whoops!" moments. -- -- ___ 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: portmaster best practices
Victor Sudakov wrote: Hello portmaster users, If portaudit shows that some installed packages have vulnerabilities, what do you usually do? Greatly depend on where am I. All my systems are staying up-to-date whereas when I'm visiting someones system I prefer to update only required pieces of software. Anyway if you tell portmaster to update port x it would try to update all ports it depends on. Do you upgrade only the vulnerable packages, or vulnerable packages and dependent packages (portmaster -r), or perhaps all packages (portmaster -a)? Or do you "pkg_delete -a" all packages first and then reinstall from scratch (from `portmaster --list-origins` perhaps)? I am a bit uneasy about "portmaster -a" because, for example, in the output below it intends to install a package which is already installed: pg01-sibptus# portmaster -n -a ===>>> Gathering distinfo list for installed ports [dd] Upgrade php5-ldap-5.3.5_1 to php5-ldap-5.3.9 Install net/openldap24-sasl-client Upgrade postgresql-server-9.0.1 to postgresql-server-9.0.6_3 Upgrade tcl-8.5.9 to tcl-8.5.11 Upgrade vim-7.3.81 to vim-7.3.121 Install devel/gettext ===>>> Proceed? y/n [y] n ===>>> If you would like to upgrade or install some, but not all of the above try adding '-i' to the command line. pg01-sibptus# pg01-sibptus# pg01-sibptus# pkg_info -xo openldap Information for openldap-sasl-client-2.4.24: Origin: net/openldap24-client As far as I recall there was some glitches with correct detection of openldap24-client presence (some symbols moving around or so). Generally I never pay attention to this glitches and when (or if) update process fails I try to recompile mentioned port with portmaster. Then update process can be continued with `portmaster -a`. The better way of debugging such problems for me is pkg_libchk from sysutils/bsdadminscripts. -- Sphinx of black quartz judge my vow. ___ 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: "portmaster --list-origins" question
On Thu, 29 Dec 2011 11:44:57 +0100 Christer Solskogen wrote: >On Thu, Dec 29, 2011 at 5:58 AM, Scott Bennett wrote: > >> =C2=A0 =C2=A0 Did I misunderstand something about the --list-origins opti= >on? =C2=A0Or have >> I run into a bug? =C2=A0Any suggestions of how to proceed would be welcom= >e. > >No, not a bug. >portmaster --list-origins | wc -l >58 >pkg_info | wc -l > 207 > >list-origins only lists packages that does not have any dependencies. > Ah, yes. I now see that I missed the part of the man page that says, "list directories from /usr/ports for root and leaf ports". Sigh. Thanks much for your direct reply, which I did see when it arrived, but was too tired at that point to reply to. At this point, the process has to be put on hold for the weekend, but I hope to proceed Monday night. Thanks again for your response! Also, I replied to Victor Sudakov directly, but neglected to Cc: this list, for which I apologize to anyone concerned. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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: "portmaster --list-origins" question
On Thu, Dec 29, 2011 at 5:58 AM, Scott Bennett wrote: > Did I misunderstand something about the --list-origins option? Or have > I run into a bug? Any suggestions of how to proceed would be welcome. No, not a bug. portmaster --list-origins | wc -l 58 pkg_info | wc -l 207 list-origins only lists packages that does not have any dependencies. -- chs, ___ 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: "portmaster --list-origins" question
Scott Bennett wrote: > have quite a few windowmaker-related ports installed. Only one of those > related ports appeared in the portmaster output, and windowmaker itself was > absent, so I looked at the numbers next. I think --list-origins lists only leaf packages and not dependencies. It is strange however that windowmaker itself was absent. What does 'pkg_info -xrR windowmaker' show? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: portmaster -r libnotify-0 problems
> > On 10/09/2011 16:12, Scott Ballantyne wrote: > > gnome-art is peculiar. There is nothing in that directory but the work > > directory, no makefile or anything. And nothing I can find in UPDATE > > about alacarte or gnome-art. > >=20 > > Any further thoughts, if you have time? > > That is an ex-port. > > lucid-nonsense:/usr/ports:# grep gnome-art MOVED > x11-themes/gnome-art||2011-08-02|Has expired: Upcoming ruby-gnome > removes dependencies > > Kicked the bucket, shuffled off this mortal coil, run down the curtain > and joined the bleeding choir invisible. > > Suggest you update your ports tree using csup(1) or portsnap(1) -- if > necessary by blowing away what you already have under /usr/ports and > starting from scratch. Seems that your current tree is in an > inconsistent state. > Thanks again, Mathew. I csuped already, but will nuke the ports and start again. Thanks again so much for your generous help. Scott -- s...@ssr.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: portmaster -r libnotify-0 problems
On 10/09/2011 16:12, Scott Ballantyne wrote: > gnome-art is peculiar. There is nothing in that directory but the work > directory, no makefile or anything. And nothing I can find in UPDATE > about alacarte or gnome-art. > > Any further thoughts, if you have time? That is an ex-port. lucid-nonsense:/usr/ports:# grep gnome-art MOVED x11-themes/gnome-art||2011-08-02|Has expired: Upcoming ruby-gnome removes dependencies Kicked the bucket, shuffled off this mortal coil, run down the curtain and joined the bleeding choir invisible. Suggest you update your ports tree using csup(1) or portsnap(1) -- if necessary by blowing away what you already have under /usr/ports and starting from scratch. Seems that your current tree is in an inconsistent state. 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: portmaster -r libnotify-0 problems
Hi Mathew, > On 09/09/2011 15:13, Scott Ballantyne wrote: > > I've been trying to update libnotify and libproxy following the > > instructions in UPDATING, which is to do > > > > portmaster -r libnotify-0 > > > > This trys to install ghostscript9, and fails. Apparently ghostscript9 > > conflicts with ghostscript8-8.71_6, which presumably is the reason for > > the failure. > > > > Could someone help me resolve this? The obvious solution of pkg_delete > > ghostscript8-8.71_6 doesn't work, because too many installed ports > > depend on ghostscript8-8.71_6. > > There are two approaches you might take here. Either > >* replace ghostscript8 with ghostscript9 > > or > >* work out why libnotify triggers a dependency on ghostscript9 > and try and make it use ghostscript8 (or nothing) instead. > > The first is a relatively mechanical process, which should work fine > from the point of view of doing all the port wrangling, but might result > in further ghostscript8 vs ghostscript9 problems down the line. > Just run: > > # portmaster -o print/ghostscript9 ghostscript8- > > That will change the dependency settings in your /var/db/pkg directory, > which may or may not be appropriate for all ghostscript dependent ports, > and indeed some may not work at all. (Although I rather doubt the > simply not-working thing: functionality between those versions hasn't > changed much at all.) > > The second is a more satisfying fix. Lets see... Try defining > >WITH_GHOSTSCRIPT_VER=8 > > in /etc/make.conf (the default is 9 nowadays) -- then try reinstalling > libnotify according to the instructions in UPDATING. > > Read /usr/ports/Mk/bsd.port.mk for the details -- search for GHOSTSCRIPT > to find the relevant bits. > Thanks so much, I am in your debt. However, I also feel that I am in maze of twisty little passages, all different. The next step here is to portmaster -r libproxy-0, where I get: --- ===>>> Currently installed version: libproxy-0.4.6 ===>>> Port directory: /usr/ports/net/libproxy ===>>> Gathering distinfo list for installed ports ===>>> Launching 'make checksum' for net/libproxy in background ===>>> Gathering dependency list for net/libproxy from ports ===>>> Initial dependency check complete for net/libproxy ===>>> Checking ports that depend on libproxy-0.4.6 ===>>> Launching child to reinstall alacarte-0.13.2_1 libproxy-0.4.6 >> alacarte-0.13.2_1 ===>>> Port directory: /usr/ports/deskutils/alacarte ===>>> No DISTINFO_FILE in /usr/ports/x11-themes/gnome-art ===>>> Aborting update Terminated Terminated ===>>> Update for alacarte-0.13.2_1 failed ===>>> Aborting update -- gnome-art is peculiar. There is nothing in that directory but the work directory, no makefile or anything. And nothing I can find in UPDATE about alacarte or gnome-art. Any further thoughts, if you have time? Thanks again, Scott ___ 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: portmaster -r libnotify-0 problems
On 09/09/2011 15:13, Scott Ballantyne wrote: > I've been trying to update libnotify and libproxy following the > instructions in UPDATING, which is to do > > portmaster -r libnotify-0 > > This trys to install ghostscript9, and fails. Apparently ghostscript9 > conflicts with ghostscript8-8.71_6, which presumably is the reason for > the failure. > > Could someone help me resolve this? The obvious solution of pkg_delete > ghostscript8-8.71_6 doesn't work, because too many installed ports > depend on ghostscript8-8.71_6. There are two approaches you might take here. Either * replace ghostscript8 with ghostscript9 or * work out why libnotify triggers a dependency on ghostscript9 and try and make it use ghostscript8 (or nothing) instead. The first is a relatively mechanical process, which should work fine from the point of view of doing all the port wrangling, but might result in further ghostscript8 vs ghostscript9 problems down the line. Just run: # portmaster -o print/ghostscript9 ghostscript8- That will change the dependency settings in your /var/db/pkg directory, which may or may not be appropriate for all ghostscript dependent ports, and indeed some may not work at all. (Although I rather doubt the simply not-working thing: functionality between those versions hasn't changed much at all.) The second is a more satisfying fix. Lets see... Try defining WITH_GHOSTSCRIPT_VER=8 in /etc/make.conf (the default is 9 nowadays) -- then try reinstalling libnotify according to the instructions in UPDATING. Read /usr/ports/Mk/bsd.port.mk for the details -- search for GHOSTSCRIPT to find the relevant bits. 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: portmaster -a -B -d
Op 28-8-2011 16:27, Matthew Seaman schreef: Ideally ports committers should bump the eaccelerator PORTREVISION to make ports management tools do that automatically, but if not, you're going to have to remember to do it by hand. Thank you for your explanation. I enjoyed reading it and learned a lot from 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: portmaster -a -B -d
On 28/08/2011 13:38, Dick Hoogendijk wrote: > A few days back I did a "portmaster -a -B -d" but later on I found out > that one port (www/eAccelerator) complained about being compiled for > another version of PHP (which by then was updated by portmaster). I > expected portmaster to take care of these kind of dependencies. Where am > I wrong in this assumption? eaccelerator is an oddity. It only works properly with the version of PHP it was compiled against. Unfortunately there isn't a good automatic mechanism in ports to say "recompile this port, because something it depends on was upgraded." It's like something that depends on a shlib in that respect, that needs to be rebuilt when the shlib ABI version changes. While it might be possible to do hackish things, like include the PHP pkg version string into the eaccelerator pkg version, on the whole the correct solution seems to be to reinstall eaccelerator each time PHP gets a significant upgrade. Ideally ports committers should bump the eaccelerator PORTREVISION to make ports management tools do that automatically, but if not, you're going to have to remember to do it by hand. 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: "portmaster -a" command fails - *** Error code 1
On Fri, 04 Mar 2011 18:37:32 + Arthur Chance wrote: > On 03/04/11 17:36, Ed Flecko wrote: > > Thanks Aurthur. > > > > :-) > > > > It's funny...I DID what it asks and it still didn't work (make > > deinstall, etc.). > ... > > Apparently, I installed it from a package, so I did a pkg_delete > > automake and then started my portmaster -a again and it seems to be > > running fine. > > Ah, the third option which I forgot to mention. It's always the > option one forgets to mention that works. > > In theory package install and port install are supposed to be the > same (modulo config options). In practice there are odd cases, and > automake seems to provoke them. Thinking back, I've had to pkg_delete > it before now in order to upgrade, and I always install from ports. It's not really a matter of ports verses packages, a make deinstall calls pkg_delete. The suggestion "You may wish to ``make deinstall'' and install this port again..." shouldn't be taken too seriously, since it just a standard response to a make install on an already installed port. It probably fails because what's needed is to delete the package, not delete and reinstall. ___ 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: "portmaster -a" command fails - *** Error code 1
these situations arise quite often where you have to delete a port before portmaster will continue. sometimes you can predict it by reading /usr/ports/UPDATING not that this is the only reason to read UPDATING. On 3/4/11 1:37 PM, "Arthur Chance" wrote: >On 03/04/11 17:36, Ed Flecko wrote: >> Thanks Aurthur. >> >> :-) >> >> It's funny...I DID what it asks and it still didn't work (make >>deinstall, etc.). > >A tip for the future: always say what you've tried. It lets us save our >waning mind reading powers for important cases, like working out what >the wife actually wants for her birthday when all she says is "oh, any >little thing will do". :-) > >> Apparently, I installed it from a package, so I did a pkg_delete >> automake and then started my portmaster -a again and it seems to be >> running fine. > >Ah, the third option which I forgot to mention. It's always the option >one forgets to mention that works. > >In theory package install and port install are supposed to be the same >(modulo config options). In practice there are odd cases, and automake >seems to provoke them. Thinking back, I've had to pkg_delete it before >now in order to upgrade, and I always install from ports. > >___ >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"
Re: "portmaster -a" command fails - *** Error code 1
On 03/04/11 17:36, Ed Flecko wrote: Thanks Aurthur. :-) It's funny...I DID what it asks and it still didn't work (make deinstall, etc.). A tip for the future: always say what you've tried. It lets us save our waning mind reading powers for important cases, like working out what the wife actually wants for her birthday when all she says is "oh, any little thing will do". :-) Apparently, I installed it from a package, so I did a pkg_delete automake and then started my portmaster -a again and it seems to be running fine. Ah, the third option which I forgot to mention. It's always the option one forgets to mention that works. In theory package install and port install are supposed to be the same (modulo config options). In practice there are odd cases, and automake seems to provoke them. Thinking back, I've had to pkg_delete it before now in order to upgrade, and I always install from ports. ___ 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: "portmaster -a" command fails - *** Error code 1
Thanks Aurthur. :-) It's funny...I DID what it asks and it still didn't work (make deinstall, etc.). Apparently, I installed it from a package, so I did a pkg_delete automake and then started my portmaster -a again and it seems to be running fine. :-) Ed ___ 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: "portmaster -a" command fails - *** Error code 1
On 03/04/11 17:00, Ed Flecko wrote: Thanks gentlemen; I was not running portmaster as root. When I re-run portmaster -a as root, I get the following: ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for devel/automake from ports ===>>> Dependency check complete for devel/automake en-freebsd-doc-20100625>> textproc/docproj-nojadetex>> graphics/netpbm>> graphics/jasper>> graphics/libglut>> x11-toolkits/libXmu>> x11-toolkits/libXt>> x11/libSM>> devel/automake ===> Installing for automake-1.11.1 ===>Generating temporary packing list ===> Checking if devel/automake already installed ===>automake-1.11.1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/automake without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /usr/ports/devel/automake. Suggestions? Do what it says? make -C /usr/ports/devel/automake deinstall reinstall or maybe (note the lack of "-a" here) env FORCE_PKG_REGISTER=yes portmaster devel/automake and then try portmaster -a 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"
Re: "portmaster -a" command fails - *** Error code 1
Thanks gentlemen; I was not running portmaster as root. When I re-run portmaster -a as root, I get the following: ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for devel/automake from ports ===>>> Dependency check complete for devel/automake en-freebsd-doc-20100625 >> textproc/docproj-nojadetex >> graphics/netpbm >> graphics/jasper >> graphics/libglut >> x11-toolkits/libXmu >> x11-toolkits/libXt >> x11/libSM >> devel/automake ===> Installing for automake-1.11.1 ===> Generating temporary packing list ===> Checking if devel/automake already installed ===> automake-1.11.1 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/automake without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /usr/ports/devel/automake. Suggestions? Thank you, Ed ___ 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: "portmaster -a" command fails - *** Error code 1
On 03/04/11 15:37, Ed Flecko wrote: [Snips] Given this: ===>/usr/ports/textproc/docproj-nojadetex/work not writable, skipping Any ideas on what my problem(s) is and how to solve it??? Either you've got a read-only /usr/ports or you've forgotten to run as root. [I will admit to doing the latter occasionally.] ___ 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: portmaster -afv -no-confirm --clean-distfiles-all command - too much automation???
Hmmm...I'll check that out Bruce. I saw the command listed on: http://www.freebsd.org/doc/handbook/ports-using.html but it doesn't give any cautions against using it. Thank you, Ed ___ 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: portmaster -afv -no-confirm --clean-distfiles-all command - too much automation???
On Wed, 2 Mar 2011 09:57:14 -0800 Ed Flecko wrote: > Do you think that's a little too much automation, or do you think that > would be pretty safe to run without screwing things up? I think portmaster's documentation explicitly advises against using -af to rebuild all ports. See the man page for details. -- Bruce Cran ___ 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: portmaster upgrade of p5-IO-Socket-SSL fails
On 1/23/11 10:12 AM, Jens Jahnke wrote: > Hi, > > On Sun, 23 Jan 2011 09:42:58 -0800 > David Newman wrote: > > DN> FreeBSD 8.0-RELEASE-p4 amd64 > DN> > DN> The command 'portmaster security/p5-IO-Socket-SSL' fails because the > DN> module is not found in any archive. I've pasted the error output > DN> below. > > I had this issue on 8.1-RELEASE amd64 but after round about a day the > module showed up in the archives queried. Thanks. It only occurred to me after posting to email the maintainer for this port, who responded that there was a mistake in posting a bad update. Refreshing ports and rerunning portmaster works fine now. dn ___ 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: portmaster upgrade of p5-IO-Socket-SSL fails
Hi, On Sun, 23 Jan 2011 09:42:58 -0800 David Newman wrote: DN> FreeBSD 8.0-RELEASE-p4 amd64 DN> DN> The command 'portmaster security/p5-IO-Socket-SSL' fails because the DN> module is not found in any archive. I've pasted the error output DN> below. I had this issue on 8.1-RELEASE amd64 but after round about a day the module showed up in the archives queried. Regards, Jens -- 23. Hartung 2011, 19:11 Homepage : http://www.jan0sch.de That's one small step for a man; one giant leap for mankind. -- Neil Armstrong pgp0hmcfJesEw.pgp Description: PGP signature
Re: Portmaster general questions and problems
On Thu, Dec 30, 2010 at 9:34 AM, Warren Block wrote: > Those look backwards to me. It's extremely rare for me to upgrade > everything that a given port depends on (-R), but common to upgrade a port > and everything that depends on it (-r). I've used -R before to correct situations where a freshly built port misbehaves due to some of its dependencies being too old. It's also sometimes handy when there are ABI changes involved, as sometimes happens with things like Perl and PHP. ___ 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: Portmaster general questions and problems
On Thu, 30 Dec 2010, Thomas Mueller wrote: Threads about portmaster and portupgrade status raise the question, what flags for portmaster are comparable to -R and -r for portupgrade? I might want to portupgrade a package and all its dependencies (-R), or less frequently, all packages that depend on the package to be portupgraded (-r). How would I do that using portmaster? I read both man pages many times. Those look backwards to me. It's extremely rare for me to upgrade everything that a given port depends on (-R), but common to upgrade a port and everything that depends on it (-r). Anyway... as I understand the man pages: "portmaster ..."= "portupgrade -r ..." "portmaster -r ..." = "portupgrade -rf ..." ___ 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: Portmaster general questions and problems
On Thu, 30 Dec 2010 12:47:59 +0100 "Christopher J. Ruwe" wrote: > On Thu, 30 Dec 2010 10:59:49 + > "Thomas Mueller" wrote: > > > Threads about portmaster and portupgrade status raise the question, > > what flags for portmaster are comparable to -R and -r for > > portupgrade? > > > > I might want to portupgrade a package and all its dependencies (-R), > > or less frequently, all packages that depend on the package to be > > portupgraded (-r). How would I do that using portmaster? I read > > both man pages many times. > > > > Tom > > > > ___ > > 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" > > Hi Tom, > > I never gave it much thought, however, I am under the impression that > portmaster does not require an explicit flag to do that. > > When installing some port, then I use portmaster -D /usr/port/ port path>, the -D determining that I do not want to be prompted > whether to retain the old distfiles or not, but to retain them (-d > being the converse and deleting old distfiles). Using portmaster in > the way described checks for dependencies and automagically updates > them in case there are newer available. > > Cheers, Sorry for missing one part (the -r) of your question ... how does "[-R] -r name/glob of port directory in /var/db/pkg rebuild the specified port, and all ports that depend on it" in the portmaster man page sound to you and does it do what you a requiring? cheers, -- Christopher J. Ruwe TZ GMT + 1 signature.asc Description: PGP signature
Re: Portmaster general questions and problems
On Thu, 30 Dec 2010 10:59:49 + "Thomas Mueller" wrote: > Threads about portmaster and portupgrade status raise the question, > what flags for portmaster are comparable to -R and -r for portupgrade? > > I might want to portupgrade a package and all its dependencies (-R), > or less frequently, all packages that depend on the package to be > portupgraded (-r). How would I do that using portmaster? I read > both man pages many times. > > Tom > > ___ > 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" Hi Tom, I never gave it much thought, however, I am under the impression that portmaster does not require an explicit flag to do that. When installing some port, then I use portmaster -D /usr/port/, the -D determining that I do not want to be prompted whether to retain the old distfiles or not, but to retain them (-d being the converse and deleting old distfiles). Using portmaster in the way described checks for dependencies and automagically updates them in case there are newer available. Cheers, -- Christopher J. Ruwe TZ GMT + 1 signature.asc Description: PGP signature
Re: Portmaster general questions and problems
Threads about portmaster and portupgrade status raise the question, what flags for portmaster are comparable to -R and -r for portupgrade? I might want to portupgrade a package and all its dependencies (-R), or less frequently, all packages that depend on the package to be portupgraded (-r). How would I do that using portmaster? I read both man pages many times. Tom ___ 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: portmaster problems upgrading to php 5.3.4
2010/12/28 Maciej Milewski : > Have you read /usr/ports/UPDATING? > There is a note: > 20101208: > AFFECTS: autotools > AUTHOR: autoto...@freebsd.org > > Another stage in the autotools cleanup that reduces tree churn whilst > updating components, a number of ports have now moved to non-versioned > locations since there is now only the concept of legacy and current > versions. > > # portmaster -o devel/autoconf devel/autoconf268 > # portmaster -o devel/automake devel/automake111 > # portmaster -o devel/libtool devel/libtool22 > # portmaster -o devel/libltdl devel/libltdl22 Awesome, that fixed my problem. Thanks very much! I hadn't seen that note in /usr/ports/UPDATING so I appreciate you pointing it out. And I just ran this on all my servers and everything is now up to date, cool! Cheers, Kelly ___ 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: portmaster problems upgrading to php 5.3.4
On 28/12/2010 22:07, Kelly Martin wrote: > I should also mention that I have an almost-identical server running > FreeBSD 7.3-release-p2 in backup production and did not experience > these problems when upgrading from php 5.3.3_2 to php 5.3.4. Something > in my 8.1-release development server is causing the problems with > upgrading PHP, so I'm reluctant to upgrade my production servers as > they are absolutely identical until I find a fix. Try running 'portmaster --check-depends', then retry the update. If it still fails, then choose one or more of the php5 modules that fails and do a forced update of it and all of its dependencies: eg # portmaster -f php5-mcrypt-5.3.3_2 This will re-install quite a lot of packages, so be prepared for it to take a while. Something like this list, although details will vary depending on your configuration: #pkg_info -rRx php5-mcrypt Information for php5-mcrypt-5.3.4: Depends on: Dependency: expat-2.0.1_1 Dependency: openssl-1.0.0_4 Dependency: libmcrypt-2.5.8 Dependency: perl-5.10.1_3 Dependency: pkg-config-0.25_1 Dependency: pcre-8.10 Dependency: libltdl-2.2.10 Dependency: mysql-client-5.1.54_1 Dependency: db48-4.8.30.0 Dependency: libiconv-1.13.1_1 Dependency: libxml2-2.7.8_1 Dependency: apr-ipv6-devrandom-db48-mysql51-1.4.2.1.3.10 Dependency: apache-2.2.17_1 Dependency: php5-5.3.4 After that you should be able to finish off the updates as usual. Oh -- beware of the extension.ini ordering problem. If php starts crashing on you after the update, it's probably because the order of the modules in /usr/local/etc/php/extensions.ini has changed and needs to be edited back to something workable. 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: portmaster problems upgrading to php 5.3.4
I should also mention that I have an almost-identical server running FreeBSD 7.3-release-p2 in backup production and did not experience these problems when upgrading from php 5.3.3_2 to php 5.3.4. Something in my 8.1-release development server is causing the problems with upgrading PHP, so I'm reluctant to upgrade my production servers as they are absolutely identical until I find a fix. Thanks, Kelly ___ 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: Portmaster general questions and problems
FYI, I agree with most of what b.f. wrote, and I thank him for answering this. I don't follow -questions anymore, so it's very helpful when I get cc'ed on posts about portmaster. A few additional thoughts ... On 12/26/2010 21:13, b. f. wrote: I'm trying to figure out what I'm doing wrong or what I don't understand about portmaster. I've looked on google and can't find any documentation that isn't just basic stuff or rehashes of the man pages (which are fine for reference, but not helpful in understanding how to use it). This shouldn't be difficult: portmaster isn't a clone of portupgrade, but the command-line options and behavior of the two are similar. Portmaster is actually somewhat easier to use because you don't have to worry about the extra databases that portupgrade uses. The portmaster manpage is fairly well written, and the EXAMPLES section demonstrates most of what the average user will need. +1. :) I have spent considerable time on the man page, and encourage you to actually read it, beginning to end. It should give you all the information you need about how portmaster works. The most important thing to keep in mind is that (as b.f. pointed out above) portmaster is not a clone of portupgrade, nor was it ever designed to be. Portmaster also doesn't seem to understand when ports are already up-to-date, so doing this: portmaster php5-* To update all the php5 ports causes portmaster to re-install things that are already up to date. Is this expected behavior? Yes. If you had read the man page you would have known that. :) Also, the * at the end is not necessary. if so, how can I upgrade ports without typing each one my hand. I'd rather not run portmaster with -a since I don't want to blindly update everything. The man page contains an example of an alias that you can use to wrap 'portmaster -L' to give you a concise output of what ports need updating. Then you could do something like: portmaster php-port1 php-port2 php-port3 to only update that subset of ports that you want. Meanwhile, -a is usually the safest route, and some of the problems you are experiencing (in addition to not following the instructions in UPDATING) may be due to the fact that you're trying to outsmart the maintainers of all of your ports. :) hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: Portmaster general questions and problems
> I had been using portupgrade for several years and never had any > problems and upgrading ports was quick and simple process every week. > But, due to portupgrade no longer being maintained and failing to work > anymore, I have switched to using portmaster and am having nothing but > problems, so much so that I dread updating my ports. It isn't that portupgrade is completely unmaintained, just that the former author and other contributors are busy, and don't spend as much time on it. And there isn't as much pressure for them to do so, because portmaster can now serve as a replacement for most purposes. > > I'm trying to figure out what I'm doing wrong or what I don't > understand about portmaster. I've looked on google and can't find any > documentation that isn't just basic stuff or rehashes of the man pages > (which are fine for reference, but not helpful in understanding how to > use it). This shouldn't be difficult: portmaster isn't a clone of portupgrade, but the command-line options and behavior of the two are similar. Portmaster is actually somewhat easier to use because you don't have to worry about the extra databases that portupgrade uses. The portmaster manpage is fairly well written, and the EXAMPLES section demonstrates most of what the average user will need. > > Here is an example of a problem I run into all the time: > > I went to update php and I got this: > > ===>>> Starting check for runtime dependencies > ===>>> Gathering dependency list for devel/libltdl from ports > ===>>> No dependencies for devel/libltdl > ===> Installing for libltdl-2.2.10 > ===> Generating temporary packing list > ===> Checking if devel/libltdl already installed > ===> libltdl-2.2.10 is already installed > You may wish to ``make deinstall'' and install this port again > by ``make reinstall'' to upgrade it properly. > If you really wish to overwrite the old port of devel/libltdl > without deleting it first, set the variable "FORCE_PKG_REGISTER" > in your environment or the "make install" command line. > *** Error code 1 > > Stop in /usr/ports/devel/libltdl. > > ok, so libltdl-2.2.10 is already installed? Why is that an issue? > Why doesn't portmaster just happily skip it since it's already > installed? What am I not understanding here? Or am I using portmaster > wrong? Remember that portmaster is just a helper script, and that it relies on the ports infrastructure to perform many tasks, just as portupgrade does. So problems like this may occasionally arise from a problem with portmaster, but more often they are a problem within the ports tree itself. Here you are probably running afoul of the recent autotools changes. Make sure that your entire ports tree is up-to-date, and then read the 20101208 entry in ports/UPDATING and follow the instructions there (or just deinstall all of the old autotools -- the new versions should be automatically installed as needed). You should routinely read the latest entries in ports/UPDATING before updates, as recommended, to avoid these kinds of problems. > > Portmaster also doesn't seem to understand when ports are already > up-to-date, so doing this: > > portmaster php5-* > > To update all the php5 ports causes portmaster to re-install things > that are already up to date. Is this expected behavior? if so, how > can I upgrade ports without typing each one my hand. I'd rather not > run portmaster with -a since I don't want to blindly update everything. This is not the expected behavior, and portmaster is designed to avoid the need for most individual updates, and to update as few ports as possible by default. In fact, it's default settings are more conservative in this regard than are those of portupgrade. Are you sure that it is actually doing more than is needed? If you provide build transcripts, and lists of what ports/packages are installed on your machine, then we may be able to see if this is the case. > > Is there a good tutorial on portmaster somewhere that can help an some > get started with it? Is portmaster the best tool for updating ports? Read the portmaster manpage, particularly the EXAMPLES section. Yes, right now portmaster is probably the best choice of updating software for the average user in the Ports tree. I use my own scripts, but then I just want speed, and not all of the portmaster features, and I can fix things when there are problems. 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: Portmaster general questions and problems
On 12/26/10 11:45 AM, Bruce Cran wrote: > On Sun, 26 Dec 2010 11:39:58 -0800 > "Ron (Lists)" wrote: > >> ok, so libltdl-2.2.10 is already installed? Why is that an issue? >> Why doesn't portmaster just happily skip it since it's already >> installed? What am I not understanding here? Or am I using >> portmaster wrong? > > That's a problem I've come across before too - I'd be interested to > know what's going wrong too. This is covered in /usr/ports/UPDATING as part of the autotools cleanup. Just search for the date '20101208' and follow the instructions in that note. It's a good idea to check the UPDATING file before running 'portmaster -a' or anytime you have problems with portmaster. dn ___ 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 status [Was Re: Portmaster general questions and problems]
On Sun, Dec 26, 2010 at 13:42, Bob Hall wrote: > On Sun, Dec 26, 2010 at 11:39:58AM -0800, Ron (Lists) wrote: >> But, due to portupgrade no longer being maintained and failing to work >> anymore, > > I'm a bit confused about this. I did a quick google search and saw that > someone had stopped maintaining portupgrade, but I also saw things that > suggested that other people were maintaining it. The handbook continues > to list it ahead of portmanager and portmaster, with no mention that it > isn't being maintained. I've never stopped using portupgrade, and it has > always worked. Updates come through periodically, two in the past month. > For a port that isn't being maintained, it seems to be remarkably well > maintained. I assume you are referring to my message from a couple months ago. At the time, the previous maintainer dropped it and transferred it to a mailing list. There had been no commits for around a year and a half. I am personally skeptical of anything maintained by a mailing list, because that seems to frequently lead to patches and bug reports being ignored for months or years. Then, the removal of MD5 distinfo broke it and it stayed broken for over a week with no indication given that a fix was in the works. On the other hand, Doug Barton has been very responsive to issues with portmaster and fixed this problem less than 48 hours after it appeared. Hence my recommendation to switch. -- Rob Farmer ___ 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: Portmaster general questions and problems
On Sun, 26 Dec 2010 11:39:58 -0800 "Ron (Lists)" wrote: > ===> Checking if devel/libltdl already installed > ===> libltdl-2.2.10 is already installed > You may wish to ``make deinstall'' and install this port again > by ``make reinstall'' to upgrade it properly. > If you really wish to overwrite the old port of devel/libltdl > without deleting it first, set the variable "FORCE_PKG_REGISTER" > in your environment or the "make install" command line. > *** Error code 1 > > Stop in /usr/ports/devel/libltdl. > > ok, so libltdl-2.2.10 is already installed? Why is that an issue? > Why doesn't portmaster just happily skip it since it's already > installed? What am I not understanding here? Or am I using > portmaster wrong? When a port gets built, the ports system looks for and installs any missing dependencies. As several different ports may satisfy a dependency the ports system looks for the functionality, a key executable, library etc, rather than a specific installed package. The error you see can occur when the port thinks it need to install a missing dependency port, but that install fails due to an existing entry in /var/db/pkg. This happens either because the appropriate files are missing or the port is looking for the wrong thing in the first place. It may be due to a mistake by the port maintainer or, more likely, a failure to deal with UPDATING entries correctly. ___ 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 status [Was Re: Portmaster general questions and problems]
On Sun, Dec 26, 2010 at 11:39:58AM -0800, Ron (Lists) wrote: > But, due to portupgrade no longer being maintained and failing to work > anymore, I'm a bit confused about this. I did a quick google search and saw that someone had stopped maintaining portupgrade, but I also saw things that suggested that other people were maintaining it. The handbook continues to list it ahead of portmanager and portmaster, with no mention that it isn't being maintained. I've never stopped using portupgrade, and it has always worked. Updates come through periodically, two in the past month. For a port that isn't being maintained, it seems to be remarkably well maintained. ___ 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: Portmaster general questions and problems
On Sun, Dec 26, 2010 at 1:39 PM, Ron (Lists) wrote: > I had been using portupgrade for several years and never had any problems > and upgrading ports was quick and simple process every week. But, due to > portupgrade no longer being maintained and failing to work anymore, I have > switched to using portmaster and am having nothing but problems, so much so > that I dread updating my ports. > > I'm trying to figure out what I'm doing wrong or what I don't understand > about portmaster. I've looked on google and can't find any documentation > that isn't just basic stuff or rehashes of the man pages (which are fine for > reference, but not helpful in understanding how to use it). > I'm pretty sure this is a problem with a port and it's depends listing or something and not specific to portmaster. This should be relatively easy to test, try it with portupgrade/portmanager instead on the same ports tree. Your implication that this sort of thing didn't happen on portupgrade directly contradicts my experience. You'll probably get better help on freebsd-ports@ although there are people on this list that can help but list activity is low right now. Anyway I also see there a recent entry in UPDATING about libltdl. -- Adam Vande More ___ 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: Portmaster general questions and problems
On Sun, Dec 26, 2010 at 2:45 PM, Bruce Cran wrote: > On Sun, 26 Dec 2010 11:39:58 -0800 > "Ron (Lists)" wrote: > > > ok, so libltdl-2.2.10 is already installed? Why is that an issue? > > Why doesn't portmaster just happily skip it since it's already > > installed? What am I not understanding here? Or am I using > > portmaster wrong? > > That's a problem I've come across before too - I'd be interested to > know what's going wrong too. > it sounds like there might be an erronous alias or wrapper-script that is changing the options of portmaster, maybe even a global in /etc/rc.conf? What does the following give you. 'alias | grep portmaster' For me, I get the following; [r...@ziggy [~]# alias | grep port alias portmaster='portmaster -d --no-confirm' [r...@ziggy [~]# grep port .bashrc alias portmaster="portmaster -d --no-confirm" [r...@ziggy [~]# as you can see, these options are expected for me. As option of '-f' is what it sounds like is being called in your case, to force-reinstall everything named from the cmdln. HTH/C- ___ 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: Portmaster general questions and problems
On Sun, 26 Dec 2010 11:39:58 -0800 "Ron (Lists)" wrote: > ok, so libltdl-2.2.10 is already installed? Why is that an issue? > Why doesn't portmaster just happily skip it since it's already > installed? What am I not understanding here? Or am I using > portmaster wrong? That's a problem I've come across before too - I'd be interested to know what's going wrong too. -- Bruce Cran ___ 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: Portmaster recursion problem
On 19/12/2010 17:03, Ron (Lists) wrote: > ===>>> Launching child to update devel/autoconf > devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> > perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> > apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> > devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> > perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> > apache-2.2.17 >> devel/autoconf > > This just keeps going and going. I've tried upgrading other ports and > they all do the same thing (with slightly different packages). This is a classic symptom of putting USE_FOO into a Makefile with global scope -- typically /etc/make.conf Don't do that. USE_FOO flags are for port maintainers to use in port specific Makefiles. They do things like make the port have a dependency on apache. Which is no good if you apply it to /every/ /single/ /port/ in the tree, and particularly bad when its a port that apache itself depends on, as you end up with a dependency loop. Dependency loops are (in Ghostbusters parlance) like crossing the streams. Anyone generating dependency loops deserves to be pelted with stay-puft marshmallow, at the very least. Instead, you want to use a WITH_FOO variable, or a WANT_FOO variable. These are intended as user servicable parts. For apache, that would be something like the following to make www/apache22 the default apache port: WITH_APACHE2= yes APACHE_PORT=www/apache22 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: portmaster question
On Mon, 8 Nov 2010 12:50:21 -0700 (MST) Warren Block wrote: > On Mon, 8 Nov 2010, RW wrote: > > > -aRr isn't implied by -a, the rR options are ignored in the former. > > > > I think it's fairly clear that recursing through installed > > packages with consistent dependecies isn't going to find a package > > that isn't in the set of all installed packages. > > That sentence makes me a little dizzy. I think you mean that since > -a is equivalent to listing all packages on the command line, -r or > -R are redundant. > > So portupgrade \* (i.e., -a) is a superset of > > portupgrade -r libexample > > because all the dependencies of libexample are included in the \* and > so portupgrade will see they need to be updated because a port they > depend on has been updated... Right? yes ___ 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: portmaster question
On Mon, 8 Nov 2010, RW wrote: -aRr isn't implied by -a, the rR options are ignored in the former. I think it's fairly clear that recursing through installed packages with consistent dependecies isn't going to find a package that isn't in the set of all installed packages. That sentence makes me a little dizzy. I think you mean that since -a is equivalent to listing all packages on the command line, -r or -R are redundant. So portupgrade \* (i.e., -a) is a superset of portupgrade -r libexample because all the dependencies of libexample are included in the \* and so portupgrade will see they need to be updated because a port they depend on has been updated... Right? ___ 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: portmaster question
On Mon, 8 Nov 2010 06:22:55 -0500
Jerry wrote:
> I don't see anything that specifically states the the "-R or -r"
> flags are in included with the "-a" flag; although I might be
> misinterpreting it. If it was implied i think it should have been
> better documented.
-aRr isn't implied by -a, the rR options are ignored in the former.
I think it's fairly clear that recursing through installed
packages with consistent dependecies isn't going to find a package
that isn't in the set of all installed packages. The remaining question
is whether -Ra also recurses though new dependencies, and that's covered
in the entry for -R.
It doesn't really matter though, since -aRr is only a waste of
keystrokes.
> Perhaps the only way to positively ascertain the correct answer would
> be to actually study the apps code,
opts.def_option("-a", "--all",
"Do with all the installed packages") {
|$all|
$recursive = false
$upward_recursive = false
}
...
opts.def_option("-r", "--recursive",
"Do with all those depending on the given packages"
<< NEXTLINE << "as well") {
$recursive = true unless $all
}
opts.def_option("-R", "--upward-recursive",
"Do with all those required by the given packages"
<< NEXTLINE << "as well / Fetch recursively if -F is specified") {
$upward_recursive = true unless $all
$fetch_recursive = true
}
...
if $fetch_recursive
cmdargs << 'checksum-recursive'
else
cmdargs << 'checksum'
end
___
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: portmaster question
On Sun, 7 Nov 2010 22:11:50 -0700 (MST) Warren Block articulated: > On Sun, 7 Nov 2010, Jerry wrote: > > > When using 'portupgrade', I commonly use the '-r' flag in > > conjunction with the previously discussed '-a' flag. While not as > > through as the "-u -p" flags with 'portmanger', it does accomplish > > its goal. > > Isn't portupgrade -a equivalent to -arR? I hope so, or I have a > correction to make... From the man: -a --allDo with all the installed packages. Equivalent to specify '*' as pkgname_glob. -r --recursive Act on all those packages depending on the given packages as well. -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) I don't see anything that specifically states the the "-R or -r" flags are in included with the "-a" flag; although I might be misinterpreting it. If it was implied i think it should have been better documented. Perhaps the only way to positively ascertain the correct answer would be to actually study the apps code, something I have neither the time nor inclination to do. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: portmaster question
On Sun, 7 Nov 2010 22:11:50 -0700 (MST) Warren Block wrote: > On Sun, 7 Nov 2010, Jerry wrote: > > > When using 'portupgrade', I commonly use the '-r' flag in > > conjunction with the previously discussed '-a' flag. While not as > > through as the "-u -p" flags with 'portmanger', it does accomplish > > its goal. > > Isn't portupgrade -a equivalent to -arR? I hope so, or I have a > correction to make... Yes, unless -F is used, in which case -R causes a checksum-recursive target to be used. ___ 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"
