Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Jeremy Huntwork wrote: I'll be starting this now. Bugzilla will be taken offline but the data will be retained. I will keep the lists advised of my progress. Trac is up and running on belgarath, accessible via the same URLs as previous. You may need to wait for the DNS to propagate before you

nss instructions and Domainname nitpick.

2006-02-04 Thread Richard A Downing
It's not so much a valid domain name that needs to be inserted as a domain name such that host.domainname will result in a valid DNS lookup. I, for instance, have a local DNS server that recognises 109bean.org.uk (which is valid, registered, responds to whois etc..) and my host, rad1, looks up

OpenSSH 4.3p1 released

2006-02-04 Thread Tim van der Molen
OpenSSH 4.3p1 has recently been released. Besides several bug fixes one security bug has been addressed. The announcement is available at http://marc.theaimsgroup.com/?l=openbsd-announcem=113893053104991w=2. Tim -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ:

Re: trac Implementation

2006-02-04 Thread Randy McMurchy
Jeremy Huntwork wrote these words on 02/04/06 12:27 CST: I'll need your help, as well, for customizing Trac to fit our needs best. There are some adjustments or tweaks we can make to the defaults for viewing/adding Tickets, and for some other sections. Many of these can be found via the

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Randy McMurchy wrote: Were you ever able to figure anything out so that you can disable getting mail, if you desire? I didn't see anything officially implemented. You can either disable or enable sending of mail to the reporter or the owner for the entire env. Nothing on an individual basis.

Re: trac Implementation

2006-02-04 Thread Randy McMurchy
Jeremy Huntwork wrote these words on 02/04/06 12:52 CST: Randy McMurchy wrote: Were you ever able to figure anything out so that you can disable getting mail, if you desire? I didn't see anything officially implemented. You can either disable or enable sending of mail to the reporter or the

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Randy McMurchy wrote: What a shame. :-( Introductions are in order: [EMAIL PROTECTED], meet Killfile: Killfile, meet [EMAIL PROTECTED] Heh. :) -- JH -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above

Re: trac Implementation

2006-02-04 Thread Randy McMurchy
Jeremy Huntwork wrote these words on 02/04/06 12:52 CST: I didn't see anything officially implemented. You can either disable or enable sending of mail to the reporter or the owner for the entire env. Nothing on an individual basis. You know, I just thought of something. I received two emails

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Randy McMurchy wrote: You know, I just thought of something. I received two emails from the Trac system in the last half hour. Unfortunately, they have already been sent to /dev/null, or I would forward them on so you know what I was talking about. Anyway, there were no messages generated in

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Jeremy Huntwork wrote: Anyway, there were no messages generated in -book from these items. Shouldn't all items generate a message to -book? I thought I remember you saying they would. Yes, thanks. Perhaps something is misconfigured. I'll look. From my few tests, and looking at the mail logs

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Jeremy Huntwork wrote: I still have to bring over the new bugs from Bugzilla that have been added over the past week or two, so please refrain from adding anything to Trac's ticketing system yet as it will just be wiped. It is late here now and I need some sleep. I will do this tomorrow. And

Re: trac Implementation

2006-02-04 Thread Jeremy Huntwork
Jeremy Huntwork wrote: Anyway, looking forward to seeing how this will be used. Enjoy! Oh, I also meant to remind everyone that we'll need to swap out links to {blfs-,}bugs.linuxfromscratch.org to wiki.linuxfromscratch.org/[subproject] -- JH --

unzip552 and PK 2.1 Compat

2006-02-04 Thread DJ Lucas
Hello guys and gals. I have a zip file that I need to extract that unzip 5.5.2 can't handle. I don't know why but I believe the flags in the book must be expanded. I've tried a few other targets to no avail, but the resultant unzip errors on this file like so: [EMAIL PROTECTED]

Re: unzip552 and PK 2.1 Compat

2006-02-04 Thread DJ Lucas
DJ Lucas wrote: Hello guys and gals. I have a zip file that I need to extract that unzip 5.5.2 can't handle. snip http://wiki.linuxfromscratch.org/blfs/ticket/1800#preview -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ:

Re: unzip552 and PK 2.1 Compat

2006-02-04 Thread DJ Lucas
DJ Lucas wrote: Hello guys and gals. I have a zip file that I need to extract that unzip 5.5.2 can't handle. This is interesting. The problem only occurs when using the shared unzip, if not building the shared library the file uncompresses as expected. I'm still digging into it, but I

Re: unzip552 and PK 2.1 Compat

2006-02-04 Thread DJ Lucas
DJ Lucas wrote: The problem only occurs when using the shared unzip snip Okay. Scratch removing it...I've tracked it down to linking with the system libz, but have no idea how to fix it. For now, the second make target should be changed to 'linux_shlib' (if a libunzip is useful to you).