August 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309362] Re-implement Download on Demand (DoD) feature
by fate_noreply＠suse.de 01 Mar '16

01 Mar '16

Feature added by: Adrian Schröter (adrianSuSE) Feature #309362, revision 1 Title: Re-implement Download on Demand (DoD) feature Buildservice: Done Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: The DoD features was dropped for 1.7. LinuxFoundation has re-implemented it in a cleaner way for 1.8 release. -- openSUSE Feature: https://features.opensuse.org/309362

1 8

[openFATE 305838] Integrate ReviewBoard in Buildservice
by fate_noreply＠suse.de 12 Feb '16

12 Feb '16

Feature added by: Klaas Freitag (kfreitag) Feature #305838, revision 1, last change by Title: Integrate ReviewBoard in Buildservice Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Klaas Freitag (kfreitag) Description: ReviewBoard is a code change review system. It should be considered to integrate it to the openSUSE Buildservice infrastructure to ease collaboration. It might be an option that submit requests to packages can be handled in the review board. -- openSUSE Feature: https://features.opensuse.org/305838

1 4

[New: openFATE 318951] YaST should log time like dmesg and journalctl
by fate_noreply＠suse.de 09 Feb '16

09 Feb '16

Feature added by: Joachim Werner (joachimwerner) Feature #318951, revision 1 Title: YaST should log time like dmesg and journalctl Requested by: Arvin Schnell (aschnell) Partner organization: openSUSE.org Description: YaST should log the time in its log-file like 'dmesg' and 'journalctl --output short-monotonic' so that times in the various logs can be compared and events can be synchronized. Relations: - YaST should log time like dmesg and journalctl (feature/copiedfrom: 318921) Business case (Partner benefit): openSUSE.org: Easier to analyse logs in bug reports. -- openSUSE Feature: https://features.opensuse.org/318951

1 4

[New: openFATE 313233] Get Zypper to remove installed patterns
by fate_noreply＠suse.de 15 Jan '16

15 Jan '16

Feature added by: Drew Adams (Druonysus) Feature #313233, revision 1 Title: Get Zypper to remove installed patterns openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Drew Adams (druonysus) Partner organization: openSUSE.org Description: Get Zypper to remove a pattern. Zypper can install a pattern nut when going to remove that same pattern, Zypper does not remove that pattern... When do a: "zypper rm -t pattern <pattern name>" Zypper, just tells you: "Uninstallation of a pattern is currently not defined and implemented." You CAN remove a pattern in YaST so I would think that there should be a way to remove the pattern with Zypper. "yum groupremove <group name>" works on Fedora/CentOS/RHEL... we should really have this working to keep up with them. Use Case: If I build a bare openSUSE image on SUSE Studio, and I decide not to install yast and only Zypper... I will only be able to install patterns but NO way to remove it. -- openSUSE Feature: https://features.opensuse.org/313233

1 2

[New: openFATE 312293] Option to disable disk check on certian volumes in YaST
by fate_noreply＠suse.de 04 Jan '16

04 Jan '16

Feature added by: Dean Hilkewich (deanjo13) Feature #312293, revision 1 Title: Option to disable disk check on certian volumes in YaST openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Partner organization: openSUSE.org Description: This is one really really really annoying feature in yast. Here is the scenario, you have a machine with a bunch of storage drives, drives that are normally kept full. Everytime you enter something like package management in YaST it pops up a low disk space warning. This warning should only apply for volumes where YaST utilizes for it's files (such as download cache, home, etc). A HTPC for example often has volumes full to the max. -- openSUSE Feature: https://features.opensuse.org/312293

1 1

[New: openFATE 318082] [Shell][Scripting] Shell-reqs command
by fate_noreply＠suse.de 19 Dec '15

19 Dec '15

Feature added by: Sławomir Lach (Lachu) Feature #318082, revision 1 Title: [Shell][Scripting] Shell-reqs command openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Idea is about creating tool, which checks that given programs are installed. If some program aren't installed then it call special program(dependent on user is working on console and GUI environment), which displays cnf output for missing programs. On program missing return code is not 0, so script can terminate. Idea was proposed by some Red Hat's developers many years ago, but this idea was about to automatically install tools from standard repositories. Use Case: Marek is normal computer user. He decided to download script, but to run correctly script needs some command. This script can looks like this: #!/bin/bash shell-reqs command1 command2 if [ $? -eq 1 ]; then exit fi; command1 parameter1 parameter2 command2 parameter1 parameter2 parameter3 When he run this script, desktop environment reports that command1 and command2 is missing and suggest how to install these commands. Marek will install these commands and rerun script. -- openSUSE Feature: https://features.opensuse.org/318082

