Search results for "contribute to wiki"

Fedora 30 updates-testing report

by updates＠fedoraproject.org

The following Fedora 30 Security updates need testing: Age URL 1 https://bodhi.fedoraproject.org/updates/FEDORA-2019-e41e19457b python-jinja2-2.10.1-1.fc30 1 https://bodhi.fedoraproject.org/updates/FEDORA-2019-4696630d6f checkstyle-8.0-7.fc30 The following Fedora 30 Critical Path updates have yet to be approved: Age URL 2 https://bodhi.fedoraproject.org/updates/FEDORA-2019-538350d153 proj-5.2.0-2.fc30 1 https://bodhi.fedoraproject.org/updates/FEDORA-2019-fb8fb8a905 pyparsing-2.4.0-1.fc30 0 https://bodhi.fedoraproject.org/updates/FEDORA-2019-63f1324ee0 v4l-utils-1.16.5-2.fc30 0 https://bodhi.fedoraproject.org/updates/FEDORA-2019-d1d54444ac libiptcdata-1.0.5-1.fc30 0 https://bodhi.fedoraproject.org/updates/FEDORA-2019-c688883c43 ibus-1.5.20-2.fc30 0 https://bodhi.fedoraproject.org/updates/FEDORA-2019-682247b2db libblockdev-2.21-3.fc30 The following builds have been pushed to Fedora 30 updates-testing E-2.3-1.fc30 adobe-source-han-sans-cn-fonts-2.001-1.fc30 adobe-source-han-sans-tw-fonts-2.001-1.fc30 appstream-generator-0.7.7-1.fc30 apvlv-0.1.5-4.fc30 cockpit-192-1.fc30 cups-2.2.11-2.fc30 dbus-broker-20-4.fc30 fedora-obsolete-packages-30-40 gif2png-2.5.13-1.fc30 gimp-layer-via-copy-cut-1.6-14.fc30 gir-to-d-0.19.0-1.fc30 glibd-2.1.0-1.fc30 gourmet-0.17.4-15.fc30 httpd-2.4.39-3.fc30 libbluray-1.1.1-1.fc30 libyuv-0-0.35.20190401git4bd08cb.fc30 linux-firmware-20190416-95.fc30 meson-0.50.1-1.fc30 mingw-pcre2-10.33-1.fc30 mingw-postgresql-11.2-2.fc30 netpbm-10.86.00-2.fc30 openssl-1.1.1b-5.fc30 pcre2-10.33-1.fc30 php-twig-1.39.1-1.fc30 php-twig2-2.8.1-1.fc30 poppler-0.73.0-9.fc30 python-natsort-6.0.0-2.fc30 qbs-1.13.0-1.fc30 qt-creator-4.9.0-2.fc30 rpmgrill-0.34-1.fc30 wesnoth-1.14.7-1.fc30 Details about builds: ================================================================================ E-2.3-1.fc30 (FEDORA-2019-a2af5c3e6e) Equational Theorem Prover -------------------------------------------------------------------------------- Update Information: Changes in version 2.3: - Merged support for lambda-free higher-order logic - Improved fingerprint indexing by excluding one more subcase for finging instances - Made clausification more robust for extreme examples -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Jerry James <loganjerry(a)gmail.com> - 2.3-1 - New upstream release - Add -format-overflow patch -------------------------------------------------------------------------------- ================================================================================ adobe-source-han-sans-cn-fonts-2.001-1.fc30 (FEDORA-2019-8ff41fe8ff) Adobe OpenType Pan-CJK font family for Simplified Chinese -------------------------------------------------------------------------------- Update Information: Update to 2.001 -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Peng Wu <pwu(a)redhat.com> - 2.001-1 - Update to 2.001 -------------------------------------------------------------------------------- ================================================================================ adobe-source-han-sans-tw-fonts-2.001-1.fc30 (FEDORA-2019-8ff41fe8ff) Adobe OpenType Pan-CJK font family for Traditional Chinese -------------------------------------------------------------------------------- Update Information: Update to 2.001 -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Peng Wu <pwu(a)redhat.com> - 2.001-1 - Update to 2.001 -------------------------------------------------------------------------------- ================================================================================ appstream-generator-0.7.7-1.fc30 (FEDORA-2019-146f3a7d7f) Fast AppStream metadata generator -------------------------------------------------------------------------------- Update Information: Update to rebuild against new `glib2` and `ldc` to fix FTBFS in Fedora 30 and make it installable. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Neal Gompa <ngompa13(a)gmail.com> - 0.7.7-1 - Update to 0.7.7 (#1674286) * Mon Feb 18 2019 Kalev Lember <klember(a)redhat.com> - 0.7.4-2 - Rebuilt for ldc 1.14 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1689701 - gir-to-d-0.19.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1689701 [ 2 ] Bug #1674286 - appstream-generator-0.7.7 is available https://bugzilla.redhat.com/show_bug.cgi?id=1674286 -------------------------------------------------------------------------------- ================================================================================ apvlv-0.1.5-4.fc30 (FEDORA-2019-819aeed576) PDF viewer which behaves like Vim -------------------------------------------------------------------------------- Update Information: - Fix FTBFS rhbz #1674653 -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Filipe Rosset <rosset.filipe(a)gmail.com> - 0.1.5-4 - Fix FTBFS rhbz #1674653 * Thu Jan 31 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.1.5-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild -------------------------------------------------------------------------------- References: [ 1 ] Bug #1674653 - apvlv: FTBFS in Fedora rawhide/f30 https://bugzilla.redhat.com/show_bug.cgi?id=1674653 -------------------------------------------------------------------------------- ================================================================================ cockpit-192-1.fc30 (FEDORA-2019-f8fc718f7b) Web Console for Linux servers -------------------------------------------------------------------------------- Update Information: - Machines: Auto-detect guest operating system - Translation cleanup - Allow accounts with non-standard shells -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Martin Pitt <mpitt(a)redhat.com> - 192-1 - Machines: Auto-detect guest operating system - Translation cleanup - Allow accounts with non-standard shells -------------------------------------------------------------------------------- ================================================================================ cups-2.2.11-2.fc30 (FEDORA-2019-d4413e5722) CUPS printing system -------------------------------------------------------------------------------- Update Information: 1700664 - Stop advertising the HTTP methods that are supported -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Zdenek Dohnal <zdohnal(a)redhat.com> - 1:2.2.11-2 - 1700664 - Stop advertising the HTTP methods that are supported -------------------------------------------------------------------------------- ================================================================================ dbus-broker-20-4.fc30 (FEDORA-2019-7b1733dc68) Linux D-Bus Message Broker -------------------------------------------------------------------------------- Update Information: Fix an assert when configuration reload fails. -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Tom Gundersen <teg(a)jklm.no> - 20-4 - Fix assert due to failing reload #1700514 * Tue Apr 16 2019 Adam Williamson <awilliam(a)redhat.com> - 20-3 - Rebuild with Meson fix for #1699099 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700514 - [abrt] dbus-broker: service_activate(): dbus-broker-launch killed by SIGABRT https://bugzilla.redhat.com/show_bug.cgi?id=1700514 -------------------------------------------------------------------------------- ================================================================================ fedora-obsolete-packages-30-40 (FEDORA-2019-1cde7963ca) A package to obsolete retired packages -------------------------------------------------------------------------------- Update Information: Obsolete python2-envisage ---- Obsolete mongodb, mongodb-server, mongodb-test < 4.0.3-4, python2-certbot < 0.31.0-3, python2-josepy < 1.1.0-7. ---- Obsolete python2-cinderclient < 3.5.0-2 ---- Obsolete python2-testify < 0.11.0-13, obsolete python2-cinderclient < 3.5.0-2. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Orion Poplawski <orion(a)nwra.com> - 30-40 - Obsolete python2-envisage (#1700310) * Tue Apr 16 2019 Miro Hron��ok <mhroncok(a)redhat.com> - 30-39 - Obsolete mongodb, mongodb-server, mongodb-test < 4.0.3-4 (#1700073) - Obsolete python2-certbot < 0.31.0-3 and python2-josepy < 1.1.0-7 (#1700045) * Mon Apr 15 2019 Kevin Fenzi <kevin(a)scrye.com> - 30-38 - Obsolete mongodb < 4.0.3-3 (#1700073) * Mon Apr 15 2019 Miro Hron��ok <mhroncok(a)redhat.com> - 30-37 - Obsolete python2-cinderclient < 3.5.0-2 * Sun Apr 14 2019 Miro Hron��ok <mhroncok(a)redhat.com> - 30-36 - Obsolete python2-testify < 0.11.0-13 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700310 - package python2-envisage-4.6.0-1.fc29.noarch requires python2-ipykernel, but none of the providers can be installed https://bugzilla.redhat.com/show_bug.cgi?id=1700310 [ 2 ] Bug #1700073 - obsolete mongodb https://bugzilla.redhat.com/show_bug.cgi?id=1700073 [ 3 ] Bug #1700045 - Obsolete python2-josepy https://bugzilla.redhat.com/show_bug.cgi?id=1700045 -------------------------------------------------------------------------------- ================================================================================ gif2png-2.5.13-1.fc30 (FEDORA-2019-ed24abb7cb) A GIF to PNG converter -------------------------------------------------------------------------------- Update Information: - New upstream release, fixes rhbz #1674965 -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Filipe Rosset <rosset.filipe(a)gmail.com> - 2.5.13-1 - New upstream release, fixes rhbz #1674965 * Thu Jan 31 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 2.5.11-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild -------------------------------------------------------------------------------- References: [ 1 ] Bug #1674965 - gif2png: FTBFS in Fedora rawhide/f30 https://bugzilla.redhat.com/show_bug.cgi?id=1674965 -------------------------------------------------------------------------------- ================================================================================ gimp-layer-via-copy-cut-1.6-14.fc30 (FEDORA-2019-f11dd13864) Layer via copy/cut plug-in for GIMP -------------------------------------------------------------------------------- Update Information: Switch back requirement to python 2 -------------------------------------------------------------------------------- ChangeLog: * Mon Apr 15 2019 Luya Tshimbalanga <luya(a)fedoraproject.org> - 1.6-14 - Apply sheband fix for Fedora 30 and up * Tue Mar 19 2019 Luya Tshimbalanga <luya(a)fedoraproject.org> - 1.6-13 - Revert to Python 2 dependency -------------------------------------------------------------------------------- References: [ 1 ] Bug #1685039 - [abrt] gimp-layer-via-copy-cut: syntax(): layer-via-copy-cut.py:27:<module>: File "/usr/lib64/gimp/2.0/python/gimpfu.py", line 224 https://bugzilla.redhat.com/show_bug.cgi?id=1685039 -------------------------------------------------------------------------------- ================================================================================ gir-to-d-0.19.0-1.fc30 (FEDORA-2019-146f3a7d7f) Tool to create D bindings from GObject introspection files -------------------------------------------------------------------------------- Update Information: Update to rebuild against new `glib2` and `ldc` to fix FTBFS in Fedora 30 and make it installable. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Neal Gompa <ngompa13(a)gmail.com> - 0.19.0-1 - Update to 0.19.0 (#1689701) * Tue Apr 16 2019 Adam Williamson <awilliam(a)redhat.com> - 0.18.0-4 - Rebuild with Meson fix for #1699099 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1689701 - gir-to-d-0.19.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1689701 [ 2 ] Bug #1674286 - appstream-generator-0.7.7 is available https://bugzilla.redhat.com/show_bug.cgi?id=1674286 -------------------------------------------------------------------------------- ================================================================================ glibd-2.1.0-1.fc30 (FEDORA-2019-146f3a7d7f) D bindings for the GLib C Utility Library -------------------------------------------------------------------------------- Update Information: Update to rebuild against new `glib2` and `ldc` to fix FTBFS in Fedora 30 and make it installable. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Neal Gompa <ngompa13(a)gmail.com> - 2.1.0-1 - Update to 2.1.0 * Mon Feb 18 2019 Kalev Lember <klember(a)redhat.com> - 2.0.2-2 - Rebuilt for ldc 1.14 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1689701 - gir-to-d-0.19.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1689701 [ 2 ] Bug #1674286 - appstream-generator-0.7.7 is available https://bugzilla.redhat.com/show_bug.cgi?id=1674286 -------------------------------------------------------------------------------- ================================================================================ gourmet-0.17.4-15.fc30 (FEDORA-2019-a80d9eaab5) Recipe Manager for the GNOME desktop environment -------------------------------------------------------------------------------- Update Information: Change python macro to specify python2, fixes FTBFS Bug 1675051 -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Jeff Raber <jeff.raber(a)gmail.com> - 0.17.4-15 - Change python macro to specify python2, fixes FTBFS Bug 1675051 * Fri Feb 1 2019 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.17.4-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Fri Jul 13 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.17.4-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild -------------------------------------------------------------------------------- References: [ 1 ] Bug #1675051 - gourmet: FTBFS in Fedora rawhide/f30 https://bugzilla.redhat.com/show_bug.cgi?id=1675051 -------------------------------------------------------------------------------- ================================================================================ httpd-2.4.39-3.fc30 (FEDORA-2019-419873d0ae) Apache HTTP Server -------------------------------------------------------------------------------- Update Information: This update fixes the `/etc/httpd/state` symlink, and fixes a **httpd 2.4.39** regression in `mod_reqtimeout`. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 9 2019 Joe Orton <jorton(a)redhat.com> - 2.4.39-3 - fix statedir symlink to point to /var/lib/httpd (#1697662) - mod_reqtimeout: fix default values regression (PR 63325) -------------------------------------------------------------------------------- References: [ 1 ] Bug #1697662 - /etc/httpd/state: broken symbolic link to ../../var/lib/httpd/state (supplied by httpd-2.4.39-2.fc29.x86_64) https://bugzilla.redhat.com/show_bug.cgi?id=1697662 -------------------------------------------------------------------------------- ================================================================================ libbluray-1.1.1-1.fc30 (FEDORA-2019-c7a4e2c202) Library to access Blu-Ray disks for video playback -------------------------------------------------------------------------------- Update Information: Update to 1.1.1 - Enable playback without menus when index.bdmv is missing. - Improve error resilience and stability. - Improve BD-J compability. - Fix resetting user-selected streams when playing without menus. - Fix stack overflow when using Java9+ with debugger connection. - Fix polygon-based BD-J graphics primitives. - Fix pkg-config Libs.private. -------------------------------------------------------------------------------- ChangeLog: * Mon Apr 8 2019 Xavier Bachelot <xavier(a)bachelot.org> 1.1.0-1 - Update to 1.1.1 (RHBZ#1676566). -------------------------------------------------------------------------------- References: [ 1 ] Bug #1676566 - libbluray-1.1.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1676566 -------------------------------------------------------------------------------- ================================================================================ libyuv-0-0.35.20190401git4bd08cb.fc30 (FEDORA-2019-36e426c909) YUV conversion and scaling functionality library -------------------------------------------------------------------------------- Update Information: * Fixed issue with linking ---- * Fixed pkgconfig-file -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Peter Lemenkov <lemenkov(a)gmail.com> - 0-0.35.20190401git4bd08cb - Fix linkage against libjpeg * Tue Apr 16 2019 Peter Lemenkov <lemenkov(a)gmail.com> - 0-0.34.20190401git4bd08cb - Fixed pkgconfig-file -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700731 - /lib64/libyuv.so.0: undefined symbol: jpeg_resync_to_restart https://bugzilla.redhat.com/show_bug.cgi?id=1700731 [ 2 ] Bug #1649246 - libyuv package should include a pkgconfig file https://bugzilla.redhat.com/show_bug.cgi?id=1649246 -------------------------------------------------------------------------------- ================================================================================ linux-firmware-20190416-95.fc30 (FEDORA-2019-2fd0fc2aa7) Firmware files used by the Linux kernel -------------------------------------------------------------------------------- Update Information: Update to upstream 20190416 release -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Peter Robinson <pbrobinson(a)fedoraproject.org> 20190416-95 - Update to upstream 20190416 release -------------------------------------------------------------------------------- ================================================================================ meson-0.50.1-1.fc30 (FEDORA-2019-7570333d2d) High productivity build system -------------------------------------------------------------------------------- Update Information: Update to 0.50.1 -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Igor Gnatenko <ignatenkobrain(a)fedoraproject.org> - 0.50.1-1 - Update to 0.50.1 * Mon Apr 15 2019 Adam Williamson <awilliam(a)redhat.com> - 0.50.0-4 - Backport patch to revert ld binary method change (#1699099) -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700772 - meson-0.50.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1700772 -------------------------------------------------------------------------------- ================================================================================ mingw-pcre2-10.33-1.fc30 (FEDORA-2019-8bb7680275) MinGW Windows pcre2 library -------------------------------------------------------------------------------- Update Information: Update to pcre2-10.33, see https://www.pcre.org/news.txt for details. -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Sandro Mani <manisandro(a)gmail.com> - 10.33-1 - Update to 10.33 -------------------------------------------------------------------------------- ================================================================================ mingw-postgresql-11.2-2.fc30 (FEDORA-2019-811bb84248) MinGW Windows PostgreSQL library -------------------------------------------------------------------------------- Update Information: Fix for static libraries -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Michael Cronenworth <mike(a)cchtml.com> - 11.2-2 - Add patches to release proper static libraries. -------------------------------------------------------------------------------- ================================================================================ netpbm-10.86.00-2.fc30 (FEDORA-2019-65444c50fe) A library for handling different graphics file formats -------------------------------------------------------------------------------- Update Information: Enable MPEG support in netpmb -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Josef Ridky <jridky(a)redhat.com> - 10.86.00-2 - Enable MPEG and MPEG-2 support (#1700164) -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700164 - Enable MPEG-2 support https://bugzilla.redhat.com/show_bug.cgi?id=1700164 -------------------------------------------------------------------------------- ================================================================================ openssl-1.1.1b-5.fc30 (FEDORA-2019-d812b6a69f) Utilities from the general purpose cryptography library with TLS implementation -------------------------------------------------------------------------------- Update Information: Fix for a regression in openssl-1.1.1b affecting some applications -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Tom�� Mr��z <tmraz(a)redhat.com> 1.1.1b-5 - fix for BIO_get_mem_ptr() regression in 1.1.1b (#1691853) * Wed Mar 27 2019 Tom�� Mr��z <tmraz(a)redhat.com> 1.1.1b-4 - drop unused BuildRequires and Requires in the -devel subpackage -------------------------------------------------------------------------------- References: [ 1 ] Bug #1691853 - BIO_set_close(bio, BIO_NOCLOSE) seems to be ignored https://bugzilla.redhat.com/show_bug.cgi?id=1691853 -------------------------------------------------------------------------------- ================================================================================ pcre2-10.33-1.fc30 (FEDORA-2019-6521c025fd) Perl-compatible regular expression library -------------------------------------------------------------------------------- Update Information: This release supports callouts from pcre2_substitute(). This release adds PCRE2_EXTRA_ESCAPED_CR_IS_LF, PCRE2_EXTRA_ALT_BSUX, and PCRE2_COPY_MATCHED_SUBJECT matching options. This release implements alphabetic names for atomic groups and lookaround assertions, and Perl script runs. It also allows non-ASCII characters in capture group names if PCRE2_UTF option is set. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Petr Pisar <ppisar(a)redhat.com> - 10.33-1 - 10.33 bump -------------------------------------------------------------------------------- ================================================================================ php-twig-1.39.1-1.fc30 (FEDORA-2019-2b77facd31) The flexible, fast, and secure template engine for PHP -------------------------------------------------------------------------------- Update Information: **Version 1.39.1** (2019-04-16) * fixed EscaperNodeVisitor ---- **Version 1.39.0** (2019-04-16) * added Traversable support for the length filter * fixed some wrong location in error messages * made exception creation faster * made escaping on ternary expressions (?: and ??) more fine-grained * added the possibility to give a nice name to string templates (template_from_string function) * fixed the "with" behavior to always include the globals (for consistency with the "include" and "embed" tags) * fixed "include" with "ignore missing" when an error loading occurs in the included template * added support for a new whitespace trimming option ({%~ ~%}, {{~ ~}}, {#~ ~#}) -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Remi Collet <remi(a)remirepo.net> - 1.39.1-1 - update to 1.39.1 -------------------------------------------------------------------------------- ================================================================================ php-twig2-2.8.1-1.fc30 (FEDORA-2019-a40959cf8b) The flexible, fast, and secure template engine for PHP -------------------------------------------------------------------------------- Update Information: **Version 2.8.1** (2019-04-16) * fixed EscaperNodeVisitor * deprecated passing a 3rd, 4th, and 5th arguments to the Sandbox exception classes * deprecated Node::setTemplateName() in favor of Node::setSourceContext() ---- **Version 2.8.0** (2019-04-16) * added Traversable support for the length filter * fixed some wrong location in error messages * made exception creation faster * made escaping on ternary expressions (?: and ??) more fine-grained * added the possibility to give a nice name to string templates (template_from_string function) * fixed the "with" behavior to always include the globals (for consistency with the "include" and "embed" tags) * fixed "include" with "ignore missing" when an error loading occurs in the included template * added support for a new whitespace trimming option ({%~ ~%}, {{~ ~}}, {#~ ~#}) * added the "column" filter -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Remi Collet <remi(a)remirepo.net> - 2.8.1-1 - update to 2.8.1 -------------------------------------------------------------------------------- ================================================================================ poppler-0.73.0-9.fc30 (FEDORA-2019-1ddce0c095) PDF rendering library -------------------------------------------------------------------------------- Update Information: Security fix for CVE-2019-11026. -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Marek Kasik <mkasik(a)redhat.com> - 0.73.0-9 - Fix infinite loop in broken files - Resolves: #1699863 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1699862 - CVE-2019-11026 poppler: infinite recursion in function FontInfoScanner::scanFonts in FontInfo.cc https://bugzilla.redhat.com/show_bug.cgi?id=1699862 -------------------------------------------------------------------------------- ================================================================================ python-natsort-6.0.0-2.fc30 (FEDORA-2019-5eb08f2bf1) Python library that sorts lists using the "natural order" sort -------------------------------------------------------------------------------- Update Information: Update to the latest stable release. The main changes since the last release are: * package suggests: pyICU (optional dependency) to sort in a locale- dependent manner; * Remove deprecated APIs (kwargs `number_type`, `signed`, `exp`, `as_path`, `py3_safe`; enums `ns.TYPESAFE`, `ns.DIGIT`, `ns.VERSION`; functions `versorted`, `index_versorted`) (issue #81); * Re-expose `natsort_key` as "public" and remove the associated `DepricationWarning`; * Better developer documentation. -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 Jos�� Matos <jamatos(a)fedoraproject.org> - 6.0.0-2 - Suggests: pyICU, to sort in a locale-dependent manner * Wed Apr 17 2019 Jos�� Matos <jamatos(a)fedoraproject.org> - 6.0.0-1 - update to 6.0.0 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1672493 - python-natsort-6.0.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1672493 -------------------------------------------------------------------------------- ================================================================================ qbs-1.13.0-1.fc30 (FEDORA-2019-4e92a1fcff) Cross platform build tool -------------------------------------------------------------------------------- Update Information: Update to qt-creator-4.9.0 final and qbs-1.13.0. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Sandro Mani <manisandro(a)gmail.com> - 1:1.13.0-1 - Update to 1.13.0 -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700515 - Can't update qt5-qtbase because of qt-creator https://bugzilla.redhat.com/show_bug.cgi?id=1700515 [ 2 ] Bug #1700446 - qbs-1.13.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1700446 -------------------------------------------------------------------------------- ================================================================================ qt-creator-4.9.0-2.fc30 (FEDORA-2019-4e92a1fcff) Cross-platform IDE for Qt -------------------------------------------------------------------------------- Update Information: Update to qt-creator-4.9.0 final and qbs-1.13.0. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Sandro Mani <manisandro(a)gmail.com> - 4.9.0-2 - Rebuild (qbs) * Mon Apr 15 2019 Sandro Mani <manisandro(a)gmail.com> - 4.9.0-1 - Update to 4.9.0 * Wed Mar 27 2019 Sandro Mani <manisandro(a)gmail.com> - 4.9.0-0.4-rc - Update to 4.9.0-rc * Thu Mar 7 2019 Sandro Mani <manisandro(a)gmail.com> - 4.9.0-0.3.beta2 - Update to 4.9.0-beta2 * Sun Mar 3 2019 Rex Dieter <rdieter(a)fedoraproject.org> - 4.9.0-0.2.beta1 - rebuild (qt5) -------------------------------------------------------------------------------- References: [ 1 ] Bug #1700515 - Can't update qt5-qtbase because of qt-creator https://bugzilla.redhat.com/show_bug.cgi?id=1700515 [ 2 ] Bug #1700446 - qbs-1.13.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=1700446 -------------------------------------------------------------------------------- ================================================================================ rpmgrill-0.34-1.fc30 (FEDORA-2019-87d4422fa0) A utility for catching problems in koji builds -------------------------------------------------------------------------------- Update Information: Includes upstream pull request #27 contributed by Petr Pisar -------------------------------------------------------------------------------- ChangeLog: * Wed Apr 17 2019 R��man Joost <roman(a)bromeco.de> - 0.34-1 - Includes upstream pull request #27 contributed by Petr Pisar -------------------------------------------------------------------------------- References: [ 1 ] Bug #1539633 - DesktopLint does not search icons directly in /usr/share/pixmaps https://bugzilla.redhat.com/show_bug.cgi?id=1539633 -------------------------------------------------------------------------------- ================================================================================ wesnoth-1.14.7-1.fc30 (FEDORA-2019-3dd23bd08e) Turn-based strategy game with a fantasy theme -------------------------------------------------------------------------------- Update Information: wesnoth 1.14.7 release. -------------------------------------------------------------------------------- ChangeLog: * Tue Apr 16 2019 Kalev Lember <klember(a)redhat.com> - 1.14.7-1 - Update to 1.14.7 --------------------------------------------------------------------------------

