November 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305693] Versioning for project data
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Martin Mohring (MartinMohring) Feature #305693, revision 1, last change by Title: Versioning for project data Buildservice: Unconfirmed Priority Requester: Mandatory Requested by: Martin Mohring (martinmohring) Partner organization: openSUSE.org Description: Currently, we have versioning of the source files with OBS.Since at least projconf correlates to the sources, it should be versioned to make versioning more of a feature to restore old versions reproducable. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305693

1 3

[openFate 305625] Emphasize my packages in a project maintained by me.
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305625, revision 1, last change by Title: Emphasize my packages in a project maintained by me. Buildservice: New Requested by: Pavol Rusnak (prusnak) Partner organization: openSUSE.org Description: When I'm a maintainer of a project and also set as an explicit maintainer of a package inside this project, I'm unable to list of these packages. "My Projects" shows only affected projects and packages outside of these projects. I suggest to show emphasize such packages in Project view (package list) for example by adding icon, or showing the package name in bold. This is especially needed for Contrib repository. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305625

1 3

[openFate 305592] Warn on creating of the package that already exists in BuildService
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305592, revision 1, last change by Title: Warn on creating of the package that already exists in BuildService Buildservice: New Priority Requester: Important Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00056.html * warn on creating of the package that already exists in BuildService (webclient and osc) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305592

1 3

