March 2013 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305553] zypper: dist upgrade could error out if more than one repository with a base product exists
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature changed by: Duncan Mac-Vicar (dmacvicar) Feature #305553, revision 44 Title: zypper: dist upgrade could error out if more than one repository with a base product exists openSUSE-11.2: Done Priority Requester: Important Projectmanager: Important - openSUSE-11.3: Evaluation by product manager + openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) + reject date: 2013-03-05 13:25:50 + reject reason: not done Priority Requester: Important Requested by: Dirk Mueller (dirkmueller) - Product Manager: Federico Lucifredi (flucifredi) Developer: Ján Kupec (jkupec) Partner organization: openSUSE.org Description: I've just learned over lunch that calling "zypper dup" is wrong if you have both buildservice repositories and a distribution repository enabled. apparently one has to call it with -r name, where name points to the distribution one wants to upgrade to, and the other repositories (e.g. buildservice addons) must not be dup'ed, but only updated via update -t package. I've verified that this indeed fixes the "reinstalling/downgrading package" issues everyone seems to be complaining about. It would be nice if zypp/zypper could detect this situation and advise the user, or alternatively do the right thing automatically. I'm not sure if channels of distributions (e.g. the factory channel, or a future openSUSE 11.0 channel) can be detected in some way.. if it does, then it could automatically add the -r argument if there is only one distribution channel enabled, and altneratively error out if more than one distribution channel is in the sources list and no -r argument was given. Relations: - make zypper dup error out if more than one repository exists (novell/bugzilla/id: 385972) https://bugzilla.novell.com/show_bug.cgi?id=385972 Discussion: #1: Stephan Kulow (coolo) (2008-05-11 02:20:39) * ** Bug 388956 has been marked as a duplicate of this bug. *** #2: Duncan Mac-Vicar (dmacvicar) (2008-12-10 15:31:24) Hm. If that is so, this feature is really important :O) Just a side question: how does installation handle this (if at all)? Currently they can't, we need to add means of such identification (as well as identification of update repos). yup, sounds good #3: Lukas Ocilka (locilka) (2008-05-12 06:17:43) Installation/Upgrade has the installation repository registered as the fist one, then Add-Ons or other repositories can be added or enabled. Upgrade doesn't handle how the packages are selected to be upgraded, it just calls solver. OK, some packages are dropped by installation by default :) See bug #300540. #4: Stephan Kulow (coolo) (2008-05-12 06:25:06) the main difference: it's pretty unusual to have 13 repos during distribution update with very comparable versions. While it's not to for zypper dup. BTW: another difference: installations sets YAST_IS_RUNNING=instsys, which some packages cause not to produce errors on updates. This might be good for dup, but bad for update #5: Duncan Mac-Vicar (dmacvicar) (2008-12-10 16:56:35) Note, I moved the bugzilla entry to fate, but mls claims the bug is invalid, as it is a perfect use case to do dist upgrade with various repositories. So this feature has to be evaluated with care and gathering opinions from various sources. It may be invalid. #7: Jiri Srain (jsrain) (2008-12-11 07:58:04) (reply to #5) I don't think it is invalid; I happened to downgrade several packages from OSS repo via zypper dup :-( #8: Duncan Mac-Vicar (dmacvicar) (2008-12-11 10:10:32) (reply to #7) The solution of stop-with-error if there is more than one repository is invalid because prevent the valid usecase of dist-upgrading with more than one repo enabled (as mls pointed out). What is valid about the feature, is that multiple repo upgrade can be dangerous, and we may warn the user if there are repos for different products there. #9: Jiri Srain (jsrain) (2008-12-11 10:53:42) (reply to #8) Sorry for not being precise in my comment: of course user must be able to override this error/warning/whatever. #6: Duncan Mac-Vicar (dmacvicar) (2008-12-10 18:34:19) Idea from mls: Use the CPE ids introduced in 11.1 to issue a warning if repositories are mixed. #10: Ján Kupec (jkupec) (2009-06-24 09:33:26) Michael, is this still relevant? Is this related to the planned --from option? #11: Michael Schröder (mlschroe) (2009-06-24 11:33:46) (reply to #10) This has nothing to do with --from, it's about doint 'zypper dup' to update the system to the next release while still having old repositories enabled. #12: Ján Kupec (jkupec) (2009-07-07 16:26:43) (reply to #11) So multiple repositories are not a problem in general, but multiple repos for different products are! OK, so now back to the solution: can you tell me or point me to some info abou these CPEs Duncan mentions in c#6? I guess they are part of the product solvable and are available as solv attribute? If so, all that's needed is to check whether there are multiple repos with a different product and write a warning if that's the case, right? #13: Michael Schröder (mlschroe) (2009-07-07 16:34:14) (reply to #12) ma, is there a libzypp interface? #14: Michael Andres (mlandres) (2009-07-13 14:16:11) (reply to #13) Yes. Since you can ask for a products CPEid, or for the CPEids related to a repository (supported or updated products). But I don't know if those CPEids are meanwhile included in the metadata (see bnc #459527). #15: Ján Kupec (jkupec) (2009-07-14 18:17:17) (reply to #14) OK, so this should not be too much work. So to sum it up: * zypper: show a warning in 'dup' if there are multiple base repos with different CPEids enabled. * metadata: check/include the CPEid in product metadata (who should do this?) #16: Ján Kupec (jkupec) (2009-07-27 17:30:09) (reply to #14) Rudi, please look at c#14 and 15 #17: Ján Kupec (jkupec) (2009-07-29 19:04:40) Current status: * TODO: put CPE IDs to content/prodcuts.xml metadata (still nobody assigned to do this!) * TODO: satsolver will need to parse the above (or is this ready already?) * PROBLEM: we need to figure out which repos don't go together for dup. I proposed to compare CPEs of 'base' or 'platform' repos, but we have no 'isBase' flag in product or repo metadata. Simply checking for different CPEs is not enough (think of one base product and one addon - two different CPEs, but 'dup' is OK with them). * PROBLEM: even if we'll have the 'isBase' flag, we'll be stuck in case of two different, but compatible bases, like e.g. SLES and SLED could be used standalone or with SLED as an add-on to SLES in the past. Do we still allow this? Any ideas? #18: Ruediger Oertel (oertel) (2009-07-30 17:20:05) adding more data (like the CPE-ids) is not a big issue. the problem for me is rather how to obtain a CPE-id #19: Marcus Meissner (msmeissn) (2009-08-04 17:55:08) CPE ids can be defined by the vendor as I udnerstand ;) I mailed Jan and Rudi. my suggestions would be: cpe:/o:opensuse:opensuse:11.1 cpe:/o:novell:suse_linux_enterprise:11:ga:server cpe:/o:novell: suse_linux_enterprise:10:sp2:desktop #20: Ralph Ulrich (ulenrich) (2009-08-05 13:25:05) (beginners question) Why products at all. Debian/Ubuntu do have so called meta-packages , which are normal package that pull in stuff: minimal, standard ...etc Without products you would loose an additional level of complication? #21: Ján Kupec (jkupec) (2009-08-05 15:02:36) (reply to #20) Using metapackages for puling stuff does not exlude using of CPE ID. It's just means to uniquely identify a product and can be used by Debian's metapackages as well. Other than that, your question is not related to this FATE, and is more appropriate for opensuse-softwaremgmt(a)opensuse.org mailing list. But you might find the answer also here http://en.opensuse.org/Product_Management #22: Ján Kupec (jkupec) (2009-08-19 17:25:34) We still need to do the TODOs and resolve the issues from c#17 here. If you have an idea, please speak up. #23: Klaus Kämpf (kwk) (2009-08-25 09:36:05) I believe the request title is wrong and should be adapted. Indeed 'distribution upgrade' is special, as it considers one repo to be 'authorative' and thus dictating package versions, which might result in a version downgrade. 'zypper dup' should provide support for this and, in case of multiple 'product' (resp. base) repositories request a decision from the user. There are two things to be solved from my pov * Detection of a 'base' vs. 'addon' repo. Could be done by looking at a 'product' resolvable. * Specifying the 'authorative' repo in case of dist upgrade. ie. passing a '--product foo' or '-to repo' to zypper. #24: Ján Kupec (jkupec) (2009-11-18 15:59:55) (reply to #23) Detection of base vs. addon is what we currently lack. The authoritative repo can now be selected using --from option. 'zypper dup --from repo-oss'. #26: Ján Kupec (jkupec) (2009-11-20 15:29:56) Following Jiri's suggestion, i've done this the simple way for now: if --repo or --from are not used, and multiple repos are enabled, 'zypper dup' will show a warning and a hint that the user should check the repo list for incompatible repos. #27: Jiri Srain (jsrain) (2009-11-25 13:55:01) (reply to #26) This is all we could do for SP1. Keeping open for further enhancements for SP2 and/or 11.3. #28: Ján Kupec (jkupec) (2010-03-04 15:15:18) (reply to #26) Marking as done also for 11.2 since the SP1 package will also be released as update for 11.2. -- openSUSE Feature: https://features.opensuse.org/305553