5 years, 1 month

Fedora 28 Update: clamav-0.101.1-1.fc28

by updates＠fedoraproject.org

-------------------------------------------------------------------------------- Fedora Update Notification FEDORA-2019-7e3eae1b62 2019-01-15 01:52:52.993232 -------------------------------------------------------------------------------- Name : clamav Product : Fedora 28 Version : 0.101.1 Release : 1.fc28 URL : https://www.clamav.net/ Summary : End-user tools for the Clam Antivirus scanner Description : Clam AntiVirus is an anti-virus toolkit for UNIX. The main purpose of this software is the integration with mail servers (attachment scanning). The package provides a flexible and scalable multi-threaded daemon, a command line scanner, and a tool for automatic updating via Internet. The programs are based on a shared library distributed with the Clam AntiVirus package, which you can use with your own software. The virus database is based on the virus database from OpenAntiVirus, but contains additional signatures (including signatures for popular polymorphic viruses, too) and is KEPT UP TO DATE. -------------------------------------------------------------------------------- Update Information: ClamAV 0.101.1 Patch has been released ClamAV 0.101.1 is an urgent patch release to address an issue in 0.101.0 specifically for developers that depend on libclamav. The issue in 0.101.0 is that clamav.h required supporting headers that were not provided on make install. To address this issue, the internal cltypes.h header has been replaced by a clamav-types.h that is generated on ./configure and will be installed alongside clamav.h. Other changes Increased the default CommandReadTimeout to reduce the chance of mail loss if using clamav-milter with the TCP socket. Contribution by Scott Kitterman. Fixes for --with-libjson and --with-libcurl to correctly accept library install path arguments. Acknowledgements The ClamAV team thanks the following individuals for their code submissions: Scott Kitterman Known Issues Some users have observed crashes the first time running freshclam after upgrading from 0.100 to 0.101. We haven't yet tracked down the source of the issue, but have found that the issue resolves itself and that subsequent calls to freshclam work as expected. ---- Fix libclamav headers -------------------------------------------------------------------------------- ChangeLog: * Thu Jan 10 2019 S��rgio Basto <sergio(a)serjux.com> - 0.101.1-1 - Update to 0.101.1 * Thu Jan 3 2019 Orion Poplawski <orion(a)nwra.com> - 0.101.0-3 - Actually apply patch * Thu Jan 3 2019 Orion Poplawski <orion(a)nwra.com> - 0.101.0-2 - Explicitly list sonames to catch soname bumps - Backport header fix (bug #1663011) * Thu Dec 13 2018 Orion Poplawski <orion(a)nwra.com> - 0.101.0-1 - Update to 0.101.0 - Add %license - pdf docs replaced with html * Thu Oct 4 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.2-2 - Revert unwanted committed parts of commit "clean whitespace" * Thu Oct 4 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.2-1 - Update to 0.100.2 - Fix logrotate example (#1610735) - Improve clamd@.service (enter in commit "clean whitespace" by mistake sorry) * Mon Jul 30 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.1-4 - Change the default location of configuration files in clamconf, binaries and man pages, replacing with our default packaging (#859339). * Sun Jul 29 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.1-3 - Modify group of /var/run/clamd.scan to virusgroup - Add some SELinux notes from (#787434) - Drop pointless clamav-0.99.1-setsebool.patch - Drop conditionalized build of noarch * Thu Jul 12 2018 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.100.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Wed Jul 11 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.1-1 - Update to 0.100.1 * Mon Jul 2 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.0-3 - Remove sub-package clamav-data-empty - Also remove conflicts between clamav-data and clamav-data-empty * Sun Jun 3 2018 S��rgio Basto <sergio(a)serjux.com> - 0.100.0-2 - Try to mitigate bug #1583599 - Move comments one line (to read before starting the scriptlet) - clamav-milter could work without clamd and without sendmail (#1583599) - Get rid of provides/requires with updateuser, virusgroup, scanuser and milteruser and just simply require clamav-filesystem * Mon May 28 2018 Robert Scheck <robert(a)fedoraproject.org> - 0.100.0-1 - Upgrade to 0.100.0 (#1565381) -------------------------------------------------------------------------------- References: [ 1 ] Bug #1663011 - clamav-devel-0.101 unusable due to missing cltypes.h https://bugzilla.redhat.com/show_bug.cgi?id=1663011 -------------------------------------------------------------------------------- This update can be installed with the "dnf" update program. Use su -c 'dnf upgrade --advisory FEDORA-2019-7e3eae1b62' at the command line. For more information, refer to the dnf documentation available at http://dnf.readthedocs.io/en/latest/command_ref.html#upgrade-command-label All packages are signed with the Fedora Project GPG key. More details on the GPG keys used by the Fedora Project can be found at https://fedoraproject.org/keys --------------------------------------------------------------------------------