1 2

[openFATE 305914] PAC support for 'system wide proxy configuration'
by fate_noreply＠suse.de 05 Dec '15

05 Dec '15

Feature added by: Dominique Leuenberger (dimstar) Feature #305914, revision 1, last change by Title: PAC support for 'system wide proxy configuration' openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Dominique Leuenberger (dimstar) Description: The distribution now contains libproxy and we should try to make as much use of it as possible. A big advantage is the ability to parse PAC (Proxy AutoConfiguration) without the need for this in every application. Simply linking against libproxy with it's very simple API (3 API calls, 2 without parameters) is enugh to have the advantage of no longer needing to 'guess' what proxy to use. What is now: - You can set in yast / proxy a general proxy to be used (http://foo.proxy.com:1234) This is bascially put into http_proxy envvar. In gnome you can set user proxy configuration as: - Use System Proxy (as configured in yast) - Use proxy configuration (static, same options as in yast) - Use automatic proxy configuration script Yast lacks the option to specify a PAC script on system wide level. This is only possible in the user sessions configuration. This made sense as most applications don't know how to handle pac files anyway. But with libroxy, this hurdle can be taken away from every single application and can thus be offered. I'm glad to elaborate on questions; I'm sure there are some :-) -- openSUSE Feature: https://features.opensuse.org/305914

1 17

[New: openFATE 318203] Let's drop commandline support from Yast
by fate_noreply＠suse.de 20 Nov '15

20 Nov '15

Feature added by: Lukas Ocilka (locilka) Feature #318203, revision 1 Title: Let's drop commandline support from Yast Requested by: Lukas Ocilka (locilka) Partner organization: openSUSE.org Description: Yast provides some kind of a commandline interface which is based on the same functions provided by standard Yast application (Qt, ncurses). Comandline could be used for scripting, but there are already tools that do it better: AutoYast, Chef, Puppet, SUSE Manager, sed (just to name some). Yast commadline has several drawbacks: * not used, not tested, not maintained, too much of obsolete code - too much maintenance for nothing * architecturally wrong - commandline interface to an app that uses commandline tools (e.g., commandline for Services Manager? This is obviously systemctl) * implemented as kind of a hack What do we lose if we remove it? * Possbility for scripting, but as Yast only builds on other cmdline tools or files, there are replacements Another possibility would be to replace commandline with a static information advicing user which tools to use to configure a particular service manually. Business case (Partner benefit): openSUSE.org: Less unused code to maintain == more time to do something that really matters -- openSUSE Feature: https://features.opensuse.org/318203

1 19

[New: openFATE 312747] Backport fix for Okular printing in KDE4 for KDE 4.7
by fate_noreply＠suse.de 18 Nov '15

18 Nov '15

Feature added by: Mindaugas Baranauskas (embar-) Feature #312747, revision 1 Title: Backport fix for Okular printing in KDE4 for KDE 4.7 openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Mindaugas Baranauskas (embar-) Partner organization: openSUSE.org Description: Please include this patch http://commits.kde.org/okular/e001fbab55aceef62ad9ca2bb87a170dacfe3fdd Kevin Kofler 2011-07-27 23:50:46 wrote: I forgot to put in a FIXED-IN tag, so let's make it clear: This fix will be in 4.8.0. 4.7.0 has already been released, and the fix requires new APIs in the Okular core, so I'm probably not supposed to backport it for 4.7.x. See https://bugs.kde.org/show_bug.cgi?id=181290#c118 -- openSUSE Feature: https://features.opensuse.org/312747

1 6

[New: openFATE 310712] Constantly usable Factory
by fate_noreply＠suse.de 18 Nov '15

18 Nov '15

