August 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306600] A small change that would make openSUSE a bit easier to use
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Glöm Det (Searching_for_Answers) Feature #306600, revision 1 Title: A small change that would make openSUSE a bit easier to use openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Glöm Det (searching_for_answers) Description: I'm not the most exprienced Unix/Linux user and as a nuub I see how you could make it easier for other nuubs coming from Windows. When I look at the openSUSE directory(is it shared with Linux and Unix?) I see alot complicated abbriviations like sbin, var, opt, mnt, proc and stuff. Now I could google what they stand for and what types of files are in there but it would be easier if I didn't have too. There for I suggest that you rename... DON'T GIVE UP... those files to their full extension names. I know this wouldn't work out well since it might be important for developers and the speed of terminal writing that the remain as they are. Instead here is my solution. Keep the directory as it is but add this feature too openSUSE. When you hold/right click your mouse over the folder the full name appears. If you for exampel hold it over the lib folder the full name of library appears and a short description telling what kinds of files that are stored here. When you comes to making your own folders you are are able too write description and the full name if you want. That can't be too complicated to make right. It is a small change that will make it alot better. But maybe I'm not asking the right persons here. Maybe Dolphin the file manager's crew is the one to tell about this suggestions. In that case or if you have any questions. Send a private message to Searching_for_answers . P.S. I discoverd this Use and Test cases now. I don't know what they're for so I leave them blank -- openSUSE Feature: https://features.opensuse.org/306600

1 7

[openFate 305724] Allow to take over old users by home directory
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Jiří Suchomel (jsuchome) Feature #305724, revision 1, last change by Title: Allow to take over old users by home directory openSUSE-11.2: New Priority Requester: Neutral Requested by: Jiří Suchomel (jsuchome) Partner organization: openSUSE.org Description: (from bug reporter:) I have a seperate /home partition and whenever I reinstall/upgrade I just set up the same user as before and he gets assigned the same uid (1000) so nothing gets broken. But I guess with more users and corresponding home directories this aproach begs for wrong permissions, so I suggest the following: In case /home isn't empty it could take all directories available and list them as users to specify their data (Name, login, passwort etc as usual) and then assign corresponding uid. References: https://bugzilla.novell.com/show_bug.cgi?id=464238 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305724

1 7

[openFATE 305945] get rid of "symsets" in kernel package dependencies
by fate_noreply＠suse.de 01 Mar '10

01 Mar '10

Feature added by: Michal Marek (michal-m) Feature #305945, revision 1, last change by Title: get rid of "symsets" in kernel package dependencies openSUSE-11.2: New Priority Requester: Important Requested by: Michal Marek (michal-m) Description: Currently, the kernel rpm packages group the exported kernel and module symbols in find-provides and provide these "symsets". It has been done this way to reduce the amount of data the solver has to process. It has a number of problems though: * Moving modules around or adding symbols changes the symset checksums, so the rpm build needs symsets of the previous kernel(s) to provide both old and new checksums * changing or removing one unused or unimportant symbol means that each kmp that uses any other symbol from the same symset needs to be rebuilt Now that we have a much better solver, it's time to get rid of this and provide just the individual symbols. I created a test project in the build service: home:michal-m:kill-symsets. which rebuilds all 11.1 kmps against a normal kernel and against a kernel with symsets turned off (this kernel is built in home:michal-m:kill-symsets:changes). The size difference is rather low, total size of all the rpms on i586 and x86_64 increased by about 1.3M, installed size decreased by 2.6M (because of the removed /boot/symsets* files). Size of yum metadata increased by 1.4M. What needs to be done is to make sure that the solver can really handle this fine (-> Michael). I'm waiting for the test repos to appear on download.o.o. -- openSUSE Feature: https://features.opensuse.org/305945

1 17

[openFATE 306781] osc sr should warn if changes are not commited
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Thorsten Kukuk (kukuk) Feature #306781, revision 1 Title: osc sr should warn if changes are not commited Buildservice: New Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Description: osc submitrequest should warn and wait for confirmation, if the local changes were not submitted to buildserver yet. This would help to avoid the problem, that old packages without changes got submitted to the project. -- openSUSE Feature: https://features.opensuse.org/306781

