Re: Advice sought on Portmaster -Faf and deleted ports
On Mon, Oct 14, 2013 at 9:48 PM, Scott Ballantyne wrote: > > Adam Vande More wrote: > > > > > It does seem like a bit > > > of over-kill to quit updating ALL ports because one is long > > > gone. Seems like it could do the others. > > > > > > > So it should continue on and potentially build 1000's of ports with > broken > > linking and dependencies? Portupgrade will do this if you tell it. Try > it > > out and see what fun you can create. > > > > Not a single program on my system depended on that program being > rebuilt. And what about libs it may have left behind and other ports picking up faulty info? Then you build unsupported and faultly packages and complain to the list when something doesn't work. Just follow /usr/ports/UPDATING as advised instead of your "shortcuts". > Portmaster should certainly refuse to rebuild anything that > did, of course. Exactly what it did. -- 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: Advice sought on Portmaster -Faf and deleted ports
On Mon 14 Oct 2013 Warren Block wrote: > On Mon, 14 Oct 2013, Scott Ballantyne wrote: > > > > > On Mon, 14 oct 2013, Warren Block wrote: > >> On Mon, 14 Oct 2013, Scott Ballantyne wrote: > >> > > > > Actually, the last time I updated my ports was when I installed 9.0, > > and I used the portmaster 'nuke all ports' method I was trying to > > day. Since then, several dozen ports of been 'deleted' or 'renamed', > > not just the linux_base-fc4. Seems in the case of ports which have > > been renamed or replaced, this could in fact be simply automated in > > most cases. > > I think it does handle renamed ports. Whether the ones it does not > handle are due to missing functionality or because they are difficult or > impossible to handle, don't know. Such was not my experience, Warren. And actually, a google search while I was trying to solve this turned up many reports of the same problem over the past years. ___ 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: Advice sought on Portmaster -Faf and deleted ports
Adam Vande More wrote: > > > It does seem like a bit > > of over-kill to quit updating ALL ports because one is long > > gone. Seems like it could do the others. > > > > So it should continue on and potentially build 1000's of ports with broken > linking and dependencies? Portupgrade will do this if you tell it. Try it > out and see what fun you can create. > Not a single program on my system depended on that program being rebuilt. Portmaster should certainly refuse to rebuild anything that did, of course. ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 Oct 2013, Scott Ballantyne wrote: On Mon, 14 oct 2013, Warren Block wrote: On Mon, 14 Oct 2013, Scott Ballantyne wrote: What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, "linux-base-fc4" has been deleted. terminating terminating terminating etc. That's correct. linux_base-fc4 is long gone (years), replaced by linux_base-f10. portmaster sees no way to upgrade that port, so evidently it quits. I understand why portmaster quits that port. It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. Some of them. It could not update any ports that depend on missing ports, which conflicts with the "-a" meaning "all". If you have ports that far out of date, the upgrade process is going to be long. Ports where the system does not know the replacement will have to be handled manually. Actually, the last time I updated my ports was when I installed 9.0, and I used the portmaster 'nuke all ports' method I was trying to day. Since then, several dozen ports of been 'deleted' or 'renamed', not just the linux_base-fc4. Seems in the case of ports which have been renamed or replaced, this could in fact be simply automated in most cases. I think it does handle renamed ports. Whether the ones it does not handle are due to missing functionality or because they are difficult or impossible to handle, don't know. ___ 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, Oct 14, 2013 at 6:35 PM, Scott Ballantyne wrote: > > > I understand why portmaster quits that port. Because it has no choice. > It does seem like a bit > of over-kill to quit updating ALL ports because one is long > gone. Seems like it could do the others. > So it should continue on and potentially build 1000's of ports with broken linking and dependencies? Portupgrade will do this if you tell it. Try it out and see what fun you can create. -- 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 oct 2013, Warren Block wrote: > On Mon, 14 Oct 2013, Scott Ballantyne wrote: > > >> > >> What errors, exactly? > > > > Well, for example: > > > > portmaster -Faf > > it starts to fetch a bunch of files > > it finds a port which has been deleted, such as > > linux-base-fc4 > > and it says, "linux-base-fc4" has been deleted. > > terminating > > terminating > > terminating > > etc. > > That's correct. linux_base-fc4 is long gone (years), replaced by > linux_base-f10. portmaster sees no way to upgrade that port, so > evidently it quits. I understand why portmaster quits that port. It does seem like a bit of over-kill to quit updating ALL ports because one is long gone. Seems like it could do the others. > If you have ports that far out of date, the upgrade process is going to > be long. Ports where the system does not know the replacement will have > to be handled manually. Actually, the last time I updated my ports was when I installed 9.0, and I used the portmaster 'nuke all ports' method I was trying to day. Since then, several dozen ports of been 'deleted' or 'renamed', not just the linux_base-fc4. Seems in the case of ports which have been renamed or replaced, this could in fact be simply automated in most cases. Best, 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: Advice sought on Portmaster -Faf and deleted ports
On Mon, 14 Oct 2013, Scott Ballantyne wrote: I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, "linux-base-fc4" has been deleted. terminating terminating terminating etc. That's correct. linux_base-fc4 is long gone (years), replaced by linux_base-f10. portmaster sees no way to upgrade that port, so evidently it quits. If you have ports that far out of date, the upgrade process is going to be long. Ports where the system does not know the replacement will have to be handled manually. So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? It should "just work". Have you converted to pkgng? I dream of the day that the ports system will "just work". I don't use binary packages, are you saying that pkgng will deal with this issue automatically? No, the concern was that you might have already converted to pkgng but still used the old package tools. ___ 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: Advice sought on Portmaster -Faf and deleted ports
> > > Hi, > > > > I'm following the recipe at the end of man portmaster for deleting and > > reinstalling all my ports, which I have done many times in the > > past. This time, I am getting errors on the portmaster -Faf step > > involving deleted ports, and I'm not sure how to deal with this > > easily. > > What errors, exactly? Well, for example: portmaster -Faf it starts to fetch a bunch of files it finds a port which has been deleted, such as linux-base-fc4 and it says, "linux-base-fc4" has been deleted. terminating terminating terminating etc. > > > So, I am seeking expert advice here. Is there a way to automate this > > and keep myself out of trouble, or do I need to do a 'port-by-port' > > upgrade of each port? > > It should "just work". Have you converted to pkgng? > I dream of the day that the ports system will "just work". I don't use binary packages, are you saying that pkgng will deal with this issue automatically? Thanks, 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: Advice sought on Portmaster -Faf and deleted ports
On Sun, 13 Oct 2013, Scott Ballantyne wrote: Hi, I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. What errors, exactly? So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? It should "just work". Have you converted to pkgng? ___ 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"
Advice sought on Portmaster -Faf and deleted ports
Hi, I'm following the recipe at the end of man portmaster for deleting and reinstalling all my ports, which I have done many times in the past. This time, I am getting errors on the portmaster -Faf step involving deleted ports, and I'm not sure how to deal with this easily. If the ports aren't in use, I have just deleted them, but for other things, such as libgsf-1.14.21_1, which is required by a dozen or more of my installed packages, it is not so easy. So, I am seeking expert advice here. Is there a way to automate this and keep myself out of trouble, or do I need to do a 'port-by-port' upgrade of each port? Thanks! 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: find ports that aren't required anymore
Cool, thanks Mark. Guess that's also a reason to learn new pkg tools. . On 2013-08-31, at 1:41 PM, Mark Felder wrote: > > > On Sat, Aug 31, 2013, at 14:19, Dale Scott wrote: >> I was using the postfix port, but decided to replace it with ssmtp to >> reduce >> ports in use and simplify system updating (deleting postfix with >> pkg_delete). Is it possible that deleting postfix will leave ports >> installed >> that aren't required anymore? Will pkg_delete also delete any >> dependencies >> no longer required? If I could have ports still installed that aren't >> required anymore? How can I find them now? Portmaster? > > If you're using the old pkg format you'll want to use something like > pkg_cutleaves which is in ports. > > If you're using the new pkg format you can simply run "pkg autoremove". > ___ > 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: find ports that aren't required anymore
On Sat, Aug 31, 2013, at 14:19, Dale Scott wrote: > I was using the postfix port, but decided to replace it with ssmtp to > reduce > ports in use and simplify system updating (deleting postfix with > pkg_delete). Is it possible that deleting postfix will leave ports > installed > that aren't required anymore? Will pkg_delete also delete any > dependencies > no longer required? If I could have ports still installed that aren't > required anymore? How can I find them now? Portmaster? > If you're using the old pkg format you'll want to use something like pkg_cutleaves which is in ports. If you're using the new pkg format you can simply run "pkg autoremove". ___ 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"
find ports that aren't required anymore
I was using the postfix port, but decided to replace it with ssmtp to reduce ports in use and simplify system updating (deleting postfix with pkg_delete). Is it possible that deleting postfix will leave ports installed that aren't required anymore? Will pkg_delete also delete any dependencies no longer required? If I could have ports still installed that aren't required anymore? How can I find them now? Portmaster? All the information I could find related to finding dependencies for a port, not for finding installed ports that don't have parent dependencies. Is it possible to invoke "pkg_info -R" on all ports and filter the output? TIA, Dale ___ 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: FreeBSD ports problem
On Thu, Aug 29, 2013 at 11:39 PM, Harpreet Singh Chawla < preet10101...@gmail.com> wrote: > yup...did it...and downloaded manually... > But its giving a checksum matching error. > > *Harpreet Singh Chawla* > > > On 29 August 2013 22:48, Amitabh Kant wrote: > >> >> On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla < >> preet10101...@gmail.com> wrote: >> >>> I have been trying to install virtualbox support for my FreeBSD 9.1. A >>> package named v4l_compat-1.0.20120501.tar.gz is causing problems in the >>> installation. The package was downloaded automatically and it exists in >>> /usr/ports/distfiles, yet it keeps giving an error stating that the file >>> doesn't exist. >>> >>> Please help. >>> *Harpreet Singh Chawla* >>> ___ >>> >> >> No idea about virtualbox port, but have you tried deleting the offending >> file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? >> >> Amitabh >> > > After deleting, you don't need to download it manually. The port should download it if needed. Try updating your ports tree to see if the problem has been rectified. Amitabh ___ 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: FreeBSD ports problem
On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla < preet10101...@gmail.com> wrote: > I have been trying to install virtualbox support for my FreeBSD 9.1. A > package named v4l_compat-1.0.20120501.tar.gz is causing problems in the > installation. The package was downloaded automatically and it exists in > /usr/ports/distfiles, yet it keeps giving an error stating that the file > doesn't exist. > > Please help. > *Harpreet Singh Chawla* > ___ > No idea about virtualbox port, but have you tried deleting the offending file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? Amitabh ___ 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 ports problem
I have been trying to install virtualbox support for my FreeBSD 9.1. A package named v4l_compat-1.0.20120501.tar.gz is causing problems in the installation. The package was downloaded automatically and it exists in /usr/ports/distfiles, yet it keeps giving an error stating that the file doesn't exist. Please help. *Harpreet Singh Chawla* ___ 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: CURDIR-relative paths in ports' Makefiles
On 27/08/2013 13:04, Koslov Sergey wrote:
> Hello
>
> I've noticed that many ports are using ${.CURDIR}/../../some/port
> construction in their Makefiles.
>
> But if you copy on of these ports elsewhere it won't work as expected
> because of the relative path.
> Shouldn't they use ${PORTSDIR}/some/port instead?
The use of relative paths is taken straight from The Porter's Handbook. eg.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-masterdir.html
So it's officially correct to do that.
While there is no direct proscription against saying
${PORTSDIR}/some/port in that circumstance that I can see in the
documentation, relative paths are generally only used in slave ports for
the ${MASTERDIR} setting or more generally for including other
Makefiles; whereas absolute paths are used for all sorts of FOO_DEPENDS
variables. A quick (and by no means definitive) grepping of the ports
tree I just did hasn't shown up any counter examples.
If you intend to copy a slave port to some other location in your
filesystem and have it refer to the original master port within the
default ports tree, then you're assumed to be capable of editing the
Makefile to resolve any such changes.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
CURDIR-relative paths in ports' Makefiles
Hello
I've noticed that many ports are using ${.CURDIR}/../../some/port
construction in their Makefiles.
But if you copy on of these ports elsewhere it won't work as expected
because of the relative path.
Shouldn't they use ${PORTSDIR}/some/port instead?
Thanks for the replies.
Kozlov Sergey
___
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: How to Fix Port Audit showing ports not installed on a system
On 08/06/2013 2:55 pm, Matthew Seaman wrote: On 06/08/2013 19:23, dweimer wrote: Of course I have WITH_PKGNG="YES" in the make.conf, and I believe that has been there ever since the server was built. Is my best option to get the correct list from pkg info use rm -r /var/db/pkg/* to clear everything out and then reinstall all of the ports? If you've had WITH_PKGNG="YES" ever since the server was built then you shouldn't have any of the old-style pkg_tools entries in /var/db/pkg. Unless, that is, you've been using pkg_add(1) directly. Don't do that. You just end up with a complete mess. Remember folks -- pkgng is like getting married. Once you go with pkgng, you're not meant to dally with other package tools, but to stay faithful to pkgng from henceforth. I hope you've got the old-style pkg_tools per-package subdirectories in /var/db/pkg because either (i) you used to use pkg_tools and you ran pkg2ng to convert or (ii) you've been using portmaster, in which case those sub-directories only /look/ like the result of what pkg_tools generates, but are really just a place for portmaster to stash a few things. If those sub-directories contain files called thing like +CONTENTS or +COMMENT or other names beginning with '+' then you do have a messed up mixture of old pkg_tools and pkgng. First: remove all the subdirectories but *not* local.sqlite or repo.sqlite -- those are rather important bits of pkgng. Then you can force a reinstall of all packages by pkg upgrade -f Obviusly, you'll need pkg(8) configured to use a repo with all the appropriate packages available. Cheers, Matthew Thanks for the info, I have never used pkg_add, everything has been installed via ports and portmaster, but it is possible that some ports were installed prior to having the with pkgng added in make.conf, and that something happened in the pk2ng conversion. I thought I had built this machine after I had been running with pkgng, but perhaps this one was built right as I was switching over to it. I had originally built this machine with Xorg and KDE to use virtual box GUI, and once I became comfortable with the commands, switched to vboxheadless and removed all the GUI components. Which is where all the extra ports that were removed came from. I have removed the sub directories, now portaudit doesn't show any vulnerabilities in non existent ports, pkg info displays the correct installed packages, and portmaster -l matches the installed ports that pkg info displays. -- 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: How to Fix Port Audit showing ports not installed on a system
On 06/08/2013 19:23, dweimer wrote: > Of course I have WITH_PKGNG="YES" in the make.conf, and I believe that > has been there ever since the server was built. Is my best option to > get the correct list from pkg info use rm -r /var/db/pkg/* to clear > everything out and then reinstall all of the ports? If you've had WITH_PKGNG="YES" ever since the server was built then you shouldn't have any of the old-style pkg_tools entries in /var/db/pkg. Unless, that is, you've been using pkg_add(1) directly. Don't do that. You just end up with a complete mess. Remember folks -- pkgng is like getting married. Once you go with pkgng, you're not meant to dally with other package tools, but to stay faithful to pkgng from henceforth. I hope you've got the old-style pkg_tools per-package subdirectories in /var/db/pkg because either (i) you used to use pkg_tools and you ran pkg2ng to convert or (ii) you've been using portmaster, in which case those sub-directories only /look/ like the result of what pkg_tools generates, but are really just a place for portmaster to stash a few things. If those sub-directories contain files called thing like +CONTENTS or +COMMENT or other names beginning with '+' then you do have a messed up mixture of old pkg_tools and pkgng. First: remove all the subdirectories but *not* local.sqlite or repo.sqlite -- those are rather important bits of pkgng. Then you can force a reinstall of all packages by pkg upgrade -f Obviusly, you'll need pkg(8) configured to use a repo with all the appropriate packages available. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: How to Fix Port Audit showing ports not installed on a system
On 08/06/2013 11:58 am, Paul Macdonald wrote: On 06/08/2013 17:25, dweimer wrote: I have a system that I just recently setup port audit, after realizing I forgot to install it on the machine. The problem is that it is finding vulnerabilities in several ports that are not installed on the system. These may have been installed at one point and removed. Firefox is one of the ones listed, I know that it was on the system previously, but was removed a few months back. portmaster -l and pkg info don't list it as installed, but port audit shows: firefox-20.0,1. Where would portaudit be picking up these ports from? Is there anyway to reset its database? rm -R /var/db/portaudit/ then run portaudit -Fda -- Already tried that, but that data only contains the list of known vulnerabilities, not the installed ports/packages. Perhaps, its not using pkgng I discovered if I do a pkg info command I get the correct list of installed ports and packages. If I do a pkg_info I get a much larger list showing everything as corrupted. ... pkg_info: the package info for package 'fftw3-3.3.3_1' is corrupt pkg_info: the package info for package 'filelight-4.10.1' is corrupt pkg_info: the package info for package 'firefox-20.0,1' is corrupt pkg_info: the package info for package 'fixesproto-5.0' is corrupt pkg_info: the package info for package 'flac-1.2.1_3' is corrupt pkg_info: the package info for package 'flex-2.5.37_1' is corrupt ... Of course I have WITH_PKGNG="YES" in the make.conf, and I believe that has been there ever since the server was built. Is my best option to get the correct list from pkg info use rm -r /var/db/pkg/* to clear everything out and then reinstall all of the ports? -- 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: How to Fix Port Audit showing ports not installed on a system
On 06/08/2013 17:25, dweimer wrote: I have a system that I just recently setup port audit, after realizing I forgot to install it on the machine. The problem is that it is finding vulnerabilities in several ports that are not installed on the system. These may have been installed at one point and removed. Firefox is one of the ones listed, I know that it was on the system previously, but was removed a few months back. portmaster -l and pkg info don't list it as installed, but port audit shows: firefox-20.0,1. Where would portaudit be picking up these ports from? Is there anyway to reset its database? rm -R /var/db/portaudit/ then run portaudit -Fda -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA High Specification Dedicated Servers from £100.00pm ___ 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"
How to Fix Port Audit showing ports not installed on a system
I have a system that I just recently setup port audit, after realizing I forgot to install it on the machine. The problem is that it is finding vulnerabilities in several ports that are not installed on the system. These may have been installed at one point and removed. Firefox is one of the ones listed, I know that it was on the system previously, but was removed a few months back. portmaster -l and pkg info don't list it as installed, but port audit shows: firefox-20.0,1. Where would portaudit be picking up these ports from? Is there anyway to reset its database? -- 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: Unable to build "DOC" ports
On Mon, Jul 22, 2013 at 08:47:47AM -0400, Carmel wrote: > I am having a problem updating some ports since installing the > "print/texlive-full" port a few days ago. I have: "TEX_DEFAULT=texlive" > sans quotes at the top of my "/etc/make.conf" file. > [...] I think you have the reason just above. For the moment the docproj port relies on print/teTeX-base and not print/texlive-full. -- Marc ___ 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"
Unable to build "DOC" ports
I am having a problem updating some ports since installing the "print/texlive-full" port a few days ago. I have: "TEX_DEFAULT=texlive" sans quotes at the top of my "/etc/make.conf" file. For instance, the "en-freebsd-doc-42326,1", and in fact all of the *-freebsd-doc" ports are refusing to build. This is from the build log: env UPGRADE_TOOL=portupgrade UPGRADE_PORT=en-freebsd-doc-42095,1 UPGRADE_PORT_VER=42095,1 make clean ===> Cleaning for docproj-1.17_13 ===> Cleaning for zh-docproj-0.1.20060303_6 ===> Cleaning for latex-cjk-4.8.2_6 ===> Cleaning for freetype-tools-1.3.1_9 ===> Cleaning for en-freebsd-doc-42326,1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=en-freebsd-doc-42095,1 UPGRADE_PORT_VER=42095,1 make ===> Found saved configuration for en-freebsd-doc-40771_1,1 ===> Fetching all distfiles required by en-freebsd-doc-42326,1 for building ===> Extracting for en-freebsd-doc-42326,1 => SHA256 Checksum OK for freebsd-doc-42326.tar.gz. ===> Patching for en-freebsd-doc-42326,1 ===> en-freebsd-doc-42326,1 depends on package: docproj>=1.17 - not found ===>Verifying install for docproj>=1.17 in /usr/ports/textproc/docproj ===> Found saved configuration for docproj-1.17_12 ===> Fetching all distfiles required by docproj-1.17_13 for building ===> Extracting for docproj-1.17_13 ===> Patching for docproj-1.17_13 ===> docproj-1.17_13 depends on executable: dvips - found ===> docproj-1.17_13 depends on executable: jadetex - found ===> Configuring for docproj-1.17_13 ===> Installing for docproj-1.17_13 ===> docproj-1.17_13 depends on executable: fixrtf - found ===> docproj-1.17_13 depends on executable: links - found ===> docproj-1.17_13 depends on executable: pngtopnm - found ===> docproj-1.17_13 depends on executable: scr2png - found ===> docproj-1.17_13 depends on executable: scr2txt - found ===> docproj-1.17_13 depends on executable: xsltproc - found ===> docproj-1.17_13 depends on executable: peps - found ===> docproj-1.17_13 depends on file: /usr/local/share/sgml/docbook/dsssl/modular - found ===> docproj-1.17_13 depends on file: /usr/local/share/sgml/iso8879 - found ===> docproj-1.17_13 depends on file: /usr/local/share/xml/dtd/xhtml/xhtml.soc - found ===> docproj-1.17_13 depends on file: /usr/local/share/xsl/docbook/html/docbook.xsl - found ===> docproj-1.17_13 depends on file: /usr/local/share/xsl/iso-schematron/xslt1/iso_schematron_skeleton_for_xslt1.xsl - found ===> docproj-1.17_13 depends on file: /usr/local/share/xml/docbook/4.5/docbookx.dtd - found ===> docproj-1.17_13 depends on file: /usr/local/share/xsl/docbook/html/docbook.xsl - found ===> docproj-1.17_13 depends on file: /usr/local/share/xsl/iso-schematron/xslt1/iso_schematron_skeleton_for_xslt1.xsl - found ===> docproj-1.17_13 depends on file: /usr/local/share/xml/docbook/4.5/docbookx.dtd - found ===> docproj-1.17_13 depends on file: /usr/local/share/xml/xmlcharent/catalog - found ===> docproj-1.17_13 depends on package: p5-XML-Parser>=2.41 - found ===> docproj-1.17_13 depends on executable: zip - found ===> docproj-1.17_13 depends on executable: svn - found ===> docproj-1.17_13 depends on executable: igor - found ===> docproj-1.17_13 depends on executable: cjktexsty - not found ===>Verifying install for cjktexsty in /usr/ports/chinese/docproj ===> Fetching all distfiles required by zh-docproj-0.1.20060303_6 for building ===> Extracting for zh-docproj-0.1.20060303_6 ===> Fetching all distfiles required by zh-docproj-0.1.20060303_6 for building ===> Patching for zh-docproj-0.1.20060303_6 ===> zh-docproj-0.1.20060303_6 depends on shared library: iconv.3 - found ===> Configuring for zh-docproj-0.1.20060303_6 ===> Building for zh-docproj-0.1.20060303_6 ===> cjktexsty (all) Warning: Object directory not changed from original /usr/ports/chinese/docproj/work/src/cjktexsty lex -t cjktexsty.l > cjktexsty.c cc -O2 -pipe -march=athlon64 -fno-strict-aliasing -march=athlon64 -I/usr/local/include -std=gnu99 -fstack-protector -c cjktexsty.c cc -O2 -pipe -march=athlon64 -fno-strict-aliasing -march=athlon64 -I/usr/local/include -std=gnu99 -fstack-protector -o cjktexsty cjktexsty.o -L/usr/local/lib -liconv ===> Installing for zh-docproj-0.1.20060303_6 ===> zh-docproj-0.1.20060303_6 depends on executable: gbklatex - not found ===>Verifying install for gbklatex in /usr/ports/print/latex-cjk ===> latex-cjk-4.8.2_6 conflicts with installed package(s): tex-kpathsea-6.1.0_2 tex-web2c-20120701_2 They install files into the same place. You may want to stop build with Ctrl + C. At that point the build continues until the following: gcc -c -g -O2 -Wall -pedantic -I./../../lib -I/usr/local/include -I. -DHAVE_LIBKPATHSE
Re: pkg: Unable to open ports directory /usr/ports: No such file or directory
On 13/07/2013 11:17, Leslie Jensen wrote: > 2013-07-12 13:25, Leslie Jensen skrev: >> >> When I run >> >> portsnap fetch update >> >> pkg version -vIL= >> >> >> It returns >> >> pkg: Unable to open ports directory /usr/ports: No such file or directory >> >> >> The directory is there and I can list the contents. >> >> What's going on? > > I get this as well > > gunzip: can't stat: > files/30173a70f7852dc247fda74d2d4babaae21067417fc17e67dc388c9ec85a8e8a.gz: > No such file or directory > gunzip: can't stat: > /var/db/portsnap/files/845df3602aa1742b771872ffbe945ee60e0c834ae1540ba0dab02f224cce56f5.gz: > No such file or directory > pkg: Unable to open ports directory /usr/ports: No such file or directory > > I'm a bit lost. Do I have to remove something for this command to succeed? Let's look at the command line you're using: pkg version -vIL= That -I means it's going to try and read the ports INDEX specifically -- ie. /usr/ports/INDEX Does that file exist? Does it have sensible contents? Now, given your further comments, it seems something relatively significant is wrong. There's on obvious (but fairly easy to fix) thing it might be. Have you run out of space on any of your partitions? What goes 'df -h' report? Any real partition reporting 100% full is a problem. (Don't worry about synthetic filesystems like devfs reporting 100% usage: that's normal.) If some filesystem is full, then you need to either delete stuff, or move it onto a filesystem with more space. You also seem to be having problems with portsnap(8) -- be aware there was a problem reported recently. See the thread on freebsd-ports@... subject 'Latest snapshot' starting with this message: http://lists.freebsd.org/pipermail/freebsd-ports/2013-July/084833.html but to summarize several people saw the problem, and the cure was to delete the files portsnap was using by 'rm -Rf /var/db/portsnap/files' and then re-run 'portsnap fetch' and 'portsnap extract' -- warning: this will wipe out everything you have in /usr/ports and download a complete set of replacements. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: pkg: Unable to open ports directory /usr/ports: No such file or directory
2013-07-12 13:25, Leslie Jensen skrev: When I run portsnap fetch update pkg version -vIL= It returns pkg: Unable to open ports directory /usr/ports: No such file or directory The directory is there and I can list the contents. What's going on? 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" I get this as well gunzip: can't stat: files/30173a70f7852dc247fda74d2d4babaae21067417fc17e67dc388c9ec85a8e8a.gz: No such file or directory gunzip: can't stat: /var/db/portsnap/files/845df3602aa1742b771872ffbe945ee60e0c834ae1540ba0dab02f224cce56f5.gz: No such file or directory pkg: Unable to open ports directory /usr/ports: No such file or directory I'm a bit lost. Do I have to remove something for this command to succeed? 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"
pkg: Unable to open ports directory /usr/ports: No such file or directory
When I run portsnap fetch update pkg version -vIL= It returns pkg: Unable to open ports directory /usr/ports: No such file or directory The directory is there and I can list the contents. What's going on? 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"
Problems Installing /usr/ports/devel/pear
Is anyone else having problems installing pear with PHP 5.5? Or do I
just have a misconfiguration on my system that is causing the install
process to look at my /tmp directory. My ports tree is updated to svn
revision 322502, and the system is running FreeBSD 9.1p4, so everything
is up to date prior to this install.
root@webmail:/usr/ports/devel/pear # make
===> pear-1.9.4_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by pear-1.9.4_1 for building
===> Extracting for pear-1.9.4_1
=> SHA256 Checksum OK for pear-1.9.4.tar.bz2.
===> Patching for pear-1.9.4_1
===> Applying FreeBSD patches for pear-1.9.4_1
===> pear-1.9.4_1 depends on file: /usr/local/include/php/main/php.h -
found
===> pear-1.9.4_1 depends on file: /usr/local/lib/php/20121212/xml.so
- found
===> Configuring for pear-1.9.4_1
root@webmail:/usr/ports/devel/pear # make install
===> Installing for pear-1.9.4_1
===> pear-1.9.4_1 depends on file: /usr/local/include/php/main/php.h -
found
===> pear-1.9.4_1 depends on file: /usr/local/lib/php/20121212/xml.so
- found
===> Generating temporary packing list
===> Checking if devel/pear already installed
Bootstrapping Installer...
Bootstrapping PEAR.php(local) ok
Bootstrapping Archive/Tar.php(local) ok
Bootstrapping Console/Getopt.php(local) ok
Strict Standards: Non-static method PEAR::setErrorHandling() should not
be called statically in
/var/ports/usr/ports/devel/pear/work/pear-1.9.4/go-pear on line 689
Extracting installer..
Using local package: PEAR.
Warning: file_exists() expects parameter 1 to be a valid path, string
given in /tmp/pear/Archive/Tar.php on line 1582
Error while opening {/tmp/pear/package2.xml} in write binary mode
sed: /usr/local/share/pear/peclcmd.php: No such file or directory
*** [do-install] Error code 1
Stop in /usr/ports/devel/pear
--
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: why is ports web page so far out of date
On Wed, Jun 5, 2013 at 11:29 PM, Waitman Gobble wrote: > On Wed, Jun 5, 2013 at 9:45 PM, Shane Ambler wrote: >> On 05/06/2013 17:00, Waitman Gobble wrote: >> >>> If you must have a web based version, another option is DIY roll your >>> own ports index based on your own local ports tree. At least you can >>> set it up how you want. >>> >>> a simple quick-together script running on my computer: >>> https://dx.burplex.com/FreeBSD-ports/index.php >>> >>> there's a github link at the bottom of the page you can hack on if you >>> wanna. >>> >>> cool thing is you can easily cross-reference all the corresponding >>> gnats PR files in your mailbox to the generated port page, i'll add >>> that bit tomorrow. >> >> >> That looks useful. One thing I would think of adding is a search box. >> >> I would have thought of breaking the lists into pages but am surprised at >> how fast the longer pages are generated. >> >> One port that it has an issue with is devel/pear-HTML_Select_Common the >> in the pkg-desc consumes all the following ports info. So you >> probably want to escape or translate "<" ">" into < > >> >> > > hi, > > search box would probably be cool! :) I'll get on it. > > and yes, it /totally/ needed to broken up into pages. I think that's > working now. > > Ok, I agree with you on the HTML entities, it's a done deal.. There > are some updates to post. I have GNATS linked up. I thought I might > have to cache a bunch of stuff considering >> du -h ports > 1.5G ports > just the ports-related GNATS stuff is 1.5G. and growing every day. but > it's live code, seems perky enough. It might be good to add in the > mailing list stuff too. maybe 10x that 1.5G though, guessing.? > > I'm thinking about trying to somehow cross-reference the Makefiles to > the Porter's Handbook and maybe the .mk files. And maybe the other way > around too. It's like a bag of examples. > > -- basic search box now working, posted on git. https://dx.burplex.com/FreeBSD-ports/index.php I think maybe need list of ports modified selectable 1day-30days out. But I think the http://www.freshports.org/ site already does this, and it's better anyhow. -- Waitman Gobble San Jose California USA 510-830-7975 ___ 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: why is ports web page so far out of date
On Wed, Jun 5, 2013 at 9:45 PM, Shane Ambler wrote: > On 05/06/2013 17:00, Waitman Gobble wrote: > >> If you must have a web based version, another option is DIY roll your >> own ports index based on your own local ports tree. At least you can >> set it up how you want. >> >> a simple quick-together script running on my computer: >> https://dx.burplex.com/FreeBSD-ports/index.php >> >> there's a github link at the bottom of the page you can hack on if you >> wanna. >> >> cool thing is you can easily cross-reference all the corresponding >> gnats PR files in your mailbox to the generated port page, i'll add >> that bit tomorrow. > > > That looks useful. One thing I would think of adding is a search box. > > I would have thought of breaking the lists into pages but am surprised at > how fast the longer pages are generated. > > One port that it has an issue with is devel/pear-HTML_Select_Common the > in the pkg-desc consumes all the following ports info. So you > probably want to escape or translate "<" ">" into < > > > hi, search box would probably be cool! :) I'll get on it. and yes, it /totally/ needed to broken up into pages. I think that's working now. Ok, I agree with you on the HTML entities, it's a done deal.. There are some updates to post. I have GNATS linked up. I thought I might have to cache a bunch of stuff considering > du -h ports 1.5G ports just the ports-related GNATS stuff is 1.5G. and growing every day. but it's live code, seems perky enough. It might be good to add in the mailing list stuff too. maybe 10x that 1.5G though, guessing.? I'm thinking about trying to somehow cross-reference the Makefiles to the Porter's Handbook and maybe the .mk files. And maybe the other way around too. It's like a bag of examples. -- Waitman Gobble San Jose California USA 510-830-7975 ___ 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: why is ports web page so far out of date
On 05/06/2013 17:00, Waitman Gobble wrote: If you must have a web based version, another option is DIY roll your own ports index based on your own local ports tree. At least you can set it up how you want. a simple quick-together script running on my computer: https://dx.burplex.com/FreeBSD-ports/index.php there's a github link at the bottom of the page you can hack on if you wanna. cool thing is you can easily cross-reference all the corresponding gnats PR files in your mailbox to the generated port page, i'll add that bit tomorrow. That looks useful. One thing I would think of adding is a search box. I would have thought of breaking the lists into pages but am surprised at how fast the longer pages are generated. One port that it has an issue with is devel/pear-HTML_Select_Common the in the pkg-desc consumes all the following ports info. So you probably want to escape or translate "<" ">" into < > ___ 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: why is ports web page so far out of date
On Tue, Jun 4, 2013 at 7:19 AM, Mark Felder wrote: > On Tue, 04 Jun 2013 07:08:15 -0500, Fbsd8 wrote: > >> I can not get current version of the ports system. >> The ports web page http://www.freebsd.org/ports/ >> is almost 2 years out of date. Says the port I am interested in is at 1.7 >> version when just 2 weeks ago it was at 2.2. Portsnap is also messed up >> showing the 1.7 version. >> >> > > I'm not sure what the status of this system is, but I'd recommend you use > the official unofficial Freshports.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" If you must have a web based version, another option is DIY roll your own ports index based on your own local ports tree. At least you can set it up how you want. a simple quick-together script running on my computer: https://dx.burplex.com/FreeBSD-ports/index.php there's a github link at the bottom of the page you can hack on if you wanna. cool thing is you can easily cross-reference all the corresponding gnats PR files in your mailbox to the generated port page, i'll add that bit tomorrow. -- Waitman Gobble San Jose California USA 510-830-7975 ___ 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: why is ports web page so far out of date
On Tue, 04 Jun 2013 07:08:15 -0500, Fbsd8 wrote: I can not get current version of the ports system. The ports web page http://www.freebsd.org/ports/ is almost 2 years out of date. Says the port I am interested in is at 1.7 version when just 2 weeks ago it was at 2.2. Portsnap is also messed up showing the 1.7 version. I'm not sure what the status of this system is, but I'd recommend you use the official unofficial Freshports.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"
why is ports web page so far out of date
I can not get current version of the ports system. The ports web page http://www.freebsd.org/ports/ is almost 2 years out of date. Says the port I am interested in is at 1.7 version when just 2 weeks ago it was at 2.2. Portsnap is also messed up showing the 1.7 version. ___ 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: using ports or gems (easy_install)
On Tue, 28 May 2013 15:06:15 +0200 Albert Shih wrote: > Le 28/05/2013 ? 14:50:25+0700, Olivier Nicole a écrit > > Hi, > > > > > I would like to known how you manage your gem (ruby) or > > > easyinstall (python). Do you use ports ? or directly gems or > > > easyinstall ? or both ? > > > > As far as I can, I use ports, for consistency. > > Me too. But what you do when you cannot ? (Like the ports don't > exist) ? > > I see three possibility : > > 1/ write the ports (unfortunately not for me) > > 2/ wait until someone does (many time it's impossible) > > 3/ use easy_install or gem It is easy to learn. I would strongly suggest learning it, even if you just maintain the ports yourself and don't contribute them to the ports tree. Doing so will drastically improve the manageability of your system. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ ___ 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: using ports or gems (easy_install)
Albert, > > > I would like to known how you manage your gem (ruby) or easyinstall > > > (python). Do you use ports ? or directly gems or easyinstall ? or both ? > > As far as I can, I use ports, for consistency. > Me too. But what you do when you cannot ? (Like the ports don't exist) ? > I see three possibility : > 1/ write the ports (unfortunately not for me) > 2/ wait until someone does (many time it's impossible) > 3/ use easy_install or gem I use the solution 3 (cpan in the case of Perl). Best regards, olivier > > > > > > But I am using mostly Perl and CPAN is very well integrated in FreeBSD > > ports. > > Yes much better than ruby or python. > > Regards. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Create bond on Infiniband ports
On Tue, May 28, 2013 at 4:35 AM, Alex Liptsin wrote:
> Hi.
>
> I use FreeBSD 9.1 with OFED compiled on it.
>
> There is a Mellanox adapter:
>
> [root@qa-h-vrt-030-006 ~]# pciconf -lv |grep mlx4 -A 3
> mlx4_core0@pci0:0:5:0: class=0x028000 card=0x005015b3 chip=0x100315b3
> rev=0x00 hdr=0x00
> vendor = 'Mellanox Technologies'
> device = 'MT27500 Family [ConnectX-3]'
> class = network
>
> I want to create Bond on the two ports (ib0 and ib1) of this device:
>
> [root@qa-h-vrt-030-006 ~]# ifconfig
> em0: flags=8843 metric 0 mtu 1500
>
> options=209b
> ether 00:50:56:23:1e:06
> inet6 fe80::250:56ff:fe23:1e06%em0 prefixlen 64 scopeid 0x2
> inet 10.195.30.6 netmask 0x broadcast 10.195.255.255
> nd6 options=23
> media: Ethernet autoselect (1000baseT )
> status: active
> lo0: flags=8049 metric 0 mtu 16384
> options=63
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
> inet 127.0.0.1 netmask 0xff00
> nd6 options=23
> ib0: flags=8043 metric 0 mtu 65520
> options=80018
> lladdr 80.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.51
> inet 11.195.30.1 netmask 0x broadcast 11.195.255.255
> inet6 fe80::250:56ff:fe23:1e06%ib0 prefixlen 64 scopeid 0x4
> nd6 options=23
> ib1: flags=8043 metric 0 mtu 65520
> options=80018
> lladdr 80.0.0.49.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.52
> inet 12.195.30.1 netmask 0x broadcast 12.195.255.255
> inet6 fe80::250:56ff:fe23:1e06%ib1 prefixlen 64 scopeid 0x5
> nd6 options=23
>
>
> 1. Is there "bond" in FreeBSD or its "Lagg"?
>
It's lagg. Setting up bonded interfaces is different (Anthony C. or someone
else can provide more details about this). failover mode via lagg is
completely different from failover mode with IB IIRC.
> 2. I tried to create this way, but failed:
>
> [root@qa-h-vrt-030-006 ~]# ifconfig lagg0 create
>
> root@qa-h-vrt-031-005 conf]# ifconfig lagg0 laggproto failover laggport
> ib0 laggport ib1
>
> ifconfig: SIOCSLAGGPORT: Protocol not supported
>
> Any ideas?
> Is it supported on Infiniband ports?
>
The media setting pieces are look to only be supported with mlx4 in en mode:
1076 static int mlx4_en_ioctl(struct ifnet *dev, u_long command, caddr_t
data)
1077 {
...
1115 case SIOCGIFMEDIA:
1116 error = ifmedia_ioctl(dev, ifr, &priv->media, command);
1117 break;
If I remember correctly, IB ports with mlx4 default to ib mode, not en mode
(it also helps to have the right drivers loaded for this).
Cheers,
-Garrett
___
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: using ports or gems (easy_install)
Le 28/05/2013 ? 14:50:25+0700, Olivier Nicole a écrit > Hi, > > > I would like to known how you manage your gem (ruby) or easyinstall > > (python). Do you use ports ? or directly gems or easyinstall ? or both ? > > As far as I can, I use ports, for consistency. Me too. But what you do when you cannot ? (Like the ports don't exist) ? I see three possibility : 1/ write the ports (unfortunately not for me) 2/ wait until someone does (many time it's impossible) 3/ use easy_install or gem > > But I am using mostly Perl and CPAN is very well integrated in FreeBSD > ports. Yes much better than ruby or python. Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: mar 28 mai 2013 15:03:58 CEST ___ 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"
Create bond on Infiniband ports
Hi. I use FreeBSD 9.1 with OFED compiled on it. There is a Mellanox adapter: [root@qa-h-vrt-030-006 ~]# pciconf -lv |grep mlx4 -A 3 mlx4_core0@pci0:0:5:0: class=0x028000 card=0x005015b3 chip=0x100315b3 rev=0x00 hdr=0x00 vendor = 'Mellanox Technologies' device = 'MT27500 Family [ConnectX-3]' class = network I want to create Bond on the two ports (ib0 and ib1) of this device: [root@qa-h-vrt-030-006 ~]# ifconfig em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:50:56:23:1e:06 inet6 fe80::250:56ff:fe23:1e06%em0 prefixlen 64 scopeid 0x2 inet 10.195.30.6 netmask 0x broadcast 10.195.255.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 nd6 options=23 ib0: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.51 inet 11.195.30.1 netmask 0x broadcast 11.195.255.255 inet6 fe80::250:56ff:fe23:1e06%ib0 prefixlen 64 scopeid 0x4 nd6 options=23 ib1: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.49.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.52 inet 12.195.30.1 netmask 0x broadcast 12.195.255.255 inet6 fe80::250:56ff:fe23:1e06%ib1 prefixlen 64 scopeid 0x5 nd6 options=23 1. Is there "bond" in FreeBSD or its "Lagg"? 2. I tried to create this way, but failed: [root@qa-h-vrt-030-006 ~]# ifconfig lagg0 create root@qa-h-vrt-031-005 conf]# ifconfig lagg0 laggproto failover laggport ib0 laggport ib1 ifconfig: SIOCSLAGGPORT: Protocol not supported Any ideas? Is it supported on Infiniband ports? Regards, Alex Liptsin ___ 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: using ports or gems (easy_install)
Hi, > I would like to known how you manage your gem (ruby) or easyinstall > (python). Do you use ports ? or directly gems or easyinstall ? or both ? As far as I can, I use ports, for consistency. But I am using mostly Perl and CPAN is very well integrated in FreeBSD ports. Voila. Olivier ___ 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"
using ports or gems (easy_install)
Hi everybody, I would like to known how you manage your gem (ruby) or easyinstall (python). Do you use ports ? or directly gems or easyinstall ? or both ? For exemple when you want install some software with lots of dependances you can use (if the software use easy_install) just one easy_install and everything is installed, you can use ports for some packages but sometime not every packages are in the ports so you should need to installed it through easy_install. After that same question about updating So what you do ? And why ? Regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: mar 28 mai 2013 09:36:34 CEST ___ 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: pkg_version says my ports need to be updated?
On Mon, 27 May 2013, Ed Flecko wrote: Since I want to know the "correct" way (or one of I'm sure many correct ways) of initially installing the OS and then getting it up to date (and staying up to date), can you tell me what I did wrong and/or what I might want to do differently? A short overview: http://www.wonkity.com/~wblock/docs/html/portupgrade.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkg_version says my ports need to be updated?
Read the relevant portions of the handbook Chapter 5: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Chapter 25: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html Then also: man portmaster man freebsd-update On Mon, May 27, 2013 at 11:49 AM, Ed Flecko wrote: > Thank you both! > > Since I want to know the "correct" way (or one of I'm sure many correct > ways) of initially installing the OS and then getting it up to date (and > staying up to date), can you tell me what I did wrong and/or what I might > want to do differently? > > Ed > > > On Mon, May 27, 2013 at 11:16 AM, Matthew Seaman wrote: > >> On 27/05/2013 19:00, Ed Flecko wrote: >> > Clearly, I'm doing something wrong. >> > >> > :-) >> > >> > I thought I was using svn to keep my ports, src and docs up to date, but >> > pkg_version seems to disagree. >> > >> > I'm running 9.1 and I've installed ports, src, and docs as part of my >> > install. After that, I use subversion to (I thought) make sure everything >> > was up to date. >> > >> > I ran these commands: >> > >> > /usr/local/bin/svn up /usr/src >> > >> > /usr/local/bin/svn up /usr/ports >> > >> > /usr/local/bin/svn up /usr/doc >> > >> > and then I ran: >> > >> > >> > pkg_version -vIL = >> > >> > >> > >> > and it says "< needs updating (index has ...) on about 1 dozen items. So >> my >> > "index" is out of sync with my ports??? >> > >> > What did I screw up and how do I correct it? >> >> You seem to have updated the ports tree, which is a collection of >> recipes for how to build ported software, but not actually updated by >> rebuilding any of the ported software that has become out of date. >> >> Try installing ports-mgmt/portmaster and then running >> >> portmaster -a >> >> Cheers, >> >> Matthew >> -- >> Dr Matthew J Seaman MA, D.Phil. >> PGP: http://www.infracaninophile.co.uk/pgpkey >> >> >> > ___ > 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: pkg_version says my ports need to be updated?
Thank you both! Since I want to know the "correct" way (or one of I'm sure many correct ways) of initially installing the OS and then getting it up to date (and staying up to date), can you tell me what I did wrong and/or what I might want to do differently? Ed On Mon, May 27, 2013 at 11:16 AM, Matthew Seaman wrote: > On 27/05/2013 19:00, Ed Flecko wrote: > > Clearly, I'm doing something wrong. > > > > :-) > > > > I thought I was using svn to keep my ports, src and docs up to date, but > > pkg_version seems to disagree. > > > > I'm running 9.1 and I've installed ports, src, and docs as part of my > > install. After that, I use subversion to (I thought) make sure everything > > was up to date. > > > > I ran these commands: > > > > /usr/local/bin/svn up /usr/src > > > > /usr/local/bin/svn up /usr/ports > > > > /usr/local/bin/svn up /usr/doc > > > > and then I ran: > > > > > > pkg_version -vIL = > > > > > > > > and it says "< needs updating (index has ...) on about 1 dozen items. So > my > > "index" is out of sync with my ports??? > > > > What did I screw up and how do I correct it? > > You seem to have updated the ports tree, which is a collection of > recipes for how to build ported software, but not actually updated by > rebuilding any of the ported software that has become out of date. > > Try installing ports-mgmt/portmaster and then running > > portmaster -a > > Cheers, > > Matthew > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > > ___ 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: pkg_version says my ports need to be updated?
On 27/05/2013 19:00, Ed Flecko wrote: > Clearly, I'm doing something wrong. > > :-) > > I thought I was using svn to keep my ports, src and docs up to date, but > pkg_version seems to disagree. > > I'm running 9.1 and I've installed ports, src, and docs as part of my > install. After that, I use subversion to (I thought) make sure everything > was up to date. > > I ran these commands: > > /usr/local/bin/svn up /usr/src > > /usr/local/bin/svn up /usr/ports > > /usr/local/bin/svn up /usr/doc > > and then I ran: > > > pkg_version -vIL = > > > > and it says "< needs updating (index has ...) on about 1 dozen items. So my > "index" is out of sync with my ports??? > > What did I screw up and how do I correct it? You seem to have updated the ports tree, which is a collection of recipes for how to build ported software, but not actually updated by rebuilding any of the ported software that has become out of date. Try installing ports-mgmt/portmaster and then running portmaster -a Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: pkg_version says my ports need to be updated?
On Mon, 27 May 2013 11:00:52 -0700 Ed Flecko wrote: > Clearly, I'm doing something wrong. > > :-) > > I thought I was using svn to keep my ports, src and docs up to date, > but pkg_version seems to disagree. > > I'm running 9.1 and I've installed ports, src, and docs as part of my > install. After that, I use subversion to (I thought) make sure > everything was up to date. > > I ran these commands: > > /usr/local/bin/svn up /usr/src > > /usr/local/bin/svn up /usr/ports > > /usr/local/bin/svn up /usr/doc > > and it says "< needs updating (index has ...) on about 1 dozen items. > So my "index" is out of sync with my ports??? You updated the source code for the base system, and the ports tree (instructions for building and installing packages from source). You updated neither the base system nor the installed packages. Take another look at the handbook. ___ 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"
pkg_version says my ports need to be updated?
Clearly, I'm doing something wrong. :-) I thought I was using svn to keep my ports, src and docs up to date, but pkg_version seems to disagree. I'm running 9.1 and I've installed ports, src, and docs as part of my install. After that, I use subversion to (I thought) make sure everything was up to date. I ran these commands: /usr/local/bin/svn up /usr/src /usr/local/bin/svn up /usr/ports /usr/local/bin/svn up /usr/doc and then I ran: pkg_version -vIL = and it says "< needs updating (index has ...) on about 1 dozen items. So my "index" is out of sync with my ports??? What did I screw up and how do I correct 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: xorg-server-1.7.7_6,1 crashes (from ports head)
El día Wednesday, May 08, 2013 a las 02:58:18PM -0700, Waitman Gobble escribió: > > Please be kind and give me some hints about best options I have: > > > > - Do we have another Xserver in the ports to try? > > - Should I post a bug report in our Gnats? > > - Should I go to the lists.x.org? > > - Any options of the Xorg server to test or to get debug messages of the > > crash? > > - Anything else? > > > > I have already ordered a new 2 GByte ddr2 RAM to change the memory, but > > as well it could be the video card or anthing else... > > > > What video driver are you using on that machine? Hi, The full Xorg.0.log was attached to the original posting in freebsd-x11, see here for details: http://lists.freebsd.org/pipermail/freebsd-x11/2013-May/013040.html The video driver is: (II) LoadModule: "intel" (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.7.7, module version = 2.7.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 ... (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, Mobile Intel? GM45 Express Chipset, Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41 Meanwhile I have changed the RAM in the netbook, it does not help either; Thanks matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ 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: xorg-server-1.7.7_6,1 crashes (from ports head)
"Matthias Apitz" wrote: > > El día Tuesday, May 07, 2013 a las 02:45:39PM +0200, Matthias Apitz escribió: > > > xorg-server-1.7.7_6,1 X.Org X server and related programs > > > > all ports are from r315646 (1st of April); > > > > I randomly face X11 crashes with the following symtoms: > > > > - the display is filled with some colored pattern > > > > - X11 seems to be still running, because I can switch with Ctrl-Alt-F1 > > to the console where "startx" was launched; and Alt+F9 brings back to > > the unuseable display; > > ... > > Hello, > > Until know the reaction in our mailing list is easy to count: zero :-( > > Please be kind and give me some hints about best options I have: > > - Do we have another Xserver in the ports to try? > - Should I post a bug report in our Gnats? > - Should I go to the lists.x.org? > - Any options of the Xorg server to test or to get debug messages of the > crash? > - Anything else? > > I have already ordered a new 2 GByte ddr2 RAM to change the memory, but > as well it could be the video card or anthing else... > > Thanks > > matthias > > > -- > Sent from my FreeBSD netbook > > Matthias Apitz | - No system with backdoors like Apple/Android > E-mail: g...@unixarea.de | - Never being an iSlave > WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail > phone: +49-170-4527211 | - Respect for open standards > ___ > 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, What video driver are you using on that machine? Waitman Gobble San Jose California ___ 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: xorg-server-1.7.7_6,1 crashes (from ports head)
El día Tuesday, May 07, 2013 a las 02:45:39PM +0200, Matthias Apitz escribió: > xorg-server-1.7.7_6,1 X.Org X server and related programs > > all ports are from r315646 (1st of April); > > I randomly face X11 crashes with the following symtoms: > > - the display is filled with some colored pattern > > - X11 seems to be still running, because I can switch with Ctrl-Alt-F1 > to the console where "startx" was launched; and Alt+F9 brings back to > the unuseable display; > ... Hello, Until know the reaction in our mailing list is easy to count: zero :-( Please be kind and give me some hints about best options I have: - Do we have another Xserver in the ports to try? - Should I post a bug report in our Gnats? - Should I go to the lists.x.org? - Any options of the Xorg server to test or to get debug messages of the crash? - Anything else? I have already ordered a new 2 GByte ddr2 RAM to change the memory, but as well it could be the video card or anthing else... Thanks matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ 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"
TexLive in ports running endless on compile?
Hi, I've seen that texlive has finally landed in the ports tree and as I had a fresh and clean setup system ready I tried it out. I tried to install texlive-full which started out okay but the last line in my terminal is: fmtutil: running `ptex -ini -jobname=ptex -progname=ptex ptex.ini #ptex' ... The ptex job is now running for 6 hours on a system with an i5 cpu and an ssd. Is this normal or is something broken here? Regards, Jens -- 07. Wonnemond 2013, 17:13 Homepage : http://www.jan0sch.de Invest in physics -- own a piece of Dirac! pgpwA1bly0t6S.pgp Description: PGP signature
Re: Managing conflicts between ports (same package with multiple maintained versions)
Thanks Matthew, your recommendation works for me. As I expect from time to time also an older version getting EOL'd, the amount of versions to look ahead can be estimated quite well. Kind regards, Matthias On 04/21/13 17:57, Matthew Seaman wrote: On 21/04/2013 10:24, Matthias Petermann wrote: root@compaq:/usr/ports/finance/trytond # portlint -AC [...] FATAL: Package conflicts with itself. You should remove "trytond-*" from CONFLICTS. 1 fatal error and 4 warnings found. root@compaq:/usr/ports/finance/trytond # So it looks like I need to explicitly specify the conflicting versions, e.g. in Tryton 2.4 Makefile put: CONFLICTS= trytond-2.6.* But this will force me to update the 2.4 Ports everytime a new series of Tryton gets introduced. The usual idiom would be to use a more complex globbing expression, perhaps like so: CONFLICTS= trytond-2.[012356789].* However clearly this won't account for all possible future versions. The thing you have to ask yourself is 'will the upstream be releasing new version series so frequently that I need to add code to all the tryton ports to account for it?' It may well be the case that updating the CONFLICTS setting in all the ports for the different streams whenerver a new stream is released really is the most effective solution. Cheers, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Managing conflicts between ports (same package with multiple maintained versions)
On 21/04/2013 10:24, Matthias Petermann wrote: > root@compaq:/usr/ports/finance/trytond # portlint -AC > [...] > FATAL: Package conflicts with itself. You should remove "trytond-*" from > CONFLICTS. > 1 fatal error and 4 warnings found. > root@compaq:/usr/ports/finance/trytond # > > So it looks like I need to explicitly specify the conflicting versions, > e.g. in Tryton 2.4 Makefile put: > > CONFLICTS= trytond-2.6.* > > But this will force me to update the 2.4 Ports everytime a new series of > Tryton gets introduced. The usual idiom would be to use a more complex globbing expression, perhaps like so: CONFLICTS= trytond-2.[012356789].* However clearly this won't account for all possible future versions. The thing you have to ask yourself is 'will the upstream be releasing new version series so frequently that I need to add code to all the tryton ports to account for it?' It may well be the case that updating the CONFLICTS setting in all the ports for the different streams whenerver a new stream is released really is the most effective solution. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Managing conflicts between ports (same package with multiple maintained versions)
Hello, I am the maintainer of most of the Tryton ports. Tryton is a python based application framework where you can easily build your own business modules on top. It also provides some default modules for common uses. Currently Tryton 2.4 series is in the ports. From upstream the successor Tryton 2.6 is available. At Tryton, also previous releases are supported for an extended time. This is required, because users who spent time to build their own modules on top of e.g. 2.4 should not be forced to migrate immediately to 2.6 (and likely use a different API) just for a security patch or a bug fix. Thats why I want to bring in 2.6 to the ports while continuing maintaining 2.4. During the planning, I ran into the following issue: Tryton 2.4 and 2.6 install files to the same Python site-packages directory /usr/local/lib/python2.7/site-packages/trytond-2.4.5-py2.7.egg /usr/local/lib/python2.7/site-packages/trytond-2.6.3-py2.7.egg Even there "egg" names are different, the contained package names are equal: /usr/local/lib/python2.7/site-packages/trytond-2.4.5-py2.7.egg/trytond /usr/local/lib/python2.7/site-packages/trytond-2.6.3-py2.7.egg/trytond So for the python interpreter it would not be clear which one to import if you just "import trytond". Renaming the package names doesn't look reasonable because it would require patching all Tryton modules (and will make it incompatible with custom built modules). So I think it is required to define it as a conflict if two versions of Tryton will be installed at the same time. My first approach was to define CONFLICTS= trytond-* in the Makefiles of trytond 2.4 and 2.6. This works and prevents installing two different versions. But portlint doesn't seem happy with it: root@compaq:/usr/ports/finance/trytond # portlint -AC [...] FATAL: Package conflicts with itself. You should remove "trytond-*" from CONFLICTS. 1 fatal error and 4 warnings found. root@compaq:/usr/ports/finance/trytond # So it looks like I need to explicitly specify the conflicting versions, e.g. in Tryton 2.4 Makefile put: CONFLICTS= trytond-2.6.* But this will force me to update the 2.4 Ports everytime a new series of Tryton gets introduced. Is there a better way to achieve this? Thanks in advance & kind regards, Matthias ___ 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: chromium won't build on FreeBSD 9.1 ports rev 315799
On 17/04/2013 19:27, Andrei Brezan wrote: > You can try: > portupgrade -m -DDISABLE_VULNERABILITIES chromium > > From what I can see there is no update yet for the mentioned security > vulnerability. > > Regards, > Andrei Hi Andrei It seems there is an update in the source but not in the ports. Source is up to 26.mumble -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: chromium won't build on FreeBSD 9.1 ports rev 315799
On 04/17/13 18:40, John wrote: Hello list, In my daily vulnerability report, I'm seeing this: Affected package: chromium-25.0.1364.160 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html Latest ports update as of 1630 UTC - 315981 I try to update it. I get: portupgrade chromium ---> Upgrading 'chromium-25.0.1364.160' to 'chromium-25.0.1364.172' (www/chromium) ---> Building '/usr/ports/www/chromium' ===> Cleaning for chromium-25.0.1364.172 To build Chromium, you should have around 1 GB of memory and a fair amount of free diskspace (~ 2.2GB). ===> chromium-25.0.1364.172 has known vulnerabilities: Affected package: chromium-25.0.1364.172 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html => Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr/ports/www/chromium. *** [build] Error code 1 Stop in /usr/ports/www/chromium. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130417-83106-6ngbzf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=chromium-25.0.1364.160 UPGRADE_PORT_VER=25.0.1364.160 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/chromium (chromium-25.0.1364.160) (unknown build error) = I know the code is now at revision 26.something. I have a look at https://wiki.freebsd.org/Chromium and follow the instructions there. I get up to here: ../../depot_tools/gclient sync --force Error: Can't update/checkout ~/tmp/depot_tools/src if an unversioned directory is present. Delete the directory and try again. Please advise if/how I can proceed? thanks, ___ You can try: portupgrade -m -DDISABLE_VULNERABILITIES chromium From what I can see there is no update yet for the mentioned security vulnerability. Regards, Andrei ___ 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"
chromium won't build on FreeBSD 9.1 ports rev 315799
Hello list, In my daily vulnerability report, I'm seeing this: Affected package: chromium-25.0.1364.160 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html Latest ports update as of 1630 UTC - 315981 I try to update it. I get: portupgrade chromium ---> Upgrading 'chromium-25.0.1364.160' to 'chromium-25.0.1364.172' (www/chromium) ---> Building '/usr/ports/www/chromium' ===> Cleaning for chromium-25.0.1364.172 To build Chromium, you should have around 1 GB of memory and a fair amount of free diskspace (~ 2.2GB). ===> chromium-25.0.1364.172 has known vulnerabilities: Affected package: chromium-25.0.1364.172 Type of problem: chromium -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/bdd48858-9656-11e2-a9a8-00262d5ed8ee.html => Please update your ports tree and try again. *** [check-vulnerable] Error code 1 Stop in /usr/ports/www/chromium. *** [build] Error code 1 Stop in /usr/ports/www/chromium. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20130417-83106-6ngbzf-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=chromium-25.0.1364.160 UPGRADE_PORT_VER=25.0.1364.160 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/chromium (chromium-25.0.1364.160) (unknown build error) = I know the code is now at revision 26.something. I have a look at https://wiki.freebsd.org/Chromium and follow the instructions there. I get up to here: ../../depot_tools/gclient sync --force Error: Can't update/checkout ~/tmp/depot_tools/src if an unversioned directory is present. Delete the directory and try again. Please advise if/how I can proceed? thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Proper way to update ports with svn
Andre Goree wrote: > On Fri, 29 Mar 2013 21:52:41 -0400, Damien Fleuriot wrote: > >> On 29 March 2013 22:29, Andre Goree wrote: >> >>> I seem to have to run 'make index' in /usr/ports after I've run 'svn up >>> >>> >>> /usr/ports' in order to see which ports need to be updated using >>> >>> 'portversion'. This doesn't seem correct...and if so portsnap would >>> >>> seem like a much better tool. Perhaps I should be running 'make >>> >>> fetchindex' instead? I'm sure I've read about the correct way to do so, >>> >>> but it doesn't appear to be here: >>> >>> https://wiki.freebsd.org/PortsSubversionPrimer >>> >>> >>> >>> Thanks in advance for any advice. >> >> 'make index' looks good to me, it's the right way to do things imo. >> >> What bothers you, following 'make index', pkg version output seems dodgy >> ? >> >> > > Mainly, just the amount of time it takes to run "make index", lol. And > the fact that I never had to do so with portsnap. I'm thinking that > perhaps portsnap runs something similar to 'make fetchindex' within the > whole 'portsnap fetch update' process...? > In case you find this of interest, FWIW I changed from the old csup to using portsnap. I also still use portupgrade. This is the command I do to check for ports in need of update: # portsnap fetch update && portsdb -u && pkgdb -F && portversion The portsnap fetch update portion outputs "Building new INDEX files... done." at the end of its run. Notice the three subsequent commands are from the portupgrade package. Portsnap will alter or change the INDEX-7, INDEX-8, and INDEX-9 files. As pointed out elsewhere portupgrade manages its own index database file separately and in parallel, which is the INDEX-9.db file. At first glance it would seem that running portsdb and pkgdb might appear to be semi-superfluos, but doing so will check the package database and ensure it is exactly in sync with the ports INDEX-* files. I would rather pkgdb dump out an error if something is wrong, and it will if there is something not quite right in the package database. As long as everything is good it just sails on through and portversion tells me which ports are in need of upgrade. Then I read the new UPDATING file prior to doing portupgrade -a, following any instructions which may pertain. I have been doing this for 3-4 months now and it has served me well. I was doing something very similar back in the csup days, but I had to work out some small changes to the above command line using trial and error. The above result is very fast, as compared to just trying to use the same old identical CLI switches from csup days. To start from a clean slate I wiped /usr/ports and followed the Handbook commands of portsnap fetch followed by the portsnap extract commands. Once I had a new pristine ports tree I update it and check for new ports with the above command. It has worked well. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Proper way to update ports with svn
On Fri, 29 Mar 2013 21:52:41 -0400, Damien Fleuriot wrote: On 29 March 2013 22:29, Andre Goree wrote: I seem to have to run 'make index' in /usr/ports after I've run 'svn up /usr/ports' in order to see which ports need to be updated using 'portversion'. This doesn't seem correct...and if so portsnap would seem like a much better tool. Perhaps I should be running 'make fetchindex' instead? I'm sure I've read about the correct way to do so, but it doesn't appear to be here: https://wiki.freebsd.org/PortsSubversionPrimer Thanks in advance for any advice. 'make index' looks good to me, it's the right way to do things imo. What bothers you, following 'make index', pkg version output seems dodgy ? Mainly, just the amount of time it takes to run "make index", lol. And the fact that I never had to do so with portsnap. I'm thinking that perhaps portsnap runs something similar to 'make fetchindex' within the whole 'portsnap fetch update' process...? -- Andre Goree an...@drenet.info ___ 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: Proper way to update ports with svn
On Sat, 30 Mar 2013 08:56:12 -0400, Lowell Gilbert wrote: Andre Goree writes: I seem to have to run 'make index' in /usr/ports after I've run 'svn up /usr/ports' in order to see which ports need to be updated using 'portversion'. This doesn't seem correct...and if so portsnap would seem like a much better tool. Perhaps I should be running 'make fetchindex' instead? I'm sure I've read about the correct way to do so, but it doesn't appear to be here: https://wiki.freebsd.org/PortsSubversionPrimer Subversion is not relevant; it has not changed the use of the index file. 'portversion' is part of the portupgrade port, and requires not just an index but its own database version of the index file. Building your own index will be slightly more accurate for what is actually on your box, but fetching it will be much faster and nearly always accurate enough. Thanks for the insight! -- Andre Goree an...@drenet.info ___ 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: Proper way to update ports with svn
Andre Goree writes: > I seem to have to run 'make index' in /usr/ports after I've run 'svn up > /usr/ports' in order to see which ports need to be updated using > 'portversion'. This doesn't seem correct...and if so portsnap would > seem like a much better tool. Perhaps I should be running 'make > fetchindex' instead? I'm sure I've read about the correct way to do so, > but it doesn't appear to be here: > https://wiki.freebsd.org/PortsSubversionPrimer Subversion is not relevant; it has not changed the use of the index file. 'portversion' is part of the portupgrade port, and requires not just an index but its own database version of the index file. Building your own index will be slightly more accurate for what is actually on your box, but fetching it will be much faster and nearly always accurate enough. ___ 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: Portsnap gets ports that claim to be out of date
John Levine wrote: > When I do portsnap update and try building stuff, I get errors like this: ^^ > "Mk/bsd.port.mk", line 5: warning: You are using a ports file that > originated from CVS!! "Mk/bsd.port.mk", line 6: warning: The FreeBSD > project has switched from CVS to SubVersion. > "Mk/bsd.port.mk", line 7: warning: This CVS repository is NO LONGER > UPDATED! If you see this "Mk/bsd.port.mk", line 8: warning: message then > your tree is STALE and you need to follow "Mk/bsd.port.mk", line 9: > warning: the update instructions to receive any more updates. > > I'm not using CVS, I'm using portsnap. Any ideas? It's a 9.1 system, > fully up to date as far as I know. > Have you tried doing: portsnap fetch update instead of portsnap update? -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Portsnap gets ports that claim to be out of date
When I do portsnap update and try building stuff, I get errors like this: "Mk/bsd.port.mk", line 5: warning: You are using a ports file that originated from CVS!! "Mk/bsd.port.mk", line 6: warning: The FreeBSD project has switched from CVS to SubVersion. "Mk/bsd.port.mk", line 7: warning: This CVS repository is NO LONGER UPDATED! If you see this "Mk/bsd.port.mk", line 8: warning: message then your tree is STALE and you need to follow "Mk/bsd.port.mk", line 9: warning: the update instructions to receive any more updates. I'm not using CVS, I'm using portsnap. Any ideas? It's a 9.1 system, fully up to date as far as I know. ___ 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: Proper way to update ports with svn
On 29 March 2013 22:29, Andre Goree wrote: > I seem to have to run 'make index' in /usr/ports after I've run 'svn up > /usr/ports' in order to see which ports need to be updated using > 'portversion'. This doesn't seem correct...and if so portsnap would > seem like a much better tool. Perhaps I should be running 'make > fetchindex' instead? I'm sure I've read about the correct way to do so, > but it doesn't appear to be here: > https://wiki.freebsd.org/PortsSubversionPrimer > > Thanks in advance for any advice. > 'make index' looks good to me, it's the right way to do things imo. What bothers you, following 'make index', pkg version output seems dodgy ? ___ 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"
Proper way to update ports with svn
I seem to have to run 'make index' in /usr/ports after I've run 'svn up /usr/ports' in order to see which ports need to be updated using 'portversion'. This doesn't seem correct...and if so portsnap would seem like a much better tool. Perhaps I should be running 'make fetchindex' instead? I'm sure I've read about the correct way to do so, but it doesn't appear to be here: https://wiki.freebsd.org/PortsSubversionPrimer Thanks in advance for any advice. -- Andre Goree an...@drenet.info ___ 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: security/heimdal generates openssl conflict [was - Re: Installing openssl from ports]
On 26/03/2013 11:53, Shane Ambler wrote: Either the man pages list is incorrect or heimdal installs a duplicate copy of the openssl man pages - maybe this could be disabled if openssl from ports is used. For reference - heimdal includes source for libhcrypto which it uses if openssl is not present. While it doesn't install libhcrypto it still installs the man pages which conflicts with the openssl port man pages. I have submitted a patch to fix this - http://www.freebsd.org/cgi/query-pr.cgi?pr=177397 ___ 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: security/heimdal generates openssl conflict [was - Re: Installing openssl from ports]
On 26/03/2013 00:42, Jim Ballantine wrote: Hi I had removed the port, but it was reinstalled as a dependency of other ports. I have WITH_OPENSSL_PORT=yes in /etc/make.conf, and after I do a pkg delete -f heimdal openssl installs fine, but when I try to install heimdal from ports (with DISABLE_CONFLICTS= openssl-1.0.1_8 in the Makefile) the installs ends with: Stop in /usr/ports/security/heimdal. So I must be doing something wrong, but what?? Your not doing anything wrong, that's why I cc'd the last email to the heimdal maintainer. I might look at making a patch to fix it today and submit a PR as it appears the maintainer didn't respond to a previous PR From what I see heimdal includes the openssl man pages in it's list of files it installs, the new pkg system is picking up the same files installed by openssl and heimdal and preventing the conflict, while the old install system overlooked it. Either the man pages list is incorrect or heimdal installs a duplicate copy of the openssl man pages - maybe this could be disabled if openssl from ports is 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"
security/heimdal generates openssl conflict [was - Re: Installing openssl from ports]
On 23/03/2013 00:21, Jim Ballantine wrote: Both openssl and heimdal install fine from the base system src, it's only when I try to install openssl from the ports, with heimdal installed by the base system that I get the error. When I run make install, what I get before the conflict message is: ===> Compressing manual pages for openssl-1.0.1_8zopenssl-1.0.1_8 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib Installing openssl-1.0.1_8...pkg: openssl-1.0.1_8 conflicts with heimdal-1.5.2_4 (installs files into the same place). Problematic files: /usr/local/man/man3/DH_generate_key.3.gz > *** [fale-pkg] Error code 70 I'll make the subject a bit more descriptive and cc the heimdal maintainer. The error appears to be generated by pkg and would indicate that you have installed heimdal from ports. heimdal uses libcrypto from openssl and may have been installed as a dependency for another port. The base system doesn't install into /usr/local and pkg shouldn't monitor any files installed by the base system, so the conflict with /usr/local/man/man3/DH_generate_key.3.gz must be from the heimdal port. I just tried a compile of heimdal within tinderbox where I have set WITH_OPENSSL_PORT=true and the log for the heimdal indicates that it deletes man pages installed by security/openssl. So either heimdal installs a duplicate copy of the openssl man pages or it erroneously includes the man pages in it's package list generation. part of tinderbox log - ===> Building package for heimdal-1.5.2_4 Deleting heimdal-1.5.2_4 === Checking filesystem state list of files present before this port was installed but missing after it was deinstalled) ./usr/local/man/man3/DES_cbc_cksum.3.gz missing ./usr/local/man/man3/DH_free.3.gz missing ./usr/local/man/man3/DH_generate_key.3.gz missing ./usr/local/man/man3/DH_get_default_method.3.gz missing ./usr/local/man/man3/RSA_new.3.gz missing ./usr/local/man/man3/RSA_new_method.3.gz missing ./usr/local/man/man3/RSA_set_method.3.gz missing Deleting sqlite3-3.7.14.1 Deleting openssl-1.0.1_8 pkg_delete: file '/usr/local/man/man3/DH_generate_key.3.gz' doesn't exist pkg_delete: file '/usr/local/man/man3/DH_new.3.gz' doesn't exist pkg_delete: file '/usr/local/man/man3/DH_set_method.3.gz' doesn't exist pkg_delete: file '/usr/local/man/man3/DES_set_odd_parity.3.gz' doesn't exist pkg_delete: file '/usr/local/man/man3/DES_string_to_key.3.gz' doesn't exist pkg_delete: couldn't entirely delete package `openssl-1.0.1_8' (perhaps the packing list is incorrectly specified?) Deleting libtool-2.4.2 Deleting libXt-1.1.1,1 Deleting db41-4.1.25_4 ___ 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: Installing openssl from ports
The port is newer than the base version: port is 1.0.1_8 and the base is 0.9.2 Both openssl and heimdal install fine from the base system src, it's only when I try to install openssl from the ports, with heimdal installed by the base system that I get the error. When I run make install, what I get before the conflict message is: ===> Compressing manual pages for openssl-1.0.1_8zopenssl-1.0.1_8 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib Installing openssl-1.0.1_8...pkg: openssl-1.0.1_8 conflicts with heimdal-1.5.2_4 (installs files into the same place). Problematic files: /usr/local/man/man3/DH_generate_key.3.gz *** [fale-pkg] Error code 70 On Fri, Mar 22, 2013 at 8:09 AM, Shane Ambler wrote: > On 22/03/2013 04:36, Jim Ballantine wrote: > > But when I attempt to install the latest openssl for the >> port system, it fails with a conflict (installs file in the same place) >> with heimdal. >> > > Take a close look at the message and what happens before. openssl only > gives a conflict message if the base version is newer than the port. > > Heimdal conflicts with krb4 krb5 and srp > > Any other conflicts will be from dependencies, you'll need to check what > port brings in a dependency that generates the conflict. > > > ___ 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: Installing openssl from ports
On 22/03/2013 04:36, Jim Ballantine wrote: But when I attempt to install the latest openssl for the port system, it fails with a conflict (installs file in the same place) with heimdal. Take a close look at the message and what happens before. openssl only gives a conflict message if the base version is newer than the port. Heimdal conflicts with krb4 krb5 and srp Any other conflicts will be from dependencies, you'll need to check what port brings in a dependency that generates the conflict. ___ 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: Installing openssl from ports
On Thu, 21 Mar 2013 14:06:52 -0400 Jim Ballantine articulated: > Hi, > > I understand that heimdal and openssl are both port of the base > system and both install > fine with a system build/install. But when I attempt to install the > latest openssl for the > port system, it fails with a conflict (installs file in the same > place) with heimdal. I've search > the web for an answer but haven't found one and asked the port owner. > > So my question is short of editing the Make file to remove the > installation of the file in > conflict, what do I need to do to install the openssl port? I have the port version installed also. You need to put this in your /etc/make.conf file sans quotations marks: "WITH_OPENSSL_PORT=yes" and then build the port. Be sure to run "make config" in the port prior to actually building it and that is about it. If you are building it manually, you might want to run "make clean" in the port prior to attempting to build it though. -- Jerry ♔ 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"
Installing openssl from ports
Hi, I understand that heimdal and openssl are both port of the base system and both install fine with a system build/install. But when I attempt to install the latest openssl for the port system, it fails with a conflict (installs file in the same place) with heimdal. I've search the web for an answer but haven't found one and asked the port owner. So my question is short of editing the Make file to remove the installation of the file in conflict, what do I need to do to install the openssl port? Thanks Jim Ballantine ___ 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"
ports issue: delete upstream perl dependencies by mistake
I did something dumb I think with ports on my box. In the process of upgrading Perl, for every package that depended on Perl, via pkgdb, I somehow managed to delete the fact that the package depends on Perl itself. So now I have a bunch of packages that no longer reference Perl in it's upstream dependency listing. e.g. $ pkg_info -R p5-Mail-SpamAssassin-3.3.2_8 Information for p5-Mail-SpamAssassin-3.3.2_8: $ How can I fix this? Short of deleting all the packages (which I don't even know all they are, except for the p5-ones) and rebuilding? Thanks in advance, Alex ___ 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: "make deinstall" within /usr/ports/lang - need to recover default language installs
Dear Chaps, Thank you very much for responding so quickly. Curiously the freeBSD 9.0 was installed with the standard answers to a sysinstall session and did contain a version of perl. I now seem to be in the state of discovering which languages I need and then re-installing. Is there a list/database for freeBSD 9.0 standard sysinstalls languages that I can view and use to re-install (via pkg_add -v -r perl etc) ? [there must a config file for sysinstall to use itself] Kind regards, Rob > lang/ contains all languages and so on ruby, lua, python, perl.. Of > course you removed perl since you typed make deinstall in that parent > port tree. > > You can type make install in /usr/ports/lang/perl5.14 to install it > again. You don't need to reinstall FreeBSD, you're not on Windows > here, you can repair everything :) > > Note: there is no perl installed by default, it's in the ports for few > years now. > > Regards, On 19/03/2013 01:19, Matthew Seaman wrote: > On 19/03/2013 07:54, Rob Navarro wrote: >> Hi Chaps, >> >> I typed "make deinstall" within the /usr/ports/lang directory of a >> FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of >> default compiled languages. >> >> How can I get back to the default FreeBSD default installed language >> state (with Perl installed etc)? > Ummm the default state is with just the base system installed: no > extra languages like perl or python and no other additional software > packages. > >> Crossing my fingers that I need not re-install the OS... > Nope. You absolutely do not need to do that -- all you did will have > affected the ports, which on FreeBSD is a distinct entity from the base > system. > > To recover, you simply need to re-install the appropriate ports. If you > know what you want installed, then it's easy: you can just feed a list > of those ports into portmaster(8) or portupgrade(8). > > If you don't know what you need installed in order to support various > end user programs, then there are various ways of checking that the > dependencies of the required ports are installed. For instance, if > you're using pkgng, you could run 'pkg check -da' At worst, and > requiring the least amount of extra software, just try re-installing the > packages in question. This should work, but you might end up doing a > lot of strictly unnecessary recompiling. > > Matthew > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ 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: "make deinstall" within /usr/ports/lang - need to recover default language installs
On 19/03/2013 07:54, Rob Navarro wrote: > Hi Chaps, > > I typed "make deinstall" within the /usr/ports/lang directory of a > FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of > default compiled languages. > > How can I get back to the default FreeBSD default installed language > state (with Perl installed etc)? Ummm the default state is with just the base system installed: no extra languages like perl or python and no other additional software packages. > Crossing my fingers that I need not re-install the OS... Nope. You absolutely do not need to do that -- all you did will have affected the ports, which on FreeBSD is a distinct entity from the base system. To recover, you simply need to re-install the appropriate ports. If you know what you want installed, then it's easy: you can just feed a list of those ports into portmaster(8) or portupgrade(8). If you don't know what you need installed in order to support various end user programs, then there are various ways of checking that the dependencies of the required ports are installed. For instance, if you're using pkgng, you could run 'pkg check -da' At worst, and requiring the least amount of extra software, just try re-installing the packages in question. This should work, but you might end up doing a lot of strictly unnecessary recompiling. Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: "make deinstall" within /usr/ports/lang - need to recover default language installs
lang/ contains all languages and so on ruby, lua, python, perl.. Of course you removed perl since you typed make deinstall in that parent port tree. You can type make install in /usr/ports/lang/perl5.14 to install it again. You don't need to reinstall FreeBSD, you're not on Windows here, you can repair everything :) Note: there is no perl installed by default, it's in the ports for few years now. Regards, 2013/3/19 Rob Navarro > Hi Chaps, > > I typed "make deinstall" within the /usr/ports/lang directory of a > FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of > default compiled languages. > > How can I get back to the default FreeBSD default installed language > state (with Perl installed etc)? > > Crossing my fingers that I need not re-install the OS... > > Kind regards, > > Rob > > ___ > 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" > -- Demelier David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
"make deinstall" within /usr/ports/lang - need to recover default language installs
Hi Chaps, I typed "make deinstall" within the /usr/ports/lang directory of a FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of default compiled languages. How can I get back to the default FreeBSD default installed language state (with Perl installed etc)? Crossing my fingers that I need not re-install the OS... Kind regards, Rob ___ 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: an upto date list of new ports
On Fri, Mar 1, 2013 at 8:50 AM, Aryeh Friedman wrote: > is there a site or other location that lists *NEW* (not updated) ports > since a given date? http://www.freshports.org/ has some limited options (24hrs, 48hrs, 7days, one month)... but since the ports tree is now under SVN, it's probably easier to use SVN directly to find out. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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"
an upto date list of new ports
is there a site or other location that lists *NEW* (not updated) ports since a given date? ___ 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: Ports & Packages [Stable] in sync
On Feb 17, 2013, at 3:44 PM, Jeff Tipton wrote: > On 02/17/2013 13:13, Damien Fleuriot wrote: >> On 16 Feb 2013, at 16:56, Jeff Tipton wrote: >> >>> Hi, >>> >>> I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are >>> no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at >>> the RELEASE versions, so I only have to compile when I need non-default >>> options or when there are no packages. Would it be possible to get the >>> ports snapshot that was used to compile the 9-STABLE packages? I think I >>> could use subversion but then I need to know the revision number of that >>> snapshot. What do you suggest? >>> >>> Thanks, >>> Jeff >>> >> Hi Jeff, >> >> I think you might be confused here. >> >> It is my understanding that there are ports for: >> - HEAD >> - x.y-RELEASE >> >> I don't think you're going to be able to get a snapshot from 9-STABLE, >> because -STABLE is a continuing work. >> >> What version do you consider to be 9-STABLE ? >> Every time there's a new commit you get a "new" 9-STABLE. >> ___ >> 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" > Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 weeks > but not every day, and it seems to be that because of the intrusion, it has > not been updated for long. The versions of the ports that come with the > 9.1-RELEASE are even slightly newer than those of 9-STABLE packages. I think > if I don't get the revision number from which the 9-STABLE was updated last > time I'll use the ports tree that comes with 9.1-RELEASE. I hope it won't > cause much version incompatibilities. I'm not sure where you're getting your 9-STABLE ports from, Jeff. In the SVN repository I only see release tags and HEAD: http://svn.freebsd.org/ports/ I also second Gilbert's advice about using HEAD for your ports tree, we do this here in production with over 50 boxes and have had no problems so far. If you still want to use the branch from 9.1-RELEASE, it's here: svn://svn.freebsd.org/ports/tags/RELEASE_9_1_0/ Note that, unless I'm wrong, you will not be getting *ANY* update to the ports tree then, it's frozen. This means no security updates and all, AFAICT. ___ 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: Ports & Packages [Stable] in sync
Jeff Tipton writes: > Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 > weeks but not every day, and it seems to be that because of the > intrusion, it has not been updated for long. The versions of the ports > that come with the 9.1-RELEASE are even slightly newer than those of > 9-STABLE packages. I think if I don't get the revision number from > which the 9-STABLE was updated last time I'll use the ports tree that > comes with 9.1-RELEASE. I hope it won't cause much version > incompatibilities. Um, not really. Or at least, not specific enough to be sure whether it is correct or not. The ports tree is not branched, and is intended to work with all supported branches and releases. In other words, regardless of whether you're running 9.1-RELEASE, 9-STABLE (in svn/cvs terms, RELENG_9), or 10.x (HEAD), you can (and, unless you have specific reasons otherwise, usually corporate security dictates) should use a ports tree checked out from HEAD. This is unrelated to whether packages are available for the ports on a particular branch or tag. Package availability is unusually limited at the moment, but that's because the build cluster has very limited capacity right now for a variety of reasons. That situation will improve over time, but until computers are infinitely fast, the package collection will lag somewhat behind the ports tree. Packages need to be built for a particular base system (or "close enough": generally all base-system versions in the same major-number release can run the packages for any other within that same series, most notably the -STABLE version). Additionally, -STABLE base system is "updated" by definition every time a developer checks into the relevant branch (currently RELENG_9). For ports, as I said earlier, there is no equivalent; updates go to HEAD, period. When packages get built for a particular base system is a matter of policy on the build cluster. I don't use downloaded packages for ports updates, but I would expect that to evolve as the new build cluster does. ___ 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: PostgreSQL 9.2: database replication on demand - easy way (Bucardo in ports not available)
On 02/16/2013 13:26, O. Hartmann wrote: Dear Sirs. I send my question to this list in the hope someone has the same problems and already found a solution. I will start explaining the background and my difficulties with recent solutions. We/I have a FreeBSD 10 box running a PostgreSQL 9.2 server containing literature references via RefDB, some sort of bugtracking via Bugzilla, several astronomical databases of the IAU (minor planet objects) and others. Those databases are kept and maintained on one single box at the department. Since a lot of the data is needed in my home office or at a lab with non-permanent internet connection, I desperately need to synchronize the databases kept on the "master" with some backup database systems acting as "master/slave" when they are online. The latter definition is fuzzy, since what I need is an automated synchronization of the "real" master with a sporadically upcoming "slave" at home or at field sites for my science where, as said, the internet connectivity isn't provided 24/7. I feel realy uncomfortable with the built-in streaming replication of PostgreSQL 9.2 since I never managed it to make a successful replication. As far as I understand, the streaming mechanism of PostgreSQL 9.X expects the "slaves" to be always online, to which the replication. I was said that Bucardo (http://bucardo.org/) would be the tool of choice, but FreeBSD ports seem not not have this tool. SLONY also is a way to complicated for my for just this task - or I'm to dumb to perform a solution that fits easily. Is someone out here who might have the same problems and already figured out how to solve this? I do not want to go into this crap "pg_dump", since I tried this many times and it failed due to some issues I never figured out why in PostgreSQL 9.2. Sorry being unspecific here, it is a long time since I tried this frustrating task and it boiled always down to some confusing "postgres/template1" issues when dumping the master and trying to update the "slave". Even following the textbook's suggestions ended up in a mess. Well, I appreaciate some hints and concepts (working, not hypothetical "could be's", those are floating enough around the FreeBSD related net). Thanks in advance and thanks for the patience, Oliver perhaps you could do WAL shipping .. ? ___ 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: Ports & Packages [Stable] in sync
On 02/17/2013 13:13, Damien Fleuriot wrote: On 16 Feb 2013, at 16:56, Jeff Tipton wrote: Hi, I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the RELEASE versions, so I only have to compile when I need non-default options or when there are no packages. Would it be possible to get the ports snapshot that was used to compile the 9-STABLE packages? I think I could use subversion but then I need to know the revision number of that snapshot. What do you suggest? Thanks, Jeff Hi Jeff, I think you might be confused here. It is my understanding that there are ports for: - HEAD - x.y-RELEASE I don't think you're going to be able to get a snapshot from 9-STABLE, because -STABLE is a continuing work. What version do you consider to be 9-STABLE ? Every time there's a new commit you get a "new" 9-STABLE. ___ 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" Thank you, Damien, for the reply. AFAIK, STABLE gets updated every 2 weeks but not every day, and it seems to be that because of the intrusion, it has not been updated for long. The versions of the ports that come with the 9.1-RELEASE are even slightly newer than those of 9-STABLE packages. I think if I don't get the revision number from which the 9-STABLE was updated last time I'll use the ports tree that comes with 9.1-RELEASE. I hope it won't cause much version incompatibilities. ___ 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: Ports & Packages [Stable] in sync
On 16 Feb 2013, at 16:56, Jeff Tipton wrote: > Hi, > > I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no > packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the > RELEASE versions, so I only have to compile when I need non-default options > or when there are no packages. Would it be possible to get the ports snapshot > that was used to compile the 9-STABLE packages? I think I could use > subversion but then I need to know the revision number of that snapshot. What > do you suggest? > > Thanks, > Jeff > Hi Jeff, I think you might be confused here. It is my understanding that there are ports for: - HEAD - x.y-RELEASE I don't think you're going to be able to get a snapshot from 9-STABLE, because -STABLE is a continuing work. What version do you consider to be 9-STABLE ? Every time there's a new commit you get a "new" 9-STABLE. ___ 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"
Ports & Packages [Stable] in sync
Hi, I upgraded 9.0 -> 9.1 on my netbook and only then found out that there are no packages for 9.1-RELEASE. On my desktops, I keep ports and packages at the RELEASE versions, so I only have to compile when I need non-default options or when there are no packages. Would it be possible to get the ports snapshot that was used to compile the 9-STABLE packages? I think I could use subversion but then I need to know the revision number of that snapshot. What do you suggest? Thanks, Jeff ___ 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"
PostgreSQL 9.2: database replication on demand - easy way (Bucardo in ports not available)
Dear Sirs. I send my question to this list in the hope someone has the same problems and already found a solution. I will start explaining the background and my difficulties with recent solutions. We/I have a FreeBSD 10 box running a PostgreSQL 9.2 server containing literature references via RefDB, some sort of bugtracking via Bugzilla, several astronomical databases of the IAU (minor planet objects) and others. Those databases are kept and maintained on one single box at the department. Since a lot of the data is needed in my home office or at a lab with non-permanent internet connection, I desperately need to synchronize the databases kept on the "master" with some backup database systems acting as "master/slave" when they are online. The latter definition is fuzzy, since what I need is an automated synchronization of the "real" master with a sporadically upcoming "slave" at home or at field sites for my science where, as said, the internet connectivity isn't provided 24/7. I feel realy uncomfortable with the built-in streaming replication of PostgreSQL 9.2 since I never managed it to make a successful replication. As far as I understand, the streaming mechanism of PostgreSQL 9.X expects the "slaves" to be always online, to which the replication. I was said that Bucardo (http://bucardo.org/) would be the tool of choice, but FreeBSD ports seem not not have this tool. SLONY also is a way to complicated for my for just this task - or I'm to dumb to perform a solution that fits easily. Is someone out here who might have the same problems and already figured out how to solve this? I do not want to go into this crap "pg_dump", since I tried this many times and it failed due to some issues I never figured out why in PostgreSQL 9.2. Sorry being unspecific here, it is a long time since I tried this frustrating task and it boiled always down to some confusing "postgres/template1" issues when dumping the master and trying to update the "slave". Even following the textbook's suggestions ended up in a mess. Well, I appreaciate some hints and concepts (working, not hypothetical "could be's", those are floating enough around the FreeBSD related net). Thanks in advance and thanks for the patience, Oliver signature.asc Description: OpenPGP digital signature
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"
Portmaster runs make config three times for some ports
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. -- Mike Clarke ___ 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"
warnings is rkhunter(8) about ports usage
Hello, I run rkhunter from time to time and have warnings about the diff between sockstat and netstat like this: [11:33:31] Warning: Differences found between sockstat and netstat output: [11:33:31] Sockstat output (ports in use): 0 1124 22 25 514 587 [11:33:31] Netstat output (ports in use): 22 25 514 587 the diff ports in sockstat are: $ sockstat | fgrep ' 0 ' root ipmon 695 0 dgram -> /var/run/logpriv $ sockstat | fgrep 1124 guru ssh-agent 1125 3 stream /tmp/ssh-KldJtKCKwQMi/agent.1124 Why is rkhunter complaining about them? Thx matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ 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: [kde-freebsd] ports, area51
On Sunday 03 February 2013 23:40:46 Olivier Smedts wrote: > Hi, > > 2013/2/3 ajtiM : > > Hi! > > > > I have installed KDE 4.9.5 and Calligra 2.5.5 from area51. > > I am not sure how is working: > > I use portsnap which update ports and KDE 4.9.5 ports are merged. Last > > time I saw many update for KDE 4.8.4 which "update" KDE 4.9.5 ports and > > so on. Does anyone knows when KDE 4.9.5 will be out in ports? They said > > after FreeBSD 9.1 but when should be the date for "after"? > > I think the answer is "now" : > > http://www.freshports.org/commit.php?category=astro&port=marble&files=yes&me > ssage_id=201302032010.r13kadmh024...@svn.freebsd.org > > Cheers Thank you. Mitja -- http://www.redbubble.com/people/lumiwa ___ 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: [kde-freebsd] ports, area51
Hi, 2013/2/3 ajtiM : > Hi! > > I have installed KDE 4.9.5 and Calligra 2.5.5 from area51. > I am not sure how is working: > I use portsnap which update ports and KDE 4.9.5 ports are merged. Last time I > saw many update for KDE 4.8.4 which "update" KDE 4.9.5 ports and so on. > Does anyone knows when KDE 4.9.5 will be out in ports? They said after FreeBSD > 9.1 but when should be the date for "after"? I think the answer is "now" : http://www.freshports.org/commit.php?category=astro&port=marble&files=yes&message_id=201302032010.r13kadmh024...@svn.freebsd.org Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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"
ports, area51
Hi! I have installed KDE 4.9.5 and Calligra 2.5.5 from area51. I am not sure how is working: I use portsnap which update ports and KDE 4.9.5 ports are merged. Last time I saw many update for KDE 4.8.4 which "update" KDE 4.9.5 ports and so on. Does anyone knows when KDE 4.9.5 will be out in ports? They said after FreeBSD 9.1 but when should be the date for "after"? Thank you. Mitja -- http://www.redbubble.com/people/lumiwa ___ 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"
[solved] How to fix a broken owner for files from world & build from ports?
It were > 20 directories/files with a wrong owner. ___ 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: How to fix a broken owner for files from world & build from ports?
I don't use space in filenames, I just wanted to ensure, that file names with spaces will be handled partly correctly. At the moment I'm not working intensively. Every once in a while I take a look at a directory and compare it with the backups. If there's something wrong, I manually run chown. I copy each step I'm doing to a file. Overcautious, without haste and without a script ;), I fix it step by step. Regards, Ralf ___ 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: How to fix a broken owner for files from world & build from ports?
On Tue, 29 Jan 2013 12:23:09 +0100, Ralf Mardorf wrote: > On Tue, 2013-01-29 at 10:08 +0100, Matthias Apitz wrote: > > This is a mayor damage and can only be repaired by a new installation. > > Perhaps true, but if such a simple mistake can't be fixed, [...] Excuse me, it's not a _simple_ mistake. It may have initially been even a typo, but anything executed with root privileges is not simple; root has the power to do anything, even to completely destroy the system, and that can also be as simple as calling rm or dd with "carefully carelessly crafted options", and there is no simple fix for this. > [...] what happens > when somebody makes a big mistake? The size of the mistake doesn't even matter. :-) > Perhaps more people stay with Linux > than other *NIX, regarding to the policy, that issues should be fixed > instead of always starting from the beginning. ;)? The fix to your issue is, in pseudocode: for part in ( OS , ports ) do: determine owner rocketmouse:* for all files compare with list with correct owner for each deviating file do: if owner != correct owner then: chown file to correct user fi od od Of course OS and ports have to be treated seperately. As you have mentioned to own a backup where the permissions (owners) are correct, obtaining the required reference data from that backup would be the easiest part. The alternative: reinstall world, reinstall ports. To avoid this task, you need to activate your admin skills. :-) > Of course, if I simply would restore from a dump, it will be less time > consuming and it wouldn't annoy you, but I would have the bad feeling, > that if ever needed, thinks can't be fixed, I always would have to > restore from backups. And what happens, if for what reason ever a backup > shouldn't be available? In that case, you would need other references to get the correct file owners. Files are usually installed to the system by the "install" command, and it is employed in the Makefiles for the OS and also for ports. As you correctly recognized, not simply all files belong to root, so everything "non-standard" could be derived from such "control files". Of course, the more files you have to treat (see wc -l of your result list), the harder the task can become, and maybe installing the port again is faster than finding out where permissions are set for the install program call. If you only have 10 files or so, do it manually, but if there are 100 and more files, coming from several different ports, reinstalling them sounds easier, and it's not a big deal to do that with portmaster. -- 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: How to fix a broken owner for files from world & build from ports?
On Tue, 29 Jan 2013 03:54:55 +0100, Ralf Mardorf wrote:
> On Tue, 29 Jan 2013 03:41:34 +0100, Joshua Isom wrote:
> > On 1/28/2013 7:56 PM, Ralf Mardorf wrote:
> >> Still not perfect, I guess I need something similar to ls -RAl for some
> >> directories :S and I didn't test what awk will do with names including a
> >> space.
> >
> > Try `find /dir -ls`. You can pipe it into sed like this `find /dir -ls|
> > sed -e 's%/dir%%g'` and then get something easily comparable.
>
> Cool, it does display the path, but there's still the other issue:
>
> $ touch test\ test
> $ find * -ls| sed -e 's%/dir%%g'| awk '{print $5" "$11}'
> rocketmouse test
>
> Perhaps awk isn't that important, but it e.g. will filter different file
> sizes, for e.g. configurations I edited in the meantime.
A thing regarding awk: For extended formatting, use the
printf() command which works the same as in sh and C, os
if you need, you can do things like
printf "%s '%s'", $1, $2;
Also note that you can have a custom delimiter for parsing
the input, e. g. -F ":" (if you would generate input lists
in :-separated CSV format).
Additionally, it seems you're running into the fun of spaces
in file names. Even though you can put them there, it doesn't
imply it's good to do it. Spaces are separators (for commands
and options), and everytime they're _not_ (e. g. when they
appear in file names), you need to care for this fact, by
escaping or quoting them.
Maybe those articles by David A. Wheeler are interesting
to you to learn about this annoyance for people writing
short shell scripts to automate tasks:
Filenames and Pathnames in Shell: How to do it correctly
http://www.dwheeler.com/essays/filenames-in-shell.html
Fixing Unix/Linux/POSIX Filenames:
Control Characters (such as Newline), Leading Dashes, and Other Problems
http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html
--
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"
How to fix a broken owner for files from world & build from ports?
I'm surprised, there's no /bin/sh for the backup: # ls -ld /bin/sh -r-xr-xr-x 1 rocketmouse wheel 142952 Dec 23 18:38 /bin/sh # ls -ld /usr/TMP4DIFF/bin/sh ls: /usr/TMP4DIFF/bin/sh: No such file or directory This is an error in reasoning :D. I compared the original /bin, with a restore from /usr, so it seems to be /bin, but it is /usr/bin ;). I have to keep the system as it is for at least a day, need to do something different and than I can continue, when I'm refreshed. root@freebsd:/usr/TMP4DIFF/ROOT # ls -l bin/sh -r-xr-xr-x 1 root wheel 142952 Dec 23 18:38 bin/sh :D There definitively is need for a real rest, to avoid mistakes. -- Sent from my PC while wearing my Relox watch and Iccug handback. If you pay me, product placement for your lemon could be placed here too, just mailto:/dev/null. ___ 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: How to fix a broken owner for files from world & build from ports?
On Tue, 29 Jan 2013 14:58:18 +0100, wrote: mtree I was confused, since the existing files only provide directories. Ok, I guess I understand, I can let mtree generate new files using the backup. I anyway need to take care about files that are missing by the backup. Thank you. -- Sent from my PC while wearing my Relox watch and Iccug handback. If you pay me, product placement for your lemon could be placed here too, just mailto:/dev/null. ___ 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: How to fix a broken owner for files from world & build from ports?
I suspect it's less effort to use Thunar and instead of scrolling, as I
did before (when I missed some wrong owners), to switch sorting by owner
between ascending and descending, to ensure not to miss a bad owner again.
I'm surprised, there's no /bin/sh for the backup:
/bin
# find /usr/TMP4DIFF/bin -ls | sed -e 's%/dir%%g' | awk '{print $5" "$11"
"$12" "$13}' > bin.TMP.txt
# find /bin -ls | sed -e 's%/dir%%g' | awk '{print $5" "$11" "$12" "$13}'
bin.BSD.txt
# diff bin.TMP.txt bin.BSD.txt > bin.DIF.txt
# grep rocketmouse bin.DIF.txt
rocketmouse /bin/sh
# ls -ld /bin/sh
-r-xr-xr-x 1 rocketmouse wheel 142952 Dec 23 18:38 /bin/sh
# ls -ld /usr/TMP4DIFF/bin/sh
ls: /usr/TMP4DIFF/bin/sh: No such file or directory
/lib
[snip ... no differences]
I anyway will unpack /usr too and take a look at the directories from the
backup. I won't bother you with each detail, but report a list of
differences, if there should be something very strange.
Regards,
Ralf
--
Sent from my PC while wearing my Relox watch and Iccug handback.
If you pay me, product placement for your lemon could be placed here too,
just mailto:/dev/nul.
___
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"
