Mailinglist Archive: opensuse-bugs (4919 mails)

< Previous Next >
[Bug 588679] New: yast2-printer: AutoYaST client destroys information in cupsd.conf
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 16 Mar 2010 15:09:32 +0000
  • Message-id: <bug-588679-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=588679

http://bugzilla.novell.com/show_bug.cgi?id=588679#c0


Summary: yast2-printer: AutoYaST client destroys information in
cupsd.conf
Classification: openSUSE
Product: openSUSE 11.3
Version: Factory
Platform: All
OS/Version: openSUSE 11.3
Status: NEEDINFO
Severity: Major
Priority: P5 - None
Component: AutoYaST
AssignedTo: jsmeix@xxxxxxxxxx
ReportedBy: jsmeix@xxxxxxxxxx
QAContact: qa@xxxxxxx
CC: ug@xxxxxxxxxx, mzugec@xxxxxxxxxx
Found By: Development
Blocker: ---


When AutoYaST calls the "Write" function in printer_auto.ycp
it results
- a /etc/cups/cupsd.conf without any comments
and without any indentation but with a strange
unexpected re-ordering of the entries
and
- a /etc/cups/client.conf without any comments
which is totally empty if there was no active entry
in the /etc/cups/client.conf of the system wherefrom
the AutoYaST control file was created.

Because the comments provide useful and sometimes even
very important information for the admin, the yast2-printer
AutoYaST client destroys information.

Because the ordering in /etc/cups/cupsd.conf in the cloned
system is the well known upstream ordering, an unexpected
strange re-ordering makes it very hard to understand
the /etc/cups/cupsd.conf file afterwards.

Therefore the bug severity is "major".


Details:
When AutoYaST calls the "Write" function in printer_auto.ycp
it calls Printerlib::WriteClientSettings and
Printerlib::WriteCupsSettings which call
SCR::Write(.cups.client, ay) and SCR::Write(.cups.server, ay)
where ay is a map as follows:
------------------------------------------------------------------------
$["cups_remote_server":
$[],
"server_settings":
$["BrowseAllow":["all"],
"BrowseOrder":["allow,deny"],
"Browsing":["On"],
"DefaultAuthType":["Basic"],
"DefaultPolicy":["default"],
"Listen":["localhost:631",
"/var/run/cups/cups.sock"],
"LogLevel":["info"],
"SystemGroup":["sys root"],
..
------------------------------------------------------------------------
and the /etc/cups/cupsd.conf file is as follows:
------------------------------------------------------------------------
Listen localhost:631
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow none
BrowseDeny all
DefaultPolicy default
DefaultAuthType Basic
SystemGroup sys root
..
LogLevel info
------------------------------------------------------------------------

I assume because a YCP map does not keep any ordering
but the actual sequence of its entries is random,
one gets also a random re-ordered cupds.conf file written.


Uwe,
for openSUSE 11.3 I will clean it up, compare
https://bugzilla.novell.com/show_bug.cgi?id=582680#c35

Which YCP structure works for AutoYaST so that config files
are written 100% identical on the target system?
I.e. on one same system "Read"->"Export"->"Import"->"Write"
must result 100% identical (i.e. unchanged) config files.

I would prefer to have both cupsd.conf and client.conf
as XML CDATA in the AutoYaST control file.

Which YCP data must the "Export" function in printer_auto.ycp
provide to AutoYaST so that the result are two XML CDATA sections,
one for cupsd.conf and one for client.conf?

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >