March 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310301] Add 'one click add' to repositories index-page
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Bart Otten (BartOtten) Feature #310301, revision 1 Title: Add 'one click add' to repositories index-page Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Bart Otten (bartotten) Partner organization: openSUSE.org Description: A link in the OBS indexpages to add an repository to zypper/yast or Recognise the .repo filetype in Yast so the meta-file handler can add the repo Use Case: - browse the OBS-repos - view folder http://download.opensuse.org/repositories/home:/georg298/openSUSE_11.3/ - click at home:georg298.repo (http://download.opensuse.org/repositories/home:/georg298/openSUSE_11.3/home…) - One click installer/ One click repo-add starts and shows some info - Click finish (with option to start packagemanagement) Business case (Partner benefit): openSUSE.org: At this moment users have to set up all information manual which could be so much easier. We have the One click install, but what if I just want to add the whole repo and there is no One click install-button? -- openSUSE Feature: https://features.opensuse.org/310301

1 1

[New: openFATE 310030] detect user specs for software downloads
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Kristan Wifler (k_wifler) Feature #310030, revision 1 Title: detect user specs for software downloads Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Kristan Wifler (k_wifler) Description: You can read info from the web browser in order to determine the most likely file the user wants for his/her computer system, Operating system, etc. This is for software.opensuse.org download of openSUSE mostly. I have seen several sites that do this, it makes it more convenient for default settings. -- openSUSE Feature: https://features.opensuse.org/310030

1 1

[New: openFATE 309738] include dependency kind in _builddepinfo
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Ludwig Nussel (lnussel) Feature #309738, revision 1 Title: include dependency kind in _builddepinfo Buildservice: Unconfirmed Priority Requester: Important Requested by: Ludwig Nussel (lnussel) Description: _builddepinfo of a repo lists the recursively expanded dependencies of a package. For analyzing dependency graphs it would be helpful to include information about whether a dependency is explicitly listed in the .spec file or got added due to dependency resolution. -- openSUSE Feature: https://features.opensuse.org/309738

1 1

[New: openFATE 308618] smart online package search
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Elmar Stellnberger (estellnb) Feature #308618, revision 1 Title: smart online package search Buildservice: Unconfirmed Priority Requester: Important Requested by: Elmar Stellnberger (estellnb) Description: A smart online package search as it can be found at debtags.alioth.debian.org (http://debtags.alioth.debian.org/ssearch.html) would be highly desirable for openSUSE, too. If I do f.i. enter 'web browser' at the YaST package module it will not find konqueror, arora, epiphany, lynx, pinfo, p3m and many others though these packages are available; i.e. at first the package tagging needs to be improved. Then we need to improve the software search at packages.opensuse-community.org (http://packages.opensuse-community.org) . It currently seems to search for package names only though optionally searching for keywords, summary, description, provides, filenames and requires fields across all known repos would be highly desirable. I do also wonder why my own buildservice packages can not be found there. A factory search in the same place would be handy too although we do not have third party repositories for factory (mere buildservice search). For openSUSE 11.3 I would wish the community search to be available from RC1 on; for os 11.2 I had to wait even weeks after the final release. A comprehensive package search utility is one of the features a good distro should comprise. -- openSUSE Feature: https://features.opensuse.org/308618

1 3

[New: openFATE 309717] make osc to remember http authentication header
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: JF Ding (jfding) Feature #309717, revision 1 Title: make osc to remember http authentication header Buildservice: Unconfirmed Priority Requester: Desirable Requested by: JF Ding (jfding) Description: In current implementation, osc use 'urllib2' to access api server for http transactions. The problem is, osc need to send out a pair of request for each access: 1st request without authentication header, and the response will be a 401 with Basic authentication challenge. 2nd request with dynamically generated authorization header (Authorization: Basic <base64 encoded string>\r\n) But we can make osc to remember the header at the first authentication challenge of each osc running. Then the http request number and network loading can be lowered a lot. Python's urllib2 module is flexible enough to add this feature. I have implemented it in my personal gitorious branch: http://gitorious.org/~jfding/opensuse/jfdings-osc/commit/62d705c29999856ec6… (http://gitorious.org/~jfding/opensuse/jfdings-osc/commit/62d705c29999856ec6…) Any advice? Thanks. -- openSUSE Feature: https://features.opensuse.org/309717

1 2

[New: openFATE 309611] Add a "ignore" file
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Johannes Obermayr (jobermayr) Feature #309611, revision 1 Title: Add a "ignore" file Buildservice: Unconfirmed Priority Requester: Important Requested by: Johannes Obermayr (jobermayr) Partner organization: openSUSE.org Description: Each time the build hosts become initialized new for providing a fresh build system. After that the defined "BuildRequires:" become copied together with all dependencies from another host and installed on the build system. Finally the build system is initialized and the actual build process can start. There are often packages installed which are not really needed for the build process but for a working system. They become installed because of a "Requires:" tag in the actual depended package (especially -branding-{upstream,opensuse}, .noarch [data] or very far depend packages). With a "ignore" file you can say to OBS that e.g. package xy-data is not needed and should not / must not be installed. It is an addition to the "Ignore:"s defined in buildconfig. Business case (Partner benefit): openSUSE.org: 1. Reduce data transfer to the build hosts 2. Improve speed of initialization the build hosts 3. It could be a workaround for bug #510360 -- openSUSE Feature: https://features.opensuse.org/309611

1 1

[New: openFATE 308617] provide FreeBSD, Solaris and OSX build targets
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Elmar Stellnberger (estellnb) Feature #308617, revision 1 Title: provide FreeBSD, Solaris and OSX build targets Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Elmar Stellnberger (estellnb) Description: The provision of build targets for the most important Unix derivates like FreeBSD, Solaris and OSX would greatly enhance the capabilities of the build service. While rebuilding packages for different distributions and Linux versions is often a rather cosmetic issue this could really leverage the future use of the build service and constitute a major advancement. The build service infrastructure could then also be sold to proffesional closed source application developers. This should not be undoable since there are also plans for a Windows build target. However the support of the program environment will be much better met on a Unix based system. -- openSUSE Feature: https://features.opensuse.org/308617

1 8

[New: openFATE 308569] exclude certain subpackages from publishing
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Wolfgang Rosenauer (wrosenauer) Feature #308569, revision 1 Title: exclude certain subpackages from publishing Buildservice: Unconfirmed Priority Requester: Important Requested by: Wolfgang Rosenauer (wrosenauer) Description: I would like to exclude certain subpackages from being published to repositories. In this example it's a package having data which is not needed but for special purposes and it's quite big (around 100MB RPM size) so it's probably a good idea not to distribute and publish it. -- openSUSE Feature: https://features.opensuse.org/308569

1 3

[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