5 years, 4 months

FYI: Centos joins RedHat

by SternData

>From the CENTOS user mailing list ********* *BEGIN ENCRYPTED or SIGNED PART* ********* With great excitement I'd like to announce that we are joining the Red Hat family. The CentOS Project ( http://www.centos.org ) is joining forces with Red Hat. Working as part of the Open Source and Standards team ( http://community.redhat.com/ ) to foster rapid innovation beyond the platform into the next generation of emerging technologies. Working alongside the Fedora and RHEL ecosystems, we hope to further expand on the community offerings by providing a platform that is easily consumed, by other projects to promote their code while we maintain the established base. We are also launching the new CentOS.org website ( http://www.centos.org ). ------------- The new initiative is going to be overseen by the new CentOS Governing Board. The initial Board comprises of the existing CentOS Core team members : - Ralph Angenent - Tru Hyunh - Johnny Hughes JR - Jim Perrin - Karanbir Singh and also sees new members: - Fabian Arrotin, who comes to the board nominated from the community - Carl Trieloff, Karsten Wade, and Mike McLean join us, nominated by Red Hat. Please join me in welcoming the new members to the Board. The key operating points of the Board are going to be: Public, Open, and Inclusive. You can find more information about the governance model, the board, and the operating policies we are proposing at http://www.centos.org/about/governance/ Furthermore, some of the existing CentOS Core members are moving to take up roles at Red Hat, as a part of their sponsorship of the CentOS Project, allowing these people to work on the Project as their primary job function. This includes Johnny Hughes Jr, Jim Perrin, Fabian Arrotin, and myself. We will be working with and operating out of the Red Hat Open Source and Standards team in the CTO's Office. ------------- Some of the things that are not changing: - The CentOS Linux platform isn't changing. The process and methods built up around the platform however are going to become more open, more inclusive and transparent. - The sponsor driven content network that has been central to the success of the CentOS efforts over the years stays intact. - The bugs, issues, and incident handling process stays as it has been with more opportunities for community members to get involved at various stages of the process. - The Red Hat Enterprise Linux to CentOS firewall will also remain. Members and contributors to the CentOS efforts are still isolated from the RHEL Groups inside Red Hat, with the only interface being srpm / source path tracking, no sooner than is considered released. In summary: we retain an upstream. Feel free to reach out if you have specific concerns about how this change impacts your CentOS story. URLs mentioned at the bottom of this email should be a good starting point. ------------- Some of the key things that are changing: - Some of us now work for Red Hat, but not RHEL. This should not have any impact to our ability to do what we have done in the past, it should facilitate a more rapid pace of development and evolution for our work on the community platform. - Red Hat is offering to sponsor some of the buildsystem and initial content delivery resources - how we are able to consume these and when we are able to make use of this is to be decided. - Sources that we consume, in the platform, in the addons, or the parallel stacks such as Xen4CentOS will become easier to consume with a git.centos.org being setup, with the scripts and rpm metadata needed to create binaries being published there. The Board also aims to put together a plan to allow groups to come together within the CentOS ecosystem as a Special Interest Group (SIG) and build CentOS Variants on our resources, as officially endorsed. You can read about the proposal at http://www.centos.org/variants/ - Because we are now able to work with the Red Hat legal teams, some of the contraints that resulted in efforts like CentOS-QA being behind closed doors, now go away and we hope to have the entire build, test, and delivery chain open to anyone who wishes to come and join the effort. The changes we make are going to be community inclusive, and promoted, proposed, formalised, and actioned in an open community centric manner on the centos-devel mailing list. And I highly encourage everyone to come along and participate. ------------- Contacting us works best via the established community mechanisms. - Real time chats via IRC ( http://wiki.centos.org/irc ) ; To keep conversation sanity intact, I recommend using the #centos-devel channel to discuss project related activity while #centos is best used for end user conversations. - The Mailing lists are a great way to interface with the developers, contributors and the community at large ( http://lists.centos.org ). As with IRC, we recommend using the centos-devel list to talk about project related issues while the general centos list is best used for end user conversations. - The CentOS Forums are another great way to engage in conversation with other users ( http://www.centos.org/forums ), if you prefer that mechanism. All the above mentioned venues are public and open to the community, should you wish to discuss something privately, you can email us at centosdev(a)centos.org. Press requests should be sent to press(a)centos.org. Please note that it will take us much longer to reply to private requests as compared to content on the public venues. ------------- In the coming days we are going to create opportunities for people to come and get involved in more face to face interactions. Starting with a regular scheduled office-hours format hangouts ( http://wiki.centos.org/OfficeHours ) that start early next week. We are trying to split the sessions into two different timezones so as to maximise the number of people who are able to join. The sessions will run live, with #centos-devel on irc.freenode.net being used for conversations alongside. We are also running a CentOS Dojo on the 31st Jan 2014 at Belgium ( http://wiki.centos.org/Events/Dojo/Brussels2014 ); The event will run two tracks, with lots of opportunities for social interaction between the talks; followed by CentOS in the Clouds Hack sessions. We are limited in the number of people we can accomodate, so I encourage everyone to register early. ------------- I want to take this opportunity to thank all the sponsors, the contributors and the CentOS team members for all their help over the years, the project is built completely upon those contributions - and I look forward to seeing even more involvement from everyone as we move forward. ------------- A Request: We are still sorting out content in various places and it might take a day or two to get everything in place. In the mean time if you find something stale and perhaps misleading in the new context ( or the old one! ) please drop in on #centos-devel at irc.centos.org and let us know. ------------- Some URLS: - http://www.centos.org/ The CentOS Project - http://wiki.centos.org/ CentOS Community wiki - http://community.redhat.com/ RedHat OSAS - http://www.redhat.com/about/news/press-archive/2014/1/red-hat-and-centos-... - Red Hat Press Release - http://community.redhat.com/centos-faq - Red Hat FAQ's about the initiative - http://wiki.centos.org/FAQ - CentOS FAQ's about the initiative Enjoy! and regards, Karanbir Singh and everyone from the CentOS team, -- Karanbir Singh, Project Chair, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ********** *END ENCRYPTED or SIGNED PART* ********** _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce -- -- Steve

