November 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306996] "out-of-date" package flag
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Artyom Aleksuk (h31) Feature #306996, revision 1 Title: "out-of-date" package flag Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Artyom Aleksuk (h31) Description: There is a very good feature in Archlinux's package list. Anybody (not only registered users) can mark packages as out-of-date. E-mail notification will be sent to a package builder and the package will be marked as out-of-dated on the site until the package would be refreshed. You can see this function, for example, here (http://www.archlinux.org/packages/extra/x86_64/flashplugin/) and here (http://www.archlinux.org/packages/flag/29883/) . It will be very good to make marking at a package search ( here (http://software.opensuse.org/search) ). For example, this feature may be situated below "Go to OBS Project". It should be useful both for Factory and home projects. Sorry for my language. -- openSUSE Feature: https://features.opensuse.org/306996

1 3

[openFATE 306948] Estimation on waiting time on a package on obs
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Glenn Doig (doiggl) Feature #306948, revision 1 Title: Estimation on waiting time on a package on obs Buildservice: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Hello, When your project is blocked in the queue because it is waiting for something to build e.g(binutils) can a time estimate be given as to how long to wait before it may start processing - put that estimation on the 'Package AAA (Project BBB home:CCC)' page when you view the page. Example: (Packages waiting queue * Average Job time) + (Your package Nth position in the Packages blocked queue * Average Job time ) = value Put that value in the package page. Some details used from https://build.opensuse.org/monitor It would be nice to know when your package may start to process. Cheers Glenn Responses so far sourced from http://lists.opensuse.org/opensuse-buildservice/2009-07/msg00235.html > One could implement something, but it will not be very reliable, because the state and order can change with any further submission. > Adrian and > I suggest to file a feature request using features.opensuse.org. But first:What to others think? Do you consider such an estimate ok? Or should we not publish anything since it might change too often? > Andreas -- openSUSE Feature: https://features.opensuse.org/306948

1 6

[openFATE 306472] Another view of build service repositories
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Jigish Gohil (cyberorg) Feature #306472, revision 1, last change by Title: Another view of build service repositories Buildservice: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: Apart from the current structure another view of oBS repositories that can greatly improve navigation of oBS repositores could be like this: download.opensuse.org/distro1/project1 /project2 /project3 /distro2/project1 /project2 /project3 /Medias/project1/iso /other /project2/iso /other /project3/iso /other This can probably be done by keeping current structure and creating symlinks. -- openSUSE Feature: https://features.opensuse.org/306472

1 3

[openFATE 306469] "Publish Current State" Button
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Stephan Binner (Beineri) Feature #306469, revision 1, last change by Title: "Publish Current State" Button Buildservice: Unconfirmed Priority Requester: Important Requested by: Stephan Binner (beineri) Description: Building packages can take quite some time (and publishing too). While upgrading a whole chain of interdepending packages some can fail to build and leave the repository in an inconsistent and non-installable state => not good to leave the repository in "Publish" state (over night/week-end). Switching from "Not Publish" to "Publish" state AFAIK doesn't trigger immediate publishing but only when some package build finished. It would be very nice to have a "Publish Current State" button which allows one to publish the current package state without having to manually switch publishing state, triggering a fake/unnecessary package rebuild and having to wait/remember to switch back to "Not Publish" state in time. -- openSUSE Feature: https://features.opensuse.org/306469

1 1

[openFATE 305874] Enable peer to peer downloading of patches/software
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Johan Kotze (gogga) Feature #305874, revision 1, last change by Title: Enable peer to peer downloading of patches/software Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Johan Kotze (gogga) Description: It would be great if we could somehow include a peer to peer functionality for the download of patches/packages. This would greatly reduce the number of mirrors required and would increase the performance for many users in countries with limited international bandwidt. I was thinking that we host a torrent tracker on opensuse.org and build a torrent client into zypper/libzypp and allow the user to allocate a portion of disk space for downloaded packages. Most modern systems have ample disk space and should be able to spare around 4GB for downloaded packages. This is also in line with the spirit of community where we help each other out. If it works well, it could also be used to distribute patched internally inside an organization when they deploy SLE. -- openSUSE Feature: https://features.opensuse.org/305874

1 6

[openFATE 307765] Debuginfo file system
by fate_noreply＠suse.de 05 Jul '13

05 Jul '13

Feature added by: Ruchir Brahmbhatt (Ruchir) Feature #307765, revision 1 Title: Debuginfo file system openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ruchir Brahmbhatt (ruchir) Description: It would be nice to have internet mountable debuginfo file system just like fedora. This will allow users to get traces from gdb without installing lots of debuginfo packages. This way we can have access to all debuginfo packages without installing them. This will encourage more users to report bugs. Some users may not be willing to install additional debuginfo packages due to lack of enough disk space or willingness to report bugs. -- openSUSE Feature: https://features.opensuse.org/307765

