From ryandesign at macports.org Wed Dec 1 06:28:37 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Dec 2021 00:28:37 -0600 Subject: build.macports.org currently down? In-Reply-To: <97837968-9BB3-4797-916D-FF087948AF01@rochester.rr.com> References: <111470CE-79CB-4D0F-B5E5-C63E2B8D711C@macports.org> <0EB25CE7-1E34-4E98-A106-C6FFC0E4F010@macports.org> <97837968-9BB3-4797-916D-FF087948AF01@rochester.rr.com> Message-ID: <5DC1F622-01DB-4905-BA8E-0655D4C56A50@macports.org> On Nov 30, 2021, at 10:43, Christopher Nielsen wrote: > >> The RAID is fine. Buildmaster and some workers are back up. I'll work on getting the remaining workers back online tonight (in a few hours). (Each has to be checked and cleaned up manually first.) > > > Ryan, do you think we?ll be able to bring the 10.13 buildbot back online soon? > > Not an emergency by any means. But would be great to publish binaries for the current commit backlog. (Now over 200 on that builder.) After the power outage, disk verification reported a problem on that builder. I would like to repair the disk or transfer the disk contents to a new disk before resuming builds. From mascguy at rochester.rr.com Wed Dec 1 15:18:28 2021 From: mascguy at rochester.rr.com (Christopher Nielsen) Date: Wed, 1 Dec 2021 10:18:28 -0500 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI Message-ID: Just encountered an interesting situation, where a Swift-based port builds successfully via 10.15 CI, but fails on our buildbot. This appears to be related to Xcode versions: Presently our 10.15 buildbot has Xcode 11.7, whereas 10.15 CI has Xcode 12.4. This brings up two questions: * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? Or are there certain ports/situations that necessitate remaining with 11.7? * Do we have control over the Xcode version used for GitHub CI, or is 12.4 the only option? Ideally both should utilize the same Xcode 12 release, specifically one that still ships with the 10.15 SDK. So the choices would be 12.0, 12.0.1, and 12.1. Thoughts? From jonesc at hep.phy.cam.ac.uk Wed Dec 1 15:32:22 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Wed, 1 Dec 2021 15:32:22 +0000 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: References: Message-ID: <891eb34e-4802-a756-2b4f-7ec584e85e0f@hep.phy.cam.ac.uk> Hi, On 01/12/2021 3:18 pm, Christopher Nielsen wrote: > Just encountered an interesting situation, where a Swift-based port builds successfully via 10.15 CI, but fails on our buildbot. > > This appears to be related to Xcode versions: Presently our 10.15 buildbot has Xcode 11.7, whereas 10.15 CI has Xcode 12.4. > > This brings up two questions: > * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? Or are there certain ports/situations that necessitate remaining with 11.7? > * Do we have control over the Xcode version used for GitHub CI, or is 12.4 the only option? > > Ideally both should utilize the same Xcode 12 release, specifically one that still ships with the 10.15 SDK. So the choices would be 12.0, 12.0.1, and 12.1. > > Thoughts? > MacPorts cannot mandate what Xcode a user has installed. Both Xcode 11 and 12 are valid options to have on macOS10.15 (and, I might be wrong here, but from memory Ryan specifically keeps the builder on Xcode 11 to avoid issues with Xcode 12 also shipping the macOS11 SDK). So basically the port needs to handle both, in whatever way is appropriate. I guess this is the new mint port https://github.com/macports/macports-ports/commit/cfc6d01aa685a5a9cc30264bc2a7e9d1badf587e I see there is a check in there on the Darwin version. It sounds this this should be changed to a test specifically on the Xcode(CLT) versions installed, if the requirement is really Xcode 12 and above, and not really the Darwin version. Chris From jasonliu at umich.edu Wed Dec 1 17:14:26 2021 From: jasonliu at umich.edu (Jason Liu) Date: Wed, 1 Dec 2021 12:14:26 -0500 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: <891eb34e-4802-a756-2b4f-7ec584e85e0f@hep.phy.cam.ac.uk> References: <891eb34e-4802-a756-2b4f-7ec584e85e0f@hep.phy.cam.ac.uk> Message-ID: A very similar situation occurs on macOS 10.11: It's fairly common to install Xcode 8.2.1 on macOS 10.11, and Xcode 8.2.1 comes with the macOS 10.12 SDK. So, in my upcoming fixes that allows godot to compile on older macOSes, I have the following check: if {${os.platform} eq "darwin" && ${os.major} <= 15} { set sdks_dir ${developer_dir}/Platforms/MacOSX.platform/Developer/SDKs set add_appkit_wrapper yes if {![catch {file lstat $sdks_dir/MacOSX10.12.sdk finfo}]} { set add_appkit_wrapper no } } Thus, if the Portfile detects the situation of the macOS 10.12 SDK being installed on macOS 10.11, then it won't add my AppKit compatibility wrapper file. I suspect a similar technique might need to be put in place to account for Xcode 11 vs 12 being installed on macOS 10.15. -- Jason Liu On Wed, Dec 1, 2021 at 10:32 AM Chris Jones wrote: > Hi, > > On 01/12/2021 3:18 pm, Christopher Nielsen wrote: > > Just encountered an interesting situation, where a Swift-based port > builds successfully via 10.15 CI, but fails on our buildbot. > > > > This appears to be related to Xcode versions: Presently our 10.15 > buildbot has Xcode 11.7, whereas 10.15 CI has Xcode 12.4. > > > > This brings up two questions: > > * Would it be feasible to update our 10.15 buildbot to a newer Xcode > release? Or are there certain ports/situations that necessitate remaining > with 11.7? > > * Do we have control over the Xcode version used for GitHub CI, or is > 12.4 the only option? > > > > Ideally both should utilize the same Xcode 12 release, specifically one > that still ships with the 10.15 SDK. So the choices would be 12.0, 12.0.1, > and 12.1. > > > > Thoughts? > > > > MacPorts cannot mandate what Xcode a user has installed. Both Xcode 11 > and 12 are valid options to have on macOS10.15 (and, I might be wrong > here, but from memory Ryan specifically keeps the builder on Xcode 11 to > avoid issues with Xcode 12 also shipping the macOS11 SDK). > > So basically the port needs to handle both, in whatever way is > appropriate. I guess this is the new mint port > > > > https://github.com/macports/macports-ports/commit/cfc6d01aa685a5a9cc30264bc2a7e9d1badf587e > > I see there is a check in there on the Darwin version. It sounds this > this should be changed to a test specifically on the Xcode(CLT) versions > installed, if the requirement is really Xcode 12 and above, and not > really the Darwin version. > > Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Wed Dec 1 17:50:22 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Wed, 1 Dec 2021 17:50:22 +0000 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: References: <891eb34e-4802-a756-2b4f-7ec584e85e0f@hep.phy.cam.ac.uk> Message-ID: <341b3b3c-54e2-a520-85ad-b449c1b04834@hep.phy.cam.ac.uk> you are making a number of assumptions in the code below on where things are installed, that I don't think are universally valid. I think it would be better to use the macPort utilities to query the SDK version and/or Xcode version instead. Chris On 01/12/2021 5:14 pm, Jason Liu wrote: > A very similar situation occurs on macOS 10.11: It's fairly common to > install Xcode 8.2.1 on macOS 10.11, and Xcode 8.2.1 comes with the macOS > 10.12 SDK. So, in my upcoming fixes that allows godot to compile on > older macOSes, I have the following check: > > if {${os.platform} eq "darwin" && ${os.major} <= 15} { > ? ? > ? ? set sdks_dir ${developer_dir}/Platforms/MacOSX.platform/Developer/SDKs > ? ? set add_appkit_wrapper yes > ? ? if {![catch {file lstat $sdks_dir/MacOSX10.12.sdk finfo}]} { > ? ? ? ? set add_appkit_wrapper no > ? ? } > } > > Thus, if the Portfile detects the situation of the macOS 10.12 SDK being > installed on macOS 10.11, then it won't add my AppKit compatibility > wrapper file. > > I suspect a similar technique might need to be put in place to account > for Xcode 11 vs 12 being installed on macOS 10.15. > > -- > Jason ?Liu > > > On Wed, Dec 1, 2021 at 10:32 AM Chris Jones > wrote: > > Hi, > > On 01/12/2021 3:18 pm, Christopher Nielsen wrote: > > Just encountered an interesting situation, where a Swift-based > port builds successfully via 10.15 CI, but fails on our buildbot. > > > > This appears to be related to Xcode versions: Presently our 10.15 > buildbot has Xcode 11.7, whereas 10.15 CI has Xcode 12.4. > > > > This brings up two questions: > > * Would it be feasible to update our 10.15 buildbot to a newer > Xcode release? Or are there certain ports/situations that > necessitate remaining with 11.7? > > * Do we have control over the Xcode version used for GitHub CI, > or is 12.4 the only option? > > > > Ideally both should utilize the same Xcode 12 release, > specifically one that still ships with the 10.15 SDK. So the choices > would be 12.0, 12.0.1, and 12.1. > > > > Thoughts? > > > > MacPorts cannot mandate what Xcode a user has installed. Both Xcode 11 > and 12 are valid options to have on macOS10.15 (and, I might be wrong > here, but from memory Ryan specifically keeps the builder on Xcode > 11 to > avoid issues with Xcode 12 also shipping the macOS11 SDK). > > So basically the port needs to handle both, in whatever way is > appropriate. I guess this is the new mint port > > > https://github.com/macports/macports-ports/commit/cfc6d01aa685a5a9cc30264bc2a7e9d1badf587e > > > I see there is a check in there on the Darwin version. It sounds this > this should be changed to a test specifically on the Xcode(CLT) > versions > installed, if the requirement is really Xcode 12 and above, and not > really the Darwin version. > > Chris > From jasonliu at umich.edu Wed Dec 1 18:03:19 2021 From: jasonliu at umich.edu (Jason Liu) Date: Wed, 1 Dec 2021 13:03:19 -0500 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: <341b3b3c-54e2-a520-85ad-b449c1b04834@hep.phy.cam.ac.uk> References: <891eb34e-4802-a756-2b4f-7ec584e85e0f@hep.phy.cam.ac.uk> <341b3b3c-54e2-a520-85ad-b449c1b04834@hep.phy.cam.ac.uk> Message-ID: The code isn't actually mine... I simply took the code from other Portfiles, e.g. the wxWidgets 1.0 PortGroup , phantomjs-qt , qt5 , qt6 , etc. Although admittedly, the code in those Portfiles are slightly more generalized than mine, since I'm only interested in the specific case of the macOS 10.12 SDK on macOS 10.11. -- Jason Liu On Wed, Dec 1, 2021 at 12:50 PM Chris Jones wrote: > > you are making a number of assumptions in the code below on where things > are installed, that I don't think are universally valid. I think it > would be better to use the macPort utilities to query the SDK version > and/or Xcode version instead. > > Chris > > On 01/12/2021 5:14 pm, Jason Liu wrote: > > A very similar situation occurs on macOS 10.11: It's fairly common to > > install Xcode 8.2.1 on macOS 10.11, and Xcode 8.2.1 comes with the macOS > > 10.12 SDK. So, in my upcoming fixes that allows godot to compile on > > older macOSes, I have the following check: > > > > if {${os.platform} eq "darwin" && ${os.major} <= 15} { > > > > set sdks_dir > ${developer_dir}/Platforms/MacOSX.platform/Developer/SDKs > > set add_appkit_wrapper yes > > if {![catch {file lstat $sdks_dir/MacOSX10.12.sdk finfo}]} { > > set add_appkit_wrapper no > > } > > } > > > > Thus, if the Portfile detects the situation of the macOS 10.12 SDK being > > installed on macOS 10.11, then it won't add my AppKit compatibility > > wrapper file. > > > > I suspect a similar technique might need to be put in place to account > > for Xcode 11 vs 12 being installed on macOS 10.15. > > > > -- > > Jason Liu > > > > > > On Wed, Dec 1, 2021 at 10:32 AM Chris Jones > > wrote: > > > > Hi, > > > > On 01/12/2021 3:18 pm, Christopher Nielsen wrote: > > > Just encountered an interesting situation, where a Swift-based > > port builds successfully via 10.15 CI, but fails on our buildbot. > > > > > > This appears to be related to Xcode versions: Presently our 10.15 > > buildbot has Xcode 11.7, whereas 10.15 CI has Xcode 12.4. > > > > > > This brings up two questions: > > > * Would it be feasible to update our 10.15 buildbot to a newer > > Xcode release? Or are there certain ports/situations that > > necessitate remaining with 11.7? > > > * Do we have control over the Xcode version used for GitHub CI, > > or is 12.4 the only option? > > > > > > Ideally both should utilize the same Xcode 12 release, > > specifically one that still ships with the 10.15 SDK. So the choices > > would be 12.0, 12.0.1, and 12.1. > > > > > > Thoughts? > > > > > > > MacPorts cannot mandate what Xcode a user has installed. Both Xcode > 11 > > and 12 are valid options to have on macOS10.15 (and, I might be wrong > > here, but from memory Ryan specifically keeps the builder on Xcode > > 11 to > > avoid issues with Xcode 12 also shipping the macOS11 SDK). > > > > So basically the port needs to handle both, in whatever way is > > appropriate. I guess this is the new mint port > > > > > > > https://github.com/macports/macports-ports/commit/cfc6d01aa685a5a9cc30264bc2a7e9d1badf587e > > < > https://github.com/macports/macports-ports/commit/cfc6d01aa685a5a9cc30264bc2a7e9d1badf587e > > > > > > I see there is a check in there on the Darwin version. It sounds this > > this should be changed to a test specifically on the Xcode(CLT) > > versions > > installed, if the requirement is really Xcode 12 and above, and not > > really the Darwin version. > > > > Chris > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrischavez at gmx.us Wed Dec 1 23:19:36 2021 From: chrischavez at gmx.us (Christopher Chavez) Date: Thu, 2 Dec 2021 00:19:36 +0100 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: References: Message-ID: > This brings up two questions: > * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? Or are there certain ports/situations that necessitate remaining with 11.7? Xcode 12 prohibiting implicit function declarations is probably no longer a reason since these must have been resolved to support Big Sur/Monterey. > * Do we have control over the Xcode version used for GitHub CI, or is 12.4 the only option? Yes, or I thought we did. A year ago I tried adding a second 10.15 CI builder to have both Xcode 11 and Xcode 12 beta: https://github.com/macports/macports-ports/pull/8162 The important part was to run xcode-select with the path for the desired version. The available versions are listed at https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xcode However there may have been an issue where the command line tools didn?t match the selected Xcode version. Christopher A. Chavez From ryandesign at macports.org Wed Dec 1 23:33:43 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 1 Dec 2021 17:33:43 -0600 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: References: Message-ID: On Dec 1, 2021, at 09:18, Christopher Nielsen wrote: > > * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? Or are there certain ports/situations that necessitate remaining with 11.7? Because there are a variety of scenarios where a build fails if the OS version and SDK version are not the same, I deliberately keep Xcode versions on the buildbot machines* on the last version that contains the SDK version that matches the OS version. If Xcode 12 contains the macOS 10.15 SDK, I can update the 10.15 worker to it, otherwise I would not want to do that. I do have work in progress on a MacOSX.sdk port which should make it easier for ports to request any SDK on any OS. It is not committed yet. *there might be one case where I did update to a newer version; I'd have to review From greg at gpanders.com Thu Dec 2 20:24:41 2021 From: greg at gpanders.com (Gregory Anders) Date: Thu, 2 Dec 2021 20:24:41 +0000 Subject: Custom user select groups Message-ID: A feature I would personally like to see in MacPorts is the ability to create my own select groups and add arbitrary programs to it. I am happy to create a prototype PR for review, but wanted to see if this had been proposed or considered before. What I have in mind is a new subcommand to 'port select', e.g. '--add' that could be used like so: sudo port select --add GROUP TARGET OPTIONS... Presently, each port that has multiple options has to provide its own 'select' companion port. Not all ports have these and it can be tedious to create them for every port that needs it. This is especially true for Python and Lua ports that install executables: users often want to use the plain executable name without the version information which is only possible with a select group. This would also solve another personal pain point for me: the current inability to use a plain 'clangd' command installed via MacPorts. I proposed adding clangd to the clang_select group in #10558, but it was closed (for perfectly valid reasons). However, if I were able to create my own select group I could still accomplish this with no compatibility issues for the greater MacPorts project: sudo port select --add clangd clangd clangd-mp-13 sudo port select --set clangd clangd-mp-13 A similar situation exists for e.g. universal-ctags, which currently installs itself as 'uctags'. I would love to be able to create my own "ctags_select" group that allows me to use universal-ctags as plain 'ctags'. sudo port select --add ctags ctags ctags uctags sudo port select --set ctags uctags I hope the above provides enough motivation for the feature. Please let me know your thoughts. I will start work on a prototype PR if I get a positive (or at least, non-negative) response. Thanks! Greg From mark at macports.org Fri Dec 3 21:18:16 2021 From: mark at macports.org (Mark Anderson) Date: Fri, 3 Dec 2021 16:18:16 -0500 Subject: Custom user select groups In-Reply-To: References: Message-ID: I rather like this idea. I'm not sure of the complexity but it would come in handy in a number of places. ?Mark _______________________ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile On Thu, Dec 2, 2021 at 3:25 PM Gregory Anders wrote: > A feature I would personally like to see in MacPorts is the ability to > create > my own select groups and add arbitrary programs to it. I am happy to > create a > prototype PR for review, but wanted to see if this had been proposed or > considered before. > > What I have in mind is a new subcommand to 'port select', e.g. '--add' > that > could be used like so: > > sudo port select --add GROUP TARGET OPTIONS... > > Presently, each port that has multiple options has to provide its own > 'select' > companion port. Not all ports have these and it can be tedious to create > them > for every port that needs it. This is especially true for Python and Lua > ports > that install executables: users often want to use the plain executable > name > without the version information which is only possible with a select group. > > This would also solve another personal pain point for me: the current > inability > to use a plain 'clangd' command installed via MacPorts. I proposed adding > clangd to the clang_select group in #10558, but it was closed (for > perfectly > valid reasons). However, if I were able to create my own select group I > could > still accomplish this with no compatibility issues for the greater > MacPorts > project: > > sudo port select --add clangd clangd clangd-mp-13 > sudo port select --set clangd clangd-mp-13 > > A similar situation exists for e.g. universal-ctags, which currently > installs > itself as 'uctags'. I would love to be able to create my own > "ctags_select" > group that allows me to use universal-ctags as plain 'ctags'. > > sudo port select --add ctags ctags ctags uctags > sudo port select --set ctags uctags > > I hope the above provides enough motivation for the feature. Please let me > know > your thoughts. I will start work on a prototype PR if I get a positive (or > at > least, non-negative) response. > > Thanks! > > Greg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrischavez at gmx.us Mon Dec 6 01:33:32 2021 From: chrischavez at gmx.us (Christopher Chavez) Date: Mon, 6 Dec 2021 02:33:32 +0100 Subject: Requesting review/testing for PR 12595 In-Reply-To: References: Message-ID: > https://github.com/macports/macports-ports/pull/12595 This update for qt5-qtwebengine has now built successfully on Monterey (both ARM64 and x86_84). I believe it is ready for final review and merging. The port maintainer has been unavailable for review. Can a committer please take a look? Christopher A. Chavez From mark at bsdbox.org Mon Dec 6 03:12:13 2021 From: mark at bsdbox.org (Mark Jamsek) Date: Mon, 6 Dec 2021 14:12:13 +1100 Subject: [new] devel/fnc 0.6 -- like devel/tig for fossil Message-ID: *ping* https://trac.macports.org/ticket/64066 feedback/comments to improve portfile? To test: $ port install fossil $ fossil clone https://fnc.bsdbox.org $ cd fnc $ fnc portfile also attached here for convenience. -- Mark Jamsek -------------- next part -------------- A non-text attachment was scrubbed... Name: portfile Type: application/octet-stream Size: 1174 bytes Desc: not available URL: From jasonliu at umich.edu Mon Dec 6 05:22:34 2021 From: jasonliu at umich.edu (Jason Liu) Date: Mon, 6 Dec 2021 00:22:34 -0500 Subject: PR 12976: request for review and merge Message-ID: Could someone take a quick look, and if there aren't any issues, merge it? I have a series of bugfixes that are waiting for this to get merged first. https://github.com/macports/macports-ports/pull/12976 -- Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Mon Dec 6 18:09:57 2021 From: jasonliu at umich.edu (Jason Liu) Date: Mon, 6 Dec 2021 13:09:57 -0500 Subject: Remove pending builds from buildbot? Message-ID: Hi all, Would it be possible to remove the queued builds for my PR that was recently merged on the 10.13 and 12_x86_64 watchers? That PR only added an auxiliary file, and really shouldn't be re-built. Since there's such a long queue on the 10.13 and 12 builders, I'm thinking that cancelling a fairly length build that isn't needed would help clear up the backlog a bit faster. If there's an easy way to cancel the build on all of the builders (not just 10.13 and 12), that would probably be even better. On the other hand, if cancelling the build would be a hassle, then don't worry about it. The commit is identified by the hash 14e7b489f630... (Jason Liu ) -- Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Mon Dec 6 19:02:13 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 6 Dec 2021 19:02:13 +0000 Subject: Remove pending builds from buildbot? In-Reply-To: References: Message-ID: Hi, If the revision and version numbers have changed, because what is installed on disc has changed, then the builds need to be rerun, otherwise you are forcing the long builds on users, which is worse than tying up the buildbots for a while. Cheers Chris > On 6 Dec 2021, at 6:10 pm, Jason Liu wrote: > > ? > Hi all, > > Would it be possible to remove the queued builds for my PR that was recently merged on the 10.13 and 12_x86_64 watchers? That PR only added an auxiliary file, and really shouldn't be re-built. Since there's such a long queue on the 10.13 and 12 builders, I'm thinking that cancelling a fairly length build that isn't needed would help clear up the backlog a bit faster. If there's an easy way to cancel the build on all of the builders (not just 10.13 and 12), that would probably be even better. On the other hand, if cancelling the build would be a hassle, then don't worry about it. > > The commit is identified by the hash > > 14e7b489f630... > (Jason Liu ) > > -- > Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Mon Dec 6 19:34:36 2021 From: jasonliu at umich.edu (Jason Liu) Date: Mon, 6 Dec 2021 14:34:36 -0500 Subject: Remove pending builds from buildbot? In-Reply-To: References: Message-ID: Neither the revision nor the version numbers were changed in the Portfile (in fact, no changes were made to the Portfile at all), only the new file got added to the files/ folder. But builds got queued up on the buildbot anyway after the PR got merged. Adding the file to the port (PR #12976 ) was only in preparation for the PR that actually includes bugfixes (PR #13266 ), which obviously will change what is installed, and do indeed need builds to be rerun. I'm trying to get the queued builds for PR #12976 removed from the builders. -- Jason Liu On Mon, Dec 6, 2021 at 2:02 PM Chris Jones wrote: > Hi, > > If the revision and version numbers have changed, because what is > installed on disc has changed, then the builds need to be rerun, otherwise > you are forcing the long builds on users, which is worse than tying up the > buildbots for a while. > > Cheers Chris > > On 6 Dec 2021, at 6:10 pm, Jason Liu wrote: > > ? > Hi all, > > Would it be possible to remove the queued builds for my PR that was > recently merged on the 10.13 > and > 12_x86_64 watchers? > That PR only added an auxiliary file, and really shouldn't be re-built. > Since there's such a long queue on the 10.13 and 12 builders, I'm thinking > that cancelling a fairly length build that isn't needed would help clear up > the backlog a bit faster. If there's an easy way to cancel the build on all > of the builders (not just 10.13 and 12), that would probably be even > better. On the other hand, if cancelling the build would be a hassle, then > don't worry about it. > > The commit is identified by the hash > > 14e7b489f630... > (Jason Liu ) > > -- > Jason Liu > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Mon Dec 6 19:40:37 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 6 Dec 2021 19:40:37 +0000 Subject: Remove pending builds from buildbot? In-Reply-To: References: Message-ID: <1D4636F4-6E6C-445A-9C95-C171A744DBF9@hep.phy.cam.ac.uk> Normally making a commit that does not change the revision or version will not trigger a rebuild, assuming the previous port revision built OK on a given platform. If this is the case then again the builds do not need to be cancelled. If the previous builds in fact did not build, then yes another rebuild will be attempted, so if nothing has changed to fix the previous build failure it will fail again. If this is the case then its best not avoid making such commits until you are able to do so at the same times as fixing the build failures. If this cannot be done the the port should use the known_fail pattern for the OSes known to fail, to avoid needless failing rebuilds. Chris > On 6 Dec 2021, at 7:35 pm, Jason Liu wrote: > > ? > Neither the revision nor the version numbers were changed in the Portfile (in fact, no changes were made to the Portfile at all), only the new file got added to the files/ folder. But builds got queued up on the buildbot anyway after the PR got merged. > > Adding the file to the port (PR #12976) was only in preparation for the PR that actually includes bugfixes (PR #13266), which obviously will change what is installed, and do indeed need builds to be rerun. I'm trying to get the queued builds for PR #12976 removed from the builders. > > -- > Jason Liu > > >> On Mon, Dec 6, 2021 at 2:02 PM Chris Jones wrote: >> Hi, >> >> If the revision and version numbers have changed, because what is installed on disc has changed, then the builds need to be rerun, otherwise you are forcing the long builds on users, which is worse than tying up the buildbots for a while. >> >> Cheers Chris >> >>>> On 6 Dec 2021, at 6:10 pm, Jason Liu wrote: >>>> >>> ? >>> Hi all, >>> >>> Would it be possible to remove the queued builds for my PR that was recently merged on the 10.13 and 12_x86_64 watchers? That PR only added an auxiliary file, and really shouldn't be re-built. Since there's such a long queue on the 10.13 and 12 builders, I'm thinking that cancelling a fairly length build that isn't needed would help clear up the backlog a bit faster. If there's an easy way to cancel the build on all of the builders (not just 10.13 and 12), that would probably be even better. On the other hand, if cancelling the build would be a hassle, then don't worry about it. >>> >>> The commit is identified by the hash >>> >>> 14e7b489f630... >>> (Jason Liu ) >>> >>> -- >>> Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Mon Dec 6 19:52:20 2021 From: jasonliu at umich.edu (Jason Liu) Date: Mon, 6 Dec 2021 14:52:20 -0500 Subject: Remove pending builds from buildbot? In-Reply-To: <1D4636F4-6E6C-445A-9C95-C171A744DBF9@hep.phy.cam.ac.uk> References: <1D4636F4-6E6C-445A-9C95-C171A744DBF9@hep.phy.cam.ac.uk> Message-ID: The builds from the previous commit were fine, and completed successfully. If the builders are smart enough to detect that nothing was changed in the Portfile and are able to skip trying to recompile the package, then I suppose it would be fine to simply leave the build requests in the queue. -- Jason Liu On Mon, Dec 6, 2021 at 2:40 PM Chris Jones wrote: > > Normally making a commit that does not change the revision or version will > not trigger a rebuild, assuming the previous port revision built OK on a > given platform. If this is the case then again the builds do not need to be > cancelled. If the previous builds in fact did not build, then yes another > rebuild will be attempted, so if nothing has changed to fix the previous > build failure it will fail again. If this is the case then its best not > avoid making such commits until you are able to do so at the same times as > fixing the build failures. If this cannot be done the the port should use > the known_fail pattern for the OSes known to fail, to avoid needless > failing rebuilds. > > Chris > > On 6 Dec 2021, at 7:35 pm, Jason Liu wrote: > > ? > Neither the revision nor the version numbers were changed in the Portfile > (in fact, no changes were made to the Portfile at all), only the new file > got added to the files/ folder. But builds got queued up on the buildbot > anyway after the PR got merged. > > Adding the file to the port (PR #12976 > ) was only in > preparation for the PR that actually includes bugfixes (PR #13266 > ), which obviously > will change what is installed, and do indeed need builds to be rerun. I'm > trying to get the queued builds for PR #12976 removed from the builders. > > -- > Jason Liu > > > On Mon, Dec 6, 2021 at 2:02 PM Chris Jones > wrote: > >> Hi, >> >> If the revision and version numbers have changed, because what is >> installed on disc has changed, then the builds need to be rerun, otherwise >> you are forcing the long builds on users, which is worse than tying up the >> buildbots for a while. >> >> Cheers Chris >> >> On 6 Dec 2021, at 6:10 pm, Jason Liu wrote: >> >> ? >> Hi all, >> >> Would it be possible to remove the queued builds for my PR that was >> recently merged on the 10.13 >> and >> 12_x86_64 watchers? >> That PR only added an auxiliary file, and really shouldn't be re-built. >> Since there's such a long queue on the 10.13 and 12 builders, I'm thinking >> that cancelling a fairly length build that isn't needed would help clear up >> the backlog a bit faster. If there's an easy way to cancel the build on all >> of the builders (not just 10.13 and 12), that would probably be even >> better. On the other hand, if cancelling the build would be a hassle, then >> don't worry about it. >> >> The commit is identified by the hash >> >> 14e7b489f630... >> (Jason Liu ) >> >> -- >> Jason Liu >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Mon Dec 6 20:18:49 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 6 Dec 2021 20:18:49 +0000 Subject: Remove pending builds from buildbot? In-Reply-To: References: Message-ID: <89E73B00-D23B-4DCF-A115-01943FEEA49A@hep.phy.cam.ac.uk> > The builds from the previous commit were fine, and completed successfully. If the builders are smart enough to detect that nothing was changed in the Portfile and are able to skip trying to recompile the package, then I suppose it would be fine to simply leave the build requests in the queue. Yes, that is the case. > > -- > Jason Liu > > >> On Mon, Dec 6, 2021 at 2:40 PM Chris Jones wrote: >> >> Normally making a commit that does not change the revision or version will not trigger a rebuild, assuming the previous port revision built OK on a given platform. If this is the case then again the builds do not need to be cancelled. If the previous builds in fact did not build, then yes another rebuild will be attempted, so if nothing has changed to fix the previous build failure it will fail again. If this is the case then its best not avoid making such commits until you are able to do so at the same times as fixing the build failures. If this cannot be done the the port should use the known_fail pattern for the OSes known to fail, to avoid needless failing rebuilds. >> >> Chris >> >>>> On 6 Dec 2021, at 7:35 pm, Jason Liu wrote: >>>> >>> ? >>> Neither the revision nor the version numbers were changed in the Portfile (in fact, no changes were made to the Portfile at all), only the new file got added to the files/ folder. But builds got queued up on the buildbot anyway after the PR got merged. >>> >>> Adding the file to the port (PR #12976) was only in preparation for the PR that actually includes bugfixes (PR #13266), which obviously will change what is installed, and do indeed need builds to be rerun. I'm trying to get the queued builds for PR #12976 removed from the builders. >>> >>> -- >>> Jason Liu >>> >>> >>>> On Mon, Dec 6, 2021 at 2:02 PM Chris Jones wrote: >>>> Hi, >>>> >>>> If the revision and version numbers have changed, because what is installed on disc has changed, then the builds need to be rerun, otherwise you are forcing the long builds on users, which is worse than tying up the buildbots for a while. >>>> >>>> Cheers Chris >>>> >>>>>> On 6 Dec 2021, at 6:10 pm, Jason Liu wrote: >>>>>> >>>>> ? >>>>> Hi all, >>>>> >>>>> Would it be possible to remove the queued builds for my PR that was recently merged on the 10.13 and 12_x86_64 watchers? That PR only added an auxiliary file, and really shouldn't be re-built. Since there's such a long queue on the 10.13 and 12 builders, I'm thinking that cancelling a fairly length build that isn't needed would help clear up the backlog a bit faster. If there's an easy way to cancel the build on all of the builders (not just 10.13 and 12), that would probably be even better. On the other hand, if cancelling the build would be a hassle, then don't worry about it. >>>>> >>>>> The commit is identified by the hash >>>>> >>>>> 14e7b489f630... >>>>> (Jason Liu ) >>>>> >>>>> -- >>>>> Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremyhu at apple.com Tue Dec 7 07:54:16 2021 From: jeremyhu at apple.com (Jeremy Huddleston Sequoia) Date: Mon, 06 Dec 2021 23:54:16 -0800 Subject: OWL - wayland for mac In-Reply-To: <6308290.0i8Xie96A5@bola> References: <6308290.0i8Xie96A5@bola> Message-ID: <32D63BA9-1350-4028-926E-B36C5450C36F@apple.com> Yes, he let me know about the release and I was chatting with him about it. Due to the license (GPL-3), I will need to talk to legal counsel before I can do anything related to it. > On Nov 30, 2021, at 03:10, Ren? J.V. Bertin via X11-users wrote: > > FYI, > > Someone has been making progress in getting a functional Wayland on Mac. > > HTH > R. > > ------------------------------- > Forwarded message: > Date: Tuesday November 30 2021 > From: Mastodon > To: rjvbertin at gmail.com > Cc: > Subject: 1 new notification since your last visit ? > > > RJVB, > > Here is a brief summary of the messages you missed since your last visit on Aug 25, 2021, 18:37 > > * ajitsinghmalra mentioned you in: > > @bugaevc @RJVB I'm trying to use wayland for mac and cloned https://github.com/owl-compositor/wayland. Any help would be higely appreciated because I'm stuck at meson.build:83:3: ERROR: Problem encountered: SFD_CLOEXEC is needed to compile Wayland libraries** > > View: https://mastodon.technology/web/statuses/107288330557594849 > > --- > > Mastodon hosted on mastodon.technology > Change e-mail preferences: https://mastodon.technology/settings/preferences > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (X11-users at lists.apple.com) > Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org > > This email sent to jeremyhu at freedesktop.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From judaew at macports.org Fri Dec 10 20:03:05 2021 From: judaew at macports.org (Vadim-Valdis Yudaev) Date: Fri, 10 Dec 2021 22:03:05 +0200 Subject: DevOps Azure will not support macOS 10.14 as of December 10 In-Reply-To: References: Message-ID: <2BADCDF0-C82C-4CD6-BAE7-C86FC9DF0465@macports.org> This day seems to have come. See https://dev.azure.com/macports/macports-ports/_build/results?buildId=18866&view=logs&j=ca395085-040a-526b-2ce8-bdc85f692774 {{{ ##[warning]An image label with the label macOS-10.14 does not exist. ##[error]The remote provider was unable to process the request. Started: Just now Duration: 18s }}} > On Nov 25, 2021, at 04:52, Joshua Root wrote: > > On 2021-11-25 12:31 , Vadim-Valdis Yudaev wrote: >> Hi here, >> Since that DevOps Azure will not support macOS 10.14 as of December 10, it's >> worth considering bump the version to 10.15. Otherwise, we may get a broken >> check again for PRs. >>> The macOS-10.14 environment is deprecated and will be removed on December 10, >>> 2021. For more details see >>> https://devblogs.microsoft.com/devops/hosted-pipelines-image-deprecation/ > > We already have GitHub Actions for 10.15, so we might as well just drop Azure as of that date. > > - Josh From john.hoyt at gmail.com Fri Dec 10 20:17:02 2021 From: john.hoyt at gmail.com (John Hoyt) Date: Fri, 10 Dec 2021 15:17:02 -0500 Subject: Review of PR 12966 - qt-qtwebkit In-Reply-To: References: Message-ID: Hi I'd like to once again request a review of PR12966 (qt5-qtwebkitI) . It's been sitting in the queue for a while now and I'm not sure what else needs to be done to get it accepted (or if I should just close the PR and let the issues languish). I am certainly more than happy to make any corrections to the portfile and/or commit messages, but I need some guidance from the team as to what needs to be done. On Sun, Nov 21, 2021 at 8:11 AM John Hoyt wrote: > I'd like to request a review for PR12966 > (qt5-qtwebkitI) which > fixes the compile issues on Monterey (and closes track ticket 63877 > ). > > I've tested the fix to work on both Arm/x86_64 on Monterey and x86_64 on > High Sierra. > > The buildbot failures are of two varieties unrelated to the fix: timeout > issues and failure to build an unrelated qt5 subport. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Fri Dec 10 21:07:19 2021 From: jasonliu at umich.edu (Jason Liu) Date: Fri, 10 Dec 2021 16:07:19 -0500 Subject: Question about `platforms` and `${os.platform}` Message-ID: Hi everyone, A conversation in one of my PRs has brought up an interesting question that I've been wondering about for a long time. In Portfiles, whenever I've had a test for `${os.major} <= xx`, I've typically always added an additional check for darwin in the front, i.e.: if {${os.platform} eq "darwin" && ${os.major} <= xx} { I've done it that way because I basically copied what I saw from other Portfiles, and because I get gently admonished by the committers when I forget to. But I've also always wondered why it's necessary. I was under the impression that the `platforms darwin` line means that the entire Portfile is supposed to be valid only for `${os.platform} eq "darwin"`, no? (In other words, my understanding is that a line such as `platforms darwin freebsd openbsd` is meant to signify that "this Portfile is supposed to be valid for the listed platforms".) If that's not the case, then what is the purpose of `platforms darwin`? -- Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at macports.org Fri Dec 10 22:24:00 2021 From: mark at macports.org (Mark Anderson) Date: Fri, 10 Dec 2021 17:24:00 -0500 Subject: Sandbox issues with Swift Package Manager In-Reply-To: <050A5C9C-8FDE-4453-B221-D76D6236817C@gmail.com> References: <4d8e9fbb-50db-f3d7-013b-db1290fda0cf@gmail.com> <050A5C9C-8FDE-4453-B221-D76D6236817C@gmail.com> Message-ID: Ah ok , that's above my paygrade right now - I had no idea we were doing that. I've copied the dev list - I think the response will be better over there. ?Mark _______________________ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile On Fri, Dec 10, 2021 at 5:12 PM Andrew Udvare wrote: > > > On 2021-12-10, at 13:01, Mark Anderson wrote: > > > > SPM and Workspace builds need to be added to the XCode portgroup - it's > something that I've been working on for a while. > > > > I'm a little surprised the sandbox is involved at all. Is it XCode's > sandbox complaining? Or is it Terminal? Make sure the terminal has full > disk access. > > This is sandbox-exec(1) complaining. When I run the same xcodebuild > command without MacPorts the build works fine in the same terminal. > > > https://github.com/macports/macports-base/blob/master/src/port1.0/portsandbox.tcl -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Fri Dec 10 22:59:14 2021 From: jasonliu at umich.edu (Jason Liu) Date: Fri, 10 Dec 2021 17:59:14 -0500 Subject: Significant security vulnerability discovered in Log4j Message-ID: In case everyone hadn't heard the news. If anyone is running Log4j for logging on any of your web servers, you might want to read this. WIRED: 'The Internet Is On Fire' A vulnerability in the Log4j logging framework has security teams scrambling to put in a fix. -- Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From egall at gwmail.gwu.edu Sat Dec 11 18:32:15 2021 From: egall at gwmail.gwu.edu (Eric Gallager) Date: Sat, 11 Dec 2021 13:32:15 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: Message-ID: On Fri, Dec 10, 2021 at 6:00 PM Jason Liu wrote: > > In case everyone hadn't heard the news. If anyone is running Log4j for logging on any of your web servers, you might want to read this. > > WIRED: 'The Internet Is On Fire' > A vulnerability in the Log4j logging framework has security teams scrambling to put in a fix. > > -- > Jason Liu so... is there anything to do about this in MacPorts? $ port search log4j jakarta-log4j @1.2.16 (java, devel) Java logging API log4cxx @0.10.0_1 (devel) log4cxx is a port to C++ of the log4j project log4jdbc @1.1 (java) JDBC driver that can log SQL and/or JDBC calls p5-log-dispatch-config @1.40.0 (perl) Log::Dispatch::Config - Log4j for Perl p5-log-log4perl @1.540.0 (perl) Log4j implementation for Perl p5.28-log-dispatch-config @1.40.0 (perl) Log::Dispatch::Config - Log4j for Perl p5.28-log-log4perl @1.540.0 (perl) Log4j implementation for Perl p5.30-log-dispatch-config @1.40.0 (perl) Log::Dispatch::Config - Log4j for Perl p5.30-log-log4perl @1.540.0 (perl) Log4j implementation for Perl p5.32-log-dispatch-config @1.40.0 (perl) Log::Dispatch::Config - Log4j for Perl p5.32-log-log4perl @1.540.0 (perl) Log4j implementation for Perl Found 11 ports. $ port installed `port -q search log4j` The following ports are currently installed: jakarta-log4j @1.2.16_0 (active) log4jdbc @1.1_0 (active) p5.28-log-log4perl @1.540.0_0 (active) p5.30-log-log4perl @1.540.0_0 (active) p5.32-log-log4perl @1.540.0_0 (active) $ ...I don't think any of these are the same thing, are they? From jasonliu at umich.edu Sat Dec 11 19:26:12 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sat, 11 Dec 2021 14:26:12 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: Message-ID: On Sat, Dec 11, 2021 at 1:32 PM Eric Gallager wrote: > > so... is there anything to do about this in MacPorts? > There's probably nothing that can be done in terms of the MacPorts packages. It's basically dependent on upstream developers to patch anything that might be affected. It was more of a general warning to anyone on the mailing list that might be running a web server. ...I don't think any of these are the same thing, are they? > Based on my googling, jakarta-log4j is some sort of wrapper that allows Jakarta to use log4j, so it's quite possible that the jakarta-log4j package is affected. Depending on how closely the C++ port follows the original Java in the log4cxx package, it might also be affected; the same applies to the log4perl packages. -- Jason Liu On Sat, Dec 11, 2021 at 1:32 PM Eric Gallager wrote: > On Fri, Dec 10, 2021 at 6:00 PM Jason Liu wrote: > > > > In case everyone hadn't heard the news. If anyone is running Log4j for > logging on any of your web servers, you might want to read this. > > > > WIRED: 'The Internet Is On Fire' > > A vulnerability in the Log4j logging framework has security teams > scrambling to put in a fix. > > > > -- > > Jason Liu > > so... is there anything to do about this in MacPorts? > > $ port search log4j > jakarta-log4j @1.2.16 (java, devel) > Java logging API > > log4cxx @0.10.0_1 (devel) > log4cxx is a port to C++ of the log4j project > > log4jdbc @1.1 (java) > JDBC driver that can log SQL and/or JDBC calls > > p5-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.28-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.28-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.30-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.30-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.32-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.32-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > Found 11 ports. > $ port installed `port -q search log4j` > The following ports are currently installed: > jakarta-log4j @1.2.16_0 (active) > log4jdbc @1.1_0 (active) > p5.28-log-log4perl @1.540.0_0 (active) > p5.30-log-log4perl @1.540.0_0 (active) > p5.32-log-log4perl @1.540.0_0 (active) > $ > > ...I don't think any of these are the same thing, are they? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Dec 11 22:19:56 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 11 Dec 2021 16:19:56 -0600 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Dec 10, 2021, at 15:07, Jason Liu wrote: > A conversation in one of my PRs has brought up an interesting question that I've been wondering about for a long time. In Portfiles, whenever I've had a test for `${os.major} <= xx`, I've typically always added an additional check for darwin in the front, i.e.: > > if {${os.platform} eq "darwin" && ${os.major} <= xx} { > > I've done it that way because I basically copied what I saw from other Portfiles, and because I get gently admonished by the committers when I forget to. Yes, please always do that. > But I've also always wondered why it's necessary. Your Portfile could be parsed or accessed by non-Darwin operating systems. For example, before we took over server hosting duties in 2016, all of the server VMs including the one that generated the PortIndex files (except the actual macOS build machines) were running Linux; perhaps some day we will once again want to try using a server OS other than macOS for this task. There are even some users using Linux to test various things in MacPorts. We don't really expect many ports to be installable on other operating systems or for maintainers to test anything on other operating systems, but just take 2 seconds when you're writing an OS version conditional to think about what you're trying to express, and then express it, including checking os.platform. Typical forms include the one you mentioned: if {${os.platform} eq "darwin" && ${os.major} <= xx} (<, <=, ==, >=, >) And the other one: if {${os.platform} ne "darwin" || ${os.major} <= xx} (<, <=, ==, >=, >) Usually the decision about which to use comes down to whether the thing you're doing is Mac-specific or not. For example, if you were writing a conditional to use the Security framework on recent macOS and openssl on older macOS, what should happen if perchance the port is used on non-macOS? In this case, the answer is that frameworks are a Mac thing, so you would want to use openssl for non-macOS. > I was under the impression that the `platforms darwin` line means that the entire Portfile is supposed to be valid only for `${os.platform} eq "darwin"`, no? (In other words, my understanding is that a line such as `platforms darwin freebsd openbsd` is meant to signify that "this Portfile is supposed to be valid for the listed platforms".) If that's not the case, then what is the purpose of `platforms darwin`? The platforms line is not used by MacPorts in any way at this time, other than to display it in the output of "port info". There is a ticket about possibly using it in the future as a way to indicate which OS versions the port is compatible with, but I don't think that got beyond the idea phase. From jasonliu at umich.edu Sat Dec 11 22:41:44 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sat, 11 Dec 2021 17:41:44 -0500 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt wrote: > > > On Dec 10, 2021, at 15:07, Jason Liu wrote: > >> >> A conversation in one of my PRs has brought up an interesting question >> that I've been wondering about for a long time. In Portfiles, whenever I've >> had a test for `${os.major} <= xx`, I've typically always added an >> additional check for darwin in the front, i.e.: >> >> if {${os.platform} eq "darwin" && ${os.major} <= xx} { >> >> I've done it that way because I basically copied what I saw from other >> Portfiles, and because I get gently admonished by the committers when I >> forget to. > > > Yes, please always do that. Then would it be easier (or even kosher) to simply wrap the majority of the Portfile inside of a single if {${os.platform} eq "darwin"} { and be done with it, instead of needing to add one each and every time I have a conditional involving `${os.major}`? I was under the impression that the `platforms darwin` line means that the >> entire Portfile is supposed to be valid only for `${os.platform} eq >> "darwin"`, no? (In other words, my understanding is that a line such as >> `platforms darwin freebsd openbsd` is meant to signify that "this Portfile >> is supposed to be valid for the listed platforms".) If that's not the case, >> then what is the purpose of `platforms darwin`? > > > The platforms line is not used by MacPorts in any way at this time, other > than to display it in the output of "port info". There is a ticket about > possibly using it in the future as a way to indicate which OS versions the > port is compatible with, but I don't think that got beyond the idea phase. > That seems like a pity, and a bit of a waste, considering that platforms is being included in each and every Portfile. -- Jason Liu On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt wrote: > > > On Dec 10, 2021, at 15:07, Jason Liu wrote: > > > A conversation in one of my PRs has brought up an interesting question > that I've been wondering about for a long time. In Portfiles, whenever I've > had a test for `${os.major} <= xx`, I've typically always added an > additional check for darwin in the front, i.e.: > > > > if {${os.platform} eq "darwin" && ${os.major} <= xx} { > > > > I've done it that way because I basically copied what I saw from other > Portfiles, and because I get gently admonished by the committers when I > forget to. > > Yes, please always do that. > > > > But I've also always wondered why it's necessary. > > Your Portfile could be parsed or accessed by non-Darwin operating systems. > For example, before we took over server hosting duties in 2016, all of the > server VMs including the one that generated the PortIndex files (except the > actual macOS build machines) were running Linux; perhaps some day we will > once again want to try using a server OS other than macOS for this task. > There are even some users using Linux to test various things in MacPorts. > We don't really expect many ports to be installable on other operating > systems or for maintainers to test anything on other operating systems, but > just take 2 seconds when you're writing an OS version conditional to think > about what you're trying to express, and then express it, including > checking os.platform. Typical forms include the one you mentioned: > > if {${os.platform} eq "darwin" && ${os.major} <= xx} > > (<, <=, ==, >=, >) > > And the other one: > > if {${os.platform} ne "darwin" || ${os.major} <= xx} > > (<, <=, ==, >=, >) > > Usually the decision about which to use comes down to whether the thing > you're doing is Mac-specific or not. For example, if you were writing a > conditional to use the Security framework on recent macOS and openssl on > older macOS, what should happen if perchance the port is used on non-macOS? > In this case, the answer is that frameworks are a Mac thing, so you would > want to use openssl for non-macOS. > > > > I was under the impression that the `platforms darwin` line means that > the entire Portfile is supposed to be valid only for `${os.platform} eq > "darwin"`, no? (In other words, my understanding is that a line such as > `platforms darwin freebsd openbsd` is meant to signify that "this Portfile > is supposed to be valid for the listed platforms".) If that's not the case, > then what is the purpose of `platforms darwin`? > > The platforms line is not used by MacPorts in any way at this time, other > than to display it in the output of "port info". There is a ticket about > possibly using it in the future as a way to indicate which OS versions the > port is compatible with, but I don't think that got beyond the idea phase. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Dec 11 22:46:28 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 11 Dec 2021 16:46:28 -0600 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Dec 11, 2021, at 16:41, Jason Liu wrote: > Then would it be easier (or even kosher) to simply wrap the majority of the Portfile inside of a single > > if {${os.platform} eq "darwin"} { The shorthand way to do that is: platform darwin { > and be done with it, instead of needing to add one each and every time I have a conditional involving `${os.major}`? I wouldn't expect you to need to write more than a couple such conditionals in a portfile so I wouldn't expect it to be that inconvenient. We use platform darwin blocks to isolate things that are obviously Mac-specific. It would be odd to see such a block enclosing most of a portfile, even bits which are obviously not Mac-specific. >> The platforms line is not used by MacPorts in any way at this time, other than to display it in the output of "port info". There is a ticket about possibly using it in the future as a way to indicate which OS versions the port is compatible with, but I don't think that got beyond the idea phase. > > That seems like a pity, and a bit of a waste, considering that platforms is being included in each and every Portfile. Well, it's as much a pity as any unimplemented feature in MacPorts. Josh did recently commit "darwin" as a default for platforms, so it is no longer mandatory to explicitly put a platforms line in each portfile. From jonesc at hep.phy.cam.ac.uk Sat Dec 11 23:41:42 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Sat, 11 Dec 2021 23:41:42 +0000 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: > On 11 Dec 2021, at 10:42 pm, Jason Liu wrote: > > ? >> On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt wrote: >> >> >>> On Dec 10, 2021, at 15:07, Jason Liu wrote: >>> >>> A conversation in one of my PRs has brought up an interesting question that I've been wondering about for a long time. In Portfiles, whenever I've had a test for `${os.major} <= xx`, I've typically always added an additional check for darwin in the front, i.e.: >>> >>> if {${os.platform} eq "darwin" && ${os.major} <= xx} { >>> >>> I've done it that way because I basically copied what I saw from other Portfiles, and because I get gently admonished by the committers when I forget to. >> >> Yes, please always do that. > > > Then would it be easier (or even kosher) to simply wrap the majority of the Portfile inside of a single > > if {${os.platform} eq "darwin"} { > > and be done with it, instead of needing to add one each and every time I have a conditional involving `${os.major}`? No, because that would render the port non functional on non darwin OSes. You should only specify the darwin platform when it is actually required, e.g. when then making a os.major conditional that inly makes sense in darwin platforms. So basically, following the recommendations as currently given. Chris > >>> I was under the impression that the `platforms darwin` line means that the entire Portfile is supposed to be valid only for `${os.platform} eq "darwin"`, no? (In other words, my understanding is that a line such as `platforms darwin freebsd openbsd` is meant to signify that "this Portfile is supposed to be valid for the listed platforms".) If that's not the case, then what is the purpose of `platforms darwin`? >> >> The platforms line is not used by MacPorts in any way at this time, other than to display it in the output of "port info". There is a ticket about possibly using it in the future as a way to indicate which OS versions the port is compatible with, but I don't think that got beyond the idea phase. > > That seems like a pity, and a bit of a waste, considering that platforms is being included in each and every Portfile. > > -- > Jason Liu > > >> On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt wrote: >> >> >> On Dec 10, 2021, at 15:07, Jason Liu wrote: >> >> > A conversation in one of my PRs has brought up an interesting question that I've been wondering about for a long time. In Portfiles, whenever I've had a test for `${os.major} <= xx`, I've typically always added an additional check for darwin in the front, i.e.: >> > >> > if {${os.platform} eq "darwin" && ${os.major} <= xx} { >> > >> > I've done it that way because I basically copied what I saw from other Portfiles, and because I get gently admonished by the committers when I forget to. >> >> Yes, please always do that. >> >> >> > But I've also always wondered why it's necessary. >> >> Your Portfile could be parsed or accessed by non-Darwin operating systems. For example, before we took over server hosting duties in 2016, all of the server VMs including the one that generated the PortIndex files (except the actual macOS build machines) were running Linux; perhaps some day we will once again want to try using a server OS other than macOS for this task. There are even some users using Linux to test various things in MacPorts. We don't really expect many ports to be installable on other operating systems or for maintainers to test anything on other operating systems, but just take 2 seconds when you're writing an OS version conditional to think about what you're trying to express, and then express it, including checking os.platform. Typical forms include the one you mentioned: >> >> if {${os.platform} eq "darwin" && ${os.major} <= xx} >> >> (<, <=, ==, >=, >) >> >> And the other one: >> >> if {${os.platform} ne "darwin" || ${os.major} <= xx} >> >> (<, <=, ==, >=, >) >> >> Usually the decision about which to use comes down to whether the thing you're doing is Mac-specific or not. For example, if you were writing a conditional to use the Security framework on recent macOS and openssl on older macOS, what should happen if perchance the port is used on non-macOS? In this case, the answer is that frameworks are a Mac thing, so you would want to use openssl for non-macOS. >> >> >> > I was under the impression that the `platforms darwin` line means that the entire Portfile is supposed to be valid only for `${os.platform} eq "darwin"`, no? (In other words, my understanding is that a line such as `platforms darwin freebsd openbsd` is meant to signify that "this Portfile is supposed to be valid for the listed platforms".) If that's not the case, then what is the purpose of `platforms darwin`? >> >> The platforms line is not used by MacPorts in any way at this time, other than to display it in the output of "port info". There is a ticket about possibly using it in the future as a way to indicate which OS versions the port is compatible with, but I don't think that got beyond the idea phase. >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Sun Dec 12 00:42:29 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sat, 11 Dec 2021 19:42:29 -0500 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Sat, Dec 11, 2021 at 5:46 PM Ryan Schmidt wrote: > On Dec 11, 2021, at 16:41, Jason Liu wrote: > >> >> and be done with it, instead of needing to add one each and every time I >> have a conditional involving `${os.major}`? > > > I wouldn't expect you to need to write more than a couple such > conditionals in a portfile so I wouldn't expect it to be that inconvenient. Actually, I find myself needing to use them more and more. For example, I now often have to check for macOS < 10.12, due to the large overhaul that happened in AppKit between 10.11 and 10.12. My workarounds for older versions of macOS are contained inside those `if {${os.major} <= 15}` conditionals. Josh did recently commit "darwin" as a default for platforms, so it is no > longer mandatory to explicitly put a platforms line in each portfile. > Does this mean that we can start removing `platforms darwin` from our portfiles? Or is it one of those "despite the fact that it's a default, you have to put it in the file anyway"? -- Jason Liu On Sat, Dec 11, 2021 at 5:46 PM Ryan Schmidt wrote: > On Dec 11, 2021, at 16:41, Jason Liu wrote: > > > Then would it be easier (or even kosher) to simply wrap the majority of > the Portfile inside of a single > > > > if {${os.platform} eq "darwin"} { > > The shorthand way to do that is: > > platform darwin { > > > > and be done with it, instead of needing to add one each and every time I > have a conditional involving `${os.major}`? > > I wouldn't expect you to need to write more than a couple such > conditionals in a portfile so I wouldn't expect it to be that inconvenient. > > We use platform darwin blocks to isolate things that are obviously > Mac-specific. It would be odd to see such a block enclosing most of a > portfile, even bits which are obviously not Mac-specific. > > > >> The platforms line is not used by MacPorts in any way at this time, > other than to display it in the output of "port info". There is a ticket > about possibly using it in the future as a way to indicate which OS > versions the port is compatible with, but I don't think that got beyond the > idea phase. > > > > That seems like a pity, and a bit of a waste, considering that platforms > is being included in each and every Portfile. > > Well, it's as much a pity as any unimplemented feature in MacPorts. > > Josh did recently commit "darwin" as a default for platforms, so it is no > longer mandatory to explicitly put a platforms line in each portfile. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasonliu at umich.edu Sun Dec 12 00:54:18 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sat, 11 Dec 2021 19:54:18 -0500 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Sat, Dec 11, 2021 at 6:41 PM Chris Jones wrote: > No, because that would render the port non functional on non darwin OSes. > You should only specify the darwin platform when it is actually required, > e.g. when then making a os.major conditional that inly makes sense in > darwin platforms. > Wait a minute, didn't Ryan say that "We don't really expect many ports to be installable on other operating systems or for maintainers to test anything on other operating systems"? So we *should* worry about the port being non-functional on non-Darwin OSes? I'm confused now.... That's why I originally thought that `platforms darwin` implied that the portfile was only intended to be valid on Darwin. Now that I've learned that `platforms darwin` doesn't actually do anything, I'm just... confused. -- Jason Liu On Sat, Dec 11, 2021 at 6:41 PM Chris Jones wrote: > > > On 11 Dec 2021, at 10:42 pm, Jason Liu wrote: > > ? > On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt > wrote: > >> >> >> On Dec 10, 2021, at 15:07, Jason Liu wrote: >> >>> >>> A conversation in one of my PRs has brought up an interesting question >>> that I've been wondering about for a long time. In Portfiles, whenever I've >>> had a test for `${os.major} <= xx`, I've typically always added an >>> additional check for darwin in the front, i.e.: >>> >>> if {${os.platform} eq "darwin" && ${os.major} <= xx} { >>> >>> I've done it that way because I basically copied what I saw from other >>> Portfiles, and because I get gently admonished by the committers when I >>> forget to. >> >> >> Yes, please always do that. > > > Then would it be easier (or even kosher) to simply wrap the majority of > the Portfile inside of a single > > if {${os.platform} eq "darwin"} { > > and be done with it, instead of needing to add one each and every time I > have a conditional involving `${os.major}`? > > > No, because that would render the port non functional on non darwin OSes. > You should only specify the darwin platform when it is actually required, > e.g. when then making a os.major conditional that inly makes sense in > darwin platforms. > > So basically, following the recommendations as currently given. > > Chris > > > I was under the impression that the `platforms darwin` line means that the >>> entire Portfile is supposed to be valid only for `${os.platform} eq >>> "darwin"`, no? (In other words, my understanding is that a line such as >>> `platforms darwin freebsd openbsd` is meant to signify that "this Portfile >>> is supposed to be valid for the listed platforms".) If that's not the case, >>> then what is the purpose of `platforms darwin`? >> >> >> The platforms line is not used by MacPorts in any way at this time, other >> than to display it in the output of "port info". There is a ticket about >> possibly using it in the future as a way to indicate which OS versions the >> port is compatible with, but I don't think that got beyond the idea phase. >> > > That seems like a pity, and a bit of a waste, considering that platforms > is being included in each and every Portfile. > > -- > Jason Liu > > > On Sat, Dec 11, 2021 at 5:20 PM Ryan Schmidt > wrote: > >> >> >> On Dec 10, 2021, at 15:07, Jason Liu wrote: >> >> > A conversation in one of my PRs has brought up an interesting question >> that I've been wondering about for a long time. In Portfiles, whenever I've >> had a test for `${os.major} <= xx`, I've typically always added an >> additional check for darwin in the front, i.e.: >> > >> > if {${os.platform} eq "darwin" && ${os.major} <= xx} { >> > >> > I've done it that way because I basically copied what I saw from other >> Portfiles, and because I get gently admonished by the committers when I >> forget to. >> >> Yes, please always do that. >> >> >> > But I've also always wondered why it's necessary. >> >> Your Portfile could be parsed or accessed by non-Darwin operating >> systems. For example, before we took over server hosting duties in 2016, >> all of the server VMs including the one that generated the PortIndex files >> (except the actual macOS build machines) were running Linux; perhaps some >> day we will once again want to try using a server OS other than macOS for >> this task. There are even some users using Linux to test various things in >> MacPorts. We don't really expect many ports to be installable on other >> operating systems or for maintainers to test anything on other operating >> systems, but just take 2 seconds when you're writing an OS version >> conditional to think about what you're trying to express, and then express >> it, including checking os.platform. Typical forms include the one you >> mentioned: >> >> if {${os.platform} eq "darwin" && ${os.major} <= xx} >> >> (<, <=, ==, >=, >) >> >> And the other one: >> >> if {${os.platform} ne "darwin" || ${os.major} <= xx} >> >> (<, <=, ==, >=, >) >> >> Usually the decision about which to use comes down to whether the thing >> you're doing is Mac-specific or not. For example, if you were writing a >> conditional to use the Security framework on recent macOS and openssl on >> older macOS, what should happen if perchance the port is used on non-macOS? >> In this case, the answer is that frameworks are a Mac thing, so you would >> want to use openssl for non-macOS. >> >> >> > I was under the impression that the `platforms darwin` line means that >> the entire Portfile is supposed to be valid only for `${os.platform} eq >> "darwin"`, no? (In other words, my understanding is that a line such as >> `platforms darwin freebsd openbsd` is meant to signify that "this Portfile >> is supposed to be valid for the listed platforms".) If that's not the case, >> then what is the purpose of `platforms darwin`? >> >> The platforms line is not used by MacPorts in any way at this time, other >> than to display it in the output of "port info". There is a ticket about >> possibly using it in the future as a way to indicate which OS versions the >> port is compatible with, but I don't think that got beyond the idea phase. >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Sun Dec 12 08:02:47 2021 From: jmr at macports.org (Joshua Root) Date: Sun, 12 Dec 2021 19:02:47 +1100 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: <269cf0f6-66f1-49fb-c9b8-1582b40f0364@macports.org> On 2021-12-12 11:54 , Jason Liu wrote: > On Sat, Dec 11, 2021 at 6:41 PM Chris Jones > wrote: > > No, because that would render the port non functional on non darwin > OSes. You should only specify the darwin platform when it is > actually required, e.g. when then making a os.major conditional that > inly makes sense in darwin platforms. > > > Wait a minute, didn't Ryan say that "We don't really expect many ports > to be installable on other operating systems or for maintainers to test > anything on other operating systems"? So we /should/ worry about the > port being non-functional on non-Darwin OSes? I'm confused now.... Ports need to be "functional" on non-darwin platforms to the extent that things like portindex, 'port mirror', and 'port info' work. They don't need to be actually installable. > That's why I originally thought that `platforms darwin` implied that the > portfile was only intended to be valid on Darwin. Now that I've learned > that `platforms darwin` doesn't actually do anything, I'm just... confused. It means the port is expected to only be installable on darwin. Ports need to be more or less "valid" anywhere. The platforms option "doesn't actually do anything" in precisely the same way that statement is true for the description, i.e. what it does is simply make that information known to users. - Josh From nils at breun.nl Sun Dec 12 09:02:01 2021 From: nils at breun.nl (Nils Breunese) Date: Sun, 12 Dec 2021 10:02:01 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: Message-ID: Eric Gallager wrote: > ?On Fri, Dec 10, 2021 at 6:00 PM Jason Liu wrote: >> >> In case everyone hadn't heard the news. If anyone is running Log4j for logging on any of your web servers, you might want to read this. >> >> WIRED: 'The Internet Is On Fire' >> A vulnerability in the Log4j logging framework has security teams scrambling to put in a fix. >> >> -- >> Jason Liu > > so... is there anything to do about this in MacPorts? > > $ port search log4j > jakarta-log4j @1.2.16 (java, devel) > Java logging API > > log4cxx @0.10.0_1 (devel) > log4cxx is a port to C++ of the log4j project > > log4jdbc @1.1 (java) > JDBC driver that can log SQL and/or JDBC calls > > p5-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.28-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.28-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.30-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.30-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > p5.32-log-dispatch-config @1.40.0 (perl) > Log::Dispatch::Config - Log4j for Perl > > p5.32-log-log4perl @1.540.0 (perl) > Log4j implementation for Perl > > Found 11 ports. > $ port installed `port -q search log4j` > The following ports are currently installed: > jakarta-log4j @1.2.16_0 (active) > log4jdbc @1.1_0 (active) > p5.28-log-log4perl @1.540.0_0 (active) > p5.30-log-log4perl @1.540.0_0 (active) > p5.32-log-log4perl @1.540.0_0 (active) > $ > > ...I don't think any of these are the same thing, are they? I?m a Java developer and MacPorts OpenJDK maintainer and to me none of these ports look related to Log4J 2.x, which is the vulnerable library. It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. Nils. From jmr at macports.org Sun Dec 12 09:57:14 2021 From: jmr at macports.org (Joshua Root) Date: Sun, 12 Dec 2021 20:57:14 +1100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: Message-ID: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> On 2021-12-12 20:02 , Nils Breunese wrote: > It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. Not all ports have installed file information available, but the web app can search the ones that do: - Josh From nils at breun.nl Sun Dec 12 12:36:34 2021 From: nils at breun.nl (Nils Breunese) Date: Sun, 12 Dec 2021 13:36:34 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> Message-ID: <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> Joshua Root wrote: > On 2021-12-12 20:02 , Nils Breunese wrote: >> It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. > > Not all ports have installed file information available, but the web app can search the ones that do: > > I?ve locally installed those five ports and found two ports that come with vulnerable versions of Log4J 2.x: 1. apache-solr8 8.9.0_0 includes log4j-core-2.13.2.jar, which is a vulnerable version of Log4J 2.x https://github.com/apache/solr/pull/454#issuecomment-991066278 says: "Just open your solr.in.sh in your favorite editor and add SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true". Restart Solr. Done, all safe.? This could be added in /opt/local/share/java/solr-8.9.0/bin/solr.in.sh. 2. elasticsearch 7.15.2_0 includes log4j-core-2.11.1.jar, which is a vulnerable version of Log4J 2.x https://github.com/elastic/elasticsearch/issues/81618 says: "This can be mitigated for the time being by adding -Dlog4j2.formatMsgNoLookups=true to ES_JAVA_OPTS". I think I?d add -Dlog4j2.formatMsgNoLookups=true in /opt/local/etc/elasticsearch/jvm.options, or add ES_JAVA_OPTS="$ES_JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true" at the end of /opt/local/bin/elasticsearch-env. The other three ports (gradle, mvnd, NetBeans) do not include Log4J 2.x. The vulnerability can generally be mitigated by setting the system property log4j2.formatMsgNoLookups to true (e.g. by passing -Dlog4j2.formatMsgNoLookups=true to a java startup command), or by setting the LOG4J_FORMAT_MSG_NO_LOOKUPS environment variable to true. For versions of Log4J 2.x older than these properties are not read yet. In that case you might want to delete the JndiLookup class from the log4j-core file: zip -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class Nils. From nils at breun.nl Sun Dec 12 12:42:44 2021 From: nils at breun.nl (Nils Breunese) Date: Sun, 12 Dec 2021 13:42:44 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> Message-ID: <9DA9F298-40D0-4A85-9B10-946810CCD1B3@breun.nl> Nils Breunese wrote: > For versions of Log4J 2.x older than these properties are not read yet. (?) I meant to write: For versions of Log4J 2.x older than *2.10* these properties are not read yet, so you can?t use the properties to mitigate the vulnerability if you?re using Log4J < 2.10. Nils. From mascguy at rochester.rr.com Sun Dec 12 13:51:39 2021 From: mascguy at rochester.rr.com (Christopher Nielsen) Date: Sun, 12 Dec 2021 08:51:39 -0500 Subject: 10.15 Xcode version: Buildbot, vs. GitHub CI In-Reply-To: References: Message-ID: <7F81F8B7-D549-46E4-A70A-9B47984A58AE@rochester.rr.com> > On 2021-12-01-W, at 18:33, Ryan Schmidt wrote: > >> On Dec 1, 2021, at 09:18, Christopher Nielsen wrote: >> >> * Would it be feasible to update our 10.15 buildbot to a newer Xcode release? Or are there certain ports/situations that necessitate remaining with 11.7? > > Because there are a variety of scenarios where a build fails if the OS version and SDK version are not the same, I deliberately keep Xcode versions on the buildbot machines* on the last version that contains the SDK version that matches the OS version. If Xcode 12 contains the macOS 10.15 SDK, I can update the 10.15 worker to it, otherwise I would not want to do that. > > I do have work in progress on a MacOSX.sdk port which should make it easier for ports to request any SDK on any OS. It is not committed yet. > > *there might be one case where I did update to a newer version; I'd have to review I find the following very helpful, as it provides a succinct matrix relative to Xcode version vs. included macOS SDK: https://xcodereleases.com/ The site also provides direct links to the readme for each Xcode release, allowing one to quickly verify that their info matches with Apple?s. In any case, per that site (and Apple?s readmes), Xcode 12.0, 12.0.1, and 12.1 all ship with the macOS 10.15 SDK. So we can choose any one of those for the 10.15 buildbot. Perhaps 12.1 might be a good choice, in terms of having the latest bug fixes, etc? -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve.t.smith at gmail.com Sun Dec 12 15:39:12 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Sun, 12 Dec 2021 10:39:12 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> Message-ID: Please see: https://github.com/macports/macports-ports/pull/13322 > On Dec 12, 2021, at 7:36 AM, Nils Breunese wrote: > > https://github.com/apache/solr/pull/454#issuecomment-991066278 says: "Just open your solr.in.sh in your favorite editor and add SOLR_OPTS="$SOLR_OPTS -Dlog4j2.formatMsgNoLookups=true". Restart Solr. Done, all safe.? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3898 bytes Desc: not available URL: From egall at gwmail.gwu.edu Sun Dec 12 18:03:43 2021 From: egall at gwmail.gwu.edu (Eric Gallager) Date: Sun, 12 Dec 2021 13:03:43 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> Message-ID: On Sun, Dec 12, 2021 at 4:57 AM Joshua Root wrote: > > On 2021-12-12 20:02 , Nils Breunese wrote: > > It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. > > Not all ports have installed file information available, but the web app > can search the ones that do: > > > > - Josh Some other ports with log4j-related files that don't show up in this search: spring-framework25 +with_libs (from the 1.x series, so it's safe), slf4j (just docs, so it's safe), log4jdbc (also old, and possibly a spurious string match, so probably also safe), duck (1.x series, so it's safe), apache-ant (not seeing version info, I dunno), apache-geode (this one might actually need checking?), appengine-java-sdk (not sure), ghidra (this one looks vulnerable), poi (1.x series, so it's safe), webtoolkit-java-sdk (I dunno), zanata-cli (1.x series, so it's safe), and commons-logging (doesn't even build). I'll attach the output of `locate /opt/local/*log4j* | xargs port provides` to this email so you can see the same list I was looking at. -------------- next part -------------- /opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/ansible_collections/community/windows/tests/integration/targets/win_xml/files/log4j.xml is provided by: py39-ansible /opt/local/include/dcmtk/oflog/log4judp.h is provided by: dcmtk /opt/local/libexec/boost/1.76/share/doc/boost176/libs/log/doc/html/log/rationale/why_not_log4j.html is provided by: boost176 /opt/local/libexec/boost/1.77/share/doc/boost177/libs/log/doc/html/log/rationale/why_not_log4j.html is provided by: boost177 /opt/local/libexec/duck/duck.bundle/Contents/Resources/log4j-1.2.17.jar is provided by: duck /opt/local/libexec/duck/duck.bundle/Contents/Resources/slf4j-log4j12-1.7.30.jar is provided by: duck /opt/local/share/doc/dcmtk/html/log4judp_8h.html is provided by: dcmtk /opt/local/share/doc/jakarta-log4j is a directory. /opt/local/share/doc/jakarta-log4j/LICENSE is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/NOTICE is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/api is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs is a directory. /opt/local/share/doc/jakarta-log4j/contribs/CONTENTS is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/CekiGulcu is a directory. /opt/local/share/doc/jakarta-log4j/contribs/CekiGulcu/AppenderTable.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/CekiGulcu/Transform.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/EirikLygre is a directory. /opt/local/share/doc/jakarta-log4j/contribs/EirikLygre/DailyFileAppender1.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/EirikLygre/mail-2001-01-18 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JamesHouse is a directory. /opt/local/share/doc/jakarta-log4j/contribs/JamesHouse/LogTextPanel.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JamesHouse/LogTextPanelExample.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JamesHouse/TextPanelAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JamesHouse/mail-2001-01-23 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/Jamie does not exist. /Users/ericgallager/Documents/GitHub/macstrop/Tsao does not exist. /opt/local/share/doc/jakarta-log4j/contribs/Jamie does not exist. /Users/ericgallager/Documents/GitHub/macstrop/Tsao/JMSQueueAppender.java does not exist. /opt/local/share/doc/jakarta-log4j/contribs/Jamie does not exist. /Users/ericgallager/Documents/GitHub/macstrop/Tsao/mail-2001-06-20 does not exist. /opt/local/share/doc/jakarta-log4j/contribs/JimMoore is a directory. /opt/local/share/doc/jakarta-log4j/contribs/JimMoore/LoggingOutputStream.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JimMoore/mail-2001-03-12T1326 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JimMoore/mail-2001-03-12T1454 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/JimMoore/mail-2001-03-13T0646 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KevinSteppe is a directory. /opt/local/share/doc/jakarta-log4j/contribs/KevinSteppe/CompositeRollingAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KevinSteppe/JDBCTest.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KevinSteppe/mail-2001-02-01 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KevinSteppe/mail-2002-03-27.txt is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon is a directory. /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/DatagramStringAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/DatagramStringWriter.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/SingleLineTracerPrintWriter.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/logconfig.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/mail-2001-02-07 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/KitchingSimon/udpserver.pl is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/LeosLiterak is a directory. /opt/local/share/doc/jakarta-log4j/contribs/LeosLiterak/TempFileAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/LeosLiterak/mail is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/MarkDouglas is a directory. /opt/local/share/doc/jakarta-log4j/contribs/MarkDouglas/Log.txt is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/MarkDouglas/SocketNode2.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/MarkDouglas/SocketServer2.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/MarkDouglas/mail-2001-01-17 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers is a directory. /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui is a directory. /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui/JListView.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui/JTableAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui/TextPaneAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui/examples is a directory. /opt/local/share/doc/jakarta-log4j/contribs/SvenReimers/gui/examples/TextPaneAppenderExample.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner is a directory. /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/JDBCAppender.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/JDBCConnectionHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/JDBCIDHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/JDBCLogger.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/Log4JTest.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/code_example1.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/code_example2.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/ThomasFenner/configfile_example.txt is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner is a directory. /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/HTTPRequestHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/Log4jRequestHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/PluggableHTTPServer.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/RootRequestHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/UserDialogRequestHandler.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/contribs/VolkerMentzner/mail-03-05-2001 is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples is a directory. /opt/local/share/doc/jakarta-log4j/examples/MyPatternLayout.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/MyPatternParser.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/NumberCruncher.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/NumberCruncherClient.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/NumberCruncherServer.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/Sort.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/SortAlgo.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/Trivial.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/customLevel is a directory. /opt/local/share/doc/jakarta-log4j/examples/customLevel/XLevel.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/factor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/factor.lcf is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5 is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingDefaultConfigurator is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingDefaultConfigurator/InitUsingDefaultConfigurator.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingLog4JProperties is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingLog4JProperties/InitUsingLog4JProperties.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingLog4JProperties/log4j.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingMultipleAppenders is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingMultipleAppenders/InitUsingMultipleAppenders.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingMultipleAppenders/example.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingPropertiesFile is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingPropertiesFile/InitUsingPropertiesFile.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingPropertiesFile/example.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingXMLPropertiesFile is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingXMLPropertiesFile/InitUsingXMLPropertiesFile.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/InitUsingXMLPropertiesFile/example.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingLogMonitorAdapter is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingLogMonitorAdapter/CustomizedLogLevels.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingLogMonitorAdapter/UsingLogMonitorAdapter.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingSocketAppenders is a directory. /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingSocketAppenders/UsingSocketAppenders.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingSocketAppenders/socketclient.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/UsingSocketAppenders/socketserver.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/lf5/index.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/mycat.bad is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/mycat.good is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/package.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/sort1.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/sort2.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/sort3.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/sort4.properties is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/subclass is a directory. /opt/local/share/doc/jakarta-log4j/examples/subclass/MyLogger.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/subclass/MyLoggerFactory.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/examples/subclass/MyLoggerTest.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/allclasses-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/allclasses-noframe.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/constant-values.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/deprecated-list.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/help-doc.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/index-all.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/index.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/options is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/AppenderSkeleton.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/AsyncAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/BasicConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Category.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/ConsoleAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/DailyRollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/DefaultThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/EnhancedPatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/EnhancedThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/FileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/HTMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Hierarchy.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Layout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Level.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/LogMF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/LogManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/LogSF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/LogXF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Logger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/MDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/NDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/PatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/Priority.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/PropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/RollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/SimpleLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/TTCCLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/WriterAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/Main.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/class-use/Main.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/doc-files is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/doc-files/screen_01.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/chainsaw/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/AppenderSkeleton.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/AsyncAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/BasicConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Category.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/ConsoleAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/DailyRollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/DefaultThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/EnhancedPatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/EnhancedThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/FileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/HTMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Hierarchy.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Layout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Level.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/LogMF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/LogManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/LogSF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/LogXF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Logger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/MDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/NDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/PatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/Priority.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/PropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/RollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/SimpleLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/TTCCLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/class-use/WriterAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/PropertyGetter.PropertyCallback.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/PropertyGetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/PropertyPrinter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/PropertySetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/PropertySetterException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use/PropertyGetter.PropertyCallback.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use/PropertyGetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use/PropertyPrinter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use/PropertySetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/class-use/PropertySetterException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/config/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/AbsoluteTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/AppenderAttachableImpl.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/BoundedFIFO.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/CountingQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/CyclicBuffer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/DateLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/DateTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/FileWatchdog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/ISO8601DateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/Loader.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/LogLog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/MDCKeySetExtractor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/NullEnumeration.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/OnlyOnceErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/OptionConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/QuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/RelativeTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/SyslogQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/SyslogWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/ThreadLocalMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/Transform.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/AbsoluteTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/AppenderAttachableImpl.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/BoundedFIFO.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/CountingQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/CyclicBuffer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/DateLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/DateTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/FileWatchdog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/ISO8601DateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/Loader.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/LogLog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/MDCKeySetExtractor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/NullEnumeration.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/OnlyOnceErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/OptionConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/QuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/RelativeTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/SyslogQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/SyslogWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/ThreadLocalMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/class-use/Transform.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/helpers/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/JDBCAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/class-use/JDBCAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jdbc/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/AbstractDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/Agent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/AppenderDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/HierarchyDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/LayoutDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/LoggerDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/AbstractDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/Agent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/AppenderDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/HierarchyDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/LayoutDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/class-use/LoggerDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/jmx/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5 is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/AppenderFinalizer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/DefaultLF5Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/LF5Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/Log4JLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/LogLevel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/LogLevelFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/LogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/LogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/PassingLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/StartLogFactor5.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/AppenderFinalizer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/DefaultLF5Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/LF5Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/Log4JLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/LogLevel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/LogLevelFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/LogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/LogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/PassingLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/class-use/StartLogFactor5.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/AdapterLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/DateFormatManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/LogFileParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/LogMonitorAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/Resource.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/ResourceUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/StreamUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/AdapterLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/DateFormatManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/LogFileParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/LogMonitorAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/Resource.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/ResourceUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/class-use/StreamUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/util/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/FilteredLogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LF5SwingUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogBrokerMonitor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogFactor5Dialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogFactor5ErrorDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogFactor5InputDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogFactor5LoadingDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogTable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogTableColumn.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogTableColumnFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/LogTableRowRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/TrackingAdjustmentListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryAbstractCellEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryElement.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerTree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryImmediateEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeEditorRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryPath.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/TreeModelAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryAbstractCellEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryElement.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryExplorerLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryExplorerModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryExplorerTree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryImmediateEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryNodeEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryNodeEditorRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryNodeRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/CategoryPath.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/class-use/TreeModelAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/categoryexplorer/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/FilteredLogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LF5SwingUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogBrokerMonitor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogFactor5Dialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogFactor5ErrorDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogFactor5InputDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogFactor5LoadingDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogTable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogTableColumn.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogTableColumnFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/LogTableRowRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/class-use/TrackingAdjustmentListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/ConfigurationManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/MRUFileManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/class-use/ConfigurationManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/class-use/MRUFileManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/configure/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/lf5/viewer/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/JMSAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/JMSSink.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SMTPAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SimpleSocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SocketAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SocketHubAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SocketNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/SyslogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/TelnetAppender.SocketHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/TelnetAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/ZeroConfSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/JMSAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/JMSSink.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SMTPAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SimpleSocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SocketAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SocketHubAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SocketNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/SyslogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/TelnetAppender.SocketHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/TelnetAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/class-use/ZeroConfSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/net/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/NTEventLogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/class-use/NTEventLogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/nt/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/ObjectRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/RendererMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/ThreadGroupRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/class-use/ObjectRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/class-use/RendererMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/class-use/ThreadGroupRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/MessageRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/class-use/MessageRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/jms/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/AttributesRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/class-use/AttributesRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/or/sax/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/BridgePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/BridgePatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/CachedDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/ClassNamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/DatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/FileDatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/FileLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/FullLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/IntegerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LevelPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LineLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LineSeparatorPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LiteralPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LogEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LoggerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/LoggingEventPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/MessagePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/MethodLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/NDCPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/NameAbbreviator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/NamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/PropertiesPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/RelativeTimePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/SequenceNumberPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/ThreadPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/ThrowableInformationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/BridgePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/BridgePatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/CachedDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/ClassNamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/DatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/FileDatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/FileLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/FullLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/IntegerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LevelPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LineLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LineSeparatorPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LiteralPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LogEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LoggerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/LoggingEventPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/MessagePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/MethodLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/NDCPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/NameAbbreviator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/NamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/PropertiesPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/RelativeTimePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/SequenceNumberPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/ThreadPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/class-use/ThrowableInformationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/pattern/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/AppenderAttachable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/DefaultRepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/ErrorCode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/ErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/Filter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/HierarchyEventListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/LocationInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/LoggerFactory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/LoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/LoggingEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/NOPLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/NOPLoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/OptionHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/RendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/RepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/RootCategory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/RootLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/ThrowableInformation.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/ThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/ThrowableRendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/TriggeringEventEvaluator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/AppenderAttachable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/DefaultRepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/ErrorCode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/ErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/Filter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/HierarchyEventListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/LocationInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/LoggerFactory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/LoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/LoggingEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/NOPLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/NOPLoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/OptionHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/RendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/RepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/RootCategory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/RootLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/ThrowableInformation.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/ThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/ThrowableRendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/class-use/TriggeringEventEvaluator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/spi/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/DenyAllFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/ExternallyRolledFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/FallbackErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/LevelMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/LevelRangeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/NullAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/ReloadingPropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/Roller.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/StringMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/DenyAllFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/ExternallyRolledFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/FallbackErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/LevelMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/LevelRangeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/NullAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/ReloadingPropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/Roller.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/class-use/StringMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/varia/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/DOMConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/Log4jEntityResolver.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/SAXErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/UnrecognizedElementHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/XMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use/DOMConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use/Log4jEntityResolver.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use/SAXErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use/UnrecognizedElementHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/class-use/XMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/doc-files is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/doc-files/log4j.dtd is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/XMLSample.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/class-use is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/class-use/XMLSample.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/XMLSample.java is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/sample1.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/sample2.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/sample3.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/sample4.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/doc-files/sample5.xml is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/examples/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/package-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/org/apache/log4j/xml/package-use.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/overview-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/overview-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/overview-tree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/package-list is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/packages is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/resources is a directory. /opt/local/share/doc/jakarta-log4j/site/apidocs/resources/inherit.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/serialized-form.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/apidocs/stylesheet.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/changes-report.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/css is a directory. /opt/local/share/doc/jakarta-log4j/site/css/maven-base.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/css/maven-theme.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/css/print.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/css/site.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/dependencies.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/download.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/faq.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images is a directory. /opt/local/share/doc/jakarta-log4j/site/images/add.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/close.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/collapsed.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/expanded.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/external.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/fix.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/icon_error_sml.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/icon_help_sml.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/icon_info_sml.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/icon_success_sml.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/icon_warning_sml.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/logo.jpg is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/logos is a directory. /opt/local/share/doc/jakarta-log4j/site/images/logos/build-by-maven-black.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/logos/build-by-maven-white.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/logos/maven-feather.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/ls-logo.jpg is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/newwindow.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/od.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/remove.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/rss.png is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/images/update.gif is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/index.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/integration.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/issue-tracking.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/license.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/mail-lists.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/manual.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/project-info.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/project-reports.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/publications.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/roadmap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/source-repository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/allclasses-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/index.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/AppenderSkeleton.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/AsyncAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/BasicConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Category.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/CategoryKey.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/ConsoleAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/DailyRollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/DefaultCategoryFactory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/DefaultThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Dispatcher.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/EnhancedPatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/EnhancedThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/FileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/HTMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Hierarchy.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Layout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Level.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/LogMF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/LogManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/LogSF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/LogXF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Logger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/MDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/NDC.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/PatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/Priority.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/PropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/ProvisionNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/RollingFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/SimpleLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/TTCCLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/WriterAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/ControlPanel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/DetailPanel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/EventDetails.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/ExitAction.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/LoadXMLAction.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/LoggingReceiver.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/Main.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/MyTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/XMLFileHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/chainsaw/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/PropertyGetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/PropertyPrinter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/PropertySetter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/PropertySetterException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/config/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/AbsoluteTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/AppenderAttachableImpl.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/BoundedFIFO.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/CountingQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/CyclicBuffer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/DateLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/DateTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/FileWatchdog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/ISO8601DateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/Loader.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/LogLog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/MDCKeySetExtractor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/NullEnumeration.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/OnlyOnceErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/OptionConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/QuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/RelativeTimeDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/SyslogQuietWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/SyslogWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/ThreadLocalMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/Transform.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/helpers/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jdbc is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jdbc/JDBCAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jdbc/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jdbc/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/AbstractDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/Agent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/AppenderDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/HierarchyDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/LayoutDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/LoggerDynamicMBean.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/MethodUnion.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/jmx/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5 is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/AppenderFinalizer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/DefaultLF5Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/LF5Appender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/Log4JLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/LogLevel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/LogLevelFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/LogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/LogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/PassingLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/StartLogFactor5.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/AdapterLogRecord.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/DateFormatManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/LogFileParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/LogMonitorAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/Resource.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/ResourceUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/StreamUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/util/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/FilteredLogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LF5SwingUtils.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogBrokerMonitor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogFactor5Dialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogFactor5ErrorDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogFactor5InputDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogFactor5LoadingDialog.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogTable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogTableColumn.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogTableColumnFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogTableModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/LogTableRowRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/TrackingAdjustmentListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryAbstractCellEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryElement.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerLogRecordFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerModel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryExplorerTree.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryImmediateEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeEditor.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeEditorRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryNodeRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/CategoryPath.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/TreeModelAdapter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/categoryexplorer/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/configure is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/configure/ConfigurationManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/configure/MRUFileManager.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/configure/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/configure/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/lf5/viewer/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/JMSAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/JMSSink.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SMTPAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SimpleSocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SocketAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SocketHubAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SocketNode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/SyslogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/TelnetAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/ZeroConfSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/net/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/nt is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/nt/NTEventLogAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/nt/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/nt/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/DefaultRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/ObjectRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/RendererMap.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/ThreadGroupRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/jms is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/jms/MessageRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/jms/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/jms/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/sax is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/sax/AttributesRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/sax/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/or/sax/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/BridgePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/BridgePatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/CachedDateFormat.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/ClassNamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/DatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/FileDatePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/FileLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/FormattingInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/FullLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/IntegerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LevelPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LineLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LineSeparatorPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LiteralPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LogEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LoggerPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/LoggingEventPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/MessagePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/MethodLocationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/NDCPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/NameAbbreviator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/NamePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/PatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/PropertiesPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/RelativeTimePatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/SequenceNumberPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/ThreadPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/ThrowableInformationPatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/pattern/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/AppenderAttachable.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/Configurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/DefaultRepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/ErrorCode.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/ErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/Filter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/HierarchyEventListener.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/LocationInfo.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/LoggerFactory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/LoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/LoggingEvent.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/NOPLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/NOPLoggerRepository.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/NullWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/OptionHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/RendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/RepositorySelector.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/RootCategory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/RootLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/ThrowableInformation.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/ThrowableRenderer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/ThrowableRendererSupport.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/TriggeringEventEvaluator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/VectorWriter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/spi/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/DenyAllFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/ExternallyRolledFileAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/FallbackErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/LevelMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/LevelRangeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/NullAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/ReloadingPropertyConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/Roller.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/StringMatchFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/varia/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml is a directory. /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/DOMConfigurator.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/Log4jEntityResolver.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/SAXErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/UnrecognizedElementHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/XMLLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/org/apache/log4j/xml/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/overview-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/overview-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref/stylesheet.css is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/allclasses-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/index.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/AsyncAppenderTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/CategoryTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/CoreTestSuite.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/DRFATestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/DefaultThrowableRendererTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/EnhancedMyPatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/EnhancedPatternLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/EnhancedPatternLayoutTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/EnhancedThrowableRendererTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/FileAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/HTMLLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/HierarchyThresholdTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/Last.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/LayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/LevelTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/LogCapture.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/LogManagerTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/LoggerTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/MDCOrderFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/MinimumTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/MyPatternLayout.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/MyPatternParser.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/PatternLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/PatternLayoutTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/PriorityTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/PropertyConfiguratorTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/RFATestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/StressCategory.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/TTCCLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/TestLogMF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/TestLogSF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/TestLogXF.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/VectorAppender.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/VectorErrorHandler.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/customLogger is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/customLogger/XLogger.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/customLogger/XLoggerTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/customLogger/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/customLogger/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/TestCase1.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/TestCase2.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/TestCase3.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/TestCase4.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/defaultInit/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/BoundedFIFOTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/CyclicBufferTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/DateLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/LogLogTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/OptionConverterTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/PatternParserTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/helpers/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/SMTPAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/ShortSocketServer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/SocketAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/SocketServerTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/SyslogAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/TelnetAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/net/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/nt is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/nt/NTEventLogAppenderTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/nt/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/nt/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/or is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/or/ORTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/or/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/or/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/CachedDateFormatTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/FormattingInfoTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/NameAbbreviatorTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/Num343PatternConverter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/PatternParserTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/pattern/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi/LocationInfoTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi/LoggingEventTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi/ThrowableInformationTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/spi/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/AbsoluteDateAndTimeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/AbsoluteTimeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/Compare.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/ControlFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/EnhancedJunitTestRunnerFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/EnhancedLineNumberFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/Filter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/ISO8601Filter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/JunitTestRunnerFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/LineNumberFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/RelativeTimeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/SerializationTestHelper.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/SunReflectFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/Transformer.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/UnexpectedFormatException.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/XMLLineAttributeFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/XMLTimestampFilter.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/util/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia/ERFATestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia/ErrorHandlerTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia/LevelMatchFilterTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/varia/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml is a directory. /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/CustomLevelTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/DOMTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/XLevel.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/XMLLayoutTest.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/XMLLayoutTestCase.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/package-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/org/apache/log4j/xml/package-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/overview-frame.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/overview-summary.html is provided by: jakarta-log4j /opt/local/share/doc/jakarta-log4j/site/xref-test/stylesheet.css is provided by: jakarta-log4j /opt/local/share/doc/log4jdbc is a directory. /opt/local/share/doc/log4jdbc/CHANGES is provided by: log4jdbc /opt/local/share/doc/log4jdbc/LICENSE is provided by: log4jdbc /opt/local/share/doc/log4jdbc/README is provided by: log4jdbc /opt/local/share/doc/log4jdbc/TODO is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3 is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/allclasses-frame.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/allclasses-noframe.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/constant-values.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/deprecated-list.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/help-doc.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/index-all.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/index.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW0H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/CallableStatementSpyW1H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ConnectionSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ConnectionSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ConnectionSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ConnectionSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/DriverSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/DriverSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PostLogProfilerProcessor.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/PreparedStatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW0H5.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/ResultSetSpyW1H5.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Slf4jSpyLogDelegatorW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Slf4jSpyLogDelegatorW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Spy.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/SpyLogDelegator.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/SpyLogFactory.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/StatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/Utilities.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/class-use/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/package-frame.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/package-summary.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/package-tree.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/package-use.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/packageW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/net/sf/log4jdbc/packageW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/overview-tree.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/package-list is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/packages.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/resources is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/resources/inherit.gif is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/serialized-form.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/src-html/net/sf/log4jdbc/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc3/stylesheet.css is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4 is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/allclasses-frame.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/allclasses-noframe.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/constant-values.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/deprecated-list.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/help-doc.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/index-all.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/index.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW0H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW0H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW1H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/CallableStatementSpyW1H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ConnectionSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/DriverSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/DriverSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PostLogProfilerProcessor.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/PreparedStatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H5.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H6.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW0H7.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H3.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H4.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H5.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H6.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/ResultSetSpyW1H7.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Slf4jSpyLogDelegatorW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Slf4jSpyLogDelegatorW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Spy.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/SpyLogDelegator.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/SpyLogFactory.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW0H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW1H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW1H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/StatementSpyW1H2.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/Utilities.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/class-use/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/package-frame.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/package-summary.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/package-tree.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/package-use.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/packageW0H0.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/net/sf/log4jdbc/packageW0H1.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/overview-tree.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/package-list is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/resources is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/resources/inherit.gif is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc is a directory. /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/CallableStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/ConnectionSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/DriverSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/PostLogProfilerProcessor.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/PreparedStatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/ResultSetSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/Slf4jSpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/Spy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/SpyLogDelegator.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/SpyLogFactory.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/StatementSpy.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/src-html/net/sf/log4jdbc/Utilities.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/apidocs-jdbc4/stylesheet.css is provided by: log4jdbc /opt/local/share/doc/log4jdbc/index.html is provided by: log4jdbc /opt/local/share/doc/log4jdbc/log4j.properties is provided by: log4jdbc /opt/local/share/doc/log4jdbc/log4j.xml is provided by: log4jdbc /opt/local/share/doc/log4jdbc/log4jdbc-logo-gray.png is provided by: log4jdbc /opt/local/share/doc/log4jdbc/log4jdbc.css is provided by: log4jdbc /opt/local/share/doc/log4jdbc/reset-fonts-grids.css is provided by: log4jdbc /opt/local/share/doc/log4jdbc/sourceforge_whitebg.gif is provided by: log4jdbc /opt/local/share/doc/slf4j/apidocs/org/apache/log4j is a directory. /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/Category.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/Level.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/Logger.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/MDC.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/Priority.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use is a directory. /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use/Category.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use/Level.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use/Logger.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use/MDC.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/class-use/Priority.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/package-frame.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/package-summary.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/package-tree.html is provided by: slf4j /opt/local/share/doc/slf4j/apidocs/org/apache/log4j/package-use.html is provided by: slf4j /opt/local/share/examples/spring-framework25/jpetstore/war/WEB-INF/log4j.properties is provided by: spring-framework25 /opt/local/share/examples/spring-framework25/petclinic/test/log4j.properties is provided by: spring-framework25 /opt/local/share/examples/spring-framework25/petclinic/war/WEB-INF/classes/log4j.properties is provided by: spring-framework25 /opt/local/share/examples/spring-framework25/petportal/war/WEB-INF/log4j.properties is provided by: spring-framework25 /opt/local/share/java/apache-ant/lib/ant-apache-log4j.jar is provided by: apache-ant /opt/local/share/java/apache-ant/lib/ant-apache-log4j.pom is provided by: apache-ant /opt/local/share/java/apache-geode/config/log4j2.xml is provided by: apache-geode /opt/local/share/java/apache-geode/lib/log4j-api-2.6.1.jar is provided by: apache-geode /opt/local/share/java/apache-geode/lib/log4j-core-2.6.1.jar is provided by: apache-geode /opt/local/share/java/apache-geode/lib/log4j-jcl-2.6.1.jar is provided by: apache-geode /opt/local/share/java/apache-geode/lib/log4j-jul-2.6.1.jar is provided by: apache-geode /opt/local/share/java/apache-geode/lib/log4j-slf4j-impl-2.6.1.jar is provided by: apache-geode /opt/local/share/java/appengine-java-sdk/config/user/log4j.properties is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/demos/new_project_template/src/log4j.properties is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j-impl is a directory. /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j-impl/resources is a directory. /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j-impl/resources/log4j.xml is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j-impl.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-api.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-impl is a directory. /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-impl/resources is a directory. /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-impl/resources/log4j2.xml is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-impl.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/log4j2-slf4j.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/logging-log4j.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/logging-log4j2.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/slf4j-log4j.mod is provided by: appengine-java-sdk /opt/local/share/java/appengine-java-sdk/jetty94/jetty-home/modules/slf4j-log4j2.mod is provided by: appengine-java-sdk /opt/local/share/java/ghidra-9.2.2/Ghidra/Framework/Generic/lib/log4j-api-2.12.1.jar is provided by: ghidra /opt/local/share/java/ghidra-9.2.2/Ghidra/Framework/Generic/lib/log4j-core-2.12.1.jar is provided by: ghidra /opt/local/share/java/ghidra-9.2.2/support/debug.log4j.xml is provided by: ghidra /opt/local/share/java/gradle/lib/log4j-over-slf4j-1.7.30.jar is provided by: gradle /opt/local/share/java/jakarta-log4j.jar is provided by: jakarta-log4j /opt/local/share/java/log4j-over-slf4j.jar is provided by: slf4j /opt/local/share/java/log4jdbc3.jar is provided by: log4jdbc /opt/local/share/java/log4jdbc4.jar is provided by: log4jdbc /opt/local/share/java/mvnd/mvn/lib/ext/log4j-over-slf4j-1.7.32.jar is provided by: mvnd /opt/local/share/java/netbeans/extide/ant/lib/ant-apache-log4j.jar is provided by: NetBeans /opt/local/share/java/netbeans/ide/modules/ext/log4j-1.2.15.jar is provided by: NetBeans /opt/local/share/java/poi/lib/log4j-1.2.13.jar is provided by: poi /opt/local/share/java/slf4j-log4j12.jar is provided by: slf4j /opt/local/share/java/solr-8.9.0/contrib/prometheus-exporter/lib/log4j-api-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/contrib/prometheus-exporter/lib/log4j-core-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/contrib/prometheus-exporter/lib/log4j-slf4j-impl-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-1.2-api-2.13.2.jar.sha1 is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-LICENSE-ASL.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-NOTICE.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-api-2.13.2.jar.sha1 is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-api-LICENSE-ASL.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-api-NOTICE.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-core-2.13.2.jar.sha1 is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-core-LICENSE-ASL.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-core-NOTICE.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-slf4j-LICENSE-ASL.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-slf4j-NOTICE.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-slf4j-impl-2.13.2.jar.sha1 is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-web-2.13.2.jar.sha1 is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-web-LICENSE-ASL.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/licenses/log4j-web-NOTICE.txt is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/lib/ext/log4j-1.2-api-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/lib/ext/log4j-api-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/lib/ext/log4j-core-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/lib/ext/log4j-slf4j-impl-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/lib/ext/log4j-web-2.13.2.jar is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/resources/log4j2-console.xml is provided by: apache-solr8 /opt/local/share/java/solr-8.9.0/server/resources/log4j2.xml is provided by: apache-solr8 /opt/local/share/java/spring-framework25/lib/log4j is a directory. /opt/local/share/java/spring-framework25/lib/log4j/log4j-1.2.15.jar is provided by: spring-framework25 /opt/local/share/java/spring-framework25/lib/slf4j/slf4j-log4j12-1.5.0.jar is provided by: spring-framework25 /opt/local/share/java/webtoolkit-java-sdk/samples/DynaTableRf/src/main/resources/log4j.properties is provided by: webtoolkit-java-sdk /opt/local/share/java/webtoolkit-java-sdk/samples/MobileWebApp/src/main/resources/log4j.properties is provided by: webtoolkit-java-sdk /opt/local/share/java/webtoolkit-java-sdk/samples/Validation/src/main/resources/log4j.properties is provided by: webtoolkit-java-sdk /opt/local/share/java/zanata-cli/lib/log4j-1.2.17.jar is provided by: zanata-cli /opt/local/share/java/zanata-cli/lib/slf4j-log4j12-1.7.22.jar is provided by: zanata-cli /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j is a directory. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/StandardTests.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12 is a directory. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/ApiClasspathStandardTestCase.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/AppClasspathStandardTestCase.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/ChildClasspathStandardTestCase.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/Log4j12StandardTests.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/ParentClasspathStandardTestCase.java is not provided by a MacPorts port. /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_java_commons-logging/commons-logging/work/commons-logging-1.2-src/src/test/java/org/apache/commons/logging/log4j/log4j12/TestAppender.java is not provided by a MacPorts port. /opt/local/var/macports/distfiles/log4jdbc is a directory. /opt/local/var/macports/distfiles/log4jdbc/log4jdbc-1.1.zip is not provided by a MacPorts port. /opt/local/var/macports/registry/portfiles/jakarta-log4j-1.2.16_0 is a directory. /opt/local/var/macports/registry/portfiles/jakarta-log4j-1.2.16_0/2270db66c79022b36558802a81a0b722b19df4aa925fa6f95c78b81ad284b6ba-1423 is a directory. /opt/local/var/macports/registry/portfiles/jakarta-log4j-1.2.16_0/2270db66c79022b36558802a81a0b722b19df4aa925fa6f95c78b81ad284b6ba-1423/Portfile is not provided by a MacPorts port. /opt/local/var/macports/registry/portfiles/log4jdbc-1.1_0 is a directory. /opt/local/var/macports/registry/portfiles/log4jdbc-1.1_0/ac8312ad009fb97a5ef49877a91ec3423e4283799f8057b3ba856cf505ac99a6-1102 is a directory. /opt/local/var/macports/registry/portfiles/log4jdbc-1.1_0/ac8312ad009fb97a5ef49877a91ec3423e4283799f8057b3ba856cf505ac99a6-1102/Portfile is not provided by a MacPorts port. /opt/local/var/macports/software/jakarta-log4j is a directory. /opt/local/var/macports/software/jakarta-log4j/jakarta-log4j-1.2.16_0.darwin_20.x86_64.tbz2 is not provided by a MacPorts port. /opt/local/var/macports/software/log4jdbc is a directory. /opt/local/var/macports/software/log4jdbc/log4jdbc-1.1_0.darwin_20.x86_64.tbz2 is not provided by a MacPorts port. /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/java/jakarta-log4j is a directory. /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/java/jakarta-log4j/Portfile is not provided by a MacPorts port. /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/java/log4jdbc is a directory. /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/java/log4jdbc/Portfile is not provided by a MacPorts port. From jasonliu at umich.edu Sun Dec 12 18:50:42 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sun, 12 Dec 2021 13:50:42 -0500 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: <269cf0f6-66f1-49fb-c9b8-1582b40f0364@macports.org> References: <269cf0f6-66f1-49fb-c9b8-1582b40f0364@macports.org> Message-ID: On Sun, Dec 12, 2021 at 3:03 AM Joshua Root wrote: > On 2021-12-12 11:54 , Jason Liu wrote: > >> On Sat, Dec 11, 2021 at 6:41 PM Chris Jones > > wrote: >> >>> >>> No, because that would render the port non functional on non darwin >>> OSes. You should only specify the darwin platform when it is >>> actually required, e.g. when then making a os.major conditional that >>> inly makes sense in darwin platforms. >> >> >> >> Wait a minute, didn't Ryan say that "We don't really expect many ports >> to be installable on other operating systems or for maintainers to test >> anything on other operating systems"? So we /should/ worry about the >> port being non-functional on non-Darwin OSes? I'm confused now.... > > > Ports need to be "functional" on non-darwin platforms to the extent that > things like portindex, 'port mirror', and 'port info' work. They don't > need to be actually installable. Ah, so it seems like you're saying that the metadata-related stuff that we typically place near the top of the portfiles (e.g. name, version, categories, description, etc.) should all still be "functional" outside of any sort of specific platform context (and thus shouldn't be wrapped inside of a `platform darwin {`), but that it would be alright to wrap the stuff related to the build phases (i.e. fetch, extract, patch, configure, build, destroot, etc.) inside of a `platform darwin {` to hide it from other platforms, because the build phases only relate to the "installable" part? Am I getting that right? Or am I still confused? -- Jason Liu On Sun, Dec 12, 2021 at 3:03 AM Joshua Root wrote: > On 2021-12-12 11:54 , Jason Liu wrote: > > On Sat, Dec 11, 2021 at 6:41 PM Chris Jones > > wrote: > > > > No, because that would render the port non functional on non darwin > > OSes. You should only specify the darwin platform when it is > > actually required, e.g. when then making a os.major conditional that > > inly makes sense in darwin platforms. > > > > > > Wait a minute, didn't Ryan say that "We don't really expect many ports > > to be installable on other operating systems or for maintainers to test > > anything on other operating systems"? So we /should/ worry about the > > port being non-functional on non-Darwin OSes? I'm confused now.... > > Ports need to be "functional" on non-darwin platforms to the extent that > things like portindex, 'port mirror', and 'port info' work. They don't > need to be actually installable. > > > That's why I originally thought that `platforms darwin` implied that the > > portfile was only intended to be valid on Darwin. Now that I've learned > > that `platforms darwin` doesn't actually do anything, I'm just... > confused. > > It means the port is expected to only be installable on darwin. Ports > need to be more or less "valid" anywhere. The platforms option "doesn't > actually do anything" in precisely the same way that statement is true > for the description, i.e. what it does is simply make that information > known to users. > > - Josh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonesc at hep.phy.cam.ac.uk Sun Dec 12 18:57:19 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Sun, 12 Dec 2021 18:57:19 +0000 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: > On 12 Dec 2021, at 6:51 pm, Jason Liu wrote: > > ? >> On Sun, Dec 12, 2021 at 3:03 AM Joshua Root wrote: >>> On 2021-12-12 11:54 , Jason Liu wrote: >>> On Sat, Dec 11, 2021 at 6:41 PM Chris Jones >> > wrote: >>>> >>>> No, because that would render the port non functional on non darwin >>>> OSes. You should only specify the darwin platform when it is >>>> actually required, e.g. when then making a os.major conditional that >>>> inly makes sense in darwin platforms. >>> >>> >>> Wait a minute, didn't Ryan say that "We don't really expect many ports >>> to be installable on other operating systems or for maintainers to test >>> anything on other operating systems"? So we /should/ worry about the >>> port being non-functional on non-Darwin OSes? I'm confused now.... >> >> Ports need to be "functional" on non-darwin platforms to the extent that >> things like portindex, 'port mirror', and 'port info' work. They don't >> need to be actually installable. > > > Ah, so it seems like you're saying that the metadata-related stuff that we typically place near the top of the portfiles (e.g. name, version, categories, description, etc.) should all still be "functional" outside of any sort of specific platform context (and thus shouldn't be wrapped inside of a `platform darwin {`), but that it would be alright to wrap the stuff related to the build phases (i.e. fetch, extract, patch, configure, build, destroot, etc.) inside of a `platform darwin {` to hide it from other platforms, because the build phases only relate to the "installable" part? Am I getting that right? Or am I still confused? The guidelines you should aim to follow are exactly what they have been so far. Ports should be ?as functional as possible? on all platforms, so you should aim to place only what you have to inside a darwin platform check. So no, blanket placing everything you mention above inside a darwin check, when there is no technical reason to do so, is not really what we want. > > -- > Jason Liu > > >> On Sun, Dec 12, 2021 at 3:03 AM Joshua Root wrote: >> On 2021-12-12 11:54 , Jason Liu wrote: >> > On Sat, Dec 11, 2021 at 6:41 PM Chris Jones > > > wrote: >> > >> > No, because that would render the port non functional on non darwin >> > OSes. You should only specify the darwin platform when it is >> > actually required, e.g. when then making a os.major conditional that >> > inly makes sense in darwin platforms. >> > >> > >> > Wait a minute, didn't Ryan say that "We don't really expect many ports >> > to be installable on other operating systems or for maintainers to test >> > anything on other operating systems"? So we /should/ worry about the >> > port being non-functional on non-Darwin OSes? I'm confused now.... >> >> Ports need to be "functional" on non-darwin platforms to the extent that >> things like portindex, 'port mirror', and 'port info' work. They don't >> need to be actually installable. >> >> > That's why I originally thought that `platforms darwin` implied that the >> > portfile was only intended to be valid on Darwin. Now that I've learned >> > that `platforms darwin` doesn't actually do anything, I'm just... confused. >> >> It means the port is expected to only be installable on darwin. Ports >> need to be more or less "valid" anywhere. The platforms option "doesn't >> actually do anything" in precisely the same way that statement is true >> for the description, i.e. what it does is simply make that information >> known to users. >> >> - Josh -------------- next part -------------- An HTML attachment was scrubbed... URL: From nils at breun.nl Sun Dec 12 20:48:13 2021 From: nils at breun.nl (Nils Breunese) Date: Sun, 12 Dec 2021 21:48:13 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> Message-ID: <3A9AFE8B-9CE0-4548-8F99-5EC260F364AA@breun.nl> Eric Gallager wrote: > On Sun, Dec 12, 2021 at 4:57 AM Joshua Root wrote: >> >> On 2021-12-12 20:02 , Nils Breunese wrote: >>> It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. >> >> Not all ports have installed file information available, but the web app >> can search the ones that do: >> >> >> >> - Josh > > Some other ports with log4j-related files that don't show up in this > search: spring-framework25 +with_libs (from the 1.x series, so it's > safe), slf4j (just docs, so it's safe), log4jdbc (also old, and > possibly a spurious string match, so probably also safe), duck (1.x > series, so it's safe), apache-ant (not seeing version info, I dunno), > apache-geode (this one might actually need checking?), > appengine-java-sdk (not sure), ghidra (this one looks vulnerable), poi > (1.x series, so it's safe), webtoolkit-java-sdk (I dunno), zanata-cli > (1.x series, so it's safe), and commons-logging (doesn't even build). > I'll attach the output of `locate /opt/local/*log4j* | xargs port > provides` to this email so you can see the same list I was looking at. > I said to look log4j-$version.jar earlier, but I should have said log4j-core-$version.jar. In your list apache-solr8 and apache-geode contain vulnerable versions of Log4J 2.x. Nils. From nils at breun.nl Sun Dec 12 20:53:27 2021 From: nils at breun.nl (Nils Breunese) Date: Sun, 12 Dec 2021 21:53:27 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <3A9AFE8B-9CE0-4548-8F99-5EC260F364AA@breun.nl> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <3A9AFE8B-9CE0-4548-8F99-5EC260F364AA@breun.nl> Message-ID: <559E280A-28CA-41B1-A80C-34286101A21A@breun.nl> Nils Breunese wrote: > Eric Gallager wrote: > >> On Sun, Dec 12, 2021 at 4:57 AM Joshua Root wrote: >>> >>> On 2021-12-12 20:02 , Nils Breunese wrote: >>>> It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. >>> >>> Not all ports have installed file information available, but the web app >>> can search the ones that do: >>> >>> >>> >>> - Josh >> >> Some other ports with log4j-related files that don't show up in this >> search: spring-framework25 +with_libs (from the 1.x series, so it's >> safe), slf4j (just docs, so it's safe), log4jdbc (also old, and >> possibly a spurious string match, so probably also safe), duck (1.x >> series, so it's safe), apache-ant (not seeing version info, I dunno), >> apache-geode (this one might actually need checking?), >> appengine-java-sdk (not sure), ghidra (this one looks vulnerable), poi >> (1.x series, so it's safe), webtoolkit-java-sdk (I dunno), zanata-cli >> (1.x series, so it's safe), and commons-logging (doesn't even build). >> I'll attach the output of `locate /opt/local/*log4j* | xargs port >> provides` to this email so you can see the same list I was looking at. >> > > I said to look log4j-$version.jar earlier, but I should have said log4j-core-$version.jar. > > In your list apache-solr8 and apache-geode contain vulnerable versions of Log4J 2.x. And ghidra indeed, sorry. The version of Apache Geode in MacPorts (1.0.0-incubating) is also rather old. Version 1.14.1 of Apache Geode bumped its dependency on Log4J to 2.15.0, which is the fixed version: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.1 Nils. From dluke at geeklair.net Sun Dec 12 22:25:15 2021 From: dluke at geeklair.net (Daniel J. Luke) Date: Sun, 12 Dec 2021 17:25:15 -0500 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: <35B7283D-8C20-43C4-92ED-B5BB904457B8@geeklair.net> On Dec 11, 2021, at 7:42 PM, Jason Liu wrote: > Actually, I find myself needing to use them more and more. For example, I now often have to check for macOS < 10.12, due to the large overhaul that happened in AppKit between 10.11 and 10.12. My workarounds for older versions of macOS are contained inside those `if {${os.major} <= 15}` conditionals. Ideally you wouldn't have to use any (and the portfiles would all be declarative) - that's not really possible now, but I think needing them is a good indication of areas where we should enhance MacPorts base to make it (eventually) possible to not need them. For os.major stuff, I think there have been some proposals for range syntax, just none have been implemented yet. -- Daniel J. Luke From egall at gwmail.gwu.edu Sun Dec 12 22:37:00 2021 From: egall at gwmail.gwu.edu (Eric Gallager) Date: Sun, 12 Dec 2021 17:37:00 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <559E280A-28CA-41B1-A80C-34286101A21A@breun.nl> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <3A9AFE8B-9CE0-4548-8F99-5EC260F364AA@breun.nl> <559E280A-28CA-41B1-A80C-34286101A21A@breun.nl> Message-ID: On Sun, Dec 12, 2021 at 3:53 PM Nils Breunese wrote: > > Nils Breunese wrote: > > > Eric Gallager wrote: > > > >> On Sun, Dec 12, 2021 at 4:57 AM Joshua Root wrote: > >>> > >>> On 2021-12-12 20:02 , Nils Breunese wrote: > >>>> It could be the case the MacPorts has ports for Java-based applications that include a vulnerable version of the Log4J library. A port that includes a file called log4j-$version.jar with $version in the range 2.0.0-2.14.1 could be vulnerable. This file could also be ?hidden? inside a compressed archive, like a .war file (basically a zip file). I?m not sure how we could check all ports for this without installing all of them. > >>> > >>> Not all ports have installed file information available, but the web app > >>> can search the ones that do: > >>> > >>> > >>> > >>> - Josh > >> > >> Some other ports with log4j-related files that don't show up in this > >> search: spring-framework25 +with_libs (from the 1.x series, so it's > >> safe), slf4j (just docs, so it's safe), log4jdbc (also old, and > >> possibly a spurious string match, so probably also safe), duck (1.x > >> series, so it's safe), apache-ant (not seeing version info, I dunno), > >> apache-geode (this one might actually need checking?), > >> appengine-java-sdk (not sure), ghidra (this one looks vulnerable), poi > >> (1.x series, so it's safe), webtoolkit-java-sdk (I dunno), zanata-cli > >> (1.x series, so it's safe), and commons-logging (doesn't even build). > >> I'll attach the output of `locate /opt/local/*log4j* | xargs port > >> provides` to this email so you can see the same list I was looking at. > >> > > > > I said to look log4j-$version.jar earlier, but I should have said log4j-core-$version.jar. > > > > In your list apache-solr8 and apache-geode contain vulnerable versions of Log4J 2.x. > > And ghidra indeed, sorry. > > The version of Apache Geode in MacPorts (1.0.0-incubating) is also rather old. Version 1.14.1 of Apache Geode bumped its dependency on Log4J to 2.15.0, which is the fixed version: https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.1 > > Nils. There's bug 58631 open for an update to apache-geode: https://trac.macports.org/ticket/58631 And I opened bug 64199 for ghidra: https://trac.macports.org/ticket/64199 From steve.t.smith at gmail.com Mon Dec 13 03:43:56 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Sun, 12 Dec 2021 22:43:56 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <29FE26F6-26F1-4D11-BA2D-006939E34488@breun.nl> Message-ID: <1FB97C65-3E33-4823-9A8F-FE1098FBFA91@gmail.com> Please see https://github.com/macports/macports-ports/pull/13331 > On Dec 12, 2021, at 7:36 AM, Nils Breunese wrote: > > 2. elasticsearch 7.15.2_0 includes log4j-core-2.11.1.jar, which is a vulnerable version of Log4J 2.x > > https://github.com/elastic/elasticsearch/issues/81618 says: "This can be mitigated for the time being by adding -Dlog4j2.formatMsgNoLookups=true to ES_JAVA_OPTS". I think I?d add -Dlog4j2.formatMsgNoLookups=true in /opt/local/etc/elasticsearch/jvm.options, or add ES_JAVA_OPTS="$ES_JAVA_OPTS -Dlog4j2.formatMsgNoLookups=true" at the end of /opt/local/bin/elasticsearch-env. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3898 bytes Desc: not available URL: From arjun at macports.org Mon Dec 13 09:35:54 2021 From: arjun at macports.org (Arjun Salyan) Date: Mon, 13 Dec 2021 15:05:54 +0530 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> Message-ID: <5F4E361A-D2B5-417C-86F8-F778AE7A66CE@macports.org> > On 12-Dec-2021, at 3:27 PM, Joshua Root wrote: > > Not all ports have installed file information available, but the web app can search the ones that do: > > I identified an issue with the way we were updating our search index. That has been fixed and now this page shows 17 ports, instead of 5. From chrischavez at gmx.us Mon Dec 13 10:48:29 2021 From: chrischavez at gmx.us (Christopher Chavez) Date: Mon, 13 Dec 2021 11:48:29 +0100 Subject: =?UTF-8?Q?Acceptability_of_depends=5Fbuild_bin=3A=E2=80=A6?= Message-ID: I recently specified bin:node:? build dependency in qt5-qtwebengine. I would not consider Node.js to be a lightweight dependency, so I thought it would be preferable to allow using whichever is present, even a non-MacPorts one, before having to install a fallback; and because I had not investigated whether the build process would always respect a path:? or port:? dependency. It has now been requested that bin:node:? not be used, in light of this comment: https://github.com/macports/macports-ports/commit/afad77a86ba6be6572cf0aff35db0b13401196f1#commitcomment-61791005 > A `bin:`-style dependency allows any binary in the path, even in locations outside of MacPorts, to satisfy a dependency, which is not usually desired. While I?m somewhat aware why bin:? dependencies are particularly undesirable for library or runtime dependencies, how strongly does the recommendation to avoid them apply to dependencies only used during build? Are they to still be avoided as much as possible, regardless of how heavy the dependencies are or whether one believes allowing third-party dependencies would not cause any significant difference in the built port (w.r.t. build reproducibility) nor pose a risk of build failure? Christopher A. Chavez From jonesc at hep.phy.cam.ac.uk Mon Dec 13 10:56:32 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Mon, 13 Dec 2021 10:56:32 +0000 Subject: =?utf-8?Q?Re=3A_Acceptability_of_depends=5Fbuild_bin=3A=E2=80=A6?= In-Reply-To: References: Message-ID: > On 13 Dec 2021, at 10:48 am, Christopher Chavez wrote: > > I recently specified bin:node:? build dependency in qt5-qtwebengine. I would not consider Node.js to be a lightweight dependency, so I thought it would be preferable to allow using whichever is present, even a non-MacPorts one, before having to install a fallback; and because I had not investigated whether the build process would always respect a path:? or port:? dependency. > > It has now been requested that bin:node:? not be used, in light of this comment: https://github.com/macports/macports-ports/commit/afad77a86ba6be6572cf0aff35db0b13401196f1#commitcomment-61791005 > > >> A `bin:`-style dependency allows any binary in the path, even in locations outside of MacPorts, to satisfy a dependency, which is not usually desired. > > > While I?m somewhat aware why bin:? dependencies are particularly undesirable for library or runtime dependencies, how strongly does the recommendation to avoid them apply to dependencies only used during build? Are they to still be avoided as much as possible, regardless of how heavy the dependencies are or whether one believes allowing third-party dependencies would not cause any significant difference in the built port (w.r.t. build reproducibility) nor pose a risk of build failure? In my opinion yes, they should be avoided. Just because it is a build dep. doesn?t make a difference, as we want reproducible builds, which means having control over the whole process, and allowing whatever is found in 'bin? to satisfy a dependency breaks this. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From ryandesign at macports.org Mon Dec 13 19:26:04 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 13 Dec 2021 13:26:04 -0600 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: On Dec 11, 2021, at 18:42, Jason Liu wrote: > On Sat, Dec 11, 2021 at 5:46 PM Ryan Schmidt wrote: >> I wouldn't expect you to need to write more than a couple such conditionals in a portfile so I wouldn't expect it to be that inconvenient. > > Actually, I find myself needing to use them more and more. For example, I now often have to check for macOS < 10.12, due to the large overhaul that happened in AppKit between 10.11 and 10.12. My workarounds for older versions of macOS are contained inside those `if {${os.major} <= 15}` conditionals. Ok, so that's one conditional. If you need multiple different Darwin os.major conditionals, you could: platform darwin { if {${os.major} <= 15} { # something } if {${os.major} <= 19} { # something } } Before you mentioned the AppKit overhaul some time ago and started addressing it in your ports, I had never heard of it and I don't think anyone else's ports do anything about it. So either we have a lot of broken ports due to this problem that we're not aware of, or for some reason it uniquely affects the ports you maintain... >> Josh did recently commit "darwin" as a default for platforms, so it is no longer mandatory to explicitly put a platforms line in each portfile. > > Does this mean that we can start removing `platforms darwin` from our portfiles? Or is it one of those "despite the fact that it's a default, you have to put it in the file anyway"? I have seen many recent commits in which the "platforms darwin" line is silently being removed while other changes are being made, so sure, that's fine. From chrischavez at gmx.us Tue Dec 14 02:41:10 2021 From: chrischavez at gmx.us (Christopher Chavez) Date: Tue, 14 Dec 2021 03:41:10 +0100 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: > Before you mentioned the AppKit overhaul some time ago and started addressing it in your ports, I had never heard of it and I don't think anyone else's ports do anything about it. So either we have a lot of broken ports due to this problem that we're not aware of, or for some reason it uniquely affects the ports you maintain... I want say this issue is not extremely uncommon, even if awareness of it is. One instance of this is Tcl/Tk, which decided to predefine the deprecated names of constants/functions/etc. to the 10.12 names when compiling for ?10.12, and leave usage of deprecated constants in their codebase alone (leaving nothing for MacPorts to fix). Maybe there are still projects using the deprecated names which ignore or suppress warnings from -Wdeprecated-declarations. But if an upstream project switched to the 10.12 names and effectively dropped support for ?10.11, I imagine the easiest course of action for a port that then broke on ?10.11 was to just drop support for ?10.11 (and not necessarily leave a more specific comment explaining why). Next up from that might be to patch the old names back in, and either ignore deprecation warnings on ?10.12, patch only on ?10.11, or suppressing warnings on ?10.12. Christopher A. Chavez From nils at breun.nl Tue Dec 14 23:47:14 2021 From: nils at breun.nl (Nils Breunese) Date: Wed, 15 Dec 2021 00:47:14 +0100 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: <5F4E361A-D2B5-417C-86F8-F778AE7A66CE@macports.org> References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <5F4E361A-D2B5-417C-86F8-F778AE7A66CE@macports.org> Message-ID: Arjun Salyan wrote:: >> On 12-Dec-2021, at 3:27 PM, Joshua Root wrote: >> >> Not all ports have installed file information available, but the web app can search the ones that do: >> >> > > I identified an issue with the way we were updating our search index. That has been fixed and now this page shows 17 ports, instead of 5. Thanks for fixing! For Log4J only log4j-core-* is relevant, and https://ports.macports.org/search/?installed_file=log4j-core&q= only shows the ports we already previously identified. A couple of hours ago https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046 was made public, which states that the previous mitigations of upgrading to Log4J 2.15.0 or setting system/environment properties is longer enough. The recommended solution is upgrading to Log4J 2.16.0. If that is not possible, it is recommended to at least remove the JndiLookup class from the log4j-core JAR (e.g. zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). Nils. From steve.t.smith at gmail.com Wed Dec 15 00:27:49 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Tue, 14 Dec 2021 19:27:49 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <5F4E361A-D2B5-417C-86F8-F778AE7A66CE@macports.org> Message-ID: <9761F479-7819-43D3-BB2A-04F464E0AF9D@gmail.com> Thank you for posting! Please see https://github.com/macports/macports-ports/pull/13353 . > On Dec 14, 2021, at 6:47 PM, Nils Breunese wrote: > > A couple of hours ago https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046 was made public, which states that the previous mitigations of upgrading to Log4J 2.15.0 or setting system/environment properties is longer enough. The recommended solution is upgrading to Log4J 2.16.0. If that is not possible, it is recommended to at least remove the JndiLookup class from the log4j-core JAR (e.g. zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3898 bytes Desc: not available URL: From steve.t.smith at gmail.com Wed Dec 15 00:43:18 2021 From: steve.t.smith at gmail.com (Steven Smith) Date: Tue, 14 Dec 2021 19:43:18 -0500 Subject: Significant security vulnerability discovered in Log4j In-Reply-To: References: <8dc86feb-e007-3a8b-c633-1a7a6933699f@macports.org> <5F4E361A-D2B5-417C-86F8-F778AE7A66CE@macports.org> Message-ID: Also please see https://github.com/macports/macports-ports/pull/13361 > On Dec 14, 2021, at 6:47 PM, Nils Breunese wrote: > > A couple of hours ago https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046 was made public, which states that the previous mitigations of upgrading to Log4J 2.15.0 or setting system/environment properties is longer enough. The recommended solution is upgrading to Log4J 2.16.0. If that is not possible, it is recommended to at least remove the JndiLookup class from the log4j-core JAR (e.g. zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3898 bytes Desc: not available URL: From jasonliu at umich.edu Thu Dec 16 21:24:28 2021 From: jasonliu at umich.edu (Jason Liu) Date: Thu, 16 Dec 2021 16:24:28 -0500 Subject: fetch phase: sourceforge with 302 redirects? Message-ID: Hi everyone, I'm working on a new portfile that has its source stored on sourceforge. MacPorts is having trouble obtaining the tarball, because apparently the mirrors are pointing to the wrong file, and if I put the full URL into ` master_sites`, it's unable to find the tarball at all. It seems that sourceforge is using 301 redirects to point to the actual file. If I use the URL with a `curl -L`, the correct file downloads just fine. Is there any way to get MacPorts to follow redirects during the fetch phase? If at all possible, I'd like to avoid manually using curl through a `system` call, but I suppose it could work as a last resort. -- Jason Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Thu Dec 16 21:29:08 2021 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 16 Dec 2021 16:29:08 -0500 Subject: fetch phase: sourceforge with 302 redirects? In-Reply-To: References: Message-ID: <67EC2FD9-2A9E-46C7-B699-F11A0E0CAA23@geeklair.net> On Dec 16, 2021, at 4:24 PM, Jason Liu wrote: > I'm working on a new portfile that has its source stored on sourceforge. MacPorts is having trouble obtaining the tarball, because apparently the mirrors are pointing to the wrong file, and if I put the full URL into `master_sites`, it's unable to find the tarball at all. It seems that sourceforge is using 301 redirects to point to the actual file. If I use the URL with a `curl -L`, the correct file downloads just fine. Is there any way to get MacPorts to follow redirects during the fetch phase? If at all possible, I'd like to avoid manually using curl through a `system` call, but I suppose it could work as a last resort. Does this sourceforge example help? https://trac.macports.org/wiki/howto/AvoidRedirects -- Daniel J. Luke From jasonliu at umich.edu Thu Dec 16 21:38:38 2021 From: jasonliu at umich.edu (Jason Liu) Date: Thu, 16 Dec 2021 16:38:38 -0500 Subject: fetch phase: sourceforge with 302 redirects? In-Reply-To: <67EC2FD9-2A9E-46C7-B699-F11A0E0CAA23@geeklair.net> References: <67EC2FD9-2A9E-46C7-B699-F11A0E0CAA23@geeklair.net> Message-ID: Yes, using the `curl -IL` command to obtain the part of the path I need to extract (which is very slightly different from the web browser URL), did the trick. Thanks! :) -- Jason Liu On Thu, Dec 16, 2021 at 4:29 PM Daniel J. Luke wrote: > On Dec 16, 2021, at 4:24 PM, Jason Liu wrote: > > I'm working on a new portfile that has its source stored on sourceforge. > MacPorts is having trouble obtaining the tarball, because apparently the > mirrors are pointing to the wrong file, and if I put the full URL into > `master_sites`, it's unable to find the tarball at all. It seems that > sourceforge is using 301 redirects to point to the actual file. If I use > the URL with a `curl -L`, the correct file downloads just fine. Is there > any way to get MacPorts to follow redirects during the fetch phase? If at > all possible, I'd like to avoid manually using curl through a `system` > call, but I suppose it could work as a last resort. > > Does this sourceforge example help? > > https://trac.macports.org/wiki/howto/AvoidRedirects > > -- > Daniel J. Luke > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From macintosh at mathiesen.info Thu Dec 16 23:17:26 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Fri, 17 Dec 2021 00:17:26 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems Message-ID: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 Ok, I've got certbot installed, but a recent upgrade of something has broken it : #=> certbot certificates gives the following error-message : pkg_resources.ContextualVersionConflict: (cryptography 2.9.2 (/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages), Requirement.parse('cryptography>=3.3'), {'PyOpenSSL'}) which to me indicates, that PyOpenSSL needs to be upgraded. So, I installed py39-pip, and did the following : #=> pip install pyopenssl Requirement already satisfied: pyopenssl in /opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages (21.0.0) Collecting cryptography>=3.3 Downloading cryptography-36.0.1.tar.gz (572 kB) |????????????????????????????????| 572 kB 1.0 MB/s Installing build dependencies ... done which resulted in the following error-message : running build_rust =============================DEBUG ASSISTANCE============================= If you are seeing a compilation error please try the following steps to successfully install cryptography: 1) Upgrade to the latest pip and try again. This will fix errors for most users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip 2) Read https://cryptography.io/en/latest/installation/ for specific instructions for your platform. 3) Check our frequently asked questions for more information: https://cryptography.io/en/latest/faq/ 4) Ensure you have a recent Rust toolchain installed: https://cryptography.io/en/latest/installation/#rust Python: 3.9.9 platform: macOS-10.6.8-i386-64bit pip: n/a setuptools: 59.6.0 setuptools_rust: 1.1.2 =============================DEBUG ASSISTANCE============================= error: can't find Rust compiler So, it's missing the rust compiler ! OK, let me install that one : ---> Fetching distfiles for rust-compiler-wrap Error: rust is only supported on macOS 10.7 or later. Error: Failed to fetch rust-compiler-wrap: unsupported platform version Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust-compiler-wrap/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port rust failed Any ideas as to how I can upgrade PyOpenSSL -or- the cryptography ? Or am I just lost ??? -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From ryandesign at macports.org Thu Dec 16 23:49:58 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 16 Dec 2021 17:49:58 -0600 Subject: fetch phase: sourceforge with 302 redirects? In-Reply-To: References: Message-ID: <33ADC8BA-7AA6-4B09-ADCE-44F41EA7D79D@macports.org> On Dec 16, 2021, at 15:24, Jason Liu wrote: > Is there any way to get MacPorts to follow redirects during the fetch phase? MacPorts always does so already. But SourceForge has a bug in at least one of their mirror servers where redirects are not working correctly. Therefore, refer to the AvoidRedirects recipe for how to ensure you avoid the redirects in the first place. From ryandesign at macports.org Thu Dec 16 23:52:34 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 16 Dec 2021 17:52:34 -0600 Subject: Question about `platforms` and `${os.platform}` In-Reply-To: References: Message-ID: <4AB9413A-71CF-4FCE-AEAC-FB881E2A4046@macports.org> On Dec 13, 2021, at 20:41, Christopher Chavez wrote: >> Before you mentioned the AppKit overhaul some time ago and started addressing it in your ports, I had never heard of it and I don't think anyone else's ports do anything about it. So either we have a lot of broken ports due to this problem that we're not aware of, or for some reason it uniquely affects the ports you maintain... > > > I want say this issue is not extremely uncommon, even if awareness of it is. One instance of this is Tcl/Tk, which decided to predefine the deprecated names of constants/functions/etc. to the 10.12 names when compiling for ?10.12, and leave usage of deprecated constants in their codebase alone (leaving nothing for MacPorts to fix). > > Maybe there are still projects using the deprecated names which ignore or suppress warnings from -Wdeprecated-declarations. > > But if an upstream project switched to the 10.12 names and effectively dropped support for ?10.11, I imagine the easiest course of action for a port that then broke on ?10.11 was to just drop support for ?10.11 (and not necessarily leave a more specific comment explaining why). Next up from that might be to patch the old names back in, and either ignore deprecation warnings on ?10.12, patch only on ?10.11, or suppressing warnings on ?10.12. I thought the "AppKit overhaul" referred to much more than just some symbols being renamed. If it's just renamed symbols, that seems like a simple enough problem to fix in either direction. From ryandesign at macports.org Thu Dec 16 23:56:50 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 16 Dec 2021 17:56:50 -0600 Subject: =?utf-8?Q?Re=3A_Acceptability_of_depends=5Fbuild_bin=3A=E2=80=A6?= In-Reply-To: References: Message-ID: <81F58807-46A5-4A34-BB4D-04364ACEC357@macports.org> On Dec 13, 2021, at 04:48, Christopher Chavez wrote: > I recently specified bin:node:? build dependency in qt5-qtwebengine. I would not consider Node.js to be a lightweight dependency, so I thought it would be preferable to allow using whichever is present, even a non-MacPorts one, before having to install a fallback; and because I had not investigated whether the build process would always respect a path:? or port:? dependency. > > It has now been requested that bin:node:? not be used, in light of this comment: https://github.com/macports/macports-ports/commit/afad77a86ba6be6572cf0aff35db0b13401196f1#commitcomment-61791005 > > >> A `bin:`-style dependency allows any binary in the path, even in locations outside of MacPorts, to satisfy a dependency, which is not usually desired. > > > While I?m somewhat aware why bin:? dependencies are particularly undesirable for library or runtime dependencies, how strongly does the recommendation to avoid them apply to dependencies only used during build? Are they to still be avoided as much as possible, regardless of how heavy the dependencies are or whether one believes allowing third-party dependencies would not cause any significant difference in the built port (w.r.t. build reproducibility) nor pose a risk of build failure? I stand by my statement. If a user already has "node" installed outside of MacPorts, you know nothing about it. Perhaps it is an ancient version the user installed 10 years ago and forgot about. Perhaps it's compiled for an architecture that doesn't run on this OS version anymore. Perhaps it's linked with libraries that the user has since removed. To increase the chance of a successful build that is the same as the one the maintainer intended to happen, use MacPorts ports as dependencies rather than whatever random thing might exist on the user's system. From khindenburg at macports.org Fri Dec 17 00:14:33 2021 From: khindenburg at macports.org (Kurt Hindenburg) Date: Thu, 16 Dec 2021 19:14:33 -0500 Subject: deleting -DNDEBUG added by cmake PG Message-ID: <6317520D-36D8-4C08-A0F8-FEA094EE2DDF@macports.org> Hello, The cmake PG adds -DNDEBUG to various flags. For the next release of ipbt I need to remove it. The normal configure.*-delete do not seem to work. Does anyone have suggestions on how to do this? configure.cflags-append -DNDEBUG configure.cxxflags-append -DNDEBUG https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/cmake-1.1.tcl Kurt -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at schamschula.com Fri Dec 17 00:28:59 2021 From: lists at schamschula.com (Marius Schamschula) Date: Thu, 16 Dec 2021 18:28:59 -0600 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> Message-ID: <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> What does port installed py39-openssl say? On my machine I get 21.00.0_0. Also, IIRC there was a change in py-cryptography versioning. On my machine I have 35.0.0_3. Mixing pip with MacPorts will guarantee a broken installation within weeks.if not within days. Marius -- Marius Schamschula > On Dec 16, 2021, at 5:17 PM, Bjarne D Mathiesen wrote: > > System Version: Mac OS X 10.6.8 (10K549) > Kernel Version: Darwin 10.8.0 > > Ok, I've got certbot installed, but a recent upgrade of something has > broken it : > > #=> certbot certificates > > gives the following error-message : > > pkg_resources.ContextualVersionConflict: (cryptography 2.9.2 > (/opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages), > Requirement.parse('cryptography>=3.3'), {'PyOpenSSL'}) > > which to me indicates, that PyOpenSSL needs to be upgraded. > So, I installed py39-pip, and did the following : > > #=> pip install pyopenssl > Requirement already satisfied: pyopenssl in > /opt/local/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages > (21.0.0) > Collecting cryptography>=3.3 > Downloading cryptography-36.0.1.tar.gz (572 kB) > |????????????????????????????????| 572 kB 1.0 MB/s > Installing build dependencies ... done > > which resulted in the following error-message : > > running build_rust > > =============================DEBUG > ASSISTANCE============================= > If you are seeing a compilation error please try the following > steps to > successfully install cryptography: > 1) Upgrade to the latest pip and try again. This will fix errors > for most > users. See: https://pip.pypa.io/en/stable/installing/#upgrading-pip > 2) Read https://cryptography.io/en/latest/installation/ for specific > instructions for your platform. > 3) Check our frequently asked questions for more information: > https://cryptography.io/en/latest/faq/ > 4) Ensure you have a recent Rust toolchain installed: > https://cryptography.io/en/latest/installation/#rust > > Python: 3.9.9 > platform: macOS-10.6.8-i386-64bit > pip: n/a > setuptools: 59.6.0 > setuptools_rust: 1.1.2 > =============================DEBUG > ASSISTANCE============================= > > error: can't find Rust compiler > > So, it's missing the rust compiler ! > OK, let me install that one : > > ---> Fetching distfiles for rust-compiler-wrap > Error: rust is only supported on macOS 10.7 or later. > Error: Failed to fetch rust-compiler-wrap: unsupported platform version > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_rust/rust-compiler-wrap/main.log > for details. > Error: Follow https://guide.macports.org/#project.tickets if you believe > there is a bug. > Error: Processing of port rust failed > > > Any ideas as to how I can upgrade PyOpenSSL -or- the cryptography ? > Or am I just lost ??? > > > -- > Bjarne D Mathiesen > Kors?r ; Danmark ; Europa > ----------------------------------------------------------------------- > denne besked er skrevet i et totalt M$-frit milj? > MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina > 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM > ATI Radeon RX 590 8 GB -------------- next part -------------- An HTML attachment was scrubbed... URL: From macintosh at mathiesen.info Fri Dec 17 08:05:09 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Fri, 17 Dec 2021 09:05:09 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> Message-ID: <06897424-6b48-2013-d4a9-179e76b33c61@mathiesen.info> Marius Schamschula wrote: > What does > > port installed py39-openssl > > say? On my machine I get 21.00.0_0. > > Also, IIRC there was a change in py-cryptography versioning. On my > machine I have 35.0.0_3. > > Mixing pip with MacPorts will guarantee a broken installation within > weeks.if not within days. > > Marius > -- > Marius Schamschula > So, on my System Version: macOS 10.15.7 (19H1519) Kernel Version: Darwin 19.6.0 I get : #=> port -q installed py39-cryptography py39-cryptography @35.0.0_3 (active) On my System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 I get : #=> port -q installed py39-cryptography py39-cryptography @2.9.2_2 (active) #=> port -f -cuNp uninstall py39-cryptography ---> Unable to uninstall py39-cryptography @2.9.2_2, the following ports depend on it: ... root at MiniWeb 08:56:20 ~ #=> port -cuNp install py39-cryptography ---> Computing dependencies for py39-cryptography ---> Fetching archive for py39-cryptography ---> Attempting to fetch py39-cryptography-2.9.2_2.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/py39-cryptography ---> Attempting to fetch py39-cryptography-2.9.2_2.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/py39-cryptography ---> Installing py39-cryptography @2.9.2_2 ---> Activating py39-cryptography @2.9.2_2 ---> Cleaning py39-cryptography ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. ---> Some of the ports you installed have notes: py39-cryptography has the following notes: This is a legacy version of cryptography that contains CVE CVE-2020-36242. So, it seams as if on 10.6.8 only an outdated legacy version is available [thinking][thumbs-down] -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Fri Dec 17 08:13:10 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Fri, 17 Dec 2021 09:13:10 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> Message-ID: <213b2f3a-4608-3c84-434c-2c59f2b9fd39@mathiesen.info> Marius Schamschula wrote: > What does > > port installed py39-openssl > > say? On my machine I get 21.00.0_0. > > Also, IIRC there was a change in py-cryptography versioning. On my > machine I have 35.0.0_3. > > Mixing pip with MacPorts will guarantee a broken installation within > weeks.if not within days. > > Marius > -- > Marius Schamschula less $( port file py39-cryptography ) gives : set cryptography_darwin_min_ver 13 # legacy support if {${python.version} eq 27 || ${os.platform} eq "darwin" && ${os.major} < ${cryptography_darwin_min_ver}} { github.setup pyca cryptography 2.9.2 revision 2 So for my System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 it looks af if I'm toast -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Fri Dec 17 08:19:57 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Fri, 17 Dec 2021 09:19:57 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> Message-ID: <55cf0599-e4ba-abec-82dc-05d1e460ef48@mathiesen.info> My work-around for now is to do the admin on my System Version: macOS 10.15.7 (19H1519) Kernel Version: Darwin 19.6.0 and then rsync to the server : /opt/local/bin/rsync \ -aHv \ -e 'ssh -p 22022 -i ~bjarne/.ssh/id_rsa.minier' \ /opt/local/etc/letsencrypt/ \ root at miniserver.local:/opt/local/etc/letsencrypt -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From jmr at macports.org Fri Dec 17 08:38:57 2021 From: jmr at macports.org (Joshua Root) Date: Fri, 17 Dec 2021 19:38:57 +1100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <55cf0599-e4ba-abec-82dc-05d1e460ef48@mathiesen.info> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> <55cf0599-e4ba-abec-82dc-05d1e460ef48@mathiesen.info> Message-ID: <80595fd1-563e-2f11-f351-e16d6ce90b9c@macports.org> On 2021-12-17 19:19 , Bjarne D Mathiesen wrote: > My work-around for now is to do the admin on my > System Version: macOS 10.15.7 (19H1519) > Kernel Version: Darwin 19.6.0 > and then rsync to the server : > > /opt/local/bin/rsync \ > -aHv \ > -e 'ssh -p 22022 -i ~bjarne/.ssh/id_rsa.minier' \ > /opt/local/etc/letsencrypt/ \ > root at miniserver.local:/opt/local/etc/letsencrypt > For simple use cases, acme-tiny may be a better alternative to certbot: - Josh From macintosh at mathiesen.info Fri Dec 17 11:29:52 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Fri, 17 Dec 2021 12:29:52 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <80595fd1-563e-2f11-f351-e16d6ce90b9c@macports.org> References: <96772908-0105-ac79-ac3d-de75d9106399@mathiesen.info> <6C59B819-ECCC-4C65-84D5-8B0F30F13AF2@schamschula.com> <55cf0599-e4ba-abec-82dc-05d1e460ef48@mathiesen.info> <80595fd1-563e-2f11-f351-e16d6ce90b9c@macports.org> Message-ID: <95355dce-0808-6f29-a1a1-04e2fa8cf85e@mathiesen.info> Joshua Root wrote: > For simple use cases, acme-tiny may be a better alternative to certbot: > > My use case is complicated : https://github.com/BjarneDM/letsencrypt-gratisdns I've got (lots of) * domains, so I have to modify dns TXT records. I've had to write my own functions to interface with my dns provider. Certificate Name: mathiesen.info Serial Number: 44550aa094ab2669e53545744b46f42aa49 Key Type: RSA Domains: mathiesen.info *.mathiesen.info *.dtu.mathiesen.info *.magento.mathiesen.info *.typo3.mathiesen.info *.zbc.mathiesen.info Expiry Date: 2022-02-12 22:19:13+00:00 (VALID: 57 days) Certificate Path: /opt/local/etc/letsencrypt/live/mathiesen.info/fullchain.pem Private Key Path: /opt/local/etc/letsencrypt/live/mathiesen.info/privkey.pem -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From ken.cunningham.webuse at gmail.com Sat Dec 18 02:17:23 2021 From: ken.cunningham.webuse at gmail.com (Ken Cunningham) Date: Fri, 17 Dec 2021 18:17:23 -0800 Subject: [10.6.8] certbot & pyOpenSSL problems Message-ID: <7C6D3695-475A-4497-92CA-0B1BEA477FE8@gmail.com> > System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 It appears that you are running a 10.6.8 system (on a macmini, I think I saw?) and I think you appear to be using it as a server for various things. In another spot, I see that it is a 32bit EFI Mac: > platform: macOS-10.6.8-i386-64bit If you are not using for much else beyond being a server, I thought I would let you know that this tiny like c program: https://github.com/demonicsweaters/make_single_eltorito.c that compiles in 10 seconds or so, will slightly modify an Ubuntu 64 bit installer image to properly boot a 32bit EFI Mac, and you can then install Ubuntu 64 bit on there. Once it is installed, you?re good to go, and you can use 64bit software everywhere, including any 64 bit software you download rather than get from the main repo, like Spotify, Google Chrome, etc. I have this now running on 3 older Macs with 32bit EFI, and it works just beautifully. And if you are just using that as a server, you would be most likely many miles ahead to be running Ubuntu 20.04 with webmin than trying to keep teasing SnowLeopard along as a server. Just my $0.02 for whatever. Ken (PS - dual booting a MacOSX install of 10.6 or 10.7 works just fine too, using ReFIND: https://www.rodsbooks.com/refind/ ) From jonesc at hep.phy.cam.ac.uk Sat Dec 18 14:17:24 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Sat, 18 Dec 2021 14:17:24 +0000 Subject: deleting -DNDEBUG added by cmake PG In-Reply-To: <6317520D-36D8-4C08-A0F8-FEA094EE2DDF@macports.org> References: <6317520D-36D8-4C08-A0F8-FEA094EE2DDF@macports.org> Message-ID: Hi > On 17 Dec 2021, at 12:14 am, Kurt Hindenburg wrote: > > ?Hello, > The cmake PG adds -DNDEBUG to various flags. For the next release of ipbt I need to remove it. Just curious but why ? Its usual to specify these flags in production releases builds, which by default is what macports provides. > The normal configure.*-delete do not seem to work. > Does anyone have suggestions on how to do this? > > configure.cflags-append -DNDEBUG > configure.cxxflags-append -DNDEBUG > > https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/cmake-1.1.tcl Just enable by default in your port the debug variant https://github.com/macports/macports-ports/blob/51edfec902a1281823f9dcd9fbaa48b44d62b29d/_resources/port1.0/group/cmake-1.1.tcl#L309 As effectively thats what you are wanting to do, provide a debug build by default. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Sat Dec 18 14:42:05 2021 From: jmr at macports.org (Joshua Root) Date: Sun, 19 Dec 2021 01:42:05 +1100 Subject: deleting -DNDEBUG added by cmake PG In-Reply-To: References: <6317520D-36D8-4C08-A0F8-FEA094EE2DDF@macports.org> Message-ID: On 2021-12-19 01:17 , Chris Jones wrote: > Hi > >> On 17 Dec 2021, at 12:14 am, Kurt Hindenburg >> wrote: >> >> ?Hello, >> ? The cmake PG adds -DNDEBUG to various flags. For?the next release of >> ipbt I need to remove it. > > Just curious but why ? Its usual to specify these flags in production > releases builds, which by default is what macports provides. > >> ?The normal configure.*-delete do not seem to work. >> Does anyone have suggestions on how to do this? >> >> configure.cflags-append ????-DNDEBUG >> configure.cxxflags-append ??-DNDEBUG Well the opposite of -D is -U, but as Chris implied, it would be helpful to know the details of the problem you are trying to solve. - Josh (BTW, please replace the old macosforge.org list address with the current macports.org version in your address book.) From macintosh at mathiesen.info Sun Dec 19 14:41:11 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Sun, 19 Dec 2021 15:41:11 +0100 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <7C6D3695-475A-4497-92CA-0B1BEA477FE8@gmail.com> References: <7C6D3695-475A-4497-92CA-0B1BEA477FE8@gmail.com> Message-ID: <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> Ken Cunningham wrote: >> System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 > > It appears that you are running a 10.6.8 system (on a macmini, I think I saw?) Correct, I've got three of those : PowerMac10,1 w/ PowerPC 7447A (G4) Presently, I don't use it MacMini1,1 (originally Intel Core Duo 1.66 GHz) MacMini2,1 both of these have been upgraded to Intel Core 2 Duo 2 GHz 4 GB RAM although the MacMini1,1 is only able to see 2 GB [crying] and the MacMini2,1 can only use 3 GB of the 4 GB All of them have 2 x original OWC miniStack w/ the HDs in AppleRAID-1 > and I think you appear to be using it as a server for various things. Correct - they have the full xAMP stack Apache 2.4 - MySQL 5.7 - PHP 8.1 Postfix - Dovecot - sqlgrey > > In another spot, I see that it is a 32bit EFI Mac: > >> platform: macOS-10.6.8-i386-64bit Also correct > > If you are not using for much else beyond being a server, I thought I would let you know that this tiny like c program: > > https://github.com/demonicsweaters/make_single_eltorito.c > > that compiles in 10 seconds or so, will slightly modify an Ubuntu 64 bit installer image to properly boot a 32bit EFI Mac, and you can then install Ubuntu 64 bit on there. > > Once it is installed, you?re good to go, and you can use 64bit software everywhere, including any 64 bit software you download rather than get from the main repo, like Spotify, Google Chrome, etc. > > I have this now running on 3 older Macs with 32bit EFI, and it works just beautifully. And if you are just using that as a server, you would be most likely many miles ahead to be running Ubuntu 20.04 with webmin than trying to keep teasing SnowLeopard along as a server. > > Just my $0.02 for whatever. [thumbs-up][nerd] Thank you for the hint [nerd][thumbs-up] Presently, I'm very much satisfied with my setup, but going to Linux on them is definitely one of the options I'm considering if I get into too many problems w/ being up-to-date. This is the 1st really serious problem I've had where I've had to abandon the MacMini for an alternative solution. Of course, not being able to upgrade to MySQL 8 is a bit of a nuisance, but not something I'm presently worrying about. One reason, I'm staying on 10.6.8 is that I really like Spaces. I'm (primarily) using Remote Desktop to admin them as they are "head-less". Another reason not going the Linux way is, that I find the macOS desktop to be far superior to the Linux desktops. > > Ken > > (PS - dual booting a MacOSX install of 10.6 or 10.7 works just fine too, using ReFIND: https://www.rodsbooks.com/refind/ ) > Thanks. One reason to originally staying on 10.6.8 was that the MacMini1,1 isn't able to go to 10.7 without some hacking - at least not before upgrading the CPU. And I like to keep them at par on the software as the MacMini1,1 is my testing platform and backup. -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From ken.cunningham.webuse at gmail.com Sun Dec 19 16:39:28 2021 From: ken.cunningham.webuse at gmail.com (Ken Cunningham) Date: Sun, 19 Dec 2021 08:39:28 -0800 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> References: <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> Message-ID: <46969132-f040-a082-69bf-17881e16767b@gmail.com> I used this set of instructions and the tool referenced in the first comment myself: https://www.youtube.com/watch?v=EJA4OUIDa7Q to upgrade the firmware in a macmini 1,1 to 2,1, to allow it to see the rest of the installed RAM. It was, for me, very quick and very painless. As you noted, many macOS systems of this vintage (and other makes using the same Intel chipsets) can only use a little over 3GB of the 4GB of RAM due to hardware addressing constraints, even when running other operating systems like linux. Best, Ken From jasonliu at umich.edu Sun Dec 19 18:19:41 2021 From: jasonliu at umich.edu (Jason Liu) Date: Sun, 19 Dec 2021 13:19:41 -0500 Subject: [10.6.8] certbot & pyOpenSSL problems In-Reply-To: <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> References: <7C6D3695-475A-4497-92CA-0B1BEA477FE8@gmail.com> <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> Message-ID: > > One reason, I'm staying on 10.6.8 is that I really like Spaces. I'm > (primarily) using Remote Desktop to admin them as they are "head-less". > Another reason not going the Linux way is, that I find the macOS > desktop to be far superior to the Linux desktops. > You might be surprised. There have been a lot of advancements in terms of Linux desktop polish, and you can even turn your entire desktop environment into an (almost) exact clone of macOS' behavior, including Expos? and Spaces, and even the application dock along the bottom. If you've ever heard of Linus Tech Tips, they're even currently doing a multi-part video series on "daily computing and gaming on Linux by a couple of people who have never used Linux" challenge. -- Jason Liu On Sun, Dec 19, 2021 at 9:41 AM Bjarne D Mathiesen wrote: > Ken Cunningham wrote: > >> System Version: Mac OS X 10.6.8 (10K549) Kernel Version: Darwin 10.8.0 > > > > It appears that you are running a 10.6.8 system (on a macmini, I think I > saw?) > > Correct, I've got three of those : > PowerMac10,1 w/ PowerPC 7447A (G4) > Presently, I don't use it > > MacMini1,1 (originally Intel Core Duo 1.66 GHz) > MacMini2,1 > both of these have been upgraded to > Intel Core 2 Duo 2 GHz > 4 GB RAM > although the MacMini1,1 is only able to see 2 GB [crying] > and the MacMini2,1 can only use 3 GB of the 4 GB > > All of them have 2 x original OWC miniStack w/ the HDs in AppleRAID-1 > > > > and I think you appear to be using it as a server for various things. > > Correct - they have the full xAMP stack > Apache 2.4 - MySQL 5.7 - PHP 8.1 > Postfix - Dovecot - sqlgrey > > > > > In another spot, I see that it is a 32bit EFI Mac: > > > >> platform: macOS-10.6.8-i386-64bit > > Also correct > > > > > If you are not using for much else beyond being a server, I thought I > would let you know that this tiny like c program: > > > > https://github.com/demonicsweaters/make_single_eltorito.c > > > > that compiles in 10 seconds or so, will slightly modify an Ubuntu 64 bit > installer image to properly boot a 32bit EFI Mac, and you can then install > Ubuntu 64 bit on there. > > > > Once it is installed, you?re good to go, and you can use 64bit software > everywhere, including any 64 bit software you download rather than get from > the main repo, like Spotify, Google Chrome, etc. > > > > I have this now running on 3 older Macs with 32bit EFI, and it works > just beautifully. And if you are just using that as a server, you would be > most likely many miles ahead to be running Ubuntu 20.04 with webmin than > trying to keep teasing SnowLeopard along as a server. > > > > Just my $0.02 for whatever. > > [thumbs-up][nerd] Thank you for the hint [nerd][thumbs-up] > > Presently, I'm very much satisfied with my setup, but going to Linux on > them is definitely one of the options I'm considering if I get into too > many problems w/ being up-to-date. This is the 1st really serious > problem I've had where I've had to abandon the MacMini for an > alternative solution. Of course, not being able to upgrade to MySQL 8 is > a bit of a nuisance, but not something I'm presently worrying about. > > One reason, I'm staying on 10.6.8 is that I really like Spaces. > I'm (primarily) using Remote Desktop to admin them as they are "head-less". > > Another reason not going the Linux way is, that I find the macOS desktop > to be far superior to the Linux desktops. > > > > > Ken > > > > (PS - dual booting a MacOSX install of 10.6 or 10.7 works just fine too, > using ReFIND: https://www.rodsbooks.com/refind/ ) > > > > Thanks. > One reason to originally staying on 10.6.8 was that the MacMini1,1 isn't > able to go to 10.7 without some hacking - at least not before upgrading > the CPU. And I like to keep them at par on the software as the > MacMini1,1 is my testing platform and backup. > > -- > Bjarne D Mathiesen > Kors?r ; Danmark ; Europa > ----------------------------------------------------------------------- > denne besked er skrevet i et totalt M$-frit milj? > MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina > 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM > ATI Radeon RX 590 8 GB > -------------- next part -------------- An HTML attachment was scrubbed... URL: From macintosh at mathiesen.info Mon Dec 20 02:19:36 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 03:19:36 +0100 Subject: [10.6.8] MacMini1,1 firmware In-Reply-To: <46969132-f040-a082-69bf-17881e16767b@gmail.com> References: <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> <46969132-f040-a082-69bf-17881e16767b@gmail.com> Message-ID: Ken Cunningham wrote: > I used this set of instructions and the tool referenced in the first > comment myself: > > https://www.youtube.com/watch?v=EJA4OUIDa7Q > > to upgrade the firmware in a macmini 1,1 to 2,1, to allow it to see the > rest of the installed RAM. It was, for me, very quick and very painless. [nerd] dosdude to the resque !!! [grinning] I've used his pathcers for many years !!! [nerd] OK - I've upgraded the firmware in my MacMini1,1 [thumbs-up] [thinking] BUT it can still only see 2 GB of the 4 GB RAM installed, so I guess my board is so early that it's impossible to get more [crying] -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Mon Dec 20 02:32:26 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 03:32:26 +0100 Subject: [10.6.8] Linux alternatives In-Reply-To: References: <7C6D3695-475A-4497-92CA-0B1BEA477FE8@gmail.com> <4fd21761-0bdb-0d1a-ccbd-d20a721af35b@mathiesen.info> Message-ID: Jason Liu wrote: > One reason, I'm staying on 10.6.8 is that I really like Spaces.?I'm > (primarily) using Remote Desktop to admin them as they are "head-less". > > > Another reason not going the Linux way is, that I find the macOS > desktop?to be far superior to the Linux desktops. > > > You might be surprised. There have been a lot of advancements in terms > of Linux desktop polish, and you can even turn your entire desktop > environment into an (almost) exact clone of macOS' behavior, including > Expos? and Spaces, and even the application dock along the bottom. I know that - & I've looked at eg Elementary OS which more-or-less looks like an exact clone of macOS. I even installed it on an iMac5,1 for my brothers grandchild. As far as could tell, that iMac would ever be able to run macOS 10.8 (hacked) and as it should run as a normal computer it had to be switched to Linux as 10.7 & 10.8 are hoplessly outdated regarding browsers. > > If you've ever heard of Linus Tech Tips, they're even currently doing a > multi-part video series on "daily computing and gaming on Linux by a > couple of people who have never used Linux" challenge. I've been following him & his staff on-and-off for years. His vidoes on eg selfbuilt NAS systems are really good. And that 4-part series where he installed a water-cooled Hackintosh in an original cMacPro case is hilarious [rolf] -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From khindenburg at macports.org Mon Dec 20 03:31:48 2021 From: khindenburg at macports.org (Kurt Hindenburg) Date: Sun, 19 Dec 2021 22:31:48 -0500 Subject: deleting -DNDEBUG added by cmake PG In-Reply-To: <26466CA0-FB0C-4CCF-AEFA-79FB49463C31@macports.org> References: <6317520D-36D8-4C08-A0F8-FEA094EE2DDF@macports.org> <26466CA0-FB0C-4CCF-AEFA-79FB49463C31@macports.org> Message-ID: <27768C98-36CE-4CBE-8931-5458EA8293B0@macports.org> I think my original email didn?t get sent. Kurt > On Dec 18, 2021, at 9:52 AM, Kurt Hindenburg wrote: > > The new version of ipbt imported a lot of code from putty and is now cmake based. Currently the build fails with the below. > > ipbt-20211203.104f822/defs.h:22:2: error: Do not compile this code base with NDEBUG defined! > #error Do not compile this code base with NDEBUG defined! > > Kurt > >> On Dec 18, 2021, at 9:42 AM, Joshua Root > wrote: >> >> On 2021-12-19 01:17 , Chris Jones wrote: >>> Hi >>>> On 17 Dec 2021, at 12:14 am, Kurt Hindenburg > wrote: >>>> >>>> ?Hello, >>>> The cmake PG adds -DNDEBUG to various flags. For the next release of ipbt I need to remove it. >>> Just curious but why ? Its usual to specify these flags in production releases builds, which by default is what macports provides. >>>> The normal configure.*-delete do not seem to work. >>>> Does anyone have suggestions on how to do this? >>>> >>>> configure.cflags-append -DNDEBUG >>>> configure.cxxflags-append -DNDEBUG >> >> Well the opposite of -D is -U, but as Chris implied, it would be helpful to know the details of the problem you are trying to solve. >> >> - Josh >> >> (BTW, please replace the old macosforge.org list address with the current macports.org version in your address book.) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From macintosh at mathiesen.info Mon Dec 20 13:18:15 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:18:15 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell Message-ID: Please bear with me ... This is the 1st post of several describing my [wink]desparate[wink] attempts to get MySQL 5.7.36_1 to compile. It might be described as a bug-repoert, but I'm unsure as to what I'll have to include in a such due to the complexity. There'll be some time between each of my post, as it takes some time for a compile to finish on a MacMini2,1 -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Mon Dec 20 13:24:21 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:24:21 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: 1st attempt : #=> port outdated The following installed ports are outdated: mysql57 5.7.35_0 < 5.7.36_1 root at MiniWeb 14:04:24 ~ #=> port -d -cuNp upgrade mysql57 [ 17%] Built target base64_test make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build" && /usr/bin/make -j2 -w all VERBOSE=ON Exit code: 2 Error: Failed to build mysql57: command execution failed DEBUG: Error code: CHILDSTATUS 8365 2 DEBUG: Backtrace: command execution failed while executing "system {*}$notty {*}$callback {*}$nice $fullcmdstring" invoked from within "command_exec -callback portprogress::target_progress_callback build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/main.log for details. DEBUG: Registry error: protobuf-cpp not registered as installed & active. So, it seems to complain about missing protobuf-cpp -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Mon Dec 20 13:34:54 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:34:54 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: <8274a8fd-ecad-b585-8333-6b77230f5328@mathiesen.info> 2nd Attempt ----------- DEBUG: Registry error: protobuf-cpp not registered as installed & active. root at MiniWeb 14:24:01 ~ #=> port clean --work mysql57 ---> Cleaning mysql57 root at MiniWeb 14:26:05 ~ #=> port -cuNp install protobuf-cpp ---> Computing dependencies for protobuf-cpp ---> Dependencies to be installed: autoconf automake ---> Fetching archive for autoconf ---> Attempting to fetch autoconf-2.71_1.darwin_10.noarch.tbz2 from http://cph.dk.packages.macports.org/autoconf ---> Attempting to fetch autoconf-2.71_1.darwin_10.noarch.tbz2.rmd160 from http://cph.dk.packages.macports.org/autoconf ---> Installing autoconf @2.71_1 ---> Activating autoconf @2.71_1 ---> Cleaning autoconf ---> Fetching archive for automake ---> Attempting to fetch automake-1.16.5_0.darwin_10.noarch.tbz2 from http://cph.dk.packages.macports.org/automake ---> Attempting to fetch automake-1.16.5_0.darwin_10.noarch.tbz2.rmd160 from http://cph.dk.packages.macports.org/automake ---> Installing automake @1.16.5_0 ---> Activating automake @1.16.5_0 ---> Cleaning automake ---> Fetching archive for protobuf-cpp ---> Attempting to fetch protobuf-cpp-2.6.1_0.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/protobuf-cpp ---> Attempting to fetch protobuf-cpp-2.6.1_0.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/protobuf-cpp ---> Installing protobuf-cpp @2.6.1_0 ---> Activating protobuf-cpp @2.6.1_0 ---> Cleaning protobuf-cpp root at MiniWeb 14:27:10 ~ #=> port -d -cuNp upgrade mysql57 DEBUG: configure phase started at Mon Dec 20 14:29:08 CET 2021 ---> Configuring mysql57 DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4 DEBUG: Using compiler 'MacPorts Clang 9.0' DEBUG: Executing proc-pre-org.macports.configure-configure-0 Error: mysql57 cannot be built while protobuf-cpp is active. Error: Please forcibly deactivate protobuf-cpp, e.g. by running: Error: Error: sudo port -f deactivate protobuf-cpp Error: Error: Then try again. You can reactivate protobuf-cpp again later. Error: Failed to configure mysql57: protobuf-cpp is active DEBUG: Error code: NONE DEBUG: Backtrace: protobuf-cpp is active while executing "$pre $targetname" Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/main.log for details. DEBUG: Registry error: protobuf3-cpp not registered as installed & active. So, now I've got : 1) It can see protobuf-cpp; but complains about it being active which contradicts the original error-message somewhat 2) and now it furthermore complains about protobuf3-cpp -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Mon Dec 20 13:40:43 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:40:43 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: <90927d49-1ecb-1252-a183-94c785002a58@mathiesen.info> 3rd attempt ----------- root at MiniWeb 14:36:29 ~ #=> port -f deactivate protobuf-cpp ---> Deactivating protobuf-cpp @2.6.1_0 ---> Cleaning protobuf-cpp root at MiniWeb 14:36:37 ~ #=> port -cuNp install protobuf3-cpp ---> Computing dependencies for protobuf3-cpp ---> Fetching archive for protobuf3-cpp ---> Attempting to fetch protobuf3-cpp-3.17.3_0.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/protobuf3-cpp ---> Attempting to fetch protobuf3-cpp-3.17.3_0.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/protobuf3-cpp ---> Installing protobuf3-cpp @3.17.3_0 ---> Activating protobuf3-cpp @3.17.3_0 ---> Cleaning protobuf3-cpp ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. root at MiniWeb 14:37:10 ~ #=> port clean --work mysql57 ---> Cleaning mysql57 root at MiniWeb 14:37:38 ~ #=> port -d -cuNp upgrade mysql57 DEBUG: configure phase started at Mon Dec 20 14:39:17 CET 2021 ---> Configuring mysql57 DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4 DEBUG: Using compiler 'MacPorts Clang 9.0' DEBUG: Executing proc-pre-org.macports.configure-configure-0 Error: mysql57 cannot be built while protobuf3-cpp is active. Error: Please forcibly deactivate protobuf3-cpp, e.g. by running: Error: Error: sudo port -f deactivate protobuf3-cpp Error: Error: Then try again. You can reactivate protobuf3-cpp again later. Error: Failed to configure mysql57: protobuf3-cpp is active DEBUG: Error code: NONE DEBUG: Backtrace: protobuf3-cpp is active while executing "$pre $targetname" Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/main.log for details. DEBUG: Registry error: boost not registered as installed & active. -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From jonesc at hep.phy.cam.ac.uk Mon Dec 20 13:42:00 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Mon, 20 Dec 2021 13:42:00 +0000 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: <8274a8fd-ecad-b585-8333-6b77230f5328@mathiesen.info> References: <8274a8fd-ecad-b585-8333-6b77230f5328@mathiesen.info> Message-ID: protobuf-cpp and protobuf3-cpp are two different ports? anyway, looks like you have got your registry into a screwy state in someway, to get DEBUG: Registry error: protobuf3-cpp not registered as installed & active. try installing protobuf3-cpp (i.e. with a 3?) and then see what happens. > On 20 Dec 2021, at 1:34 pm, Bjarne D Mathiesen wrote: > > 2nd Attempt > ----------- > > DEBUG: Registry error: protobuf-cpp not registered as installed & active. > > root at MiniWeb 14:24:01 ~ > #=> port clean --work mysql57 > ---> Cleaning mysql57 > > root at MiniWeb 14:26:05 ~ > #=> port -cuNp install protobuf-cpp > ---> Computing dependencies for protobuf-cpp > ---> Dependencies to be installed: autoconf automake > ---> Fetching archive for autoconf > ---> Attempting to fetch autoconf-2.71_1.darwin_10.noarch.tbz2 from > http://cph.dk.packages.macports.org/autoconf > ---> Attempting to fetch autoconf-2.71_1.darwin_10.noarch.tbz2.rmd160 > from http://cph.dk.packages.macports.org/autoconf > ---> Installing autoconf @2.71_1 > ---> Activating autoconf @2.71_1 > ---> Cleaning autoconf > ---> Fetching archive for automake > ---> Attempting to fetch automake-1.16.5_0.darwin_10.noarch.tbz2 from > http://cph.dk.packages.macports.org/automake > ---> Attempting to fetch automake-1.16.5_0.darwin_10.noarch.tbz2.rmd160 > from http://cph.dk.packages.macports.org/automake > ---> Installing automake @1.16.5_0 > ---> Activating automake @1.16.5_0 > ---> Cleaning automake > ---> Fetching archive for protobuf-cpp > ---> Attempting to fetch protobuf-cpp-2.6.1_0.darwin_10.x86_64.tbz2 > from http://cph.dk.packages.macports.org/protobuf-cpp > ---> Attempting to fetch > protobuf-cpp-2.6.1_0.darwin_10.x86_64.tbz2.rmd160 from > http://cph.dk.packages.macports.org/protobuf-cpp > ---> Installing protobuf-cpp @2.6.1_0 > ---> Activating protobuf-cpp @2.6.1_0 > ---> Cleaning protobuf-cpp > > root at MiniWeb 14:27:10 ~ > #=> port -d -cuNp upgrade mysql57 > > DEBUG: configure phase started at Mon Dec 20 14:29:08 CET 2021 > ---> Configuring mysql57 > DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 > macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 > macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4 > DEBUG: Using compiler 'MacPorts Clang 9.0' > DEBUG: Executing proc-pre-org.macports.configure-configure-0 > Error: mysql57 cannot be built while protobuf-cpp is active. > Error: Please forcibly deactivate protobuf-cpp, e.g. by running: > Error: > Error: sudo port -f deactivate protobuf-cpp > Error: > Error: Then try again. You can reactivate protobuf-cpp again later. > Error: Failed to configure mysql57: protobuf-cpp is active > DEBUG: Error code: NONE > DEBUG: Backtrace: protobuf-cpp is active > while executing > "$pre $targetname" > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/main.log > for details. > DEBUG: Registry error: protobuf3-cpp not registered as installed & active. > > So, now I've got : > > 1) It can see protobuf-cpp; > but complains about it being active > which contradicts the original error-message somewhat > 2) and now it furthermore complains about protobuf3-cpp > > -- > Bjarne D Mathiesen > Kors?r ; Danmark ; Europa > ----------------------------------------------------------------------- > denne besked er skrevet i et totalt M$-frit milj? > MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina > 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM > ATI Radeon RX 590 8 GB -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From macintosh at mathiesen.info Mon Dec 20 13:45:54 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:45:54 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: <88ccb774-7ff5-29c3-bddb-02cfe138744b@mathiesen.info> 4th attempt ----------- root at MiniWeb 14:41:16 ~ #=> port -f deactivate protobuf3-cpp ---> Deactivating protobuf3-cpp @3.17.3_0 ---> Cleaning protobuf3-cpp root at MiniWeb 14:41:27 ~ #=> port -cuNp install boost ---> Computing dependencies for boost ---> Dependencies to be installed: boost176 lzma ---> Fetching archive for lzma ---> Attempting to fetch lzma-4.65_1.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/lzma ---> Attempting to fetch lzma-4.65_1.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/lzma ---> Installing lzma @4.65_1 ---> Activating lzma @4.65_1 ---> Cleaning lzma ---> Fetching archive for boost176 ---> Attempting to fetch boost176-1.76.0_2+no_single+no_static+python39.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/boost176 ---> Attempting to fetch boost176-1.76.0_2+no_single+no_static+python39.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/boost176 ---> Installing boost176 @1.76.0_2+no_single+no_static+python39 ---> Activating boost176 @1.76.0_2+no_single+no_static+python39 ---> Cleaning boost176 ---> Fetching archive for boost ---> Attempting to fetch boost-1.76_0.darwin_10.x86_64.tbz2 from http://cph.dk.packages.macports.org/boost ---> Attempting to fetch boost-1.76_0.darwin_10.x86_64.tbz2.rmd160 from http://cph.dk.packages.macports.org/boost ---> Installing boost @1.76_0 ---> Activating boost @1.76_0 ---> Cleaning boost ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. ---> Some of the ports you installed have notes: lzma has the following notes: The LZMA SDK program is installed as "lzma_alone", to avoid conflict with LZMA Utils root at MiniWeb 14:42:48 ~ #=> port clean --work mysql57 ---> Cleaning mysql57 root at MiniWeb 14:43:20 ~ #=> port -d -cuNp upgrade mysql57 DEBUG: configure phase started at Mon Dec 20 14:44:46 CET 2021 ---> Configuring mysql57 DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4 DEBUG: Using compiler 'MacPorts Clang 9.0' DEBUG: Executing proc-pre-org.macports.configure-configure-0 Error: mysql57 cannot be built while boost is active. Error: Please forcibly deactivate boost, e.g. by running: Error: Error: sudo port -f deactivate boost Error: Error: Then try again. You can reactivate boost again later. Error: Failed to configure mysql57: boost is active DEBUG: Error code: NONE DEBUG: Backtrace: boost is active -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From jonesc at hep.phy.cam.ac.uk Mon Dec 20 13:51:44 2021 From: jonesc at hep.phy.cam.ac.uk (Christopher Jones) Date: Mon, 20 Dec 2021 13:51:44 +0000 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: <88ccb774-7ff5-29c3-bddb-02cfe138744b@mathiesen.info> References: <88ccb774-7ff5-29c3-bddb-02cfe138744b@mathiesen.info> Message-ID: <1E14271F-612F-475B-ADC0-C39599368C04@hep.phy.cam.ac.uk> > > DEBUG: configure phase started at Mon Dec 20 14:44:46 CET 2021 > ---> Configuring mysql57 > DEBUG: Preferred compilers: macports-clang-9.0 macports-clang-8.0 > macports-clang-7.0 macports-clang-6.0 macports-clang-5.0 > macports-clang-11 macports-clang-10 macports-clang-3.7 macports-clang-3.4 > DEBUG: Using compiler 'MacPorts Clang 9.0' > DEBUG: Executing proc-pre-org.macports.configure-configure-0 > Error: mysql57 cannot be built while boost is active. > Error: Please forcibly deactivate boost, e.g. by running: > Error: > Error: sudo port -f deactivate boost > Error: > Error: Then try again. You can reactivate boost again later. > Error: Failed to configure mysql57: boost is active > DEBUG: Error code: NONE > DEBUG: Backtrace: boost is active and? did you try following the instructions above ? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1930 bytes Desc: not available URL: From macintosh at mathiesen.info Mon Dec 20 13:56:50 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 14:56:50 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: 5th attempt ----------- root at MiniWeb 14:46:03 ~ #=> port -f deactivate boost ---> Deactivating boost @1.76_0 ---> Cleaning boost root at MiniWeb 14:46:14 ~ #=> port clean --work mysql57 ---> Cleaning mysql57 root at MiniWeb 14:46:32 ~ #=> port -d -cuNp upgrade mysql57 [ 17%] Built target base64_test make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/work/build" && /usr/bin/make -j2 -w all VERBOSE=ON Exit code: 2 Error: Failed to build mysql57: command execution failed DEBUG: Error code: CHILDSTATUS 12856 2 DEBUG: Backtrace: command execution failed while executing "system {*}$notty {*}$callback {*}$nice $fullcmdstring" invoked from within "command_exec -callback portprogress::target_progress_callback build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql57/mysql57/main.log for details. DEBUG: Registry error: protobuf-cpp not registered as installed & active. root at MiniWeb 14:54:32 ~ #=> port installed protobuf-cpp The following ports are currently installed: protobuf-cpp @2.6.1_0 So, now we are in a catch22 situation And this is as far as I've been able to get -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From macintosh at mathiesen.info Mon Dec 20 14:17:33 2021 From: macintosh at mathiesen.info (Bjarne D Mathiesen) Date: Mon, 20 Dec 2021 15:17:33 +0100 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: I've got the main.log files for the following attempts root at MiniWeb 14:56:09 ~ #=> ls -l MySQL57/ total 3728 -rw-r--r-- 1 root wheel 922159 20 Dec 14:23 attempt_1_main.log -rw-r--r-- 1 root wheel 24827 20 Dec 14:34 attempt_2_main.log -rw-r--r-- 1 root wheel 24785 20 Dec 14:45 attempt_4_main.log -rw-r--r-- 1 root wheel 922174 20 Dec 14:56 attempt_5_main.log and can publish these on my website if needed. If someone wants me to test something, I'll of course do that gladly -- Bjarne D Mathiesen Kors?r ; Danmark ; Europa ----------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit milj? MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM ATI Radeon RX 590 8 GB From reneeotten at macports.org Mon Dec 20 14:42:00 2021 From: reneeotten at macports.org (Renee Otten) Date: Mon, 20 Dec 2021 09:42:00 -0500 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: References: Message-ID: <151F1634-0553-45CE-84B9-E6E7F00C62AC@macports.org> Please don?t use the mailing list for this stuff - Trac is the appropriate medium for this IMHO? > On Dec 20, 2021, at 9:17 AM, Bjarne D Mathiesen wrote: > > I've got the main.log files for the following attempts > > root at MiniWeb 14:56:09 ~ > #=> ls -l MySQL57/ > total 3728 > -rw-r--r-- 1 root wheel 922159 20 Dec 14:23 attempt_1_main.log > -rw-r--r-- 1 root wheel 24827 20 Dec 14:34 attempt_2_main.log > -rw-r--r-- 1 root wheel 24785 20 Dec 14:45 attempt_4_main.log > -rw-r--r-- 1 root wheel 922174 20 Dec 14:56 attempt_5_main.log > > and can publish these on my website if needed. > > If someone wants me to test something, I'll of course do that gladly > > -- > Bjarne D Mathiesen > Kors?r ; Danmark ; Europa > ----------------------------------------------------------------------- > denne besked er skrevet i et totalt M$-frit milj? > MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina > 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM > ATI Radeon RX 590 8 GB From jonesc at hep.phy.cam.ac.uk Mon Dec 20 18:03:20 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Mon, 20 Dec 2021 18:03:20 +0000 Subject: [10.6.8] MySQL 5.7.36_1 compile hell In-Reply-To: <151F1634-0553-45CE-84B9-E6E7F00C62AC@macports.org> References: <151F1634-0553-45CE-84B9-E6E7F00C62AC@macports.org> Message-ID: > On 20 Dec 2021, at 2:42 pm, Renee Otten wrote: > > ?Please don?t use the mailing list for this stuff - Trac is the appropriate medium for this IMHO? Agreed. Please open a trac ticket and post any logs you wish to share there. > > > >> On Dec 20, 2021, at 9:17 AM, Bjarne D Mathiesen wrote: >> >> I've got the main.log files for the following attempts >> >> root at MiniWeb 14:56:09 ~ >> #=> ls -l MySQL57/ >> total 3728 >> -rw-r--r-- 1 root wheel 922159 20 Dec 14:23 attempt_1_main.log >> -rw-r--r-- 1 root wheel 24827 20 Dec 14:34 attempt_2_main.log >> -rw-r--r-- 1 root wheel 24785 20 Dec 14:45 attempt_4_main.log >> -rw-r--r-- 1 root wheel 922174 20 Dec 14:56 attempt_5_main.log >> >> and can publish these on my website if needed. >> >> If someone wants me to test something, I'll of course do that gladly >> >> -- >> Bjarne D Mathiesen >> Kors?r ; Danmark ; Europa >> ----------------------------------------------------------------------- >> denne besked er skrevet i et totalt M$-frit milj? >> MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina >> 2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM >> ATI Radeon RX 590 8 GB > From jerryyhom at gmail.com Wed Dec 22 14:40:57 2021 From: jerryyhom at gmail.com (Jerry) Date: Wed, 22 Dec 2021 06:40:57 -0800 Subject: security certificate Message-ID: <53cc1d96-4daf-0417-592c-acf9eade6b3a@gmail.com> Hi. I would like to ask a favor of someone who has access to a v10.7 and v10.8 system. Could you please tell me if a security certificate[1] exists on each system? It was created after v10.6 was released, but I am not sure when it was added. Thanks in advance! [1] Starfield Services Root Certificate Authority - G2 From ryandesign at macports.org Fri Dec 24 07:08:07 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 24 Dec 2021 01:08:07 -0600 Subject: security certificate In-Reply-To: <53cc1d96-4daf-0417-592c-acf9eade6b3a@gmail.com> References: <53cc1d96-4daf-0417-592c-acf9eade6b3a@gmail.com> Message-ID: On Dec 22, 2021, at 08:40, Jerry wrote: > > Hi. I would like to ask a favor of someone who has access to a v10.7 and v10.8 system. Could you please tell me if a security certificate[1] exists on each system? It was created after v10.6 was released, but I am not sure when it was added. Thanks in advance! > > [1] Starfield Services Root Certificate Authority - G2 I checked on our buildbot worker machines and I do see that certificate in Keychain Access on Mac OS X 10.6.8, 10.7.5, and 10.8.5. From ryandesign at macports.org Sat Dec 25 16:47:44 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 25 Dec 2021 10:47:44 -0600 Subject: Change your ports' gettext dependencies! Message-ID: <237A9AB8-0F6A-46FF-8D20-4424A5C55A0B@macports.org> Hi! If you maintain (or work on updating, or review a PR that updates) a port that depends on the gettext internationalization library (libintl.dylib): depends_lib-append port:gettext Please change it to: depends_build-append port:gettext depends_lib-append port:gettext-runtime This is necessary to ensure that gettext's library is installed for the correct architectures when other ports are installed (i.e. that it is rebuilt with the universal variant when needed). See: https://trac.macports.org/ticket/64291 Since this is a change of library dependencies this change should be accompanied by a revision increase but since there are hundreds of ports that need this change, changing all affected ports at once would take too much build time on the buildbot, so please combine this change with any existing version or revision update of a port. Background: The gettext port used to provide all of the parts of gettext but with the gettext 0.21 update it was split into several subports. The gettext port now only provides build utilities while the main library is now in the gettext-runtime port. For this reason the gettext port now specifies "installs_libs no", which assists with distributability but also disables the architecture checking that we desire for the library. Therefore you must depend directly on gettext-runtime which provides the libraries so that arch checking is performed. There are also two new libraries - libasprintf.dylib and libtextstyle.dylib - now provided by gettext in separate subports libasprintf and libtextstyle. If your port uses these new libraries, declare library dependencies directly on those ports as needed. Three libraries that the gettext tools use internally - libgettextlib.dylib, libgettextpo.dylib and libgettextsrc.dylib - are provided by the gettext-tools-libs port. I don't know of any ports that need these libraries directly, but if your does, declare a library dependency directly on this port. From ryandesign at macports.org Sun Dec 26 20:06:24 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 26 Dec 2021 14:06:24 -0600 Subject: Change your ports' gettext dependencies! In-Reply-To: <237A9AB8-0F6A-46FF-8D20-4424A5C55A0B@macports.org> References: <237A9AB8-0F6A-46FF-8D20-4424A5C55A0B@macports.org> Message-ID: <158405D8-24BA-4C4D-AC3E-78885DA58ED2@macports.org> On Dec 25, 2021, at 10:47, Ryan Schmidt wrote: > Hi! If you maintain (or work on updating, or review a PR that updates) a port that depends on the gettext internationalization library (libintl.dylib): > > depends_lib-append port:gettext > > Please change it to: > > depends_build-append port:gettext > depends_lib-append port:gettext-runtime > > This is necessary to ensure that gettext's library is installed for the correct architectures when other ports are installed (i.e. that it is rebuilt with the universal variant when needed). > > See: https://trac.macports.org/ticket/64291 Josh has pointed out in the ticket that not all ports need the gettext build dependency. Those that use auto(re)conf do, and select others may as well. The remaining ports may be able to just use the gettext-runtime library dependency. Please use your best judgement (and, for example, testing by using trace mode) in deciding how to update your ports' gettext dependencies. From jmr at macports.org Tue Dec 28 13:28:36 2021 From: jmr at macports.org (Joshua Root) Date: Wed, 29 Dec 2021 00:28:36 +1100 Subject: Python updates, news, and policy Message-ID: <5cc2aa5e-45c3-8c67-9dec-40c332559631@macports.org> Here are a few Python-related FYIs and one proposal to solidify our policy. Python 3.6 reached end-of-life as of 2021-12-23. Please feel free to start removing use of it from ports, and accelerate removal of use of 3.5 and older. But *please* remember to only remove py36 subports (and indeed any ports) *after* they have no remaining dependents. Python upstream has switched to an annual release cycle[1]. This means that new major versions will always be released in October going forward. I propose that we sync up with this schedule and change the default Python version in MacPorts, i.e. the default value of python.default_version in the python portgroup and the recommended default variant for ports that offer pythonXY variants, to the latest upstream release every year on the 1st of January, unless there are known issues that would make this significantly problematic. This timing means that the new major version will have had its first bugfix release for a few weeks, giving time for evaluation; plus it has the advantage of being easy to remember. :) Setuptools has deprecated 'setup.py install', which is currently the default installation method used by the python portgroup. It still works fine for now, but at some unspecified point in the future it will be going away, so all ports using the portgroup need to start being migrated to use the new PEP 517 style builds. This is done by setting 'python.pep517 yes' in the Portfile. That option is only supported with Python 3.6 and newer, so ports that still support older pythons will need to set it conditionally based on the python version. Setting python.pep517 will add dependencies on an appropriate build front-end automatically, but each port will need to specify its dependencies for the back-end used by the project being built. Most will use setuptools, but others may use different back-ends such as flit or poetry. Unfortunately, setuptools alone is not sufficient to do a pep517 build, and any ports that use setuptools as their pep517 back-end will need to additionally depend on pyXY-wheel. You also can't just build with distutils in a PEP 517 world (and distutils will also be disappearing from the stdlib in a future Python release.) So anything currently relying on distutils (i.e. no dependencies but pythonXY) will need to add dependencies on setuptools and wheel. - Josh [1] https://www.python.org/dev/peps/pep-0602/ From reneeotten at macports.org Tue Dec 28 14:14:35 2021 From: reneeotten at macports.org (Renee Otten) Date: Tue, 28 Dec 2021 09:14:35 -0500 Subject: Python updates, news, and policy In-Reply-To: <5cc2aa5e-45c3-8c67-9dec-40c332559631@macports.org> References: <5cc2aa5e-45c3-8c67-9dec-40c332559631@macports.org> Message-ID: <05B1BA9B-D041-4EF9-9657-D2B1B46DB101@macports.org> Thanks Josh - sounds good to me. I am just wondering whether it would be worthwhile to add one more variable to the python PG, perhaps ?python.pep517_backend? that would support the commonly used backends you mentioned (perhaps defaulting to setuptools) and add its required dependencies? Renee > On Dec 28, 2021, at 8:28 AM, Joshua Root wrote: > > Here are a few Python-related FYIs and one proposal to solidify our policy. > > Python 3.6 reached end-of-life as of 2021-12-23. Please feel free to start removing use of it from ports, and accelerate removal of use of 3.5 and older. But *please* remember to only remove py36 subports (and indeed any ports) *after* they have no remaining dependents. > > Python upstream has switched to an annual release cycle[1]. This means that new major versions will always be released in October going forward. I propose that we sync up with this schedule and change the default Python version in MacPorts, i.e. the default value of python.default_version in the python portgroup and the recommended default variant for ports that offer pythonXY variants, to the latest upstream release every year on the 1st of January, unless there are known issues that would make this significantly problematic. This timing means that the new major version will have had its first bugfix release for a few weeks, giving time for evaluation; plus it has the advantage of being easy to remember. :) > > Setuptools has deprecated 'setup.py install', which is currently the default installation method used by the python portgroup. It still works fine for now, but at some unspecified point in the future it will be going away, so all ports using the portgroup need to start being migrated to use the new PEP 517 style builds. This is done by setting 'python.pep517 yes' in the Portfile. That option is only supported with Python 3.6 and newer, so ports that still support older pythons will need to set it conditionally based on the python version. > > Setting python.pep517 will add dependencies on an appropriate build front-end automatically, but each port will need to specify its dependencies for the back-end used by the project being built. Most will use setuptools, but others may use different back-ends such as flit or poetry. > > Unfortunately, setuptools alone is not sufficient to do a pep517 build, and any ports that use setuptools as their pep517 back-end will need to additionally depend on pyXY-wheel. You also can't just build with distutils in a PEP 517 world (and distutils will also be disappearing from the stdlib in a future Python release.) So anything currently relying on distutils (i.e. no dependencies but pythonXY) will need to add dependencies on setuptools and wheel. > > - Josh > > [1] https://www.python.org/dev/peps/pep-0602/ From jmr at macports.org Wed Dec 29 01:43:43 2021 From: jmr at macports.org (Joshua Root) Date: Wed, 29 Dec 2021 12:43:43 +1100 Subject: Python updates, news, and policy In-Reply-To: <0100017e028bbb20-b7962a40-b7d6-4fed-803c-25f24acdd03f-000000@email.amazonses.com> References: <5cc2aa5e-45c3-8c67-9dec-40c332559631@macports.org> <0100017e028bbb20-b7962a40-b7d6-4fed-803c-25f24acdd03f-000000@email.amazonses.com> Message-ID: On 2021-12-29 06:36 , Jeremy Lavergne wrote: > Do we know how this may impact test phase? For example, `setup.py test` Only the install command is deprecated in setuptools, so other commands like test should continue to work fine, for projects that ship a setup.py. Projects don't have to have a setup.py though, and in that case tests need to be run with an alternative command depending on the test framework used by the project. 'python -m pytest' would be one example. - Josh From jmr at macports.org Wed Dec 29 03:40:49 2021 From: jmr at macports.org (Joshua Root) Date: Wed, 29 Dec 2021 14:40:49 +1100 Subject: Python updates, news, and policy In-Reply-To: <05B1BA9B-D041-4EF9-9657-D2B1B46DB101@macports.org> References: <5cc2aa5e-45c3-8c67-9dec-40c332559631@macports.org> <05B1BA9B-D041-4EF9-9657-D2B1B46DB101@macports.org> Message-ID: <0c74b506-4c2c-04c9-5156-693c287cd091@macports.org> On 2021-12-29 01:14 , Renee Otten wrote: > I am just wondering whether it would be worthwhile to add one more variable to the python PG, perhaps ?python.pep517_backend? that would support the commonly used backends you mentioned (perhaps defaulting to setuptools) and add its required dependencies? Good idea. Implemented in . - Josh From mark at macports.org Wed Dec 29 16:24:22 2021 From: mark at macports.org (Mark Anderson) Date: Wed, 29 Dec 2021 11:24:22 -0500 Subject: iTerm 2 Discussion Message-ID: >From iTerm2 dev: "Running is supported on 10.14 but building is only ever supported on the most recent released version of Xcode." This situation has caused me no end of trouble - I kinda wish I could have the build bots build a version that runs on supported version The other idea I have is to build where I can (11 and 12), and then download from our stuff, and just download the binary that works for 10.15 - 10.n from gnachman himself. I'm building one that uses the XCode portgroup but once again - trying to fix bugs in versions I don't have and can't build has become problematic. I'm just kinda fishing for ideas here, since I would like to keep iTerm2 as a working MacPort and not give up on getting it to work most places. ?Mark _______________________ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile -------------- next part -------------- An HTML attachment was scrubbed... URL: From mascguy at rochester.rr.com Wed Dec 29 18:27:50 2021 From: mascguy at rochester.rr.com (Christopher Nielsen) Date: Wed, 29 Dec 2021 13:27:50 -0500 Subject: gcc11-devel and our buildbots Message-ID: It seems like we?re updating this port at least weekly. With the result being that our Intel buildbots are routinely bogged down for a long time, sometimes as long as 4-5 hours. While I understand that we want to follow upstream?s progress - particularly for the ARM version - is this really necessary for Intel? From mascguy at rochester.rr.com Wed Dec 29 18:30:22 2021 From: mascguy at rochester.rr.com (Christopher Nielsen) Date: Wed, 29 Dec 2021 13:30:22 -0500 Subject: gcc11-devel and our buildbots In-Reply-To: References: Message-ID: <554344C1-19A8-47D9-8AEE-8C8FA1B06302@rochester.rr.com> > It seems like we?re updating this port at least weekly. With the result being that our Intel buildbots are routinely bogged down for a long time, sometimes as long as 4-5 hours. > > While I understand that we want to follow upstream?s progress - particularly for the ARM version - is this really necessary for Intel? The reality is even worse, as libgcc-devel takes as long to build - if not longer - than gcc-devel. So net-net, our Intel buildbots are routinely being tied up for 8+ hours on each update. Can we please stop this insanity? From ryandesign at macports.org Wed Dec 29 20:37:21 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 29 Dec 2021 14:37:21 -0600 Subject: iTerm 2 Discussion In-Reply-To: References: Message-ID: On Dec 29, 2021, at 10:24, Mark Anderson wrote: > From iTerm2 dev: "Running is supported on 10.14 but building is only ever supported on the most recent released version of Xcode." > > This situation has caused me no end of trouble - I kinda wish I could have the build bots build a version that runs on supported version > > The other idea I have is to build where I can (11 and 12), and then download from our stuff, and just download the binary that works for 10.15 - 10.n from gnachman himself. I'm building one that uses the XCode portgroup but once again - trying to fix bugs in versions I don't have and can't build has become problematic. > > I'm just kinda fishing for ideas here, since I would like to keep iTerm2 as a working MacPort and not give up on getting it to work most places. When they say they need "the most recent released version of Xcode", I assume what they actually need is the MacOSX.sdk from the latest macOS and maybe a recent version of clang. MacPorts already has recent clangs and I have work in progress on adding ports to offer various versions of MacOSX.sdk; let me see if I can get that committed and then I'll see if it helps with iTerm2. Alternately, a builtbot-centric idea: https://trac.macports.org/ticket/60878 From mascguy at rochester.rr.com Thu Dec 30 13:09:59 2021 From: mascguy at rochester.rr.com (Christopher Nielsen) Date: Thu, 30 Dec 2021 08:09:59 -0500 Subject: gcc11-devel and our buildbots References: <217ECA58-89A0-4899-AA85-CE74B836248B@rochester.rr.com> Message-ID: >> It seems like we?re updating this port at least weekly. With the result being that our Intel buildbots are routinely bogged down for a long time, sometimes as long as 4-5 hours. >> >> While I understand that we want to follow upstream?s progress - particularly for the ARM version - is this really necessary for Intel? > > The reality is even worse, as libgcc-devel takes as long to build - if not longer - than gcc-devel. So net-net, our Intel buildbots are routinely being tied up for 8+ hours on each update. After sleeping on this, it?s apparent that my e-mails from yesterday weren?t quite as constructive as one might hope. And they could also be construed as critical, which wasn?t my intention. So let me start with this: I totally respect - and appreciate! - that we?re closely following upstream. Particularly if anyone is using ?gccdevel? for cross-compilation, targeting evolving architectures like RISC-V. (And support for things like the latter are likely occurring at a rapid pace.) That said, I?m wondering whether it might make sense to curb our updates slightly... perhaps limiting them to a twice-monthly update cadence? That would still ensure that we?re able to provide leading-edge toolchain components, without quite as much impact to our buildbot resources. Ultimately, I?m not opposed to weekly updates, particularly if there is a strong need and/or demand for it. But it would help to know how we decide on which commit we choose, when updating such a port. For example, does upstream bless beta releases on a certain day of the week, and/or with certain commits? Etc. Thoughts on all of the above? From jonesc at hep.phy.cam.ac.uk Thu Dec 30 23:41:10 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Thu, 30 Dec 2021 23:41:10 +0000 Subject: gcc11-devel and our buildbots In-Reply-To: References: Message-ID: <64AF0715-F0DA-493A-8B0E-3662E918AFD8@hep.phy.cam.ac.uk> Hi Before arm came along the gccdevel ports indeed did not update that regularly. Normally in the run up to a new major release they might see more activity, as we take a look as to if the upcoming release has any issues, but outside that they perhaps would go a month or two between updates. Arm changed that in that currently its still the version with the best support for that platform, as none of the production releases have official support. I suspect once these stabilise, with a production gcc release with full arm support, we will likely go back to the old update patterns. Chris > On 30 Dec 2021, at 1:10 pm, Christopher Nielsen wrote: > > ? >> >>> It seems like we?re updating this port at least weekly. With the result being that our Intel buildbots are routinely bogged down for a long time, sometimes as long as 4-5 hours. >>> >>> While I understand that we want to follow upstream?s progress - particularly for the ARM version - is this really necessary for Intel? >> >> The reality is even worse, as libgcc-devel takes as long to build - if not longer - than gcc-devel. So net-net, our Intel buildbots are routinely being tied up for 8+ hours on each update. > > After sleeping on this, it?s apparent that my e-mails from yesterday weren?t quite as constructive as one might hope. And they could also be construed as critical, which wasn?t my intention. > > So let me start with this: I totally respect - and appreciate! - that we?re closely following upstream. Particularly if anyone is using ?gccdevel? for cross-compilation, targeting evolving architectures like RISC-V. (And support for things like the latter are likely occurring at a rapid pace.) > > That said, I?m wondering whether it might make sense to curb our updates slightly... perhaps limiting them to a twice-monthly update cadence? That would still ensure that we?re able to provide leading-edge toolchain components, without quite as much impact to our buildbot resources. > > Ultimately, I?m not opposed to weekly updates, particularly if there is a strong need and/or demand for it. But it would help to know how we decide on which commit we choose, when updating such a port. For example, does upstream bless beta releases on a certain day of the week, and/or with certain commits? Etc. > > Thoughts on all of the above? From ryandesign at macports.org Fri Dec 31 09:14:56 2021 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 31 Dec 2021 03:14:56 -0600 Subject: gcc11-devel and our buildbots In-Reply-To: <64AF0715-F0DA-493A-8B0E-3662E918AFD8@hep.phy.cam.ac.uk> References: <64AF0715-F0DA-493A-8B0E-3662E918AFD8@hep.phy.cam.ac.uk> Message-ID: <20E6B741-1DB0-44AF-8E25-C2014342AF8B@macports.org> On Dec 30, 2021, at 17:41, Chris Jones wrote: > Hi > > Before arm came along the gccdevel ports indeed did not update that regularly. They did some years ago. Then for a time they didn't. > Normally in the run up to a new major release they might see more activity, as we take a look as to if the upcoming release has any issues, but outside that they perhaps would go a month or two between updates. Arm changed that in that currently its still the version with the best support for that platform, as none of the production releases have official support. I suspect once these stabilise, with a production gcc release with full arm support, we will likely go back to the old update patterns. Since arm and i386 get different versions of gcc-devel, it would be fine to update the arm version more frequently than the i386 version. From vince at macports.org Fri Dec 31 13:10:09 2021 From: vince at macports.org (Vincent Habchi) Date: Fri, 31 Dec 2021 14:10:09 +0100 Subject: Detecting Apple Silicon (vs. legacy Intel) Message-ID: Folks, finally put my hands on my brand new MacBook Pro 14?! (Well, not really mine, rather my company?s, but let?s pretend?) I was wondering if there is a simple scheme to detect on which type of architecture MacPorts is running. My problem here is that clang on M1 does not honour the -march flag and exits with an error. Thanks and early happy new year to all! Vincent From jonesc at hep.phy.cam.ac.uk Fri Dec 31 17:36:29 2021 From: jonesc at hep.phy.cam.ac.uk (Chris Jones) Date: Fri, 31 Dec 2021 17:36:29 +0000 Subject: Detecting Apple Silicon (vs. legacy Intel) In-Reply-To: References: Message-ID: I > On 31 Dec 2021, at 5:13 pm, Vincent Habchi wrote: > > ?Folks, > > finally put my hands on my brand new MacBook Pro 14?! (Well, not really mine, rather my company?s, but let?s pretend?) > > I was wondering if there is a simple scheme to detect on which type of architecture MacPorts is running. My problem here is that clang on M1 does not honour the -march flag and exits with an error. if {${os.arch} eq "arm"} { ? } > > Thanks and early happy new year to all! > > Vincent > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vince at macports.org Fri Dec 31 17:50:43 2021 From: vince at macports.org (Vincent Habchi) Date: Fri, 31 Dec 2021 18:50:43 +0100 Subject: Detecting Apple Silicon (vs. legacy Intel) In-Reply-To: References: Message-ID: <56E6422E-A2A0-4654-B84F-65121FEC5E4B@macports.org> > On 31 Dec 2021, at 18:36, Chris Jones wrote: > >> I was wondering if there is a simple scheme to detect on which type of architecture MacPorts is running. My problem here is that clang on M1 does not honour the -march flag and exits with an error. > > if {${os.arch} eq "arm"} { > ? > } Thanks Chris! Have a great evening and a wonderful 2022 (let?s hope that this sentence still makes sense?) Vincent