July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305905] Package and Project Marking
by fate_noreply＠suse.de 02 Jun '10

02 Jun '10

Feature added by: Will Stephenson (wstephenson) Feature #305905, revision 1, last change by Title: Package and Project Marking Buildservice: Unconfirmed Priority Requester: Important Requested by: Will Stephenson (wstephenson) Description: * Add the ability to have a 'status update' on packages AND projects * * status updates are not package changelogs; logs refer to changes to the contents of the package, status updates relate to ongoing work on the packages * * 1:N relationship, status updates are timestamped. Like facebook or $microblogging service. * show current status on checkout or list * Add a command to read all the status updates on a package. Examples: 1) Jack is updating Commodore:Amiga:Workbench:Factory to 23.2 and disables publish on the whole project before the actual release date with the status message '20090224 - disabled publish pending 23.2 release' 2) Jill is triaging breakages in Commodore:Amiga:Workbench:Factory and marks packages without checking them out before assigning work to team members Denise and Paula, with "osc mark -m 'broken by input.device changes' Commodore:Amiga:Workbench:Factory Preferences" 3) Paula is fixing a breakage in Commodore:Amiga:Workbench:Factory Preferences and locks (see #305899) the package with status update using "osc co -l -m '20090225 - fixing build failure due to input.device changes' Commodore:Amiga:Workbench:Factory Preferences" -- openSUSE Feature: https://features.opensuse.org/305905

1 3

[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 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

[openFATE 306852] YaST2 screen title needs a machine-name in it
by fate_noreply＠suse.de 15 Mar '10

15 Mar '10

Feature added by: Greg Riedesel (Gracal) Feature #306852, revision 1 Title: YaST2 screen title needs a machine-name in it openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Greg Riedesel (gracal) Description: The nomenclature, "[YaST control panel] @ [machine name]' is very useful for figuring out which window belongs to which server. Especially if the managing workstation is also openSUSE. Formerly Bug 385625 Use Case: When managing openSUSE servers over X-forwarding via SSH, it is possible to have multiple YaST screens up at the same time, each belonging to a different remote server. Having a way to differentiate between YaST instances in the title-bar will reduce confusion, and help avoid config mistakes. -- openSUSE Feature: https://features.opensuse.org/306852

1 5

[openFate 305104] Provide possibility to configure WEP/WPA/WPA2/... at installation
by fate_noreply＠suse.de 09 Mar '10

09 Mar '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305104, revision 1, last change by Title: Provide possibility to configure WEP/WPA/WPA2/... at installation openSUSE-11.1: New Priority Requester: Desirable Requested by: Jim Creech <jacreech(a)suddenlink.net> Partner organization: openSUSE.org Description: It is possible to configure a network in the first stage installation but it is only possible to select DHCP or Static + configure proxy. It is impossible to configure a secure wireless connection. See also: Bug 293609 (https://bugzilla.novell.com/show_bug.cgi?id=293609) - No provision for entering WEP at installation -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305104

1 9

[openFATE 306379] Use rsync when refreshing repositories
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Piotrek Juzwiak (BenderBendingRodriguez) Feature #306379, revision 1, last change by Title: Use rsync when refreshing repositories openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Piotrek Juzwiak (benderbendingrodriguez) Description: It would be a great idea to use rsync when refreshing repositories, one of the bad things is the refresh speed. It gets worse when people have many repositories. I'm not sure but it already compares if something has changed in the repo but to speed things up it would be great to use rsync. -- openSUSE Feature: https://features.opensuse.org/306379

1 14

[openFATE 306921] s390(x) dump analysis on x86/x86_64 using crosscrash
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Petr Tesařík (ptesarik) Feature #306921, revision 1 Title: s390(x) dump analysis on x86/x86_64 using crosscrash Hackweek IV: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Petr Tesařík (ptesarik) Description: crosscrash is an unfinished tool, though interesting. One of the major drawbacks is its inability to open dumps from big-endian architectures on little-endian hosts, most importantly s390x dumps on x86_64. -- openSUSE Feature: https://features.opensuse.org/306921

1 5

[openFATE 306760] upgrade dmraid to RC16
by fate_noreply＠suse.de 02 Mar '10

02 Mar '10

Feature added by: Marcin Labun (mlabun) Feature #306760, revision 1 Title: upgrade dmraid to RC16 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Marcin Labun (mlabun) Description: RC16 version of dmraid (not yet published) will include following features/bug fixes (full description of bugs can be RH BZ): 479419 [SEC] OROM/DMRAID metadata inconsistency 479425 Incorrect status displayed when disk is missing [status] 483282 dmraid -r will falsely toggle the OROM back to 'normal' status after a failed rebuild 481735 [SEC] dmraid does not allow to activate RAID arrays in degraded state 481749 [SEC] DMRAID does not receive and process kernel events for active devices 505005 dmraid always creates error mapping for the last device in an isw RAID5 set 505007 dmraid regression on raid45 target kernel status interface 506893 Segmentation fault for RAID5 when starting manual rebuild 473282 [SEC] Include support for compatibility with IMSM 9.0 metadata in dmraid 505011 dmraid doesn't update isw metadata to OK during rebuild -- openSUSE Feature: https://features.opensuse.org/306760

1 1

[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