Feature added by: Christoph Obexer (cobexer) Feature #310712, revision 1 Title: Constantly usable Factory openSUSE-11.4: Unconfirmed Priority Requester: Mandatory Requested by: Christoph Obexer (cobexer) Partner organization: openSUSE.org Description: I recently read about the Debain CUT project, ( http://cut.debian.net/ (http://cut.debian.net/) , http://kitenet.net/~joey/code/debian/cut/ (http://kitenet.net/~joey/code/debian/cut/) ) looking at the current situation with openSuSE Factory i see that it is dangerous to use, unstable alpha or beta packages come into Factory all the time, while other packages become out of date. The result is a system that is pretty much unusable. Only allowing stable packages to enter Factory would make that a lot better, and if one finds bugs chances are that those bugs aren't already fixed in a newer svn/git snapshot, but are real bugs. This would save a lot of time for testers and developers in dealing with "invalid", or "temporary" bugs. I think that a robust, "stable" Factory would lead to more people using it full time and thus a better quality of the next openSuSE version. I see that this would have negative aspects as well, but i think most devel projects have unstable/testing repositories set up already and those could still contain the snapshots of upcoming versions, testers of those specific projects could use tose repositories then. Doing a release of openSuSE would be easier then too, simply snapshot Factory, and declare it as openSuSE $VERSION. The transition from the current state to a "constantly usable Factory" would be smooth too. And it's also in line with the openSuSE vision, stable rather than bleeding edge. Business case (Partner benefit): openSUSE.org: More users using Factory -> better stability of Factory -> better stability of openSuSE $VERSION -> openSuSE back where it should be - the Linux for professionals. -- openSUSE Feature: https://features.opensuse.org/310712

1 4

[New: openFATE 309700] Advanced uninstall/Rollback support in package management, zypper
by fate_noreply＠suse.de 30 Oct '15

30 Oct '15

Feature added by: Nikanth K (nikanth) Feature #309700, revision 1 Title: Advanced uninstall/Rollback support in package management, zypper openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Nikanth K (nikanth) Description: # Zypper install evolution This will install say 13 packages, evolution and its dependencies including evolution-data-server etc.... #zypper remove evolution This will remove only evolution. Leaving the dependencies installed. The 12 packages are left installed. Instead provide an easy way to rollback/uninstall all those packages using say a transaction-id from the history. So that, say we have foo.rpm which needs bar.rpm #zypper install foo #zypper remove foo will not leave bar installed in the system. -- openSUSE Feature: https://features.opensuse.org/309700

1 4

[New: openFATE 309070] Allow auth
by fate_noreply＠suse.de 27 Oct '15

27 Oct '15

Feature added by: Adrian Schröter (adrianSuSE) Feature #309070, revision 1 Title: Allow auth Buildservice: Evaluation Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Description: Implement authentification plugin for api which allows authentification against remote http web server. This may need changes in session handling. We want to use this plugin and setup for opensuse.org and connect api.o.o and build.o.o directly to internet without iChain proxy. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-23 12:06:04) Tom, we need your expertise here, what is possible with rails and what makes sense. -- openSUSE Feature: https://features.opensuse.org/309070

1 7

[New: openFATE 310233] skip repo update when installing packages with zypper
by fate_noreply＠suse.de 24 Sep '15

24 Sep '15

Feature added by: Denny Beyer (lumnis) Feature #310233, revision 1 Title: skip repo update when installing packages with zypper openFATE: Unconfirmed Priority Requester: Important Requested by: Denny Beyer (lumnis) Description: When installing a new package with zypper etc. everytime you run zypper, repos get updated and the user has to wait. Because a general user needs several extra repos, this waiting time always seems to be too long. Why not running 'zypper ref' as a low priority task after startup/time intervall has passed and give the used immidiate access to install a software package? -- openSUSE Feature: https://features.opensuse.org/310233

1 18

[New: openFATE 318306] Systemd service to catch crashed X, try to auto repair it and restart
by fate_noreply＠suse.de 08 Sep '15

08 Sep '15

Feature added by: Mindaugas Baranauskas (embar-) Feature #318306, revision 1 Title: Systemd service to catch crashed X, try to auto repair it and restart openSUSE Distribution: Unconfirmed Priority Requester: Important SUSE Studio: Unconfirmed Priority Requester: Important Requested by: Mindaugas Baranauskas (embar-) Partner organization: openSUSE.org Description: We could have solution automatically detect, if X.Org X Server terminated with error. Then we could try repair X configuration and restart X server. Test Case: That case encouraged me to write systemd service and script, which temporaly is named as check-x-failed. You can download it as systemd-check-x-failed-service RPM package: http://software.opensuse.org/download.html?project=home%3Aembar-%3ALietukas… Source is here: https://build.opensuse.org/package/show/home:embar-:Lietukas/systemd-check-… This is included in openSUSE based appliance âLietukasâ ( https://susestudio.com/a/CttYWz/lietukas-13-2-64-bit ) Use Case: This is very important now as we swithed to system and much system modules are included in initrd. This my cose much problems, e.g. then we we boot from LiveCD/LiveUSB. One problematic case described here: http://suse-studio-users.1598176.n2.nabble.com/Tesdrive-OK-but-does-not-dir… -- openSUSE Feature: https://features.opensuse.org/318306