10 years, 5 months

[Bug 817268] Review Request: python-faces - Python project management tool

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=817268 --- Comment #10 from Alec Leamas <leamas.alec(a)gmail.com> 2012-05-09 04:22:09 EDT --- (In reply to comment #9) > Issues: > [!]: MUST Requires correct, justified where necessary. > Not requiring pygtk2. Good catch! Agreed. > [!]: The 'git' macro is defined but not used Agreed > [!]: I suggest the srpm be named 'faces-pm', and split into four rpms: > - faces-pm "A project management tool based on Python" (the executable, > and desktop entry file if you can provide) > - python-faces "Python modules of Faces project management tool" > - python-metapie "An application framework based on wxpython" (quoted from > metapie/__init__.py) > - python-faces-timescale "Timescale module for python-faces for Faces > project management tool" Agreed: split out python-metapie. As for application faces-pm, see below. > [!] There is a special homepage for this project: http://faces.homeip.net/ Agreed. There is more about that, faces have been and is hosted at many sites. Still I think sourceforge is the place for the most recent activities. The submitter of bug #693425 made some work here, and the overall conclusion at that point was to proceed like this. Since then, no more actual source has been released, so the situation is the same. Agreed: URL:http://faces.homeip.net/ > [!] The urls for Patch0 and Patch3 are the same. Agreed (patch0 is wrong). > [!] Patch0 is too heavy, actually cuts and relicenses the original file. I > think the job can be done within OpenERP instead of patching faces/__init__.py. Agreed: to patch the license is unacceptable. This is published under GPLv2+, and a patch can't change this. Also a good catch! That said, is there a rule saying how heavy a patch can be? Given that current code doesn't even pass setup.py? And that upstream doesn't respond when submitting patches? > Since Faces-pm seems dead, it may be acceptable that OpenERP adopts some useful > source files from Faces directly. This would be to bundle. That's something to avoid IMHO. > [!]: MUST Changelog in prescribed format. > Every time of change should bump release number, even still under review. No. http://fedoraproject.org/wiki/Packaging:Guidelines#Multiple_Changelog_Ent... > An empty is required between two changelog entries I could certainly put a blank between the entries. Is there such a requirement in the guidelines? > [!]: SHOULD Package functions as described. > I may not approve this package if the application doesn't run. Simply removing > the executable is not responsible. This is the core issue. We have here a package which is not maintained since many years, and thus partly doesn't work with recent python. There is no recent upstream activities I'm aware of about this. I have actually looked into patching it, and my conclusion is that it would *not* be responsible of me to try to fix it. It's simply beyond what I can do, it would end up in something which doesn't work. OTOH, openerp is doing exactly that for the libraries. It's just that they have no interest in the application. The project is dead, definitely. The openerp patch represents among other things what need to be done just to build it. This patch is sent upstream without any response at all. Note that the last commits (2010) are indeed openerp contributions i. e., openerp is nowadays the part which (partly) keeps faces up to recent python standards, something the upstream project don't. Open issues: - If you can't approve removing the application. - If you can't accept patch0 (revised for licensing) because being to heavy. I suggest that we consult the mailing list in case these cannot be resolved here. With these issues open, I don't publish new links ATM. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

