Description of problem:
system-config-printer does not allow browsing for samba printers if python3-smbc package is not installed. The 'Browse' button in samba printer config dialog is disabled if python-3-smbc package is missing.
Also system-config-printer wrongly reports that is requires 'pysmbc' package instead of python3-smbc (see the tooltip on the 'Browse' button when it is disabled).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Steps to Reproduce:
Fedora has just added python3-smbc as a Suggests to the libs subpackage, so we can do the same. pysmbc is the name of the software, so it's actually not wrong; it's not meant to match the package name.
(In reply to David Walser from comment #1)
> pysmbc is the name of the software, so it's actually
> not wrong; it's not meant to match the package name.
But this name would completely confuse users. Mageia is a user friendly linux distribution, right? I think it should match the package name. This would allow users to find the required package with rpmdrake easily.
That would be the matter for a separate bug report, but will probably not happen, see our naming conventions: https://wiki.mageia.org/en/Python_policy#Naming_Conventions
FWIW, this issue was also reported via forums:
(In reply to Oleg Bosis from comment #2)
> (In reply to David Walser from comment #1)
> > pysmbc is the name of the software, so it's actually
> > not wrong; it's not meant to match the package name.
> But this name would completely confuse users. Mageia is a user friendly
> linux distribution, right? I think it should match the package name. This
> would allow users to find the required package with rpmdrake easily.
No, that message is the program saying which Python module it failed to find. It is from upstream and they have no way of knowing for sure what downstream is going to call the package that contains it. It should be a non-issue once the suggests is added and I don't see any value in patching that.
I will add python3-smbc as a Suggests
Done in Cauldron, is an update in Mageia 5 really necessary ?
I don't think so. You could commit it there, and it can be pushed along with the next regular update.
On the 25th of July, Phillipem uploaded the following packages to
@ Anyone reading this:
* If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report.
* If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.
Fixed on 5 and cauldron.
Actually this wasn't fixed for 5 because we never pushed it, but that's OK.