1 5

[New: openFATE 312852] Hack your windows with sticky notes
by fate_noreply＠suse.de 25 Aug '15

25 Aug '15

Feature added by: Christopher De Nicolo (dec16180) Feature #312852, revision 1 Title: Hack your windows with sticky notes Hackweek VII: Unconfirmed Priority Requester: Desirable Requested by: Christopher De Nicolo (dec16180) Partner organization: openSUSE.org Description: What geeks really need: http://www.geekosystem.com/french-post-it-note-war/ -- openSUSE Feature: https://features.opensuse.org/312852

1 5

[New: openFATE 312810] Build a wireless lan access point
by fate_noreply＠suse.de 25 Aug '15

25 Aug '15

Feature added by: Juergen Weigert (jnweiger) Feature #312810, revision 1 Title: Build a wireless lan access point openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Juergen Weigert (jnweiger) Partner organization: openSUSE.org Description: Use hostap mode to turn a laptop into a full featured access point. (not just ad-hoc). Find out which hardware is suitable. I have an USB-Wlan-dongle with rt73 chipset, whichis reported to support AP-mode. -- openSUSE Feature: https://features.opensuse.org/312810

1 3

[New: openFATE 319359] Wicked Internet Connection Tool
by fate_noreply＠suse.de 22 Aug '15

22 Aug '15

Feature added by: Norman Gorlt (norgo70) Feature #319359, revision 1 Title: Wicked Internet Connection Tool openFATE: Unconfirmed Priority Requester: Important Requested by: Norman Gorlt (norgo70) Partner organization: openSUSE.org Description: Up to openSUSE 13.1 we had the option to use ifup alternatively to Networkmanager. Internet connection via ifup was easy to use because we had smpppd and qinternet e.g. Now ifup is replaced by wicked and smpppd and qinternet aren't available anymore. For desktop computer with a fixed internet connection it's quite silly to use Networkmanager in my opinion. In this case wicked would be a good choice. But, unfortunately there don't exist a simple connection tool for easy useability. Connecting or disconnecting of internet connection via command line is not userfriendly. I would wish a simple icon in the taskbar similar we had in qinternet. Fist click onto icon establish the connection, 2nd click disconnect network connection. Maybe right click to show up/down load data rate. -- openSUSE Feature: https://features.opensuse.org/319359

1 1

[New: openFATE 319369] add Svdvorak to supported keyboard layouts
by fate_noreply＠suse.de 21 Aug '15

21 Aug '15

Feature added by: August Lindberg (aggelito) Feature #319369, revision 1 Title: add Svdvorak to supported keyboard layouts openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: August Lindberg (aggelito) Partner organization: openSUSE.org Description: Right now there are no alternatives for swedish dvorak layouts in the system keyboard layouts. Having the Svdvorak layout as a supported layout would be a nice addition. -- openSUSE Feature: https://features.opensuse.org/319369

1 1

[New: openFATE 314922] Amazon EC2
by fate_noreply＠suse.de 14 Aug '15

14 Aug '15

Feature added by: Paulo Andrade (bugsoftware) Feature #314922, revision 1 Title: Amazon EC2 SUSE Studio: Unconfirmed Priority Requester: Important Requested by: Paulo Andrade (bugsoftware) Partner organization: openSUSE.org Description: I would like Amazon EC2 support for Opensuse 12.3 -- openSUSE Feature: https://features.opensuse.org/314922

1 2

[New: openFATE 311401] Live CD templates
by fate_noreply＠suse.de 14 Aug '15

14 Aug '15

Feature added by: Mustafa Hadi (mustafa1987) Feature #311401, revision 1 Title: Live CD templates SUSE Studio: Unconfirmed Priority Requester: Desirable Requested by: Mustafa Hadi (mustafa1987) Partner organization: openSUSE.org Description: Add a template with their default package selection is all the software available on the live CDs (KDE Live CD and Gnome Live CD) and the software automatically selected on the first yast software manager run, adding these templates is not hard to do (they are just package selection lists) an its benifits will be great. Business case (Partner benefit): openSUSE.org: To provide a complete operating system that can be then extended with additional software, the KDE4 template is just not enough. -- openSUSE Feature: https://features.opensuse.org/311401

1 3

[openFATE 305015] support noarch via own scheduler in Build Service
by fate_noreply＠suse.de 14 Aug '15

14 Aug '15