1 0

[New: openFATE 309445] Make yast proxy work with Microsoft ISA
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: francesco nigro (frappa_nigro) Feature #309445, revision 1 Title: Make yast proxy work with Microsoft ISA openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: francesco nigro (frappa_nigro) Description: The yast proxy module doesn't work with Microsoft ISA proxy, the ntlm authentication is not managed correctly and fails. The only viable solution at the moment (the only one I found at least) is to install cntlm on every machines... -- openSUSE Feature: https://features.opensuse.org/309445

1 3

[openFATE 305546] Support for NTLM authentication (proxy) in YaST and libzypp
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature changed by: Duncan Mac-Vicar (dmacvicar) Feature #305546, revision 37 Title: Support for NTLM authentication (proxy) in YaST and libzypp openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) reject date: 2009-07-16 18:02:44 reject reason: out of context for openSUSE. Priority Requester: Desirable Projectmanager: Desirable - openSUSE-11.3: Evaluation by product manager + openSUSE-11.3: Rejected by Duncan Mac-Vicar (dmacvicar) + reject date: 2013-03-05 13:24:31 + reject reason: not done Priority Requester: Desirable Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Katarina Machalkova (kmachalkova) Partner organization: openSUSE.org Description: YaST and libzypp should work in an environment with proxy server requiring NTLM authentication. The feature consists of two parts: 1) YaST proxy module has to provide UI to let user choose NTLM and write configuration file (/root/.curlrc) accordingly 2) libzypp media backend needs to be adapted to read and understand such configuration( that is, accept also --proxy-ntlm option instead of bare --proxy only) References: https://bugzilla.novell.com/show_bug.cgi?id=440296 https://bugzilla.novell.com/show_bug.cgi?id=412137 Relations: - Cntlm Authentication Proxy (url: http://cntlm.sourceforge.net/) Business case (Partner benefit): openSUSE.org: Significant for adoption in mixed datacenters where the proxy infrastruture is on MSFT assets. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-26 20:57:23) Sadly, there is a realistic business case for this in mixed datacenters. Some odd people like to use NTLM proxies, I will never understand why. this will be a headache to do :-/ #2: Mark Muhlestein (mmuhlestein) (2010-01-13 18:10:39) Many of the engineers at Dell Computer in Austin want to use openSUSE 11.2 on their desktop machines. Dell uses a NTLM proxy on their corporate network so a lack of this functionality is keeping them from doing so. This group of engineers are very loyal SUSE/Novell folks who are trying very hard to help a SUSE desktop make inroads into Dell's corporate environment. Current number of engineers who cannot use the product is 50 - 60 On a side note, they see this a glaring problem. I don't know how many corporations use NTLM proxies but the gents at Dell seem to think it is quite a lot. #3: Katarina Machalkova (kmachalkova) (2010-01-14 15:03:36) I was wondering whether aria2c can handle NTLM auth. curl certainly does, but it's not our default downloader anymore. I googled a bit and found this table (http://curl.haxx.se/docs/comparison-table.html) and it doesn't look too positive :( #4: Duncan Mac-Vicar (dmacvicar) (2010-01-14 16:51:17) Because we are now using aria2 (however ZYpp stll can fall back to curl) I asked aria2 author if he planned something in the direction. He does not, however he will look into the protocol. The problem, appart of the time, is that he does not have a server to test. He pointed me to http://ntlmaps.sourceforge.net/ which allows to authenticate against a NTLM server acting as a normal proxy server. I have never tested this, but I wonder if companies really need support for this protocol in the tooling. #5: Michael Calmer (mcalmer) (2010-01-14 16:57:35) (reply to #4) I would say yes. I see sometimes logs from the registration where is a proxy is in use with NTLM authentication. I think this is some kind of Windows Server which is doing the authentication and automatically support NTLM. If possible, we should have a way to support this. #7: Michael Andres (mlandres) (2010-08-10 15:32:24) (reply to #4) Might be worth mentioning that post 11.3 we're about to drop aria2 again. We now have a builtin solution suporting metalink and zync, base on libcurl. #6: Carlo Baffè (cbaffe) (2010-08-05 14:04:03) also Telecom Italia (http://www.telecomitalia.it) asked us about this feature support since their SLES / SMT should pass through MSFT ISA proxies with authentication in order to reach our nu.novell.com. but SLES 11 SP1 does not support it. #9: Andi Chandler (andibing) (2011-12-01 19:58:54) NTLM authentication should be an option in YAST to work seamlessly across all services. #10: Duncan Mac-Vicar (dmacvicar) (2011-12-05 09:27:32) (reply to #9) Has anyone really tried this? I can see in ZYpp code > grep CURLOPT_PROXYAUTH * MediaCurl.cc: SET_OPTION(CURLOPT_PROXYAUTH, CURLAUTH_BASIC|CURLAUTH_DIGEST|CURLAUTH_NTLM ); Which means NTLM is enabled. #12: Michael Calmer (mcalmer) (2011-12-05 10:04:30) (reply to #10) I had this enabled for SMT and a customer was able to authenticate to a proxy.So I went to zypp team and they have enabled this too. I think it is part of 12.1 and Factory, but not on older versions. #17: Michael Andres (mlandres) (2012-06-26 10:24:50) (reply to #12) It's available since 12.1 and in SLES11-SP1 since libzypp-6.37.7 SLES11- SP2 since libzypp-9.11.9 #11: Duncan Mac-Vicar (dmacvicar) (2011-12-05 09:59:45) (reply to #10) Oh, I just realized this commit is only a few days old. This should enable NTLM support, but it needs to be tested. It will be in next openSUSE, SLE service pack or major version. If we need a backport we can do it, but it needs to be tested. commit 3524f4d265a9c697fb201977f60cc7eba3570250 Author: Michael Andres <ma(a)suse.de> Date: Thu Oct 20 15:57:02 2011 +0200 Set CURLOPT_PROXYAUTH diff --git a/zypp/media/MediaCurl.cc b/zypp/media/MediaCurl.cc index cb27760..901ac45 100644 --- a/zypp/media/MediaCurl.cc +++ b/zypp/media/MediaCurl.cc @@ -620,6 +620,7 @@ void MediaCurl::setupEasy() if ( ! _settings.proxy().empty() ) { SET_OPTION(CURLOPT_PROXY, _settings.proxy().c_str()); + SET_OPTION(CURLOPT_PROXYAUTH, CURLAUTH_BASIC|CURLAUTH_DIGEST| CURLAUTH_NTLM ); /*--------------------------------------------------------------- * CURLOPT_PROXYUSERPWD: [user name]:[password] #13: Yury Krasovski (krasoffski) (2011-12-13 16:06:41) NTLM is very important feature for me, because I have to use proxy with NTLMv2 authentication. I hope, I'll get it in next release, and also I recommend to use a cntlm package. -- openSUSE Feature: https://features.opensuse.org/305546

