October 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307196] Buildservice: Accepting of Submissions only with Successfully Build Packages
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Andreas Jaeger (a_jaeger) Feature #307196, revision 1 Title: Buildservice: Accepting of Submissions only with Successfully Build Packages Buildservice: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: I recently noticed that somebody submitted a package to openSUSE:Factory (and it got checked in) that has never ever build in the build service since it has obvious packaging problems (the %setup step did not work at all plus many more problems). I propose that "osc request show" informs the reviewer about the build status of the package. Additionally, "osc accept" should ask for confirmation if the package has not build successfully. Business case (Partner benefit): openSUSE.org: This will help to not have packages that do not build at all. -- openSUSE Feature: https://features.opensuse.org/307196

1 3

[openFATE 307480] Development of .spec files - .specfile editor and wizard
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Glenn Doig (doiggl) Feature #307480, revision 1 Title: Development of .spec files - .specfile editor and wizard Buildservice: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Hello, Can this tool be included to help and assist on the creation of .spec files ?. http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide (http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide) The Specfile Editor plug-in provides a wizard for creating new .spec files too. Cheers Glenn -- openSUSE Feature: https://features.opensuse.org/307480

1 1

[openFATE 307474] Show link-tooltip also in stage succeeded with info from build-compare
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Jan-Simon Möller (dl9pf) Feature #307474, revision 1 Title: Show link-tooltip also in stage succeeded with info from build-compare Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Jan-Simon Möller (dl9pf) Description: Use-Case: If a package is in status "Finished" we already display e.g. "new build"/"no change" info. We should show the same data also in state succeeded when hovering the link. It helps on large projects to keep easily track on unchanged build. -- openSUSE Feature: https://features.opensuse.org/307474

1 1

[openFATE 307841] distributed computing for build service
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Adam Mizerski (etamPL) Feature #307841, revision 1 Title: distributed computing for build service Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Adam Mizerski (etampl) Description: Facts: Build service is overloaded. Now there is about 5000 packages in i586 waiting queue and the same in x86_64. Few days ago it was 3000, so it's growing. My idea: Distributed packaging using BOINC (http://boinc.berkeley.edu) platform. I think that for security reasons big and important packages (like kernel) should be build on OBS build hosts, but everything else can be distributed. -- openSUSE Feature: https://features.opensuse.org/307841

1 4

[openFATE 307840] add aggregate next to link package in web client
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Adam Mizerski (etamPL) Feature #307840, revision 1 Title: add aggregate next to link package in web client Buildservice: Unconfirmed Priority Requester: Important Requested by: Adam Mizerski (etampl) Description: Creating aggregations, where features of linking (like project patches) are not needed, will unburden build hosts. If there is no option in web client to create them, beginners will create links and create unneeded load of packages to compile. -- openSUSE Feature: https://features.opensuse.org/307840

1 1

[openFATE 307916] osc plugin for writing patchinfos
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Dirk Mueller (dirkmueller) Feature #307916, revision 1 Title: osc plugin for writing patchinfos Buildservice: New Priority Requester: Mandatory Requested by: Dirk Mueller (dirkmueller) Description: We need an externally accessible way to write a patchinfo and submit it as part of an update to Update:Test The ideal implementation would be a osc plugin that provides functionality similar to the internally available tool edit_patchinfo. It should be able to use the date provided by the build service. in its first iteration, it should not support the patchinfo validation steps that the internal tool does. Ideally it should write a "_patchinfo" file that is added to the current osc package working copy and can be submitted as part of osc submitrequest for an update. -- openSUSE Feature: https://features.opensuse.org/307916

1 4

[openFATE 308074] Provide way to do a local build and upload the binaries to the repository
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Sankar P (psankar) Feature #308074, revision 1 Title: Provide way to do a local build and upload the binaries to the repository Buildservice: Unconfirmed Priority Requester: Important Requested by: Sankar P (psankar) Description: Most of my time in build service is spent in seeing "Scheduled" There are always 1000s of packages waiting in queue for i586 and x86_64. I have a pretty powerful machine and would like to do my own local build and upload the binaries to the project repository. -- openSUSE Feature: https://features.opensuse.org/308074

1 8

[openFATE 306006] btrfs in openSUSE
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Marek Stopka (m4r3k) Feature #306006, revision 1, last change by Title: btrfs in openSUSE openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Marek Stopka (m4r3k) Description: I think it is time to make btrfs as a part of upcoming openSUSE 11.2, probably with BIG warning but still there should be possibility to use btrfs and even better with some kind of integration in YaST disk module... Fedora is going for btrfs with next release either. -- openSUSE Feature: https://features.opensuse.org/306006

1 12

[openFATE 307914] package maintenance owner handling
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #307914, revision 1 Title: package maintenance owner handling Buildservice: Evaluation Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Dirk Mueller (dirkmueller) Description: We need to support the package maintainer handling for maintenance update via a new mechanism for the following reasons: * internal PDB is not be used anymore for openSUSE 11.2 * We have now the situation that package X may have different maintainers depending on maintained products. Current discussion points to the following needs: * bugowner needs to be set on packages also for released product projects (like openSUSE:11.1). * request mechanism to add or change a bugowner in foreign projects * maintained products/projects list must be requestable (can be hardcoded list in first attempt) * osc command needs to find all projects and package maintainers for a certain package via an api call. Later steps: * define how a maintained package can be set in the projects * support a "osc prepare_maintainance_update $package" call which creates one projects with all affected package versions for a certain package. * SWAMP integration. -- openSUSE Feature: https://features.opensuse.org/307914

1 5

[openFATE 308133] Easy way to add information about a repository to be shown during its activation
by fate_noreply＠suse.de 21 Jan '10

21 Jan '10

Feature added by: Lubos Lunak (llunak) Feature #308133, revision 1 Title: Easy way to add information about a repository to be shown during its activation Buildservice: New Priority Requester: Desirable Requested by: Lubos Lunak (llunak) Description: Currently there doesn't seem to be a simple way to give information to use users who add a repository. For example, users adding the KDE:KDE4:Factory:Desktop repository should know that the KDE provided there a working version for the next openSUSE release and it may not be as stable as they might expect (they can just read about the repository e.g. in a forum and not know more). One way to do this could be to reuse the licence dialog, showing information about the repository instead of a licence, but there appears to be no simple way to do this (it reportedly requires creating a ftp product somehow, for which I could find any usable instructions). -- openSUSE Feature: https://features.opensuse.org/308133

1 1