Feature changed by: Adrian Schröter (adrianSuSE) Feature #305015, revision 13 Title: support noarch via own scheduler in Build Service Buildservice: Evaluation by engineering manager Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: We would like to build noarch packages only once to avoid multiple builds and wasted space on the server. This can be reached by building noarch packages only via an dedicated scheduler. However, we need to avoid that have a horrible project configuration, where all BuildRequired noarch packages needs to get submitted into all other architecture repository :full trees. + The biggest problem is that build cycle detection is not working + accross schedulers. We would have endless builds easily with the + current code. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-19 10:48:58) Theoretically already possible, still questionable if we want this. -> keep it in evaluation #2: Greg Freemyer (gregfreemyer) (2012-03-30 20:14:05) I can think of of at least 3 ways to accomplish the goal: 1) Allow noarch builds of just one arch to be accepted to factory. Then encourage people to just enable one arch. Hopefully randomly to spread the load around. 2) Create a new "noarch" architecture and scheduler. Have that feed whatever actual scheduler has the lightest load at schedule time. That way even non-Intel machines could build the noarch packages. 3) Enforce in all schedulers but one, that they ignore noarch packages. Then document that so everyone knows they can only build noarch on i586 (as an example). idea 1) seems relatively doable for a modest effort. idea 2) would require changes lots of places I assume, so it is not trivial. idea 3) seems like the least work by far, and it sheds work load from one of the schedulers. I don't know if that would benefit the overall OBS load or not. And I'm sure there are other ways. === The question is if the wasted build resources is worth the R&D to bother with fixing this. #3: Claudio Freire (klaussfreire) (2012-03-30 20:30:05) (reply to #2) 3) Enforce in all schedulers but one, that they ignore noarch packages. Then document that so everyone knows they can only build noarch on i586 (as an example). I think this is the best option. For one, making sure noarch packages are built in the same architecture every time will help avoid spurious deltas: if a package builds differently on different architectures, but the packager decided that the difference is inconsequential. For instance, arm zlib needs not produce the same output as x86 zlib. For two, i586 and x86_64, AFAIK, use the same hosts. Right? So spreading the load among those two is useless. But there are quite a few caveats. One, people should not care about which arch is enabled, if there is any enabled archs for a noarch package, it should be built by "the noarch" scheduler (say, the x86_64 scheduler). If there are many archs enabled, only one build should be scheduled, and build results should be replicated. This might need some doing. 2) Create a new "noarch" architecture and scheduler. Have that feed whatever actual scheduler has the lightest load at schedule time. That way even non-Intel machines could build the noarch packages. So, more to-the-point would be option 2, but it still doesn't completely convince me, because it would be quite confusing in the UI. There also option 1, which I guess would work for factory (but not other projects). It's already common practice in OBS to only enable one arch for big noarch packages, so it should be rather easy to do - just fix factory-auto's validation script to account for noarch packages. About the benefits, I have a few projects that build hundred-MB noarch rpms with game data. Those take a lot of I/O resources to build, so the inefficiency (in that case) is significant. I'm not sure about how many projects are found in that situation, though. I would vote to get option 1 implemented ASAP - it should be easy and immediate. If I wanted to patch it... where should I go to find the factory-auto script? #5: Jan Engelhardt (jengelh) (2015-08-14 00:06:13) (reply to #2) >[3.] Then document that so everyone knows they can only build noarch on i586 And if you have no x86? Like, a PPC-only pool. Suggestion [2] doing a round-robin seems preferable. #4: Stefan Brüns (stefanbruens) (2015-07-20 17:10:51) I think this should be reevaluated - ARM builds are really slow, and e. g kernel-docs takes a full day to rebuild. -- openSUSE Feature: https://features.opensuse.org/305015

1 0

[openFATE 305015] support noarch via own scheduler in Build Service
by fate_noreply＠suse.de 13 Aug '15

13 Aug '15

