Bug 902649 - yast2-sane still referring to /etc/init.d/xinetd ...
Summary: yast2-sane still referring to /etc/init.d/xinetd ...
Status: RESOLVED DUPLICATE of bug 902680
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: 13.2 RC 1
Hardware: All openSUSE 13.2
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-26 14:11 UTC by Dieter Jurzitza
Modified: 2014-11-01 08:53 UTC (History)
1 user (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Jurzitza 2014-10-26 14:11:54 UTC
Today I installed 13.2 RC1 and had to discover that a bug I had had reported several month ago with regard to 13.1 is still present in 13.2.

This is related to /usr/lib/YaST2/bin/setup_network_scanner_config

the current version from factory (yast2-scanner-3.1.1) still doesn't refer to systemd. So, if you want to set up network scanning yast2 is failing because the call to /etc/init.d/xinetd is failing - what is expected to happen.

Please fix prior to releasing!

Thank you for looking into this,
take care




Dieter Jurzitza
Comment 1 Johannes Meixner 2014-10-27 08:28:40 UTC
It was fixed in bug#859353 and you reported in
https://bugzilla.opensuse.org/show_bug.cgi?id=859353#c11
that it worked for you.

I have no idea why it is no longer working now.

*** This bug has been marked as a duplicate of bug 859353 ***
Comment 2 Dieter Jurzitza 2014-10-27 09:09:30 UTC
Well, I had a look onto the messages and into

/usr/lib/YaST2/bin/setup_network_scanner_config

both the new ones (from 3.1.1) and the ones from the distribution refer to /etc/init.d/xinetd.

And the error - messages being spitted out are caused by exactly this fact - that the script is using /etc/init.d/xinetd what does not exist any more in both 13.1 and 13.2

What made me wonder is the fact that the date and the size of the file setup_network_scanner_config does not differ from 13.1 and from factory ... both carry the timestamp from 2010 ...

Thank you for looking into this,
my guess is, the patch did not make it's way into the distribution.

Take care




Dieter Jurzitza
Comment 3 Johannes Meixner 2014-10-27 09:30:12 UTC
Yes, your guess is right.

The fix only made it's way into SLE12 but not into openSUSE.

In OBS the fixed package is in SUSE:SLE-12:GA/yast2-scanner

To make it right now available for you to test it I copied
SUSE:SLE-12:GA/yast2-scanner to home:jsmeix/yast2-scanner-sle12.

For now the fixed yast2-scanner RPM is available at
http://download.opensuse.org/repositories/home:/jsmeix/openSUSE_13.2/
Comment 4 Johannes Meixner 2014-10-27 09:49:52 UTC
I submitted bug#902680
"Provide yast2-printer and yast2-scanner from SLE12 in openSUSE 13.2"

*** This bug has been marked as a duplicate of bug 902680 ***
Comment 5 Dieter Jurzitza 2014-11-01 08:53:06 UTC
Dear Mr. Meissner,
I portetd your patch back to my daily - use openSUSE 13.1 and I tested on 13.2. However, I had to modify yast2-scanner from factory as the version you supplied in your "private" repository had an older release-tag than the one actually distributed with 13.2 RC1.

However, both of them worked flawlessly, so, thank you for taking care and I hope you'll get it managed to distribute the fixed version with 13.2 (and it would be kind if an update for 13.1 could be provided, but put that somewhere on the wishlist ;-))

Thanks again,
take care






Dieter Jurzitza