June 2010 - 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

[New: openFATE 309148] boot-process: starting network / dbus with ldap authentification
by fate_noreply＠suse.de 30 Jul '13

30 Jul '13

Feature added by: Alexander Fleischer (afleischer) Feature #309148, revision 1 Title: boot-process: starting network / dbus with ldap authentification openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Alexander Fleischer (afleischer) Description: I asked to file this bug report as feature request: https://bugzilla.novell.com/show_bug.cgi?id=569953 (https://bugzilla.novell.com/show_bug.cgi?id=569953) After configuring LDAP authentification via yast the system needs about 20 minutes to start the dbus-daemon on boot. I got a lot of ldap messages in /var/log/messages like these: Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: failed to bind to LDAP server ldaps://10.0.0.10: Can't contact LDAP server Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Of course, because network is started after dbus, dbus can't connect to the ldap server, and waits several times until the timeout is reached. Network has dbus as "required-start", so i can't change the startup order and add $network to required-start in the dbus script. My temporary solution is to replace the /etc/nsswitch.conf file with a one without ldap access in /etc/init.d/boot.local and restoring the original one after the network is up. But this is not a clean solution, maybe an extra startup script can solve the problem. -- openSUSE Feature: https://features.opensuse.org/309148

1 2

[New: openFATE 308824] Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options)
by fate_noreply＠suse.de 09 Jul '13

09 Jul '13

Feature added by: Katarina Machalkova (kmachalkova) Feature #308824, revision 1 Title: Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options) openSUSE-11.3: New Priority Requester: Important Requested by: Katarina Machalkova (kmachalkova) Description: For years, SUSE-based products have been appending '127.0.0.2 host.domain host' to /etc/hosts as a convenience for applications which want to resolve the hostname and which thus become irresponsive without active network [1] Localhost IP associated with FQDN however causes various network services (samba, SLP, LDAP, ntp, ... ) to behave oddly [2]. An option in product-wide control files has been introduced so as not to append 127.0.0.2 on server-oriented products (SLES) - FaTE#303875, while keeping user the possibility to override the default in GUI and AutoYaST profile. Nevertheless, even reasonably set default doesn't prevent misconfigurations and user complaints [3] The suggestion is therefore to drop 127.0.0.2 modification of /etc/hosts altogether and drop GUI/control options associated with configuration thereof. These include: * GUI option in YaST installer * XML profile elements in AutoYaST * Variable in product-wide control file (control.xml) * Possibly also sysconfig variable Appending 127.0.0.2 line has always been sort of workaround for flawed (mostly) desktop applications and DNS servers, so rather than providing workaround with plethora of side effects, it'd more reasonable to have affected apps fixed. Bugs have been filed against some of them and fixed already. References: [1] Apps become slow when offline bugs https://bugzilla.novell.com/show_bug.cgi?id=304632 https://bugzilla.novell.com/show_bug.cgi?id=383336 [2] Network services going insane with localhost IP associated with FQDN https://bugzilla.novell.com/show_bug.cgi?id=207392 https://bugzilla.novell.com/show_bug.cgi?id=355608 https://bugzilla.novell.com/show_bug.cgi?id=570108 [3] Even reasonably set default doesn't help https://bugzilla.novell.com/show_bug.cgi?id=510228 -- openSUSE Feature: https://features.opensuse.org/308824

1 21

[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 308496] Include OpenShot Video Editor
by fate_noreply＠suse.de 23 May '13

23 May '13

Feature added by: Karl Fischer (karlfischer) Feature #308496, revision 1 Title: Include OpenShot Video Editor openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Karl Fischer (karlfischer) Partner organization: openSUSE.org Description: OpenShot is a Open source, Non Linear video editor, I believe that openSUSE 11.3 will benefit greatly to a such a Video Editor. Business case (Partner benefit): openSUSE.org: Making openSUSE a better MultiMedia desktop, having Gimp, Inkscape and Banshee this would be a very complementary. -- openSUSE Feature: https://features.opensuse.org/308496

1 12

[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