Re: Postgresql 8.2 branch - keep it in tree
On Sun, Mar 25, 2012 at 06:18:16PM +0300, Konstantin Belousov wrote: > On Sun, Mar 25, 2012 at 12:54:36PM +, Chris Rees wrote: > > On 25 Mar 2012 13:51, "Radim Kolar" wrote: > > > > > > please do not remove this pgsql branch. its newest branch using old > > postgresql-contrib full text search engine. Upgrading to 8.3+ is not > > possible for such applications. > > > > I'm afraid it's not only end of life by upstream, but also vulnerable in > > more than one CVE, and will not be fixed. > Why is presence of a CVE relevant for 90% of all port users ? How are we supposed to know how people are using the ports? It is impossible to know how much the CVE will impact our users, keeping ports with known unfixed CVE is proposing potentially risky software to our users, which is not acceptable. If upstream has dropped their support for a given version, a maintainer has two choices: do himself the active support instead of upstream, or follow upstream policy and drop the port. regards, Bapt pgp49cezoHypy.pgp Description: PGP signature
Re: Where are conventions like -devel ports documented?
On Sun, Mar 25, 2012 at 11:24:59PM +0300, Gerald Pfeifer wrote: > Perhaps I am missing the obvious and will be rewarded with > embarrassement, but where are conventions like the use and > naming of -devel ports described? > > I would have expected this to be covered in > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html > but -- it is not. > > (If this is an omission, can someone more closely involved than > I have been so far donate a paragraph or two?) > > Gerald > > PS: I am thinking to split the existing emulators/wine port into > two, the regular one (tracking releases of Wine) and a -devel port > that tracks the bi-weekly snapshots that will lead to the next > release in a year or two. Somehow I would prefer something like > wine-stable / wine instead of wine / wine-devel, but the latter is > more in line with how we are doing things, right? Correct, the latter is how things are done. I think of it this way: as a user of wine I want the "wine" port/package to give me the best working version while "wine-devel" to give me a development version, for whatever "development version" means. It is clear to me that I'm getting something not as well tested as the latest release. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Where are conventions like -devel ports documented?
Op zo 25 mrt 2012 23:24:59 schreef Gerald Pfeifer: > Perhaps I am missing the obvious and will be rewarded with > embarrassement, but where are conventions like the use and > naming of -devel ports described? > > I would have expected this to be covered in > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html > but -- it is not. > Try this section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#PORTING-PKGNAME ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Where are conventions like -devel ports documented?
Perhaps I am missing the obvious and will be rewarded with embarrassement, but where are conventions like the use and naming of -devel ports described? I would have expected this to be covered in http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html but -- it is not. (If this is an omission, can someone more closely involved than I have been so far donate a paragraph or two?) Gerald PS: I am thinking to split the existing emulators/wine port into two, the regular one (tracking releases of Wine) and a -devel port that tracks the bi-weekly snapshots that will lead to the next release in a year or two. Somehow I would prefer something like wine-stable / wine instead of wine / wine-devel, but the latter is more in line with how we are doing things, right? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 6.4 stable
On 2012-03-25 20:26, Jos Chrispijn wrote: > I just re-animated an my old FreeBSD server but have some serious issues with > updating my ports collection: > > fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found > *** Error code 1 > > I already tried: > portupgrade make fetchindex > portupgrade make index > > but every time the first error comes up. Can someone tell me how solve this? > 6.4 is EOL but it seems the index is build for portsnap. Even in 8.3-RC2 you can find the following lines in /etc/portsnap.conf INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 At last on my 8.3-RC2 system INDEX-6 will be renewed per default during "portsnap update" So if you use portsnap you have a real chance to get INDEX-6 but ports are not guarantied to build since most of the 6.x specific parts are already removed from the ports tree. If you want to try portsnap rename /usr/ports to ports.old so you have your old tree as fall-back. -- Regards, olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD 6.4 stable
On 3/25/12 2:26 PM, Jos Chrispijn wrote: I just re-animated an my old FreeBSD server but have some serious issues with updating my ports collection: fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found *** Error code 1 I already tried: portupgrade make fetchindex portupgrade make index but every time the first error comes up. Can someone tell me how solve this? upgrade to FreeBSD 7.3 or 7.4 6.4 is not supported by ports tree anymore. Not only will you have problems with INDEX, but a lot of ports you want to (re)?build will have dependencies or libraries that don't exist in 6.4. (its not all that painful. build a 7.3/7.4 kernel with 6.x support, install it like 'make kernel KODIR=/boot/testkernel' nextboot -f testkernel (i think that is syntax) if it boots, follow instructions on rebuilding world and ports, make sure you put 7.3/4 kernel back on: make installkernel. if it doesn't boot, well, power cycle and it will boot your old 6.4 (but, ps, strange, I have a test machine still running 6.4 and I test ports on it. never had that issue) but the real answer is, upgrade so you don't have support problems. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD 6.4 stable
I just re-animated an my old FreeBSD server but have some serious issues with updating my ports collection: fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found *** Error code 1 I already tried: portupgrade make fetchindex portupgrade make index but every time the first error comes up. Can someone tell me how solve this? regards, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: _DEPENDS+= and make index speed
On 25/03/2012 17:22, Michael Scheidell wrote: > I don't think it hurts anything but if you have a bunch of ports > doing this, doesn't it have to slow down make index? The extra check > for, reassign and cat an undefined var has to take more cpu than a > strict assign, right or am I just nitpicking? Unlikely to make a significant difference. Most of the time in building the INDEX is spent doing file IO -- opening all those Makefiles, and the files they include, etc., ad nauseam. -- and then parsing the thousands of lines of make code. And then doing all over again for the next port. Couple of assignments using += in a couple of port specific Makefiles isn't much compared to that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
_DEPENDS+= and make index speed
Maybe it is because the last two prs in a row had it and that made me notice, or maybe I am spending more time looking over Makefile, but I have seen a couple of ports with BUILD_DEPENDS+= in cases where it was not needed. Wasn't a master or slave port. Was not wrapped in a .ifdef. port had no options to select or not. I don't think it hurts anything but if you have a bunch of ports doing this, doesn't it have to slow down make index? The extra check for, reassign and cat an undefined var has to take more cpu than a strict assign, right or am I just nitpicking? Nothing I think we need to go on the hunt for or publicly but is it something that committers and ports maintainers should just fix? Right? -- Michael Scheidell, CTO >|SECNAP Network Security ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/gnutls update when...
Jason Hellenthal wrote: > > Apparently this port has fell two versions behind. Is there anything > that is going to happen to update it to the current stable version ? > > > These advisories have been out for a week now. And the current version > is 2.12.18. > > > Database created: Sat Mar 24 13:15:03 EDT 2012 > Affected package: gnutls-2.12.16 > Type of problem: libtasn1 -- ASN.1 length decoding vulnerability. > Reference: > http://portaudit.FreeBSD.org/2e7e9072-73a0-11e1-a883-001cc0a36e12.html > > Affected package: gnutls-2.12.16 > Type of problem: gnutls -- possible overflow/Denial of service > vulnerabilities. > Reference: > http://portaudit.FreeBSD.org/aecee357-739e-11e1-a883-001cc0a36e12.html > > 2 problem(s) in your installed packages found. The port was updated to 2.12.18 with some hacks to prevent shlib version bump. Please report if you have any problems with that. Roman Bogorodskiy pgpepbxCPIb12.pgp Description: PGP signature
Re: Postgresql 8.2 branch - keep it in tree
On Sun, Mar 25, 2012 at 12:54:36PM +, Chris Rees wrote: > On 25 Mar 2012 13:51, "Radim Kolar" wrote: > > > > please do not remove this pgsql branch. its newest branch using old > postgresql-contrib full text search engine. Upgrading to 8.3+ is not > possible for such applications. > > I'm afraid it's not only end of life by upstream, but also vulnerable in > more than one CVE, and will not be fixed. Why is presence of a CVE relevant for 90% of all port users ? Sigh. > > Can you give more detail on exactly what you are trying to do? > > Chris > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" pgpJIBr4Sxl52.pgp Description: PGP signature
Re: Postgresql 8.2 branch - keep it in tree
On 25 Mar 2012 13:51, "Radim Kolar" wrote: > > please do not remove this pgsql branch. its newest branch using old postgresql-contrib full text search engine. Upgrading to 8.3+ is not possible for such applications. I'm afraid it's not only end of life by upstream, but also vulnerable in more than one CVE, and will not be fixed. Can you give more detail on exactly what you are trying to do? Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Postgresql 8.2 branch - keep it in tree
please do not remove this pgsql branch. its newest branch using old postgresql-contrib full text search engine. Upgrading to 8.3+ is not possible for such applications. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What about Firefox 11?
On 03/25/12 16:06, Heino Tiedemann wrote: Florian Smeets wrote: For those who cannot wait we are always looking for testes ;) svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox/ LOL. Do you mean those with the balls enough to try it out? Or is that a typo? :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
