Re: Will we get a RELEASE-9.1 for Christmas?
On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. than portmaster start with os many errors. Is it better to deinstal previous version and try to install 1.0.4, please? Thanks. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 21/12/2012 14:12, Walter Hurry wrote: Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? No, actually that is teething problems with my code to ensure the version numbers are set consistently. As you can see, it doesn't work reliably yet... A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): Good to hear. $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ Could you show me the output from: ldd /usr/local/bin/VBoxBalloonCtrl objdump -p /usr/local/bin/VBoxBalloonCtrl This one is odd, because it is clearly an application that certainly should be able to find the shlibs it uses. It's possibly dependent on having LD_LIBRARY_PATH set in the environment, which is arguably a bug in the port. objdmp -p /usr/local/lib/libreoffice/program/configmgr.uno.so This is presumably a loadable object rather than a shared library. 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: Will we get a RELEASE-9.1 for Christmas?
On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt pgpYH9EbNPtke.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? What says pkg_info ? regards, Bapt pgpYBnWj1u4Vd.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
On Fri, 21 Dec 2012 17:13:56 +, Matthew Seaman wrote: Could you show me the output from: ldd /usr/local/bin/VBoxBalloonCtrl objdump -p /usr/local/bin/VBoxBalloonCtrl $ sudo ldd /usr/local/bin/VBoxBalloonCtrl /usr/local/bin/VBoxBalloonCtrl: VBoxRT.so (0x800832000) VBoxXPCOM.so (0x800b53000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x800e76000) libm.so.5 = /lib/libm.so.5 (0x801186000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x8013a7000) libc.so.7 = /lib/libc.so.7 (0x8015b4000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x801907000) librt.so.1 = /usr/lib/librt.so.1 (0x801beb000) libz.so.6 = /lib/libz.so.6 (0x801df) libthr.so.3 = /lib/libthr.so.3 (0x802004000) libssl.so.6 = /usr/lib/libssl.so.6 (0x802226000) libcrypto.so.6 = /lib/libcrypto.so.6 (0x802479000) libxml2.so.5 = /usr/local/lib/libxml2.so.5 (0x80281a000) libcurl.so.6 = /usr/local/lib/libcurl.so.6 (0x802b6b000) $ sudo objdump -p /usr/local/bin/VBoxBalloonCtrl /usr/local/bin/VBoxBalloonCtrl: file format elf64-x86-64-freebsd Program Header: PHDR off0x0040 vaddr 0x00400040 paddr 0x00400040 align 2**3 filesz 0x01c0 memsz 0x01c0 flags r-x INTERP off0x0200 vaddr 0x00400200 paddr 0x00400200 align 2**0 filesz 0x0015 memsz 0x0015 flags r-- LOAD off0x vaddr 0x0040 paddr 0x0040 align 2**21 filesz 0x00018f35 memsz 0x00018f35 flags r-x LOAD off0x00019000 vaddr 0x00619000 paddr 0x00619000 align 2**21 filesz 0x0b78 memsz 0x0e98 flags rw- DYNAMIC off0x000194f8 vaddr 0x006194f8 paddr 0x006194f8 align 2**3 filesz 0x01f0 memsz 0x01f0 flags rw- NOTE off0x0218 vaddr 0x00400218 paddr 0x00400218 align 2**2 filesz 0x0018 memsz 0x0018 flags r-- EH_FRAME off0x00015664 vaddr 0x00415664 paddr 0x00415664 align 2**2 filesz 0x07a4 memsz 0x07a4 flags r-- STACK off0x vaddr 0x paddr 0x align 2**3 filesz 0x memsz 0x flags rw- Dynamic Section: NEEDED VBoxRT.so NEEDED VBoxXPCOM.so NEEDED libstdc++.so.6 NEEDED libm.so.5 NEEDED libgcc_s.so.1 NEEDED libc.so.7 RPATH /usr/local/lib/virtualbox INIT0x402d28 FINI0x411034 HASH0x400230 STRTAB 0x4013d0 SYMTAB 0x400680 STRSZ 0xb24 SYMENT 0x18 DEBUG 0x0 PLTGOT 0x619730 PLTRELSZ0xb70 PLTREL 0x7 JMPREL 0x4021b8 RELA0x402080 RELASZ 0x138 RELAENT 0x18 VERNEED 0x402010 VERNEEDNUM 0x3 VERSYM 0x401ef4 Version References: required from libgcc_s.so.1: 0x0b792650 0x00 05 GCC_3.0 required from libstdc++.so.6: 0x056bafd3 0x00 04 CXXABI_1.3 0x08922974 0x00 03 GLIBCXX_3.4 required from libc.so.7: 0x077a28b0 0x00 02 FBSD_1.0 $ objdmp -p /usr/local/lib/libreoffice/program/configmgr.uno.so $ objdump -p /usr/local/lib/libreoffice/program/configmgr.uno.so /usr/local/lib/libreoffice/program/configmgr.uno.so: file format elf64-x86-64-freebsd Program Header: LOAD off0x vaddr 0x paddr 0x align 2**21 filesz 0x0007e1a0 memsz 0x0007e1a0 flags r-x LOAD off0x0007e1a0 vaddr 0x0027e1a0 paddr 0x0027e1a0 align 2**21 filesz 0x4d80 memsz 0x5288 flags rw- DYNAMIC off0x000823c8 vaddr 0x002823c8 paddr 0x002823c8 align 2**3 filesz 0x0260 memsz 0x0260 flags rw- EH_FRAME off0x0006510c vaddr 0x0006510c paddr 0x0006510c align 2**2 filesz 0x1d84 memsz 0x1d84 flags r-- STACK off0x vaddr 0x paddr 0x align 2**3 filesz 0x memsz 0x flags rw- Dynamic Section: NEEDED libcomphelpgcc3.so NEEDED libuno_cppuhelpergcc3.so.3 NEEDED libuno_cppu.so.3 NEEDED libuno_salhelpergcc3.so.3 NEEDED libuno_sal.so.3 NEEDED libxmlreader.so NEEDED libstdc++.so.6 NEEDED libm.so.5 NEEDED libgcc_s.so.1 NEEDED libthr.so.3 NEEDED libc.so.7 RPATH $ORIGIN:$ORIGIN/../ure-link/lib RUNPATH $ORIGIN:$ORIGIN/../ure-link/lib INIT0x13570 FINI0x61eb8 GNU_HASH0x158 STRTAB 0x2470 SYMTAB 0x610 STRSZ 0x502f SYMENT 0x18
Re: Will we get a RELEASE-9.1 for Christmas?
On 21/12/2012 18:01, Walter Hurry wrote: On Fri, 21 Dec 2012 17:13:56 +, Matthew Seaman wrote: Could you show me the output from: ldd /usr/local/bin/VBoxBalloonCtrl objdump -p /usr/local/bin/VBoxBalloonCtrl Thank you for that. [...] Dynamic Section: NEEDED VBoxRT.so NEEDED VBoxXPCOM.so NEEDED libstdc++.so.6 NEEDED libm.so.5 NEEDED libgcc_s.so.1 NEEDED libc.so.7 RPATH /usr/local/lib/virtualbox Looks perfectly normal to me. No idea why it isn't finding /usr/local/lib/virtualbox/VBoxRT.so given that information. I shall investigate even further. $ objdump -p /usr/local/lib/libreoffice/program/configmgr.uno.so RPATH $ORIGIN:$ORIGIN/../ure-link/lib RUNPATH $ORIGIN:$ORIGIN/../ure-link/lib Using $ORIGIN twice in the same path and using both RPATH and RUNPATH. OK. I can fix that. 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: Will we get a RELEASE-9.1 for Christmas?
On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Ok this is a problem with the seat belt and portmaster not with your setup. I disabled the seat belt for now until we find a better way. regards, Bapt pgpr3oEmX0uST.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
On Friday 21 December 2012 11:58:00 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? What says pkg_info ? regards, Bapt pkg_info shows many corrupted packages. For example: fontsproto-2.1.1Fonts extension headers foomatic-filters-4.0.7_1 Foomatic wrapper scripts fotoxx-11.03_1 Application to organize and edit image collections freeglut-2.8.0 An alternative to the OpenGL Utility Toolkit (GLUT) library freetype-1.3.1_4A free and portable TrueType font rendering engine freetype-tools-1.3.1_9 Tools for FreeType 1 freetype2-2.4.9_1 A free and portable TrueType font rendering engine frei0r-1.3_1Minimalistic plugin API for video effects fribidi-0.19.2_1A Free Implementation of the Unicode Bidirectional Algorith pkg_info: the package info for package 'gamin-0.1.10_4' is corrupt gawk-4.0.1 The GNU version of Awk gcc-4.6.3 GNU Compiler Collection 4.6 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' pkg_info: the package info for package 'gconf2-2.32.0_3' is corrupt gd-2.0.35_8,1 A graphics library for fast creation of images gdbm-1.9.1 The GNU database manager pkg_info: the package info for package 'gdk-pixbuf-2.23.5_3' is corrupt geeqie-1.1 Lightweight image viewer forked from GQview pkg_info: the package info for package 'gegl-0.1.8_4' is corrupt ... ... Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Fri, Dec 21, 2012 at 12:48:45PM -0600, ajtiM wrote: On Friday 21 December 2012 11:58:00 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? What says pkg_info ? regards, Bapt pkg_info shows many corrupted packages. For example: fontsproto-2.1.1Fonts extension headers foomatic-filters-4.0.7_1 Foomatic wrapper scripts fotoxx-11.03_1 Application to organize and edit image collections freeglut-2.8.0 An alternative to the OpenGL Utility Toolkit (GLUT) library freetype-1.3.1_4A free and portable TrueType font rendering engine freetype-tools-1.3.1_9 Tools for FreeType 1 freetype2-2.4.9_1 A free and portable TrueType font rendering engine frei0r-1.3_1Minimalistic plugin API for video effects fribidi-0.19.2_1A Free Implementation of the Unicode Bidirectional Algorith pkg_info: the package info for package 'gamin-0.1.10_4' is corrupt gawk-4.0.1 The GNU version of Awk gcc-4.6.3 GNU Compiler Collection 4.6 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' pkg_info: the package info for package 'gconf2-2.32.0_3' is corrupt gd-2.0.35_8,1 A graphics library for fast creation of images gdbm-1.9.1 The GNU database manager pkg_info: the package info for package 'gdk-pixbuf-2.23.5_3' is corrupt geeqie-1.1 Lightweight image viewer forked from GQview pkg_info: the package info for package 'gegl-0.1.8_4' is corrupt ... ... So your conversion wasn't totally complete, for each of them (aka non corrupted) test if they are in your pkgng database pkg info gcc gawk etc.
Re: Will we get a RELEASE-9.1 for Christmas?
On Friday 21 December 2012 12:52:52 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 12:48:45PM -0600, ajtiM wrote: On Friday 21 December 2012 11:58:00 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? What says pkg_info ? regards, Bapt pkg_info shows many corrupted packages. For example: fontsproto-2.1.1Fonts extension headers foomatic-filters-4.0.7_1 Foomatic wrapper scripts fotoxx-11.03_1 Application to organize and edit image collections freeglut-2.8.0 An alternative to the OpenGL Utility Toolkit (GLUT) library freetype-1.3.1_4A free and portable TrueType font rendering engine freetype-tools-1.3.1_9 Tools for FreeType 1 freetype2-2.4.9_1 A free and portable TrueType font rendering engine frei0r-1.3_1Minimalistic plugin API for video effects fribidi-0.19.2_1A Free Implementation of the Unicode Bidirectional Algorith pkg_info: the package info for package 'gamin-0.1.10_4' is corrupt gawk-4.0.1 The GNU version of Awk gcc-4.6.3 GNU Compiler Collection 4.6 gccmakedep-1.0.2Create dependencies in makefiles using 'gcc -M' pkg_info: the package info for package 'gconf2-2.32.0_3' is corrupt gd-2.0.35_8,1 A graphics library for fast creation of images gdbm-1.9.1 The GNU database manager pkg_info: the package info for package 'gdk-pixbuf-2.23.5_3' is corrupt geeqie-1.1 Lightweight image viewer forked from GQview pkg_info: the package info for package
Re: Will we get a RELEASE-9.1 for Christmas?
On Friday 21 December 2012 12:44:14 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 11:53:16AM -0600, ajtiM wrote: On Friday 21 December 2012 11:26:19 Baptiste Daroussin wrote: On Fri, Dec 21, 2012 at 09:55:00AM -0600, ajtiM wrote: On Friday 21 December 2012 08:12:49 Walter Hurry wrote: On Thu, 20 Dec 2012 23:40:19 +, Matthew Seaman wrote: I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Before I had a chance to try the git version, pkg-1.0.4 turned up in the ports. Good work! Hmm... $ pkg info pkg pkg-1.0.4 New generation package manager $ pkg -v 1.0.3 $ Forgotten (by bapt I assume) again? A definite improvement in 'pkg ckeck -Ba' though; many fewer reported exceptions than before (openjdk7 and firefox are OK now): $ sudo pkg check -Ba pkg: (libreoffice-3.5.7_1) /usr/local/lib/libreoffice/program/ configmgr.uno.so - shared library libxmlreader.so not found pkg: (virtualbox-ose-4.1.22) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found other virtualbox-ose exceptions snipped for brevity $ locate libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so $ locate VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so $ file /usr/local/lib/libreoffice/ure/lib/libxmlreader.so /usr/local/lib/libreoffice/ure/lib/libxmlreader.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxRT.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org I try to update but I am not sure how. I am usin FreeBSD 9.1 RC3 and I have in my make.conf WITH_PKGNG=yes and it works (I did pkg2ng long time ago). I use portmaster. If I put as I got after error of update: WITHOUT_PKGNG=yes - switch to pkgng: 1) Add WITHOUT_PKGNG to /etc/make.conf 2) Install ports-mgmt/pkg 3) Convert your package database by running pkg2ng 4) Remove WITHOUT_PKGNG from /etc/make.conf *** [pre-everything] Error code 1 Stop in /usr/ports/ports-mgmt/pkg. That is the seat belt that means that you have WITH_PKGNG but you also have an incomplete conversion to pkgng It tests if there are any old package installed, and should leave you alone if you have completly and cleanly switch to pkgng. That should have been added long ago. regards, Bapt And how can I find it if was not okay? When I ran pkg2ng was everythin okay (looks like, no errors). I will run pkg2ng again. Do I need to keep WITH_PKGNG=yes in make.conf as was instructed, please? Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org Ok this is a problem with the seat belt and portmaster not with your setup. I disabled the seat belt for now until we find a better way. regards, Bapt Thank you very much. Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 13/12/2012 08:29, Matthew Seaman wrote: (On 'pkg check -Ba' producing 'shared library not found' errors for some packages) Unfortunately it seems to be a fairly common effect in some large projects. Other packages showing the same symptoms: thunderbird (yeah -- that one was predictable...) openjdk6 virtualbox-ose ... and that's just out of what's installed on my desktop: by no means comprehensive. As far as I can tell from a quick check, openjdk6 doesn't rely on setting LD_LIBRARY_PATH in the environment. I've raised issue #403 in pkgng Github. I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Cheers, Matthew PS. If you're running pkg-1.0.3, I recommend you pull down the release-1.0 branch for these tests. While you could upgrade to 1.1.a1 from master, that involves various local.sqlite DB schema changes which will be tedious to unwind should you want to revert to the released version. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Will we get a RELEASE-9.1 for Christmas?
On 12/21/12 00:40, Matthew Seaman wrote: On 13/12/2012 08:29, Matthew Seaman wrote: (On 'pkg check -Ba' producing 'shared library not found' errors for some packages) Unfortunately it seems to be a fairly common effect in some large projects. Other packages showing the same symptoms: thunderbird (yeah -- that one was predictable...) openjdk6 virtualbox-ose ... and that's just out of what's installed on my desktop: by no means comprehensive. As far as I can tell from a quick check, openjdk6 doesn't rely on setting LD_LIBRARY_PATH in the environment. I've raised issue #403 in pkgng Github. I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Cheers, Matthew PS. If you're running pkg-1.0.3, I recommend you pull down the release-1.0 branch for these tests. While you could upgrade to 1.1.a1 from master, that involves various local.sqlite DB schema changes which will be tedious to unwind should you want to revert to the released version. I would like to. But just getting used to svn and other new things since simple csup and friends. How do I pull it? I have pkg-1.0.3_1 on a machine building packages for my laptop right now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 20/12/2012 23:55, Bas Smeelen wrote: On 12/21/12 00:40, Matthew Seaman wrote: On 13/12/2012 08:29, Matthew Seaman wrote: (On 'pkg check -Ba' producing 'shared library not found' errors for some packages) Unfortunately it seems to be a fairly common effect in some large projects. Other packages showing the same symptoms: thunderbird (yeah -- that one was predictable...) openjdk6 virtualbox-ose ... and that's just out of what's installed on my desktop: by no means comprehensive. As far as I can tell from a quick check, openjdk6 doesn't rely on setting LD_LIBRARY_PATH in the environment. I've raised issue #403 in pkgng Github. I've just finished committing fixes for this problem to the master and release-1.0 branches in Github. If anyone is feeling enthusiastic and would like to try pulling those sources and confirming that their favourite packages no longer generate scads of nasty errors when re-analysing shlib dependencies, I'd be grateful. Cheers, Matthew PS. If you're running pkg-1.0.3, I recommend you pull down the release-1.0 branch for these tests. While you could upgrade to 1.1.a1 from master, that involves various local.sqlite DB schema changes which will be tedious to unwind should you want to revert to the released version. I would like to. But just getting used to svn and other new things since simple csup and friends. How do I pull it? I have pkg-1.0.3_1 on a machine building packages for my laptop right now. Install git, and then something like: git clone https://github.com/pkgng/pkgng.git cd pkgng git checkout release-1.0 make then you can run pkg-static from the pkg-static directory, or you can 'make install', and run pkg as usual. There will be a pkg-1.0.4 release fairly soon though. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Will we get a RELEASE-9.1 for Christmas?
On 13/12/2012 07:37, Scot Hetzel wrote: This same issue with firefox was reported in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=131237 And included a simple fix which was rejected by the firefox maintainer due to firefox sets LD_LIBRARY_PATH at runtime to find its share libraries. Unfortunately it seems to be a fairly common effect in some large projects. Other packages showing the same symptoms: thunderbird (yeah -- that one was predictable...) openjdk6 virtualbox-ose ... and that's just out of what's installed on my desktop: by no means comprehensive. As far as I can tell from a quick check, openjdk6 doesn't rely on setting LD_LIBRARY_PATH in the environment. I've raised issue #403 in pkgng Github. Cheers, Matthew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Is the SVN revision gonna disappear from the uname -a output ? I hope. cheers, 2012/12/12 Mark Linimon lini...@lonesome.com On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: the ISO are on the master server The release is official when, and only when, a signed email from the release engineering team says that it is. In a past release cycle there was indeed a last-minute fix that had to be made after the ISO had already started propogating. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- Demelier David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Is the SVN revision gonna disappear from the uname -a output ? I hope. This comment surprises me - having the svn revision there is one of the best thigns about moving to svn from csup for me. I can look at a running machine, and know how to chekcout precisely the code is was built from. Very useful. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
You're right, but one who install a 9.1-RELEASE from iso will obviously still have the same SVN revision, of course it is still great when following -STABLE. 2012/12/12 Pete French petefre...@ingresso.co.uk Is the SVN revision gonna disappear from the uname -a output ? I hope. This comment surprises me - having the svn revision there is one of the best thigns about moving to svn from csup for me. I can look at a running machine, and know how to chekcout precisely the code is was built from. Very useful. -pete. -- Demelier David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Problem is not release, problem are ports: second day and I am still running update for cyrus-sasl and pcre new because there are so many errors. Today I check /usr/ports/UPDATE and I saw another week for update: ImageMagick -r... And than after March we will gt GIMP 2.8, KDE whatever version...and New year will be here... And the same story repeat again... On Sun, Dec 9, 2012 at 5:26 AM, ajtiM lum...@gmail.com wrote: On Saturday 08 December 2012 22:26:30 Chris Petrik wrote: It will be released when it is ready. Perfect answer... And one hour after release thounsands of new ports for building on Christmas time ): Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Wed, Dec 12, 2012 at 3:21 AM, Franci Nabalanci lum...@gmail.com wrote: Problem is not release, problem are ports: second day and I am still running update for cyrus-sasl and pcre new because there are so many errors. Today I check /usr/ports/UPDATE and I saw another week for update: ImageMagick -r... And than after March we will gt GIMP 2.8, KDE whatever version...and New year will be here... And the same story repeat again... Please, don't work so hard! ImageMagick required a re-installation of exactly ONE port on my laptop, editors/emacs (which has now been fixed so it actually will re-build). pcre was worse, but still I got everything for all of the commits yesterday rebuilt in a few hours yesterday afternoon. The only REAL issue was avahi-app which has a badly ordered set of lib directories. (Yes, I should submit a PR to get this fixed.) Install sysutils/bsdadminscripts and run: pkg_libchk -o | grep LIB_THAT_GOT_BUMPED | cut -f1 -d: | sort | uniq SOMEFILE portmaster -D `cat SOMEFILE` pkg_libchk will take a while. On my 2 year old Core i5 laptop it takes around 6 minutes for my 1100 installed ports, but it does let you know just how it is prograssing. This will build a vastly smaller number of ports. You will probably need to remove graphics/py-clutter from SOMEFILE if you have it installed as it is BROKEN for the moment. There may be a couple of others, as well. If you use pkgng, please try editing /usr/local/sbin/pkg_libchk to replace pkg_info with pkg info in all locations and let me know how it works, . I'm hoping that will make it work with pkgng, but I have no way to check as I can't currently use pkgng on any of my systems, yet. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Hi, Reference: From: Ronald Klop ronald-freeb...@klop.yi.org Date: Tue, 11 Dec 2012 17:38:13 +0100 Message-id: op.wo5u5zxq8527sy@ronaldradial.versatec.local Ronald Klop wrote: On Tue, 11 Dec 2012 17:18:44 +0100, Mark Saad nones...@longcount.org wrote: So what is the short summary ? The short summary is that nobody knows. The people who can know anything don't say much more than it's ready when it's ready Cos theyre doubtless working full time on it no time to answer inanne noise. and the rest of the people guess from information from various e-mails and other sources which reliability can be doubted. Only stuff I count is URLs. cynicalAnd the last few days people are saying that you have to donate to the freebsd foundation if you want a release or better information. ;-)/cynical Last paragraph completely False. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 12/12/2012 17:38, Kevin Oberman wrote:
If you use pkgng, please try editing /usr/local/sbin/pkg_libchk to
replace pkg_info with pkg info in all locations and let me know
how it works, . I'm hoping that will make it work with pkgng, but I
have no way to check as I can't currently use pkgng on any of my
systems, yet.
I'd like to draw people's attention to one of the newer capabilities of
pkgng as it's directly relevant to this problem. You can use pkgng to
track which shared libraries are used by binaries in all packages.
Shared library use is determined by analysing the dynamic loading
information recorded in ELF binaries -- either executables or shared
libraries -- so it's pretty reliable.
The feature is turned off by default, but you can enable it by adding:
SHLIBS: YES
to ${LOCALBASE}/etc/pkg.conf and then generate the shlib info by:
pkg check -Ba
This will take a while on a system with lots of packages installed: it
will investigate every file installed by every package. If you aren't
using a repo where the shlibs function is enabled, you'll have to use
pkg check thike this on any new pkgs you subsequently install.
Then, for example, you can find all the pkgs with files that link
against, say, libssh2 by:
worm:~:% pkg query -a %n-%v %B | grep libssh2
curl-7.24.0_1 libssh2.so.1
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: Will we get a RELEASE-9.1 for Christmas?
A.J. 'Fonz' van Werven wrote: Christmas comes early this year: there hasn't been an official announce- ment yet and perhaps not all mirrors have synced yet, but I've seen the ISOs on the NL mirror, so it looks like 9.1-RELEASE is out now. Yup, ftp2.de.freebsd.org also has i386 amd64, (I didnt look for other cpus) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Wed, 12 Dec 2012 18:39:51 +, Matthew Seaman wrote:
On 12/12/2012 17:38, Kevin Oberman wrote:
If you use pkgng, please try editing /usr/local/sbin/pkg_libchk to
replace pkg_info with pkg info in all locations and let me know how
it works, . I'm hoping that will make it work with pkgng, but I have no
way to check as I can't currently use pkgng on any of my systems, yet.
I'd like to draw people's attention to one of the newer capabilities of
pkgng as it's directly relevant to this problem. You can use pkgng to
track which shared libraries are used by binaries in all packages.
Shared library use is determined by analysing the dynamic loading
information recorded in ELF binaries -- either executables or shared
libraries -- so it's pretty reliable.
The feature is turned off by default, but you can enable it by adding:
SHLIBS: YES
to ${LOCALBASE}/etc/pkg.conf and then generate the shlib info by:
pkg check -Ba
This will take a while on a system with lots of packages installed: it
will investigate every file installed by every package. If you aren't
using a repo where the shlibs function is enabled, you'll have to use
pkg check thike this on any new pkgs you subsequently install.
Then, for example, you can find all the pkgs with files that link
against, say, libssh2 by:
worm:~:% pkg query -a %n-%v %B | grep libssh2 curl-7.24.0_1
libssh2.so.1
That looks like a useful feature. But why is it saying this?
pkg: (firefox-17.0.1,1) shared library libxpcom.so not found
pkg: (firefox-17.0.1,1) shared library libmozalloc.so not found
(lots more output snipped)
$ locate libxpcom.so
/usr/local/lib/firefox/libxpcom.so
$ locate libmozalloc.so
/usr/local/lib/firefox/libmozalloc.so
$ file /usr/local/lib/firefox/libxpcom.so
/usr/local/lib/firefox/libxpcom.so: ELF 64-bit LSB shared object, x86-64,
version 1 (FreeBSD), dynamically linked, stripped
$ file /usr/local/lib/firefox/libmozalloc.so
/usr/local/lib/firefox/libmozalloc.so: ELF 64-bit LSB shared object,
x86-64, version 1 (FreeBSD), dynamically linked, stripped
$
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
A few hours ago I ran freebsd-update on a 9.1 RC3 VM system on an esxi server and got 9.1-RELEASE. I know there hasnt been an announcement but it would appear it is very close. Brian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 12/12/2012 23:17, Walter Hurry wrote: That looks like a useful feature. But why is it saying this? pkg: (firefox-17.0.1,1) shared library libxpcom.so not found pkg: (firefox-17.0.1,1) shared library libmozalloc.so not found (lots more output snipped) $ locate libxpcom.so /usr/local/lib/firefox/libxpcom.so $ locate libmozalloc.so /usr/local/lib/firefox/libmozalloc.so $ file /usr/local/lib/firefox/libxpcom.so /usr/local/lib/firefox/libxpcom.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/firefox/libmozalloc.so /usr/local/lib/firefox/libmozalloc.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ Ah -- that would be a bug. At a guess, it's not finding the shlibs because they're in a location not on the usual path and there's something odd about the RPATH settings in the binaries. I shall investigate further. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Will we get a RELEASE-9.1 for Christmas?
On Thu, Dec 13, 2012 at 12:29 AM, Matthew Seaman matt...@freebsd.org wrote: On 12/12/2012 23:17, Walter Hurry wrote: That looks like a useful feature. But why is it saying this? pkg: (firefox-17.0.1,1) shared library libxpcom.so not found pkg: (firefox-17.0.1,1) shared library libmozalloc.so not found (lots more output snipped) $ locate libxpcom.so /usr/local/lib/firefox/libxpcom.so $ locate libmozalloc.so /usr/local/lib/firefox/libmozalloc.so $ file /usr/local/lib/firefox/libxpcom.so /usr/local/lib/firefox/libxpcom.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ file /usr/local/lib/firefox/libmozalloc.so /usr/local/lib/firefox/libmozalloc.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ Ah -- that would be a bug. At a guess, it's not finding the shlibs because they're in a location not on the usual path and there's something odd about the RPATH settings in the binaries. I shall investigate further. This same issue with firefox was reported in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=131237 And included a simple fix which was rejected by the firefox maintainer due to firefox sets LD_LIBRARY_PATH at runtime to find its share libraries. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, 11 Dec 2012 05:06:24 +0100, Kevin Oberman kob6...@gmail.com wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. Then they can communicate they don't know a date. People accept hearing: 'because of unforeseen problems the expected date is unknown' in stead of '2012-10-29' (http://wiki.freebsd.org/Releng/9.1TODO). Not knowing something is not an excuse for not communicating. Ronald. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Kevin Oberman wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glassbr...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: [...] This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. ISOs are on FTP site today (with date of 2012-12-04, but yesterday there were none) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Mon, Dec 10, 2012 at 08:06:24PM -0800, Kevin Oberman wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. I don't remember seeing any updates in e-mail, but the http://www.freebsd.org/news/2012-compromise.html url has been updated. Its a litle out of date now (last update about 2 weeks ago), but it does include information on the release of 9.1 and what is holding it up (specifically getting a minimal set of packages built). With the 2 branches tagged (ports and src) it is likely still a matter of getting stuff built in a known clean environment. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
So what is the short summary ? From what I can see, the wiki is out of date again. the ISO are on the master server, and working out to the mirrors. FreeBSD update is still not updated. Does someone just need to just update the wiki with the relevant info ? On Tue, Dec 11, 2012 at 9:00 AM, Gary Palmer gpal...@freebsd.org wrote: On Mon, Dec 10, 2012 at 08:06:24PM -0800, Kevin Oberman wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. I don't remember seeing any updates in e-mail, but the http://www.freebsd.org/news/2012-compromise.html url has been updated. Its a litle out of date now (last update about 2 weeks ago), but it does include information on the release of 9.1 and what is holding it up (specifically getting a minimal set of packages built). With the 2 branches tagged (ports and src) it is likely still a matter of getting stuff built in a known clean environment. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- mark saad | nones...@longcount.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Am Tue, 11 Dec 2012 11:18:44 -0500 schrieb Mark Saad nones...@longcount.org: So what is the short summary ? From what I can see, the wiki is out of date again. the ISO are on the master server, and working out to the mirrors. FreeBSD update is still not updated. Does someone just need to just update the wiki with the relevant info ? From my experience, it usually takes a couple of days from uploading the ISOs to the official announcement. I don't think it makes sense anymore to update the wiki now. For the future, I also suggest not to make a timeline or a public schedule at all. It will stop people from making assumptions and plans for their rollouts that more often than not just turn out to be unrealistic. I myself actually anticipated a October/November-ish release-date when I saw the first schedule...and even that turned out to be too optimistic. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, 11 Dec 2012 17:18:44 +0100, Mark Saad nones...@longcount.org wrote: So what is the short summary ? The short summary is that nobody knows. The people who can know anything don't say much more than it's ready when it's ready and the rest of the people guess from information from various e-mails and other sources which reliability can be doubted. cynicalAnd the last few days people are saying that you have to donate to the freebsd foundation if you want a release or better information. ;-)/cynical Ronald. From what I can see, the wiki is out of date again. the ISO are on the master server, and working out to the mirrors. FreeBSD update is still not updated. Does someone just need to just update the wiki with the relevant info ? On Tue, Dec 11, 2012 at 9:00 AM, Gary Palmer gpal...@freebsd.org wrote: On Mon, Dec 10, 2012 at 08:06:24PM -0800, Kevin Oberman wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. I don't remember seeing any updates in e-mail, but the http://www.freebsd.org/news/2012-compromise.html url has been updated. Its a litle out of date now (last update about 2 weeks ago), but it does include information on the release of 9.1 and what is holding it up (specifically getting a minimal set of packages built). With the 2 branches tagged (ports and src) it is likely still a matter of getting stuff built in a known clean environment. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, 11 Dec 2012 17:32:34 +0100, Rainer Duffner rai...@ultra-secure.de wrote: Am Tue, 11 Dec 2012 11:18:44 -0500 schrieb Mark Saad nones...@longcount.org: So what is the short summary ? From what I can see, the wiki is out of date again. the ISO are on the master server, and working out to the mirrors. FreeBSD update is still not updated. Does someone just need to just update the wiki with the relevant info ? From my experience, it usually takes a couple of days from uploading the ISOs to the official announcement. I don't think it makes sense anymore to update the wiki now. For the future, I also suggest not to make a timeline or a public schedule at all. It will stop people from making assumptions and plans for their rollouts that more often than not just turn out to be unrealistic. I myself actually anticipated a October/November-ish release-date when I saw the first schedule...and even that turned out to be too optimistic. I suggest to make a timeline AND communicate what is happening _now_. Some small official statement from the release team now and then would make a large difference. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Hello, For the future, I also suggest not to make a timeline or a public schedule at all. That seems to be a very bad idea, it will invite the usual freebsd-is-dead crowd. It will stop people from making assumptions and plans for their rollouts that more often than not just turn out to be unrealistic. I myself actually anticipated a October/November-ish release-date when I saw the first schedule...and even that turned out to be too optimistic. The last few years it was always shortly after x-mas 8-} -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Kurt Jaeger wrote: The last few years it was always shortly after x-mas 8-} Christmas comes early this year: there hasn't been an official announce- ment yet and perhaps not all mirrors have synced yet, but I've seen the ISOs on the NL mirror, so it looks like 9.1-RELEASE is out now. AvW -- Obsig: developing a new sig pgpFarmHjImPD.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
Hi! The last few years it was always shortly after x-mas 8-} Christmas comes early this year: there hasn't been an official announce- ment yet So, as every year: be patient, wait for the official release announcement, it still might change due to some last-minute bug. -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Short summary: http://lists.freebsd.org/pipermail/freebsd-stable/2012-December/071023.html On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: So what is the short summary ? From what I can see, the wiki is out of date again. the ISO are on the master server, and working out to the mirrors. FreeBSD update is still not updated. Does someone just need to just update the wiki with the relevant info ? On Tue, Dec 11, 2012 at 9:00 AM, Gary Palmer gpal...@freebsd.org wrote: On Mon, Dec 10, 2012 at 08:06:24PM -0800, Kevin Oberman wrote: On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. I don't remember seeing any updates in e-mail, but the http://www.freebsd.org/news/2012-compromise.html url has been updated. Its a litle out of date now (last update about 2 weeks ago), but it does include information on the release of 9.1 and what is holding it up (specifically getting a minimal set of packages built). With the 2 branches tagged (ports and src) it is likely still a matter of getting stuff built in a known clean environment. Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- mark saad | nones...@longcount.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Kurt Jaeger wrote: Christmas comes early this year: there hasn't been an official announcement yet So, as every year: be patient, wait for the official release announcement, it still might change due to some last-minute bug. True. But it still looks like an early Christmas ;-) I doubt it will be two weeks before the announcement comes. AvW -- Obsig: developing a new sig pgpZprXgZhtVi.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
On 11 December 2012 08:44, Ronald Klop ronald-freeb...@klop.yi.org wrote: I suggest to make a timeline AND communicate what is happening _now_. Some small official statement from the release team now and then would make a large difference. The release team (and developer team in general) know that communication about 9.1-RELEASE hasn't been all that great. They've been doing the focus on getting work done thing and yes, unfortunately communication has suffered. Let's all be supportive of them and the enormous amount of hard work they put into trying to get a free release out there for people to use; being critical like this is very likely going to have exactly the opposite effect for people under pressure. :) Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
At 09:32 AM 12/11/2012, Rainer Duffner wrote: For the future, I also suggest not to make a timeline or a public schedule at all. Less communication rather than more? I would not be in favor of this. YMMV, but it seems to me that this is more the way of large, secretive corporations like Apple than it is of a collaborative open source project. And it is important to have targets. Transparency is vital. I do not mind justified schedule slippages, so long as I can track progress and plan appropriately. It is when I (and everyone else) are in the dark that things get difficult. --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, Dec 11, 2012 at 06:55:59PM +0100, Kurt Jaeger wrote: Hi! The last few years it was always shortly after x-mas 8-} Christmas comes early this year: there hasn't been an official announce- ment yet So, as every year: be patient, wait for the official release announcement, it still might change due to some last-minute bug. It usually gets officially released some days _after_ heise.de announces that it is released. :-s Nothing to see on heise, yet, so please be patient. ;-) pgpr8sTUso7fe.pgp Description: PGP signature
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: the ISO are on the master server The release is official when, and only when, a signed email from the release engineering team says that it is. In a past release cycle there was indeed a last-minute fix that had to be made after the ISO had already started propogating. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Mon, Dec 10, 2012 at 12:14:13AM +0100, Julian H. Stacey wrote: Clue to a quick check with CVS is/was grep RELENG_9_1_0_RELEASE /usr/cvs/src/Makefile,v grep RELEASE_9_1_0 /usr/cvs/ports/Makefile,v but as CVS is about to disappear, what's a quick check for svn ? Some time before the turn of the millennium I wrote this little script that updates a local list of FreeBSD/sendmail/bind versions every night. I recently adapted it for svn. It's just a hack but works for me, use it as you please: http://www.psconsult.nl/pub/FB/fb_releases It expects the svn repository to be file:///FreeBSD/svn/base and writes a file called /FreeBSD/rel. Kind regards, Paul Schenkeveld ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
At 03:41 PM 12/9/2012, Adrian Chadd wrote: I'll amend my stuff that will help list: * Donate to the freebsd foundation, along with opening discussions to them about how your organisation uses / relies upon freebsd; * Volunteer to join the release engineering / package building teams, and actively donate manpower to the project. I've thought about donating manpower; tried to many years ago, in fact. But I was deterred by the egos, the politics, and the territoriality and hotheadedness of some of the developers. So, most of my contributions of code (and I have made quite a few) have been passed quietly through committers so as to avoid this. Maybe the situation is better now; I don't know. As for monetary donations: We are not a large corporation, and so could only make relatively small ones as opposed to more valuable in kind donations. --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 10 December 2012 09:34, Brett Glass br...@lariat.net wrote: I've thought about donating manpower; tried to many years ago, in fact. But I was deterred by the egos, the politics, and the territoriality and hotheadedness of some of the developers. So, most of my contributions of code (and I have made quite a few) have been passed quietly through committers so as to avoid this. Maybe the situation is better now; I don't know. There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. But somehow I have a commit bit and get away with breaking things. :-) As for monetary donations: We are not a large corporation, and so could only make relatively small ones as opposed to more valuable in kind donations. Even a $5k a year donation from 25 organisations is a significant chunk of money to the foundation. Please don't believe that you can't have a positive effect from a small donation. the foundation will definitely benefit from any and all contributions, no matter how small. I'd rather see the Foundation funded from thousands of small donations a year than a handful of big ones. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Mon, Dec 10, 2012 at 3:52 PM, Brett Glass br...@lariat.net wrote: At 04:29 PM 12/10/2012, Adrian Chadd wrote: There's politics in every organisation. There are ego clashes in every organisation. Sometimes you'll fit in, sometimes you won't. If you feel there are issues, find people inside the community who you do get along well with and talk with them about it. It sucks, yes. I'm one of those shut up and code already types and I deal badly with politics. Me, too. That's why I have been contributing code quietly through others rather than putting myself out in the front lines. In any event -- back to the original topic -- there should indeed be better communications between the Release Engineering team and the community. The time it takes to post updates -- especially as it gets close to release time -- would be recovered many times over because folks like me wouldn't have any need to e-mail regarding status and projected schedules. ;-) I whole-heatedly agree... but I know a little about release engineering for a large project, especially when the release team is unpaid and has to honor commitments to $real_job. Release engineering is very detail-oriented and unforgiving. This is not really compatible with part-time work. The RE must be focused, first ans foremost, on getting a release out the door as quickly as possible and not to have any serious problems with that release. This makes it very had to pull bakc and make announcements or even update posted schedules. That is made even worse by hte desire to make such communication accurate or at least useful. Since there is a LOT of guessing involved in pulling together a release (how long will Joe take to fix this problem or why are there half a dozen reports of a serious issue with the RC, when no one else can reproduce it or even figure out what part of the system is causing it), RE folks are usually reticent about trying to give out any information since it will most likely be inaccurate. This is why I accept the line that it will be released when it is ready. I really think it's about ready, but not even the head of the 9.1 RE team KNOWS when it will be ready, even if the ISO builds are started. There is many a slip twixt the cup and the lip. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 12/10/2012 06:34 PM, Brett Glass wrote: At 03:41 PM 12/9/2012, Adrian Chadd wrote: I'll amend my stuff that will help list: * Donate to the freebsd foundation, along with opening discussions to them about how your organisation uses / relies upon freebsd; I just had a little conversation with my employer about donating to the FreeBSD Foundation and sent the three *most important* people in the organization a follow up mail on it with the link of course. Let's see what happens. Maybe they will take it out of our Christmas gift :) Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Saturday 08 December 2012 22:26:30 Chris Petrik wrote: It will be released when it is ready. Perfect answer... And one hour after release thounsands of new ports for building on Christmas time ): Mitja http://www.redbubble.com/people/lumiwa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
This is good answer for end users, not so much when somebody is genuinely concerned if there were some unforeseen issues. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Will-we-get-a-RELEASE-9-1-for-Christmas-tp5767716p5767785.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
...so needless to say, I prefer one provided by developer (in this case Adrian's), even if it is laconic. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Will-we-get-a-RELEASE-9-1-for-Christmas-tp5767716p5767789.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 9 December 2012 08:48, Jakub Lach jakub_l...@mailplus.pl wrote: This is good answer for end users, not so much when somebody is genuinely concerned if there were some unforeseen issues. Agreed. Companies need predictability. FWIW: The ports tree is open now (ports branch was tagged). The 9.1.0 src branch was tagged already. I'd expect to be released *very* shortly (before Christmas), although I don't know an exact date. -- Eitan Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 2012-12-09 04:18, Brett Glass wrote: Just checking in, yet again, to ask about the status of FreeBSD 9.1. We've been delaying construction of new servers (which we wanted to build during the US Thanksgiving holiday) until the release, and really want to be able to work on them over Christmas. I understand that the release was held back by server security issues and possibly by problems with CLANG's failure to emulate obscure quirks of GCC; It has nothing to do with clang; it is not the default compiler for 9.1, and will never be for the 9.x series. Using it to compile your system (or ports) is entirely optional. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Brett Glass brett at lariat.net writes: Just checking in, yet again, to ask about the status of FreeBSD 9.1. We've been delaying construction of new servers (which we wanted to build during the US Thanksgiving holiday) until the release, and really want to be able to work on them over Christmas. I understand that the release was held back by server security issues and possibly by problems with CLANG's failure to emulate obscure quirks of GCC; are these now resolved? Is there anything else on the TODO list (the version on the Wiki is of no help; it's woefully out of date) to be done prior to release? Does the FreeBSD project need a fresh server to be donated to handle the release? --Brett Glass A few days ago I installed 9.0 and tested twice: - updating security/errata - updating ports tree with portsnap - setting up the system for Linux, Java, browsers (as in Handbook) - and then from ports to make work the usual suspects: cdrecord, smartmontools It all seems to be OK until, after many subsequent ports tree updates, I decided to update xterm, vlc, xfce, pan from ports. If I managed to update some of them, then it seemed the dependencies hell or something else started to take effect and I could not finish building them because they were dying with errors. I have done such an exercise in the past many times and I never failed to bring my system to a stable state. Only after this security compromise, time wise, things were so unstable. I understand that releng people will build all packages once more right before 9.1 release, but perhaps caution is warranted - would 9.1-RC4 make sense ? jb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On 12/09/2012 10:37 AM, jb wrote: I understand that releng people will build all packages once more right before 9.1 release, but perhaps caution is warranted - would 9.1-RC4 make sense ? I recently upgraded in place from 8.3-STABLE to 9.1-PRE. I needed to redo the system because of the sec compromise just to be sure, so this seemed to be a good time to do it. So, using the now-preferred portsnap and svn download mechanisms, I rebuilt the OS AND every single port. Thus far, I've not had a significant problem ... well, other than the fact that when sasl rebuilds it does not restart the daemon and I couldn't figure out why mail wasn't going out ... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Sun, Dec 9, 2012 at 5:37 PM, jb jb.1234a...@gmail.com wrote: A few days ago I installed 9.0 and tested twice: (..) Only after this security compromise, time wise, things were so unstable. I understand that releng people will build all packages once more right before 9.1 release, but perhaps caution is warranted - would 9.1-RC4 make sense ? Was also true for me to crash the 9.0 system with dependencies inconsistency after some time. But! Try 9.1-RC3 and use PORTINSTALL (ports-mgmt/portupgrade port) - see how beautiful life become when you only type what program you wand and it gets installed from BINARY PACKAGES with all necessary dependencies :-) So far I have no problem at all with portinstall on two machines running 9.1-RC3 for some weeks. PORTINSTALL should become a standard equipment of FreeBSD :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
CeDeROM cederom at tlen.pl writes: ... Was also true for me to crash the 9.0 system with dependencies inconsistency after some time. But! Try 9.1-RC3 and use PORTINSTALL ... The reason I abandoned 9.1-RC? was the security update statement that It is believed that the compromise may have occurred as early as the 19th September 2012. I looked at 9.1 release schedule and saw this: Action Expected Actual RC1 2012-07-20 2012-08-23 RC2 2012-09-07 2012-10-09 ... and decided to drop the ball, go back to 9.0 and bring myself up from there. The result was as described. jb ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
My prediction is 9.1 will be released the last day of Hanukkah and I will tell you why: When I was a kid sometimes I would ask my patients to give me one big gift for Hanukkah instead of a small present each day. This would mean I would have to wait until the final day though. My assumption is that my Jewish mother has told re@ core@ of this preference and they are just setting up to surprise the members of the tribe with one big gift. So everyone please hold onto your dreidels! Sent from my iPhone On Dec 9, 2012, at 6:04 AM, Eitan Adler li...@eitanadler.com wrote: On 9 December 2012 08:48, Jakub Lach jakub_l...@mailplus.pl wrote: This is good answer for end users, not so much when somebody is genuinely concerned if there were some unforeseen issues. Agreed. Companies need predictability. FWIW: The ports tree is open now (ports branch was tagged). The 9.1.0 src branch was tagged already. I'd expect to be released *very* shortly (before Christmas), although I don't know an exact date. -- Eitan Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
At 07:42 AM 12/9/2012, Dimitry Andric wrote: It has nothing to do with clang; it is not the default compiler for 9.1, and will never be for the 9.x series. Using it to compile your system (or ports) is entirely optional. I am actually eagerly awaiting a completely un-GNUed toolchain. But I am glad that this is not the holdup. I just need to plan my time so that I get a vacation SOMETIME this season and also keep my commitments. Alas, there have been no updates to the projected schedule or to the To Do list to help me out. --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
.. if people would like to see more resources thrown at getting things like timely releases done, please consider donating to the FreeBSD foundation and write to them about what you'd like to see. I think people are really quite used to getting something for nothing. This isn't an attack at you Brett; this is more of a general observation. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Sun, 09 Dec 2012 12:59:31 -0800, Adrian Chadd wrote: .. if people would like to see more resources thrown at getting things like timely releases done, please consider donating to the FreeBSD foundation and write to them about what you'd like to see. I think people are really quite used to getting something for nothing. This isn't an attack at you Brett; this is more of a general observation. Well said, Sir. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
At 01:59 PM 12/9/2012, Adrian Chadd wrote: .. if people would like to see more resources thrown at getting things like timely releases done, please consider donating to the FreeBSD foundation and write to them about what you'd like to see. I think people are really quite used to getting something for nothing. This isn't an attack at you Brett; this is more of a general observation. I hope it's not. In my previous message, I offered to donate a server. Along with some bandwidth, if that's useful. --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Hi, It's definitely not targeted at you. The 9.1 stuff is an intersection of: * personal issues with some of the people involved (ie, real life got to them and that took precedence); * the security incident; * the freebsd cluster shuffling and reshuffling that was going on at the same time From my understanding there's enough hardware. Definitely not a hardware specific problem. The foundation funds and provides plenty of hardware, as well as yahoo and a few other companies. I don't think we're short of i386/amd64 hardware. It's honestly just an intersection of bad timing. Since it's a volunteer project, it's on the timelines of the volunteers in question. I think people are right though when they comment on the lack of communication from the project about this. See the list of things above to understand why communication may not have been terribly great. :-) I'll amend my stuff that will help list: * Donate to the freebsd foundation, along with opening discussions to them about how your organisation uses / relies upon freebsd; * Volunteer to join the release engineering / package building teams, and actively donate manpower to the project. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Sun, Dec 9, 2012 at 2:41 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, It's definitely not targeted at you. The 9.1 stuff is an intersection of: * personal issues with some of the people involved (ie, real life got to them and that took precedence); * the security incident; * the freebsd cluster shuffling and reshuffling that was going on at the same time From my understanding there's enough hardware. Definitely not a hardware specific problem. The foundation funds and provides plenty of hardware, as well as yahoo and a few other companies. I don't think we're short of i386/amd64 hardware. It's honestly just an intersection of bad timing. Since it's a volunteer project, it's on the timelines of the volunteers in question. I think people are right though when they comment on the lack of communication from the project about this. See the list of things above to understand why communication may not have been terribly great. :-) I'll amend my stuff that will help list: * Donate to the freebsd foundation, along with opening discussions to them about how your organisation uses / relies upon freebsd; * Volunteer to join the release engineering / package building teams, and actively donate manpower to the project. Adrian ___ http://www.freebsdfoundation.org/ http://www.freebsdfoundation.org/donate/ http://www.freebsdfoundation.org/announcements.shtml#fundraising Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
Brett Glass wrote:
At 07:42 AM 12/9/2012, Dimitry Andric wrote:
It has nothing to do with clang; it is not the default compiler for 9.1,
and will never be for the 9.x series. Using it to compile your system
(or ports) is entirely optional.
I am actually eagerly awaiting a completely un-GNUed toolchain. But I am
glad that this is not the holdup. I just need to plan my time so that I get
a vacation SOMETIME this season and also keep my commitments. Alas, there
have been no updates to the projected schedule or to the To Do list to
help me out.
--Brett Glass
Hi those eagerly awaiting,
Re-read Eitan's post of Sun, 9 Dec 2012 09:04:25 -0500 (15:04 CET)
Those with knowledge, time enthusiasm can already build
their own 9.1-RELEASE from released public sources. No longer need to wait.
As I wrote 3 local friends Fri, 07 Dec 2012 08:37:20 +0100
] In case you'r waiting to upgrade any production servers to latest release:
] {
] Although FreeBSD-9.1-RELEASE has not been announced yet, it's available:
] in (ctm distributed) CVS tree (I admit I havent converted to use svn yet)
] grep RELENG_9_1_0_RELEASE
/pub/FreeBSD/development/FreeBSD-CVS/src/Makefile,v
] I am exporting with
] cvs -R export -r RELENG_9_1_0_RELEASE src # du=867 M tgz=149 M
] ports doc have not been tagged yet, they will later be:
] cvs -R export -r RELEASE_9_1_0 ports # du=... M tgz=... M
] cvs -R export -r RELEASE_9_1_0 doc
]
] The .iso images are not in ftp.freebsd.org or eg ftp2.de.freebsd.org yet,
]( I havent bothered to look for packages as I dont use them, I always
]compile my own ports)
] I assume the delay to announce release is 'cos they're still recovering
] from their security intrusion still rebuilding packages after
]http://www.freebsd.org/news/2012-compromise.html
]
] freebsd.org also have sigbus issues with cvsup (affecting send-pr),
] may also be slowing build cluster
]
http://lists.freebsd.org/pipermail/freebsd-hackers/2012-December/041352.html
Clue to a quick check with CVS is/was
grep RELENG_9_1_0_RELEASE /usr/cvs/src/Makefile,v
grep RELEASE_9_1_0 /usr/cvs/ports/Makefile,v
but as CVS is about to disappear, what's a quick check for svn ?
Compliments to re@ team who have doubtless been working very hard,
probably on a problematic cluster base. Hopefully there'll be less
When ? questions that might distract re@, now people realise it's
tagged you can build yourself if you're in a rush.
ports/ is also tagged available:
From: Thomas Abthorpe portmgr-secret...@freebsd.org
Date: Sun, 9 Dec 2012 19:59:09 +
To: po...@freebsd.org
(though no tag for that yet in preceeding cvs-cur 19073 )
Those who want this lot must wait till announcement (a few days I guess)
binaries compiled at freebsd.org
+ for all architectures,
+ packages build on freebsd.org cluster
+ docs
+ iso's built
+ all ftp'd from master server to mirror servers globaly
+ Release Notes written by re@ team who are doubtless
tired, working flat out ;-)
+ all of that work to be done on a freebsd cluster that was
compromised needed to be checked before the relase rolled,
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
Reply below not above, like a play script. Indent old text with .
Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Will we get a RELEASE-9.1 for Christmas?
Just checking in, yet again, to ask about the status of FreeBSD 9.1. We've been delaying construction of new servers (which we wanted to build during the US Thanksgiving holiday) until the release, and really want to be able to work on them over Christmas. I understand that the release was held back by server security issues and possibly by problems with CLANG's failure to emulate obscure quirks of GCC; are these now resolved? Is there anything else on the TODO list (the version on the Wiki is of no help; it's woefully out of date) to be done prior to release? Does the FreeBSD project need a fresh server to be donated to handle the release? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
It's still progressing, albeit slowly. There's been a lot of security checking going on in the background as part of this task and that takes time. Adrian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It will be released when it is ready. On 12/8/2012 9:18 PM, Brett Glass wrote: Just checking in, yet again, to ask about the status of FreeBSD 9.1. We've been delaying construction of new servers (which we wanted to build during the US Thanksgiving holiday) until the release, and really want to be able to work on them over Christmas. I understand that the release was held back by server security issues and possibly by problems with CLANG's failure to emulate obscure quirks of GCC; are these now resolved? Is there anything else on the TODO list (the version on the Wiki is of no help; it's woefully out of date) to be done prior to release? Does the FreeBSD project need a fresh server to be donated to handle the release? --Brett Glass ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQxBL1AAoJEAGnn5Nn8qWUrPAH/2cgbQ3BYL+E6B1C0Vce0XNY Yxf7IQByzLCsmdXJW62OZoXkOvS1RV/bPFqqiOtd/Vl6v7eaxQgXmXTZuf401eRD FHz2/j9j0BouVnU2nOwcrQxrjB5phjqpAe/87MWrqR2/bQFt3/b7x5EC/oB1hKJ6 5S5A0/Yukh//gpaA5LcMxLZuus3xmRKA7zUugiYi9x8eis+pNu/7n470nnKtZKkZ pRvGxr4F/olUqj0yOw/Pqap9a41Xc4R8L1MjZfbu2fs5ob60qPMva00WEhBgOKQy xfkLFU7hHj+KaZ3AqdoHQbmsiKrMjjK/q1aeibS8nEDMB+RF8T8xoCd33P33960= =aroh -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