12 years, 1 month

Re: FESCo elections

by Toshio Kuratomi

On Sat, 2007-06-23 at 17:14 -0700, Karsten Wade wrote: > On Wed, 2007-06-20 at 10:00 -0700, Toshio Kuratomi wrote: > > Basically, you should be able to vote if you are under FESCo's > > authority. You should not be able to vote if you are not. > > The problem I have with this is that FESCo, unlike all bodies save the > Board, makes decisions that affect the entire project. > > I think "affects" should be the criteria, not "authority." > This raises some interesting thought-experiments. Let me state my core thought before diving off on those tangents, though: I think "authority" should be the guiding principle. "Affects" is much too broad. To take the argument to absurdium, what FESCo decides affects Ubuntu, SuSE, and the rest of the greater Linux Community. Should they be allowed to vote? At some point in the spectrum between cvsextras and absurdium, FESCo is the ruler of a body of people and therefore needs to listen to the wishes of those people by being elected by them. At some point beyond that, FESCo becomes the ruler of a neighboring project and FESCo's Project and the Neighbor Project have to learn to get along with each other. The farther out from the central purpose of a group that you cast your net of enfranchisement, the more you dilute the knowledge of what work the people you're voting for are doing presently. What is candidate A going to contribute to FESCo's future? Are they active in groups that are part of the central purpose of FESCo? Do they make good decisions there? Do they stick to their guns on things that are important and compromise on things that are not? The wider the scope of people, the more likely that you're going to end up with people who only know about a single issue: Candidate A wanted to delay the Fedora 8 Release Date, what do I care about their decisions on acls, packaging standards, string freeze, legality of firmware, etc. The only thing that affected me was the Release Date. That said, I won't argue that FESCo's authority has been expanded since the merge. Is FESCo's new charter to have (loose) authority over all of Fedora? FESCo is in charge of implementing Board decisions so Art, Docs, l10n, infrastructure, and the rest of Fedora are subprojects of FESCo? For the purposes of the election I can see a certain attraction to this. What you say about FESCo's decisions affecting everybody within Fedora has merit. For the purposes of working within the Fedora Project I am a small bit worried, though. Firstly, FESCo can only be a part of so much, involved in so much, accountable for so much. Secondly, Docs, Art, and other groups are viable independent communities that don't need the (hopefully light) hand of another committee sitting between them and the Board. In concrete terms, I'm against opening the election to cla_done. I'm for expanding and contracting FESCo's area of authority until it includes the groups that want to vote for FESCo (if everyone does and we end up including every group that's not cla_done/cla_fedora I'd be a little worried about the long term ramifications but we'll see when we get there.) P.S. If we include the wiki EditGroup in the "groups that can vote" someone has to write an importer that turns the EditGroup into Fedora Account System (FAS) accounts and adds them to a new FAS group. This may not be as hard as writing a new package dep solver but it is not trivial. And we're on a deadline. [OFFTOPIC] In our current world we have one very large and powerful neighbor that every other community has to learn to exist with. Would the world be better or worse if everyone affected by the neighbor had the ability to vote in the elections held there? Bonus points for humor if your reply starts with "Does this assume Microsoft stocks are equally distributed or still concentrated in the hands of a few?" ;-) [/OFFTOPIC] -Toshio

