September 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [yast-announce] YDialogSpy: An Interactive YaST Dialog Debugger
by Ricardo Cruz 15 Sep '08

15 Sep '08

Qui, 2008-09-11 às 17:29 +0200, Stefan Hundhammer escreveu: > http://lizards.opensuse.org/2008/09/11/ydialogspy-an-interactive-yast-dialo… > > Short version: Hit Ctrl-Shift-Alt-Y, and you'll get a window with the > widget > tree of the current dialog. You can highlight parts of the dialog (Buttons, > HBoxes/VBoxes with their content) to see the layout engine in action. > Very cool. Added support for the GTK UI. Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] [11.0] Change ipv6 setting via commandline?
by Lars Behrens 11 Sep '08

11 Sep '08

Hi there, which yast module do I have to use in order to switch off the ipv6 option? And btw. is there a browsable list of all options which can be configured via yast on the commandline? TIA! Cheerz, Lars -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 6

[yast-devel] Re: [zypp-devel] repository 'path'
by Jan Kupec 11 Sep '08

11 Sep '08

Michael Andres wrote: > On Thu, Sep 11, Jan Kupec wrote: > >> Hi Hackers, >> >> the support for *path* in repositories (the piece appended to baseurl) is >> still not perfect in libzypp. I am about to fix it, but first i've got a >> few questions. >> >> - DO WE NEED THIS AT ALL? :O) >> >> AFAICT, we needed this for multi-product media (like patch-CDs >> probably). I'm not sure why, though, can't we just go about it with >> two different URLs? If some 'conent' file references the other >> repo with a relative path, it should be no problem for libzypp to >> just use the baseurl+this_path, no need to treat them separately(?). > > > To handle a media set we need to to know 2 urls. > > > 1) the media root > > - This is the location of media.<n>/media. We need it to check e.g whether > the correct media is inserted. > > There are also other files like the gpg-keys, releasenotes,.. kept in the > media root directory and not per repository. > > - In case you copy a media set to your disk (to offer it via http, > nfs,...) > > /somewhere/DVD1 > /DVD2 > ... > /DVD<N> > > this is the place where you have to change DVD1 to DVD2 when changing > from media 1 to 2. > > > 2) the repositories root on the media > > This is the path to acces the repository on the media. If the media has > just one repo at /, you don't need the path. > > > > Libzypp could live without 'path'. We could simply guess the media root > when changing or verifying media. For CD/DVD it's obvious. And for disc > copies we could probe for a ending in digits, or for a media.<n> > directory. > > But you also have to adapt YaST (and maybe other tools), which currently > expect the url pointing to the media root. They download e.g > > repo.url()/control.xml OK, so this is what escaped my attention, some metadata only in the media root, and multiple-media repos (mutliple CDs/DVDs). Thanx! > Or we have to change the media layout an keep certain files per repo and > not per media. This might even be reasonable, but... We would still have problem with changing media http://foo/DVD1/ http://foo/DVD2/ http://foo/DVD1/repo2 http://foo/DVD2/repo2 currently we expect the media number at the end of the URL. We use this regexp: "^(.*)(cd|dvd)[0-9]+(/)?$". But you're right, this is not hard to solve. > It's not a zypp local change. If we want to go for this, we have to > convince some people. But it could be worth trying to do this. I agree. At this point i can't asses whether keeping and fixing the path in libzypp is more tricky than getting rid of it, i would need info from affected people. But i guess some people will say it is too late for 11.1. But another thing is, we never dealt with this kind of media layout since libzypp's refactoring after 10.2. So we really need to do something about it one way or the other. A side question: would we add such multi-product repository as two zypp repos? -- cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] [Fwd: Re: [zypp-devel] repository 'path']
by Jan Kupec 11 Sep '08

11 Sep '08