1 0

[openFATE 305546] Support for NTLM authentication (proxy) in YaST and libzypp
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature changed by: Duncan Mac-Vicar (dmacvicar) Feature #305546, revision 36 Title: Support for NTLM authentication (proxy) in YaST and libzypp openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) reject date: 2009-07-16 18:02:44 reject reason: out of context for openSUSE. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.3: Evaluation by product manager Priority Requester: Desirable Package Wishlist: Unconfirmed Priority Requester: Important - Info Provider: Federico Lucifredi (flucifredi) Requested by: Katarina Machalkova (kmachalkova) - Product Manager: Federico Lucifredi (flucifredi) Partner organization: openSUSE.org Description: YaST and libzypp should work in an environment with proxy server requiring NTLM authentication. The feature consists of two parts: 1) YaST proxy module has to provide UI to let user choose NTLM and write configuration file (/root/.curlrc) accordingly 2) libzypp media backend needs to be adapted to read and understand such configuration( that is, accept also --proxy-ntlm option instead of bare --proxy only) References: https://bugzilla.novell.com/show_bug.cgi?id=440296 https://bugzilla.novell.com/show_bug.cgi?id=412137 Relations: - Cntlm Authentication Proxy (url: http://cntlm.sourceforge.net/) Business case (Partner benefit): openSUSE.org: Significant for adoption in mixed datacenters where the proxy infrastruture is on MSFT assets. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-26 20:57:23) Sadly, there is a realistic business case for this in mixed datacenters. Some odd people like to use NTLM proxies, I will never understand why. this will be a headache to do :-/ #2: Mark Muhlestein (mmuhlestein) (2010-01-13 18:10:39) Many of the engineers at Dell Computer in Austin want to use openSUSE 11.2 on their desktop machines. Dell uses a NTLM proxy on their corporate network so a lack of this functionality is keeping them from doing so. This group of engineers are very loyal SUSE/Novell folks who are trying very hard to help a SUSE desktop make inroads into Dell's corporate environment. Current number of engineers who cannot use the product is 50 - 60 On a side note, they see this a glaring problem. I don't know how many corporations use NTLM proxies but the gents at Dell seem to think it is quite a lot. #3: Katarina Machalkova (kmachalkova) (2010-01-14 15:03:36) I was wondering whether aria2c can handle NTLM auth. curl certainly does, but it's not our default downloader anymore. I googled a bit and found this table (http://curl.haxx.se/docs/comparison-table.html) and it doesn't look too positive :( #4: Duncan Mac-Vicar (dmacvicar) (2010-01-14 16:51:17) Because we are now using aria2 (however ZYpp stll can fall back to curl) I asked aria2 author if he planned something in the direction. He does not, however he will look into the protocol. The problem, appart of the time, is that he does not have a server to test. He pointed me to http://ntlmaps.sourceforge.net/ which allows to authenticate against a NTLM server acting as a normal proxy server. I have never tested this, but I wonder if companies really need support for this protocol in the tooling. #5: Michael Calmer (mcalmer) (2010-01-14 16:57:35) (reply to #4) I would say yes. I see sometimes logs from the registration where is a proxy is in use with NTLM authentication. I think this is some kind of Windows Server which is doing the authentication and automatically support NTLM. If possible, we should have a way to support this. #7: Michael Andres (mlandres) (2010-08-10 15:32:24) (reply to #4) Might be worth mentioning that post 11.3 we're about to drop aria2 again. We now have a builtin solution suporting metalink and zync, base on libcurl. #6: Carlo Baffè (cbaffe) (2010-08-05 14:04:03) also Telecom Italia (http://www.telecomitalia.it) asked us about this feature support since their SLES / SMT should pass through MSFT ISA proxies with authentication in order to reach our nu.novell.com. but SLES 11 SP1 does not support it. #9: Andi Chandler (andibing) (2011-12-01 19:58:54) NTLM authentication should be an option in YAST to work seamlessly across all services. #10: Duncan Mac-Vicar (dmacvicar) (2011-12-05 09:27:32) (reply to #9) Has anyone really tried this? I can see in ZYpp code > grep CURLOPT_PROXYAUTH * MediaCurl.cc: SET_OPTION(CURLOPT_PROXYAUTH, CURLAUTH_BASIC|CURLAUTH_DIGEST|CURLAUTH_NTLM ); Which means NTLM is enabled. #12: Michael Calmer (mcalmer) (2011-12-05 10:04:30) (reply to #10) I had this enabled for SMT and a customer was able to authenticate to a proxy.So I went to zypp team and they have enabled this too. I think it is part of 12.1 and Factory, but not on older versions. #17: Michael Andres (mlandres) (2012-06-26 10:24:50) (reply to #12) It's available since 12.1 and in SLES11-SP1 since libzypp-6.37.7 SLES11- SP2 since libzypp-9.11.9 #11: Duncan Mac-Vicar (dmacvicar) (2011-12-05 09:59:45) (reply to #10) Oh, I just realized this commit is only a few days old. This should enable NTLM support, but it needs to be tested. It will be in next openSUSE, SLE service pack or major version. If we need a backport we can do it, but it needs to be tested. commit 3524f4d265a9c697fb201977f60cc7eba3570250 Author: Michael Andres <ma(a)suse.de> Date: Thu Oct 20 15:57:02 2011 +0200 Set CURLOPT_PROXYAUTH diff --git a/zypp/media/MediaCurl.cc b/zypp/media/MediaCurl.cc index cb27760..901ac45 100644 --- a/zypp/media/MediaCurl.cc +++ b/zypp/media/MediaCurl.cc @@ -620,6 +620,7 @@ void MediaCurl::setupEasy() if ( ! _settings.proxy().empty() ) { SET_OPTION(CURLOPT_PROXY, _settings.proxy().c_str()); + SET_OPTION(CURLOPT_PROXYAUTH, CURLAUTH_BASIC|CURLAUTH_DIGEST| CURLAUTH_NTLM ); /*--------------------------------------------------------------- * CURLOPT_PROXYUSERPWD: [user name]:[password] #13: Yury Krasovski (krasoffski) (2011-12-13 16:06:41) NTLM is very important feature for me, because I have to use proxy with NTLMv2 authentication. I hope, I'll get it in next release, and also I recommend to use a cntlm package. -- openSUSE Feature: https://features.opensuse.org/305546

