March 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305267] Installation using Orca (screen reader) to Improve Accessibility
by fate_noreply＠suse.de 10 Aug '10

10 Aug '10

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305267, revision 1, last change by Title: Installation using Orca (screen reader) to Improve Accessibility openSUSE-11.2: New Priority Requester: Desirable Requested by: Darragh Ó Héiligh <d(a)digitaldarragh.com> Partner organization: openSUSE.org Description: Original title: Accessibility for installation could be automated with better results. Users can currently press F9 at the boot screen to hear the boot options spoken. THis is a fantastic new feature and is one that OpenSuSE is the first to add. For this you should be very proud. However, I would ask that you further build upon this success by recognising that accessibility at the boot menu has been enabled and automatically start the Orca screen reader with also setting gnome accessibility to enabled. One further consideration should be taken into account. To enable Orca to access the installation screen, Orca must be run as root. However, if Orca is run as root, the rest of the desktop is not accessible due to permissioning issues. Therefore, the installation should be run automatically if the f9 key si pressed. Note, a similar feature excluding the accessible boot menu has also been added to Ubuntu 8.04. Note that they also have a key press (F5) to automatically enable assistive technologies for installation on their live CD. References: See bnc #417874 (https://bugzilla.novell.com/show_bug.cgi?id=417874) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305267

1 5

[openFate 305589] Checkbox "include user home projects in search"
by fate_noreply＠suse.de 30 Jul '10

30 Jul '10

Feature added by: Pavol Rusnak <prusnak(a)novell.com> Feature #305589, revision 1, last change by Title: Checkbox "include user home projects in search" Buildservice: New Priority Requester: Desirable Requested by: Pavol Rusnak <prusnak(a)novell.com> Partner organization: openSUSE.org Description: Here's one idea to start with: on the search page, have a checkbox labeled "Include user home projects in search" which defaults to OFF. Then at least you have one level of separation (between "official" and home projects) that is clear to both developers and users. And developers will be motivated to move their generally useful packages into an "official" project by the fact that the default checkbox is OFF. http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00088.html -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305589

1 4

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

[openFate 305693] Versioning for project data
by fate_noreply＠suse.de 20 Feb '10

20 Feb '10

Feature added by: Martin Mohring (MartinMohring) Feature #305693, revision 1, last change by Title: Versioning for project data Buildservice: Unconfirmed Priority Requester: Mandatory Requested by: Martin Mohring (martinmohring) Partner organization: openSUSE.org Description: Currently, we have versioning of the source files with OBS.Since at least projconf correlates to the sources, it should be versioned to make versioning more of a feature to restore old versions reproducable. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305693

1 3