Control: reassign -1 podman-compose Control: affects -1 = src:libpod On Sun, Sep 01, 2024 at 01:08:07PM +0100, James Addison wrote: > In #1054460 a duplicate-file conflict on the podman-compose.1 manual was > resolved: the manual was dropped from the podman binary package and the > version from podman-compose was retained. > > However, invoking the default podman 5.2.1 'compose' subcommand produces > output referring the user to configuration settings only found in the libpod > documentation: > > $ podman compose help > >>>> Executing external compose provider "/usr/bin/podman-compose". Please > see podman-compose(1) for how to disable this message. <<<< > ... > > This tripped me up recently: running 'man -s 1 podman-compose' opened a manual > that seemed to be the one instructed, but that didn't describe the relevant > compose_warning_logs setting to disable the message. > > I'd like to request that we ship the upstream libpod manual[1] instead, and > optionally that we could retain the podman-compose version of the manual in > section 7 (misc). Most installers of podman-compose would be provided with > the > libpod manual thanks to the Recommends dependency that podman-compose has on > libpod.
I actually agree with this, and was also bitten by it recently! It's worth noting that podman-compose upstream does not ship a manpage at all -- this is a Debian modification and divergence from upstream. For podman to ship this manpage again, podman-compose needs to stop shipping it, so reassigning the bug to the podman-compose source package. Athos & other podman-compose contributors, what do you think? Thanks! Faidon _______________________________________________ Pkg-go-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