forwarding Michael's reply (i posted the original to wrong mailing list) -------- Original Message -------- Subject: Re: [zypp-devel] repository 'path' Date: Thu, 11 Sep 2008 12:51:44 +0200 From: Michael Andres <ma(a)suse.de> Organization: SUSE LINUX Products GmbH, D-90409 Nuernberg, Germany To: Jan Kupec <jkupec(a)suse.cz> CC: ZYpp-Devel <zypp-devel(a)opensuse.org>, yast(a)suse.cz References: <48C8E7D3.3040800(a)suse.cz> On Thu, Sep 11, Jan Kupec wrote: > Hi Hackers, > > the support for *path* in repositories (the piece appended to baseurl) is > still not perfect in libzypp. I am about to fix it, but first i've got a > few questions. > > - DO WE NEED THIS AT ALL? :O) > > AFAICT, we needed this for multi-product media (like patch-CDs > probably). I'm not sure why, though, can't we just go about it with > two different URLs? If some 'conent' file references the other > repo with a relative path, it should be no problem for libzypp to > just use the baseurl+this_path, no need to treat them separately(?). To handle a media set we need to to know 2 urls. 1) the media root - This is the location of media.<n>/media. We need it to check e.g whether the correct media is inserted. There are also other files like the gpg-keys, releasenotes,.. kept in the media root directory and not per repository. - In case you copy a media set to your disk (to offer it via http, nfs,...) /somewhere/DVD1 /DVD2 ... /DVD<N> this is the place where you have to change DVD1 to DVD2 when changing from media 1 to 2. 2) the repositories root on the media This is the path to acces the repository on the media. If the media has just one repo at /, you don't need the path. Libzypp could live without 'path'. We could simply guess the media root when changing or verifying media. For CD/DVD it's obvious. And for disc copies we could probe for a ending in digits, or for a media.<n> directory. But you also have to adapt YaST (and maybe other tools), which currently expect the url pointing to the media root. They download e.g repo.url()/control.xml Or we have to change the media layout an keep certain files per repo and not per media. This might even be reasonable, but... It's not a zypp local change. If we want to go for this, we have to convince some people. But it could be worth trying to do this. > Is the 'path' part of YUM's definition? AFAIK not. It's not needed if you don't deal with media sets the way we do it. 'path' is actually part of the media handling, not of the repo. > - our repository definition allows multiple baseurls to be defined, as > well as mirrors (these are ignored currently IIRC). What to do with > this: > > [foorepo] > baseurl = http://url1.org/repos > baseurl = http://url2.org/whatever > path = foorepo/openSUSE/11.1 > > not to mention mirrors. Should we just use the path for all of the > baseurls? We have to. We must assume all urls point to locations with the same layout (not just same content). And in most cases you dont need the path as it's /. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] [YaST] Czech YaST2 team (Prague) meeting 2008-09-09
by Michal Zugec 11 Sep '08

11 Sep '08

