Re: Updating arc-theme and self introduction
Hello Martin, And welcome aboard! Before you can claim an orphaned package, you should first get someone to sponsor you into the packager group. The process you need to go through is documented here: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers Best of luck ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Fedocal] Reminder meeting : Modularity Team (weekly)
Dear all, You are kindly invited to the meeting: Modularity Team (weekly) on 2019-04-23 from 15:00:00 to 16:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Meeting of the Modularity Team. More information available at: [Modularity Team Docs](https://docs.pagure.org/modularity/) The agenda for the meeting is available as flagged tickets [in the Modularity repository](https://pagure.io/modularity/issues?status=Open=Meeting). Source: https://apps.fedoraproject.org/calendar/meeting/9480/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 30-20190422.n.1 compose check report
Missing expected images: Atomichost qcow2 x86_64 Atomichost raw-xz x86_64 Failed openQA tests: 2/146 (x86_64), 1/2 (arm) ID: 389227 Test: x86_64 Server-dvd-iso server_cockpit_default URL: https://openqa.fedoraproject.org/tests/389227 ID: 389273 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/389273 ID: 389276 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/389276 Soft failed openQA tests: 3/24 (i386), 3/146 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 389236 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/389236 ID: 389237 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/389237 ID: 389246 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/389246 ID: 389255 Test: x86_64 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/389255 ID: 389256 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/389256 ID: 389260 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/389260 Passed openQA tests: 136/146 (x86_64), 21/24 (i386) Skipped non-gating openQA tests: 6 of 172 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 30 compose report: 20190422.n.1 changes
OLD: Fedora-30-20190421.n.0 NEW: Fedora-30-20190422.n.1 = SUMMARY = Added images:1 Dropped images: 5 Added packages: 0 Dropped packages:0 Upgraded packages: 7 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 43.26 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 102.26 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Astronomy_KDE live i386 Path: Labs/i386/iso/Fedora-Astronomy_KDE-Live-i386-30-20190422.n.1.iso = DROPPED IMAGES = Image: Python_Classroom vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-30-20190421.n.0.x86_64.vagrant-libvirt.box Image: Python_Classroom vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-30-20190421.n.0.x86_64.vagrant-virtualbox.box Image: Cinnamon live x86_64 Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-30-20190421.n.0.iso Image: Games live i386 Path: Labs/i386/iso/Fedora-Games-Live-i386-30-20190421.n.0.iso Image: LXDE raw-xz armhfp Path: Spins/armhfp/images/Fedora-LXDE-armhfp-30-20190421.n.0-sda.raw.xz = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: appstream-data-30-5.fc30 Old package: appstream-data-30-4.fc30 Summary: Fedora AppStream metadata RPMs: appstream-data Size: 16.92 MiB Size change: 47.79 KiB Changelog: * Thu Apr 18 2019 Kalev Lember - 30-5 - New metadata version Package: fedora-obsolete-packages-30-40 Old package: fedora-obsolete-packages-30-35 Summary: A package to obsolete retired packages RPMs: fedora-obsolete-packages Size: 53.49 KiB Size change: 1.02 KiB Changelog: * Sun Apr 14 2019 Miro Hron??ok - 30-36 - Obsolete python2-testify < 0.11.0-13 * Mon Apr 15 2019 Miro Hron??ok - 30-37 - Obsolete python2-cinderclient < 3.5.0-2 * Mon Apr 15 2019 Kevin Fenzi - 30-38 - Obsolete mongodb < 4.0.3-3 (#1700073) * Tue Apr 16 2019 Miro Hron??ok - 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) * Tue Apr 16 2019 Orion Poplawski - 30-40 - Obsolete python2-envisage (#1700310) Package: fedora-release-30-1 Old package: fedora-release-30-0.26 Summary: Fedora release files RPMs: fedora-release fedora-release-cinnamon fedora-release-cloud fedora-release-common fedora-release-container fedora-release-coreos fedora-release-iot fedora-release-kde fedora-release-matecompiz fedora-release-server fedora-release-silverblue fedora-release-snappy fedora-release-soas fedora-release-workstation fedora-release-xfce Size: 173.81 KiB Size change: 680 B Changelog: * Thu Apr 18 2019 Mohan Boddu - 30-1 - Setup for F30 Final Package: fedora-repos-30-1 Old package: fedora-repos-30-0.6 Summary: Fedora package repositories RPMs: fedora-gpg-keys fedora-repos fedora-repos-ostree fedora-repos-rawhide Size: 127.54 KiB Size change: 108 B Changelog: * Thu Apr 18 2019 Mohan Boddu - 30-1 - Setup for F30 Final Package: gnome-shell-3.32.1-1.fc30 Old package: gnome-shell-3.32.0-1.fc30 Summary: Window management and application launching for GNOME RPMs: gnome-shell Size: 8.38 MiB Size change: 9.88 KiB Changelog: * Sat Mar 23 2019 Phil Wyett - 3.32.0-2 - Update source URL - Add gcc BuildRequires - Update versions required for gjs and mutter * Wed Apr 17 2019 Adam Williamson - 3.32.0-3 - Backport MR #463 and MR #494 to fix a couple of bugs Resolves: #1696270 Resolves: #1690429 * Wed Apr 17 2019 Florian M??llner - 3.32.1-1 - Update to 3.32.1 Package: gnome-shell-extensions-3.32.1-1.fc30 Old package: gnome-shell-extensions-3.32.0-1.fc30 Summary: Modify and extend GNOME Shell functionality and behavior RPMs: gnome-classic-session gnome-shell-extension-apps-menu gnome-shell-extension-auto-move-windows gnome-shell-extension-common gnome-shell-extension-drive-menu gnome-shell-extension-launch-new-instance gnome-shell-extension-native-window-placement gnome-shell-extension-places-menu gnome-shell-extension-screenshot-window-sizer gnome-shell-extension-user-theme gnome-shell-extension-window-list gnome-shell-extension-windowsNavigator gnome-shell-extension-workspace-indicator Size: 326.74 KiB Size change: -1.98 KiB Changelog: * Wed Apr 17 2019 Florian M??llner - 3.32.1-1 - Update to 3.32.1 Package: mutter-3.32.1-1.fc30 Old package: mutter-3.32.0-2.fc30 Summary: Window and compositing manager based on Clutter RPMs: mutter mutter-devel mutter-tests Size: 17.29 MiB Size change: 44.79 KiB Changelog: * Tue Apr 16 2019 Adam Williamson - 3.32.0-3 - Rebuild with Meson fix for #1699099 * Wed Apr 17 2019 Adam Williamson - 3.3
Re: Maintainer test instances
> On Apr 22, 2019, at 12:58 PM, Stephen John Smoogen wrote: > > > >> On Mon, 22 Apr 2019 at 11:37, Richard Shaw wrote: >>> On Mon, Apr 22, 2019 at 10:15 AM Kevin Fenzi wrote: >> >>> On 4/16/19 11:43 AM, Richard Shaw wrote: >>> > Also, pertinent to the main topic... Any chance of getting a EL 8 test >>> > instance? >>> >>> I'd prefer not to put up a beta instance that gets no updates, but >>> perhaps we can figure something out. >> >> It would be nice in order to start troubleshooting builds since COPR has EL8 >> available. >> > > Yes it would be. However these systems are set up and maintained as a > secondary function of our primary work. We have not had time to set up > ansible roles for EL-8 and do not currently have time to deal with 'oh wait > this doesn't work? why?' problems on a beta. We are waiting until RHEL-8 > General Availability to evaluate how long that will take and begin. You can > download and install the RHEL-8 beta into a virtual machine of your choosing > in the mean time. That beta is missing a *lot* of common compilation dependencies. doxygen was the first I personally ran into, but the python modules are pretty sparse, too. > > >> Thanks, >> Richard >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > -- > Stephen J Smoogen. > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1698803] Upgrade perl-File-Slurp to 9999.27
https://bugzilla.redhat.com/show_bug.cgi?id=1698803 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-File-Slurp-.27-1.f ||c29 Resolution|--- |ERRATA Last Closed||2019-04-22 21:35:17 --- Comment #5 from Fedora Update System --- perl-File-Slurp-.27-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: I plan to remove python2-pep8
[ Removed pylast and ovirt-guest-agent emails from Cc. ] On Mon, Apr 22, 2019 at 17:53:03 +0200, Miro Hrončok wrote: > Maintainers by package: > cachedir mathstuf > cmdtest salimma > genbackupdatasalimma > python-cliappsalimma > python-larch salimma These are all packages from obnam which is now retired/EOL. I think larch and genbackupdata can probably be retired (though maybe others find genbackupdata useful?). cachedir is still useful and uses cliapp. cmdtest *could* be dropped; it is only used for the testing in cachedir (as is pep8), but running the testsuite is nice-to-have. --Ben ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers
Hello, Kevin Fenzi. Mon, 22 Apr 2019 11:22:27 -0700 you wrote: > If you are in the packager group you can still push via ssh for now. In time, > we are planning to deprecate this. And this is not good. Received HTTPS tokens can be easily stolen. SSH keys using hardware tokens much more secure. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers
Hi Simo, On Mon, 22 Apr 2019 at 20:39, Simo Sorce wrote: > > Any reason why oidc is required instead of a simple GSSAPI (via > mod_auth_gssapi) ? > GSSAPI authentication won't require a graphical session to work. The main reasons for going with OIDS rather than GSSAPI are: 1. User support: we have had a *lot* of contributors that had issues using GSSAPI for Fedora, often because they have older or employer-specific krb configurations: a lot of them are for example missing the "includedir /etc/krb5.conf.d" and the dns_kdc_lookup options. One other very common occurrence are the dns_canonicalize_hostname and rdns options: the Fedora defaults for these options are required for the Fedora Infra krb5 to work, but a lot of employers set (or even require) these to be set to "true". Fedora Infra is unable to work with these options set to true, because we have a lot of nodes for which we do not control recursive DNS, in addition to the fact that we have the exact same set of entry points for all services, which means reverse DNS is useless. 2. With the upcoming account system change (to be backed by FreeIPA) our plan is to start requiring 2 factor auth for some groups (primarily the system administrators, it'll be opt-in for other users), and then we want to be able to enforce using the same 2fa tokens for any access. The 2FA scheme that we are solely planning to support is U2F/FIDO2, and to the best of my knowledge there has so far not been any work on integrating this with any krb5 server. The current plan is to integrate the 2FA flow into the identity provider, and have it enforce and check the tokens. Using OpenID Connect for this login would mean that we get the 2fa enforcement "for free". Also, please note that there are concrete plans to lift the requirement for a graphical session for OpenID Connect tokens, but that would be part of the same authentication work. Patrick ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: PySide2 Python packaging questions
On Mon, Apr 22, 2019 at 06:14:15PM +0200, Miro Hrončok wrote: > On 18. 04. 19 18:17, Richard Shaw wrote: > >I'm working on packaging PySide2 for Fedora[1] and have a couple of > >questions... > > > >*** Also, I could use an experienced python packager to do the review! *** > > > >1. Should the %python_provide macro be applied to > >python--devel packages? Or just for the main python > >module package? > > Everything that is called python2-foo or python3-foo should be > accompanied by %python_provide. it doesn't matter whether it is > "main python module package" or not. > > If the package is called python--devel (sometimes happens > if it is Python version agnostic) -> no need for %python_provide. > > If the package is called python3--devel, %python_provide should be > used. > > >2. Do I need to filter requires/provides for C python libraries if > >their not private? > > I always understand it that provided libxxx.so.so.X.Y() are intended > to be used by linkers directly. E.g. Python modules should not > provide libxxx.cpython-37m-x86_64-linux-gnu.so or similar. tl;dr: the Provides in question is harmless and/or correct and should be left in. The problem seems to be caused by the location of the module: > /usr/lib64/libshiboken2.cpython-37m-x86_64-linux-gnu.so.5.12 which leads to Provides: libshiboken2.cpython-37m-x86_64-linux-gnu.so.5.12()(64bit). IIUC, the module is compiled using the python stable ABI (PEP 384). Normally, cpython modules live under a python-version-specific directory (e.g. /usr/lib64/python3.8/site-packages/). But with the stable ABI, no version-specific directory is appropriate, and thus the library was put in the general library location. This means that the default rpm filters to ignore cpython modules don't work. The module that is loaded from python is at /usr/lib64/python3.7/site-packages/shiboken2/shiboken2.cpython-37m-x86_64-linux-gnu.so, and it links to /usr/lib64/libshiboken2.cpython-37m-x86_64-linux-gnu.so.5.12. I assume this split is done to share the code. The binary in /usr/lib64 is 270k, and the one in site-packages is 20k. I think this split and using /usr/lib64 is a reasonable solution. It could even be argued that the Provides is correct. Despite the strange name, the module in /usr/lib64 is a shared library that could be used (linked to) by multiple python-version-specific modules. Also, because of the "cpython-37m-x86_64-linux-gnu" tag there is no possibility to mistake this for any normal library. (That said, we are unlikely to make any use of this split in Fedora. We generally have just one version of python3, and further packaging work would be needed to make the whole thing work anyway. But I don't see any reason to deviate from upstream and remove the split.) Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Understanding Fedora's use of systemd presets and packaging requirements
On Mon, Apr 22, 2019 at 09:31:19AM -0700, Adam Williamson wrote: > On Mon, 2019-04-22 at 09:25 -0700, Adam Williamson wrote: > > On Sat, 2019-04-20 at 07:59 +, Zbigniew Jędrzejewski-Szmek wrote: > > > On Fri, Apr 19, 2019 at 04:35:54PM -0400, John Florian wrote: > > > > I'm generally familiar with how systemd presets work but I'm at a > > > > bit of loss as to how part of all the magic works. To best explain > > > > my confusion, let me say that I make a customized live spin of > > > > Fedora and I have a package we'll call "my-dist" which is similar in > > > > nature to the "fedora-release" package in that it provides a custom > > > > preset file. I still use fedora-release because this spin is not > > > > *that* customized, so it's best to think of this as an extension. I > > > > have another package we'll call "my-service" which has a systemd > > > > service unit file and all the usual %systemd_post, etc. macros. > > > > When I boot my live spin I find that my-service is not enabled > > > > despite the preset in my-dist. I can "systemctl preset-all" to > > > > rectify this so I believe most requirements are correct. I do see > > > > that livemedia-creator installs my-service *before* it installs > > > > my-dist so if the %systemd_post is called as each rpm is installed > > > > that would explain my problem because my custom preset isn't present > > > > yet. > > > > > > > > How does Fedora itself accomplish this??? I don't see every package > > > > providing a service having a dependency on fedora-release to address > > > > this ordering issue. I can certainly stick the "systemctl > > > > preset-all" into the %post of my kickstart as final cleanup, but > > > > that feels dirty and wrong. Similarly, I don't wish to have to have > > > > a "Requires: my-dist" in every one of "my-service" and other > > > > packages like it. I've scrutinized fedora-release.spec and didn't > > > > see anything all that different than what I have in my-dist. > > > > > > systemd.rpm does preset-all when it is installed, so it is enough > > > that systemd.rpm is installed after fedora-release-common.rpm. > > > fedora-release-common is required by setup.rpm, so it is installed > > > early. But you raise a good point — I don't see any *explicit* > > > ordering chain between fedora-release-common and systemd. > > > > > > There is no need to order individual rpms against either > > > fedora-release-common and other packages providing presets or > > > systemd. The only thing that is necessary is for systemd.rpm to be > > > installed after all presets. If that is satisfied, packages proving > > > services can be installed both earlier and later and the effect > > > (in the sense of service enablement) should be identical. > > > > AIUI, the design is that any package that *ships a preset* should run > > systemctl preset on it in its scriptlets (there should be guidelines > > for this somewhere but I can't find them right now). There's no explicitly stated rule, afaik, but scriptlets [1] document %systemd_requires and scriptlets are part of the guidelines. [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_scriptlets > > However, there's a > > loophole here in that if any package that ships a preset gets ordered > > before systemd itself during install, its attempt to run 'systemctl > > preset' will obviously fail. This is why we run 'preset-all' in the > > systemd package scriptlets: to apply the presets for any packages which > > were already installed. It's not intended that all other packages can > > *rely* on the call in systemd's scripts. > > BTW if you're wondering "why not just make sure everything that ships a > preset gets installed after systemd"...sadly there are some awkward > cases that make that not practical, basically 'systemd depends on > something that installs a preset' or 'systemd depends on something that > depends on something that installs a preset'. I think that the attempt to install all packages that provide services after systemd is misguided / outdated. As you say, doing this comprehensively isn't possible because of circular deps. Furthermore, since you restored the call to preset-all, there is no point. The effect is the same in either order. I want to open an FPC ticket to change the guidelines to not require any dependency on systemd for packages that simply provide a service file. Things are complicated by the fact that packages might require systemd for different reasons, e.g. use some systemd helper in installation scriptlets. So we can't simply drop the dependency and ordering on systemd everywhere, but I think we could do it in many places. This will remove some noise, shorten our spec files a bit, and give rpm more freedom to order package installation according to requirements (there will be less requirements, so less loops). I was planning to start the discussion on this after F30 is released, but since we're already discussing this, I'll try to
[Bug 1699247] perl-IO-Socket-SSL-2.056-1.fc28 FTBFS: tests fail due to expired certificates
https://bugzilla.redhat.com/show_bug.cgi?id=1699247 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-IO-Socket-SSL-2.066-1. ||fc28 Resolution|--- |ERRATA Last Closed||2019-04-22 18:42:17 --- Comment #3 from Fedora Update System --- perl-IO-Socket-SSL-2.066-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers
Any reason why oidc is required instead of a simple GSSAPI (via mod_auth_gssapi) ? GSSAPI authentication won't require a graphical session to work. Simo. On Mon, 2019-04-22 at 11:22 -0700, Kevin Fenzi wrote: > Greetings. > > I'm happy to announce that you can now use https to push commits > > to src.fedoraproject.org. You will need to use 'fedpkg clone -a' > > and have a session with a running browser to do the initial > authentication, but after that everything should be transparent. > > > Users who are not part of the 'packager' group can now use > this to push to forks of projects to create pull requests. > > Please see https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits > > for more details. > > We hope this support will allow more community members to > contribute along with allowing more flexibility to maintainers > who don't always have SSH access. > > kevin > > ___ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Simo Sorce Sr. Principal Software Engineer Red Hat, Inc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers
Greetings. I'm happy to announce that you can now use https to push commits to src.fedoraproject.org. You will need to use 'fedpkg clone -a' and have a session with a running browser to do the initial authentication, but after that everything should be transparent. Users who are not part of the 'packager' group can now use this to push to forks of projects to create pull requests. Please see https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits for more details. We hope this support will allow more community members to contribute along with allowing more flexibility to maintainers who don't always have SSH access. kevin signature.asc Description: OpenPGP digital signature ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
announcing HTTPS pushing to dist-git/src.fedoraproject.org for packagers and non-packagers
Greetings. I'm happy to announce that you can now use https to push commits to src.fedoraproject.org. You will need to use 'fedpkg clone -a' and have a session with a running browser to do the initial authentication, but after that everything should be transparent. Users who are not part of the 'packager' group can now use this to push to forks of projects to create pull requests. Please see https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits for more details. We hope this support will allow more community members to contribute along with allowing more flexibility to maintainers who don't always have SSH access. kevin signature.asc Description: OpenPGP digital signature ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Updating arc-theme and self introduction
Hi, I'm a french student learning IT in high school and I wanted to get involved into Fedora's packaging process so i started to read the guidelines and tried to update an orphaned package. This package is arc-theme and i've done the .spec and the SRPM successfully : https://grudler.eu/Fedora/arc-theme/arc-theme-20190330-1.fc30.src.rpm https://grudler.eu/Fedora/arc-theme/arc-theme.spec I want to know if i have to write an issue on the releng's page or if i need to do something else to being mentored and my new package being checked. Martin GRUDLER___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Understanding Fedora's use of systemd presets and packaging requirements
On 4/22/19 9:25 AM, Adam Williamson wrote: AIUI, the design is that any package that *ships a preset* should run systemctl preset on it in its scriptlets (there should be guidelines for this somewhere but I can't find them right now). However, there's a loophole here in that if any package that ships a preset gets ordered before systemd itself during install, its attempt to run 'systemctl preset' will obviously fail. This is why we run 'preset-all' in the systemd package scriptlets: to apply the presets for any packages which were already installed. It's not intended that all other packages can *rely* on the call in systemd's scripts. So, basically: if you're making a package that includes presets, run 'systemctl preset' on the presets it ships in its scripts. Not 'preset- all', but run it specifically per preset that you ship. Couldn't you run the preset script in a %posttrans block to ensure everything is installed? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Maintainer test instances
On Mon, 22 Apr 2019 at 11:37, Richard Shaw wrote: > On Mon, Apr 22, 2019 at 10:15 AM Kevin Fenzi wrote: > >> On 4/16/19 11:43 AM, Richard Shaw wrote: >> > Also, pertinent to the main topic... Any chance of getting a EL 8 test >> > instance? >> >> I'd prefer not to put up a beta instance that gets no updates, but >> perhaps we can figure something out. >> > > It would be nice in order to start troubleshooting builds since COPR has > EL8 available. > > Yes it would be. However these systems are set up and maintained as a secondary function of our primary work. We have not had time to set up ansible roles for EL-8 and do not currently have time to deal with 'oh wait this doesn't work? why?' problems on a beta. We are waiting until RHEL-8 General Availability to evaluate how long that will take and begin. You can download and install the RHEL-8 beta into a virtual machine of your choosing in the mean time. > Thanks, > Richard > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora Rawhide-20190422.n.0 compose check report
Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Compose FAILS proposed Rawhide gating check! 2 of 47 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 8/137 (x86_64), 4/24 (i386), 1/2 (arm) ID: 388827 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/388827 ID: 388834 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/388834 ID: 388859 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/388859 ID: 388860 Test: x86_64 Workstation-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/388860 ID: 388862 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/388862 ID: 388863 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/388863 ID: 388876 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/388876 ID: 388878 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/388878 ID: 388879 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/388879 ID: 388898 Test: x86_64 universal install_updates_img_local URL: https://openqa.fedoraproject.org/tests/388898 ID: 388942 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/388942 ID: 388947 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/388947 ID: 388967 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/388967 Soft failed openQA tests: 2/24 (i386), 8/137 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 388839 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/388839 ID: 388840 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/388840 ID: 388849 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/388849 ID: 388858 Test: x86_64 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/388858 ID: 388890 Test: x86_64 universal upgrade_minimal_64bit URL: https://openqa.fedoraproject.org/tests/388890 ID: 388892 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/388892 ID: 388893 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/388893 ID: 388894 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/388894 ID: 388929 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/388929 ID: 388950 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/388950 Passed openQA tests: 121/137 (x86_64), 18/24 (i386) Skipped non-gating openQA tests: 1 of 163 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Understanding Fedora's use of systemd presets and packaging requirements
On Mon, 2019-04-22 at 09:25 -0700, Adam Williamson wrote: > On Sat, 2019-04-20 at 07:59 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, Apr 19, 2019 at 04:35:54PM -0400, John Florian wrote: > > > I'm generally familiar with how systemd presets work but I'm at a > > > bit of loss as to how part of all the magic works. To best explain > > > my confusion, let me say that I make a customized live spin of > > > Fedora and I have a package we'll call "my-dist" which is similar in > > > nature to the "fedora-release" package in that it provides a custom > > > preset file. I still use fedora-release because this spin is not > > > *that* customized, so it's best to think of this as an extension. I > > > have another package we'll call "my-service" which has a systemd > > > service unit file and all the usual %systemd_post, etc. macros. > > > When I boot my live spin I find that my-service is not enabled > > > despite the preset in my-dist. I can "systemctl preset-all" to > > > rectify this so I believe most requirements are correct. I do see > > > that livemedia-creator installs my-service *before* it installs > > > my-dist so if the %systemd_post is called as each rpm is installed > > > that would explain my problem because my custom preset isn't present > > > yet. > > > > > > How does Fedora itself accomplish this??? I don't see every package > > > providing a service having a dependency on fedora-release to address > > > this ordering issue. I can certainly stick the "systemctl > > > preset-all" into the %post of my kickstart as final cleanup, but > > > that feels dirty and wrong. Similarly, I don't wish to have to have > > > a "Requires: my-dist" in every one of "my-service" and other > > > packages like it. I've scrutinized fedora-release.spec and didn't > > > see anything all that different than what I have in my-dist. > > > > systemd.rpm does preset-all when it is installed, so it is enough > > that systemd.rpm is installed after fedora-release-common.rpm. > > fedora-release-common is required by setup.rpm, so it is installed > > early. But you raise a good point — I don't see any *explicit* > > ordering chain between fedora-release-common and systemd. > > > > There is no need to order individual rpms against either > > fedora-release-common and other packages providing presets or > > systemd. The only thing that is necessary is for systemd.rpm to be > > installed after all presets. If that is satisfied, packages proving > > services can be installed both earlier and later and the effect > > (in the sense of service enablement) should be identical. > > AIUI, the design is that any package that *ships a preset* should run > systemctl preset on it in its scriptlets (there should be guidelines > for this somewhere but I can't find them right now). However, there's a > loophole here in that if any package that ships a preset gets ordered > before systemd itself during install, its attempt to run 'systemctl > preset' will obviously fail. This is why we run 'preset-all' in the > systemd package scriptlets: to apply the presets for any packages which > were already installed. It's not intended that all other packages can > *rely* on the call in systemd's scripts. BTW if you're wondering "why not just make sure everything that ships a preset gets installed after systemd"...sadly there are some awkward cases that make that not practical, basically 'systemd depends on something that installs a preset' or 'systemd depends on something that depends on something that installs a preset'. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Understanding Fedora's use of systemd presets and packaging requirements
On Sat, 2019-04-20 at 07:59 +, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Apr 19, 2019 at 04:35:54PM -0400, John Florian wrote: > > I'm generally familiar with how systemd presets work but I'm at a > > bit of loss as to how part of all the magic works. To best explain > > my confusion, let me say that I make a customized live spin of > > Fedora and I have a package we'll call "my-dist" which is similar in > > nature to the "fedora-release" package in that it provides a custom > > preset file. I still use fedora-release because this spin is not > > *that* customized, so it's best to think of this as an extension. I > > have another package we'll call "my-service" which has a systemd > > service unit file and all the usual %systemd_post, etc. macros. > > When I boot my live spin I find that my-service is not enabled > > despite the preset in my-dist. I can "systemctl preset-all" to > > rectify this so I believe most requirements are correct. I do see > > that livemedia-creator installs my-service *before* it installs > > my-dist so if the %systemd_post is called as each rpm is installed > > that would explain my problem because my custom preset isn't present > > yet. > > > > How does Fedora itself accomplish this??? I don't see every package > > providing a service having a dependency on fedora-release to address > > this ordering issue. I can certainly stick the "systemctl > > preset-all" into the %post of my kickstart as final cleanup, but > > that feels dirty and wrong. Similarly, I don't wish to have to have > > a "Requires: my-dist" in every one of "my-service" and other > > packages like it. I've scrutinized fedora-release.spec and didn't > > see anything all that different than what I have in my-dist. > > systemd.rpm does preset-all when it is installed, so it is enough > that systemd.rpm is installed after fedora-release-common.rpm. > fedora-release-common is required by setup.rpm, so it is installed > early. But you raise a good point — I don't see any *explicit* > ordering chain between fedora-release-common and systemd. > > There is no need to order individual rpms against either > fedora-release-common and other packages providing presets or > systemd. The only thing that is necessary is for systemd.rpm to be > installed after all presets. If that is satisfied, packages proving > services can be installed both earlier and later and the effect > (in the sense of service enablement) should be identical. AIUI, the design is that any package that *ships a preset* should run systemctl preset on it in its scriptlets (there should be guidelines for this somewhere but I can't find them right now). However, there's a loophole here in that if any package that ships a preset gets ordered before systemd itself during install, its attempt to run 'systemctl preset' will obviously fail. This is why we run 'preset-all' in the systemd package scriptlets: to apply the presets for any packages which were already installed. It's not intended that all other packages can *rely* on the call in systemd's scripts. So, basically: if you're making a package that includes presets, run 'systemctl preset' on the presets it ships in its scripts. Not 'preset- all', but run it specifically per preset that you ship. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Review swap: easy library needed for new supertuxkart
See subject. Willing to review one of yours if you like. https://bugzilla.redhat.com/show_bug.cgi?id=1701995 -- Gwyn Ciesla she/her/hers in your fear, seek only peace in your fear, seek only love -d. bowie Sent with ProtonMail Secure Email. signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 52 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced guacamole-server-1.0.0-1.el6 31 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-62f9745b71 drupal7-7.65-1.el6 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-73e99f4a82 python34-3.4.10-1.el6 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9f732040bd python3-jinja2-2.8.1-2.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing libmediainfo-18.12-3.el6 Details about builds: libmediainfo-18.12-3.el6 (FEDORA-EPEL-2019-bd4638e5a3) Library for supplies technical and tag information about a video or audio file Update Information: Fix CVE-2019-11372 ChangeLog: * Mon Apr 22 2019 Vasiliy N. Glazov - 18.12-3 - Fix CVE-2019-11372 * Fri Feb 1 2019 Fedora Release Engineering - 18.12-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild References: [ 1 ] Bug #1701849 - CVE-2019-11372 CVE-2019-11373 libmediainfo: various flaws [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1701849 [ 2 ] Bug #1701847 - CVE-2019-11372 CVE-2019-11373 libmediainfo: various flaws [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=1701847 ___ epel-devel mailing list -- epel-de...@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-de...@lists.fedoraproject.org
Re: PySide2 Python packaging questions
On 18. 04. 19 18:17, Richard Shaw wrote: I'm working on packaging PySide2 for Fedora[1] and have a couple of questions... *** Also, I could use an experienced python packager to do the review! *** 1. Should the %python_provide macro be applied to python--devel packages? Or just for the main python module package? Everything that is called python2-foo or python3-foo should be accompanied by %python_provide. it doesn't matter whether it is "main python module package" or not. If the package is called python--devel (sometimes happens if it is Python version agnostic) -> no need for %python_provide. If the package is called python3--devel, %python_provide should be used. 2. Do I need to filter requires/provides for C python libraries if their not private? I always understand it that provided libxxx.so.so.X.Y() are intended to be used by linkers directly. E.g. Python modules should not provide libxxx.cpython-37m-x86_64-linux-gnu.so or similar. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
I plan to remove python2-pep8
Hey. pep8 is no longer released upstream and its successor is called pycodestyle. I plan to retire python-pep8, as tracked in [1], however there are still too many consumers of python3-pep8. On the other hand, python2-pep8 is only buildrequired by: cachedir - already FTBFS, not dependent upon genbackupdata - already FTBFS, fails to install, not dependent upon ovirt-guest-agent - already FTBFS, not dependent upon outside of subpackages pylast - python2-pylast is not dependent upon python-cliapp - python2-cliapp is required by: cachedir cmdtest - FTBFS, fails to install, required by: cachedir genbackupdata python-larch - FTBFS, not dependent upon outside of subpackages genbackupdata python-larch Maintainers by package: cachedir mathstuf cmdtest salimma genbackupdatasalimma ovirt-guest-agentevilissimo nyoxi pylast peter python-cliappsalimma python-larch salimma Packages by maintainer: evilissimo ovirt-guest-agent mathstuf cachedir nyoxi ovirt-guest-agent peter pylast salimmacmdtest genbackupdata python-cliapp python-larch Would you like to take python2-pep8? I'd advice against, please update to Python 3 and/or pycodestyle instead. This is my attempt to follow [2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1667200 [2] https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Process_for_abandoning_Python_2_subpackages -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Maintainer test instances
On Mon, Apr 22, 2019 at 10:15 AM Kevin Fenzi wrote: > On 4/16/19 11:43 AM, Richard Shaw wrote: > > Also, pertinent to the main topic... Any chance of getting a EL 8 test > > instance? > > I'd prefer not to put up a beta instance that gets no updates, but > perhaps we can figure something out. > It would be nice in order to start troubleshooting builds since COPR has EL8 available. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 250 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 58 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2 tor-0.3.5.8-1.el7 52 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9c2c40e3df guacamole-server-1.0.0-1.el7 31 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-317c9a2f81 drupal7-7.65-1.el7 26 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 24 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f1efad2982 aria2-1.34.0-4.el7 18 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd afflib-3.7.18-2.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-77190f3ef7 python34-3.4.10-1.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8395a0247 transmission-2.94-6.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-6ea040e59b hostapd-2.7-1.el7 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ae064347d8 python3-jinja2-2.8.1-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing hub-2.11.2-1.el7 libmediainfo-18.12-3.el7 pam_radius-1.4.0-4.el7 Details about builds: hub-2.11.2-1.el7 (FEDORA-EPEL-2019-be1883503f) A command-line wrapper for git with github shortcuts Update Information: Update to hub 2.11.1 * Fix writing over existing cache files in hub api * Allow repository names that start with a - character * List api among custom hub commands in help * Fix compatibility with git when run with no arguments: hub --git-dir=.git * Fix issue/PR --format %L output in no-color mode * Create draft pull requests with hub pull-request --draft * Fix non-draft pull requests for certain repositories ChangeLog: * Mon Apr 22 2019 Stephen Gallagher - 2.11.2-1 - Update to 2.11.2 - Avoid crash in hub remote argument parsing - Fix `hub -C mydir merge ` by propagating global git arguments to Before/After chains - Preserve tilde ~ character in man pages * Fri Mar 29 2019 Stephen Gallagher - 2.11.1-1 - Update to 2.11.1 - Fix compatibility with git when run with no arguments: hub --git-dir=.git - Fix issue/PR --format %L output in no-color mode - Create draft pull requests with hub pull-request --draft - Fix non-draft pull requests for certain repositories * Thu Mar 28 2019 Stephen Gallagher - 2.10.1-1 - Update to 2.10.1 - Fix writing over existing cache files in hub api - Allow repository names that start with a - character - List api among custom hub commands in help libmediainfo-18.12-3.el7 (FEDORA-EPEL-2019-7fc4459823) Library for supplies technical and tag information about a video or audio file Update Information: Fix CVE-2019-11372 ChangeLog: * Mon Apr 22 2019 Vasiliy N. Glazov - 18.12-3 - Fix CVE-2019-11372 * Fri Feb 1 2019 Fedora Release Engineering - 18.12-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild References: [ 1 ] Bug #1701849 - CVE-2019-11372 CVE-2019-11373 libmediainfo: various flaws [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1701849 [ 2 ] Bug #1701847 - CVE-2019-11372 CVE-2019-11373 libmediainfo: various flaws [fedora-all] https://bugzilla.redhat.com/show_bug.cgi?id=1701847 pam_radius-1.4.0-4.el7 (FEDORA-EPEL-2019-489d75ec9c) PAM Module for RADIUS Authentication Update Information: Fix garbage password contents in add_password `add_password` does length rounding prior to coyping the contents of the password buffer. This causes two problems: 1. The hashed contents include trailing memory past the length of the password. 2. The hashed contents will no longer be NULL-terminated. Apply the following two upstream commits to fix: 1. `6bae92df885602b2558333bdb6d2db67d1365683` 2. `ac2c16774be593ebaa769b09c95722d08216cb95` ChangeLog: * Mon Apr 22 2019 Alexander Scheel - 1.4.0-4 - Fix NULL-termination of password buffer,
pghmcfc pushed to perl-Test2-Plugin-NoWarnings (f30). "Update to 0.07 (..more)"
Notification time stamped 2019-04-22 15:28:31 UTC
From fa6ad2169b6480a5519e7ce4660e6bcc3e95cd7d Mon Sep 17 00:00:00 2001
From: Paul Howarth
Date: Apr 22 2019 15:23:02 +
Subject: Update to 0.07
- New upstream release 0.07
- Reverted back to using the Warning event type, since the bug in the Test2
core that caused this to be a problem has since been fixed
- Replaced use of Test2::Bundle::Extended with Test2::V0
- Package new document CODE_OF_CONDUCT.md
- Modernize spec using %{make_build} and %{make_install}
---
diff --git a/perl-Test2-Plugin-NoWarnings.rpmlintrc
b/perl-Test2-Plugin-NoWarnings.rpmlintrc
new file mode 100644
index 000..15c4609
--- /dev/null
+++ b/perl-Test2-Plugin-NoWarnings.rpmlintrc
@@ -0,0 +1,3 @@
+from Config import *
+
+addFilter("spelling-error %description -l en_US diag -> ")
diff --git a/perl-Test2-Plugin-NoWarnings.spec
b/perl-Test2-Plugin-NoWarnings.spec
index 1321514..a44860f 100644
--- a/perl-Test2-Plugin-NoWarnings.spec
+++ b/perl-Test2-Plugin-NoWarnings.spec
@@ -1,6 +1,6 @@
Name: perl-Test2-Plugin-NoWarnings
-Version: 0.06
-Release: 6%{?dist}
+Version: 0.07
+Release: 1%{?dist}
Summary: Fail if tests warn
License: Artistic 2.0
URL: https://metacpan.org/release/Test2-Plugin-NoWarnings
@@ -9,22 +9,24 @@ BuildArch:noarch
# Build
BuildRequires: coreutils
BuildRequires: make
-BuildRequires: perl-interpreter
BuildRequires: perl-generators
+BuildRequires: perl-interpreter
BuildRequires: perl(ExtUtils::MakeMaker) > 6.75
# Module Runtime
BuildRequires: perl(Carp)
BuildRequires: perl(parent)
BuildRequires: perl(strict)
+BuildRequires: perl(Test2) >= 1.302096
BuildRequires: perl(Test2::API)
BuildRequires: perl(Test2::Event)
BuildRequires: perl(Test2::Util::HashBase)
BuildRequires: perl(warnings)
# Test Suite
+BuildRequires: perl(Capture::Tiny)
BuildRequires: perl(File::Spec)
BuildRequires: perl(IPC::Run3)
-BuildRequires: perl(Test2::Bundle::Extended)
BuildRequires: perl(Test2::Require::Module)
+BuildRequires: perl(Test2::V0)
BuildRequires: perl(Test::More) >= 0.96
# Optional Tests
BuildRequires: perl(CPAN::Meta) >= 2.120900
@@ -45,10 +47,10 @@ this module will stop working.
%build
perl Makefile.PL INSTALLDIRS=vendor NO_PERLLOCAL=1 NO_PACKLIST=1
-make %{?_smp_mflags}
+%{make_build}
%install
-make install DESTDIR=%{buildroot}
+%{make_install}
%{_fixperms} -c %{buildroot}
%check
@@ -56,12 +58,20 @@ make test
%files
%license LICENSE
-%doc Changes README.md
+%doc Changes CODE_OF_CONDUCT.md README.md
%{perl_vendorlib}/Test2/
%{_mandir}/man3/Test2::Event::Warning.3*
%{_mandir}/man3/Test2::Plugin::NoWarnings.3*
%changelog
+* Mon Apr 22 2019 Paul Howarth - 0.07-1
+- Update to 0.07
+ - Reverted back to using the Warning event type, since the bug in the Test2
+core that caused this to be a problem has since been fixed
+ - Replaced use of Test2::Bundle::Extended with Test2::V0
+- Package new document CODE_OF_CONDUCT.md
+- Modernize spec using %%{make_build} and %%{make_install}
+
* Sat Feb 02 2019 Fedora Release Engineering -
0.06-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
diff --git a/sources b/sources
index 863c17f..b791cb9 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Test2-Plugin-NoWarnings-0.06.tar.gz) =
aed9a3769085028adffd0aa7cbbe2d7d8b89b5f4768e47ae4155dcc1f4aa8fd47319ae7c87ddbc1ed08ca99e1d703eebb74977e88696ea4dcc1104a53332ade2
+SHA512 (Test2-Plugin-NoWarnings-0.07.tar.gz) =
fe9f9c9ca7372177655979a222688753b8c3b0affdcf19866ebe758b19e0c6082128687051588869a0fd41170d244ee0876d64306604a9a19bcd92d1ef3db748
https://src.fedoraproject.org/rpms/perl-Test2-Plugin-NoWarnings/c/fa6ad2169b6480a5519e7ce4660e6bcc3e95cd7d?branch=f30
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
pghmcfc pushed to perl-Test2-Plugin-NoWarnings (master). "Update to 0.07 (..more)"
Notification time stamped 2019-04-22 15:23:46 UTC
From fa6ad2169b6480a5519e7ce4660e6bcc3e95cd7d Mon Sep 17 00:00:00 2001
From: Paul Howarth
Date: Apr 22 2019 15:23:02 +
Subject: Update to 0.07
- New upstream release 0.07
- Reverted back to using the Warning event type, since the bug in the Test2
core that caused this to be a problem has since been fixed
- Replaced use of Test2::Bundle::Extended with Test2::V0
- Package new document CODE_OF_CONDUCT.md
- Modernize spec using %{make_build} and %{make_install}
---
diff --git a/perl-Test2-Plugin-NoWarnings.rpmlintrc
b/perl-Test2-Plugin-NoWarnings.rpmlintrc
new file mode 100644
index 000..15c4609
--- /dev/null
+++ b/perl-Test2-Plugin-NoWarnings.rpmlintrc
@@ -0,0 +1,3 @@
+from Config import *
+
+addFilter("spelling-error %description -l en_US diag -> ")
diff --git a/perl-Test2-Plugin-NoWarnings.spec
b/perl-Test2-Plugin-NoWarnings.spec
index 1321514..a44860f 100644
--- a/perl-Test2-Plugin-NoWarnings.spec
+++ b/perl-Test2-Plugin-NoWarnings.spec
@@ -1,6 +1,6 @@
Name: perl-Test2-Plugin-NoWarnings
-Version: 0.06
-Release: 6%{?dist}
+Version: 0.07
+Release: 1%{?dist}
Summary: Fail if tests warn
License: Artistic 2.0
URL: https://metacpan.org/release/Test2-Plugin-NoWarnings
@@ -9,22 +9,24 @@ BuildArch:noarch
# Build
BuildRequires: coreutils
BuildRequires: make
-BuildRequires: perl-interpreter
BuildRequires: perl-generators
+BuildRequires: perl-interpreter
BuildRequires: perl(ExtUtils::MakeMaker) > 6.75
# Module Runtime
BuildRequires: perl(Carp)
BuildRequires: perl(parent)
BuildRequires: perl(strict)
+BuildRequires: perl(Test2) >= 1.302096
BuildRequires: perl(Test2::API)
BuildRequires: perl(Test2::Event)
BuildRequires: perl(Test2::Util::HashBase)
BuildRequires: perl(warnings)
# Test Suite
+BuildRequires: perl(Capture::Tiny)
BuildRequires: perl(File::Spec)
BuildRequires: perl(IPC::Run3)
-BuildRequires: perl(Test2::Bundle::Extended)
BuildRequires: perl(Test2::Require::Module)
+BuildRequires: perl(Test2::V0)
BuildRequires: perl(Test::More) >= 0.96
# Optional Tests
BuildRequires: perl(CPAN::Meta) >= 2.120900
@@ -45,10 +47,10 @@ this module will stop working.
%build
perl Makefile.PL INSTALLDIRS=vendor NO_PERLLOCAL=1 NO_PACKLIST=1
-make %{?_smp_mflags}
+%{make_build}
%install
-make install DESTDIR=%{buildroot}
+%{make_install}
%{_fixperms} -c %{buildroot}
%check
@@ -56,12 +58,20 @@ make test
%files
%license LICENSE
-%doc Changes README.md
+%doc Changes CODE_OF_CONDUCT.md README.md
%{perl_vendorlib}/Test2/
%{_mandir}/man3/Test2::Event::Warning.3*
%{_mandir}/man3/Test2::Plugin::NoWarnings.3*
%changelog
+* Mon Apr 22 2019 Paul Howarth - 0.07-1
+- Update to 0.07
+ - Reverted back to using the Warning event type, since the bug in the Test2
+core that caused this to be a problem has since been fixed
+ - Replaced use of Test2::Bundle::Extended with Test2::V0
+- Package new document CODE_OF_CONDUCT.md
+- Modernize spec using %%{make_build} and %%{make_install}
+
* Sat Feb 02 2019 Fedora Release Engineering -
0.06-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
diff --git a/sources b/sources
index 863c17f..b791cb9 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Test2-Plugin-NoWarnings-0.06.tar.gz) =
aed9a3769085028adffd0aa7cbbe2d7d8b89b5f4768e47ae4155dcc1f4aa8fd47319ae7c87ddbc1ed08ca99e1d703eebb74977e88696ea4dcc1104a53332ade2
+SHA512 (Test2-Plugin-NoWarnings-0.07.tar.gz) =
fe9f9c9ca7372177655979a222688753b8c3b0affdcf19866ebe758b19e0c6082128687051588869a0fd41170d244ee0876d64306604a9a19bcd92d1ef3db748
https://src.fedoraproject.org/rpms/perl-Test2-Plugin-NoWarnings/c/fa6ad2169b6480a5519e7ce4660e6bcc3e95cd7d?branch=master
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Fedora rawhide compose report: 20190422.n.0 changes
OLD: Fedora-Rawhide-20190421.n.0 NEW: Fedora-Rawhide-20190422.n.0 = SUMMARY = Added images:3 Dropped images: 5 Added packages: 0 Dropped packages:0 Upgraded packages: 28 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 216.31 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 44.58 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Xfce live i386 Path: Spins/i386/iso/Fedora-Xfce-Live-i386-Rawhide-20190422.n.0.iso Image: LXQt live i386 Path: Spins/i386/iso/Fedora-LXQt-Live-i386-Rawhide-20190422.n.0.iso Image: Security live i386 Path: Labs/i386/iso/Fedora-Security-Live-i386-Rawhide-20190422.n.0.iso = DROPPED IMAGES = Image: KDE raw-xz armhfp Path: Spins/armhfp/images/Fedora-KDE-armhfp-Rawhide-20190421.n.0-sda.raw.xz Image: Python_Classroom vagrant-virtualbox i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190421.n.0.i386.vagrant-virtualbox.box Image: Python_Classroom vagrant-libvirt i386 Path: Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190421.n.0.i386.vagrant-libvirt.box Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20190421.n.0.iso Image: Cinnamon live i386 Path: Spins/i386/iso/Fedora-Cinnamon-Live-i386-Rawhide-20190421.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: bionetgen-2.4.0-5.fc31 Old package: bionetgen-2.4.0-4.fc30 Summary: Software for rule-based modeling of biochemical systems RPMs: bionetgen bionetgen-perl Size: 2.07 MiB Size change: 666.64 KiB Changelog: * Sat Apr 20 2019 Antonio Trande - 2.4.0-5 - Ready for MPI (disabled) - Bundle Sundials Package: cantor-18.12.3-3.fc31 Old package: cantor-18.12.3-2.fc31 Summary: KDE Frontend to Mathematical Software RPMs: cantor cantor-devel cantor-libs python3-cantor Size: 12.27 MiB Size change: 519.97 KiB Changelog: * Sun Apr 21 2019 Mukundan Ragavan - 18.12.3-3 - rebuild for libqalculate Package: cifs-utils-6.9-1.fc31 Old package: cifs-utils-6.8-4.fc30 Summary: Utilities for mounting and managing CIFS mounts RPMs: cifs-utils cifs-utils-devel pam_cifscreds Size: 747.99 KiB Size change: 116.88 KiB Changelog: * Sun Apr 21 2019 Jeff Layton - 6.9-1 - Update to v6.9 release Package: dav1d-0.2.2-1.fc31 Old package: dav1d-0.2.1-3.fc31 Summary: AV1 cross-platform Decoder RPMs: dav1d libdav1d libdav1d-devel Size: 2.84 MiB Size change: 17.89 KiB Changelog: * Sun Apr 21 2019 Robert-Andr?? Mauchin - 0.2.2-1 - Release 0.2.2 (#1701494) Package: electrum-3.3.4-2.fc31 Old package: electrum-3.3.4-1.fc31 Summary: A lightweight Bitcoin Client RPMs: electrum Size: 3.28 MiB Size change: -56 B Changelog: * Sun Apr 21 2019 Jonny Heggheim - 3.3.4-2 - Allow usage of aiorpcx-0.12 Package: getdp-3.1.0-1.fc31 Old package: getdp-2.11.3-9.fc30 Summary: General Environment for the Treatment of Discrete Problems RPMs: getdp getdp-devel Size: 7.07 MiB Size change: 2.82 MiB Changelog: * Sat Apr 20 2019 Sandro Mani - 3.1.0-1 - Update to 3.1.0 Package: gnome-shell-extension-dash-to-dock-66-1.fc31 Old package: gnome-shell-extension-dash-to-dock-64-2.fc30 Summary: Dock for the Gnome Shell by micxgx.gmail.com RPMs: gnome-shell-extension-dash-to-dock Size: 144.65 KiB Size change: 320 B Changelog: * Sun Apr 21 2019 Bj??rn Esser - 66-1 - Upgrade to 66 for GNOME 3.32 (f30) compatibility (rhbz#1700690) Package: infiniband-diags-2.1.0-3.fc31 Old package: infiniband-diags-2.1.0-2.fc30 Summary: OpenFabrics Alliance InfiniBand Diagnostic Tools RPMs: infiniband-diags infiniband-diags-compat infiniband-diags-devel infiniband-diags-devel-static Size: 2.16 MiB Size change: 146.11 KiB Changelog: * Sun Apr 21 2019 Honggang Li - 2.1.0-3 - Rebuild against latest opensm-3.3.22 Package: libqalculate-3.1.0-1.fc31 Old package: libqalculate-3.0.0-1.fc31 Summary: Multi-purpose calculator library RPMs: libqalculate libqalculate-devel qalculate Size: 10.54 MiB Size change: 217.54 KiB Changelog: * Sat Apr 20 2019 Mukundan Ragavan - 3.1.0-1 - Update to 3.1.0 Package: mediawriter-4.1.3-1.fc31 Old package: mediawriter-4.1.2-2.fc30 Summary: Fedora Media Writer RPMs: mediawriter Size: 21.79 MiB Size change: 277.13 KiB Changelog: * Sun Apr 21 2019 Martin Bza - 4.1.3-1 - Update to 4.1.3 - Resolves #1574717 Package: mingw-mediawriter-4.1.3-1.fc31 Old package: mingw-mediawriter-4.1.2-2.fc30 Summary: Fedora Media Writer RPMs: mingw32-mediawriter mingw64-mediawriter Size: 7.16 MiB Size change: 291.98 KiB Changelog: * Sun Apr 21 2019
Re: Maintainer test instances
On 4/16/19 11:43 AM, Richard Shaw wrote: > Also, pertinent to the main topic... Any chance of getting a EL 8 test > instance? I'd prefer not to put up a beta instance that gets no updates, but perhaps we can figure something out. kevin signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1701780] perl-DateTime-1.51 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701780 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- perl-DateTime-1.51-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2aeee196dd -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: ceph packages submitted to testing four days ago still haven't been pushed
They got stuck while getting signed, I retagged them and that should fix this. On Fri, Apr 19, 2019 at 6:47 PM Kaleb Keithley wrote: > > ceph-12.2.12 for f28 and f29. > > Happens every time. > > Someone please give them a kick. > > Thanks. > > -- > > Kaleb > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: two Ceph updates for f28, f29, stuck in pending testing for six days
I retagged them, that should fix this. On Mon, Apr 22, 2019 at 6:35 AM Kaleb Keithley wrote: > Two more are stuck again. > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-3b8418 > https://bodhi.fedoraproject.org/updates/FEDORA-2019-399f5bd105 > > On Fri, Mar 22, 2019 at 3:08 PM Kevin Fenzi wrote: > >> On 3/21/19 5:45 PM, Kaleb Keithley wrote: >> > On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi wrote: >> > >> >> On 2/18/19 12:56 PM, Kaleb Keithley wrote: >> >>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 >> >>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a >> >>> >> >>> Would someone please give them a kick? >> >> >> >> For some reason autosign likes to not process these correctly. >> >> >> >> I've retagged them to get it to do another pass... >> >> >> >> Sorry for not fixing them sooner. >> >> >> > >> > Looks like another Ceph build is stuck. >> > >> > https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1 >> > >> > Would someone kick it please? Thanks >> >> Fixed, and I looked and asked upstream and this is fixed in sigul 1.0. >> >> So, hopefully we won't have to keep doing this too much longer. >> >> kevin >> >> >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >> > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1701780] perl-DateTime-1.51 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701780 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- perl-DateTime-1.51-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2aeee196dd -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1701910] New: perl-Canary-Stability-2013 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701910 Bug ID: 1701910 Summary: perl-Canary-Stability-2013 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Canary-Stability Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 2013 Current version/release in rawhide: 2012-8.fc30 URL: http://search.cpan.org/dist/Canary-Stability/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/6613/ -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Understanding Fedora's use of systemd presets and packaging requirements
On 4/20/19 3:59 AM, Zbigniew Jędrzejewski-Szmek wrote: On Fri, Apr 19, 2019 at 04:35:54PM -0400, John Florian wrote: I'm generally familiar with how systemd presets work but I'm at a bit of loss as to how part of all the magic works. To best explain my confusion, let me say that I make a customized live spin of Fedora and I have a package we'll call "my-dist" which is similar in nature to the "fedora-release" package in that it provides a custom preset file. I still use fedora-release because this spin is not *that* customized, so it's best to think of this as an extension. I have another package we'll call "my-service" which has a systemd service unit file and all the usual %systemd_post, etc. macros. When I boot my live spin I find that my-service is not enabled despite the preset in my-dist. I can "systemctl preset-all" to rectify this so I believe most requirements are correct. I do see that livemedia-creator installs my-service *before* it installs my-dist so if the %systemd_post is called as each rpm is installed that would explain my problem because my custom preset isn't present yet. How does Fedora itself accomplish this??? I don't see every package providing a service having a dependency on fedora-release to address this ordering issue. I can certainly stick the "systemctl preset-all" into the %post of my kickstart as final cleanup, but that feels dirty and wrong. Similarly, I don't wish to have to have a "Requires: my-dist" in every one of "my-service" and other packages like it. I've scrutinized fedora-release.spec and didn't see anything all that different than what I have in my-dist. systemd.rpm does preset-all when it is installed, so it is enough that systemd.rpm is installed after fedora-release-common.rpm. fedora-release-common is required by setup.rpm, so it is installed early. But you raise a good point — I don't see any *explicit* ordering chain between fedora-release-common and systemd. There is no need to order individual rpms against either fedora-release-common and other packages providing presets or systemd. The only thing that is necessary is for systemd.rpm to be installed after all presets. If that is satisfied, packages proving services can be installed both earlier and later and the effect (in the sense of service enablement) should be identical. Zbyszek Thank you for the nicely detailed answer. So if there's no explicit ordering chain in Fedora, does it mean that it's just luck to make it all work out? If I read that right, it would seem that systemd would have to be one of the very last packages installed, but maybe it doesn't matter much for Fedora proper given how most everything is disabled by default. Should I try to achieve that with my spin or is there even a way? It would seem I would need some sort of reverse Requires to achieve this without touching Fedora's native packages. I'm guessing that means doing a "systemctl preset-all" at the end of my kickstart is probably as good a solution as any. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Can we maybe reduce the set of packages we install by default a bit?
On 4/17/19 4:38 AM, Lennart Poettering wrote: On Di, 16.04.19 09:06, Adam Williamson (adamw...@fedoraproject.org) wrote: I think all of these are good ideas. "No udev-settle" seems like a nice highlevel goal to shoot for. Another one I might add: "No stuck stop jobs" - it annoys me every single time when I reboot and something like rngd or conmon holds up my reboot for several minutes for no reason at all. I've seen the rngd stop thing, hadn't had time to investigate it yet as more urgent fires keep showing up :/ What's the story anyway for rngd? Why would userspace be better at providing entropy to the kernel than the kernel itself? Why do we enable it on desktops at all, such systems should not be entropy-starved. Non developers, true. Developer's workstations, wrong. Just signing a few packages (java's jarsigner) to test your code runs fine under those conditions can drop to near zero the entropy, taking a lot of time to finish the signing. Do we need this at all now that the kernel can use RDRAND itself? rngd runs as regular system service, hence what's the point of that altogether? I mean, it runs so late during boot, at a point where the entropy pool is full anyway, and we need the kernel's RNG much much earlier already (already because systemd assigns a uuid to each service invocation that derives from kernel RNG, and it does that super early). So, why run a service that is supposed to fill up the entropy pool at a point where we don't need it anymore, and if the kernel can do what it does most likely already on its own? Isn't it time to kick rngd out of the default install, in particular on the workstation image? Isn't keeping it around just cargo culting? Lennart -- Lennart Poettering, Berlin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: two Ceph updates for f28, f29, stuck in pending testing for six days
Two more are stuck again. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3b8418 https://bodhi.fedoraproject.org/updates/FEDORA-2019-399f5bd105 On Fri, Mar 22, 2019 at 3:08 PM Kevin Fenzi wrote: > On 3/21/19 5:45 PM, Kaleb Keithley wrote: > > On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi wrote: > > > >> On 2/18/19 12:56 PM, Kaleb Keithley wrote: > >>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 > >>> https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a > >>> > >>> Would someone please give them a kick? > >> > >> For some reason autosign likes to not process these correctly. > >> > >> I've retagged them to get it to do another pass... > >> > >> Sorry for not fixing them sooner. > >> > > > > Looks like another Ceph build is stuck. > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1 > > > > Would someone kick it please? Thanks > > Fixed, and I looked and asked upstream and this is fixed in sigul 1.0. > > So, hopefully we won't have to keep doing this too much longer. > > kevin > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Update to ispc 1.11.0 failure due to cpp11
On 2019-04-21 2:16 p.m., Dominik 'Rathann' Mierzejewski wrote: > On Sunday, 21 April 2019 at 22:15, Luya Tshimbalanga wrote: >> Hello team, >> >> Can someone investigate the issue related to the build ? >> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=34323450 >> >> The failure occurred at those lines despite using gcc: >> >> BUILDSTDERR: At global scope: >> BUILDSTDERR: cc1plus: error: unrecognized command line option >> '-Wno-deprecated-register' [-Werror] >> BUILDSTDERR: cc1plus: error: unrecognized command line option >> '-Wno-c99-extensions' [-Werror] >> BUILDSTDERR: cc1plus: all warnings being treated as errors >> BUILDSTDERR: make[2]: *** [CMakeFiles/ispc.dir/build.make:1201: >> CMakeFiles/ispc.dir/src/opt.cpp.o] Error 1 > Yes, remove -Werror from compiler flags. I haven't looked, but I'm > guessing it's added by ispc build system. You might need to patch them > out. > Patch is already applied as seen on https://src.fedoraproject.org/rpms/ispc/tree/master It turned out CMakeList.txt includes these wno and werror so I removed them accordingly. Thanks for the pointer. Luya ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
