Re: libreoffice fails to build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 think the unzip path is ok. i have reinstall unzip. now will update libreoffice. # whereis unzip unzip: /usr/bin/unzip /usr/share/man/en.ISO8859-15/man1/unzip.1.gz /usr/src/usr.bin/unzip # locate \*/unzip /media/disk/usr/bin/unzip /usr/bin/unzip /usr/jails/basejail/usr/bin/unzip /usr/jails/basejail/usr/ports/archivers/unzip /usr/jails/basejail/usr/ports/chinese/unzip /usr/jails/basejail/usr/ports/korean/unzip /usr/jails/basejail/usr/ports/russian/unzip /usr/local/bin/unzip /usr/local/share/doc/unzip /usr/obj/usr/src/usr.bin/unzip /usr/obj/usr/src/usr.bin/unzip/unzip /usr/ports/archivers/unzip /usr/src/usr.bin/unzip /var/db/ports/unzip # uname -a FreeBSD xxx.xxx.xxx 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #3: Mon Jul 2 17:58:18 CEST 2012 r...@xxx.xxx.xxx:/usr/obj/usr/src/sys/KERNEL amd64 Am 22.07.2012 04:00, schrieb Robert Backhaus: > On 22 July 2012 06:39, Joerg Surmann wrote: >> > #build > mkdir -p ../../unxfbsd.pro/misc/java_src/ > cp > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/solver/unxfbsd.pro/bin/jurt_src.zip > ../../unxfbsd.pro/misc/java_src/jurt_src.zip > cd ../../unxfbsd.pro/misc/java_src && unzip -quo jurt_src.zip > unzip: -n, -o and -u are contradictory > > > Hmm, there is something wrong with your unzip. The stock unzip has no > > problems with those options. > > Could you please run "whereis unzip"? Unzip should be in /usr/bin. > > Check your path, check the output of "locate \*/unzip" (that will list > > directories as well as files called unzip). You seem to have a > > different version of unzip that is causing that problem. > > The output of "uname -a" would help us too. > > > dmake: Error code 1, while making > '../../unxfbsd.pro/misc/java_src/jurt_src.zip' > dmake: '../../unxfbsd.pro/misc/java_src/jurt_src.zip' removed. > > --- > Oh dear - something failed during the build - sorry ! > For more help with debugging build errors, please see the section in: > http://wiki.documentfoundation.org/Development > > internal build errors: > > ERROR: error 65280 occurred while making > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > > > Am 21.07.2012 13:40, schrieb Robert Huff: > >>> > >>> Joerg Surmann writes: > >>> > I have delete all qt3. > > now i have a new error: > > internal build errors: > > ERROR: error 65280 occurred while making > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > > it seems that the error is inside 'odk', please re-run build > inside this module to isolate the error and/or test your fix: > - --- > >>> > >>> Did you do: > >>> > /usr/local/bin/bash > cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3 > source ./Env.Host.sh > cd odk > rm -Rf > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/unxfbsd.pro > # optional module 'clean' > build > >>> > >>> ? > >>> > >>> > >>> Robert Huff > > >> >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQC7gcAAoJEDyDkpKh+9pTulcP/0cjAam5s8LwkDe06vkKE69w gPKDSSYdGk2PoKA9t3XnvDc/fgI4516R71RsqFeQedMvkA9TFgZcUqozRop0J3T2 qh7wkK24BDRIJXwGtyhdUiCEPVqw9zAtNKCB8LWqabIEQ2ZgGowEfxlbNyByup5U hlKYVyclMB+d5whz67hISXfA+/DEaG4l8yb4m4FprFUx5VkvwnyC9i97j3kFYFSn 85UnkgLAj07tI2GVE2g4J5uhHCIvWuwMpuBpccBYy7OV558BZzGA1BhZoE+fAbPP ZG7G21ZVYd8bt4oReePU3pz9+6y1gaKrlX6VUSpxe6Isqc81uGdppU1JZ0WIPfet DrWlW5vTtuyujfObCNdNaXxhsz4DMz4Hy8cyg2WQuHFIfWL0Hisx6JMf8y2TUnxp pp18q/J5GI+863iIAfrX22XjKNGwD7JZlfzKwi258QcelWKVvtMHepvQuduM1MUr +44A9COG8AePK+JYziySlSsFrFwaiVYGDa9GAmA5YwOjpkxd6WFR2lgDjL8Al8HR YMaANQADVY+P6wQgBgl/t3rd2hrdzMGAlF3vQ1IXLks+8epS5lR56IkhTFBtWZX3 bo5qUKVX/b7PWXtKKmTqm2bmcLVVE4GtLkAbSoXoVM3/LCA7kOmBpgdJh4leOsZG w6lIl8Zw8YGal1X7vGHK =Gk4V -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libreoffice fails to build
On 22 July 2012 18:21, Joerg Surmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > think the unzip path is ok. > i have reinstall unzip. > now will update libreoffice. > > # whereis unzip > unzip: /usr/bin/unzip /usr/share/man/en.ISO8859-15/man1/unzip.1.gz > /usr/src/usr.bin/unzip > > # locate \*/unzip > /media/disk/usr/bin/unzip > /usr/bin/unzip > /usr/jails/basejail/usr/bin/unzip > /usr/jails/basejail/usr/ports/archivers/unzip > /usr/jails/basejail/usr/ports/chinese/unzip > /usr/jails/basejail/usr/ports/korean/unzip > /usr/jails/basejail/usr/ports/russian/unzip > /usr/local/bin/unzip > /usr/local/share/doc/unzip > /usr/obj/usr/src/usr.bin/unzip > /usr/obj/usr/src/usr.bin/unzip/unzip > /usr/ports/archivers/unzip > /usr/src/usr.bin/unzip > /var/db/ports/unzip > > # uname -a > FreeBSD xxx.xxx.xxx 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #3: Mon Jul 2 > 17:58:18 CEST 2012 r...@xxx.xxx.xxx:/usr/obj/usr/src/sys/KERNEL amd64 > > > Ah, sorry, I mislead you there. I've got linux on this notebook, and the window I tested unzip in happened to be local, not ssh! The /usr/bin one fails. the /usr/local/bin one succeded. Try unzipping a file, using /usr/bin/unzip -uo, and again using /usr/local/bin/unzip -uo . The first should fail, the second should succeed. I do not know why it is using the wrong unzip, I do not know > Am 22.07.2012 04:00, schrieb Robert Backhaus: > > On 22 July 2012 06:39, Joerg Surmann > > wrote: > >> > > #build > > mkdir -p ../../unxfbsd.pro/misc/java_src/ > > cp > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/solver/ > unxfbsd.pro/bin/jurt_src.zip > > ../../unxfbsd.pro/misc/java_src/jurt_src.zip > > cd ../../unxfbsd.pro/misc/java_src && unzip -quo jurt_src.zip > > unzip: -n, -o and -u are contradictory > > > > > Hmm, there is something wrong with your unzip. The stock unzip has no > > > problems with those options. > > > Could you please run "whereis unzip"? Unzip should be in /usr/bin. > > > Check your path, check the output of "locate \*/unzip" (that will list > > > directories as well as files called unzip). You seem to have a > > > different version of unzip that is causing that problem. > > > The output of "uname -a" would help us too. > > > > > > dmake: Error code 1, while making > > '../../unxfbsd.pro/misc/java_src/jurt_src.zip' > > dmake: '../../unxfbsd.pro/misc/java_src/jurt_src.zip' removed. > > > > --- > > Oh dear - something failed during the build - sorry ! > > For more help with debugging build errors, please see the section in: > > http://wiki.documentfoundation.org/Development > > > > internal build errors: > > > > ERROR: error 65280 occurred while making > > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > > > > > > Am 21.07.2012 13:40, schrieb Robert Huff: > > >>> > > >>> Joerg Surmann writes: > > >>> > > I have delete all qt3. > > > > now i have a new error: > > > > internal build errors: > > > > ERROR: error 65280 occurred while making > > > > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > > > > it seems that the error is inside 'odk', please re-run build > > inside this module to isolate the error and/or test your fix: > > - > --- > > >>> > > >>> Did you do: > > >>> > > /usr/local/bin/bash > > cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3 > > source ./Env.Host.sh > > cd odk > > rm -Rf > > > > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/ > unxfbsd.pro > > # optional module 'clean' > > build > > >>> > > >>> ? > > >>> > > >>> > > >>> Robert Huff > > > > > >> > >> ___ > >> freebsd-ports@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports > >> To unsubscribe, send any mail to > "freebsd-ports-unsubscr...@freebsd.org" > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to > > "freebsd-ports-unsubscr...@freebsd.org" > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.19 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQIcBAEBCAAGBQJQC7gcAAoJEDyDkpKh+9pTulcP/0cjAam5s8LwkDe06vkKE69w > gPKDSSYdGk2PoKA9t3XnvDc/fgI4516R71RsqFeQedMvkA9TFgZcUqozRop0J3T2 > qh7wkK24BDRIJXwGtyhdUiCEPVqw9zAtNKCB8LWqabIEQ2ZgGowEfxlbNyByup5U > hlKYVyclMB+d5whz67hISXfA+/DEaG4l8yb4m4FprFUx5VkvwnyC9i97j3kFYFSn > 85UnkgLAj07tI2GVE2g4J5uhHCIvWuwMpuBpccBYy7OV558BZzGA1BhZoE+fAbPP > ZG7G21ZVYd8bt4oReePU3pz9+6y1gaKrlX6VUSpxe6Isqc81uGdppU1JZ0WIPfet > DrWlW5vTtuyujfObCNdNaXxhsz4DMz4Hy8cyg2WQuHFIfWL0Hisx6JMf8y2TUnxp > pp18q/J5GI+863iIAfrX22XjKNGwD7JZlfzKwi258QcelWKVvtMHepvQuduM1MUr > +44A9COG8AeP
Re: libreoffice fails to build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 /usr/bin/unzip -uo test.zip unzip: -n, -o and -u are contradictory /usr/local/bin/unzip -uo test.zip Archive: test.zip i will create a symlink to /usr/bin/zip and run a test in libreoffice. Am 22.07.2012 11:20, schrieb Robert Backhaus: > On 22 July 2012 18:21, Joerg Surmann wrote: > >> > think the unzip path is ok. > i have reinstall unzip. > now will update libreoffice. > > # whereis unzip > unzip: /usr/bin/unzip /usr/share/man/en.ISO8859-15/man1/unzip.1.gz > /usr/src/usr.bin/unzip > > # locate \*/unzip > /media/disk/usr/bin/unzip > /usr/bin/unzip > /usr/jails/basejail/usr/bin/unzip > /usr/jails/basejail/usr/ports/archivers/unzip > /usr/jails/basejail/usr/ports/chinese/unzip > /usr/jails/basejail/usr/ports/korean/unzip > /usr/jails/basejail/usr/ports/russian/unzip > /usr/local/bin/unzip > /usr/local/share/doc/unzip > /usr/obj/usr/src/usr.bin/unzip > /usr/obj/usr/src/usr.bin/unzip/unzip > /usr/ports/archivers/unzip > /usr/src/usr.bin/unzip > /var/db/ports/unzip > > # uname -a > FreeBSD xxx.xxx.xxx 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #3: Mon Jul 2 > 17:58:18 CEST 2012 r...@xxx.xxx.xxx:/usr/obj/usr/src/sys/KERNEL amd64 > > > Ah, sorry, I mislead you there. I've got linux on this notebook, and the > > window I tested unzip in happened to be local, not ssh! > > The /usr/bin one fails. the /usr/local/bin one succeded. Try unzipping a > > file, using /usr/bin/unzip -uo, and again using /usr/local/bin/unzip -uo . > > The first should fail, the second should succeed. > > I do not know why it is using the wrong unzip, I do not know > > > > Am 22.07.2012 04:00, schrieb Robert Backhaus: > >>> On 22 July 2012 06:39, Joerg Surmann wrote: > > >>> #build > >>> mkdir -p ../../unxfbsd.pro/misc/java_src/ > >>> cp > >>> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/solver/ > unxfbsd.pro/bin/jurt_src.zip > >>> ../../unxfbsd.pro/misc/java_src/jurt_src.zip > >>> cd ../../unxfbsd.pro/misc/java_src && unzip -quo jurt_src.zip > >>> unzip: -n, -o and -u are contradictory > >>> > Hmm, there is something wrong with your unzip. The stock unzip has no > problems with those options. > Could you please run "whereis unzip"? Unzip should be in /usr/bin. > Check your path, check the output of "locate \*/unzip" (that will list > directories as well as files called unzip). You seem to have a > different version of unzip that is causing that problem. > The output of "uname -a" would help us too. > >>> > >>> > >>> dmake: Error code 1, while making > >>> '../../unxfbsd.pro/misc/java_src/jurt_src.zip' > >>> dmake: '../../unxfbsd.pro/misc/java_src/jurt_src.zip' removed. > >>> > >>> --- > >>> Oh dear - something failed during the build - sorry ! > >>> For more help with debugging build errors, please see the section in: > >>> http://wiki.documentfoundation.org/Development > >>> > >>> internal build errors: > >>> > >>> ERROR: error 65280 occurred while making > >>> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > >>> > >>> > >>> Am 21.07.2012 13:40, schrieb Robert Huff: > >> > >> Joerg Surmann writes: > >> > >>> I have delete all qt3. > >>> > >>> now i have a new error: > >>> > >>> internal build errors: > >>> > >>> ERROR: error 65280 occurred while making > >>> > >>> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > >>> > >>> it seems that the error is inside 'odk', please re-run build > >>> inside this module to isolate the error and/or test your fix: > >>> - > --- > >> > >> Did you do: > >> > >>> /usr/local/bin/bash > >>> cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3 > >>> source ./Env.Host.sh > >>> cd odk > >>> rm -Rf > >>> > >>> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/ > unxfbsd.pro > >>> # optional module 'clean' > >>> build > >> > >> ? > >> > >> > >> Robert Huff > >>> > >>> > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscr...@freebsd.org" > >>> ___ > >>> freebsd-ports@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports > >>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > >> >> > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG wit
Re: For those that want to test vdr 1.7.29... - updated wiki
On Sun, Jul 15, 2012 at 10:26:51PM +0200, Juergen Lock wrote: > On Sat, Jul 14, 2012 at 11:06:54PM +0200, Juergen Lock wrote: > > ..I've put a shar here: > > > > http://people.freebsd.org/~nox/tmp/vdr-ports-1.7.29-001.shar > > Klaus posted a patch to fix a small bug in the recordings menu so > I posted a new shar: > > http://people.freebsd.org/~nox/tmp/vdr-ports-1.7.29-002.shar > > Again: > > > > Unshar in /usr/ports , stop vdr, then run: > > > > portmaster vdr-plugins > > > > If that succeeded (which it should, this update was rather painless) > > you can restart vdr. > > And I have just updated the wiki page a bit, > > http://wiki.freebsd.org/VDR > > it now also has a Quick start section that should make things a little > easier for new users. Committed the update: http://www.freshports.org/multimedia/vdr Enjoy, :) Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.."Makefile", line 48: Could not find /a/erwin/tindex/ports/chinese/mutt/../../mail/mutt-devel/Makefile make: fatal errors encountered -- cannot continue ===> chinese/mutt failed *** Error code 1 *** Error code 1 Stop in /a/erwin/tindex/ports. *** Error code 1 Stop in /a/erwin/tindex/ports. 1 error Committers on the hook: crees culot daichi kuriyama mm mva nox pawel Most recent CVS update was: U Mk/bsd.options.desc.mk U audio/libbs2b/Makefile U devel/p5-CPAN-Perl-Releases/Makefile U devel/p5-CPAN-Perl-Releases/distinfo U devel/p5-Module-CoreList/Makefile U devel/p5-Module-CoreList/distinfo U devel/p5-Test-MockObject/Makefile U japanese/mozc-server/Makefile U japanese/trac/Makefile U japanese/trac/distinfo U mail/Makefile U mail/mutt/Makefile U mail/mutt/distinfo U mail/mutt/files/extra-patch-aspell U mail/mutt/files/extra-patch-doc-ref U mail/mutt/files/extra-patch-doc-xml U mail/mutt/files/extra-patch-greeting U mail/mutt/files/extra-patch-ifdef U mail/mutt/files/extra-patch-maildir-mtime U mail/mutt/files/extra-patch-maildir-mtime-nntp U mail/mutt/files/extra-patch-no-mbox-manpage U mail/mutt/files/extra-patch-nodoc-contrib U mail/mutt/files/extra-patch-parent-child-match U mail/mutt/files/extra-patch-pgp-dw U mail/mutt/files/extra-patch-reverse_reply U mail/mutt/files/extra-patch-sidebar U mail/mutt/files/extra-patch-sidebar-nntp U mail/mutt/files/extra-patch-signature-menu U mail/mutt/files/extra-patch-smime-outlook U mail/mutt/files/extra-patch-trash-purge U mail/mutt/files/patch-02 U mail/mutt/files/patch-05 U mail/mutt/files/patch-08 U mail/mutt/files/patch-Makefile.am U mail/mutt/files/patch-Makefile.am.doc U mail/mutt/files/patch-bdb U mail/mutt/files/patch-color-eol U mail/mutt/files/patch-configure.ac U mail/mutt/files/patch-contrib-Makefile.am U mail/mutt/files/patch-crypt-gpgme.c U mail/mutt/files/patch-date-conditional U mail/mutt/files/patch-doc-manual.xml.head U mail/mutt/files/patch-examples U mail/mutt/files/patch-gnutls-CN-validation U mail/mutt/files/patch-imap-message.c U mail/mutt/files/patch-mktemp U mail/mutt/files/patch-nbsp U mail/mutt/files/patch-pgp U mail/mutt/files/patch-smime-self U mail/mutt/files/patch-smime-sender U mail/mutt/files/patch-threadcomplete U mail/mutt/scripts/generate-plist U mail/mutt-lite/Makefile U mail/mutt14/Makefile U mail/mutt14-lite/Makefile U mail/p5-Mail-GnuPG/Makefile U mail/p5-Mail-GnuPG/distinfo U multimedia/gavl/Makefile U multimedia/gavl/distinfo U multimedia/gavl/pkg-plist U multimedia/gmerlin/Makefile U multimedia/gmerlin/distinfo U multimedia/gmerlin/pkg-plist U multimedia/gmerlin-avdecoder/Makefile U multimedia/gmerlin-avdecoder/distinfo U multimedia/gmerlin-avdecoder/files/patch-lib-demux_ffmpeg.c U www/py-bleach/Makefile U www/py-bleach/distinfo U www/trac-accountmanager/Makefile U www/trac-accountmanager/distinfo U www/vdr-plugin-live/Makefile ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: INDEX build failed for 7.x
I think the script was updating when I committed the mutt move. Hopefully the next build will be OK. Chris On 22 Jul 2012 11:19, "Erwin Lansing" wrote: > INDEX build failed with errors: > Generating INDEX-7 - please wait.."Makefile", line 48: Could not find > /a/erwin/tindex/ports/chinese/mutt/../../mail/mutt-devel/Makefile > make: fatal errors encountered -- cannot continue > ===> chinese/mutt failed > *** Error code 1 > *** Error code 1 > > Stop in /a/erwin/tindex/ports. > *** Error code 1 > > Stop in /a/erwin/tindex/ports. > 1 error > > Committers on the hook: > crees culot daichi kuriyama mm mva nox pawel > > Most recent CVS update was: > U Mk/bsd.options.desc.mk > U audio/libbs2b/Makefile > U devel/p5-CPAN-Perl-Releases/Makefile > U devel/p5-CPAN-Perl-Releases/distinfo > U devel/p5-Module-CoreList/Makefile > U devel/p5-Module-CoreList/distinfo > U devel/p5-Test-MockObject/Makefile > U japanese/mozc-server/Makefile > U japanese/trac/Makefile > U japanese/trac/distinfo > U mail/Makefile > U mail/mutt/Makefile > U mail/mutt/distinfo > U mail/mutt/files/extra-patch-aspell > U mail/mutt/files/extra-patch-doc-ref > U mail/mutt/files/extra-patch-doc-xml > U mail/mutt/files/extra-patch-greeting > U mail/mutt/files/extra-patch-ifdef > U mail/mutt/files/extra-patch-maildir-mtime > U mail/mutt/files/extra-patch-maildir-mtime-nntp > U mail/mutt/files/extra-patch-no-mbox-manpage > U mail/mutt/files/extra-patch-nodoc-contrib > U mail/mutt/files/extra-patch-parent-child-match > U mail/mutt/files/extra-patch-pgp-dw > U mail/mutt/files/extra-patch-reverse_reply > U mail/mutt/files/extra-patch-sidebar > U mail/mutt/files/extra-patch-sidebar-nntp > U mail/mutt/files/extra-patch-signature-menu > U mail/mutt/files/extra-patch-smime-outlook > U mail/mutt/files/extra-patch-trash-purge > U mail/mutt/files/patch-02 > U mail/mutt/files/patch-05 > U mail/mutt/files/patch-08 > U mail/mutt/files/patch-Makefile.am > U mail/mutt/files/patch-Makefile.am.doc > U mail/mutt/files/patch-bdb > U mail/mutt/files/patch-color-eol > U mail/mutt/files/patch-configure.ac > U mail/mutt/files/patch-contrib-Makefile.am > U mail/mutt/files/patch-crypt-gpgme.c > U mail/mutt/files/patch-date-conditional > U mail/mutt/files/patch-doc-manual.xml.head > U mail/mutt/files/patch-examples > U mail/mutt/files/patch-gnutls-CN-validation > U mail/mutt/files/patch-imap-message.c > U mail/mutt/files/patch-mktemp > U mail/mutt/files/patch-nbsp > U mail/mutt/files/patch-pgp > U mail/mutt/files/patch-smime-self > U mail/mutt/files/patch-smime-sender > U mail/mutt/files/patch-threadcomplete > U mail/mutt/scripts/generate-plist > U mail/mutt-lite/Makefile > U mail/mutt14/Makefile > U mail/mutt14-lite/Makefile > U mail/p5-Mail-GnuPG/Makefile > U mail/p5-Mail-GnuPG/distinfo > U multimedia/gavl/Makefile > U multimedia/gavl/distinfo > U multimedia/gavl/pkg-plist > U multimedia/gmerlin/Makefile > U multimedia/gmerlin/distinfo > U multimedia/gmerlin/pkg-plist > U multimedia/gmerlin-avdecoder/Makefile > U multimedia/gmerlin-avdecoder/distinfo > U multimedia/gmerlin-avdecoder/files/patch-lib-demux_ffmpeg.c > U www/py-bleach/Makefile > U www/py-bleach/distinfo > U www/trac-accountmanager/Makefile > U www/trac-accountmanager/distinfo > U www/vdr-plugin-live/Makefile > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libreoffice fails to build
On 22 July 2012 20:13, Joerg Surmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > /usr/bin/unzip -uo test.zip > unzip: -n, -o and -u are contradictory > > /usr/local/bin/unzip -uo test.zip > Archive: test.zip > > i will create a symlink to /usr/bin/zip > and run a test in libreoffice. Just to be clear, it is /usr/bin/unzip that doesn't seem to work for libreoffice, and /usr/local/bin/unzip does, so any symlinks will need to point to /usr/local/bin/unzip. The port should have worked this our, though - I had no problems, and no one else has chimed in with any explanation. > > Am 22.07.2012 11:20, schrieb Robert Backhaus: >> On 22 July 2012 18:21, Joerg Surmann wrote: >> >>> >> think the unzip path is ok. >> i have reinstall unzip. >> now will update libreoffice. >> >> # whereis unzip >> unzip: /usr/bin/unzip /usr/share/man/en.ISO8859-15/man1/unzip.1.gz >> /usr/src/usr.bin/unzip >> >> # locate \*/unzip >> /media/disk/usr/bin/unzip >> /usr/bin/unzip >> /usr/jails/basejail/usr/bin/unzip >> /usr/jails/basejail/usr/ports/archivers/unzip >> /usr/jails/basejail/usr/ports/chinese/unzip >> /usr/jails/basejail/usr/ports/korean/unzip >> /usr/jails/basejail/usr/ports/russian/unzip >> /usr/local/bin/unzip >> /usr/local/share/doc/unzip >> /usr/obj/usr/src/usr.bin/unzip >> /usr/obj/usr/src/usr.bin/unzip/unzip >> /usr/ports/archivers/unzip >> /usr/src/usr.bin/unzip >> /var/db/ports/unzip >> >> # uname -a >> FreeBSD xxx.xxx.xxx 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #3: Mon Jul 2 >> 17:58:18 CEST 2012 r...@xxx.xxx.xxx:/usr/obj/usr/src/sys/KERNEL amd64 >> >> >> Ah, sorry, I mislead you there. I've got linux on this notebook, and the >> > window I tested unzip in happened to be local, not ssh! >> > The /usr/bin one fails. the /usr/local/bin one succeded. Try unzipping a >> > file, using /usr/bin/unzip -uo, and again using /usr/local/bin/unzip > -uo . >> > The first should fail, the second should succeed. >> > I do not know why it is using the wrong unzip, I do not know >> >> >> >> Am 22.07.2012 04:00, schrieb Robert Backhaus: >> >>> On 22 July 2012 06:39, Joerg Surmann > wrote: >> >> >>> #build >> >>> mkdir -p ../../unxfbsd.pro/misc/java_src/ >> >>> cp >> >>> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/solver/ >> unxfbsd.pro/bin/jurt_src.zip >> >>> ../../unxfbsd.pro/misc/java_src/jurt_src.zip >> >>> cd ../../unxfbsd.pro/misc/java_src && unzip -quo jurt_src.zip >> >>> unzip: -n, -o and -u are contradictory >> >>> >> Hmm, there is something wrong with your unzip. The stock unzip has no >> problems with those options. >> Could you please run "whereis unzip"? Unzip should be in /usr/bin. >> Check your path, check the output of "locate \*/unzip" (that will > list >> directories as well as files called unzip). You seem to have a >> different version of unzip that is causing that problem. >> The output of "uname -a" would help us too. >> >>> >> >>> >> >>> dmake: Error code 1, while making >> >>> '../../unxfbsd.pro/misc/java_src/jurt_src.zip' >> >>> dmake: '../../unxfbsd.pro/misc/java_src/jurt_src.zip' removed. >> >>> >> >>> > --- >> >>> Oh dear - something failed during the build - sorry ! >> >>> For more help with debugging build errors, please see the section in: >> >>> http://wiki.documentfoundation.org/Development >> >>> >> >>> internal build errors: >> >>> >> >>> ERROR: error 65280 occurred while making >> >>> >> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu >> >>> >> >>> >> >>> Am 21.07.2012 13:40, schrieb Robert Huff: >> >> >> >> Joerg Surmann writes: >> >> >> >>> I have delete all qt3. >> >>> >> >>> now i have a new error: >> >>> >> >>> internal build errors: >> >>> >> >>> ERROR: error 65280 occurred while making >> >>> >> >>> >> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu >> >>> >> >>> it seems that the error is inside 'odk', please re-run build >> >>> inside this module to isolate the error and/or test your fix: >> >>> - >> --- >> >> >> >> Did you do: >> >> >> >>> /usr/local/bin/bash >> >>> cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3 >> >>> source ./Env.Host.sh >> >>> cd odk >> >>> rm -Rf >> >>> >> >>> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/ >> unxfbsd.pro >> >>> # optional module 'clean' >> >>> build >> >> >> >> ? >> >> >> >> >> >> Robert Huff >> >>> >> >>> >> >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to >> > "freebsd-ports-unsubscr...@freebsd.org" >> >>> ___ >> >>>
Re: Re: How to remove erroneous deps from pkgng
On Sat, 21 Jul 2012 21:56:49 -0700 Doug Barton wrote: > KDE folks Jason's suggestion (by private e-mail for some reason) > was that we add pkgconfig to USE_GNOME= for every port that depends on > kdelibs that doesn't already have it; since almost, if not actually all > of them are currently relying on the run-dep side effect. I can't see > any reason NOT to do this, but if you have an objection please speak up > sooner rather than later. KDE 4 ports don't require pkgconfig although they may use it if available. If some ports strongly rely on pkgconfig and don't set USE_GNOME properly they must be fixed. So let have exp-run first. Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
INDEX now builds successfully on 7.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On Sat, Jul 21, 2012 at 11:56 PM, Doug Barton wrote: > KDE folks Jason's suggestion (by private e-mail for some reason) > was that we add pkgconfig to USE_GNOME= for every port that depends on > kdelibs that doesn't already have it; since almost, if not actually all > of them are currently relying on the run-dep side effect. I can't see > any reason NOT to do this, but if you have an objection please speak up > sooner rather than later. > > On 07/21/2012 21:33, Jeremy Messenger wrote: >> On Sat, Jul 21, 2012 at 4:04 PM, Doug Barton wrote: >>> On 07/21/2012 13:48, Jason E. Hale wrote: >>> IMO I don't really see what the hurry is. This has been the behavior for years. >>> >>> Yes, and some of us have been annoyed by it for years as well. :) >>> >>> The current behavior is wrong, and becomes increasingly painful in a >>> world where most FreeBSD users are using packages because it drags in a >>> totally pointless package to essentially every FreeBSD system. Fixing >>> this bug is a good thing, and needs to be done sooner rather than later. >> >> >> It is unnecessary to be in hurry when that pkg-config has been in the >> bsd.gnome.mk for about nine years. > > The sooner we start fixing it, the better off we are. > >> I already have a better solution >> available for weeks. Therefore, you (and others) need to be patient >> because when I add the :build/:run dependency in the bsd.gnome.mk then >> that pkg-config runtime dependency will be re-added. > > Um, yeah ... don't do that. You need to start to respect the people's work and plan, Doug. Also I am part of team that maintaining the bsd.gnome.mk. Yes it will be re-add if anyone plan to remove it, because I already have planned add the :build/:run feature in the bsd.gnome.mk that the without :* will be both build/run time dependency. It is impossible for me to not re-add it. It is not going to be long because I already have function :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) available. The only thing that I don't plan is to chase thousands of port to have the 'pkgconfig;build'. If anyone want to take up this task is cool with me. > I mis-attributed your patch to Jason previously, sorry about that. But > before it goes in your patch should have the logic I spoke about in my > previous posts, to make sure that the USE_GNOME bits cannot get added as > the wrong kinds of deps. > >> And no I am not >> going to work on chase all ports to have the 'pkgconfig:build' >> (sorry). > > Not asking you to. I'm asking you to fix your patch so that things that > should only be one kind of dep or the other (like pkgconfig, but not > necessarily limited to it) are handled properly by default if the right > :label is not attached, and error out if the wrong one is. That way the > work that's being done now to fix ports that need explicit build deps > for pkg-config will solve this part of the problem for you. > > As you pointed out, the current situation has existed for a long time > already. If we have to wait another week or 2 for the pkg-config run dep > problem to be fixed properly before your patch gets committed, that's > not really a problem. > > Doug > > -- > > Change is hard. > > > -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
CFT: New mplayer / mencoder snapshot
Hi all, if you are a regular mplayer / mencoder user, you are invited to test a new snapshot from 2012-07-21. The drop-in replacements for the ports files for both can be found here: http://bsdistfiles.googlecode.com/files/m20120722.tar.bz2 There are no new spectacular features, however especially the continuous ffmpeg evolvement justifies regular upgrades. This snapshot was surprisingly easy to port, so I probably have overlooked something :-) I made one noticeable change, though: stable/9 and later users won't see the OPTION to use gcc4.6+ any more. The port uses clang on these systems now. Note that I have tested this snapshot only on amd64. Have fun and as usual, feel free to report problems or suggestions to me. Best regards Riggs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: libreoffice fails to build
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Yes, you are right. The update is finish. Thanks for your help. Best regards Suri Am 22.07.2012 14:18, schrieb Robert Backhaus: > On 22 July 2012 20:13, Joerg Surmann wrote: >> > /usr/bin/unzip -uo test.zip > unzip: -n, -o and -u are contradictory > > /usr/local/bin/unzip -uo test.zip > Archive: test.zip > > i will create a symlink to /usr/bin/zip > and run a test in libreoffice. > > > Just to be clear, it is /usr/bin/unzip that doesn't seem to work for > > libreoffice, and /usr/local/bin/unzip does, so any symlinks will need > > to point to /usr/local/bin/unzip. > > > The port should have worked this our, though - I had no problems, and > > no one else has chimed in with any explanation. > > > Am 22.07.2012 11:20, schrieb Robert Backhaus: > >>> On 22 July 2012 18:21, Joerg Surmann wrote: > >>> > > >>> think the unzip path is ok. > >>> i have reinstall unzip. > >>> now will update libreoffice. > >>> > >>> # whereis unzip > >>> unzip: /usr/bin/unzip /usr/share/man/en.ISO8859-15/man1/unzip.1.gz > >>> /usr/src/usr.bin/unzip > >>> > >>> # locate \*/unzip > >>> /media/disk/usr/bin/unzip > >>> /usr/bin/unzip > >>> /usr/jails/basejail/usr/bin/unzip > >>> /usr/jails/basejail/usr/ports/archivers/unzip > >>> /usr/jails/basejail/usr/ports/chinese/unzip > >>> /usr/jails/basejail/usr/ports/korean/unzip > >>> /usr/jails/basejail/usr/ports/russian/unzip > >>> /usr/local/bin/unzip > >>> /usr/local/share/doc/unzip > >>> /usr/obj/usr/src/usr.bin/unzip > >>> /usr/obj/usr/src/usr.bin/unzip/unzip > >>> /usr/ports/archivers/unzip > >>> /usr/src/usr.bin/unzip > >>> /var/db/ports/unzip > >>> > >>> # uname -a > >>> FreeBSD xxx.xxx.xxx 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #3: Mon Jul 2 > >>> 17:58:18 CEST 2012 r...@xxx.xxx.xxx:/usr/obj/usr/src/sys/KERNEL amd64 > >>> > >>> > >>> Ah, sorry, I mislead you there. I've got linux on this notebook, and the > window I tested unzip in happened to be local, not ssh! > The /usr/bin one fails. the /usr/local/bin one succeded. Try unzipping a > file, using /usr/bin/unzip -uo, and again using /usr/local/bin/unzip > -uo . > The first should fail, the second should succeed. > I do not know why it is using the wrong unzip, I do not know > >>> > >>> > >>> > >>> Am 22.07.2012 04:00, schrieb Robert Backhaus: > >> On 22 July 2012 06:39, Joerg Surmann > wrote: > >>> > >> #build > >> mkdir -p ../../unxfbsd.pro/misc/java_src/ > >> cp > >> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/solver/ > >>> unxfbsd.pro/bin/jurt_src.zip > >> ../../unxfbsd.pro/misc/java_src/jurt_src.zip > >> cd ../../unxfbsd.pro/misc/java_src && unzip -quo jurt_src.zip > >> unzip: -n, -o and -u are contradictory > >> > >>> Hmm, there is something wrong with your unzip. The stock unzip has no > >>> problems with those options. > >>> Could you please run "whereis unzip"? Unzip should be in /usr/bin. > >>> Check your path, check the output of "locate \*/unzip" (that will > list > >>> directories as well as files called unzip). You seem to have a > >>> different version of unzip that is causing that problem. > >>> The output of "uname -a" would help us too. > >> > >> > >> dmake: Error code 1, while making > >> '../../unxfbsd.pro/misc/java_src/jurt_src.zip' > >> dmake: '../../unxfbsd.pro/misc/java_src/jurt_src.zip' removed. > >> > >> > --- > >> Oh dear - something failed during the build - sorry ! > >> For more help with debugging build errors, please see the section in: > >> http://wiki.documentfoundation.org/Development > >> > >> internal build errors: > >> > >> ERROR: error 65280 occurred while making > >> > >>> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > >> > >> > >> Am 21.07.2012 13:40, schrieb Robert Huff: > > > > Joerg Surmann writes: > > > >> I have delete all qt3. > >> > >> now i have a new error: > >> > >> internal build errors: > >> > >> ERROR: error 65280 occurred while making > >> > >> > >>> > /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/pack/gendocu > >> > >> it seems that the error is inside 'odk', please re-run build > >> inside this module to isolate the error and/or test your fix: > >> - > >>> --- > > > > Did you do: > > > >> /usr/local/bin/bash > >> cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3 > >> source ./Env.Host.sh > >> cd odk > >> rm -Rf > >> > >> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.5.3/odk/ > >>> unxfbsd.pro > >> # optional module 'clean' > >
Re: [HEADSUP & CFT] pkg 1.0rc1 and schedule
Am 13.07.2012 18:20, schrieb John Baldwin: > To clarify, you are not being criticized for speaking up, you are being > criticized for the way in which you are speaking up (an accusatory tone) and > for blowing off a pointer to a talk that would perhaps answer some of your > questions. John, for lack of testing PKGNG I can't really comment on it on a technical grounds. I do need to support Doug in the way he's 'blown off a pointer to a talk' though, and understand Doug's reluctance in following it. I, too, would refuse to watch a one hour video if I've asked less than a handful of concise and specific questions. Luckily, the answers have more or less been given in sibling threads. > Back to my original e-mail: FreeBSD is a big project. I try to keep a pulse > on as much of it as I can (mostly by reading/skimming a _lot_ of e-mail each > day), but even with all that there is a lot going on that I don't know the > intimate details of. Instead, I choose to trust my fellow developers to > best manage the areas over which they have expertise and detailed knowledge > until given strong evidence to assume otherwise. My humble suggestion to you > would be to adopt a similar strategy. There is one other personal line of thinking I have: if people can't concisely explain what they're up to, I get suspicious, and I sympathize with Doug there. And even though Bapt has made efforts to explain, I can't help but get the feeling that Doug and Bapt have been talking past each other for a while. And I also do not believe that Doug was interested in "this made me happy" case stories by systems administrators, for neither was I. While it's good that we can make some individuals happy, that's a question quite distinct from the question "will it benefit the project as a whole". I found the discussion that spun off between Peter Jeremy and Matthew Seaman rather elucidating, but the one thing I fear is that we no longer have text-based metadata. If you've ever used "pver" as a port version comparision tool, you know how fast the answer "which ports need updating/removal/replacement" can be even with the classical /var/db/pkg layout. I personally see that some of the 1.0rc shortcomings are showstoppers, but then since I've not really been helpful on getting ports in shape for -CURRENT beyond fixing ports so they could be removed from the "fails to build on " wiki lists, my opinion hasn't much weight regarding -CURRENT. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: A maintainers question: how to create a user?
On 16 December 2011 17:56, Chris Rees wrote:
> On 16 December 2011 15:27, Paul Schmehl wrote:
>> --On December 15, 2011 7:16:09 PM -0500 Aryeh Friedman
>> wrote:
>>
>>> See subject for the main question... the details: I am the maintainer of
>>> devel/aegis and the final installation step typically (linux RPM's for
>>> example) is to create a user to hold the baselines (in svn/cvs/csup speak
>>> the project's repo) of the varioous projects managed by aegis...
>>> customerly this is MUST be a non-logginable (you MUST [requirements
>>> document meaning of upper case MUST/SHOULD/MAY {NOT}) but allow for su
>>> from either root or via sudo a member of "wheel")... it is a standard
>>> account in all other respects for example I typically set it to tcsh but
>>> the port might want to make that an make time option... what is the best
>>> way of setting this all up (both the no options and the options based
>>> versions)
>>>
>>
>> Look at USERS and GROUPS in /usr/ports/Mk/bsd.port.mk
>>
>
>
> It is possible to have aegis automatically added to wheel, but
> personally I'd prefer that a message were printed to suggest that
> rather than automate it Others may disagree!
How are you getting on with this?
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 07/22/2012 07:51, Jeremy Messenger wrote: > You need to start to respect the people's work and plan, Doug. Also I > am part of team that maintaining the bsd.gnome.mk. Yes it will be > re-add if anyone plan to remove it, because I already have planned add > the :build/:run feature in the bsd.gnome.mk that the without :* will > be both build/run time dependency. It is impossible for me to not > re-add it. It is not going to be long because I already have function > :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) > available. > > The only thing that I don't plan is to chase thousands of port to have > the 'pkgconfig;build'. If anyone want to take up this task is cool > with me. So what you're saying is that in spite of the fact that the community has identified a bug that it wants to fix, a bug which was added by the team maintaining bsd.gnome.mk, that you are refusing to modify your patch to handle the bug; but instead are demanding your right to reintroduce the bug, and then further demanding the right to not fix it after the patch is in? And furthermore, you're refusing to even look at the other dependencies which are handled by bsd.gnome.mk to see if similar bugs were introduced *by your team*, but you're happy to let everyone else sort out the problems in thousands of ports for you. And you want me to respect that? -- Change is hard. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 07/22/2012 06:10, Max Brazhnikov wrote: > On Sat, 21 Jul 2012 21:56:49 -0700 Doug Barton wrote: >> KDE folks Jason's suggestion (by private e-mail for some reason) >> was that we add pkgconfig to USE_GNOME= for every port that depends on >> kdelibs that doesn't already have it; since almost, if not actually all >> of them are currently relying on the run-dep side effect. I can't see >> any reason NOT to do this, but if you have an objection please speak up >> sooner rather than later. > > KDE 4 ports don't require pkgconfig although they may use it if available. If > some ports strongly rely on pkgconfig and don't set USE_GNOME properly they > must be fixed. So let have exp-run first. Okey dokey. -- Change is hard. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
thank you for svn ports tree!!
The switch to svn made maintaining my ports tree easier. Big thank to whoever made this possible! P.S. There has been quite a bit of negative opinion/emotion on this list recently. So, just to say that I'm a happy customer, and, as a user, I do appreciate all the hard work lots of people put (have put? are putting? have been putting?) in making the ports tree one of the best parts of the FreeBSD project. Thanks! -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portlint 2.3.11 not .svn ready yet?
Stepping into the water... portlint -C has not be updated to look for .svn and not CVS directories? portlint -V portlint version 2.13.11 portlint -abmt looks fine. portlint -C WARN: .svn: dotfiles are not preferred. If this file is a dotfile to be installed as an example, consider importing it as "dot.svn". FATAL: .svn/props: empty directory should be removed. FATAL: .svn/tmp/text-base: empty directory should be removed. FATAL: .svn/tmp/prop-base: empty directory should be removed. FATAL: .svn/tmp/props: empty directory should be removed. WARN: files/.svn: dotfiles are not preferred. If this file is a dotfile to be installed as an example, consider importing it as "dot.svn". FATAL: files/.svn/props: empty directory should be removed. FATAL: files/.svn/tmp/text-base: empty directory should be removed. FATAL: files/.svn/tmp/prop-base: empty directory should be removed. FATAL: files/.svn/tmp/props: empty directory should be removed. WARN: no CVS directories. Use -N to check a new port. 8 fatal errors and 3 warnings found. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re: How to remove erroneous deps from pkgng
On Sun, 22 Jul 2012 09:51:40 -0500 Jeremy Messenger wrote: > You need to start to respect the people's work and plan, Doug. Also I > am part of team that maintaining the bsd.gnome.mk. Yes it will be > re-add if anyone plan to remove it, because I already have planned add > the :build/:run feature in the bsd.gnome.mk that the without :* will > be both build/run time dependency. in kde4.mk we support not only run/build suffixes, but also have default dependence type if suffix is not set. > The only thing that I don't plan is to chase thousands of port to have > the 'pkgconfig;build'. If anyone want to take up this task is cool > with me. Why should we change lots of ports and always keep eyes on new ports, if it can be altered once in .mk ?? Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re: How to remove erroneous deps from pkgng
On Sun, Jul 22, 2012 at 6:22 PM, Max Brazhnikov wrote: > On Sun, 22 Jul 2012 09:51:40 -0500 Jeremy Messenger wrote: >> You need to start to respect the people's work and plan, Doug. Also I >> am part of team that maintaining the bsd.gnome.mk. Yes it will be >> re-add if anyone plan to remove it, because I already have planned add >> the :build/:run feature in the bsd.gnome.mk that the without :* will >> be both build/run time dependency. > > in kde4.mk we support not only run/build suffixes, but also have default > dependence type if suffix is not set. > >> The only thing that I don't plan is to chase thousands of port to have >> the 'pkgconfig;build'. If anyone want to take up this task is cool >> with me. > > Why should we change lots of ports and always keep eyes on new ports, if it > can be altered once in .mk ?? Because it's not a right solution. There are very few need pkg-config in the runtime dependency. Also I already have designed feature that way (it's not for pkg-config, but all stuff in the bsd.gnome.mk) and it doesn't break anything by defaut. But don't worry because bapt, kwm and I have discussed about add USE_PKGCONFIG in the bsd.port.mk and rip pkg-config out of bsd.gnome.mk. It's even better, but I know it's more work like USE_GNOME=pkgconfig:build. Cheers, Mezz > Max -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On Sun, Jul 22, 2012 at 4:16 PM, Doug Barton wrote: > On 07/22/2012 07:51, Jeremy Messenger wrote: >> You need to start to respect the people's work and plan, Doug. Also I >> am part of team that maintaining the bsd.gnome.mk. Yes it will be >> re-add if anyone plan to remove it, because I already have planned add >> the :build/:run feature in the bsd.gnome.mk that the without :* will >> be both build/run time dependency. It is impossible for me to not >> re-add it. It is not going to be long because I already have function >> :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) >> available. >> >> The only thing that I don't plan is to chase thousands of port to have >> the 'pkgconfig;build'. If anyone want to take up this task is cool >> with me. > > So what you're saying is that in spite of the fact that the community > has identified a bug that it wants to fix, a bug which was added by the > team maintaining bsd.gnome.mk, that you are refusing to modify your > patch to handle the bug; but instead are demanding your right to > reintroduce the bug, and then further demanding the right to not fix it > after the patch is in? Remove the runtime dependency is a bug either because there are a few that need it in the runtime dependency. I have written a best solution than remove that runtime line. It will be 99% bug free when all ports have the right :build/:run. > And furthermore, you're refusing to even look at > the other dependencies which are handled by bsd.gnome.mk to see if > similar bugs were introduced *by your team*, but you're happy to let > everyone else sort out the problems in thousands of ports for you. Quiet simple, I do not have time for that huge project. I already have added :build/:run feature before anyone complain about the pkg-config dependency. The feature happened to address this issue and fix all pkg-config dependency was not part of my TODO list. My method does not break before or after patch any port, but still have the wrong dependency which it's minor and can be fixed by edit to pkgconfig:build. > And you want me to respect that? > > -- > > Change is hard. -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On 07/22/2012 17:50, Jeremy Messenger wrote: > On Sun, Jul 22, 2012 at 4:16 PM, Doug Barton wrote: >> On 07/22/2012 07:51, Jeremy Messenger wrote: >>> You need to start to respect the people's work and plan, Doug. Also I >>> am part of team that maintaining the bsd.gnome.mk. Yes it will be >>> re-add if anyone plan to remove it, because I already have planned add >>> the :build/:run feature in the bsd.gnome.mk that the without :* will >>> be both build/run time dependency. It is impossible for me to not >>> re-add it. It is not going to be long because I already have function >>> :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) >>> available. >>> >>> The only thing that I don't plan is to chase thousands of port to have >>> the 'pkgconfig;build'. If anyone want to take up this task is cool >>> with me. >> >> So what you're saying is that in spite of the fact that the community >> has identified a bug that it wants to fix, a bug which was added by the >> team maintaining bsd.gnome.mk, that you are refusing to modify your >> patch to handle the bug; but instead are demanding your right to >> reintroduce the bug, and then further demanding the right to not fix it >> after the patch is in? > > Remove the runtime dependency is a bug either because there are a few > that need it in the runtime dependency. Which ports are those? And even if these ports exist, an explicit run dep can be added for them. Better to add one more dep for a few ports than bogus ones for thousands. > I have written a best solution > than remove that runtime line. It will be 99% bug free when all ports > have the right :build/:run. I'm interested in your feedback to Max' point that the equivalent functionality for kde.mk already has the right logic to handle proper defaults if the right :label isn't set. >> And furthermore, you're refusing to even look at >> the other dependencies which are handled by bsd.gnome.mk to see if >> similar bugs were introduced *by your team*, but you're happy to let >> everyone else sort out the problems in thousands of ports for you. > > Quiet simple, I do not have time for that huge project. That's fine, stand aside and let people who are willing to solve the problem properly do the work. Then when your patch is in proper shape it can be committed without fear of adding new bugs, or re-adding old ones. The position you're taking that we can't fix the bug because you demand your right to get *your* patch in is entirely unreasonable. Doug -- Change is hard. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to remove erroneous deps from pkgng
On Mon, Jul 23, 2012 at 4:22 AM, Doug Barton wrote: > On 07/22/2012 17:50, Jeremy Messenger wrote: >> On Sun, Jul 22, 2012 at 4:16 PM, Doug Barton wrote: >>> On 07/22/2012 07:51, Jeremy Messenger wrote: You need to start to respect the people's work and plan, Doug. Also I am part of team that maintaining the bsd.gnome.mk. Yes it will be re-add if anyone plan to remove it, because I already have planned add the :build/:run feature in the bsd.gnome.mk that the without :* will be both build/run time dependency. It is impossible for me to not re-add it. It is not going to be long because I already have function :build/:run in the bsd.mate.mk (was repocopied from bsd.gnome.mk) available. The only thing that I don't plan is to chase thousands of port to have the 'pkgconfig;build'. If anyone want to take up this task is cool with me. >>> >>> So what you're saying is that in spite of the fact that the community >>> has identified a bug that it wants to fix, a bug which was added by the >>> team maintaining bsd.gnome.mk, that you are refusing to modify your >>> patch to handle the bug; but instead are demanding your right to >>> reintroduce the bug, and then further demanding the right to not fix it >>> after the patch is in? >> >> Remove the runtime dependency is a bug either because there are a few >> that need it in the runtime dependency. > > Which ports are those? > > And even if these ports exist, an explicit run dep can be added for > them. Better to add one more dep for a few ports than bogus ones for > thousands. > >> I have written a best solution >> than remove that runtime line. It will be 99% bug free when all ports >> have the right :build/:run. > > I'm interested in your feedback to Max' point that the equivalent > functionality for kde.mk already has the right logic to handle proper > defaults if the right :label isn't set. > >>> And furthermore, you're refusing to even look at >>> the other dependencies which are handled by bsd.gnome.mk to see if >>> similar bugs were introduced *by your team*, but you're happy to let >>> everyone else sort out the problems in thousands of ports for you. >> >> Quiet simple, I do not have time for that huge project. > > That's fine, stand aside and let people who are willing to solve the > problem properly do the work. Then when your patch is in proper shape it > can be committed without fear of adding new bugs, or re-adding old ones. > > The position you're taking that we can't fix the bug because you demand > your right to get *your* patch in is entirely unreasonable. > > Doug > > -- > > Change is hard. > > > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Looking at the bsd.kde4.mk it looks like there's not much logic to detect the "right" kind of dependency. It seems to use suffixes _build and _run to achieve the same effect as pkgconfig:build and pkgconfig:run would have. It defaults to both build and run dependency if no type is specified. In my opinion Jeremy's solution would be fine for now, least amount of immediate destruction :P Regards, Kimmo Paasiala ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