Czech YaST2 team (Prague) meeting 2008-09-09 ============================================ Present: jsrain, jkupec, jreidinger, jsuchome, kmachalkova, locilka, lslezak, mzugec Absent: juhliarik, mvidner Minutes: mzugec Next Minutes: jsrain jsrain ------ - fixed some issues with uefi booting - work on yast2-support module jkupec ------ - support for services in libzypp (fate #302376, #303563, #304915) - username/password stored in separate file for repository authentication in libzypp - new zypper commands: targetos, versioncmp jreidinger ---------- - hackweek project: downloader for openSUSE ISO images http://idea.opensuse.org/content/ideas/standalone-download-program-for-open… - fixed bootloader problem (when replace kernel-default with kernel-pae, remember which item is default) (bnc#402789) jsuchome -------- - work on SCR agent for pam_mount.conf.xml (fate 300967) - yast2-users: load cracklib dictionary during installation only for the time needed - yast2-nis-*: use rpcbind as default instead of portmap (bnc#423026) kmachalkova ----------- - hackweek project: improved ayast_setup.ycp (CLI support) from autoyast2 package - netconfig support in yast2-network (DNS part - /etc/resolv.conf) - nfs-client integration with partitioner - works with nfs(v3) - nfs-client(v4) can write dmapd.conf now locilka ------- - WFM::ClientExists ( http://lists.opensuse.org/yast-devel/2008-09/msg00033.html ) - support for ButtonBoxes in yast2 - AutoYaST can use images now (like "normal" installation) (fate#301321) - different workflow can be used while upgrading an add-on comparing to workflow used for new installation (FATE#301997) lslezak ------- - hackweek project: exporting a yast namespace as a DBus service (the code is not much usable, too many problems, but at least I successfully installed a package via pkg-bindings namespace Pkg:: running on DBus) - PkgBindings uses Selectables instead of Pool - removed duplicate code, bug compatible with other tools - support for services in PkgBindings mzugec ------ - work on yast2-support - support for InfiniBand in yast2-network (fate#304870), (fate#304115) - special proposal for virtualization network (fate#303386) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Enforcing okButton and cancelButton
by Stefan Hundhammer 10 Sep '08

10 Sep '08

https://bugzilla.novell.com/show_bug.cgi?id=422612 This shows that there are cases where it is legitimate to have a pop-up dialog with a ButtonBox with more than one button, but only an okButton and no cancelButton: ...message... <Countdown> [Stop] [OK] We (mschmidkunz + tgoettlicher + sh) thought that this is the one exception from that rule; in general, all dialogs with more than one button should have an okButton (for the regular end) and a cancelButton (as a safe escape). Now locilka found one more exception: ...error... [OK] [Details...] Now I can't help that sinking feeling that there might be even more. If there is a significant number of cases where it makes sense to not enforce that sanity check (must have only one button or both okButton and cancelButton), we have to get rid of that check. But I still think that it's useful. Who has more examples where it might be legitimate to have more than one button, yet not both an okButton and a cancelButton? Opinions? Suggestions? CU -- Stefan Hundhammer <sh(a)suse.de> Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 21

[yast-devel] Re: [yast-announce] YaST .pot-files back from proofreading
by Johannes Meixner 10 Sep '08

10 Sep '08

Hello, On Sep 8 12:20 Jiri Srain wrote (shortened): > YaST .pot-files are back from proofreading. They are available at > /suse/jsrain/Export/proofed-os11.1-2008-09-08 It seems the current printer.pot is for obsolete code: grep '^#:' /suse/jsrain/Export/proofed-os11.1-2008-09-08/printer.pot #: src/common/helps.ycp:272 #: src/modules/Spooler.ycp:532 ../devtools/yast2/ycp_puttext printer.pot.new . Warning: Can't find .ycp file src/common/helps.ycp Warning: Can't find .ycp file src/modules/Spooler.ycp There are no longer such source files in yast2-printer so that there is nothing to apply here at the moment. Therefore I simply moved the current printer.pot to /suse/jsrain/Export/proofed-os11.1-2008-09-08/DONE/ Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] use ALog::Item
by Martin Vidner 09 Sep '08

09 Sep '08

Dear hackers, you are all admins of your own workstations, I believe. Have you ever wondered what YaST did to your system? Or even what *you* did to your system a week or a month ago? Please have a look at your y2log now: sudo less /var/log/YaST2/y2log The information is (mostly) there, but it is buried in piles and heaps of debugging information. So yes, as if you did not have enough features to implement already, I am asking you for more. But the users will love it. Please take one (or all) of your modules and put in log messages using the API below. Presumably they are already there, using y2milestone. ALog stands for Admin's log, to remind you who the reader is. ALog::Item("/etc/ntp.conf: added 'server ntp.example.org'") ALog::Item("enabled /etd/init.d/ntp") ALog::Item("started /etd/init.d/ntp") ALog::CommitPopup() will lead to ALog::Note("set up ntp from local server") A prototype is in SVN already: http://svn.opensuse.org/svn/yast/trunk/yast2/library/log/src/ALog.ycp The interface is not set in stone (yet). Please comment and let's find a design that is useful and easy to use. Open questions: - actual log format References: - https://keeper.novell.com/sxkeeper/feature/303700?contenttype=text/html - https://keeper.novell.com/sxkeeper/feature/100386?contenttype=text/html - related log in zypp: http://lists.opensuse.org/zypp-devel/2008-07/msg00043.html -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 14

[yast-devel] Annoucement: New built-in functions WFM::ClientExists(...) && getenv(...)
by Lukas Ocilka 08 Sep '08

08 Sep '08

Hi, I've enabled the getenv() and implemented new WFM::ClientExists() functions recently. *getenv* (implemented by juhliarik) returns the current value if ENV variables which you can set using setenv [1]. *WFM::ClientExists* is similar to WFM::call [2] (without args) but instead of calling the client, it only returns whether client you want to call exists. This is very useful to prevent from runtime errors when running clients from another YaST modules, especially during installation. New documentation for these built-in functions will be available soon (next time we rebuild the documentation). [1] http://forgeftp.novell.com/yast/doc/SL11.1/tdg/setenv-choose.html [2] http://forgeftp.novell.com/yast/doc/SL11.1/tdg/call.html Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] y2makeall --clean
by Stanislav Visnovsky 04 Sep '08

04 Sep '08

Hi! I've added a new option to y2makeall script to invoke 'make clean' before building. This is quite helpful if you did not recompile whole subversion for quite some time. Usage: 'y2tool y2makeall --clean' Patch for trunk yast2-devtools attached. Please, review and commit if useful. Stano

2 2