1 0

[openFATE 303793] Mount /var/run as tmpfs
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature changed by: Duncan Mac-Vicar (dmacvicar) Feature #303793, revision 62 Title: Mount /var/run as tmpfs openSUSE-11.2: Rejected by Matthias Eckermann (mge1512) reject date: 2009-07-16 11:42:53 reject reason: Rejected on request of Engineering. Priority Requester: Mandatory Projectmanager: Important openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2010-10-06 16:02:09 reject reason: not done. Priority Requester: Mandatory Projectmanager: Important openSUSE-11.4: Done Priority Requester: Mandatory Requested by: Kay Sievers (kay_sievers) Technical Contact: Kay Sievers (kay_sievers) Partner organization: openSUSE.org Description: /var/run should be mounted as tmpfs. This would avoid the cleaning of stale files or sockets on bootup and avoid atime updates of any mounted filesystems. This is required for eg powermanagement, which currently wakes up the system from any idle states for a socket operation. Services must be modified not to depend on a preexisting content in /var/run upon startup. RPMs must be modified to not place anything there. Discussion: #2: Federico Lucifredi (flucifredi) (2008-07-08 19:30:23) somehow SLES/SLED got out of sync here. Matching. #4: Duncan Mac-Vicar (dmacvicar) (2008-07-14 15:30:03) There are no resources for this feature. Please postpone, (as agreed with MgE) #5: Duncan Mac-Vicar (dmacvicar) (2008-07-14 15:46:55) Just as a side note this feature will require an effort of aprox. 1 week, together with #303810 (they averlap about 95%) #10: Arvin Schnell (aschnell) (2009-02-04 10:50:32) Any requirements on the size for the tmpfs or should the default of tmpfs be used? #11: Arvin Schnell (aschnell) (2009-02-05 19:27:03) (reply to #10) Kay replied by personal mail: Size doesn't matter. /var/lock should also be on tmpfs. #12: Duncan Mac-Vicar (dmacvicar) (2009-06-02 11:22:49) Christoph, please reject with openSUSE 11.2, because disk encryption we can't promise this feature for 11.2. It may get done as bonus if encryption gets done earlier than expected, but we can't commit to it (which is what rejection means, which does not mean we may work on it). It is the next thing we will work on after encryption support. #32: Dirk Mueller (dirkmueller) (2010-04-26 12:08:04) rpmlint check implemented (badness 900) #35: Duncan Mac-Vicar (dmacvicar) (2010-11-03 15:50:03) Kay, is this still feature desired now with relatime as default? or can be closed forever? #36: Kay Sievers (kay_sievers) (2010-11-03 18:52:22) (reply to #35) It is a good feature to have, because we don't want to cleanup the dir on bootup. Systemd has this mandatory and you can't even disable it. #37: Andreas Jaeger (a_jaeger) (2010-11-04 09:24:36) (reply to #35) This feature is done with using systemd. The scripts mount /var/run already and packages get fixed. I don't think any changes in YaST are needed, so I guess this can be marked as done. Duncan, please check for YaST work - and if none is needed, mark as done. #38: Arvin Schnell (aschnell) (2010-11-04 12:02:02) (reply to #37) When systemd mounts it and no entry in fstab is desired the feature is done from my side. I'm sure the mounting happens after potentially mounting /var. + #39: Duncan Mac-Vicar (dmacvicar) (2013-03-05 11:29:23) + Jiri, assuming SLE12 uses systemd, this feature can be marked as done. -- openSUSE Feature: https://features.opensuse.org/303793

