Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default
On Thu, Aug 06, 2015 at 05:19:54PM -0700, Xin Li wrote:
Hi,
Currently the default portsnap.conf would generate INDEX-11, INDEX-10
and INDEX-9. The INDEX file is only used for searching ports, and only
one (INDEX-${OSREL:R}) file is actually used.
This is default behaviour for other tools like fetchindex already. It
makes no sense to have all INDEXes installed on all systems for almost
all users, so I'm all for it. The few corner cases can, say someone
building packages for different releases, can be easily scripted around
(or recommend poudriere).
Erwin
pgpycTJTv88g5.pgp
Description: PGP signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ archivers/rvm | 1.07| 1.11 +-+ science/psychopy| 1.82.01 | 1.82.02 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: Proposal: make portsnap generate INDEX-${OSREL:R} only by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/07/15 08:50, Jamie Landeg-Jones wrote: Xin Li delp...@delphij.net wrote: On 8/6/15 22:24, Kevin Oberman wrote: Or the code in portsnap could be modified to get the current running version. I thought about this today but it won't work as advertised: someone (currently me) still have to tweak the portsnap builder configuration to announce new major version (9, 10, 11 now, and we would need 12 when 11.0-STABLE appears). However, freebsd-update or mergemaster would take care for this. I was going to suggest this too. Isn't this information available using /bin/freebsd-version -u ? Client side: yes. Server side: someone has to tell the server to start building for new - -CURRENT or stop building for old -STABLE. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.1.6 (FreeBSD) iQIcBAEBCgAGBQJVxNcgAAoJEJW2GBstM+ns2HQP/iQfmSjJ853Aj4Bs+0qed7Ya UoE4LDaX1PJSIpqswyWir34mSgqZ5jHC8wuEkNrT3dlXaSnuxBmjvZfm23T/AUFH 9b/ytjJGlZWT0Db88AOnIeiMKKKX786m9mkDxiY2C747Q0L+KqLzQx6Ltrgl7DEm 9arRlB3nQcix9u7badVgP+B3CRfspUwtqmL9m+4LFIlJQA3OPsMxySdKoJlCQD8H E1rJNV/6NOxIIX2Y+/6EBhtNnhQwbXyKT74B/4UKFaGNaKfw7XIjB5T4yGBaWhPL 4VXqzDRU2g0YGY8VM3/uXA3AfSVuVYi9kmm2R3W/91TFwOVqGH31OQQczeK78Gpn dx8+kOfC7OLGWaQ9Xb9H3bNcPUknRuUVusb4+Wbe8qXk5cWfeyIJLTK7GC4Vvq4i dGf+rYpEMls/0t+W+6e1re+XTlZtgepLfWQMuuhCbOQf8egKktClbJ++Th6krc1B Aob62BmfgNgq4mS8t21Ee2heBTTrjNwp+openjPv9+ffvhmDngshNrdp+z4umQ3G uryURepM9YYmrRWVmD9ZOei81R2QIpzdFh/Xv4w8bwTAoiV3oJfNIavbJWuhsEsk sAKU2Kk0oBiTDwOqe4ZEVfF1HWbOZe6X6gBWjwO0f/RG7Rtn9pexU9TRzBL1SmeE qUix6Wbx6VfCB+7QiQgg =LDxP -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: Proposal: make portsnap generate INDEX-${OSREL:R} only by default
Xin Li delp...@delphij.net wrote: On 8/6/15 22:24, Kevin Oberman wrote: Or the code in portsnap could be modified to get the current running version. I thought about this today but it won't work as advertised: someone (currently me) still have to tweak the portsnap builder configuration to announce new major version (9, 10, 11 now, and we would need 12 when 11.0-STABLE appears). However, freebsd-update or mergemaster would take care for this. I was going to suggest this too. Isn't this information available using /bin/freebsd-version -u ? Yes, I realise this script basically has it hardcoded, but it seems, therefore, that someone already has the task to announce new major version in that file! Cheers! Jamie ___ 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: Proposal: make portsnap generate INDEX-${OSREL:R} only by default
Xin Li delp...@delphij.net wrote: I was going to suggest this too. Isn't this information available using /bin/freebsd-version -u ? Client side: yes. Server side: someone has to tell the server to start building for new - -CURRENT or stop building for old -STABLE. Ahhh! Gotcha! Thanks for the quick response. I'll stop bike-shedding now! Cheers, Jamie ___ 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: Fwd: broken strings compiled-in into mutt
Hi! According to the mutt mailinglist: it's an issue with sed. By copying attached file as files/patch-txt2c.sh to the mutt port fixes it. I will submit an port-update in the next couple of days which also fixes other issues. Tested this patch, works. -- p...@freebsd.org +49 171 31013725 years to go ! ___ 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: Fwd: broken strings compiled-in into mutt
According to the mutt mailinglist: it's an issue with sed. By copying attached file as files/patch-txt2c.sh to the mutt port fixes it. I will submit an port-update in the next couple of days which also fixes other issues. Udo On Tue, Aug 04, 2015 at 21:48:24 +0200, Kurt Jaeger wrote: Hi! Hello Udo (as maintainer), Maybe it's a FreeBSD issue, rather than a mutt one? I see similar effects on 10.1-amd64. Mutt 1.5.23 (2014-03-12) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 10.2-RC2 (amd64) ncurses: ncurses 5.7.20081102 (compiled with 5.7) libiconv: 1.14 libidn: 1.31 (compiled with 1.29) Compiler: F eeBSD clang ve sion 3.4.1 ( ags/RELEASE_34/do 1-final 208032) 20140512 Ta ge: x86_64-unknown-f eebsd10.1 Th ead model: posix Selec ed GCC ins allaion: cc: wa ning: a gumen unused du ing compila ion: '-I /us /local/include' Configure options: '--disable-fcn l' '--wih-ssl=/us ' '--wi h-docdi =/us /local/sha e/doc/mu ' '--sysconfdi =/us /local/e c' '--enable-ex e nal-dolock' '--enable-pop' '--enable-imap' '--disable-wa nings' '--disable-flock' '--wih-libiconv-p efix=/us /local' '--wi h-idn' '--disable-gpgme' '--enable-sm p' '--enable-debug' '--enable-comp essed' '--disable-hcache' '--p efix=/us /local' '--locals a edi =/va ' '--mandi =/us /local/man' '--infodi =/us /local/info/' '--build=amd64-po bld-f eebsd10.1' 'build_alias=amd64-po bld-f eebsd10.1' 'CC=cc -I/us /local/include' 'CFLAGS=-pipe -g -fsack-p o ec o -fno-s ic-aliasing' 'LDFLAGS= -L/us /local/lib -Wl,- pah=/us /local/lib:/us /lib -l infow -Wl,- pah=/us /lib:/us /local/lib -fsack-p o ec o ' 'LIBS=' 'CPPFLAGS=' 'CPP=cpp' Compilation CFLAGS: -pipe -g -fsack-p o ec o -fno-s ic-aliasing Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +COMPRESSED +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID -USE_HCACHE -ISPELL SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to mutt-...@mutt.org. To report a bug, please visit http://bugs.mutt.org/. patch-1.5.4.cd.ifdef.1 patch-1.5.0.ats.date_conditional.1 dgc.deepif.1 vvv.quote vvv.initials rr.compressed -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ 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: Fwd: broken strings compiled-in into mutt
El día Friday, August 07, 2015 a las 07:51:42PM +0200, Schweigert, Udo escribió: According to the mutt mailinglist: Yes, I know; because I nailed it down and sent it to the mutt' mailinglist :-) it's an issue with sed. No, it's not an issue with sed itself, but with the usage of sed by someone which is not portable. Just to make sure. By copying attached file as files/patch-txt2c.sh to the mutt port fixes it. I will submit an port-update in the next couple of days which also fixes other issues. Fine. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ ☎ +49-176-38902045 No! Nein! ¡No! Όχι! -- Ευχαριστούμε! ___ 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