16 years, 11 months

tomh pushed to nodejs-grunt-contrib-uglify (master). "Update to 0.11.1 upstream release"

by notifications＠fedoraproject.org

From 0ee85f917fa7903809856c6c9d1f1860a504bbfa Mon Sep 17 00:00:00 2001 From: Tom Hughes <tom(a)compton.nu> Date: Thu, 11 Feb 2016 09:38:43 +0000 Subject: Update to 0.11.1 upstream release --- .gitignore | 1 + ...y-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch | 25 -------- nodejs-grunt-contrib-uglify.spec | 70 ++++++++-------------- sources | 4 +- 4 files changed, 28 insertions(+), 72 deletions(-) delete mode 100644 nodejs-grunt-contrib-uglify-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch diff --git a/.gitignore b/.gitignore index 91e7be9..ebbbd5e 100644 --- a/.gitignore +++ b/.gitignore @@ -4,3 +4,4 @@ /docs-v0.5.0.tar.bz2 /grunt-contrib-uglify-0.5.0.tgz /tests-v0.5.0.tar.bz2 +/grunt-contrib-uglify-0.11.1.tar.gz diff --git a/nodejs-grunt-contrib-uglify-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch b/nodejs-grunt-contrib-uglify-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch deleted file mode 100644 index 497c610..0000000 --- a/nodejs-grunt-contrib-uglify-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch +++ /dev/null @@ -1,25 +0,0 @@ -From 61e329c76e6e229dd2460fb57aac4865f44acd43 Mon Sep 17 00:00:00 2001 -From: Jamie Nguyen <j(a)jamielinux.com> -Date: Thu, 8 May 2014 18:50:26 +0100 -Subject: [PATCH] Do not use gzip feature of maxmin - ---- - tasks/uglify.js | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/tasks/uglify.js b/tasks/uglify.js -index e31d9b8..50fcaa5 100644 ---- a/tasks/uglify.js -+++ b/tasks/uglify.js -@@ -160,7 +160,7 @@ module.exports = function(grunt) { - } - - grunt.log.writeln('File ' + chalk.cyan(f.dest) + ' created: ' + -- maxmin(result.max, output, options.report === 'gzip')); -+ maxmin(result.max, output, false)); - }); - }); - }; --- -1.9.0 - diff --git a/nodejs-grunt-contrib-uglify.spec b/nodejs-grunt-contrib-uglify.spec index 4d85db5..f02ed93 100644 --- a/nodejs-grunt-contrib-uglify.spec +++ b/nodejs-grunt-contrib-uglify.spec @@ -2,43 +2,31 @@ %global enable_tests 1 -Name: nodejs-grunt-contrib-uglify -Version: 0.5.0 -Release: 4%{?dist} -Summary: Minify files with UglifyJS -License: MIT -Group: System Environment/Libraries -URL: https://github.com/gruntjs/grunt-contrib-uglify -Source0: http://registry.npmjs.org/grunt-contrib-uglify/-/grunt-contrib-uglify-%{v... -# The test files are not included in the npm tarball. -# Source1 is generated by running Source10, which pulls from the upstream -# version control repository. -Source1: tests-v%{version}.tar.bz2 -Source2: docs-v%{version}.tar.bz2 -Source10: dl-tests.sh -# wget https://raw.githubusercontent.com/gruntjs/grunt-contrib-uglify/6f5563bfc4... -Source20: Gruntfile-v%{version}.js - -# The gzip feature of maxmin requires js-zlib, which cannot be packaged for -# fedora<20 or rhel<7 so we shall disable the use of this feature where -# needed. -Patch0: %{name}-0.4.0-Do-not-use-gzip-feature-of-maxmin.patch - -BuildArch: noarch +Name: nodejs-grunt-contrib-uglify +Version: 0.11.1 +Release: 1%{?dist} +Summary: Minify files with UglifyJS +License: MIT +Group: System Environment/Libraries +URL: https://github.com/gruntjs/grunt-contrib-uglify +Source0: https://github.com/gruntjs/grunt-contrib-uglify/archive/v%{version}/grunt... +BuildArch: noarch + %if 0%{?fedora} >= 19 -ExclusiveArch: %{nodejs_arches} noarch +ExclusiveArch: %{nodejs_arches} noarch %else -ExclusiveArch: %{ix86} x86_64 %{arm} noarch +ExclusiveArch: %{ix86} x86_64 %{arm} noarch %endif BuildRequires: nodejs-packaging -BuildRequires: npm(grunt-cli) -BuildRequires: uglify-js - %if 0%{?enable_tests} BuildRequires: npm(chalk) +BuildRequires: npm(lodash) BuildRequires: npm(maxmin) +BuildRequires: npm(uglify-js) +BuildRequires: npm(uri-path) +BuildRequires: npm(grunt-cli) BuildRequires: npm(grunt-contrib-clean) BuildRequires: npm(grunt-contrib-internal) BuildRequires: npm(grunt-contrib-nodeunit) @@ -49,19 +37,9 @@ BuildRequires: npm(grunt-contrib-nodeunit) %prep -%setup -q -n package -%setup -q -T -D -a 1 -n package -%setup -q -T -D -a 2 -n package - -%if 0%{?fedora} < 21 || 0%{?rhel} < 7 -%patch0 -p1 -%endif - -cp -p %{SOURCE20} Gruntfile.js - -%nodejs_fixdep lodash '^3.10.1' -%nodejs_fixdep maxmin '~0.2' -%nodejs_fixdep uglify-js '~2.4' +%setup -q -n grunt-contrib-uglify-%{version} +%nodejs_fixdep lodash "^3.10.1" +%nodejs_fixdep maxmin "^0.2.0" %build @@ -72,23 +50,27 @@ cp -p %{SOURCE20} Gruntfile.js mkdir -p %{buildroot}%{nodejs_sitelib}/grunt-contrib-uglify cp -pr package.json tasks/ \ %{buildroot}%{nodejs_sitelib}/grunt-contrib-uglify - %nodejs_symlink_deps %if 0%{?enable_tests} %check %nodejs_symlink_deps --check -/usr/bin/grunt test +/usr/bin/grunt uglify +/usr/bin/grunt nodeunit %endif %files -%doc LICENSE-MIT README.md docs/ +%doc README.md CONTRIBUTING.md AUTHORS CHANGELOG docs/ +%license LICENSE-MIT %{nodejs_sitelib}/grunt-contrib-uglify %changelog +* Thu Feb 11 2016 Tom Hughes <tom(a)compton.nu> - 0.11.1-1 +- Update to 0.11.1 upstream release + * Thu Feb 04 2016 Fedora Release Engineering <releng(a)fedoraproject.org> - 0.5.0-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild diff --git a/sources b/sources index 9806344..397601d 100644 --- a/sources +++ b/sources @@ -1,3 +1 @@ -785cad118f6ada59f3f98cb40df1f28b docs-v0.5.0.tar.bz2 -9d331aec2ee97eb005155f7d0dc693e1 grunt-contrib-uglify-0.5.0.tgz -46d6cd9ce0d6bd5380a0525d48d91d14 tests-v0.5.0.tar.bz2 +9e039ab959739aaf40141fdd7b8fcad3 grunt-contrib-uglify-0.11.1.tar.gz -- cgit v0.11.2 http://pkgs.fedoraproject.org/cgit/nodejs-grunt-contrib-uglify.git/commit...

8 years, 3 months

Re: Yum repo compatibility

by Michael Schwendt