[openFate 305590] Virtual packages and virtual joint projects
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305590, revision 1, last change by Title: Virtual packages and virtual joint projects Buildservice: New Priority Requester: Desirable Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00094.html Virtual packages and virtual joint project would be a special type of projects, that are part of a standard binary repository, but they have no source present in the project. It may have several typical use cases: Virtual dependency packages --------------------------- When a project intents to update a library to a newer version, virtual dependency packages and projects may determine packages that will have broken/changed dependencies after installing of a new library. How it should look. Either package or a project should have a new attribute: "Rebuild parent project packages" Possible values: "ignore": Rebuild only packages in this project and nothing else (just the current behavior) "rebuild broken": Rebuild parent project packages, that cannot be used with newer version any more (it typically happens for package, that require exact version it is built against, or packages that don't follow shared library packaging conventions) "smart rebuild": Rebuild packages that require package or symbol that are no more part of the output of the new package. "all dependencies": Behave just like a single repository and rebuild everything which uses the new in the build. Examples of use for particular values: "rebuild broken": Building some modules require the same version of the base package it was build with. When trying to update base package in a project, it will rebuild all such modules. "smart rebuild": Testing package poppler update: New poppler has a new soname and it requires to rebuild all packages that are linked with poppler. However it is possible to install these packages (and use shared library from the parent project), testing of the new library requires to rebuild these package with the new library). "all dependencies": Testing new core package (bison, gcc). All packages, that have this package in BuildRequires on build system will be rebuilt. Virtual package may become non-virtual. If you need to patch one of the packages to be able to rebuild it in the new repository, you have to link it physically to the joint repository. In this moment, package becomes equal to the normal link package, disabled by default. Virtual/non-virtual joint project --------------------------------- Just now, one can include two different projects, that have a disjunctive packages. Virtual joint project would determine packages that will build differently (or break) in one or another parent repository and rebuild them as a separate repository. Virtual joint project could be a separate project that contains rebuilds of packages in the intersection of both project. Virtual joint project may become non-virtual. If you need to patch one of the packages to be able to rebuild it with both projects included, you have to add it physically to the joint repository. In this moment, the joint project feature would be equal to the normal repository with "Rebuild parent project packages" set. Example: Suppose you have a testing repository of new poppler (different soname) and a multimedia:photo with a new version of GIMP (requires poppler). You can easily include both multimedia:photo and poppler test repositories, but you cannot test new gimp with a new poppler. Creating of virtual joint project will automatically detect these packages and rebuild them. There could be again the tag "Rebuild parent projects packages" with the same values as above. Benefits: Virtual packages: Now they are often substituted by links. Several years later, nobody knows, why such link was created and the link may rot there forever. Virtual joint project: It will allow to test result of a dangerous package check-in without actually doing it. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305590

1 3

[openFate 305595] Show dependencies between packages in repo
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305595, revision 1, last change by Title: Show dependencies between packages in repo Buildservice: New Priority Requester: Important Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: * Show dependencies (Requires, BuildRequires) between packages in repository OBS should provide lists of required packages (runtime and build dependencies) - BuildRequires could be extracted from spec files - it is important to show also reverse dependencies (eg. which packages depend on the package I'm maintaining) - Requires are much harder (will probably need also symbol resolution), but not so desperately needed as BuildRequires -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305595

1 4

[openFATE 305937] Delete Request Mechanism
by fate_noreply＠suse.de 19 Feb '10

19 Feb '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #305937, revision 1, last change by Title: Delete Request Mechanism Buildservice: Evaluation Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Description: As part of our PDB migration, we need a mechanism to request a package removal in a project, where no write access exists. Klaas, can you make a proposal how a package (and project ?) removal can look alike ? -- openSUSE Feature: https://features.opensuse.org/305937

1 3

[New: openFATE 308408] Add lightscibe applications to installation DVD or repo
by fate_noreply＠suse.de 17 Feb '10

17 Feb '10

Feature added by: Mindaugas Baranauskas (embar-) Feature #308408, revision 1 Title: Add lightscibe applications to installation DVD or repo openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Mindaugas Baranauskas (embar-) Description: Add lightscibe applications to installation DVD or repo, for example http://www.lacie.com/download/drivers/4L-1.0-r6.i586.rpm and drivers from http://lightscribe.com/downloadSection/linux/index.aspx -- openSUSE Feature: https://features.opensuse.org/308408

1 4

[New: openFATE 308367] Rename YaST2 to YaST
by fate_noreply＠suse.de 14 Feb '10

14 Feb '10

Feature added by: Lars Müller (lmuelle) Feature #308367, revision 1 Title: Rename YaST2 to YaST openSUSE-11.3: New Priority Requester: Desirable Requested by: Lars Müller (lmuelle) Partner organization: openSUSE.org Description: YaST1 is gone for a long time but we still use everywhere YaST2. I'm not suggesting to drop the yast2 cmd. My intention is to only use the word "YaST" in the documentation (in the app and printed) and in the screenshots. See also http://bugzilla.novell.com/show_bug.cgi?id=555659 Business case (Partner benefit): openSUSE.org: Make the wording easier. Make IT Work As One. ;) -- openSUSE Feature: https://features.opensuse.org/308367

1 2

[openFATE 307391] yast2-control-center-qt4 move back to qt "appereance"
by fate_noreply＠suse.de 14 Feb '10

14 Feb '10

Feature added by: andrea florio (anubisg1) Feature #307391, revision 1 Title: yast2-control-center-qt4 move back to qt "appereance" openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: andrea florio (anubisg1) Description: Finally yast developers are moving control-center to qt4, but installing the version provided in kde:kde4:factory:desktop i saw that really bad looking, It actually lookss the gnome version written in qt4, with that i mean that it appears like a single long list of yast modules. That list is too long and confuse the user, in the same way, selecting groups on right side, produce nothing useful because the modules available on that groups are still hidden (only the first one is on the bottom of the page). i think developers should maintain qt3 layout where you see only modules available on that group and possibly in 2 or more columns -- openSUSE Feature: https://features.opensuse.org/307391

1 9

[openFATE 306990] pkgconfig automatic provides / requires
by fate_noreply＠suse.de 12 Feb '10

12 Feb '10

Feature added by: Andrew Jorgensen (ajorgensen) Feature #306990, revision 1 Title: pkgconfig automatic provides / requires openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Andrew Jorgensen (ajorgensen) Description: Integrate macros for automatically determining RPM provides / requires based on pkgconfig for -devel packages. This would consequently automatically determine the dependency chains between -devel packages that use pkgconfig. It would also allow packagers to use the pkgconfig(pkg) string instead of the specific -devel package name. This would make packaging easier both for cross-distro spec files and because when configure complains that a pkgconfig package is missing the packager can immediately add the BuildRequires rather than searching to determine which package contains that .pc file. Fedora and Mandriva both already have this feature. -- openSUSE Feature: https://features.opensuse.org/306990

1 5