1 4

[openFATE 307518] list medias created on oBS on http://software.opensuse.org/
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Jigish Gohil (cyberorg) Feature #307518, revision 1 Title: list medias created on oBS on http://software.opensuse.org/ Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Jigish Gohil (cyberorg) Description: Please list some of the important projects' images from here: http://en.opensuse.org/Live on http://software.opensuse.org/, at least KDE, GNOME and Education images. -- openSUSE Feature: https://features.opensuse.org/307518

1 3

[openFATE 307176] Buildservice and bugzilla integration
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Michal Vyskocil (mvyskocil) Feature #307176, revision 1 Title: Buildservice and bugzilla integration Buildservice: Unconfirmed Priority Requester: Important Requested by: Michal Vyskocil (mvyskocil) Description: The current worflow needs to synchronize a bugzilla and a BuildService manually, which is fragile and tends to mistakes. Buildservice could be integrated with a bugzilla. The submitrequests (and probably any other requests) should contains the bug ids and change the status of a bug(s), when the request state is changed. The osc submitreq --bug bnc:12345 -m "some fix" will create a submit request and mark a bnc#12345 as RESOLVED/FIXED. Later, when the submitrequest was accepted, BS mark the bug as CLOSED/FIXED. In other cases, the bug will be REOPENED. The alternative to --bug command line argument should be an automatic read of changelog for bnc#, but this might be fragile and unwanted in some cases. -- openSUSE Feature: https://features.opensuse.org/307176

1 2

[openFATE 306685] devel projects used for a project
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Hendrik Vogelsang (hennevogel) Feature #306685, revision 1 Title: devel projects used for a project Buildservice: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: To know about the devel projects used for a project one has currently to query all package _meta files. For large projects this is a lot of data. Can we do this serverside somehow? Like write it into the _meta file of the project or something. -- openSUSE Feature: https://features.opensuse.org/306685

1 6

[openFATE 306343] 'Pkgstars' to reward contributors
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Will Stephenson (wstephenson) Feature #306343, revision 1, last change by Title: 'Pkgstars' to reward contributors Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: In KDE we use 'dashstars' to reward those who fix build breakages. When a broken build module is fixed, the person responsible for the commit that fixed the build is awarded a 'dashstar', and an IRC bot advertises this in the developer channel with a message such as "JohnDoe fixed kdelibs (64 dashstars)" so the community sees their contribution. In addition, contributors can query their dashstar totals. A similar system for eg package build fixes or package version updates that is visible on the user's opensuse homepage and advertised in community channels (or a weekly summary mail to -project) would be a fun way to reward contributions. -- openSUSE Feature: https://features.opensuse.org/306343

1 2

[openFATE 305930] Don't increase version number if not strictly needed
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Joop Boonen (worldcitizen) Feature #305930, revision 1, last change by Title: Don't increase version number if not strictly needed Buildservice: Unconfirmed Priority Requester: Important Requested by: Joop Boonen (worldcitizen) Description: As I use KDE42 and other newer packages I often do a factory update. I see that the footprint is very big. Because a package gets always rebuild when for instance a dependent library get rebuild. Even if the package is 100% the same it'll gets the same version number. If possible I would like to have binary identical packages yo keep the same version number this reduces bandwidth usage for users/mirrors and it can give people a false feeling that Linux is buggy "as so many packages need to be updated". -- openSUSE Feature: https://features.opensuse.org/305930

1 4

[openFate 305689] Allow creation of meta-repositories
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Magnus Boman (MBoman) Feature #305689, revision 1, last change by Title: Allow creation of meta-repositories Buildservice: Unconfirmed Priority Requester: Important Requested by: Magnus Boman (mboman) Partner organization: openSUSE.org Description: It'd be extremely useful if it was possible to create meta-repositories in OBS. The way it would work, is that anyone could create a project in OBS, and from there, include several other projects to combine them in one meta-repository. It is kind of possible today if one use _links or _aggregate, but that either forces the entire repo to be built in the users own project, or requires a lot of disk space. A meta-repository would basically only create symlinks to the other projects (would not require any extra disk space, nor OBS resources for re-compiling everything in a "new" project) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305689

1 6