Re: Updating Ports Question
On Mon, Jan 5, 2015 at 4:00 PM, John Merriam j...@johnmerriam.net wrote: If I then do another /usr/ports/infrastructure/bin/out-of-date I still see this: Collecting installed packages: ok Collecting port versions: ok Collecting port signatures: ok Outdated ports: devel/quirks # always-update - quirks-2.9 mail/roundcubemail # @php-5.4.35,@php-mcrypt-5.4.35,@php-pspell-5.4.35,@php-zip-5.4.35 - @php-5.4.36,@php-mcrypt-5.4.36,@php-pspell-5.4.36,@php-zip-5.4.36 www/pear,-utils# @php-5.4.35 - @php-5.4.36 Why do roundcubemail and pear still show up there when php has been updated? Trying to run a make update for either of them does nothing. Those are showing up because they were built against the older version of PHP and PHP modules. Those packages themselves did not change but you need to rebuild them. Ports won't rebuild a package you already have built. There might be a way to override that which I don't know about, but you can just find and delete them from /usr/ports/packages/* then 'make reinstall'. Tim.
Re: Updating Ports Question
On 2015-01-05, trondd tro...@gmail.com wrote: On Mon, Jan 5, 2015 at 4:00 PM, John Merriam j...@johnmerriam.net wrote: If I then do another /usr/ports/infrastructure/bin/out-of-date I still see this: Collecting installed packages: ok Collecting port versions: ok Collecting port signatures: ok Outdated ports: devel/quirks # always-update - quirks-2.9 mail/roundcubemail # @php-5.4.35,@php-mcrypt-5.4.35,@php-pspell-5.4.35,@php-zip-5.4.35 - @php-5.4.36,@php-mcrypt-5.4.36,@php-pspell-5.4.36,@php-zip-5.4.36 www/pear,-utils# @php-5.4.35 - @php-5.4.36 Why do roundcubemail and pear still show up there when php has been updated? Trying to run a make update for either of them does nothing. Those are showing up because they were built against the older version of PHP and PHP modules. Those packages themselves did not change but you need to rebuild them. Ports won't rebuild a package you already have built. There might be a way to override that which I don't know about, but you can just find and delete them from /usr/ports/packages/* then 'make reinstall'. Or just ignore the output from out-of-date, there won't be any real change for these other packages.
Re: Updating Ports Question
On 1/5/2015 7:46 PM, Stuart Henderson wrote: On 2015-01-05, trondd tro...@gmail.com wrote: On Mon, Jan 5, 2015 at 4:00 PM, John Merriam j...@johnmerriam.net wrote: If I then do another /usr/ports/infrastructure/bin/out-of-date I still see this: Collecting installed packages: ok Collecting port versions: ok Collecting port signatures: ok Outdated ports: devel/quirks # always-update - quirks-2.9 mail/roundcubemail # @php-5.4.35,@php-mcrypt-5.4.35,@php-pspell-5.4.35,@php-zip-5.4.35 - @php-5.4.36,@php-mcrypt-5.4.36,@php-pspell-5.4.36,@php-zip-5.4.36 www/pear,-utils# @php-5.4.35 - @php-5.4.36 Why do roundcubemail and pear still show up there when php has been updated? Trying to run a make update for either of them does nothing. Those are showing up because they were built against the older version of PHP and PHP modules. Those packages themselves did not change but you need to rebuild them. Ports won't rebuild a package you already have built. There might be a way to override that which I don't know about, but you can just find and delete them from /usr/ports/packages/* then 'make reinstall'. Or just ignore the output from out-of-date, there won't be any real change for these other packages. So long as I'm not doing something incorrectly, I think I'll go with option 2 and just ignore it since it's PHP, not like a library or something. Thanks again! -- John Merriam
Updating Ports Question
Hello. I am running 5.6-stable amd64 and using the -stable ports. I must be doing something wrong when I am updating ports. I do: cd /usr/ports cvs -q up -rOPENBSD_5_6 -Pd infrastructure/bin/out-of-date and I see: Collecting installed packages: ok Collecting port versions: ok Collecting port signatures: ok Outdated ports: devel/quirks # always-update - quirks-2.9 lang/php/5.4,-main,ap2 # 5.4.35 - 5.4.36 lang/php/5.4,-mcrypt # 5.4.35 - 5.4.36 lang/php/5.4,-pdo_mysql# 5.4.35 - 5.4.36 lang/php/5.4,-pspell # 5.4.35 - 5.4.36 lang/php/5.4,-zip # 5.4.35 - 5.4.36 mail/roundcubemail # @php-5.4.35,@php-mcrypt-5.4.35,@php-pspell-5.4.35,@php-zip-5.4.35 - @php-5.4.36,@php-mcrypt-5.4.36,@php-pspell-5.4.36,@php-zip-5.4.36 www/pear,-utils# @php-5.4.35 - @php-5.4.36 so I do: cd lang/php/5.4 env FLAVOR=ap2 SUBPACKAGE=-main make update (I would guess I probably don't need the env variables since it seems to be smart enough to update only what I have installed already but whatever) If I then do another /usr/ports/infrastructure/bin/out-of-date I still see this: Collecting installed packages: ok Collecting port versions: ok Collecting port signatures: ok Outdated ports: devel/quirks # always-update - quirks-2.9 mail/roundcubemail # @php-5.4.35,@php-mcrypt-5.4.35,@php-pspell-5.4.35,@php-zip-5.4.35 - @php-5.4.36,@php-mcrypt-5.4.36,@php-pspell-5.4.36,@php-zip-5.4.36 www/pear,-utils# @php-5.4.35 - @php-5.4.36 Why do roundcubemail and pear still show up there when php has been updated? Trying to run a make update for either of them does nothing. I must be doing something wrong or missing another step I should be doing but I'm not sure what it is. I haven't found any answers through searching. Any suggestions would be appreciated. Thanks! PS - devel/quirks is always there and I am assuming it should be? -- John Merriam
general ports question
So if one has a 5.3 release system running, but finds a desired package in say 5.1, will pkg_add work on this, assuming I adjust the PKG_PATH to point to a 5.1 package folder? Or will doing this cause other instabilities? Thanks, Richard
Re: general ports question
On Wed, Sep 18, 2013 at 06:16:20PM -0400, Richard Thornton wrote: So if one has a 5.3 release system running, but finds a desired package in say 5.1, will pkg_add work on this, assuming I adjust the PKG_PATH to point to a 5.1 package folder? Or will doing this cause other instabilities? The dependency mechanisms in pkg_add apply to the library of the base system. Meaning that if you manage to install a package from 5.1 on a pure 5.3 machine, your package has *no* dependency at all on any shared library whatsoever from the base system. So, yeah, you can install the books from 5.1. And some of the fonts. That's about it.
Re: general ports question
Ok, thanks for the help. Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. From: Marc EspieSent: Wednesday, September 18, 2013 6:24 PMTo: Richard ThorntonReply To: espie@nerim.netCc: OpenBSD general usage listSubject: Re: general ports question On Wed, Sep 18, 2013 at 06:16:20PM -0400, Richard Thornton wrote: So if one has a 5.3 release system running, but finds a desired package in say 5.1, will pkg_add work on this, assuming I adjust the PKG_PATH to point to a 5.1 package folder? Or will doing this cause other instabilities? The dependency mechanisms in pkg_add apply to the library of the base system. Meaning that if you manage to install a package from 5.1 on a pure 5.3 machine, your package has *no* dependency at all on any shared library whatsoever from the base system. So, yeah, you can install the books from 5.1. And some of the fonts. That's about it.
Ports question, net/pidgin (Finch bug)
Hey misc readers, (I don't see general questions on ports@, is this the right list?) As an avid user of Pidgin I decided to look into the distributed console based client Finch, after sifting through the man pages I managed to make the context menu work properly in xterm, but when I tried to use the port outside of X.. it didn't go over so well. After searching for solutions, I found that I could either: 1) Use the Escape key. 2) Remap the Alt key using, wsconsctl keyboard.map+=keycode 56=Cmd2 Escape Unfortunately, it's still not working as expected... pressing Alt(or Escape) + 'a' was supposed to bring up a context menu.. but it disappears suddenly. I'm using OpenBSD 4.3, with pidgin 2.3.1. -Brynet
Ports Question
I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file, since a lot ports dont compile some because of missing files to be downloaded, Others just give error that kernel interface has changed and the downloaded source is not compilable against the 4.2 kernel. Manpreet
Re: Ports Question
On Nov 27, 2007 1:55 PM, Manpreet Nehra [EMAIL PROTECTED] wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file, since a lot ports dont compile some because of missing files to be downloaded, Others just give error that kernel interface has changed and the downloaded source is not compilable against the 4.2 kernel. [...] If you follow -current, then you need to update your src and ports tree, rebuild the kernel, and then try building the ports (with the updated source). If you follow -release, then the snapshot should work fine. These are mere guesses, as your email lacks information. Oh, and if you follow -current http://www.openbsd.org/faq/current.html is a good place to look. -Amarendra
Re: Ports Question
On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. since a lot ports dont compile some because of missing files to be downloaded, Others just give error that kernel interface has changed and the downloaded source is not compilable against the 4.2 kernel. http://www.openbsd.org/faq/faq15.html#NoFun
Re: Ports Question
--- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. Using a snapshot ports tree to use with RELEASE or STABLE is very unintuitive. Shouldn't we simply just replace the older ports tarball? since a lot ports dont compile some because of missing files to be downloaded, Others just give error that kernel interface has changed and the downloaded source is not compilable against the 4.2 kernel. http://www.openbsd.org/faq/faq15.html#NoFun I don't see how this faq applies to the OP. It refers to making sure your source and your ports tree are in sync. It doesn't mention using the snapshot ports tree. // juan Looking for a X-Mas gift? Everybody needs a Flickr Pro Account. http://www.flickr.com/gift/
Re: Ports Question
On 2007/11/27 08:08, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. Using a snapshot ports tree to use with RELEASE or STABLE is very unintuitive. Shouldn't we simply just replace the older ports tarball? You don't use it with release or stable, you use it with a snapshot. http://www.openbsd.org/faq/faq15.html#NoFun I don't see how this faq applies to the OP. 15.4.1 - I'm getting all kinds of crazy errors. I just can't seem to get this ports stuff working at all. sounds about right to me.
Re: Ports Question
--- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 08:08, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. Using a snapshot ports tree to use with RELEASE or STABLE is very unintuitive. Shouldn't we simply just replace the older ports tarball? You don't use it with release or stable, you use it with a snapshot. Right, but is he using a snapshot? I don't think so. // juan Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
Re: Ports Question
On 2007/11/27 08:53, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 08:08, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. Using a snapshot ports tree to use with RELEASE or STABLE is very unintuitive. Shouldn't we simply just replace the older ports tarball? You don't use it with release or stable, you use it with a snapshot. Right, but is he using a snapshot? I don't think so. In that case, 4.2 release ports.tar.gz, dated Sept 1 2007, is the right one.
Re: Ports Question
i am using the 4.2 release and that's why wondering if the ports tree is a little outdated, since alot of stuff has changed over from september 1 to Novemeber 1 when 4.2 actually released. Arent the release base and ports in sync? On Nov 27, 2007 7:59 PM, Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 08:53, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 08:08, Juan Miscaro wrote: --- Stuart Henderson [EMAIL PROTECTED] wrote: On 2007/11/27 13:55, Manpreet Nehra wrote: I have been compiling the ports and some of the ports fail flat. On checking the ftp.openbsd.org, I found the ports.tar.gz was created on Sep 1. Will there be a newer ports file ftp ls /pub/OpenBSD/snapshots/ports.tar.gz 227 Entering Passive Mode (129,128,5,191,169,249) 150 Have a Gorilla. -r--r--r--1 1114 1114 13733974 Nov 26 04:05 ports.tar.gz 226 There, everyone likes a Gorilla. ftp bye 221 Goodbye. Using a snapshot ports tree to use with RELEASE or STABLE is very unintuitive. Shouldn't we simply just replace the older ports tarball? You don't use it with release or stable, you use it with a snapshot. Right, but is he using a snapshot? I don't think so. In that case, 4.2 release ports.tar.gz, dated Sept 1 2007, is the right one.
Re: Ports Question
--- Ted Unangst [EMAIL PROTECTED] wrote: On 11/27/07, Manpreet Nehra [EMAIL PROTECTED] wrote: i am using the 4.2 release and that's why wondering if the ports tree is a little outdated, since alot of stuff has changed over from september 1 to Novemeber 1 when 4.2 actually released. Arent the release base and ports in sync? it's not possible to build thousands of packages and burn cdroms and then ship them so that they arrive before the release date if we start on the release date. I think he's talking about having the ports tree updated online. // juan Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/
Re: Ports Question
On 11/27/07, Manpreet Nehra [EMAIL PROTECTED] wrote: i am using the 4.2 release and that's why wondering if the ports tree is a little outdated, since alot of stuff has changed over from september 1 to Novemeber 1 when 4.2 actually released. Arent the release base and ports in sync? it's not possible to build thousands of packages and burn cdroms and then ship them so that they arrive before the release date if we start on the release date.
Re: Ports Question
On Nov 27, 2007 9:56 PM, Manpreet Nehra [EMAIL PROTECTED] wrote: i am using the 4.2 release and that's why wondering if the ports tree is a little outdated, since alot of stuff has changed over from september 1 to Novemeber 1 when 4.2 actually released. Arent the release base and ports in sync? [...] Actually not. It is the correct ports tree you are looking at. Though 4.2 officially released on 01/Nov/2007, the src was tagged earlier, and on 01/Nov, developers' were working on -current. -Amarendra
ports question
Sometimes ports have helpful messages that tell you the proper way to start it from rc.local or some other set of instructions that shoudl be your next step etc... Sometimes these get installed as a dependency of another app though and so the screen just keeps right on trucking and you don't have time to read it. Is there some command or somewhere you can go to see what the message was? --Bryan
Re: ports question
Bryan Irvine wrote: Sometimes these get installed as a dependency of another app though and so the screen just keeps right on trucking and you don't have time to read it. Is there some command or somewhere you can go to see what the message was? $ man pkg_info The argument you're looking for is '-M'. -- Matthew Weigel
Re: ports question
On Wed, Oct 11, 2006 at 03:28:08PM -0700, Bryan Irvine wrote:
Sometimes these get installed as a dependency of another app
though and so the screen just keeps right on trucking and you
don't have time to read it. Is there some command or somewhere
you can go to see what the message was?
$ man pkg_info
$ pkg_info -D python-2.4.3p0
Information for python-2.4.3p0
Install notice:
If you want to use this package as your default system python, create
symbolic links like so:
ln -s /usr/local/bin/python2.4 /usr/local/bin/python
ln -s /usr/local/bin/pydoc2.4 /usr/local/bin/pydoc
--
o--{ Will Maier }--o
| web:...http://www.lfod.us/ | [EMAIL PROTECTED] |
*--[ BSD Unix: Live Free or Die ]--*
Re: ports question
On 10/11/06, Matthew Weigel [EMAIL PROTECTED] wrote: Bryan Irvine wrote: Sometimes these get installed as a dependency of another app though and so the screen just keeps right on trucking and you don't have time to read it. Is there some command or somewhere you can go to see what the message was? $ man pkg_info The argument you're looking for is '-M'. Bingo! thanks! --Bryan
Re: ports question
PKG_INFO(1)OpenBSD Reference Manual NAME pkg_info - a utility for displaying information on software packages [...] -D Show the install-message file (if any) for each package (depre- cated option). -M Show the install-message file (if any) for each package. On Wed, 11 Oct 2006, Bryan Irvine wrote: Sometimes ports have helpful messages that tell you the proper way to start it from rc.local or some other set of instructions that shoudl be your next step etc... Sometimes these get installed as a dependency of another app though and so the screen just keeps right on trucking and you don't have time to read it. Is there some command or somewhere you can go to see what the message was? --Bryan l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ...from back in the heady days when helpdesk meant nothing, diskquota meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were.
Upgrading packages from ports question
Hi everybody, I'm getting familiar with ports at the moment since I restricted myself to using packages exclusively in the past. I have been skimming throught the FAQ and the manpages covering ports and the possible make targets. I have also read the chapter covering ports in Secure architectures with OpenBSD. There are some questions that I couldn't find the answers to, however. I have read about the out-of-date tool in /usr/ports/infrastructure/ build/ yet I coudn't find a manpage on the OpenBSD website or any other reference to it. What I'm after is something like this: I'm using DarwinPorts on an Apple Mac OS X machine. When I want to sync the tree I simply do a port sync and maybe a port selfupdate to update the DarwinPorts system itself. This would correspond to doing a CVS checkout or update. So far no problem :-) Now I'd do a port outdated to see what ports need upgrading. This corresponds to doing a ./infrastructure/build/out-of-date in /usr/ src. Still no problem. Now comes the tricky part. Using DarwinPorts I'd do a port upgrade installed to upgrade all installed ports. What would correspond to this in OpenBSD? Do I have to go after each individual port and its dependencies myself that gets mentioned by out-of-date like described in Secure architectures with OpenBSD? Brandon Palmer and Jose Nazario write that it would be easier to just upgrade an entire ports tree. How is this done? Let's say, out-of-date outputs a collection of 7 packages. How do I get rid of the 7 old installed packages, install the seven newer versions of those packages, including removing, rebuilding and installing all depending packages through ports in a convenient way like port upgrade installed? kind regards, Tobias W.
Re: Upgrading packages from ports question
Sorry, meant to send to list as well... On 5/24/06, Tobias Weisserth [EMAIL PROTECTED] wrote: Hi everybody, I'm getting familiar with ports at the moment since I restricted myself to using packages exclusively in the past. I have been skimming throught the FAQ and the manpages covering ports and the possible make targets. I have also read the chapter covering ports in Secure architectures with OpenBSD. There are some questions that I couldn't find the answers to, however. I have read about the out-of-date tool in /usr/ports/infrastructure/ build/ yet I coudn't find a manpage on the OpenBSD website or any other reference to it. What I'm after is something like this: I'm using DarwinPorts on an Apple Mac OS X machine. When I want to sync the tree I simply do a port sync and maybe a port selfupdate to update the DarwinPorts system itself. This would correspond to doing a CVS checkout or update. So far no problem :-) Now I'd do a port outdated to see what ports need upgrading. This corresponds to doing a ./infrastructure/build/out-of-date in /usr/ src. Still no problem. Now comes the tricky part. Using DarwinPorts I'd do a port upgrade installed to upgrade all installed ports. What would correspond to this in OpenBSD? Do I have to go after each individual port and its dependencies myself that gets mentioned by out-of-date like described in Secure architectures with OpenBSD? Brandon Palmer and Jose Nazario write that it would be easier to just upgrade an entire ports tree. How is this done? Let's say, out-of-date outputs a collection of 7 packages. How do I get rid of the 7 old installed packages, install the seven newer versions of those packages, including removing, rebuilding and installing all depending packages through ports in a convenient way like port upgrade installed? It's ugly, and doesn't take care of eg updating first png, and only after that the packages that depend on it, but i sometimes use: for i in `/usr/ports/infrastructure/build/out-of-date | cut -f1 -d ` ; do cd /usr/ports/$i ; make update clean ; done And that obviously doesn't work with flavors. You could also look at FORCE_UPDATE in bsd.port.mk(5) - setting that in /etc/mk.conf will make system rebuild and reinstall ALL packages the port depends on - so better do make clean-depends somewhere along the line or you'll end up with left-overs from building all those packages. There's also a graphical ports browser somewhere in ports tree, but I didn't play much with it, that could possibly have a way to do that with a few clicks... maybe. HTH kind regards, Tobias W. -- viq
Re: Upgrade + ports question
On Tue, 18 Oct 2005, Keith Richardson wrote: Hello, This is my first attempt at actually upgrading a system. Usually, it was quicker to simply reinstall from scratch but now that is not the case. So... When I upgrade to from 3.7 - 3.8, I know I have to update my ports as well. Before I do any Oh My God! blunders, I would like to see if I am missing anything. I am running i386 3.7-release currently. Target is 3.8-stable. My plan so far: 1) Upgrade to OpenBSD 3.8 binary snapshots since 3.8 release will not be available for a few weeks. 2)fetch and build OpenBSD 3.8 -stable using the following FAQ as a guide. Snapshots are already past 3.8, so you will be doing a downgrade, this will not work. You'll have to wait for a 3.8 CD or until 3.8 is released on the ftp sites. -Otto http://www.openbsd.org/faq/faq5.html 3) Backup my existing /usr/ports 4) Update ports to 3.8-stable: From: http://www.se.openbsd.org/anoncvs.html (modified for my shell/desired tag) # *export [EMAIL PROTECTED]:/cvs* # *cd /usr* # *cvs -q get -rOPENBSD_3_8 -P ports* 5) make; make install in /usr/ports/devel/jdk/... (yes, this is only for java) Am I missing and/or doing anything wrong? -Keith OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD Athlon(tm) (AuthenticAMD 686-class) 1.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 1073258496 (1048104K) avail mem = 972713984 (949916K) using 4278 buffers containing 53764096 bytes (52504K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(56) BIOS, date 01/21/03, BIOS32 rev. 0 @ 0xfb520 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown pcibios0 at bios0: rev 2.1 @ 0xf/0xdf94 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdef0/160 (8 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT8366 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8366 PCI rev 0x00 ppb0 at pci0 dev 1 function 0 VIA VT8366 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Matrox MGA G400/G450 AGP rev 0x04 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ATT/Lucent FW322 1394 rev 0x61 at pci0 dev 10 function 0 not configured ohci0 at pci0 dev 11 function 0 NEC USB rev 0x41: irq 11, version 1.0 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci0 dev 11 function 1 NEC USB rev 0x41: irq 11, version 1.0 usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0 at pci0 dev 11 function 2 NEC USB rev 0x02: irq 10 ehci0: EHCI version 0.95 ehci0: companion controllers, 3 ports each: ohci0 ohci1 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: single transaction translator uhub2: 5 ports with 5 removable, self powered Texas Instruments ACX100A rev 0x00 at pci0 dev 12 function 0 not configured pciide0 at pci0 dev 13 function 0 Promise PDC20265 rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using irq 10 for native-PCI interrupt pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) cmpci0 at pci0 dev 14 function 0 C-Media Electronics CMI8738/C3DX Audio rev 0x10: irq 11 audio0 at cmpci0 pcib0 at pci0 dev 17 function 0 VIA VT8366 ISA rev 0x00 pciide1 at pci0 dev 17 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide1 channel 0 drive 0: WDC WD400BB-00CLB0 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide1: channel 1 disabled (no drives) vr0 at pci0 dev 18 function 0 VIA RhineII-2 rev 0x70: irq 11 address 00:50:2c:01:b5:26 icsphy0 at vr0 phy 1: ICS1893 10/100 PHY, rev. 1 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker sysbeep0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 it0 at isa0 port 0x290/8: IT87 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port
Re: Ports question
On Fri, Sep 30, 2005 at 03:12:33AM +0100, the unit calling itself Stuart Henderson wrote: --On 29 September 2005 20:36 -0500, J Moore wrote: Can someone tell me if and when the clamav in the -stable tree is going to have the security flaw patched? On Wednesday just gone. http://www.openbsd.org/cgi-bin/cvsweb/ports/security/clamav/Makefile I get the following errors when trying to make clamav v0.87 from the -stable ports tree: server-th.o(.text+0x98a): In function `acceptloop_th': : undefined reference to `cl_dup' collect2: ld returned 1 exit status *** Error code 1 Stop in /usr/ports/security/clamav/w-clamav-0.87/clamav-0.87/clamd (line 322 of Makefile). *** Error code 1 Stop in /usr/ports/security/clamav/w-clamav-0.87/clamav-0.87 (line 368 of Makefile). *** Error code 1 Stop in /usr/ports/security/clamav/w-clamav-0.87/clamav-0.87 (line 227 of Makefile). *** Error code 1 Stop in /usr/ports/security/clamav (line 1769 of /usr/ports/infrastructure/mk/bsd.port.mk).
Re: Ports question
On 9/29/05, Chad M Stewart [EMAIL PROTECTED] wrote: While not at all supported and could break things I have done in the past ## CLAMAV on OpenBSD cd /usr [EMAIL PROTECTED]:/cvs cvs get \ -rHEAD -Pports/security/clamav then go make a package and assuming that works, install it. YMMV and use at your own risk or demise. :) I did it this week on a 3.7 system, has been working nicely. This is how I do it too, except I isntall all of ports via cvs, and update the entire tree before updating. Definitely use at your own risk as Chad says. --Bryan
Ports question
I know ports questions are not supposed to be posted to misc@, but I've been unable to get a response there, so ... I run 3.7 -stable. A significant security issue with clamav was announced a week or so ago. I checked, and found no patch was available, so I posted to [EMAIL PROTECTED] The maintainer responded, and told me that he was responsible only for -current; someone else was responsible for -stable. He was kind enough to offer to handle this for me if I was willing to pay him, but I run my systems on a hobby basis. Anyway - I have found clamav to be useful, and would like to continue to use it if it's going to be maintained. Can someone tell me if and when the clamav in the -stable tree is going to have the security flaw patched? Thanks, Jay
Re: Ports question
--On 29 September 2005 20:36 -0500, J Moore wrote: Can someone tell me if and when the clamav in the -stable tree is going to have the security flaw patched? On Wednesday just gone. http://www.openbsd.org/cgi-bin/cvsweb/ports/security/clamav/Makefile
Re: Ports question
While not at all supported and could break things I have done in the past ## CLAMAV on OpenBSD cd /usr [EMAIL PROTECTED]:/cvs cvs get \ -rHEAD -Pports/security/clamav then go make a package and assuming that works, install it. YMMV and use at your own risk or demise. :) I did it this week on a 3.7 system, has been working nicely. -Chad
Re: Ports Question - Update
On Mon, 15 Aug 2005 21:22:15 -0500, Dave Feustel wrote: So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. Because they depend on it. pkg_delete does not require you to enter the /usr/ports/-directory, btw. But you have to remove everything depending and re-install. AFAIKD. Uwe
Re: Ports Question - Update
* Uwe Dippel [EMAIL PROTECTED] [2005-08-16 10:53]: On Mon, 15 Aug 2005 21:22:15 -0500, Dave Feustel wrote: So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. Because they depend on it. pkg_delete does not require you to enter the /usr/ports/-directory, btw. But you have to remove everything depending and re-install. AFAIKD. huh? pkg_add -r is your friend, updating packages inline. -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Ports Question - Update
On Tuesday 16 August 2005 03:41, Uwe Dippel wrote: On Mon, 15 Aug 2005 21:22:15 -0500, Dave Feustel wrote: So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. Because they depend on it. I was surprised to finally discover that. pkg_delete does not require you to enter the /usr/ports/-directory, btw. But you have to remove everything depending and re-install. AFAIKD. Uwe I tried using pkg_add -r unzip That didn't work, but I think the reason is that both the new and the old had the same version number (5.51).
Re: Ports Question - Update
On Tue, Aug 16, 2005 at 05:03:34AM -0500, Dave Feustel wrote: I tried using pkg_add -r unzip That didn't work, but I think the reason is that both the new and the old had the same version number (5.51). This is 3.7 behavior, newer pkg_add will update if something useful actually changed.
Ports Question - Update
I'm running release 3.7 and I've put the release src and ports trees in /usr. I've updated both trees using cvs. I remade unzip as per the instructions in ports.html. When I attempted to make install, I got an error message saying that unzip was already present (which it was). So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. -Update--- I finally found the newly made unzip-5.51.tgz and tried a pkg_add -r, but it didn't work (console log follows) == /usr/ports/packages/i386/all}ls -l total 244 -rw-r--r-- 3 root wheel 122973 Aug 14 13:11 unzip-5.51.tgz /usr/ports/packages/i386/all}sudo pkg_add -r unzip-5.51.tgz Password: Can't install unzip-5.51 because it's already installed /usr/sbin/pkg_add: unzip-5.51.tgz:Fatal error /usr/ports/packages/i386/all} ===
Ports Question
I'm running release 3.7 and I've put the release src and ports trees in /usr. I've updated both trees using cvs. I remade unzip as per the instructions in ports.html. When I attempted to make install, I got an error message saying that unzip was already present (which it was). So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. Thanks, Dave Feustel
Re: Ports Question
On Sun, Aug 14, 2005 at 01:51:02PM -0500, Dave Feustel wrote: I'm running release 3.7 and I've put the release src and ports trees in /usr. I've updated both trees using cvs. I remade unzip as per the instructions in ports.html. When I attempted to make install, I got an error message saying that unzip was already present (which it was). So I attempted to pkg_delete unzip and then got the following: === /usr/ports}cd archivers/unzip /usr/ports/archivers/unzip}sudo pkg_delete unzip Password: Can't remove unzip without also removing: xmms-1.2.10p0 kdeaddons-3.3.2 kdenetwork-3.3.2p0 xmms-mp3-1.2.10p0 /usr/ports/archivers/unzip} I don't understand why I would need to remove xmms, kdeaddons, and kdenetwork in order to remove unzip. Enlightenment will be appreciated. Thanks, Dave Feustel Try pkg_add -r unzip
