[Pkg-tcltk-devel] Bug#987397: Bug#987397: tcltls: build conflict with openssl requires removal of too many packages

Sergei Golovan sgolovan at gmail.com
Fri Apr 23 11:13:13 BST 2021


Hi Andrej,

On Fri, Apr 23, 2021 at 1:07 PM Andrej Shadura <andrewsh at debian.org> wrote:
>
> Hi,
>
> On Fri, 23 Apr 2021, at 11:21, Sergei Golovan wrote:
> > On Fri, Apr 23, 2021 at 11:27 AM Andrej Shadura <andrewsh at debian.org> wrote:
> > > While trying to build your package from the source in quite a minimal
> > > container, the Build-Conflicts requirement forced the following packages
> > > out:
> > >
> > > > ca-certificates devscripts git-buildpackage libconfig-model-dpkg-perl
> > > > liblwp-protocol-https-perl libsoap-lite-perl libwww-perl libxml-parser-perl
> > > > libxml-sax-expat-perl libxmlrpc-lite-perl openssl osc osc-plugin-dput
> > > > osc-plugins-dput python3-certifi python3-requests
> > >
> > > On my normal system, it forces the removal of 358 packages including a
> > > huge number of my development tools, the editor and parts of the desktop
> > > environment.
> > >
> > > Please implement what this requirement was supposed to accomplish in a
> > > different way not requiring removing openssl.
> >
> > Currently, tcltls conflicts with openssl because it tries to generate
> > DH pair on the fly,
> > which sometimes fails due to lack of entropy on buildds. Though it
> > looks like the
> > newest tcltls allows one to supply option --enable-deterministic and
> > get the same result.
> >
> > I'll fix this bug after the bullseye's release. Thank you for pointing it out.
>
> Thanks. Would you be okay if I went ahead with a team upload with the patch I attached if the release team grant me an unblock?

No, it wouldn't. The point is that there's no need of any patch. An
extra option in debian/rules should be sufficient. I'll try it today
and commit the fix to salsa if it'll work. Or if it won't then I'll
accept your patch.


-- 
Sergei Golovan



More information about the Pkg-tcltk-devel mailing list