November 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307729] Officially Provide LXDE
by fate_noreply＠suse.de 25 Jan '10

25 Jan '10

Feature added by: andrea florio (anubisg1) Feature #307729, revision 1 Title: Officially Provide LXDE openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: andrea florio (anubisg1) Partner organization: openSUSE.org Description: LXDE stands for L ightweight X 11 D esktop E nvironment.It is an extremely faster, performing and energy saving desktop environment. It is maintained by an international community of developers and comes with a beautiful interface, multi-language support, standard keyboard short cuts and additional features like tabbed file browsing LXDE actually is lighter than xfce and it's stable and mature enought to stay into openSUSE. Actually big distros like mandriva already provides LXDE. Mandriva for example allow you to install LXDE from DVD media. The only "problem" that LXDE has is the Login Manager, xdm is quite ugly and SLIM looks to be no more developed. That "problem" will be hopefully fixed in few weeks, infact they are now developing their login manager, LXDM as you can see here: http://blog.lxde.org/?p=531 Will be wonderful to have LXDE officially supported by openSUSE and why not, even available into the installation media. more infos: http://en.opensuse.org/LXDE http://lxde.org/ Use Case: The user will find LXDE packages into OSS repository, He will be able to install it using patterns. The user will install openSUSE using DVD, on DE selection he will able to select "other DE" and then LXDE from that list Business case (Partner benefit): openSUSE.org: Because that will attract more user, and will allow you to provide an openSUSE version able to running on 128MB of ram with X server running -- openSUSE Feature: https://features.opensuse.org/307729

1 32

[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

[New: openFATE 308295] [hermes] option to provide diff of changes in notification (prjconf/pkg changed)
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Jan-Simon Möller (dl9pf) Feature #308295, revision 1 Title: [hermes] option to provide diff of changes in notification (prjconf/pkg changed) Buildservice: Unconfirmed Priority Requester: Important Requested by: Jan-Simon Möller (dl9pf) Description: Mail from hermes: [obs update] Project openSUSE:Factory updated cool, but what changed ?? Thats always my question. And I can't remember all previous lines and also I'm not as smart as "diff" :P . -- openSUSE Feature: https://features.opensuse.org/308295

1 1

[New: openFATE 308310] OBS - External workers / Project namespace dedicated
by fate_noreply＠suse.de 22 Jan '10

22 Jan '10

Feature added by: Dominique Leuenberger (dimstar) Feature #308310, revision 1 Title: OBS - External workers / Project namespace dedicated Buildservice: Unconfirmed Priority Requester: Important Requested by: Dominique Leuenberger (dimstar) Description: OBS is a great platform but often the queues are long and it's difficult to schedule any timely 'release' of a package. The main issue is the available build power. Suggest to allow for 'external' workers to connect (authenticated) to the BS and act as workers. Preferrably an authenticated worker should be allowed to pick up packages where the authenticated user has maintainer rights (this eliminates pretty much the 'danger' of injection of malicious binary results: the owner of the worker has full access to the repository anyhow). Additionally it would be interesting if my 'worker farm' could be dedicated to one specific <project / target / arch> in order to plan the resources there (instead of it picking up any random package I'm maintainer, i'd prefer it favor a specific project I'm planning on having a release). -- openSUSE Feature: https://features.opensuse.org/308310

1 3