June 2012 - openSUSE Features - openSUSE Mailing Lists

[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

[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

[New: openFATE 313152] Distribution cleanup (smaller disk footprint)
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #313152, revision 1 Title: Distribution cleanup (smaller disk footprint) openSUSE Distribution: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: We want to have an as small as default base system (default text install) as possible. For this, I suggest to install a base system and investigate then what can be done to decrease the footprint. One idea is to check documentation (in /usr/share/doc/packages) and move them to doc or devel package (with the exception of license files). Also, we can check whether all dependencies (manual requires) are still correct - or in other words: Does every package that's there needs to be in the base install? Business case (Partner benefit): openSUSE.org: A small base system is important especially for appliances and virtual environments. -- openSUSE Feature: https://features.opensuse.org/313152

1 3

[New: openFATE 310310] Installer partition layout to allow "Whole Disk Usage"
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Darryl Miles (dlmiles) Feature #310310, revision 1 Title: Installer partition layout to allow "Whole Disk Usage" openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Darryl Miles (dlmiles) Description: Currently the installer doesn't provide any option for Whole Disk Usage for a single purpose (such as rootfs or swap or /home etc...). Whole disk usage means there is no partition table and that file-system or swap is formatted directly. This has use-cases for virtulization where it is easier for the hypervisor to provision two block devices to the guest, one for rootfs and one for swap. These may come from LVM, SAN, etc... it is easier to manage because resizing either is a straight forward event due to the single purpose of each block device. One possible option to shoe-horn it into the UI would be under the Expert.../Advanced... buttons when either a partition or a disk device is selected. More ideas suggested in the bugzilla link further down this comment. Other possible considerations go with the bootloader options for installing GRUB. It would need to be adjusted to disallow/auto-disable MBR when no partition table is present. But the option still remains to install in the rootfs. Also submitted as ENH in Buzilla please read => https://bugzilla.novell.com/show_bug.cgi?id=628056 "installer doesn't support whole-disk usage", since this contain other comments not found here. -- openSUSE Feature: https://features.opensuse.org/310310

1 6