On Fri, Jan 24, 2025 at 10:00:10AM +0000, Arif Ali wrote:
> Hi mentors,
>
> I am working on an ITP [1] for avocado, and have an interest in this
> package for testing framework for sosreport, which is a package I am
> maintaining.
>
> However, currently it has various lintian errors, which I am working
> through with upstream at the moment.
>
> We are very close, but want to see where we stand on some of the items.
>
> like some of the following rules are of my concern, as these may take time
> to resolve upstream, and some commands just are helper commands, and don't
> really make sense for man pages.
Helper commands that shouldn't be run by a human probably belong in
libexec, not in $PATH.
> - executable-in-usr-lib
> - repeated-path-segment
> - no-manual-page
>
The key one was, if my first upload had the above 3 lintian issues, would DDs be willing to accept the package on the premise that I can continue to work on the issues upstream, and close these gaps?
> I am already fixing with upstream 2 key items from lintian (see below), and
> have raised with upstream, and won't be uploading before these 2 items as
> we could have potential issues, especially with python3.13 support issues
> with deprecated libs.
>
> - uses-deprecated-python-stdlib
> - bash-term-in-posix-shell (already resolved upstream)
>
> I am keen to get through the initial package in, and can work on the 3
> first bullet points over time while I work with upstream, thoughts?
Sorry, what is your actual question?
--
WBR, wRAR