Re: Did check 0.15.x in rawhide break packages' test suites?
On Sun, Aug 2, 2020 at 9:55 AM Fabio Valentini wrote: > I'm looking through F33 FTBFS issues, and I see an increasing number > of packages that fail to build because their test suites (using check) > fail to build with errors like this: > > /usr/include/check.h:502:27: note: declared here > 502 | CK_DLL_EXP void CK_EXPORT _ck_assert_failed(const char *file, int > line, > | ^ > path_utils/path_utils_ut.c:698:3: error: too few arguments to function > '_ck_assert_failed' > > For example, gsignond-plugin-oauth, gsignond-plugin-sasl, > libaccounts-glib, signon-glib, ding-libs fail with these issues. > > Any idea if that's a problem with the "check" 0.15.x builds > themselves, or if packages need to adapt to changed API here? You can point the finger of blame at least partly at me for this. Version 0.15.0 of check introduced the use of __attribute__((printf)) to check the arguments to some of the calls. However, upstream didn't do it right, with the result that gcc warned on pretty much every use of the check macros. I submitted a patch upstream to fix that, which upstream applied and included in version 0.15.1. That patch, however, broke other things, such as the ability to call fail_if() with only one argument. I've been working on another patch to fix *that*. It's not too hard to do for gcc, which makes __VA_OPT__ available to the C compiler, but not so easy for the Microsoft compiler. I'll attach what I have so far. Comments or suggestions on how to make it better are much appreciated. I would like to submit something upstream by tomorrow. If upstream likes the idea, I'll do another build of check that includes the patch. -- Jerry James http://www.jamezone.org/ diff --git a/src/check.h.in b/src/check.h.in index 56187fb..000a31e 100644 --- a/src/check.h.in +++ b/src/check.h.in @@ -92,6 +92,17 @@ CK_CPPSTART #undef GCC_VERSION_AT_LEAST +#define CK_THIRD_ARG(x,y,z,...) z +#define CK_HAS_VA_OPT_I(...) CK_THIRD_ARG(__VA_OPT__(,),1,0,) +#define CK_HAS_VA_OPT CK_HAS_VA_OPT_I(?) + +#if CK_HAS_VA_OPT +#define CK_CALL(...)NULL +#define CK_CALL_ARGS(...) __VA_ARGS__ +#define CK_CHOOSE_CALLER(...) CK_CALL ## __VA_OPT__(_ARGS) +#define CK_ARGS(...) CK_CHOOSE_CALLER(__VA_ARGS__)(__VA_ARGS__) +#endif + #include #if defined(_MSC_VER) @@ -478,10 +489,17 @@ static void __testname ## _fn (int _i CK_ATTRIBUTE_UNUSED) * FIXME: these macros may conflict with C89 if expr is * FIXME: strcmp (str1, str2) due to excessive string length. */ +#if CK_HAS_VA_OPT #define fail_if(expr, ...)\ (expr) ? \ - _ck_assert_failed(__FILE__, __LINE__, "Failure '"#expr"' occurred" , ## __VA_ARGS__) \ + _ck_assert_failed(__FILE__, __LINE__, "Failure '"#expr"' occurred", CK_ARGS(__VA_ARGS__)) \ : _mark_point(__FILE__, __LINE__) +#else +#define fail_if(expr, ...)\ + (expr) ? \ + _ck_assert_failed(__FILE__, __LINE__, "Failure '"#expr"' occurred" , ## __VA_ARGS__, NULL) \ + : _mark_point(__FILE__, __LINE__) +#endif /* * Fail the test @@ -532,10 +550,17 @@ CK_DLL_EXP void CK_EXPORT _ck_assert_failed(const char *file, int line, * * @since 0.9.6 */ +#if CK_HAS_VA_OPT #define ck_assert_msg(expr, ...) \ (expr) ? \ _mark_point(__FILE__, __LINE__) : \ - _ck_assert_failed(__FILE__, __LINE__, "Assertion '"#expr"' failed" , ## __VA_ARGS__) + _ck_assert_failed(__FILE__, __LINE__, "Assertion '"#expr"' failed", CK_ARGS(__VA_ARGS__)) +#else +#define ck_assert_msg(expr, ...) \ + (expr) ? \ + _mark_point(__FILE__, __LINE__) : \ + _ck_assert_failed(__FILE__, __LINE__, "Assertion '"#expr"' failed" , ## __VA_ARGS__, NULL) +#endif /** * Unconditionally fail the test @@ -554,7 +579,11 @@ CK_DLL_EXP void CK_EXPORT _ck_assert_failed(const char *file, int line, * * @since 0.9.6 */ -#define ck_abort_msg(...) _ck_assert_failed(__FILE__, __LINE__, "Failed" , ## __VA_ARGS__) +#if CK_HAS_VA_OPT +#define ck_abort_msg(...) _ck_assert_failed(__FILE__, __LINE__, "Failed", CK_ARGS(__VA_ARGS__)) +#else +#define ck_abort_msg(...) _ck_assert_failed(__FILE__, __LINE__, "Failed" , ## __VA_ARGS__, NULL) +#endif /* Signed and unsigned integer comparison macros with improved output compared to ck_assert(). */ /* OP may be any comparison operator. */ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: Fedora rawhide compose report: 20200802.n.0 changes
On Sun, Aug 02, 2020 at 12:55:28PM +, Fedora Rawhide Report wrote: > OLD: Fedora-Rawhide-20200731.n.0 > NEW: Fedora-Rawhide-20200802.n.0 > > = SUMMARY = > Added images:4 > Dropped images: 5 > Added packages: 11 > Dropped packages:6 > Upgraded packages: 18240 > Downgraded packages: 41 I ran the releng check-latest-build script to fix these 41 downgrades: ansible-lint-4.2.0-5.fc33 < ansible-lint-4.2.0a1-2.fc32 retagged ansible-lint-4.2.0a1-2.fc32 to f33 erlang-p1_acme-1.0.3-2.fc33 < erlang-p1_acme-1.0.8-1.fc33 retagged erlang-p1_acme-1.0.8-1.fc33 to f33 fpdns-0.10.0-4.20190131.fc33 < fpdns-0.10.0-20190131.fc31.2 retagged fpdns-0.10.0-20190131.fc31.2 to f33 git-lab-porcelain-0-2020325git75a12220.fc33.2 < git-lab-porcelain-0-20200123git4eeaa725.fc32.1 retagged git-lab-porcelain-0-20200123git4eeaa725.fc32.1 to f33 golang-github-acobaugh-osrelease-0-3.20200607gita93a0a5.fc33 < golang-github-acobaugh-osrelease-0.0.0-1.2020 0607gita93a0a5.fc33 retagged golang-github-acobaugh-osrelease-0.0.0-1.20200607gita93a0a5.fc33 to f33 golang-github-openapi-loads-0.19.0-4.fc33 < golang-github-openapi-loads-0.19.5-1.fc33 retagged golang-github-openapi-loads-0.19.5-1.fc33 to f33 golang-github-openapi-strfmt-0.19.0-4.fc33 < golang-github-openapi-strfmt-0.19.5-1.fc33 retagged golang-github-openapi-strfmt-0.19.5-1.fc33 to f33 golang-github-opencontainers-image-spec-1.0.1-4.20190626gitda296dc.fc33 < golang-github-opencontainers-image -spec-1.0.1-5.20200730git79b036d.fc33 retagged golang-github-opencontainers-image-spec-1.0.1-5.20200730git79b036d.fc33 to f33 golang-github-opencontainers-runtime-spec-1.0.1-4.20200728gita1b50f6.fc33 < golang-github-opencontainers-run time-spec-1.0.2-1.fc33 retagged golang-github-opencontainers-runtime-spec-1.0.2-1.fc33 to f33 golang-github-opencontainers-selinux-1.2.2-4.fc33 < golang-github-opencontainers-selinux-1.6.0-1.fc33 retagged golang-github-opencontainers-selinux-1.6.0-1.fc33 to f33 golang-github-opentracing-1.1.0-5.fc33 < golang-github-opentracing-1.2.0-1.fc33 retagged golang-github-opentracing-1.2.0-1.fc33 to f33 golang-github-opentracing-basictracer-1.0.0-4.fc33 < golang-github-opentracing-basictracer-1.1.0-1.fc33 retagged golang-github-opentracing-basictracer-1.1.0-1.fc33 to f33 golang-github-opentracing-contrib-grpc-0-0.4.20190701git4b5a12d.fc33 < golang-github-opentracing-contrib-grp c-0-0.5.20200730gitdb30781.fc33 retagged golang-github-opentracing-contrib-grpc-0-0.5.20200730gitdb30781.fc33 to f33 golang-github-opentracing-contrib-stdlib-0-0.4.20190628git3020fec.fc33 < golang-github-opentracing-contrib-s tdlib-1.0.0-1.fc33 retagged golang-github-opentracing-contrib-stdlib-1.0.0-1.fc33 to f33 golang-github-openzipkin-zipkin-0.1.6-5.fc33 < golang-github-openzipkin-zipkin-0.2.2-1.fc33 retagged golang-github-openzipkin-zipkin-0.2.2-1.fc33 to f33 golang-github-otiai10-copy-1.1.1-2.fc33 < golang-github-otiai10-copy-1.2.0-1.fc33 retagged golang-github-otiai10-copy-1.2.0-1.fc33 to f33 golang-github-otiai10-mint-1.3.0-2.fc33 < golang-github-otiai10-mint-1.3.1-1.fc33 retagged golang-github-otiai10-mint-1.3.1-1.fc33 to f33 golang-github-ovh-0-0.7.20181207gitba5adb4.fc33 < golang-github-ovh-1.1.0-1.fc33 retagged golang-github-ovh-1.1.0-1.fc33 to f33 golang-github-oxtoacart-bpool-0-0.4.20190628git8c4636f.fc33 < golang-github-oxtoacart-bpool-0-0.5.20200730git03653db.fc33 retagged golang-github-oxtoacart-bpool-0-0.5.20200730git03653db.fc33 to f33 golang-github-peterbourgon-diskv-3.0.0-4.fc33 < golang-github-peterbourgon-diskv-3.0.0-5.fc33 retagged golang-github-peterbourgon-diskv-3.0.0-5.fc33 to f33 golang-github-peterh-liner-1.1.0-6.fc33 < golang-github-peterh-liner-1.2.0-1.fc33 retagged golang-github-peterh-liner-1.2.0-1.fc33 to f33 golang-github-pires-proxyproto-0-0.2.20200307git833e5d0.fc33 < golang-github-pires-proxyproto-0.1.3-1.fc33 retagged golang-github-pires-proxyproto-0.1.3-1.fc33 to f33 golang-github-pkg-profile-1.3.0-4.fc33 < golang-github-pkg-profile-1.5.0-1.fc33 retagged golang-github-pkg-profile-1.5.0-1.fc33 to f33 golang-github-pkg-sftp-1.10.0-5.fc33 < golang-github-pkg-sftp-1.11.0-1.fc33 retagged golang-github-pkg-sftp-1.11.0-1.fc33 to f33 golang-github-pkg-term-0-0.5.20190305gitaa71e9d.fc33 < golang-gi
Re: Unretire rgbds
On Sunday, 2 August 2020 11:45:13 CEST Andy Mender wrote: > On Sat, 1 Aug 2020 at 18:55, Benjamin Lowry wrote: > > I've created a review request to unretire rgbds: > > https://bugzilla.redhat.com/show_bug.cgi?id=1862705 > > > > -ben > > Nice, GameBoy development! I'll review it. Do you need a sponsor? I'm not > senior enough to be one, but perhaps someone else would be willing to :). > > Cheers, > Andy Benjamin Lowry is a packager. If you're on Freenode IRC, you can check it with zodbot .fas/.fasinfo commands. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: Unretire rgbds
On Sun, 2 Aug 2020 at 21:42, Robert-André Mauchin wrote: > On Sunday, 2 August 2020 11:45:13 CEST Andy Mender wrote: > > On Sat, 1 Aug 2020 at 18:55, Benjamin Lowry wrote: > > > I've created a review request to unretire rgbds: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1862705 > > > > > > -ben > > > > Nice, GameBoy development! I'll review it. Do you need a sponsor? I'm not > > senior enough to be one, but perhaps someone else would be willing to :). > > > > Cheers, > > Andy > > Benjamin Lowry is a packager. If you're on Freenode IRC, you can check it > with > zodbot .fas/.fasinfo commands. > > My bad and thanks! I haven't used IRC in a while. I'll make sure to drop by the Fedora channels :). ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Minimal Mock's buildroot
As part of https://github.com/rpm-software-management/mock/issues/382 I found that the very minimal spec file can be built only using: * shadow-utils - mock needs /usr/sbin/useradd from this package * rpm-build - mock needs /usr/bin/rpmbuild * glibc-minimal-langpack - this is optional, but helps to avoid installation of huge glibc-all-langpacks. in buildroot. Everything else is transitively installed. Though the list of those transitive dependencies is quite long (see end of this mail). It may come handy to minimization team. I see there some low-hanging fruits: * why gdb-minimal, quile, dwz (needed for debuginfos) - especially when gcc has to be explicitly stated? * do we really need alternatives in minimal buildroot? * do we really need zip and unzip in minimal buildroot? But every change in minimal buildroot needs lots of administrative work (fesco, fepco, communication with packagers affected by change). I currently do not have will to work on this. So this is merely FYI and for anyone willing to continue to work on this. List of transitive dependencies. alternatives-1.11-6.fc32.x86_64 audit-libs-3.0-0.19.20191104git1c2f876.fc32.x86_64 basesystem-11-9.fc32.noarch bash-5.0.11-2.fc32.x86_64 binutils-gold-2.34-2.fc32.x86_64 binutils-2.34-2.fc32.x86_64 bzip2-libs-1.0.8-2.fc32.x86_64 bzip2-1.0.8-2.fc32.x86_64 ca-certificates-2020.2.40-3.fc32.noarch coreutils-common-8.32-3.fc32.1.x86_64 coreutils-8.32-3.fc32.1.x86_64 cpio-2.13-4.fc32.x86_64 crypto-policies-20191128-5.gitcd267a5.fc32.noarch curl-7.69.1-1.fc32.x86_64 cyrus-sasl-lib-2.1.27-4.fc32.x86_64 diffutils-3.7-4.fc32.x86_64 efi-srpm-macros-4-4.fc32.noarch elfutils-default-yama-scope-0.179-1.fc32.noarch elfutils-libelf-0.179-1.fc32.x86_64 elfutils-libs-0.179-1.fc32.x86_64 elfutils-0.179-1.fc32.x86_64 expat-2.2.8-2.fc32.x86_64 fedora-gpg-keys-32-1.noarch fedora-release-common-32-1.noarch fedora-release-32-1.noarch fedora-repos-32-1.noarch file-libs-5.38-2.fc32.x86_64 filesystem-3.14-2.fc32.x86_64 file-5.38-2.fc32.x86_64 findutils-4.7.0-3.fc32.x86_64 fonts-srpm-macros-2.0.3-1.fc32.noarch fpc-srpm-macros-1.3-1.fc32.noarch gawk-5.0.1-7.fc32.x86_64 gc-8.0.4-3.fc32.x86_64 gdb-minimal-9.1-3.fc32.x86_64 ghc-srpm-macros-1.5.0-2.fc32.noarch glibc-all-langpacks-2.31-2.fc32.x86_64 glibc-common-2.31-2.fc32.x86_64 glibc-2.31-2.fc32.x86_64 gmp-6.1.2-13.fc32.x86_64 gnat-srpm-macros-4-11.fc32.noarch go-srpm-macros-3.0.8-5.fc32.noarch grep-3.3-4.fc32.x86_64 guile-2.0.14-19.fc32.x86_64 gzip-1.10-2.fc32.x86_64 keyutils-libs-1.6-4.fc32.x86_64 krb5-libs-1.18-1.fc32.x86_64 libacl-2.2.53-5.fc32.x86_64 libarchive-3.4.2-1.fc32.x86_64 libattr-2.4.48-8.fc32.x86_64 libbrotli-1.0.7-10.fc32.x86_64 libcap-ng-0.7.10-2.fc32.x86_64 libcap-2.26-7.fc32.x86_64 libcom_err-1.45.5-3.fc32.x86_64 libcurl-7.69.1-1.fc32.x86_64 libdb-utils-5.3.28-40.fc32.x86_64 libdb-5.3.28-40.fc32.x86_64 libffi-3.1-24.fc32.x86_64 libgcc-10.0.1-0.11.fc32.x86_64 libgomp-10.0.1-0.11.fc32.x86_64 libidn2-2.3.0-2.fc32.x86_64 libmetalink-0.1.3-10.fc32.x86_64 libnghttp2-1.40.0-2.fc32.x86_64 libpkgconf-1.6.3-3.fc32.x86_64 libpsl-0.21.0-4.fc32.x86_64 libselinux-3.0-3.fc32.x86_64 libsemanage-3.0-3.fc32.x86_64 libsepol-3.0-3.fc32.x86_64 libsigsegv-2.11-10.fc32.x86_64 libssh-config-0.9.3-2.fc32.noarch libssh-0.9.3-2.fc32.x86_64 libstdc++-10.0.1-0.11.fc32.x86_64 libtasn1-4.16.0-1.fc32.x86_64 libtool-ltdl-2.4.6-33.fc32.x86_64 libunistring-0.9.10-7.fc32.x86_64 libverto-0.3.0-9.fc32.x86_64 libxcrypt-4.4.16-1.fc32.x86_64 libxml2-2.9.10-3.fc32.x86_64 libzstd-1.4.4-2.fc32.x86_64 lua-libs-5.3.5-7.fc32.x86_64 lz4-libs-1.9.1-2.fc32.x86_64 mpfr-4.0.2-3.fc32.x86_64 ncurses-base-6.1-15.20191109.fc32.noarch ncurses-libs-6.1-15.20191109.fc32.x86_64 ncurses-6.1-15.20191109.fc32.x86_64 nim-srpm-macros-3-2.fc32.noarch ocaml-srpm-macros-6-2.fc32.noarch openblas-srpm-macros-2-7.fc32.noarch openldap-2.4.47-4.fc32.x86_64 openssl-libs-1.1.1d-7.fc32.x86_64 patch-2.7.6-12.fc32.x86_64 pcre2-syntax-10.34-9.fc32.noarch pcre2-10.34-9.fc32.x86_64 pcre-8.44-1.fc32.x86_64 perl-srpm-macros-1-34.fc32.noarch pkgconf-m4-1.6.3-3.fc32.noarch pkgconf-pkg-config-1.6.3-3.fc32.x86_64 pkgconf-1.6.3-3.fc32.x86_64 popt-1.16-19.fc32.x86_64 publicsuffix-list-dafsa-20190417-3.fc32.noarch python-srpm-macros-3-55.fc32.noarch p11-kit-trust-0.23.20-1.fc32.x86_64 p11-kit-0.23.20-1.fc32.x86_64 qt5-srpm-macros-5.13.2-2.fc32.noarch readline-8.0-4.fc32.x86_64 redhat-rpm-config-150-1.fc32.noarch rpm-build-libs-4.15.1-2.fc32.1.x86_64 rpm-build-4.15.1-2.fc32.1.x86_64 rpm-libs-4.15.1-2.fc32.1.x86_64 rpm-4.15.1-2.fc32.1.x86_64 rust-srpm-macros-13-2.fc32.noarch sed-4.5-5.fc32.x86_64 setup-2.13.6-2.fc32.noarch shadow-utils-4.8.1-2.fc32.x86_64 tar-1.32-4.fc32.x86_64 tzdata-2019c-3.fc32.noarch unzip-6.0-47.fc32.x86_64 xxhash-libs-0.7.3-1.fc32.x86_64 xz-libs-5.2.5-1.fc32.x86_64 xz-5.2.5-1.fc32.x86_64 zip-3.0-26.fc32.x86_64 zlib-1.2.11-21.fc32.x86_64 zstd-1.4.4-2.fc32.x86_64 -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno,
Re: postgis LTO failure
On 02.08.20 07:43, Jeff Law wrote: On Sun, 2020-08-02 at 00:36 +0200, Sandro Mani wrote: Hi postgis seems another one suffering from LTO related failures. LTO (results in test failures): https://koji.fedoraproject.org/koji/taskinfo?taskID=48393090 LTO disabled (tests pass): https://koji.fedoraproject.org/koji/taskinfo?taskID=48394173 I've been able to reproduce the testsuite failure. I'll try to take it from here. Thanks! Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: Unretire rgbds
On Sat, 1 Aug 2020 at 18:55, Benjamin Lowry wrote: > I've created a review request to unretire rgbds: > https://bugzilla.redhat.com/show_bug.cgi?id=1862705 > > -ben > Nice, GameBoy development! I'll review it. Do you need a sponsor? I'm not senior enough to be one, but perhaps someone else would be willing to :). Cheers, Andy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Did check 0.15.x in rawhide break packages' test suites?
Hi all, I'm looking through F33 FTBFS issues, and I see an increasing number of packages that fail to build because their test suites (using check) fail to build with errors like this: /usr/include/check.h:502:27: note: declared here 502 | CK_DLL_EXP void CK_EXPORT _ck_assert_failed(const char *file, int line, | ^ path_utils/path_utils_ut.c:698:3: error: too few arguments to function '_ck_assert_failed' For example, gsignond-plugin-oauth, gsignond-plugin-sasl, libaccounts-glib, signon-glib, ding-libs fail with these issues. Any idea if that's a problem with the "check" 0.15.x builds themselves, or if packages need to adapt to changed API here? Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: module build: BuildrootError: could not init mock buildroot
Hi, > Weird. The actual error is: > "ERROR: Could not find useradd in chroot, maybe the install failed?" > > But that sounds like what happens when it didn't install the build rpms > in there. > > Can you try again now? we fixed a major issue with mbs, which I wouldn't > think was related to this, but who knows... Thanks for checking. Ah I found the error message you mentioned in mock_output.log with "Option --old-chroot has been deprecated.". Weird. I just executed the command `fedpkg module-build` without `--old-chroot` or any options. ``` $ rpm -q fedpkg fedpkg-1.38-4.fc32.noarch ``` https://kojipkgs.fedoraproject.org//work/tasks/4473/48194473/mock_output.log ``` ERROR: Option --old-chroot has been deprecated. Use --isolation=simple instead. ... ERROR: Could not find useradd in chroot, maybe the install failed? ``` Sure. Let me try it. -- Jun | He - His - Him ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: Fedora rawhide compose report: 20200802.n.0 changes
On Sun, 2020-08-02 at 11:27 -0700, Kevin Fenzi wrote: > On Sun, Aug 02, 2020 at 12:55:28PM +, Fedora Rawhide Report wrote: > > OLD: Fedora-Rawhide-20200731.n.0 > > NEW: Fedora-Rawhide-20200802.n.0 > > > > = SUMMARY = > > Added images:4 > > Dropped images: 5 > > Added packages: 11 > > Dropped packages:6 > > Upgraded packages: 18240 > > Downgraded packages: 41 > > I ran the releng check-latest-build script to fix these 41 downgrades: Just went through these. Most were correct - the apparently-newer build really was newer - but some were not, due to errors in package versioning (the 'newer' build is actually an older build with a problematic version). CCing the recent builders of all affected packages to take appropriate action. Packagers, please refresh your memory on https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning and https://fedoraproject.org/wiki/Package_Versioning_Examples , particularly regarding correct versioning of pre-release builds. When correcting a package's versioning to meet the guidelines, please remember to check if the corrected version parses as older, and if so either bump the Epoch or do something else (e.g. cut an upstream release, if you can) to fix that. I've put "FAO " at the start of each item so you can just search for your FAS name to find the package that I'm CCing you for. > ansible-lint-4.2.0-5.fc33 < ansible-lint-4.2.0a1-2.fc32 > retagged ansible-lint-4.2.0a1-2.fc32 to f33 FAO pnemade: This is clearly a package versioning error, the Alpha build should've been versioned 4.2.0-0.2.alpha1 or so. Will need a 4.2.1 or an epoch bump to fix unfortunately. > fpdns-0.10.0-4.20190131.fc33 < fpdns-0.10.0-20190131.fc31.2 > retagged fpdns-0.10.0-20190131.fc31.2 to f33 > FAO mmckinst, jplesnik: Also looks like a versioning error. The fc31.2 build is basically entirely missing the 'normal' release component. Mark fixed the versioning in fpdns-0.10.0-1.20190131.fc32 , but did not bump the epoch, so the new builds are lower versioned than the older ones. Again needs an epoch bump or a new version (or a *really* big release tag...) to fix properly. > git-lab-porcelain-0-2020325git75a12220.fc33.2 < > git-lab-porcelain-0-20200123git4eeaa725.fc32.1 > retagged git-lab-porcelain-0-20200123git4eeaa725.fc32.1 to f33 FAO nhorman: More date fun! This looks like a 0 typo: the newer build has '2020325' instead of '20200325' (I do this one myself all the damn time, sigh). Fixing that typo would make things work, though the versioning is still violating the guidelines by not having a 0.x release number between the (notional) version and the snapshot date. Fixing that would require bumping either the notional version or the epoch, though, and it likely won't ever cause a real problem unless there's ever an actual stable release versioned '0'. > > golang-github-acobaugh-osrelease-0-3.20200607gita93a0a5.fc33 < > golang-github-acobaugh-osrelease-0.0.0-1.2020 > 0607gita93a0a5.fc33 > FAO eclipseo, harrymichal: This looks like rpm considers 0.0.0 to be higher than 0. Interesting. Needs a version higher than 0.0.0 or an epoch bump. > icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc33.5 < > icedtea-web-2.0.0-pre.2.alpha13.patched1.fc33 > retagged icedtea-web-2.0.0-pre.2.alpha13.patched1.fc33 to f33 FAO jvanek: you made the versioning more correct between icedtea-web- 2.0.0-pre.2.alpha13.patched1.fc33 and icedtea-web-2.0.0- pre.0.2.alpha13.patched1.fc33 , but 'pre.0.2' (and 'pre.0.3' and 'pre.0.anything') parses as lower than 'pre.2', so this needed an epoch bump to work right. (I think the 'pre' could also be left out as it isn't doing anything useful, but IMBW there). > pveclib-1.0.4-4.fc33 < pveclib-1.0.4alpha2-3.fc33 > retagged pveclib-1.0.4alpha2-3.fc33 to f33 FAO munroesj52: this is a pre-release naming fail - '1.0.4alpha2' parses as higher than '1.0.4' to rpm. Needs an epoch bump or a 1.0.5 release. Older build should have been versioned 'pveclib-1.0.4- 0.1.alpha2' or so, please bear that in mind for future pre-releases. > salt-3001-2.fc33 < salt-3001rc1-2.fc33 > retagged salt-3001rc1-2.fc33 to f33 FAO dmurphy18 (SaltStack Packaging Team): same as pveclib - '3001rc1' parses as higher than '3001'. Needs epoch bump or release above 3001. Older build should have been salt-3001-0.2.rc1. Also your email address is wrong in the package changelog, it has .com.com not just .com. :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___
Re: Why lxd is not included in Fedora?
On Sun, 2 Aug 2020 at 18:45, Sergio Belkin wrote: > > Hi! > Just out of curiosity, why is lxd not included in Fedora? > Thanks in advance! > A quick review of the development mailing lists sees the last person mentioning that they were working on packaging LXD was in 2016, and they only did it in COPR versus getting it included in Fedora. I don't see anyone else working on it and no component in bugzilla so I don't know if someone tried and found it too hard or they just decided doing it in a COPR was all they needed. -- 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://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/devel@lists.fedoraproject.org
Re: Why lxd is not included in Fedora?
On Sun, Aug 2, 2020 at 6:45 PM Sergio Belkin wrote: > > Hi! > Just out of curiosity, why is lxd not included in Fedora? > Thanks in advance! > No one has attempted to bring it into Fedora. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: [Test-Announce] RIP: Thomas Gilliard (satellit)
This is very sad news, he was a very enthusiastic tester. Dennis On Sun, Aug 2, 2020 at 5:49 PM Adam Williamson wrote: > > Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a > valued member of the QA team for many years, passed away last week. His > wife contacted me with the news. Thomas was a regular and reassuring > presence at QA and blocker review meetings and ran many thousands of > tests since he first joined the team in 2009. He was particularly > dedicated to testing our Sugar builds. We'll miss him. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > http://www.happyassassin.net > ___ > test-announce mailing list -- test-annou...@lists.fedoraproject.org > To unsubscribe send an email to test-announce-le...@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/test-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://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/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://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/devel@lists.fedoraproject.org
Re: [Test-Announce] RIP: Thomas Gilliard (satellit)
Sad to hear this. You will be missed. Geoff Marr IRC: coremodule On Sun, Aug 2, 2020 at 7:27 PM Dennis Gilmore wrote: > This is very sad news, he was a very enthusiastic tester. > > Dennis > > On Sun, Aug 2, 2020 at 5:49 PM Adam Williamson > wrote: > > > > Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a > > valued member of the QA team for many years, passed away last week. His > > wife contacted me with the news. Thomas was a regular and reassuring > > presence at QA and blocker review meetings and ran many thousands of > > tests since he first joined the team in 2009. He was particularly > > dedicated to testing our Sugar builds. We'll miss him. > > -- > > Adam Williamson > > Fedora QA Community Monkey > > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net > > http://www.happyassassin.net > > ___ > > test-announce mailing list -- test-annou...@lists.fedoraproject.org > > To unsubscribe send an email to > test-announce-le...@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/test-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://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/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://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/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://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/devel@lists.fedoraproject.org
[Test-Announce] RIP: Thomas Gilliard (satellit)
Hi, folks. I'm sad to report that Thomas Gilliard (satellit), who was a valued member of the QA team for many years, passed away last week. His wife contacted me with the news. Thomas was a regular and reassuring presence at QA and blocker review meetings and ran many thousands of tests since he first joined the team in 2009. He was particularly dedicated to testing our Sugar builds. We'll miss him. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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/test-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://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/devel@lists.fedoraproject.org
[Test-Announce] 2020-08-03 @ 16:00 UTC - Fedora 33 Blocker Review Meeting
# F33 Blocker Review meeting # Date: 2020-08-03 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hello testers! As of this email, we have four proposed blockers in the works, so let's meet and knock these (and any others that appear) out! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F33 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good remainder of your weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria Geoff Marr IRC: coremodule ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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/test-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://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/devel@lists.fedoraproject.org
Re: Automatic logout due to quota
Hello, On Saturday, August 1, 2020 1:27:07 PM EDT Steven Grubb wrote: > I was using my desktop system when I got logged out. After logging back in, > I found this message in my logs: > > Aug 1 13:08:22 x2 journal[1751]: UID 1000 exceeded its 'bytes' quota on > UID 1000. I wrote a script that searched every binary on my system to see what possibly matches this output. Turns out this cryptic message is from dbus-broker. As best I can tell, a KDE program is triggering this. And I have no idea how to reconfigure things to fix it, but the failure is catestrophic when it shouldn't be. And its happening with some regularity. You are warned... -Steve > which was then followed by: > > Aug 1 13:08:22 x2 dbus-broker[1751]: Peer :1.200 is being disconnected as > it does not have the resources to perform an operation. > Aug 1 13:08:22 > x2 dbus-broker[1751]: Peer :1.176 is being disconnected as it does not > have the resources to receive a signal it subscribed to ... > > then > > Aug 1 13:08:22 x2 /usr/libexec/gdm-x-session[1703]: > cinnamon-session[1754]: WARNING: t+7310.22685s: Lost name on bus: > org.gnome.SessionManager > Aug 1 13:08:22 x2 > /usr/libexec/gdm-x-session[1703]: cinnamon-session[1754]: CRITICAL: > t+7310.22738s: We failed, but the fail whale is dead. Sorry Aug 1 > 13:08:22 x2 cinnamon-session[1754]: WARNING: t+7310.22685s: Lost name on > bus: org.gnome.SessionManager Aug 1 13:08:22 x2 cinnamon-session[1754]: > CRITICAL: t+7310.22738s: We failed, but the fail whale is dead. Sorry > Aug 1 13:08:23 x2 /usr/libexec/gdm-x-session[1703]: Cinnamon warning: > CurrentTime used to choose focus window; focus window may not be correct > Aug 1 13:08:23 x2 cinnamon-session[1754]: WARNING: t+7310.45021s: Playing > logout sound '/usr/share/cinnamon-control-center/sounds/logout.ogg' > Does anyone have any idea what this quota message is about? I don't use > quotas on my system since it's not shared. > Thanks, > -Steve > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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/de...@lists.fedoraproject.or > g ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Why lxd is not included in Fedora?
Hi! Just out of curiosity, why is lxd not included in Fedora? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
ghc-cryptonite LTO failure on s390x
Hi,
The build for ghc-cryptonite failed in the mass rebuild [1] and a
later rebuild by me [2], but only on s390x. The failure appears to be
LTO related. This doesn't appear to affect many other Haskell
packages. (I've found one seemingly-related failure in
ghc-haskell-src-exts [3].) Since it's Haskell, I'm using the standard
macros that should pass consistent flags, etc., so I'm not sure what
more information I can provide.
What happens is that ld.gold warns about mixed LTO/non-LTO:
[ 1 of 131] Compiling Crypto.Cipher.DES.Primitive (
Crypto/Cipher/DES/Primitive.hs,
dist/build/Crypto/Cipher/DES/Primitive.p_o )
/usr/bin/ld.gold: warning: incremental linking of LTO and non-LTO
objects; using -flinker-output=nolto-rel which will bypass whole
program optimization
and then errors out because of many LTO mismatches like:
/tmp/ghc794663_0/ghc_19.c:11:19: error:
warning: type of
‘cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc’
does not match original declaration [-Wlto-type-mismatch]
11 | extern CostCentre
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[];
| ^
|
11 | extern CostCentre
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[];
| ^
/tmp/ghc794663_0/ghc_18.hc:44:9: error:
note: type ‘StgWord’ should match type ‘struct CostCentre’
44 | StgWord
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))=
{
| ^
|
44 | StgWord
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))=
{
| ^
/tmp/ghc794663_0/ghc_18.hc:44:9: error:
note:
‘cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc’
was previously declared here
|
44 | StgWord
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))=
{
| ^
/tmp/ghc794663_0/ghc_18.hc:44:9: error:
note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used
|
44 | StgWord
cryptonitezm0zi26zmIKFu0XykBrR53imeIPM2Uw_CryptoziCipherziDESziPrimitive_CAFs_cc[]__attribute__((aligned(8)))=
{
| ^
followed by inlining failures:
/usr/include/bits/string_fortified.h: In function ‘fill_segment’:
/usr/include/bits/string_fortified.h:59:1: error:
error: inlining failed in call to ‘always_inline’ ‘memset’:
function body can be overwritten at link time
59 | __NTH (memset (void *__dest, int __ch, size_t __len))
| ^
|
59 | __NTH (memset (void *__dest, int __ch, size_t __len))
| ^
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=47957210
[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=48408236
[3] https://koji.fedoraproject.org/koji/taskinfo?taskID=48322376
--
Elliott
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: libcroco retired on Rawhide, breaking builds
On Sat, 1 Aug 2020 at 14:42, Kevin Fenzi wrote: > > On Sat, Aug 01, 2020 at 06:35:30PM +0100, Richard W.M. Jones wrote: > > On Sat, Aug 01, 2020 at 03:13:50PM +0200, Fabio Valentini wrote: > > > On Sat, Aug 1, 2020 at 2:44 PM Richard W.M. Jones > > > wrote: > > > > > > > > On Sat, Aug 01, 2020 at 03:25:48AM -0400, Elliott Sales de Andrade > > > > wrote: > > > > > libcroco was retired on Rawhide, but the libcroco-0.6.so.3()(64bit) it > > > > > provides is used by libtextstyle.so.0, part of gettext. > > > > > > > > > > gettext is used by many many things. Please unretire libcroco, or > > > > > rebuild gettext without it. > > > > > > > > Yes, can confirm this breaks the whole virt stack, again. Any > > > > "Second build" that needs libvirt has been broken by this. > > > > > > > > I really think we should redo this whole mass rebuild from the start. > > > > > > > > Rich. > > > > > > Well, gettext-0.20.2-4.fc33 without the libcroco dependency has now > > > been successfully built for f33-rebuild: > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1574351 > > > > > > It looks like f33-rebuild doesn't use its own packages for the > > > buildroot though, so anything using gettext is broken in both f33 and > > > f33-rebuild :( > > > Can we get gettext-0.20.2-4.fc33 tagged into the f33? I'd do it > > > myself, if I was sure not to break anything ... would "koji tag > > > f33-updates-candidate gettext-0.20.2-4.fc33" be enough? > > Yeah, I tagged it in a bit ago, sorry for not updating the list. > Thanks. Out of my 84 FTBFS, 75% were due to this breakage. I've already re-submitted them and they've passed, but I suspect a reasonable number of the failures in the second pass might be related to this. Only 2 were related to the cmake change. > > I don't know if this was done already, but libvirt is now installable > > and I was able to build virt-v2v, so it seems I'm now able to build > > the remaining virt packages. > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=48382603 > > > > https://kojipkgs.fedoraproject.org//work/tasks/2636/48382636/root.log > > => gettext 0.20.2-4.fc33 > > libvirt 6.5.0-1.fc33 > > We are just checking to make sure all the f33-rebuild packages are > signed, and then will be merging the tag. > > Waiting on 2020-08-01 17:12:08,374 INFO: Calling koji to write 228467 rpms > > Fingers crossed. > > kevin -- Elliott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: [Test-Announce] RIP: Thomas Gilliard (satellit)
Sad news indeed. ;( He will be missed... kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
Re: Why lxd is not included in Fedora?
> Am 03.08.2020 um 01:13 schrieb Stephen John Smoogen : > > On Sun, 2 Aug 2020 at 18:45, Sergio Belkin wrote: >> >> Hi! >> Just out of curiosity, why is lxd not included in Fedora? >> Thanks in advance! >> > > A quick review of the development mailing lists sees the last person > mentioning that they were working on packaging LXD was in 2016, and > they only did it in COPR versus getting it included in Fedora. I don't > see anyone else working on it and no component in bugzilla so I don't > know if someone tried and found it too hard or they just decided doing > it in a COPR was all they needed. > There is currently a quite recent version of LXD in copr (version 3.22 2020, https://copr.fedorainfracloud.org/coprs/ganto/lxc3/). Work on version 4 is in progress. We use the copr version for about nearly 2 years on some of our machines without issues. It’s currently more or less a one man show and Ganto is doing a great job. There was a short discussion about adding it to Fedora (https://github.com/ganto/copr-lxc3/issues/14). Technically it doesn't seem to be such a difficult thing, but organizationally it's a matter of manpower. Maybe someone with knowledge in go can be found to assist? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org
[Bug 1861795] perl-HTTP-BrowserDetect-3.31 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1861795 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-HTTP-BrowserDetect-3.3 ||1-1.fc33 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2020-08-02 11:37:17 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1578318 -- 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://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/perl-devel@lists.fedoraproject.org
[Bug 1861508] perl-Test-TempDir-0.11 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1861508 Emmanuel Seyman changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Test-TempDir-0.11-1.fc ||33 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2020-08-02 11:38:17 --- Comment #1 from Emmanuel Seyman --- Built for rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1578326 -- 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://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/perl-devel@lists.fedoraproject.org
pghmcfc pushed to perl-MCE-Shared (master). "Update to 1.873 (..more)"
Notification time stamped 2020-08-02 13:53:50 UTC
From b3c2efee38fed6717ac8fb873d8cdbe19c4edead Mon Sep 17 00:00:00 2001
From: Paul Howarth
Date: Aug 02 2020 13:51:40 +
Subject: Update to 1.873
- New upstream release 1.873
- Resolved construction MCE::Shared->share hanging when specifying a module
that does not exist
---
diff --git a/perl-MCE-Shared.spec b/perl-MCE-Shared.spec
index 2ccdb3a..cf4f1d4 100644
--- a/perl-MCE-Shared.spec
+++ b/perl-MCE-Shared.spec
@@ -1,6 +1,6 @@
Name: perl-MCE-Shared
-Version: 1.872
-Release: 3%{?dist}
+Version: 1.873
+Release: 1%{?dist}
Summary: MCE extension for sharing data, supporting threads and processes
License: GPL+ or Artistic
URL: https://metacpan.org/release/MCE-Shared
@@ -21,7 +21,7 @@ BuildRequires:perl(constant)
BuildRequires: perl(Errno)
BuildRequires: perl(if)
BuildRequires: perl(IO::Handle)
-BuildRequires: perl(MCE) >= 1.872
+BuildRequires: perl(MCE) >= 1.873
BuildRequires: perl(MCE::Mutex)
BuildRequires: perl(MCE::Signal)
BuildRequires: perl(MCE::Util)
@@ -45,7 +45,7 @@ BuildRequires:perl(utf8)
# Runtime
Requires: perl(:MODULE_COMPAT_%(eval "$(perl -V:version)"; echo $version))
Requires: perl(IO::FDPass) >= 1.2
-Requires: perl(MCE) >= 1.872
+Requires: perl(MCE) >= 1.873
Requires: perl(overloading)
Requires: perl(POSIX)
Requires: perl(Storable) >= 2.04
@@ -93,6 +93,11 @@ make test
%{_mandir}/man3/MCE::Shared::Server.3*
%changelog
+* Sun Aug 2 2020 Paul Howarth - 1.873-1
+- Update to 1.873
+ - Resolved construction MCE::Shared->share hanging when specifying a module
+that does not exist
+
* Tue Jul 28 2020 Fedora Release Engineering -
1.872-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
@@ -107,7 +112,7 @@ make test
- Added hsetnx method to MCE::Shared::Minidb
- Updated keys, pairs, and values in
MCE::Shared::{ Array, Cache, Hash and Ordhash }
- - The MCE::Shared project is completed
+ - The MCE::Shared project is feature complete
* Wed May 13 2020 Paul Howarth - 1.871-1
- Update to 1.871
diff --git a/sources b/sources
index 05ca424..bd901f6 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (MCE-Shared-1.872.tar.gz) =
11fdcbfcdfe54428e04a0bc2f900cae9fbc51d9edc3aba62f2044670a6c858ff83608d1dadf805c037faa3adecbc2c2fcbad829a0041cda818177b549c337761
+SHA512 (MCE-Shared-1.873.tar.gz) =
7bbc10fdff62f42324e2fefb697147247ba58dd17bdb174d58da7153ec2e0264fa5c56d3c3da3f6e9d5dfa399573f49fdfca9eab4e3d98b011a9988bbb441bca
https://src.fedoraproject.org/rpms/perl-MCE-Shared/c/b3c2efee38fed6717ac8fb873d8cdbe19c4edead?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://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/perl-devel@lists.fedoraproject.org
[Bug 1862721] perl-MCE-1.873 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1862721 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-MCE-1.873-1.fc33 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2020-08-02 13:54:10 --- Comment #1 from Paul Howarth --- Build done: https://koji.fedoraproject.org/koji/taskinfo?taskID=48439618 -- 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://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/perl-devel@lists.fedoraproject.org
[Bug 1862651] perl-IO-Compress-2.096 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1862651 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-IO-Compress-2.096-1.fc ||33 Resolution|--- |RAWHIDE Assignee|jples...@redhat.com |p...@city-fan.org Doc Type|--- |If docs needed, set a value Last Closed||2020-08-02 09:54:30 --- Comment #1 from Paul Howarth --- Build done: https://koji.fedoraproject.org/koji/taskinfo?taskID=48385889 -- 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://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/perl-devel@lists.fedoraproject.org
[Bug 1862829] New: perl-Data-Visitor-0.31 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1862829 Bug ID: 1862829 Summary: perl-Data-Visitor-0.31 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Data-Visitor Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, trem...@tremble.org.uk Target Milestone: --- Classification: Fedora Latest upstream release: 0.31 Current version/release in rawhide: 0.30-18.fc33 URL: http://search.cpan.org/dist/Data-Visitor/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/7052/ -- 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://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/perl-devel@lists.fedoraproject.org
