Bug 26414

Summary:	perl-Razor-Agent forcing netcat-traditional as a requirement
Product:	Mageia	Reporter:	Muhammad Tailounie <mageia>
Component:	RPM Packages	Assignee:	Pascal Terjan <pterjan>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	shlomif
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	perl-Razor-Agent-2.850.0-25.mga7.src.rpm	CVE:
Status comment:

Description Muhammad Tailounie 2020-04-01 15:03:38 CEST

Trying to install perl-Razor-Agent I had to remove the previously installed netcat-openbsd due to an enforced requirement of netcat-traditional in perl-Razor-Agent package.

I think that either netcat packages should fulfil that requirement so this requirement in perl-Razor-Agent should be changed.

Comment 1 Lewis Smith 2020-04-01 21:39:00 CEST

Thank you for pointing this out.
Certainly at present, 'perl-Razor-Agent' requires 'netcat-traditional'. Can it be made to require either that OR 'netcat-openbsd'. Both packages look extremely similar, and both provide:
 /usr/bin/nc
 /usr/bin/netcat
openbsd: (the program is actually nc)
traditional: (the program is now netcat)

Assigning to Thierry who did the last update to 'perl-Razor-Agent', CC'ing Shlomi.

Source RPM: (none) => perl-Razor-Agent-2.850.0-25.mga7.src.rpm
Assignee: bugsquad => thierry.vignaud
CC: (none) => shlomif

Comment 2 Thierry Vignaud 2020-04-02 10:44:39 CEST

nc is used in %post, changed made by Pascal.
See http://svnweb.mageia.org/packages?view=revision&revision=r1151497
We could just not run razor-admin in post…
And let users rely on /usr/share/doc/perl-Razor-Agent/INSTALL instructions
WDYT?

Assignee: thierry.vignaud => pterjan

Comment 3 Pascal Terjan 2020-04-02 11:57:41 CEST

I had made that change as it was getting stuck forever when trying to install the package on a machine without network access but actually don't know what this package does and how it is used :)

A simpler solution could be echo > /dev/tcp/discovery.razor.cloudmark.com/80 && ...

This will fail immediately if the DNS doesn't work or the connection is refused, but may still block if the packets are silently dropped...

Maybe something like:

( echo > /dev/tcp/discovery.razor.cloudmark.com/80 ) & checkpid=$!
( sleep 5 && kill $pid ) & alarmpid=$!
if wait $checkpid 2>/dev/null; then
    # No error and no timeout, there is networking
    kill $alarmpid
    wait $alarmpid

    %{_bindir}/razor-admin -d -create -home=%{_sysconfdir}/razor
else
    # Network not working
    # Cleanup in case this was a fast failure
    kill $alarmpid
    wait $alarmpid

    echo "You might want to run \"%{_bindir}/razor-admin -d -create -home=%{_sysconfdir}/razor\" when your network works"
fi

Comment 4 Aurelien Oudelet 2021-07-06 13:17:42 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 5 Marja Van Waes 2021-09-07 14:10:48 CEST

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Status: NEW => RESOLVED
Resolution: (none) => OLD