Feature changed by: Jan Engelhardt (jengelh) Feature #305015, revision 12 Title: support noarch via own scheduler in Build Service Buildservice: Evaluation by engineering manager Priority Requester: Desirable Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: We would like to build noarch packages only once to avoid multiple builds and wasted space on the server. This can be reached by building noarch packages only via an dedicated scheduler. However, we need to avoid that have a horrible project configuration, where all BuildRequired noarch packages needs to get submitted into all other architecture repository :full trees. Discussion: #1: Adrian Schröter (adriansuse) (2010-02-19 10:48:58) Theoretically already possible, still questionable if we want this. -> keep it in evaluation #2: Greg Freemyer (gregfreemyer) (2012-03-30 20:14:05) I can think of of at least 3 ways to accomplish the goal: 1) Allow noarch builds of just one arch to be accepted to factory. Then encourage people to just enable one arch. Hopefully randomly to spread the load around. 2) Create a new "noarch" architecture and scheduler. Have that feed whatever actual scheduler has the lightest load at schedule time. That way even non-Intel machines could build the noarch packages. 3) Enforce in all schedulers but one, that they ignore noarch packages. Then document that so everyone knows they can only build noarch on i586 (as an example). idea 1) seems relatively doable for a modest effort. idea 2) would require changes lots of places I assume, so it is not trivial. idea 3) seems like the least work by far, and it sheds work load from one of the schedulers. I don't know if that would benefit the overall OBS load or not. And I'm sure there are other ways. === The question is if the wasted build resources is worth the R&D to bother with fixing this. #3: Claudio Freire (klaussfreire) (2012-03-30 20:30:05) (reply to #2) 3) Enforce in all schedulers but one, that they ignore noarch packages. Then document that so everyone knows they can only build noarch on i586 (as an example). I think this is the best option. For one, making sure noarch packages are built in the same architecture every time will help avoid spurious deltas: if a package builds differently on different architectures, but the packager decided that the difference is inconsequential. For instance, arm zlib needs not produce the same output as x86 zlib. For two, i586 and x86_64, AFAIK, use the same hosts. Right? So spreading the load among those two is useless. But there are quite a few caveats. One, people should not care about which arch is enabled, if there is any enabled archs for a noarch package, it should be built by "the noarch" scheduler (say, the x86_64 scheduler). If there are many archs enabled, only one build should be scheduled, and build results should be replicated. This might need some doing. 2) Create a new "noarch" architecture and scheduler. Have that feed whatever actual scheduler has the lightest load at schedule time. That way even non-Intel machines could build the noarch packages. So, more to-the-point would be option 2, but it still doesn't completely convince me, because it would be quite confusing in the UI. There also option 1, which I guess would work for factory (but not other projects). It's already common practice in OBS to only enable one arch for big noarch packages, so it should be rather easy to do - just fix factory-auto's validation script to account for noarch packages. About the benefits, I have a few projects that build hundred-MB noarch rpms with game data. Those take a lot of I/O resources to build, so the inefficiency (in that case) is significant. I'm not sure about how many projects are found in that situation, though. I would vote to get option 1 implemented ASAP - it should be easy and immediate. If I wanted to patch it... where should I go to find the factory-auto script? + #5: Jan Engelhardt (jengelh) (2015-08-14 00:06:13) (reply to #2) + >[3.] Then document that so everyone knows they can only build noarch + on i586 And if you have no x86? Like, a PPC-only pool. + Suggestion [2] doing a round-robin seems preferable. #4: Stefan Brüns (stefanbruens) (2015-07-20 17:10:51) I think this should be reevaluated - ARM builds are really slow, and e. g kernel-docs takes a full day to rebuild. -- openSUSE Feature: https://features.opensuse.org/305015

1 0

[New: openFATE 318204] Drop Yast LXC (replaced by libvirt / docker)
by fate_noreply＠suse.de 05 Aug '15

05 Aug '15

Feature added by: Lukas Ocilka (locilka) Feature #318204, revision 1 Title: Drop Yast LXC (replaced by libvirt / docker) Requested by: Lukas Ocilka (locilka) Partner organization: openSUSE.org Description: Yast LXC is not needed anymore, libvirt-lxc already covers that. Additionally, docker with Yast Docker module seem to be a good replacement for LXC. Business case (Partner benefit): openSUSE.org: Less code to maintain, less bugs. Yast doesn't need to provide functionality that already exists and is maintained elsewhere. -- openSUSE Feature: https://features.opensuse.org/318204

1 6

[New: openFATE 319299] require libvirt-images subvolume creation at install time
by fate_noreply＠suse.de 03 Aug '15

03 Aug '15

Feature added by: Chris Murphy (cmurf) Feature #319299, revision 1 Title: require libvirt-images subvolume creation at install time Requested by: Chris Murphy (cmurf) Partner organization: openSUSE.org Description: Similar to https://features.opensuse.org/319287 Create a subvolume in the top level of the file system for libvirt images, and add it to fstab to mount at /var/lib/libvirt/images/ Without this, any rollback will be missing virt-manager VM images. -- openSUSE Feature: https://features.opensuse.org/319299

1 4