On Fri, 5 Nov 2004 16:05:00 +0100 (CET), Dag Wieers wrote: > > > http://www.fedora.us/wiki/RepositoryMixingProblems > > > > That page also explains why fedora.us cannot guarantee compatibility with > > other repositories, quoted below for completeness and as food for > > discussion. The paragraph is unchanged since April 25th, 2003. > Since fedora.us started without any packages and there were already a > number of existing repositories with a good amount of packages. The > fedora.us policy could have been to work together with existing > repositories and implement something that could have worked. Sorry that I won't participate in going back to very old threads from fedora-devel(a)fedora.us list, which were not fruitful. It's beyond my time. The list archives are still open. Everybody is free to skim over the several hundred relevant messages and look at the problem. Okay, I added my comments in this thread, but that's just because I'm subscribed to this list. There are a very few people (or maybe it's just one) who don't realize that I'm just a contributor. I'm not in charge of the policies and objectives. I'm not a fedora.us spokesman either. Gah! It's insane to think that, when I never ever claimed to be a spokesman. Fedora.us provides a system which allows community commitment, where I, as a member of the community, can contribute. Other contributors have noticed the possibility, too. On the contrary, when fedora.us was started, and even many months later, no other packaging project was ready to accept community commitment beyond private mails or mailing-lists. An environment, where competition between repositories dominates and crushes any attempts at working towards a higher common goal, is hostile instead of beneficial. Do we all have the same goal with extra packages? No, we don't. Not even with common libraries, I've been told. I understand that e.g. Matthias Saou didn't want to "give up" freshrpms.net in favour of maintaining his packages as part of a project that started as "Fedora Linux". But as could be read on the old fedora-devel list, the other contributors did not see a way to base their project on packages from an external repository, packages which are out of their control. > > * Users may also have any arbitrary mix of repositories, creating an > > unsupportable testing nightmare. > > Which is only true if you have 5 SPEC files resulting in 5 packages, as I > said there are other ways to reach the same goal and we've opted to have a > single SPEC file resulting (if necessary) into 5 packages. The next step > obviously is to look at why we still need 5 packages and how to merge the > lot. Why not take the route of Fedora Extras and extend Fedora Core with add-on packages, which to use as foundation for even more packages? A single easy-to-find place where to get extra packages instead of a multitude of repositories around the world. A single repository which CD manufacturers can mirror and burn onto CD/DVD. A single repository which to include and support directly from within Fedora Core. Why have many 3rd party repositories, which first extend Fedora Core and then extend eachother? Why not create Fedora Extras and then add complementry, special purpose 3rd party repositories, which depend on it? > I'm sure fedora.us, now that it has packages and is maturing, is working > at a slower pace than at the beginning. You can't just change direction > anymore if you have a large userbase. IMHO, the situation hasn't changed at all. The total number of package developers has increased. There are still new submissions added to the package requests queue. But the general willingness to adhere to the policies/guidelines and make _utilisable contributions_ (reviews, approvals, packages which don't fail to build) is still missing. The interest in getting packages accepted and included is there. But the willingness to team up with other developers is missing. -- Fedora Core release 2 (Tettnang) - Linux 2.6.9-1.2_FC2 loadavg: 0.06 0.14 0.07

19 years, 7 months

jkurik's meeting titled "F24 Alpha Readiness Meeting" ended in #fedora-meeting

by notifications＠fedoraproject.org

============================================ #fedora-meeting: F24 Alpha Readiness Meeting ============================================ Meeting started by jkurik at 19:00:10 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2016-03-17/f24-alpha-rea... . Meeting summary --------------- * Roll Call (jkurik, 19:00:25) * Purpose of this meeting (jkurik, 19:03:22) * Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well coordinated. (jkurik, 19:03:35) * LINK: https://fedoraproject.org/wiki/Release_Readiness_Meetings (jkurik, 19:03:37) * Current status (jkurik, 19:03:48) * Fedora 24 Alpha is No-Go (jkurik, 19:03:50) * Due to present blockers the Alpha release has been postponed (jkurik, 19:03:51) * The next Go/No-Go meeting is planned on Wednesday, March 23rd (jkurik, 19:03:53) * Design (jkurik, 19:04:45) * design team is good for alpha (jkurik, 19:06:17) * Infrastructure (jkurik, 19:06:55) * Infrastructure team is all set. There is a storage upgrade planned for alpha release day, but nirik is asking them to move it. (jkurik, 19:07:59) * Ambassadors (jkurik, 19:08:17) * Ambassadors have not discussed the readiness for Alpha, however each region have everything set. (jkurik, 19:10:34) * Documentation (jkurik, 19:10:56) * ACTION: jkurik to check offline whether the Documentation team is ready for F24 Alpha release (jkurik, 19:14:01) * FESCo (jkurik, 19:14:18) * FESCo sees no blockers and should be good to go... (jkurik, 19:15:26) * Fedora Engineering Manager (jkurik, 19:15:48) * Fedora Project Leader (jkurik, 19:18:07) * Fedora Engineering Manager (jkurik, 19:18:42) * Fedora Engineering Manager has no pending items in his area that would delay the release (jkurik, 19:19:43) * Fedora Project Leader (jkurik, 19:19:57) * Marketing (jkurik, 19:22:27) * no blockers from the releas but Marketing is trying to generate talking points of all the "new things" in F24 from the Editions and Spins.Workstation + Cloud should be set, but they still need to gather info from Server and the Spins. (jkurik, 19:24:32) * People having info about F24 Server changes are requested to contribute (jkurik, 19:25:09) * LINK: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.... (jkurik, 19:25:17) * ACTION: jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine (jflory7, 19:26:45) * QA (jkurik, 19:27:07) * QE is more or less on top of things. Alpha 1.5 test coverage is nearly complete, only missing Server tests. (jkurik, 19:28:33) * QE is doing a lot of work behind the scenes to keep the validation process working , but that should all be mostly done by now and stuff is...mostly working (jkurik, 19:29:23) * Release Engineering (jkurik, 19:30:03) * Documentation (jkurik, 19:33:13) * Documentation is just getting started. However there is no blocking issue for F24 Alpha at the moment. (jkurik, 19:36:49) * Translations (jkurik, 19:37:06) * Software String Freeze happened with Alpha freeze i.e. on 2016-03-08. The team have just started doing translations. (jkurik, 19:38:14) * The team sees no issues to go live with the Alpha (jkurik, 19:38:45) * Websites (jkurik, 19:39:37) * websites are all in a good shape, however the team needs to sync out with releng to fix paths and checksums (jkurik, 19:40:56) * The Websites team welcomes testers (jkurik, 19:41:46) * Scheduling of the Release time (jkurik, 19:42:12) * ACTION: jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng) (jkurik, 19:49:01) * ACTION: jkurik to follow up with release time via ML (jkurik, 19:49:23) * ACTION: jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC (jflory7, 19:49:39) * Fedora Project Leader (jkurik, 19:51:51) * Fedora Project Leader will make sure to be ready for next week with the annoucement (jkurik, 19:53:25) * Open floor (jkurik, 19:58:34) * CommOps (jkurik, 19:59:17) * CommOps has no blockers for F24. The team has a lot on ongoing tasks to improve some areas in time for the full release of F24.The major focus right now is looking at Onboarding and building a strategy for the different sub-projects across Fedora with Badges. (jkurik, 20:02:48) * Open floor (jkurik, 20:03:16) Meeting ended at 20:05:16 UTC. Action Items ------------ * jkurik to check offline whether the Documentation team is ready for F24 Alpha release * jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine * jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng) * jkurik to follow up with release time via ML * jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC Action Items, by person ----------------------- * jflory7 * jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine * jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC * jkurik * jkurik to check offline whether the Documentation team is ready for F24 Alpha release * jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng) * jkurik to follow up with release time via ML * mattdm * jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine * jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng) * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jkurik (120) * jflory7 (22) * zodbot (16) * stickster (14) * robyduck (14) * randomuser (8) * mattdm (8) * nirik (7) * pravins (6) * adamw (4) * potty (4) * mizmo (2) * b10n1k (1) * bowlofeggs (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot https://meetbot.fedoraproject.org/fedora-meeting/2016-03-17/f24-alpha-rea... -- You received this message due to your preference settings at https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...

8 years, 2 months

Re: automated rpm signing woes

by John Florian

