Hello Tobias,
Just a friendly ping following up on my earlier[1] mail to this bug
report,in case you missed it.
I wanted to know if you've had the chance to work on this ITS/plan to
maintain libconfig going forward. If not, I’d be happy to offer help
maintaining libconfig and handle the upda
Hi Tobias,
I noticed that this ITS bug has been sitting without any activity for
the past 2 years. I needed libconfig 1.7 for a new release of picom, so
I went ahead and prepared a new version which I've been using locally
for some time now. I wanted to reach out and see if you still plan on
Package: libconfig9
Version: 1.5-0.4+b1
Followup-For: Bug #1037313
hi
i would be happy to help in this however it is possible, since a while ago i've
been trying to package the latest release of picom for a while now but stumbled
on a roadblock after noticing that while i could compile the upstr
Hi,
picom[1] now hard depends on libconfig 1.7. So it'd be great if libconfig
was updated in Debian as this will help both in updating the picom package
in debian and others who prefer build/install from source.
[1] - https://github.com/yshui/picom
Regards
Mohd Bilal
Hi Tobias,
On Sun, Jun 11, 2023 at 08:06:41AM +0200, Tobias Frost wrote:
> I'm intending to to salvage libconfig. If you are unaware of the ITS
> procedure,
> see [1] for details.
Thanks for filing this bug. Please go ahead.
I unfortunately don't have the time to maintain libconfig these days,
Source: libconfig
Version: 1.5-0.4
Severity: important
Hi Jonathan,
I'm intending to to salvage libconfig. If you are unaware of the ITS procedure,
see [1] for details.
Eligibility for ITS: [2]
There is no visible maintainer acitvity on the package since 2017, the package
is
NMU maintained sin
6 matches
Mail list logo
