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
pgpCR7ucGKwwR.pgp
Description: PGP signature
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On Wed, Nov 06, 2013 at 02:59:15PM +0100, Erwin Lansing wrote: E E Erwin, can you please handle that? E E Things are much worse that this, the ports are completely written under the assumption that there is a Bind in base, which of course would already break with WITHOUT_BIND before Bind was completely removed. It will be hard to fix without breaking the installed base of 8 and 9. Sigh. E E I'll try to work on it this week, but unfortunately have a full schedule of meetings and travel as well. Suggestion. An option to install the rc script would solve that problem. If only it was that simple, it would have been done a long time ago. As Gleb points out, the ports are broken by design. The rc script needs a complete rewrite, and that's only after fixing all configuration files, setting up chroot, etc etc and all that while not breaking the installed base on 8 and 9. I spent most of yesterday on this and if I'm lucky, I'm halfway through. Sorry about the delay, but I did finally update all three dns/bind9* ports today. I have dropped the complicated chroot, and related symlinking, logic from the default rc script as I don't think that is the right place to implement things. I would recommend users who want the extra security to use jail(8) instead of a mere chroot. This change should not affect the installed base of FreeBSD 9.x and earlier systems, but new installations there should note that the symlink option is no longer turned on by default, but still supported. I tested some default cases, but by no means can test every corner case, so please let me know how this works out. Best, Erwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 10 Beta2 /etc/rc.d/named script and /etc/defaults/rc.conf
On 04 Nov 2013, at 09:34, Gleb Smirnoff gleb...@freebsd.org wrote: [adding maintainer to Cc] On Mon, Nov 04, 2013 at 01:41:01AM +0200, George Kontostanos wrote: G Am 03.11.2013 um 23:06 schrieb Gleb Smirnoff gleb...@freebsd.org: G G On Sun, Nov 03, 2013 at 10:05:02PM +0200, Özkan KIRIK wrote: G Ö Altough bind removed from FreeBSD 10 distribution, /etc/rc.d/named G script G Ö still exists. G Ö and this script depends on /etc/mtree/BIND.chroot.dist file but G there is G Ö no such file in source tree. G Ö I think this file was forgotten to be removed. G Ö G Ö And also, named_* definitions still exists in /etc/defaults/rc.conf G file. G G Please review attached file that removes named from /etc. G G It would be great if the port would learn to install its own script etc. G in time for that change. (Unless it’s already there, and I’m just too blind G to see it.) G G No you are not blind. Installing bind from ports still relies on the G /etc/rc.d/named script. Erwin, can you please handle that? Things are much worse that this, the ports are completely written under the assumption that there is a Bind in base, which of course would already break with WITHOUT_BIND before Bind was completely removed. It will be hard to fix without breaking the installed base of 8 and 9. Sigh. I'll try to work on it this week, but unfortunately have a full schedule of meetings and travel as well. Erwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CURRENT] unbound: zonefiles?
On Thu, Sep 26, 2013 at 11:26:48AM +0200, O. Hartmann wrote: I try my first steps with unbound on most recent current and snealing through the web I find interesting things and howto's. But I realise if I'd like to replace my office's DNS server (based on BIND as it was part of the FreeBSD world) I run into a serious problem regarding the The unbound included in base is really only ment as a local resolver for the host only. If you want to serve machines outside localhost, it is recommended to install bind, unbound, or any other server from ports. Erwin zone- and authorative files keeping all the PTR and A records. As I can see in the unbound.conf, the statements of those files (address to name resolution, name to address resolution) is now somehow hard coded into unbound.conf via those appropriate config tags like local-zone and local-data. Since I have some larger files defining a local domain, I'd expect having a data file to be loaded. Maybe I'm wrong, eventually someone can send me short notice whether external file load is possible or not. Thanks in advance, Oliver -- Erwin Lansinghttp://droso.dk er...@freebsd.orghttp:// www.FreeBSD.org pgpv55PmLP4if.pgp Description: PGP signature
Re: make[6]: stopped in /usr/src/lib/bind/dns
On Mon, Aug 12, 2013 at 04:42:12PM -0400, AN wrote: /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c -o zone.o /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:2772:23: warning: comparison of constant 245 with expression of type 'dns_hash_t' is always false [-Wtautological-constant-out-of-range-compare] nsec3param.hash == DNS_NSEC3_UNKNOWNALG !dynamic) ~~~ ^ /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/zone.c:14682:11: warning: null character ignored [-Wnull-character] isc_time_ ^ I can't reproduce this on a stock system. Do you have any make or other environment variables set that may cause this? Erwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule
On Tue, Aug 21, 2012 at 02:43:13PM -0700, Garrett Cooper wrote: What Doug mentioned (and I don't think was really considered, but is valid) would break people that use pkg_* outside of ports. I know of at least two instances where this would be the case (one case that uses pkg_* directly, and another case that uses libpkg from pkg_* 0-o...). As to the old libpkg, it only existed for little over a year and only in HEAD and was even removed from there over a year ago, and the commit message clearly states that it should not be used. OTOH, for those using it, the only alternative for them is probably pkgng which is only now turning stable. Erwin -- Erwin Lansinghttp://droso.dk er...@freebsd.orghttp:// www.FreeBSD.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [UPDATE] Re: Update on ports on 10.0
On Fri, Oct 21, 2011 at 12:44:34PM +0300, Ion-Mihai Tetcu wrote: What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... Erwin is currently running a build on i386-10 with this and the following patches: - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@ patches) - python patch from beat - python patch from linimon - WITH_FBSD10_FIX in: - textproc/expat2 - devel/pcre - devel/libtool - audio/libogg Results by Monday. These patches have now been committed to the tree, notably with lang/python27 missing in the above list but was included as well. There have been some proposals already and we can now incrementally improve the workaround and, more importantly, start fixing individual ports. Please note that the patch tries to balance between being a general enough fix to make it easy to get a working system running while not just swiping the whole issue under the rug and forget about it until the next release cycle. Make sure to send any fixes upstream to the hack can be removed from the ports again. Thanks for all your patience and thanks for all those involved, especially beat who sent many patches and improvements. Erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Update on ports on 10.0
Since the release has been pushed back some more since the last mail, we do have some time to test a possible fix for the issues we're seeing with libtool on FreeBSD 10.0. However, fixing libtool is only part of the problem as hundreds, if not thousands, of ports roll their own detection and need to be fixed individually. We are currently running a fixed libtool (ports/161404) to assess how many ports are fixed by this patch and how many need to be patches manually before deciding how to move forward. Other options include the big find/grep/awk solution that has been posted several times and fiddling with uname to go to FreeBSD 9.99 for a while, while ports can be fixed. Hopefully, we can move forward in a day or two, but needless to say this needs a lot of testing both on 10.0 and earlier releases so we are sure we don't break backwards compatability, especially on 9.0 that is soon to be released. For those that cannot wait a few days, several patches have been proposed on the lists, of which dougb's seems most complete, so I recommend applying one of those locally. Please note that these are not tested widely and may break when the final fix is committed. To conclude with some fun facts, only 232 ports break on HEAD currently. Unfortunately, some of these are pretty high profile and prevent almost 19.000 other ports from building, leaving only slighty more than 3000 ports to build successfully. Erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Screwy behavior in ports framework
On Tue, Sep 13, 2011 at 06:57:04AM +, wrote:
I just installed FreeBSD 9.0-BETA2 last night, now I try to build ports
starting with Perl 5.14.1 (successful), then Python 2.7 fails on something
dubious, but when I try to build Lynx, ports framework can't find a directory
right under its nose. Problem is with dependency libiconv-1.13.1_1. I am
using the ports tree from BETA1, from portsnap, hence ports directory is
/BETA1/usr/ports, BETA1 being the BETA1 partition/file system. My
/etc/make.conf is
PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=workb2
# added by use.perl 2011-09-13 02:49:43
PERL_VERSION=5.14.1
Error screen shows, copied with the mouse, thanks to moused:
[snip]
=== Applying distribution patches for libiconv-1.13.1_1
patch: can't cd to workb2/libiconv-1.13.1: No such file or directory
*** Error code 1
Stop in /BETA1/usr/ports/converters/libiconv.
*** Error code 1
WKRDIR needs to be an absolute path and will break when it moves up the
tree to install dependencies. The most likely fix is to adjust the
default value ${WRKDIRPREFIX}${.CURDIR}/work to your liking, but what
you probably want is to set WRKDIRPREFIX to say /BETA1/workb2/ or
similar.
Erwin
--
Erwin Lansing http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Screwy behavior in ports framework
On Tue, Sep 13, 2011 at 09:45:05AM +, Thomas Mueller wrote:
PORTSDIR=/BETA1/usr/ports
PACKAGES=/usr/packages
WRKDIR=workb2
# added by use.perl 2011-09-13 02:49:43
PERL_VERSION=5.14.1
Maybe WRKDIR should have been ${MASTERDIR}/workb2 , or should it be
${.CURDIR}/workb2 ?
The latter. Default for WRKDIR is ${WRKDIRPREFIX}${.CURDIR}/work, so
you'll need to include ${.CURDIR} as well.
Erwin
--
Erwin Lansing http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Ports doesnt respect fetch environment settings
On Mon, Jun 21, 2010 at 11:04:16AM +0100, Tom Evans wrote: My company recently enabled proxy authentication for outgoing connections, and this has stopped ports from working. From fetch(5), I understand that I can place my proxy authentication in plain text in the environment*, and this will allow fetch to work correctly, and this does work: # env | grep -i proxy ftp_proxy=http://proxy:3128/ HTTP_PROXY_AUTH=basic:*:tev...@domain.com:password HTTP_PROXY=http://proxy:3128/ # fetch http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz googlecl-0.9.5.tar.gz 100% of 36 kB 77 MBps However, the ports makefiles seem to do something funky to my environment which hides these environment variables, and so the ports infrastructure stops working: You should use FETCH_ENV or FETCH_ARGS to pass information to fetch(1) from the ports infrastructure. It is documented in /usr/ports/Mk/bsd.port.mk, search for FETCH_BINARY. Hope that helps. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpifgXh0rQzZ.pgp Description: PGP signature
Re: Ports breakage since r205471
On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: Hi all, I realize that this is most suitable for current@ and I'm cross-posting, but I wanted to jot down all of the ports broken since the zlib version bump so that we can keep track of what's going on and what needs to be fixed. I have just started a new package build against todays HEAD on pointyhat , actually before seeing this thread, so these, and any others, will be picked up there. I'll update the list with the results when it finishes in a day or two. Also, I really think we should add packaging metadata to third party libraries in base and at least track the versioning and dependencies because this CURRENT upgrade has turned into a royal mess and has eaten up more of my time than it should have. Unfortunately, the story of ports on CuRRENT :-( -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpcMxDbzRDjq.pgp Description: PGP signature
Re: Ports breakage since r205471
On Mon, Apr 05, 2010 at 02:02:46AM -0700, Xin LI wrote: On 2010/04/05 01:50, Erwin Lansing wrote: On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote: Hi all, I realize that this is most suitable for current@ and I'm cross-posting, but I wanted to jot down all of the ports broken since the zlib version bump so that we can keep track of what's going on and what needs to be fixed. I have just started a new package build against todays HEAD on pointyhat , actually before seeing this thread, so these, and any others, will be picked up there. I'll update the list with the results when it finishes in a day or two. Which svn revision is currently using on the build cluster? Unfortunately, we're still using cvs for updating, but I just double checked that it is past r206058. The update is less than an hour old from cvs. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpxXYOcVBKqh.pgp Description: PGP signature
Re: GBDE does not recognize g partition
On Sat, Oct 25, 2003 at 06:16:40PM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Erwin Lansing writes: --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 25, 2003 at 02:07:34PM +0200, Poul-Henning Kamp wrote: =20 Can you check with diskinfo that the partition has the right size ? =20 Ok, and stupid question time: You do have GBDE in your kernel ? (Or to ask another way, is GBDE working on any other device (try a md(4) device for instance) Yup, that's what so funny about it, it works fine for the other disk: /dev/ad2s1c.bde on /stuff (ufs, local, soft-updates) -- _._ _,-'`-._ Erwin Lansing (,-.`._,'( |\`-/|[EMAIL PROTECTED] http://droso.org `-.-' \ )-`( , o o)[EMAIL PROTECTED] -bf- `-\`_`'- pgp0.pgp Description: PGP signature
GBDE does not recognize g partition
Howdy, For some reason, GBDE does not want to initialize the g partition om a disk. Am I overlooking something or is this an undocumented feature? grizzly# ls -l /dev/ad0s2g crw-r- 1 root operator4, 19 Oct 22 09:30 /dev/ad0s2g grizzly# gbde init /dev/ad0s2g -i -L /etc/gbde/ad0s1g gbde: /dev/ad0s2g: No such file or directory Cheers, -erwin -- _._ _,-'`-._ Erwin Lansing (,-.`._,'( |\`-/|[EMAIL PROTECTED] http://droso.org `-.-' \ )-`( , o o)[EMAIL PROTECTED] -bf- `-\`_`'- pgp0.pgp Description: PGP signature
Re: GBDE does not recognize g partition
On Sat, Oct 25, 2003 at 02:07:34PM +0200, Poul-Henning Kamp wrote: Can you check with diskinfo that the partition has the right size ? grizzly# diskinfo -v /dev/ad0s2g /dev/ad0s2g 512 # sectorsize 55658270720 # mediasize in bytes 108707560 # mediasize in sectors 107844 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. grizzly# disklabel ad0s2 # /dev/ad0s2: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 40960004.2BSD 2048 16384 25608 b: 2097152 409600 swap c: 1353315600unused0 0 # raw part, d: 1048576 25067524.2BSD 2048 16384 8 e: 2097152 35553284.2BSD 2048 16384 28552 f: 20971520 56524804.2BSD 2048 16384 28552 g: 108707560 26624000unused 2048 16384 -- _._ _,-'`-._ Erwin Lansing (,-.`._,'( |\`-/|[EMAIL PROTECTED] http://droso.org `-.-' \ )-`( , o o)[EMAIL PROTECTED] -bf- `-\`_`'- pgp0.pgp Description: PGP signature
Re: vinum lock panic at startup -current
On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Aaron Wohl writes: I just cvsuped -current this afternoon to get about 1 weeks updates. After that the kernel panics booting starting vinum. I removed the one vinum volume (reformated as UFS2) I had for testing. And it still panics. I changed the /etc/rc.conf start_vinum=YES to NO and can start ok now. What was the actual panic message ? Would http://people.freebsd.org/~erwin/koala.trace2 be related ? This happens after a couple of hours of activity, things are fine again after reboot (for a while) on 5-1-RELEASE. -- _._ _,-'`-._ Erwin Lansing (,-.`._,'( |\`-/|[EMAIL PROTECTED] http://droso.org `-.-' \ )-`( , o o)[EMAIL PROTECTED] -bf- `-\`_`'- pgp0.pgp Description: PGP signature
Re: Promise tx2 ata100 and Atapi-Dma
On Tue, Oct 08, 2002 at 02:32:07PM +0200, Soeren Schmidt wrote: It seems Hanspeter Roth wrote: Hello, I'm trying to run burncd on CD-RW connected via Promise TX2 ATA100 with UDMA2 (UDMA33) enabled. Reading a CD with DMA is no problem. Attempting to burn with DMA enabled hangs the system. This is the case for current as well as 4.6.2-Release. What burner is this ? (dmesg please!) Is there work in progress on this issue? Its not an issue as such, its more like a feature of some ATAPI devices I'm afraid... I'm seeing similar behaviour on 4.6.2R with only ATA devices (see dmesg at http://panda.droso.net/~erwin/valhalla.dmesg ; note that the faulty disk in the vinum array is unrelated). -erwin -- _._ _,-'`-._ Erwin Lansing (,-.`._,'( |\`-/|http://droso.org/ [EMAIL PROTECTED] `-.-' \ )-`( , o o)http://fnidder.dk/ -bf- `-\`_`'- msg44275/pgp0.pgp Description: PGP signature