1 2

[New: openFATE 308320] YMP YaST Workflow
by fate_noreply＠suse.de 17 May '13

17 May '13

Feature added by: Hendrik Vogelsang (hennevogel) Feature #308320, revision 1 Title: YMP YaST Workflow openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: If you click on a YMP link firefox opens a window[1] asking you what you want to do with that link, suggesting to let the meta package handler handle it. You click okay from which another window[2] opens, the download manager of firefox. After it is finished an new window[3] pops up asking you the initial questions about the YMP handling. Which repos to subscribe to and which package to install. If you okay twice yet another window[4] opens asking me for the root password to start the package manager. Which is another window[5]. If there is a new repo in the YMP that you did not have before it will open a window[6] asking you to import the signing key. Somehow i doubt that this many windows are neccessarry. For a workflow that is desinged for the stupid user this should be improved imho. -- openSUSE Feature: https://features.opensuse.org/308320

1 2

[New: openFATE 308285] Easy way to switch from 11.2 to Factory Repositories - and to 11.3
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #308285, revision 1 Title: Easy way to switch from 11.2 to Factory Repositories - and to 11.3 openSUSE-11.3: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Description: Right now, I have to manually change the repositories when upgrading from 11.2 to Factory - or from Factory to 11.3. I'd like to have an easy way, e.g. 1-Click-Install or a script that does this automatically for my system. This might not change external repositories, e.g. on the Build Service, but it should change the official distribution repositories. -- openSUSE Feature: https://features.opensuse.org/308285

1 5

[openFATE 308181] Yast Install - textbox to test the keyboard
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Kayo Hamid (kayohf) Feature #308181, revision 1 Title: Yast Install - textbox to test the keyboard openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Kayo Hamid (kayohf) Description: Hi, i see that the Yast Install (11.2 M8) do not have a textbox to test the keymap that i have selected. My idea is to put one textbox to test the keyboard after the choose of keymap. -- openSUSE Feature: https://features.opensuse.org/308181

1 3

[openFATE 307628] give client a way to indicate preferred country for mirror choice
by fate_noreply＠suse.de 05 Mar '13

05 Mar '13

Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #307628, revision 1 Title: give client a way to indicate preferred country for mirror choice openSUSE-11.3: New Priority Requester: Desirable Requested by: Peter Poeml (poeml) Description: Hi, the mirror selection is based on precise, but relatively narrow network topology knowledge, as well as the "mostly" precise and sometimes lacking GeoIP information. For the cases where the IP cannot resolved, or cannot be resolved correctly, to a country, we can give the client a way to specify the country it is located in, to influence the mirror choice into the right direction. There are several groups of users that are affected by this: * users connected through satellite links can often be resolved only as country=A2, which is not a real country, it only indicates that this is a satellite link. * AOL users outside the US are not resolved (pseudo country A1). * IPs unknown to the GeoIP database, and not in one of the AS's which contain a mirror either * clients connected through a VPN that uses address space that's allocated in another country (e.g. clients in the Netherlands, whose employer is based in the US and runs a VPN that uses IP addresses that geolocate to the US) * Ipv6 clients (no GeoIP for that yet) Thus, it is desirable to give clients a way to indicate their location. CentOS uses something like that to influence or override mirror choice: http://www.centos.org/modules/news/article.php?storyid=118 In 11.2 libzypp, this could be implemented relatively easily (I believe) by adding a configuration directive "download-preferred-country" to /etc/zypp/zypp.conf, taking an ISO3166-1 two-letter code, and adding an HTTP request header (X-Preferred-Country) _if_ something is configured there. On another hand, since we intend to mainly use metalinks in the future, we could just use another aria2c option that makes this configurable: --metalink-location=LOCATION[,...] The location of the preferred server. A comma-delimited list of locations is acceptable, for example, JP,US. On the server side, the latter doesn't require anything to do. The former would be easy to implement. Something similar already exists, through ?country=xy request parameter, so one only needs to pick up the new header, which is a few lines of code. It could be used to deal with libcurl downloads, but in the light of metalink usage we should be able to neglect them. Relations: - give client a way to indicate preferred country for mirror choice (novell/bugzilla/id: 482894) https://bugzilla.novell.com/show_bug.cgi?id=482894 Discussion: #1: Peter Poeml (poeml) (2009-03-06 10:20:33) Duncan, can I assign this to you? I look into the git repository, tried to update but I stupidly failed with a file conflict and resolving it, else I would have given it a go... -- openSUSE Feature: https://features.opensuse.org/307628

1 1