February 2014 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 308489] Source Code Distribution
by fate_noreply＠suse.de 13 Feb '14

13 Feb '14

Feature added by: Andreas Jaeger (a_jaeger) Feature #308489, revision 1 Title: Source Code Distribution Buildservice: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: Make it easy to download source packages of milestone and final releases, e.g. with a specific web page with input of package name and release version. Btw. we should also document in the wiki properly how we distribute source code for milestone and final releases - and how for build service packages. Business case (Partner benefit): openSUSE.org: Source code availability is a requirement of the various Open Source licenses, this feature will help us to do this properly and in a documented way. -- openSUSE Feature: https://features.opensuse.org/308489

1 7

[New: openFATE 315250] Make it easier to move around kiwi files in OBS
by fate_noreply＠suse.de 13 Feb '14

13 Feb '14

Feature added by: Adrian Schröter (adrianSuSE) Feature #315250, revision 1 Title: Make it easier to move around kiwi files in OBS Buildservice: Implementation Milestone: 2.5 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: We have often problems when moving around kiwi files in OBS, since they often need a changed repository list then. OBS will support a directive to use the repositories from the project repository definition instead. This can be triggered via defining an "obsrepositories:/" repository in the kiwi file. OBS (and osc) will patch then the kiwi file when a build starts to use the expanded repository list from the project definition. It will work therefore with all kiwi version, but we should add some proper error message to kiwi, if someone tries to run kiwi manually on such a file. -- openSUSE Feature: https://features.opensuse.org/315250

1 23

[New: openFATE 316834] Licensing problems of cdrtools
by fate_noreply＠suse.de 07 Feb '14

07 Feb '14

Feature added by: Chuck Norris (bugmenot12) Feature #316834, revision 1 Title: Licensing problems of cdrtools Buildservice: Unconfirmed Priority Requester: Important Requested by: Chuck Norris (bugmenot12) Partner organization: openSUSE.org Description: In https://features.opensuse.org/311186 it was discussed that cdrtools do not have a valid license (for binary distribution) because of linking GPL to CDDL code. Nevertheless, the opensource build system does include a number of copies of cdrtools. Maybe cdrtools needs to be put on a block list, because of this known license problem? See e.g. https://build.opensuse.org/package/show/multimedia:apps/cdrtools but searching for "cdrtools" will yield other copies of this software that cannot be legally distributed in compiled form. -- openSUSE Feature: https://features.opensuse.org/316834

1 5

[openFATE 309385] Improve "Pattern" handling
by fate_noreply＠suse.de 05 Feb '14

05 Feb '14

Feature changed by: Frederic Crozat (fcrozat) Feature #309385, revision 40 Title: Improve "Pattern" handling openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2013-08-09 13:10:33 reject reason: Not done for 11.3. Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Michael Andres (mlandres) + Partner organization: openSUSE.org Description: We need to clearly define the way to deal with patterns. - The code11 decision not to install pattern makes them hard to handle. The solver not knowing which patterns were actually selected by the user results in bugs like https://bugzilla.novell.com/show_bug.cgi?id=576059 or https://bugzilla.novell.com/show_bug.cgi?id=676994. It also produces poor results on upgrades, as we can only guess which patterns should be updated. - The approach on opensuse 11.2 to use a package to represent the pattern and it's dependencies might be a step into the right direction (similar to the release-package representing a product). But the link between a pattern and it's prepresenting package is missing. This leads to bugs like https://bugzilla.novell.com/show_bug.cgi?id=592640, where actions like 'set Taboo' on patterns have no effect, because we don't know, thus can't lock, the corresponding package. Another open issue is removal of patterns like in https://bugzilla.novell.com/show_bug.cgi?id=407040. Removing the pattern package with cleanup enabled could be an option. This also requires a link between pattern and package. Whithout a decision accepted by all stakeholders, libzypp/zypper won't be able to resolve several bugs satisfactory. Discussion: #19: Michael Andres (mlandres) (2014-01-27 11:35:53) Done in libzypp-14.7.0 / libsolv-0.4.2 for alpha3. We should be able to drop the old pattern metadata files. -- openSUSE Feature: https://features.opensuse.org/309385

1 0