On Sat, Feb 22, 2025 at 10:32:08PM -0500, Robert Middleton wrote:
> Should we do a bugfix release of log4cxx soon? We've just had a
> release recently, but we have fixed a few bugs with the fuzzing that
> was just added. I would like to have a good release for Debian 13.
> The soft freeze is Apri
(Just an follow up, not sure if the previous mail went through anyways;
to make sure I'll CC Robert and Piotr, please feel free to forward the
mail if it didn't make it to the list)
Soft Freeze actually starts March 15th, and from this date on
"No large/disruptive changes" are no longer appropiat
t;
> On Fri, Jan 6, 2023 at 7:36 AM Tobias Frost wrote:
> >
> > On Mon, Jan 02, 2023 at 10:45:37PM -0500, Robert Middleton wrote:
> > > Awesome! Thanks for the packaging work that you do. Once we get it
> > > voted on you should have a proper release.
> >
&g
ddleton
>
> On Mon, Jan 2, 2023 at 2:52 PM Tobias Frost wrote:
> >
> > Update:
> >
> > FTP masters have been very quick and approved the package, so the snapshot
> > is
> > already in experimental. [1]
> >
> > I've also rebuilt all reve
xx
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027746
Cheers,
--
tobi
On Sat, Dec 31, 2022 at 10:52:43AM +0100, Tobias Frost wrote:
> On Thu, Dec 29, 2022 at 05:21:34PM -0500, Robert Middleton wrote:
>
> > The last time we talked about this Tobias Frost said that the
> >
On Sat, Dec 31, 2022 at 10:38:37AM -0500, Robert Middleton wrote:
> On Sat, Dec 31, 2022 at 4:22 AM Tobias Frost wrote:
> > The generated file names look strange:
> >
> > Now:
> > tobi@isildor:~/workspace/deb/packages/log4cxx/upstream/log4cxx/debian/tmp/usr/lib/x8
On Thu, Dec 29, 2022 at 05:21:34PM -0500, Robert Middleton wrote:
> The last time we talked about this Tobias Frost said that the
> soft-freeze for Debian is the 12th of January[1], so after that point
> an updated library wouldn't make it into Debian. I would like to get
>
On Fri, Dec 30, 2022 at 12:43:18PM -0500, Robert Middleton wrote:
> On Fri, Dec 30, 2022 at 11:43 AM Tobias Frost wrote:
> > When doing the same against the branch "next_stable", currently at [2]
> > the result is much much worse:
> > https://people.deb
On Fri, Dec 30, 2022 at 10:29:46AM -0500, Robert Middleton wrote:
> On Fri, Dec 30, 2022 at 10:17 AM Tobias Frost wrote:
> >
> > On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote:
> > > IF an SONAME bump is required, it will become more challenging, as othe
On Fri, Dec 30, 2022 at 07:18:46AM +0100, Tobias Frost wrote:
> IF an SONAME bump is required, it will become more challenging, as other
> Debian teams are involved (and other maintainers if it casues breakages in
> reverse dependencies)
> I would basically needs something (it does no
ase was to
> make things ABI stable, so as long as we commit to that going
> forward(and only breaking it with proper versioning) we should be
> good.
>
> The last time we talked about this Tobias Frost said that the
> soft-freeze for Debian is the 12th of January[1], so after
On Sat, Sep 24, 2022 at 09:56:50AM -0400, Robert Middleton wrote:
> Because of the above, I'm inclined to do an 0.13.1 release before the
> end of the year and wait a bit on the next major version before we're
> comfortable with it. Does anybody have any thoughts?
Just a datapoint: Debian 11 ("bo
On Sat, Jan 01, 2022 at 08:38:43PM -0500, Robert Middleton wrote:
> The full path is already in the compiled code anyway, this would
> simply add the ability to get the filename from the full path(so
> another member to the LocationInfo class). I can see certain
> circumstances where it is useful
On Wed, Aug 05, 2020 at 06:08:48PM -0700, Ralph Goers wrote:
> Remember, releases don’t have to be perfect. In practice, you just want them
> to hopefully be better than the prior release.
this SO-NAME bug can create some havoc down the road, especially at
distributions… So I have some interest
On Mon, Aug 03, 2020 at 07:34:15PM -0500, Matt Sicker wrote:
> Very well said! It helps get user feedback quicker, too.
+1!
Also, the current "stable" has some many bugs (I carry 13 non Debian-specific
patches in the current Debian package…) and a new release would also fix some
open
Bugs on the
On Mon, Aug 03, 2020 at 07:49:14PM -0400, Robert Middleton wrote:
> Thorsten,
>
> > > A number of these are rather large changes, so it probably
> > > doesn't make sense to work on them until there's a known-good release, as
> > > they would likely break both API and ABI compatibility.
> >
> > D
On Tue, Mar 03, 2020 at 04:51:28PM +1100, Stephen Webb wrote:
> I would be surprised if any unix distribution would change to 0.11 log4cxx
> if its API is incompatible with 0.10.
With my Debian maintainer hat on:
This is nothing special and day to day businesss with distos:
It will "just" invok
Hi,
I think this was discussed already earlier on this mailing list (but I
cannot find the reference atm), so I'd like to nag again about a new
release of liblog4cxx, as the last release was 10 years ago and there
have been many improvements since then.
I'd like to update the package in Debian (
Hi,
Sorry for being late for the party (I was just checking if there is a
new release for liblog4cxx, which I would really apprecicate when I
came about this thread)
Robert Middleton wrote on Tue, 25 Jul 2017 19:11:09 -0700:
> It's more of an expected behavior - when people download an autotool
19 matches
Mail list logo
