Hi Ralph,
On Fri, 30 Dec 2022 at 21:56, Ralph Goers wrote:
> I am not understanding the format of this table. I expected it to contain a
> list of PRs/Jira issues that were not propagated. Instead it seems to be a
> list of modules and package names. Are we supposed to mark the packages that
>
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.debian.org/~tobi/log4cxx/1_to_next/compat_report
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
> this version into Debi
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/x86_64-linux-gnu$
> ls -la liblog4cxx*
> lrwxrwxrwx 1 tobi tobi 20 Dec 31 08:51 liblog4cxx.so ->
> liblo
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/x86_64-linux-gnu$
> > ls -la liblog
On Sat, Dec 31, 2022 at 1:57 PM Tobias Frost wrote:
> (sorry for being short worded, not having much time right now)
> Please note that library versioning has nothing do do with project versioning,
> don't conflate them… It is a sign of improper library versioning if the
> project has the same ver