I saw mention of FPO's rollout of new koji hubs and builders and am wondering does that mean integration is now possible again with sigul? If so, are any special side repos for special builds necessary? Is it best to deploy all of koji and sigul both on F35 or is there some other combination that works better or is required? John Florian On 2021-11-16 10:36, John Florian wrote: > On 2021-11-11 18:38, Kevin Fenzi wrote: >> On Thu, Nov 11, 2021 at 09:14:56AM -0500, John Florian wrote: >>> What is the recommended solution for this these days? What is >>> fedoraproject.org using? >> sigul. >> >>> I presently have a setup using Sigul on CentOS 7 but that's leading to my >>> current problem of being unable to upgrade anything. I can't find anything >>> workable with CentOS 8, meanwhile my Koji Hub is stuck at 1.21.1 because I'm >>> unaware of any newer builds via epel7. My Koji Builders are now stuck at >>> Fedora 33 because tasks fail if they have a newer version of Koji than the >>> Hub. >> koji has moved to python3, so I can't update epel7 koji until I move it >> to python3. There's still some prereq packages needed: >> https://bugzilla.redhat.com/show_bug.cgi?id=1862810 >> I keep wanting to work on this, but have had no time. ;( >> >> Perhaps with holidays up soon I can finally get to it. > > > Please let me know if I can be of any help. I do Python all day and > have been under the hood of koji a fair bit, but sigul much less. > Like everyone else, I'm always busy, but I like to help where I can, > even if it's just testing or writing docs. > > >>> My attempts at moving Sigul to CentOS 8 Stream have just led to one bug >>> after another using the only build I could find, located athttps://kojipkgs.fedoraproject.org/repos-dist/epel$releasever-infra/lat.... >>> I've fumbled my way through a few fixes and would be happy to contribute >>> when I can or, at least, report bugs. However, whenever I go to >>> https://pagure.io/sigul/, the apparent upstream for the project, I see the >>> last commit as 10 months ago, the last comment on any issue as 7 months ago, >>> no issues closed, no PRs merged. Is it dead? >> it's... sleeping. :) >> >> The primary developer, Patrick is busy on other stuff and hasn't had >> much time for it lately. > > That's fair. We all have fires to put out and I'm not going to tell > anyone which fire is bigger. I saw he's put a lot of work into > improvements and I've been hoping to benefit from those, but ... (below) > >> We are using a el8 version from our infra tags: >> https://koji.fedoraproject.org/koji/buildinfo?buildID=1668924 > I found that and have tried to use it, but without docs for migrating > the schema I wasn't sure how to populate the new keys.keytype field > that didn't exist back with sigul-0.101-1.el7. (The new field was > preventing a simple dump & load.) I thought I'd be clever and `sigul > new-key tempkey` to see what value a brand new key would have and > mimic that by editing a data dump from the old server before importing > into the new server. However, that failed, first with an error because > the variable key_name was undefined. I took a reasonable guess at a > patch for that problem but then ran into a unique constraint error > from the database. Since the project is "sleeping" I just now created > https://pagure.io/sigul/issue/15 to report this problem, but am > confounded how fpo is making this work. >> We don't have it in epel8 because python-nss was dropped there (and >> upstream). Patrick plans to re-write things so it doesn't use python-nss >> anymore, but hasn't yet done so. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1933855 >> tracks sigul in epel8. >> >> Sorry this is such a mess. ;( >> >> kevin > No apologies needed, it's FOSS. I do really appreciate the effort of > all involved and the difficulty of taming so many finicky parts to > harmonize. >> >> _______________________________________________ >> buildsys mailing list --buildsys(a)lists.fedoraproject.org >> To unsubscribe send an email tobuildsys-leave(a)lists.fedoraproject.org >> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives:https://lists.fedoraproject.org/archives/list/buildsys@lists.fed... >> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure > > John Florian > > _______________________________________________ > buildsys mailing list --buildsys(a)lists.fedoraproject.org > To unsubscribe send an email tobuildsys-leave(a)lists.fedoraproject.org > Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives:https://lists.fedoraproject.org/archives/list/buildsys@lists.fed... > Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

2 years, 3 months

Re: F26 Release Notes help needed

by Petr Bokoc

Correction: Turns out I remembered the registration process wrong. After you register in FAS, log in to pagure once, and then send me your nickname either in a mail (off-list) or on IRC - I have to add you to the "fedora-docs" Pagure group before you're able to assign issues to yourself. Apologies for the confusion. Petr On 06/22/2017 12:58 PM, Petr Bokoc wrote: > Hi everyone, let's revive this a little bit. > > We're going to have to produce some release notes for Fedora 26. I've > seen a few people on the list in the past mention they'd like to help, > and writing these is probably the best way to start with that. > > Note: There seems to be some confusion among newcomers: the Docs > Project doesn't maintain the Wiki, we take care (well, > occasionally...) of docs.fedoraproject.org. The guides published there > are currently written in DocBook XML[0], stored in Git repositories on > Pagure[1], and published using publican[2]. We have some vague-ish > plans to replace most of that with something more modern and > accessible to newcomers, since docbook really isn't user friendly, but > that's not going to happen for F26, so for this release we'll have to > stick with our current tools. > > Luckily, Release Notes in particular can be done in a way that avoids > DocBook, Git, and Publican altogether; they're short bits of text I or > someone else with experience can mark up and commit for you - you just > need find the right information and write them. > > The only thing you will need is a Pagure account - which is actually > your FAS account. If you don't have one yet, make one[3], make sure to > sign the CLA (Contributor License Agreement), log in to FAS, and apply > to join the "docs" group; I'll approve you once I see your > application. That should give you permissions to comment on Pagure > issues, which is where I'd like you to save what you write for release > notes unless we agree on some other approach. Also, I'm pretty sure > gaining membership in a group will allow you to edit the wiki, if > you're interested in that - wheee! > > If anyone has any questions, contact me on this mail or in > #fedora-docs on IRC; my time zone is CEST (UTC+2) and I'm online > mostly during afternoons on workdays. > > ===HOW DO I ACTUALLY CONTRIBUTE?=== > > Lately our main focus was covering Accepted Changes in our release > notes, since that's an easy and expansive source of information about > changes in each release. > > I took the liberty of opening an Issue on Pagure for every change; you > can see them here: https://pagure.io/release-notes/issues > > Contributors should: > > * go through the list and find something to write about that isn't > assigned to anyone yet (the rightmost column), open the issue and the > link to Wiki inside it > > * on the wiki page, you'll find three important pieces of info: 1) a > tracker bug in Bugzilla, 2) change owner(s) and 3) a short, hopefully > coherent description of the change. > > 1) the tracker bug is somewhat useful when trying to determine if > the change actually made it into the release. Don't count on it really > being there, in theory changes that are postponed or canceled should > be deleted from the wiki or at least marked somehow, but they often > aren't. Therefore, check the bug's status: if it's on ON_QA, VERIFIED, > RELEASE_PENDING or CLOSED-CURRENTRELEASE, it's safe to assume it did > make it in. If it has a status like NEW, ASSIGNED, or MODIFIED, > contact the owner before you start writing and ask them if the change > made it to F26. If it didn't, we shouldn't be writing about it. > > 2) the change owners are people you should contact a) to check if > the change still applies if required (see above), and b) when you > write a draft release note so they can check it for technical accuracy. > > 3) the description should give you some information so you can get > started on your draft. > > * once you have something you believe to be publishable, go back to > the Issue on pagure and save your text as a comment there. > > Some additional notes: > > * the current issue list (or the changeset wiki page) is by no means > exhaustive. You're very welcome to add more release notes for things > like changes in widely used components from kernel to firefox to > freeciv. Just make sure you're writing about a component version that > will be available in Fedora 26 upon release, not a previous version, > *not the latest upstream version*. It's common for Fedora to come out > with something like Firefox X, but on its website you can already > download version X+1 at the same time. We're writing this about > Fedora, so keep that in mind. The previous sentence also means that we > shouldn't be covering any third-party repos, proprietary drivers, etc. > - Fedora only. > > * there often are upstream release notes that are much more exhaustive > than what we would write, so use them. I'm talking about changes like > "upgrade Boost to 1.63" - Boost version 1.63 already has its own > release notes, and this change just means Fedora is using that > version. In that case, you can just write as much, maybe provide a > short list of the most important changes, and then link to Boost's > website for the full version, like we usually do[4]. > > * the current release date is July 11, so please, make sure you're > done two days before so I have time to convert everything. If you > can't make it, please send me an e-mail and drop (unassign) any issues > you can't do in time. There's no shame in backing out, we all have > other things to do, but please make sure someone can still pick it up. > > ===BUT PETR, HOW ARE WE GOING TO PUBLISH? WE STILL NEED THAT ANCIENT > PUBLICAN VERSION THAT ONLY RUNS ON A FEDORA RELEASE THAT CAN'T PUSH TO > PAGURE!=== > > Yeah, but we should be able to publish by building the website in the > VM like we used to until now, and then mounting the VM's storage on a > more modern system that can push and doing the last step that way. > > Good luck everyone, and again, ping or e-mail me if you have any > questions. > > Petr > > --- > [0] http://tdg.docbook.org/tdg/4.5/docbook.html > [1] https://pagure.io/group/fedora-docs > [2] https://jfearn.fedorapeople.org/en-US/Publican/ > [3] https://admin.fedoraproject.org/accounts/ > [4] > https://docs.fedoraproject.org/en-US/Fedora/25/html/Release_Notes/sect-Re... > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org -- Petr Bokoc (irc: pbokoc) Technical Writer Customer Content Services Red Hat Czech, s. r. o. Purkynova 99 612 45 Brno, Czech Republic

6 years, 11 months

Search results for query "contribute to wiki"