November 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 307556] Provide an easy way to find Factory devel package with unsubmitted project.diff
by fate_noreply＠suse.de 10 May '10

10 May '10

Feature added by: Ralf Haferkamp (rhafer) Feature #307556, revision 1 Title: Provide an easy way to find Factory devel package with unsubmitted project.diff Buildservice: Unconfirmed Priority Requester: Important Requested by: Ralf Haferkamp (rhafer) Description: It would be very helpful to have an overiew in the webfrontends that shows which factory-devel packages are "out-of-sync" with factory. I.e. they have uncommited (not submitted to Factory) projects.diffs in their file list. This could e.g. be part of the "My Projects" page. (Or hermes could sent regular notification about uncommited changes.) -- openSUSE Feature: https://features.opensuse.org/307556

1 9

[openFATE 307915] Project source link (forwarder)
by fate_noreply＠suse.de 03 May '10

03 May '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #307915, revision 1 Title: Project source link (forwarder) Buildservice: Candidate Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Description: For preparing maintenance updates we need a way to allow references to the :Update projects, even if a certain package does not exist there yet. This need to work for source check outs and source links. However, not for building (:Update shall not build all packages by default). A proposal to support this would be via a so called "project source link" with additional flags. Something like this for the project xml meta data: <link project="$PROJECT" /> This could be later extended to enable entire shadow builds (aka our former BETA distributions: <link project="$PROJECT"> <build repository="$REPOSITORY" arch="$ARCH"> </link> -- openSUSE Feature: https://features.opensuse.org/307915

1 5

[New: openFATE 308261] Include Bibus, a bibliography tool that interacts with Openoffice via UNO
by fate_noreply＠suse.de 26 Apr '10

26 Apr '10

Feature added by: Sven Burmeister (rabauke) Feature #308261, revision 1 Title: Include Bibus, a bibliography tool that interacts with Openoffice via UNO Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Description: OpenOffice lacks a decent bibliography support which is mandatory for scientific writing. Bibus is a python tool available for all platforms, i.e. Windows users can use the same tool when switching to Linux. It can interact with Openoffice via the UNO api, i.e. it does not only export its data, but inserts it into the OO document. It can even be used with a central database, i.e. for companies that want to share their bibliogrphic data. The projects website is: http://bibus-biblio.sourceforge.net/ -- openSUSE Feature: https://features.opensuse.org/308261

1 4

[openFATE 306502] Disable automount
by fate_noreply＠suse.de 14 Apr '10

14 Apr '10

Feature added by: Jakub Rusinek (liviopl) Feature #306502, revision 1 Title: Disable automount openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jakub Rusinek (liviopl) Description: When repartitioning HDD, automount can hurt. The same when installing system. At least for partitioners and installers "lifetime", automount should be disabled. -- openSUSE Feature: https://features.opensuse.org/306502

1 5

[openFATE 307552] Cups 1.4 RPM's
by fate_noreply＠suse.de 30 Mar '10

30 Mar '10

Feature added by: Dean Hilkewich (deanjo13) Feature #307552, revision 1 Title: Cups 1.4 RPM's Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Dean Hilkewich (deanjo13) Description: It would be nice if the cups packages could be upgraded to 1.4 in 11.2. I realize it's a bit late in the development stage but it just went final on Aug 28th and does carry a large number of improvements. http://www.cups.org/documentation.php/whatsnew.html -- openSUSE Feature: https://features.opensuse.org/307552

1 5

[New: openFATE 308407] Simplify debranding in Kiwi and SUSE Studio
by fate_noreply＠suse.de 29 Mar '10

29 Mar '10