1 0

[openFATE 72] Thank good brainshare is over
by fate_noreply＠suse.de 04 Mar '13

04 Mar '13

Feature changed by: Thomas Schmidt (digitaltomm) Feature #72, revision 246 Title: Thank good brainshare is over Requested by: Thomas Schmidt (digitaltomm) Partner organization: openSUSE.org Description: We are all tired. Feet are hurtingXXX Rejected: Was just a test dummy during feature tool training. dbxml updated to 2.2.13 testing partner notification + new keeper testing partner notification CC testing testing new notification system test References: http://www.pfeifer.com/gerald/gerald.jerus.png Relations: - 55555 (novell/bugzilla/id: 55555) https://bugzilla.novell.com/show_bug.cgi?id=55555 - Test Case (novell/testopia/case: 12345) https://bugzilla.novell.com/tr_show_case.cgi?case_id=12345 Documentation Impact: tremendous Test Case: foo bar external ID: 123 Discussion: #1: Inttools Team (inttools) (2005-11-02 16:06:21) Remove some comments, test utf8 with kate: ???????????? #2: Gerald Pfeifer (geraldpfeifer) (2007-10-25 09:51:22) (reply to #1) Dudle. #17: Andre Duffeck (aduffeck) (2008-05-20 06:59:31) (reply to #2) test #25: Thomas Schmidt (digitaltomm) (2008-07-17 13:37:50) (reply to #17) test +šščřžčřýřáýáí + #58: Thomas Schmidt (digitaltomm) (2013-03-04 15:08:47) (reply to #17) + test #51: Michael Löffler (michl19) (2009-03-13 14:02:34) (reply to #1) blabla #55: Thomas Schmidt (digitaltomm) (2011-09-28 16:44:52) (reply to #51) Test Hermes #56: Thomas Schmidt (digitaltomm) (2011-09-28 17:01:22) (reply to #55) test hermes again #4: Andre Duffeck (aduffeck) (2007-10-25 14:17:35) webfate test #5: Gerald Pfeifer (geraldpfeifer) (2007-10-26 14:58:39) blub #6: Stephan Kulow (coolo) (2007-11-19 18:20:44) testing if this crashes too #7: Stephan Kulow (coolo) (2007-11-19 18:21:17) (reply to #6) hmm, this works #8: Andre Duffeck (aduffeck) (2008-01-07 19:10:09) test #9: Thomas Schmidt (digitaltomm) (2008-01-07 19:13:11) test #10: Andre Duffeck (aduffeck) (2008-01-07 19:43:19) test #11: Sukanta Dash (sukantadash) (2008-01-30 10:18:52) Test entry added as advised by Gerald. #12: Stephan Kulow (coolo) (2008-02-13 12:45:46) please do not use a product we're currently looking at for such tests #13: Thomas Schmidt (digitaltomm) (2008-02-20 16:14:01) test #14: Christopher Hofmann (cwh) (2008-02-21 19:32:56) Hallo, Mary Lou #15: Matthias Eckermann (mge1512) (2008-02-22 15:26:03) Brainshare will restart soon, ... #16: Andre Duffeck (aduffeck) (2008-03-05 13:20:23) blubb #19: Andre Duffeck (aduffeck) (2008-05-23 11:35:26) test #20: Gerald Pfeifer (geraldpfeifer) (2008-05-24 12:55:27) (reply to #19) Tst. #32: Juergen Weigert (jnweiger) (2008-07-23 11:31:38) (reply to #19) mal dere kleine crash zwischendurch von JW. #33: Juergen Weigert (jnweiger) (2008-07-23 11:47:57) (reply to #32) der war einfach. nochmal crash mit kdebugdialog --fullmode #41: Juergen Weigert (jnweiger) (2008-07-23 15:04:45) (reply to #33) so, und nun nochmal mit [x] enable cache .... #42: Juergen Weigert (jnweiger) (2008-07-23 15:06:09) (reply to #41) viel besser jetzt! #21: Christopher Hofmann (cwh) (2008-06-04 13:27:58) linkszwodreivier #22: Andre Duffeck (aduffeck) (2008-06-11 07:37:50) test #23: Andre Duffeck (aduffeck) (2008-06-11 07:38:18) testzwei #24: Thomas Schmidt (digitaltomm) (2008-06-11 12:15:59) Added attachment (patch_information.xml) #27: Andre Duffeck (aduffeck) (2008-07-17 16:36:20) test #30: Thomas Schmidt (digitaltomm) (2008-07-21 20:09:23) tuut #31: Andre Duffeck (aduffeck) (2008-07-23 11:22:26) test #34: Juergen Weigert (jnweiger) (2008-07-23 14:09:20) noch ein crash! #35: Andre Duffeck (aduffeck) (2008-07-23 14:11:00) blubb #36: Juergen Weigert (jnweiger) (2008-07-23 14:13:25) ghjhghj #37: Juergen Weigert (jnweiger) (2008-07-23 14:14:03) dsfgdfgfhh #38: Andre Duffeck (aduffeck) (2008-07-23 14:15:48) testcrash #39: Andre Duffeck (aduffeck) (2008-07-23 14:20:13) ttttt #40: Andre Duffeck (aduffeck) (2008-07-23 14:28:26) asdf #43: Andre Duffeck (aduffeck) (2008-07-30 07:29:33) test #44: Thomas Roelz (tomout) (2008-07-31 18:17:36) sdgdfhdfhd #45: Gerald Pfeifer (geraldpfeifer) (2008-08-15 15:36:13) (reply to #44) d #46: Andre Duffeck (aduffeck) (2008-08-26 13:56:51) test #47: Andre Duffeck (aduffeck) (2008-11-28 18:18:55) bla #49: Gerald Pfeifer (geraldpfeifer) (2009-02-09 17:16:42) (reply to #47) Nein! #54: Thomas Schmidt (digitaltomm) (2011-09-21 12:42:04) (reply to #49) Doch #50: Andre Duffeck (aduffeck) (2009-02-25 09:11:25) Changed attachment patch (patch_information.xml) #52: Thomas Schmidt (digitaltomm) (2010-08-11 14:43:33) test #53: Andre Duffeck (aduffeck) (2011-01-31 11:11:33) test #57: Thomas Schmidt (digitaltomm) (2013-02-21 20:17:14) (reply to #53) test -- openSUSE Feature: https://features.opensuse.org/72

1 0

[New: openFATE 314878] [DOCU] Merge KVM, XEN and LXC Documentation into a Single Virtualization Manual
by fate_noreply＠suse.de 01 Mar '13

01 Mar '13

Feature added by: Frank Sundermeyer (fsundermeyer) Feature #314878, revision 1 Title: [DOCU] Merge KVM, XEN and LXC Documentation into a Single Virtualization Manual Requested by: Frank Sundermeyer (fsundermeyer) Partner organization: openSUSE.org Description: Currently we have three guides covering Virtualization: * Virtualization with KVM * Virtualization with XEN * Virtualization with LXC Quickstart Although it applies to all three virtualization techniques, libvirt and tools is only covered in the KVM Guide. A single Virtualization Guide should cover libvirt and tools as a management layer for all three virtualization techniques and should also have specific parts on KVM, XEN and LXC. Documentation Impact: Merge the three guides as requested -- openSUSE Feature: https://features.opensuse.org/314878

1 0