[opensuse-factory] New Tumbleweed snapshot 20151229 released!
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Packages changed: attica-qt5 (5.16.0 -> 5.17.0) baloo5 (5.16.0 -> 5.17.0) bluedevil5 (5.4.3 -> 5.5.1) bluez-qt (5.16.0 -> 5.17.0) branding-openSUSE (13.2 -> 13.3) breeze (5.4.3 -> 5.5.1) breeze4-style (5.4.3 -> 5.5.1) breeze5-icons (5.16.0 -> 5.17.0) desktop-data-openSUSE (13.2 -> 13.3) extra-cmake-modules (5.16.0 -> 5.17.0) fcitx-libpinyin (0.3.2 -> 0.3.3) frameworkintegration (5.16.0 -> 5.17.0) gom (0.3.1 -> 0.3.2) ibus-libpinyin (1.7.2git20150720 -> 1.7.4) ibus-libzhuyin (1.7.4 -> 1.7.6) kactivities5 (5.16.0 -> 5.17.0) karchive (5.16.0 -> 5.17.0) kauth (5.16.0 -> 5.17.0) kbookmarks (5.16.0 -> 5.17.0) kcm_sddm (5.4.3 -> 5.5.1) kcmutils (5.16.0 -> 5.17.0) kcodecs (5.16.0 -> 5.17.0) kcompletion (5.16.0 -> 5.17.0) kconfig (5.16.0 -> 5.17.0) kconfigwidgets (5.16.0 -> 5.17.0) kcoreaddons (5.16.0 -> 5.17.0) kcrash (5.16.0 -> 5.17.0) kdbusaddons (5.16.0 -> 5.17.0) kde-branding-openSUSE kde-cli-tools5 (5.4.3 -> 5.5.1) kde-gtk-config5 (5.4.3 -> 5.5.1) kde-user-manager (5.4.3 -> 5.5.1) kdeclarative (5.16.0 -> 5.17.0) kded (5.16.0 -> 5.17.0) kdelibs4support (5.16.0 -> 5.17.0) kdesignerplugin (5.16.0 -> 5.17.0) kdesu (5.16.0 -> 5.17.0) kdewebkit (5.16.0 -> 5.17.0) kdnssd-framework (5.16.0 -> 5.17.0) kdoctools (5.16.0 -> 5.17.0) kemoticons (5.16.0 -> 5.17.0) kernel-source kfilemetadata5 (5.16.0 -> 5.17.0) kglobalaccel (5.16.0 -> 5.17.0) kgpg (15.08.3 -> 15.12.0) kguiaddons (5.16.0 -> 5.17.0) khotkeys5 (5.4.3 -> 5.5.1) khtml (5.16.0 -> 5.17.0) ki18n (5.16.0 -> 5.17.0) kiconthemes (5.16.0 -> 5.17.0) kidletime (5.16.0 -> 5.17.0) kimageformats (5.16.0 -> 5.17.0) kinfocenter5 (5.4.3 -> 5.5.1) kinit (5.16.0 -> 5.17.0) kio (5.16.0 -> 5.17.0) kitemmodels (5.16.0 -> 5.17.0) kitemviews (5.16.0 -> 5.17.0) kjobwidgets (5.16.0 -> 5.17.0) kjs (5.16.0 -> 5.17.0) kjsembed (5.16.0 -> 5.17.0) kmenuedit5 (5.4.3 -> 5.5.1) knewstuff (5.16.0 -> 5.17.0) knotifications (5.16.0 -> 5.17.0) knotifyconfig (5.16.0 -> 5.17.0) kpackage (5.16.0 -> 5.17.0) kparts (5.16.0 -> 5.17.0) kpeople5 (5.16.0 -> 5.17.0) kplotting (5.16.0 -> 5.17.0) kpty (5.16.0 -> 5.17.0) kross (5.16.0 -> 5.17.0) krunner (5.16.0 -> 5.17.0) kscreen5 (5.4.3 -> 5.5.1) kservice (5.16.0 -> 5.17.0) ksshaskpass5 (5.4.3 -> 5.5.1) ksysguard5 (5.4.3 -> 5.5.1) ktexteditor (5.16.0 -> 5.17.0) ktextwidgets (5.16.0 -> 5.17.0) kunitconversion (5.16.0 -> 5.17.0) kwallet (5.16.0 -> 5.17.0) kwayland (5.4.3 -> 5.5.1) kwidgetsaddons (5.16.0 -> 5.17.0) kwin5 (5.4.3 -> 5.5.1) kwindowsystem (5.16.0 -> 5.17.0) kxmlgui (5.16.0 -> 5.17.0) kxmlrpcclient5 (5.16.0 -> 5.17.0) libKF5ModemManagerQt (5.16.0 -> 5.17.0) libKF5NetworkManagerQt (5.16.0 -> 5.17.0) libkdecoration2 (5.4.3 -> 5.5.1) libkscreen2 (5.4.3 -> 5.5.1) libksysguard5 (5.4.3 -> 5.5.1) libpinyin (1.2.0+git20150731.958c597 -> 1.3.0+git20151204.7b790c9) libzhuyin (1.0.91 -> 1.1.0) milou5 (5.4.3 -> 5.5.1) oxygen5 (5.4.3 -> 5.5.1) oxygen5-icon-theme (5.16.0 -> 5.17.0) perl-Apache-AuthCookie (3.22 -> 3.23) perl-Glib (1.314 -> 1.320) plasma-framework (5.16.0 -> 5.17.0) plasma-nm5 (5.4.3 -> 5.5.1) plasma5-addons (5.4.3 -> 5.5.1) plasma5-desktop (5.4.3 -> 5.5.1) plasma5-openSUSE (13.2 -> 13.3) plasma5-pa (5.4.3 -> 5.5.1) plasma5-session (5.4.3 -> 5.5.1) plasma5-workspace (5.4.3 -> 5.5.1.1) polkit-kde-agent-5 (5.4.3 -> 5.5.1) powerdevil5 (5.4.3 -> 5.5.1) solid (5.16.0 -> 5.17.0) sonnet (5.16.0 -> 5.17.0) systemsettings5 (5.4.3 -> 5.5.1) threadweaver (5.16.0 -> 5.17.0) === Details === ==== attica-qt5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: attica-qt5-devel libKF5Attica5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== baloo5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: baloo5-devel baloo5-file baloo5-kioslaves baloo5-tools libKF5Baloo5 libKF5BalooEngine5 - Update to 5.17.0 * Fix date filter used by timeline:// * BalooCtl: Return after commands * Clean up and armour Baloo::Database::open(), handle more crash conditions * Add check in Database::open(OpenDatabase) to fail if db doesn't exist * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== bluedevil5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: bluedevil5-lang - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== bluez-qt ==== Version update (5.16.0 -> 5.17.0) Subpackages: bluez-qt-devel bluez-qt-imports bluez-qt-udev libKF5BluezQt6 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== branding-openSUSE ==== Version update (13.2 -> 13.3) Subpackages: gfxboot-branding-openSUSE grub2-branding-openSUSE plymouth-branding-openSUSE wallpaper-branding-openSUSE xfce4-splash-branding-openSUSE yast2-qt-branding-openSUSE - Update branding for Tumbleweed with new graphics. - Reuse .spec file from Leap branding package. ==== breeze ==== Version update (5.4.3 -> 5.5.1) Subpackages: breeze5-cursors breeze5-decoration breeze5-style breeze5-wallpapers - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible - Drop set-breezyGTK-as-default-gtk-theme.patch, no longer needed ==== breeze4-style ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== breeze5-icons ==== Version update (5.16.0 -> 5.17.0) - Update to 5.17.0 * Many icons added or improved * Use stylesheets in breeze icons (kde#126166) * Fix and changed system-lock-screen (kde#355902) * Add 24px dialog-information for GTK apps (kde#355204) * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php - Drop upstreamed applets.patch ==== desktop-data-openSUSE ==== Version update (13.2 -> 13.3) - Bump version to 13.3 ==== extra-cmake-modules ==== Version update (5.16.0 -> 5.17.0) Subpackages: extra-cmake-modules-doc - Update to 5.17.0 * Don't warn when SVG(Z) icons are provided with multiple sizes/level of detail * Make sure we load translations on the main thread. (kde#346188) * Overhaul the ECM build system. * Make it possible to enable Clazy on any KDE project * Do not find XCB's XINPUT library by default. * Clean export dir before generating an APK again * Use quickgit for Git repository URL. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== fcitx-libpinyin ==== Version update (0.3.2 -> 0.3.3) - update version 0.3.3 * fix sogou download wrong file name encoding * update libpinyin requirement to 1.2.91 ==== frameworkintegration ==== Version update (5.16.0 -> 5.17.0) Subpackages: frameworkintegration-devel frameworkintegration-plugin libKF5Style5 - Update to 5.17.0 * Add plasmoid installation failed to plasma_workspace.notifyrc * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php - Drop upstreamed 0001-Don-t-add-extra-KDE-SNI-actions-in-our-systemtray-qp.patch ==== gom ==== Version update (0.3.1 -> 0.3.2) - Updated to version 0.3.2: + Add missing annotation for repository object. + Support ordering queries. + Add support for creating new tables in a version. + Fix memory leak in GomResource. + Bindings: - Add missing annotation for repository object. - Add a working Python example. - Make ResourceGroup a sequence in Python bindings. ==== ibus-libpinyin ==== Version update (1.7.2git20150720 -> 1.7.4) - update version 1.7.4 * use pinyin_in_chewing_keyboard method * fixes m_bopomofo_keyboard_mapping option - changes in version 1.7.3 * use libpinyin 1.2.91 * add Catalan * fix for lua 5.2 API change (luaL_register is deprecated) * update clearPinyinUserData method * update m_dictionaries * use pinyin_load_addon_phrase_library function * update setup dialog ==== ibus-libzhuyin ==== Version update (1.7.4 -> 1.7.6) - Update to 1.7.6 * clean up getCursorRight method * fixes getCursorRight and selectCandidate method * fixes getCursorRight method * fixes probe_section_start function * fixes getCursorRight method * fixes processSpace method * fixes prepareCandidates method ==== kactivities5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: kactivities5-devel kactivities5-imports libKF5Activities5 - Update to 5.17.0 * Fixed a lock on the first start of the daemon * Moving QAction creation to the main thread. (kde#351485) * Sometimes clang-format makes a bad decision (kde#355495) * Killing potential synchronization issues * Use org.qtproject instead of com.trolltech * Removing the usage of libkactivities from the plugins * KAStats config removed from the API * Added linking and unlinking to ResultModel * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== karchive ==== Version update (5.16.0 -> 5.17.0) Subpackages: karchive-devel libKF5Archive5 - Update to 5.17.0 * Fix KCompressionDevice::seek(), called when creating a KTar on top of a KCompressionDevice. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kauth ==== Version update (5.16.0 -> 5.17.0) Subpackages: kauth-devel libKF5Auth5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kbookmarks ==== Version update (5.16.0 -> 5.17.0) Subpackages: kbookmarks-devel libKF5Bookmarks5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kcm_sddm ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kcmutils ==== Version update (5.16.0 -> 5.17.0) Subpackages: kcmutils-devel libKF5KCMUtils5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kcodecs ==== Version update (5.16.0 -> 5.17.0) Subpackages: kcodecs-devel libKF5Codecs5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kcompletion ==== Version update (5.16.0 -> 5.17.0) Subpackages: kcompletion-devel libKF5Completion5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kconfig ==== Version update (5.16.0 -> 5.17.0) Subpackages: kconf_update5 kconfig-devel libKF5ConfigCore5 libKF5ConfigGui5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kconfigwidgets ==== Version update (5.16.0 -> 5.17.0) Subpackages: kconfigwidgets-devel libKF5ConfigWidgets5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kcoreaddons ==== Version update (5.16.0 -> 5.17.0) Subpackages: kcoreaddons-devel libKF5CoreAddons5 - Update to 5.17.0 * KAboutData: Allow https:// and other URL schemas in homepage. (kde#355508) * Repair MimeType property when using kcoreaddons_desktop_to_json() * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kcrash ==== Version update (5.16.0 -> 5.17.0) Subpackages: kcrash-devel libKF5Crash5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdbusaddons ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdbusaddons-devel kdbusaddons-tools libKF5DBusAddons5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kde-branding-openSUSE ==== Subpackages: kdelibs4-branding-openSUSE ksplash-qml-branding-openSUSE ksplashx-branding-openSUSE - Update branding for Tumbleweed with new graphics. - Reuse .spec file from Leap branding package.- enable grub theme on aarch64 ==== kde-cli-tools5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kde-gtk-config5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kde-user-manager ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kdeclarative ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdeclarative-components kdeclarative-devel libKF5Declarative5 libKF5QuickAddons5 - Update to 5.17.0 * Port KDeclarative to use KI18n directly * DragArea delegateImage can now be a string from which an icon is automatically created * Add new CalendarEvents library * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kded ==== Version update (5.16.0 -> 5.17.0) Subpackages: kded-devel - Update to 5.17.0 * Unset SESSION_MANAGER envvar instead of setting it empty * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php - Drop upstreamed kded-fix-cmdline-parsing.patch ==== kdelibs4support ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdelibs4support-devel libKF5KDELibs4Support5 - Update to 5.17.0 * Fix some i18n calls. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdesignerplugin ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdesignerplugin-devel kdesignerplugin-lang - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdesu ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdesu-devel libKF5Su5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdewebkit ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdewebkit-devel libKF5WebKit5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdnssd-framework ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdnssd-framework-devel libKF5DNSSD5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kdoctools ==== Version update (5.16.0 -> 5.17.0) Subpackages: kdoctools-devel kdoctools-lang - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kemoticons ==== Version update (5.16.0 -> 5.17.0) Subpackages: kemoticons-devel libKF5Emoticons5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kernel-source ==== Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms - config: armv7hl: Enable EXTCON (boo#959818) CONFIG_PHY_SUN4I_USB could not be enabled, breaking USB on several popular ARM boards such as Cubietruck. - commit 10b7cff ==== kfilemetadata5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: kfilemetadata5-devel - Update to 5.17.0 * Mark m4a as readable by taglib * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kglobalaccel ==== Version update (5.16.0 -> 5.17.0) Subpackages: kglobalaccel-devel kglobalaccel5 libKF5GlobalAccel5 libKF5GlobalAccelPrivate5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kgpg ==== Version update (15.08.3 -> 15.12.0) - Install properly the ServiceMenus on plasma5 bnc#959490- Update to KDE Applications 15.12.0 * KDE Applications 15.12.0 * https://www.kde.org/announcements/announce-applications-15.12.0.php * boo#958887 ==== kguiaddons ==== Version update (5.16.0 -> 5.17.0) Subpackages: kguiaddons-devel libKF5GuiAddons5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== khotkeys5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: khotkeys5-devel - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== khtml ==== Version update (5.16.0 -> 5.17.0) Subpackages: khtml-devel libKF5KHtml5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== ki18n ==== Version update (5.16.0 -> 5.17.0) Subpackages: ki18n-devel libKF5I18n5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kiconthemes ==== Version update (5.16.0 -> 5.17.0) Subpackages: kiconthemes-devel libKF5IconThemes5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kidletime ==== Version update (5.16.0 -> 5.17.0) Subpackages: kidletime-devel libKF5IdleTime5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kimageformats ==== Version update (5.16.0 -> 5.17.0) - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kinfocenter5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible - Drop upstreamed kinfocenter-fix-cmdline-parsing.patch ==== kinit ==== Version update (5.16.0 -> 5.17.0) Subpackages: kinit-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kio ==== Version update (5.16.0 -> 5.17.0) Subpackages: kio-core kio-devel - Update to 5.17.0 * Cookie dialogue: make it work as intended * Fix filename suggestion changing to something random when changing save-as mimetype. * Register DBus name for kioexec (kde#353037) * Update KProtocolManager after configuration change. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php - Drop upstreamed register-dbus-name-for-kioexec.patch ==== kitemmodels ==== Version update (5.16.0 -> 5.17.0) Subpackages: kitemmodels-devel libKF5ItemModels5 - Update to 5.17.0 * Fix KSelectionProxyModel usage in QTableView (kde#352369) * Fix resetting or changing the source model of a KRecursiveFilterProxyModel. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kitemviews ==== Version update (5.16.0 -> 5.17.0) Subpackages: kitemviews-devel libKF5ItemViews5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kjobwidgets ==== Version update (5.16.0 -> 5.17.0) Subpackages: kjobwidgets-devel libKF5JobWidgets5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kjs ==== Version update (5.16.0 -> 5.17.0) Subpackages: kjs-devel libKF5JS5 libKF5JSApi5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kjsembed ==== Version update (5.16.0 -> 5.17.0) Subpackages: kjsembed-devel libKF5JsEmbed5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kmenuedit5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== knewstuff ==== Version update (5.16.0 -> 5.17.0) Subpackages: knewstuff-devel libKF5NewStuff5 - Update to 5.17.0 * registerServicesByGroupingNames can define default more items * Make KMoreToolsMenuFactory::createMenuFromGroupingNames lazy * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== knotifications ==== Version update (5.16.0 -> 5.17.0) Subpackages: knotifications-devel libKF5Notifications5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== knotifyconfig ==== Version update (5.16.0 -> 5.17.0) Subpackages: knotifyconfig-devel libKF5NotifyConfig5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kpackage ==== Version update (5.16.0 -> 5.17.0) Subpackages: kpackage-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kparts ==== Version update (5.16.0 -> 5.17.0) Subpackages: kparts-devel libKF5Parts5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kpeople5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: kpeople5-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kplotting ==== Version update (5.16.0 -> 5.17.0) Subpackages: kplotting-devel libKF5Plotting5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kpty ==== Version update (5.16.0 -> 5.17.0) Subpackages: kpty-devel libKF5Pty5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kross ==== Version update (5.16.0 -> 5.17.0) Subpackages: kross-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== krunner ==== Version update (5.16.0 -> 5.17.0) - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kscreen5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kservice ==== Version update (5.16.0 -> 5.17.0) Subpackages: kservice-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== ksshaskpass5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== ksysguard5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== ktexteditor ==== Version update (5.16.0 -> 5.17.0) Subpackages: ktexteditor-devel - Update to 5.17.0 * Add syntax highlighting for TaskJuggler and PL/I * Make it possible to disable keyword-completion via the config interface. * Resize the tree when the completion model got reset. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== ktextwidgets ==== Version update (5.16.0 -> 5.17.0) Subpackages: ktextwidgets-devel libKF5TextWidgets5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kunitconversion ==== Version update (5.16.0 -> 5.17.0) Subpackages: kunitconversion-devel libKF5UnitConversion5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kwallet ==== Version update (5.16.0 -> 5.17.0) Subpackages: kwallet-devel kwallet-tools kwalletd5 libKF5Wallet5 libkwalletbackend5-5 - Update to 5.17.0 * Correctly handle the case where the user deactivated us * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kwayland ==== Version update (5.4.3 -> 5.5.1) Subpackages: kwayland-devel - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible - Drop no longer applicable fix-wayland-1.3-dependency.diff ==== kwidgetsaddons ==== Version update (5.16.0 -> 5.17.0) Subpackages: kwidgetsaddons-devel libKF5WidgetsAddons5 - Update to 5.17.0 * Fix a small artifact of KRatingWidget on hi-dpi. * Refactor and fix the feature introduced in bug 171343 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kwin5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: kwin5-devel - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== kwindowsystem ==== Version update (5.16.0 -> 5.17.0) Subpackages: kwindowsystem-devel libKF5WindowSystem5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kxmlgui ==== Version update (5.16.0 -> 5.17.0) Subpackages: kxmlgui-devel libKF5XmlGui5 - Update to 5.17.0 * Don't call QCoreApplication::setQuitLockEnabled(true) on init. * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== kxmlrpcclient5 ==== Version update (5.16.0 -> 5.17.0) Subpackages: kxmlrpcclient5-devel libKF5XmlRpcClient5 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== libKF5ModemManagerQt ==== Version update (5.16.0 -> 5.17.0) Subpackages: libKF5ModemManagerQt-devel libKF5ModemManagerQt6 - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== libKF5NetworkManagerQt ==== Version update (5.16.0 -> 5.17.0) Subpackages: libKF5NetworkManagerQt-devel libKF5NetworkManagerQt6 - Added 0001-make-it-work-with-older-NM-versions.patch committed also upstream. This adds some #ifdefs around code that needs NM 0.9.10 so it also builds with NM 0.9.8- Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== libkdecoration2 ==== Version update (5.4.3 -> 5.5.1) Subpackages: libkdecoration2-devel libkdecorations2-5 libkdecorations2private5 - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== libkscreen2 ==== Version update (5.4.3 -> 5.5.1) Subpackages: libKF5Screen6 libkscreen2-devel libkscreen2-plugin - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== libksysguard5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: libksysguard5-devel libksysguard5-helper - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== libpinyin ==== Version update (1.2.0+git20150731.958c597 -> 1.3.0+git20151204.7b790c9) - Update to version 1.3.0+git20151204.7b790c9: * support force tone in pinyin parsers * support fallback tables in double pinyin * many bugfixes and refactors - drop patch: libpinyin-1.2.0-avoid_download_at_buildtime.patch - add patch: libpinyin-avoid_download_at_buildtime.patch ==== libzhuyin ==== Version update (1.0.91 -> 1.1.0) Subpackages: libzhuyin-data libzhuyin7 - Update to 1.1.0 * fixes zhuyin_choose_candidate method * rename zhuyin_get_raw_full_pinyin to zhuyin_get_raw_user_input method * write zhuyin_valid_zhuyin_keys method * fixes zhuyin_in_chewing_keyboard method * fixes ChewingDiscreteParser2 ==== milou5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== oxygen5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: oxygen5-cursors oxygen5-decoration oxygen5-devel oxygen5-lang oxygen5-sounds oxygen5-style - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== oxygen5-icon-theme ==== Version update (5.16.0 -> 5.17.0) Subpackages: oxygen5-icon-theme-large - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== perl-Apache-AuthCookie ==== Version update (3.22 -> 3.23) - updated to 3.23 see /usr/share/doc/packages/perl-Apache-AuthCookie/Changes 3.23 2015-09-10 - Improve CGI mode param() handling to avoi CGI.pm's "param() called in list context" warning. - add support for Apache 2.4 via mod_perl 1.09. * **** IMPORTANT ***** Apache 2.4 has a *VERY* different API for authentication. You will need to port your subclass and configuration over to the Apache 2.4 API in order to use Apache 2.4! Please be sure to read README.apache-2.4.pod for porting instructions! ==== perl-Glib ==== Version update (1.314 -> 1.320) - Update to 1.320: * Makefile.PL: Add IRC link to metadata block. * Glib::GenPod: Supply default namespace blurbs. * Properly escape dash in generated API index POD. ==== plasma-framework ==== Version update (5.16.0 -> 5.17.0) Subpackages: plasma-framework-components plasma-framework-private - Make plasma-framework-devel conflict with kapptemplate- Update to 5.17.0 * Add basic plasmoid as example for developerguide * Add a couple of plasmoid templates for kapptemplate/kdevelop * [calendar] Delay the model reset until the view is ready (kde#355943) * Don't reposition while hiding. (kde#354352) * [IconItem] Don't crash on null KIconLoader theme (kde#355577) * Dropping image files onto a panel will no longer offer to set them as wallpaper for the panel * Dropping a .plasmoid file onto a panel or the desktop will install and add it * Remove the now unused platformstatus kded module (kde#348840) * Allow paste on password fields * Fix positioning of edit menu, add a button to select * [calendar] Use ui language for getting the month name (kde#353715) * [calendar] Sort the events by their type too * [calendar] Move the plugin library to KDeclarative * [calendar] qmlRegisterUncreatableType needs a bit more arguments * Allow adding config categories dynamically * [calendar] Move the plugins handling to a separate class * Allow plugins to supply event data to Calendar applet (kde#349676) * Check for slot existence before connecting or disconnecting (kde#354751) * [plasmaquick] Don't link OpenGL explicitly * [plasmaquick] Drop XCB::COMPOSITE and DAMAGE dependency * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== plasma-nm5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: plasma-nm5-openconnect plasma-nm5-openvpn plasma-nm5-pptp plasma-nm5-vpnc - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== plasma5-addons ==== Version update (5.4.3 -> 5.5.1) Subpackages: plasma5-addons-kimpanel - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== plasma5-desktop ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php - Drop upstreamed fix-migration-of-multiple-favorites.patch- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible- Add fix-migration-of-multiple-favorites.patch: fixes migration of kickoff's favorites (kde#356398) ==== plasma5-openSUSE ==== Version update (13.2 -> 13.3) Subpackages: plasma5-desktop-branding-openSUSE plasma5-workspace-branding-openSUSE - Bump version to 13.3 - the current internal version of Tumbleweed.- Bump Plasma (Build)Requires to 5.5.1- Bump Plasma (Build)Requires to 5.5.0 ==== plasma5-pa ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== plasma5-session ==== Version update (5.4.3 -> 5.5.1) - Bump to 5.5.1- Bump to 5.5.0 - Split the wayland session into separate package ==== plasma5-workspace ==== Version update (5.4.3 -> 5.5.1.1) Subpackages: drkonqi5 plasma5-workspace-devel plasma5-workspace-libs - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php - Drop upstreamed patches: 0001-notifications-Check-if-the-popup-is-visible-before-u.patch 0002-notifications-Move-reading-globalConfig-from-ctor-to.patch 0003-Make-comment-section-of-the-timezones-configuration-.patch 0004-notifications-Fix-default-notification-position-sett.patch 0001-Forward-mouse-enter-and-leave-events-on-feathered-ed.patch kde355684.patch use-old-connect-syntax.patch- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible - Drop no longer needed fix-wayland-requirement.patch and rb125743.patch - Added patches from upstream: 0001-notifications-Check-if-the-popup-is-visible-before-u.patch 0002-notifications-Move-reading-globalConfig-from-ctor-to.patch 0003-Make-comment-section-of-the-timezones-configuration-.patch 0004-notifications-Fix-default-notification-position-sett.patch 0001-Forward-mouse-enter-and-leave-events-on-feathered-ed.patch kde355684.patch use-old-connect-syntax.patch- Rebased fix-breeze-sddm-theme-with-many-users.patch in preparation for 5.5.0- add dependency on xprop (called by /usr/bin/startkde) ==== polkit-kde-agent-5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== powerdevil5 ==== Version update (5.4.3 -> 5.5.1) - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== solid ==== Version update (5.16.0 -> 5.17.0) Subpackages: libKF5Solid5 solid-devel solid-imports solid-tools - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== sonnet ==== Version update (5.16.0 -> 5.17.0) Subpackages: libKF5SonnetCore5 libKF5SonnetUi5 sonnet-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php ==== systemsettings5 ==== Version update (5.4.3 -> 5.5.1) Subpackages: systemsettings5-devel - Update to 5.5.1: * Bugfix release * For more details please see: https://www.kde.org/announcements/plasma-5.5.1.php- Update to 5.5.0: * For more details please see: https://dot.kde.org/2015/12/08/plasma-55-beautiful-new-artwork - Move to cmake(...) BuildRequires where possible ==== threadweaver ==== Version update (5.16.0 -> 5.17.0) Subpackages: libKF5ThreadWeaver5 threadweaver-devel - Update to 5.17.0 * For more details please see: https://www.kde.org/announcements/kde-frameworks-5.17.0.php Packages removed: dynamic-wallpaper-branding-openSUSE krunner-devel libpinyin6 plasma-framework-devel tennebon-dynamic-wallpaper xembed-sni-proxy Packages added: libKF5CalendarEvents5 kscreenlocker
kscreenlocker-lang libKScreenLocker5 libpinyin7 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
[pruned] A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list? The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference: http://lists.opensuse.org/opensuse/2015-12/msg00646.html (Do I hear a dissenting voice in the form of Patrick Shanahan? :-) ) BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.3.3-5 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
[pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC
Hey Basil, you're suscribed to both list right? Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it. The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution. You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others. ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op maandag 4 januari 2016 10:02:23 schreef Bruno Friedmann:
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
[pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC
Hey Basil, you're suscribed to both list right?
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff.
Hear, hear. Better than my own words. -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/01/16 21:38, Knurpht - Gertjan Lettink wrote:
Op maandag 4 januari 2016 10:02:23 schreef Bruno Friedmann:
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. [pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC Hey Basil, you're suscribed to both list right?
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff. Hear, hear. Better than my own words.
Good heavens! Are you sure?! I wasn't impressed with "those" words. Are you sure you couldn't do better than "those" words? (Remember: you have put your name down for a position on the board.) BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.3.3-6 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04/01/16 20:02, Bruno Friedmann wrote:
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. [pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC Hey Basil, you're suscribed to both list right?
Yes, I am subscribed to both lists. You're point being?
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
Ah, that's your point. Well, you see, I am not the author of those messages and I do not have the authority to FWD them. Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
You know what I think? I think that you have been taking lessons from your 'Fearless Leader' in how to reply to people's posts and therefore "how to make friends and influence people". I ask a legitimate question from Ludwig and you, who is not Ludwig, come out with your response. I didn't ask you the question -- and your response did not even come close in providing a sensible answer. And, therefore, I await the sensible answer from Ludwig.
ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff.
Bruno, you wrote this message at 2002 hours on 4 January 2015. As a board member who has been active on the board for the past 2 years and taking a keen interest in all things openSUSE-Community-Board and openSUSE-Community itself you would know that nominations for vacancies on the board closed on 1 January 2015[#]. Apart from missing the closing date for nominating I have no intention of nominating for anything -- I have had my share of being on boards et al. [#] http://lists.opensuse.org/opensuse-project/2015-12/msg00083.html BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.3.3-6 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hey Basil, you're suscribed to both list right?
Yes, I am subscribed to both lists. You're point being?
As you found out: reading more of the message before replying makes sense.. don't reply to every word / sentence
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
Ah, that's your point. Well, you see, I am not the author of those messages and I do not have the authority to FWD them.
Say what? I hereby authorize you to forward the mails as you see fit. In case you did not get the point yet: openSUSE is an open project - you don't have to ask for authorization to do awesome things.. you just have to want to do them and then chose to do them.
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
You know what I think? I think that you have been taking lessons from your 'Fearless Leader' in how to reply to people's posts and therefore "how to make friends and influence people".
Maybe he did... I did not :) so: GET MOVING :) (and for people immune to sarcasm: this was some!)
I ask a legitimate question from Ludwig and you, who is not Ludwig, come out with your response.
You actually replied to an auto-generated email... which is not sent by Ludwig, the person as we know, himself. The mailaddress used there is just a technicality, as it was easier for him to setup.
I didn't ask you the question -- and your response did not even come close in providing a sensible answer.
eh... he tried to go the approach of finding a solution for the NOW until the final solution can be / will be implemented. That's a noble gesture.
And, therefore, I await the sensible answer from Ludwig.
As Ludwig is on holiday, you'll have to wait a bit longer... and don't get fooled by "Ludwig's" automatic mails about new snapshots.. he's still on holiday and not in front of the PC. So... I know I'm not Ludwig, but I gave you all the things to empower you to go DO the things... let's not only TALK about things, let's get things done. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 6 January 2016 at 13:27, Dominique Leuenberger / DimStar <dimstar@opensuse.org> wrote:
Say what? I hereby authorize you to forward the mails as you see fit. In case you did not get the point yet: openSUSE is an open project - you don't have to ask for authorization to do awesome things.. you just have to want to do them and then chose to do them.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
eh... he tried to go the approach of finding a solution for the NOW until the final solution can be / will be implemented. That's a noble gesture.
So... I know I'm not Ludwig, but I gave you all the things to empower you to go DO the things... let's not only TALK about things, let's get things done.
+100 Thank you Dominique for doing a perfect job of reflecting an opinion which I share but have struggled to convey satisfactorily lately. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dominique Leuenberger / DimStar wrote:
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
Where is this being called from? (or how do I find out where it is called from?) The To: address(es) appears to be specified by the caller, not hardcoded in the script. According to the README, the scripts are deployed on openqa.opensuse.org, I guess that's where the changes are needed? -- Per Jessen, Zürich (6.2°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 6 January 2016 at 16:31, Per Jessen <per@computer.org> wrote:
Dominique Leuenberger / DimStar wrote:
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
Where is this being called from? (or how do I find out where it is called from?) The To: address(es) appears to be specified by the caller, not hardcoded in the script. According to the README, the scripts are deployed on openqa.opensuse.org, I guess that's where the changes are needed?
Good question, and I don't know the answer, but at this is a thread more focused on the topic of the announcer script than the original I want to leave my opinion here If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Richard Brown wrote:
On 6 January 2016 at 16:31, Per Jessen <per@computer.org> wrote:
Dominique Leuenberger / DimStar wrote:
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
Where is this being called from? (or how do I find out where it is called from?) The To: address(es) appears to be specified by the caller, not hardcoded in the script. According to the README, the scripts are deployed on openqa.opensuse.org, I guess that's where the changes are needed?
Good question, and I don't know the answer,
I found it - https://github.com/openSUSE/osc-plugin-factory/blob/master/factory-package-n...
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ? -- Per Jessen, Zürich (5.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 6 January 2016 at 16:43, Per Jessen <per@computer.org> wrote:
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
I don't see how that is relevant - maintenance updates to 13.2 and Leap 42.1 can cause issues too, and users are expected to ask for support at opensuse@ while the announcements regarding updates get sent to opensuse-updates@ Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing) I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Richard Brown wrote:
On 6 January 2016 at 16:43, Per Jessen <per@computer.org> wrote:
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
I don't see how that is relevant - maintenance updates to 13.2 and Leap 42.1 can cause issues too, and users are expected to ask for support at opensuse@ while the announcements regarding updates get sent to opensuse-updates@
I guess I see TW slightly differently, but as I don't use TW myself, my view might not count for much. I have kindof assumed that TW users would be keeping their installations "more" current than a typical Leap or 13.2 user.
Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing)
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think? -- Per Jessen, Zürich (5.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
06.01.2016 18:58, Per Jessen пишет:
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think?
Whatever place is selected I'd rather avoid getting the same notification multiple times on multiple lists. Is it possible to select for which versions user gets notifications on -updates? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jan 6, 2016 at 10:58 AM, Per Jessen <per@computer.org> wrote:
Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing)
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think?
I think you're asking in the wrong place. The main opensuse list is what will be affected, not -factory, so you need to ask there. fyi: my experience with Tumbleweed is as developer/tester, not as a user. I don't run it on any of my "production" systems. Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jan 06, 2016 at 04:58:06PM +0100, Per Jessen wrote:
Richard Brown wrote:
On 6 January 2016 at 16:43, Per Jessen <per@computer.org> wrote:
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
I don't see how that is relevant - maintenance updates to 13.2 and Leap 42.1 can cause issues too, and users are expected to ask for support at opensuse@ while the announcements regarding updates get sent to opensuse-updates@
I guess I see TW slightly differently, but as I don't use TW myself, my view might not count for much. I have kindof assumed that TW users would be keeping their installations "more" current than a typical Leap or 13.2 user.
Tumbleweed is a rolling release. There are no updates. Despite the case of emergencies.
Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing)
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think?
-1 Less lists please. openSUSE already has more than enough. If I run Tumbleweed I'm subscribed to opensuse-factory and that's it. Ludwigs script does exactly what it is intended for. It's a heads up to Tumbleweed users that there is a new release available. Enhancements to the format, structure of the content as we have it seen recently are always welcome. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 6 January 2016 at 17:18, Lars Müller <lmuelle@suse.com> wrote:
On Wed, Jan 06, 2016 at 04:58:06PM +0100, Per Jessen wrote:
Richard Brown wrote:
On 6 January 2016 at 16:43, Per Jessen <per@computer.org> wrote:
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
I don't see how that is relevant - maintenance updates to 13.2 and Leap 42.1 can cause issues too, and users are expected to ask for support at opensuse@ while the announcements regarding updates get sent to opensuse-updates@
I guess I see TW slightly differently, but as I don't use TW myself, my view might not count for much. I have kindof assumed that TW users would be keeping their installations "more" current than a typical Leap or 13.2 user.
Tumbleweed is a rolling release. There are no updates. Despite the case of emergencies.
Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing)
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think?
-1
Less lists please. openSUSE already has more than enough. If I run Tumbleweed I'm subscribed to opensuse-factory and that's it.
Ludwigs script does exactly what it is intended for. It's a heads up to Tumbleweed users that there is a new release available.
Enhancements to the format, structure of the content as we have it seen recently are always welcome.
Thanks,
Lars
Lars, we're talking about adding opensuse-updates@ to the destinations for TW Announcements We're not talking about removing opensuse-factory@ from the destinations for TW announcements So don't worry, you would not have to add another mailinglist -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/06/2016 11:18 AM, Lars Müller wrote:
On Wed, Jan 06, 2016 at 04:58:06PM +0100, Per Jessen wrote:
Richard Brown wrote:
On 6 January 2016 at 16:43, Per Jessen <per@computer.org> wrote:
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
I don't see how that is relevant - maintenance updates to 13.2 and Leap 42.1 can cause issues too, and users are expected to ask for support at opensuse@ while the announcements regarding updates get sent to opensuse-updates@
I guess I see TW slightly differently, but as I don't use TW myself, my view might not count for much. I have kindof assumed that TW users would be keeping their installations "more" current than a typical Leap or 13.2 user.
Tumbleweed is a rolling release. There are no updates. Despite the case of emergencies.
Don't get me wrong, if there are people out there who really want opensuse@ to get the TW announcements 3-5 times a week, I'm not objecting to the idea (more attention to TW in more places is not a bad thing)
I just see the TW announcements as equivalent to the opensuse-updates@ announcements we have for the other distributions, so I think opensuse-updates@ is the natural place for the TW announcements
I'm fine with that, what do others think?
-1
Less lists please. openSUSE already has more than enough. If I run Tumbleweed I'm subscribed to opensuse-factory and that's it.
Well we have seen that having all the mail traffic related to TW show up on -factory can cause certain problems. Thus, I'd say we should consider other options. And as Richard alreday pointed out, -updates already exists, thus we will not be creating a net new list. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
On 01/06/2016 10:43 AM, Per Jessen wrote:
Richard Brown wrote:
On 6 January 2016 at 16:31, Per Jessen <per@computer.org> wrote:
Dominique Leuenberger / DimStar wrote:
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
True: https://github.com/openSUSE/osc-plugin-factory/blob/master/factor y-package-news/announcer.py is the code of the announcer... care to create a pull request for the right things?
Where is this being called from? (or how do I find out where it is called from?) The To: address(es) appears to be specified by the caller, not hardcoded in the script. According to the README, the scripts are deployed on openqa.opensuse.org, I guess that's where the changes are needed?
Good question, and I don't know the answer,
I found it -
https://github.com/openSUSE/osc-plugin-factory/blob/master/factory-package-n...
If the TW announcer is changed to mail additional addresses, I think it should mail the snapshot announcements to opensuse-updates@opensuse.org and not opensuse@opensuse.org
We don't mail the user support list every time we release updates to our other distributions, and I don't think regular TW updates should be of any particular interest to the readers of opensuse@ like they are to the readers of opensuse-factory@
Agreed. I am not certain if we even send an announcement mail to opensuse@ for major releases. Just because we release new packages more frequently for TW than for openSUSE_X or openSUSE Leap X shouldn't really change the behavior w.r.t. message sending. I think opensuse-updates@ is the place for those messages, as well as -factory.
Perhaps it depends on the best/primary place for support for TW users - do they address their questions to opensuse@ or opensuse-factory@ ?
Well that I think is really somewhat of a predicament. The primary purpose of -factory is to discuss topics that are related to the development of TW thus user support message do not really fall into that realm. At the same time the opensuse@ list is not really targeted at users of TW but more toward openSUSE_X and openSUSE Leap users. I'd say both arrangement are more of a historical artifact as when the lists were established TW did not exist and non developers were not encouraged to use Factory or Factory-Tested. Given the development of TW as a contender for those that are interested in rolling releases but are not developers it is probably worth to think about the definition and be more explicit where we expect ML traffic for those users to go. My initial response would be that for those users that use TW and are not developers the traffic should go to opensuse@. That risks a delay in developers becoming aware of an issue, but things that are real issues should end up in bugzilla anyway rather than be discussed on the list. This approach, I think, would require us to expand the definition of opensuse@ a bit from it's current description Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
On 6 January 2016 at 17:17, Robert Schweikert <rjschwei@suse.com> wrote:
My initial response would be that for those users that use TW and are not developers the traffic should go to opensuse@. That risks a delay in developers becoming aware of an issue, but things that are real issues should end up in bugzilla anyway rather than be discussed on the list. This approach, I think, would require us to expand the definition of opensuse@ a bit from it's current description
I agree, but I don't think that requires an expansion of the definition of opensuse@, which is defined as "Generic questions and User to User support for all the openSUSE distributions" on http://lists.opensuse.org/ That seems to fit exactly what you're saying, and what opensuse@ has always been about -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/06/2016 11:27 AM, Richard Brown wrote:
On 6 January 2016 at 17:17, Robert Schweikert <rjschwei@suse.com> wrote:
My initial response would be that for those users that use TW and are not developers the traffic should go to opensuse@. That risks a delay in developers becoming aware of an issue, but things that are real issues should end up in bugzilla anyway rather than be discussed on the list. This approach, I think, would require us to expand the definition of opensuse@ a bit from it's current description
I agree, but I don't think that requires an expansion of the definition of opensuse@, which is defined as "Generic questions and User to User support for all the openSUSE distributions" on http://lists.opensuse.org/
That seems to fit exactly what you're saying, and what opensuse@ has always been about
Yes, technically you are correct. However, I would say there is more to the story. TW is perceived as being different due to it's rolling nature. Per's question, "where should the user traffic for TW go" is perfectly valid. And while it is technically already answered by the opensuse@ description I bet that if there is one person asking the question there will be others (and we know there have been others). Thus, we have to ask ourselves whether it is better to sit on the technically correct description of the opensuse@ list as it is, and potentially answer the "where does the user traffic for TW go" question over and over again, or should we consider the human factor and human perception and expand the opensuse@ description to include TW? I would lean toward the later option to make things more explicit and hopefully direct traffic to the right location from the get go. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
Op woensdag 6 januari 2016 23:17:56 schreef Basil Chupin:
On 04/01/16 20:02, Bruno Friedmann wrote:
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
[pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC
Hey Basil, you're suscribed to both list right?
Yes, I am subscribed to both lists. You're point being?
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
Ah, that's your point. Well, you see, I am not the author of those messages and I do not have the authority to FWD them.
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
You know what I think? I think that you have been taking lessons from your 'Fearless Leader' in how to reply to people's posts and therefore "how to make friends and influence people".
I ask a legitimate question from Ludwig and you, who is not Ludwig, come out with your response.
I didn't ask you the question -- and your response did not even come close in providing a sensible answer.
And, therefore, I await the sensible answer from Ludwig.
ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff.
Bruno, you wrote this message at 2002 hours on 4 January 2015.
As a board member who has been active on the board for the past 2 years and taking a keen interest in all things openSUSE-Community-Board and openSUSE-Community itself you would know that nominations for vacancies on the board closed on 1 January 2015[#]. Apart from missing the closing date for nominating I have no intention of nominating for anything -- I have had my share of being on boards et al.
[#] http://lists.opensuse.org/opensuse-project/2015-12/msg00083.html
BC
Leaving out the "please": Stop your anti-board campaign. Either contribute or refrain from posting. -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 6 januari 2016 23:17:56 schreef Basil Chupin:
On 04/01/16 20:02, Bruno Friedmann wrote:
On Monday 04 January 2016 17.51:58 Basil Chupin wrote:
On 02/01/16 03:58, Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
[pruned]
A question, Ludwig: why are these announcements about the release of new snapshots of Tumbleweed still being posted in this Factory list -- a list which most people probably do not read -- instead of being posted for all to see in the opensuse [help] list?
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list -- reference:
http://lists.opensuse.org/opensuse/2015-12/msg00646.html
(Do I hear a dissenting voice in the form of Patrick Shanahan? :-) )
BC
Hey Basil, you're suscribed to both list right?
Yes, I am subscribed to both lists. You're point being?
Then it would be nice contribution for those end users, to simply forward the mail to the users list until factory/tumbleweed team find a way to auto-push to it.
Ah, that's your point. Well, you see, I am not the author of those messages and I do not have the authority to FWD them.
Besides, it doesn't take much effort to add a 'CC:' in the HEADER to also send a copy of a message to 'opensuse' list.
The Chairman, as any board member, as any contributor, do what he can, with the free time, we can all allow to openSUSE contribution.
You've plenty of time to write, nice. Use that to drive the community to a be a nice place to play with others.
You know what I think? I think that you have been taking lessons from your 'Fearless Leader' in how to reply to people's posts and therefore "how to make friends and influence people".
I ask a legitimate question from Ludwig and you, who is not Ludwig, come out with your response.
I didn't ask you the question -- and your response did not even come close in providing a sensible answer.
And, therefore, I await the sensible answer from Ludwig.
ps : You know, you can still apply to become Board Member, so you will be able to share the slaps some of you have kindly throw to our Board staff.
Bruno, you wrote this message at 2002 hours on 4 January 2015.
As a board member who has been active on the board for the past 2 years and taking a keen interest in all things openSUSE-Community-Board and openSUSE-Community itself you would know that nominations for vacancies on the board closed on 1 January 2015[#]. Apart from missing the closing date for nominating I have no intention of nominating for anything -- I have had my share of being on boards et al.
[#] http://lists.opensuse.org/opensuse-project/2015-12/msg00083.html
BC
A second reply: some googling and going through the archives shows you have a long history of questioning and ridiculing board decisions, mostly wrapped up in personal attacks. IMHO that's not what these lists ( nor the forums, nor the social media pages ) are for. -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 04.01.2016 um 07:51 schrieb Basil Chupin:
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list
Actually, all of Factory/Tumbleweed is mostly for developers and thus, IMHO the opensuse-factory ML seems to be a very appropriate place. On the other hand, every developer is also a user so you may as well forward the mail to the other ML if people dont mind the extra traffic. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlaLaF0ACgkQSTYLOx37oWTXTgCfd85wbLSjsUlUcvCf3v+1VnhT M3IAoOWjlE3mXmUDxRNUTectQ/va1kdi =7Wwb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/01/16 17:53, Bernhard M. Wiedemann wrote:
Am 04.01.2016 um 07:51 schrieb Basil Chupin:
The current incumbent to the role of the Chairman of the OpenSUSE Board pronounced his dictum that the Factory list was for developer matters and that user support/matters are to be dealt with in the opensuse list
Actually, all of Factory/Tumbleweed is mostly for developers and thus, IMHO the opensuse-factory ML seems to be a very appropriate place.
On the other hand, every developer is also a user so you may as well forward the mail to the other ML if people dont mind the extra traffic.
Without going over what I asked a couple of times about Tumbleweed (TW) in recent times, and what others have stated along the lines which you just expressed above, the bottom line is that TW is now considered to be an official release and another release version of openSUSE. As the post I quoted in the earlier msg states, questions about TW should be addressed to 'opensuse' and not '*-factory'. What has muddied the waters is that every time someone asked a question about TW in 'opensuse' Patrick Shanahan would come down on them "like a ton of bricks" :-) telling them that the question belonged in '*-factory'. However, TW is no longer "factory" and questions about it should now be asked in 'opensuse'. To make matters worse, I now see that questions about *Leap* -- yes, Leap! -- are being asked in '*-factory' and I am waiting for Patrick to set them right :-) . If he fails to do so by the middle of this year I think I will mention something to anyone asking Qs about Leap in '*-factory' :-) . BC -- Using openSUSE 13.2, KDE 4.14.9 & kernel 4.3.3-6 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (12)
-
Andrei Borzenkov -
Basil Chupin -
Bernhard M. Wiedemann -
Bruno Friedmann -
Dominique Leuenberger / DimStar -
Greg Freemyer -
Knurpht - Gertjan Lettink -
Lars Müller -
Ludwig Nussel -
Per Jessen -
Richard Brown -
Robert Schweikert