Feature added by: M. Edward (Ed) Borasky (znmeb) Feature #308407, revision 1 Title: Simplify debranding in Kiwi and SUSE Studio openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: M. Edward (Ed) Borasky (znmeb) Description: I build appliances based on openSUSE. I've done some of them in SUSE Studio, and some of them on my workstation using Kiwi, VirtualBox OSE, Xen or VMware Workstation. I am starting to get some that I'd like to distribute. In order to distribute them, I need to be able to re-brand some packages - remove the openSUSE branding and replace it with upstream branding or my own. See http://en.opensuse.org/Making_a_SUSE_based_distribution (http://en.opensuse.org/Making_a_SUSE_based_distribution) for the details. I've tried to do this using SUSE Studio, since it's a lot more convenient, but I have been unable to create a de-branded appliance because of package conflicts in the built-in patterns. See http://n2.nabble.com/Branding-distributing-etc-tp4030350p4030350.html (http://n2.nabble.com/Branding-distributing-etc-tp4030350p4030350.html) The essential difficulty, both in SUSE Studio and in Kiwi is that the base patterns which define package lists contain unremovable branding packages. For these patterns, I need to 1) Find a list of all the packages in the patterns and their dependencies 2) Acquire the source for the branded packages, de-brand them at the source level, and then rebuild binary RPMs. That's a significant amount of labor with no value added to the recipients of the redistributed software. So what I am requesting is that the openSUSE project 1) Make the base patterns ("default", "kde4", "gnome", "xfce", etc.) branding-free, and create a new "branding-openSUSE" pattern to replace the upstream branding with openSUSE branding, and 2) Create de-branded RPMs for the few packages that don't have a "branding-upstream" equivalent. I haven't done the research to identify all of these, but I believe most of them are in the YaST infrastructure. -- openSUSE Feature: https://features.opensuse.org/308407

1 4

[New: openFATE 308344] archive mounter
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Andrew Jorgensen (ajorgensen) Feature #308344, revision 1 Title: archive mounter openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Andrew Jorgensen (ajorgensen) Description: GVFS supports mounting archives like iso, zip, tar.gz, etc. Making a menu entry to mount archives is trivial. Ubuntu has had this for a while now and it's very handy. -- openSUSE Feature: https://features.opensuse.org/308344

1 3

[openFATE 307423] clone_system client should accept a list of modules
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Uwe Gansert (ug) Feature #307423, revision 1 Title: clone_system client should accept a list of modules openSUSE-11.2: New Priority Requester: Mandatory Requested by: Uwe Gansert (ug) Description: the clone_system client that was actually invented only for AutoYaST internal purposes is used quite often by customers too on the command line. Currently the client reads the list of modules to clone from the control.xml file. It would be nice if that list could be passed via command line too. -- openSUSE Feature: https://features.opensuse.org/307423

1 3

[openFATE 307424] invent an "ask"-rule for AutoYaST
by fate_noreply＠suse.de 24 Mar '10

24 Mar '10

Feature added by: Uwe Gansert (ug) Feature #307424, revision 1 Title: invent an "ask"-rule for AutoYaST openSUSE-11.2: New Priority Requester: Mandatory Requested by: Uwe Gansert (ug) Description: two customers had an idea for a new feature for the rule-mechanism for AutoYaST. It would be nice if AutoYaST could ask for the files to merge. So that it looks which XML snippets are available and presents them in some kind of dialog to choose from. -- openSUSE Feature: https://features.opensuse.org/307424

1 3

[openFATE 306192] Make BuildService accessible for anonymous users
by fate_noreply＠suse.de 22 Mar '10

22 Mar '10

Feature added by: Michal Vyskocil (mvyskocil) Feature #306192, revision 1, last change by Title: Make BuildService accessible for anonymous users Buildservice: Unconfirmed Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Description: We hides many useful information about our distribution behind a Novell login, which makes a participation harder. Other distributions are much more opened even for anonymous users, so you can browse source codes, patches, changelogs, build logs, ... even if you are an anonymous users. We should be opened as much as possible if we want to be a community based distribution. Some examples: * Fedora CVS (http://cvs.fedoraproject.org/viewvc//) expose all Fedora packages with full history and for anonymous users * kojibuild info (http://koji.fedoraproject.org/koji/buildinfo?buildID=81815) - you have a full access to building informations from koji system and some of them are not available for OBS users at all. * Debian changelog browsing (http://packages.debian.org/changelogs/pool/main/c/cdbs/cdbs_0.4.52/changelog) Debian offers a changelog browsing (they don't use a centralized VCS) without registration. * lintian reports (http://lintian.debian.org/maintainer/build-common-hackers@lists.alioth.debi…) you can see a lintian issues for every package. * Debian build log (http://buildd.debian.org/pkg.cgi?pkg=libmatthew-java) Debian also offers an access to a build log of package. * Gentoo package information (http://packages.gentoo.org/package/app-office/nostaples?ts=2009-03-11T05:57…) Gentoo offers many information about package Those examples are only for illustrate of other approaches. I don't try to tell we must implement CVS because Fedora has it. And some issues like an alternative of Gentoo package view should be implemented in upcoming Software Portal. We should publish (at least for openSUSE:* projects) sources of packages and a build logs. -- openSUSE Feature: https://features.opensuse.org/306192

1 25