:29 PM Davyd McColl wrote:
Hi all,
This is a vote to release the Apache Log4net 2.0.17.
Website:
https://logging.staged.apache.org/log4net/release/release-notes.html
GitHub: https://github.com/apache/logging-log4net
GitHub release (pre-release):
https://github.com/apache/logging-log4net/releases
build
log4net@2.0.12 clean-build
rimraf build
log4net@2.0.12 build
zarro @
Why does it say log4net@2.0.12 when I am building 2.0.17?
Then the build errors out with https://paste.apache.org/1ropz
I, off course, don't know what I'm doing with .net... ;-)
Gary
On 2024/03/15 12:28:03 Davyd McColl w
Hi all,
This is a vote to release the Apache Log4net 2.0.17.
Website:
https://logging.staged.apache.org/log4net/release/release-notes.html
GitHub: https://github.com/apache/logging-log4net
GitHub release (pre-release):
https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1
the messages already from your email
app, go to lists.apache.org
Gary
On Fri, Mar 8, 2024, 8:59 AM Davyd McColl wrote:
Hi Gary
I'll try to remember that for the future. From memory now, there was
only one person who had any holdups and that was due to outdated build
docs from me - so it should
On 2024/03/08 14:22, Gary Gregory wrote:
Process:
You need to reply to this thread with a [RESULT] prefix, tally all the
votes, and say whether the vote passes or not. It is helpful to note which
votes are binding or not.
Gary
On Fri, Mar 8, 2024, 6:06 AM Davyd McColl wrote:
Hi all
Thanks
, but I don't find it a
blocker. (I have fixed it in `master`.)
On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote:
Hi all
This is the vote to release Apache log4net version 2.0.16
Website:
https://logging.staged.apache.org/log4net/release/release-notes.html
GitHub: https://github.com/apache/lo
gt; > We integrated the new version into our test environment and all manual
tests were successful.
> >
> > Jan
> >
> >> +1
> >
> >> Verified signatures.
> >> Verified hashes.
> >
> >> `NOTICE` contains 2022 as the copyright year,
ows>
Let me know if this does/doesn't help.
Good luck!
On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl wrote:
Hi Volkan
That was my whole point with the question on my release vote: I
have put things in svn, bit I'm not seeing them at the url you've
posted. I assume I've done somethi
svn-for-windows>
Let me know if this does/doesn't help.
Good luck!
On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl wrote:
Hi Volkan
That was my whole point with the question on my release vote: I
have put things in svn, bit I'm not seeing them at the url you've
posted. I assume I'v
://dist.apache.org/repos/dist/dev/logging /log4net` Subversion folder
along with checksum and signature files, please?
On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote:
Hi all
This is the vote to release Apache log4net version 2.0.16
Website:
https://logging.staged.apache.org/log4net/release
Hi all
This is the vote to release Apache log4net version 2.0.16
Website:
https://logging.staged.apache.org/log4net/release/release-notes.html
GitHub: https://github.com/apache/logging-log4net
GitHub release (pre-release):
https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1
Hi Davyd,
On Thu, 29 Feb 2024 at 12:29, Davyd McColl wrote:
Jan, Volkan brings up one of the sticky points - signing the release -
which I can do from my personal
machine, with the binary artifacts in place - so I could do steps 3 and
4 (build and sign) - but I'll only
This is just a curios
whenever needed.
If you say this will make things more difficult, that is also
understandable.
On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl
wrote:
Considering my constrained time, and even though @FreeAndNil
<https://github.com/FreeAndNil> recently stepped up to be a maintainer, I
don't se
Apologies, I responded directly to Volkan instead of the list ):
-d
Forwarded Message
Subject:Re:
Date: Tue, 13 Feb 2024 12:00:05 +0200
From: Davyd McColl
To: Volkan Yazıcı
I'd really like to chuck JIRA in a lake of fire and watch it burn slowly /2c
Welcome Fred!
-d
On 09 February 2024 21:54:45 Fred am Nil wrote:
Hello,
thank you very much for the warm welcome.
I'm looking forward to collaborating with everyone and making meaningful
contributions to the Apache Logging Services projects.
Best regards.
Jan
PPK> Welcome, Jan!
PPK>
Hi
That would be great! I'd really appreciate the help, and I've obviously
seen your prior contributions (: There is a process to follow, so we'll
get that started and get back to you (:
-d
On 2024/01/31 13:01, Fred am Nil wrote:
Hi,
as proposed by Volkan Yazıcı in
?
On Wed, Nov 1, 2023 at 1:20 PM Davyd McColl wrote:
Hi
Yes, I'd agree that log4net is "at risk" seeing as I'm apparently
the only active maintainer - and I'm not even that active, having
not found time in quite a while to do some log4net work ):
-d
On 2023/1
Ralph, I'd appreciate any help here. Seems there's a permissions error or
something - sdk docs links return a 403.
-d
On 16 November 2022 23:22:26 Alex Winfield <7nil...@gmail.com> wrote:
Where should I look for the docs?
All of the examples point to dead links:
Hi all
Thanks for the votes, 2.0.15 is now live.
-d
On Aug 4 2022, at 5:14 am, Davyd McColl wrote:
>
> Hi Ralph
> Yes, I'll release as soon as I get a gap. I replied to the signing request
> too - not sure what happened to 2.0.14, but every other release is signed.
> The si
Middleton
On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl
wrote:
Hi all
It's been a while, but I've finally tied together some work in a 2.0.15
release for log4net. An rc tag is up at GitHub with details:
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.15-rc1
I've pushed docs
his vote.
> >>
> >> I'll take a look at it in a bit just to validate that the signatures
> >> are good, as I know nothing about .net development.
> >>
> >> -Robert Middleton
> >>
> >> On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl
> >&g
; I'll take a look at it in a bit just to validate that the signatures
> >> are good, as I know nothing about .net development.
> >>
> >> -Robert Middleton
> >>
> >> On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl
> >> wrote:
> >>>
>
Hi all
It's been a while, but I've finally tied together some work in a 2.0.15 release
for log4net. An rc tag is up at GitHub with details:
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.15-rc1
I've pushed docs to staging as well as binaries to
Hi Vladimir
Yes, you're correct that the event log appender isn't available in the
netstandard version of log4net because it's not cross-platform.
Right now, I don't have capacity to build one (I have outstanding work I'd like
to do in log4net as it is), so the best suggestions I can give are:
hread in the mailing list, rather than creating a new thread on
each response?
Thank you guys
Denis
From: Davyd McColl mailto:dav...@gmail.com]>
Sent: Tuesday, February 22, 2022 3:29 PM
To: dev@logging.apache.org [mailto:dev@logging.apache.org]
Cc: Petker Denis 8BM3 mailto:denis.pet...@r
e would then be provided to LoggingEvent objects
> > from whatever is creating them?
> >
> >
> > -Original Message-
> > From: Davyd McColl
> > Sent: Monday, February 21, 2022 6:43 PM
> > To: dev@logging.apache.org; Petker Denis 8BM3 <
> &g
's Place of Business: München, Registereintrag /
Commercial Register No.: HRB 7 534, Umsatzsteuer-Identifikationsnummer
(USt-IdNr.) / VAT Identification No.: DE 130 256 683, Elektro-Altgeräte
Register (EAR) / WEEE Register No.: DE 240 437 86
From: Davyd McColl
Sent: Tuesday, February 22, 2022
for the remaining runtime? In order to be backward compatible, we then
still need to maintain the UserName property in the LoggingEvent class I guess.
So the username would then be provided to LoggingEvent objects from whatever is
creating them?
-Original Message-
From: Davyd McColl
Sent: Monday
Hi Denis
Thanks for the report (:
I'm happy to review contributions, though for this particular issue, it seems
like the resolution is to cache the resolved user name, rather than allowing
specifying the name via config. The whole point of this property is to log the
username under which the
+1, option 1
Apologies for the delay, took me a while to find the original email.
-d
On December 29, 2021 21:33:35 "Christian Grobmeier"
wrote:
Hello,
as discussed in another thread, this is a vote about the future of log4j 1.
This vote stays open for the usual 72h.
Options are
+1 for accounts per project
-d
On December 31, 2021 01:02:08 Remko Popma wrote:
I also like this idea and agree with separate accounts for each component.
On Fri, Dec 31, 2021 at 7:48 AM Gary Gregory wrote:
Great idea. I would suggest one account for the each component. I'm not
sure
On Dec 28, 2021, at 16:11, Davyd McColl wrote:
Hi Matt, I'm happy to, just need to get the time to do the actually release
(: holiday mode has kicked in good and proper. Can I close out before I
release?
-d
On December 28, 2021 21:37:21 Matt Sicker wrote:
Seems like we have enough votes
:
* old-log4net.snk.gpg has been the old key to sign binaries.
* @Matt, where is the root logging KEYS file located?
The changes in the release look good to me. +1
On Mon, 20 Dec 2021 at 07:34, Davyd McColl wrote:
Thanks Matt
Since you've given a +1, I'll write up some sticky notes
version), contain appropriate LICENSE and NOTICE
(besides the outdated copyright year, but not a blocker), no binaries in
the source zip, appropriate files in the binary zip.
--
Matt Sicker
On Dec 16, 2021, at 07:47, Davyd McColl wrote:
Hi all
I'd like to raise a vote to release log4net
artifacts at GitHub too.
-d
On 2021-12-17 08:28:35, Davyd McColl wrote:
Hi Robert
Binaries are signed with my key, though I remember someone raising that my key
wasn't in a known area last time, so I'd appreciate help with that. I had a key
signing party with Ralph and Matt quite a long time ago
the log4net site? I would like to verify that the log4net website
looks good in staging.
Cheers
Dominik
On Thu, 16 Dec 2021 at 15:09, Davyd McColl
wrote:
Hi all
I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the
pre-release page at
https://github.com/apache/logging-log4net
it signed with?
-Robert Middleton
On Thu, Dec 16, 2021 at 8:47 AM Davyd McColl wrote:
Hi all
I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the
pre-release page at
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.14-rc1
I have updated staging docs and I _t
Hi all
I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the
pre-release page at
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.14-rc1
I have updated staging docs and I _think_ I've done the right thing with
respect to getting binaries and source up to
Hi all
I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the
pre-release page at
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.14-rc1
I have updated staging docs and I _think_ I've done the right thing with
respect to getting binaries and source up to the
Hi Joe
No, it shouldn't, particularly because we're very different projects, on
very different platforms, and I understand that the log4j vuln is largely
linked to a _dependency_ of log4j. The closest we've had was an xml vuln
that was patched some time ago.
That being said, I'm currently
Thanks Ralph, appreciated.
-d
On November 7, 2021 09:54:55 Ralph Goers wrote:
I have committed the release files to
https://dist.apache.org/repos/dist/release/logging/log4net/
Ralph
On Nov 2, 2021, at 8:56 AM, Davyd McColl wrote:
Hi Ralph
Yes. I'd gladly upload them myself if I had
Hi
asf-staging branch merged into asf-site and I can see the latest release notes
are up
Apologies again for missing this.
-d
On 2021/11/05 16:31:41, Davyd McColl wrote:
Apologies - staging docs have not been set live ):
I'll have a look at it now
-d
On 2021/11/05 16:24:55, Volkan Yazıcı
Apologies - staging docs have not been set live ):
I'll have a look at it now
-d
On 2021/11/05 16:24:55, Volkan Yazıcı wrote:
I think this message is best suited for this mailing list.
Would anybody from the log4net crew mind addressing the request of John
Bigler, please?
-- Forwarded
wrote:
How do I download the files from there?
Ralph
On Nov 1, 2021, at 11:12 PM, Davyd McColl wrote:
Hi
Thanks all for the +1's; please can someone with access copy the binaries
from the GitHub release (I've renamed to
https://github.com/apache/logging-log4net/releases/tag/rel%2F2.0.13
download the files from there?
Ralph
> On Nov 1, 2021, at 11:12 PM, Davyd McColl wrote:
>
> Hi
>
> Thanks all for the +1's; please can someone with access copy the binaries
> from the GitHub release (I've renamed to
> https://github.com/apache/logging-log4net/rele
Hi again
2.0.13 is up on nuget, so the only missing piece of the puzzle is the build
artifacts to be up on download.apache.org, whenever someone has a gap to assist.
Thanks for the vote (:
-d
On 2021/11/02 08:13:08, Davyd McColl wrote:
Hi
Thanks all for the +1's; please can someone
[Vote] Release log4net 2.0.13-rc2
>
> +1
>
> Ralph
>
>> On Oct 31, 2021, at 5:52 AM, Robert Middleton wrote:
>>
>> Looks good to me.
>>
>> +1
>>
>> -Robert Middleton
>>
>> On Fri, Oct 29, 2021 at 6:08 PM Davyd McColl wrote:
>>>
&g
Thank-you Remko
-d
Sent from Mailspring (https://getmailspring.com/), the best free email app for
work
On Oct 29 2021, at 11:04 pm, Remko Popma wrote:
> +1
>
> On Sat, Oct 30, 2021 at 2:13 AM Davyd McColl
> wrote:
>
> > Hi
> >
> > I'd like to raise
Hi
I'd like to raise a vote to release log4net 2.0.13 (this is an rc2 where the
only difference is the archive layout for the associated source and binary
artifacts)
- there's an rc up at GitHub with release notes:
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.13-rc2
-
Thanks Matt
I'm cancelling this vote in deference to the new one.
-d
On October 29, 2021 17:21:09 Matt Sicker wrote:
Just reply to the old vote thread with a message saying you’re cancelling
the vote.
On Oct 29, 2021, at 9:29 AM, Davyd McColl wrote:
Hi Ralph
I'm not sure how
apologize for not replying earlier.
Ralph
> On Oct 28, 2021, at 12:48 AM, Davyd McColl wrote:
>
> Update: I've added a 2.0.13 RC2 release at GitHub with the suggested
> modifications to release artifacts (source and binary zips). The released
> functionality remains unchanged.
>
Update: I've added a 2.0.13 RC2 release at GitHub with the suggested
modifications to release artifacts (source and binary zips). The released
functionality remains unchanged.
-d
On 2021/10/28 08:49:23, Davyd McColl wrote:
Hi Robert
Thanks for checking all these things and feeding back to me
for logging, so I can't
check that: https://www.apache.org/dist/logging/KEYS
-Robert Middleton
On Wed, Oct 27, 2021 at 2:10 AM Davyd McColl
wrote:
>
> Hi
>
> I'd like to raise a vote to release log4net 2.0.13
>
> - there's an rc up at GitHub with release notes:
> https://gith
Hi
I'd like to raise a vote to release log4net 2.0.13
- there's an rc up at GitHub with release notes:
https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.13
- documentation is updated on staging:
https://logging.staged.apache.org/log4net/
I do, however, require some assistance
. In fact, let me know if there is anything I can do for log4net in
general. Always wanted to be part of an open source project in a more real way.
Thanks
David
-Original Message-
From: Davyd McColl
Sent: Sunday, October 24, 2021 4:07 PM
To: dev@logging.apache.org
Subject: [EXTERNAL] Re: Fix
Hi
I'll try get some time to look at this this week. There's another small fix
I'd like to make and I've been putting it off because the release process
is such a mission (the apache way of doing things - unlike my libraries
which I can just release, log4net has to go through a vote and
to
create a new repo. But before doing that I would create a confluence page to
lay out the initial requirements and design.
If you can’t create a repo and would like one I can certainly help with that.
Ralph
> On Jun 30, 2021, at 12:44 PM, Davyd McColl wrote:
>
> I'm rather new to go, bu
I'm rather new to go, but looking for ways to improve by writing code
alongside people who actually know what they're doing. If I can help,
please ping me.
-d
On June 30, 2021 18:12:46 Christofer Dutz wrote:
Hi all,
and sorry for being late to the party ;-)
I am currently working hard
Hi Matt
log4net has been quite quiet over the last quarter, partly because I took a
break from all things code for a month, and partly because I'm still trying to
pick up momentum after that break!
However, there has been minor movement at GitHub, and your mail has reminded me
to get back on
Thanks Ralph
-d
On October 26, 2020 18:48:30 Ralph Goers wrote:
The files were added to the distribution directory.
Ralph
On Oct 26, 2020, at 9:22 AM, Ralph Goers wrote:
OK
+1 to these.
Ralph
On Oct 26, 2020, at 8:57 AM, Davyd McColl wrote:
Ralph, here's the 2.0.12 thread where
Hi all
I'd like to announce the release of log4net 2.0.12, which resolves issues
LOG4NET-652 AND LOG4NET-653, both of which are related to correctly
retrieving the username for the current thread, which would throw an
exception on non-win32 platforms.
The site is up, nupkg is released,
Ralph, here's the 2.0.12 thread where Matt and Remko voted.
-d
On October 23, 2020 17:57:31 Davyd McColl wrote:
Thanks Matt
I think I need 3 to release... Any other takers?
-d
On October 23, 2020 17:33:19 Matt Sicker wrote:
It seems I forgot to add my +1 here.
On Mon, 19 Oct 2020
a hiccup :|
-d
On 2020/10/26 16:35:46, Davyd McColl wrote:
Hi Matt
Thanks, I still forget some of the dots and crosses ):
-d
On 2020/10/26 16:20:58, Matt Sicker wrote:
Yes, an email confirming the vote passed along with the tally. Then,
after everything has been uploaded and mirrored, we can send
Oct 2020 at 06:58, Davyd McColl wrote:
>
> By results, I understand you mean a tally? There were only three votes, all
> positive. I've pushed the nupkg.
>
> -d
>
>
> On October 26, 2020 13:35:15 Apache wrote:
>
> > You need to close the vote thread with th
PM, Davyd McColl wrote:
Thanks Ralph
Could you assist with getting artifacts up to downloads.apache.org? I'm
going to push the nupkg because people are waiting on it, and will have to
set the new documentation live because people will expect it, but right
now, the download links are broken
01:21:15, Ralph Goers wrote:
My +1
Ralph
> On Sep 22, 2020, at 11:21 PM, Davyd McColl wrote:
>
> Thanks all; I've completed the release as far as I can (Ralph, please push
> the relevant artifacts from
> https://github.com/apache/logging-log4net/releases/tag/rel%2F2.0.11 t
Hi Dominik
iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user
name on !win32, is waiting on one more +1 vote for release.
-d
On October 23, 2020 18:05:18 Dominik Psenner wrote:
See the message below.
--
Sent from my phone.
-- Forwarded message -
Thanks Matt
I think I need 3 to release... Any other takers?
-d
On October 23, 2020 17:33:19 Matt Sicker wrote:
It seems I forgot to add my +1 here.
On Mon, 19 Oct 2020 at 01:45, Davyd McColl wrote:
Hi Remko
Yes, this is a vote thread -- thanks for your +1 (:
Matt, I've fortunately
nds, it’s not a release blocker
> at least.
>
>> On Sun, Oct 18, 2020 at 23:14 Davyd McColl wrote:
>>
>> Hi Matt
>>
>> Looks like the culprit is gulp-zip, specifically, the source I see sets
>> mode for files but not folders (with a source comment about why and a l
. :)
On Sun, 18 Oct 2020 at 13:55, Davyd McColl wrote:
Hi Matt
Zip files are created from windows as there are certain targets that Unix
compiles can't hit (specifically < net40 and client profiles), which would
probably explain the permissions. Not a lot I can do about it though, that
I k
t20/log4net.dll
...
The directories need to be executable to be able to list files from
them (Unix/POSIX). I'm not sure how these zip files got these
permissions. I see that the previous 2.0.10 release of log4net has the
same problem, though.
On Sun, 18 Oct 2020 at 11:03, Davyd McColl wrote:
Hi
Hi all
Not much has changed in 2.0.12 except that an issue affecting non-windows users
has been addressed. LOG4NET-652 and LOG4NET-653 both stem from the same source,
wherein the username for the current logging thread was not correctly retrieved
on non-windows platforms and would throw a
:23 Dominik Psenner wrote:
> +1
>
>
>
> --
>
> Sent from my phone. Typos are a kind gift to anyone who happens to find
>
> them.
>
>
>
> On Tue, Sep 22, 2020, 08:37 Davyd McColl wrote:
>
>
>
> > Hi all
>
> >
>
> >
>
> > On Sep 20, 2020, at 1:01 PM, Matt Sicker wrote:
> >
> > I sent a Google Meet invite to you.
> >
> > On Sun, 20 Sep 2020 at 14:26, Davyd McColl wrote:
> >>
> >> I'm happy to be available at 8am my side, if that works for everyone else.
>
Africa is 11pm the night before in Phoenix AZ.
However, I frequently am up until midnight so that could work. 5-5:30 pm is
7:30-8 am in Phoenix. I usually am not in front of my computer on a weekday
until 8 am but on occasion I can do earlier.
Ralph
On Sep 20, 2020, at 9:46 AM, Davyd McColl
could work for exchanging keys. What times would you be available to do
that?
On Sun, Sep 20, 2020 at 03:09 Davyd McColl wrote:
Hi Ralph
I think I miscommunicated: I'm not regenerating my signing key - just the
nuget API key for package upload. This forces me to log in in nuget.org
which has
are
building a web of trust. Sooner or later there will be someone in that web
that you personally know and trust.
Ralph
On Sep 19, 2020, at 11:26 PM, Davyd McColl wrote:
Thanks Matt, I've updated the artifacts on GitHub to have detached
signatures. I had previously also uploaded my key
/logging/KEYS
[3]: https://infra.apache.org/release-signing.html#keys-policy
On Sat, 19 Sep 2020 at 12:48, Davyd McColl wrote:
>
> Thanks Matt, I've done so. Hopefully that makes it easier to verify
> artifacts that I have signed.
>
> -d
>
>
> On September 18, 2020 23:
53, Matt Sicker wrote:
> >
> > Oh sorry, I didn't notice that you uploaded them there (wasn't even
> > aware that it was possible to be honest).
> >
> > On Fri, 18 Sep 2020 at 14:43, Davyd McColl wrote:
> > >
> > > Hi Matt
> > >
> > &
I don't think we've imported that to the KEYS
> file as far as I can tell?
>
> On Fri, 18 Sep 2020 at 15:53, Matt Sicker wrote:
> >
> > Oh sorry, I didn't notice that you uploaded them there (wasn't even
> > aware that it was possible to be honest).
> >
> &g
not
released yet. :)
On Fri, 18 Sep 2020 at 09:05, Davyd McColl wrote:
Hi all
I have another potential release available: 2.0.11, tagged as rc/2.0.11
Changes are really minor:
- fixed assembly versioning (all assemblies should report 2.0.11.0 as their
version now)
- properly dispose
Hi all
I have another potential release available: 2.0.11, tagged as rc/2.0.11
Changes are really minor:
- fixed assembly versioning (all assemblies should report 2.0.11.0 as their
version now)
- properly dispose of StreamWriters within logging appenders (thanks to
@NicholasNoise)
Binaries
Hi all
I have another potential release available: 2.0.11, tagged as rc/2.0.11
Changes are really minor:
- fixed assembly versioning (all assemblies should report 2.0.11.0 as their
version now)
- properly dispose of StreamWriters within logging appenders (thanks to
@NicholasNoise)
Binaries
string for one of the client profile version strings and a
good few places where StreamWriters weren't being disposed, so it's not for
nought)
Thanks again for notifying me.
-d
On 2020/09/18 13:10:26, Davyd McColl wrote:
hm, that's not great ): I'll investigate. Thanks for letting me know!
-d
hm, that's not great ): I'll investigate. Thanks for letting me know!
-d
On 2020/09/18 13:05:58, Dominik Psenner wrote:
See the message below. Apparently something went wrong during the last
release.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
--
>>
>> --
>> Sent from my phone. Typos are a kind gift to anyone who happens to find
>> them.
>>
>> On Fri, Sep 11, 2020, 08:08 Remko Popma wrote:
>>
>>> +1
>>> Remko.
>>>
>>>
>>>
>>> (Shameless plug) Eve
Hi all
I'd like to start (at some point) clearing up JIRA a bit and getting on top of
associated pull requests (for example, the one for a REST appender,
https://issues.apache.org/jira/projects/LOG4NET/issues/LOG4NET-644) and I'd
appreciate any guidance on the accepted methods. To clarify, if
my phone. Typos are a kind gift to anyone who happens to find
them.
On Thu, Sep 10, 2020, 08:48 Davyd McColl wrote:
> Hi
>
> Sorry to be a bother, but I haven't heard anything back on this apart from
> Dominik's inquiry into netstandard 1.3 support. I'd really like to ge
/09/06 20:51:38, Davyd McColl wrote:
Hi all
I'd like to propose a vote to release 2.0.10 of log4net, with:
- updated netstandard 2.0 support from community member NicholasNoise
- cherry-picked fix for CVE-2018-1285 (I had to modify slightly since the
mechanism used there is outdated
for netstandard 2.0 users
Thanks
-d
On 2020/09/07 21:15:42, Davyd McColl wrote:
Hi Dominik
No, it doesn't. Netstandard 2.0 support is added in addition to the existing
netstandard 1.3 target.
Whilst I'd really like to diminish the target list of the package (particularly
the client profile
2020, 9:59 PM Davyd McColl wrote:
Thanks! I'm surprised that you had the experience you had, because those
environments are very similar to ours at work. May I ask what process you
use to deploy? We use Octopus.
At least if I see the same odd behaviour, I have one more idea to check (:
-d
Enterprise Applications
2195 Hearst Avenue, 250-29
Berkeley, CA 94720-4876
510-508-4443
jmit...@berkeley.edu
From: Davyd McColl
Sent: Tuesday, September 8, 2020 1:18 PM
To: Joseph A. MITOLA
Cc: dev@logging.apache.org
Subject: RE: issues with log4net 2.0.9 under IIS for projects using .net
fra
.
Thanks for all your help,
Joseph
Joseph A. Mitola, Information Systems Analyst
University of California, Berkeley
IST - Enterprise Applications
2195 Hearst Avenue, 250-29
Berkeley, CA 94720-4876
510-508-4443
jmit...@berkeley.edu
From: Davyd McColl
Sent: Tuesday, September 8, 2020 11:15 AM
19:08:55 Matt Sicker wrote:
That's this dev list! Though if we need a separate mailing list, we
can always create more.
On Tue, 8 Sep 2020 at 11:54, Davyd McColl wrote:
What if there was another Apache email address that messages were sent to,
and multiple people could observe that account? I
the chain
are expecting a different version or an assembly with a different public key.
-d
On 2020/09/08 18:52:09, Davyd McColl wrote:
Have you tried an assembly rebind to force resolution to 2.0.9?
-d
On September 8, 2020 18:00:45 "Joseph A. MITOLA" wrote:
Hi Davyd,
The w
earst Avenue, 250-29
Berkeley, CA 94720-4876
510-508-4443
jmit...@berkeley.edu
From: Davyd McColl
Sent: Tuesday, September 8, 2020 12:08 AM
To: jmit...@berkeley.edu
Cc: dev@logging.apache.org
Subject: RE: issues with log4net 2.0.9 under IIS for projects using .net
framework 4.5+
Hi Joseph
I've p
and/or the official project website.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Tue, Sep 8, 2020, 08:34 Davyd McColl wrote:
> Ralph
>
> I understand that the emails provide a bit of workload, and I'm trying to
> figure out a solution to help everyone
Hi Joseph
I've performed a (rather belated) upgrade to log4net 2.0.9 on a work project
targeting net462 and, apart from having to perform some assembly rebinds to
handle dependencies which expect log4net 2.0.8, it's working fine with an
ado.net appender and a rolling log file appender, so I'd
, I'd like the situation to be better for both the PMC and users. I'm
open to any suggestions.
-d
On 2020/09/08 07:24:25, Davyd McColl wrote:
Hi Ralph
I'll investigate this today. I'd like more information, particularly
configuration and, eg if the ado.net [http://ado.net] appender is used
Hi Ralph
I'll investigate this today. I'd like more information, particularly
configuration and, eg if the ado.net appender is used, table structures.
Joseph, please open a ticket at
https://issues.apache.org/jira/browse/LOG4NET to help me track this.
-d
On September 7, 2020 23:35:12
1 - 100 of 156 matches
Mail list logo
