[Bug 1793917] perl-Test-mysqld-1.0012-4.fc32 FTBFS: DBI connect('dbname=mysql;mysql_socket=/tmp/B_Fm_kLtjo/tmp/mysql.sock;user=root','',...) failed: Access denied for user 'root'@'localhost' at /build
https://bugzilla.redhat.com/show_bug.cgi?id=1793917 --- Comment #5 from Fedora Release Engineering --- Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (that's on 2020-03-18). A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html -- 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 1799856] perl-Syntax-Highlight-Perl6: FTBFS in Fedora rawhide/f32
https://bugzilla.redhat.com/show_bug.cgi?id=1799856 --- Comment #7 from Fedora Release Engineering --- Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 32. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (that's on 2020-04-02). A week before the mass branching of Fedora 33 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 31 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html -- 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
Fedora-Rawhide-20200307.n.1 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 18 of 43 required tests failed, 9 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 80/171 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-Rawhide-20200304.n.1): ID: 536309 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/536309 ID: 536313 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/536313 ID: 536404 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/536404 Old failures (same test failed in Fedora-Rawhide-20200304.n.1): ID: 536253 Test: x86_64 Server-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/536253 ID: 536254 Test: x86_64 Server-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/536254 ID: 536255 Test: x86_64 Server-dvd-iso install_vnc_server URL: https://openqa.fedoraproject.org/tests/536255 ID: 536256 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/536256 ID: 536258 Test: x86_64 Server-dvd-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/536258 ID: 536259 Test: x86_64 Server-dvd-iso install_vncconnect_server URL: https://openqa.fedoraproject.org/tests/536259 ID: 536260 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/536260 ID: 536261 Test: x86_64 Server-dvd-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/536261 ID: 536262 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/536262 ID: 536276 Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation URL: https://openqa.fedoraproject.org/tests/536276 ID: 536284 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/536284 ID: 536289 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/536289 ID: 536293 Test: x86_64 Everything-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/536293 ID: 536294 Test: x86_64 Everything-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/536294 ID: 536295 Test: x86_64 Everything-boot-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/536295 ID: 536296 Test: x86_64 Everything-boot-iso install_default **GATING** URL: https://openqa.fedoraproject.org/tests/536296 ID: 536332 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/536332 ID: 536334 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/536334 ID: 536335 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/536335 ID: 536346 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/536346 ID: 536347 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/536347 ID: 536349 Test: x86_64 universal install_kickstart_hdd URL: https://openqa.fedoraproject.org/tests/536349 ID: 536350 Test: x86_64 universal install_ext3 URL: https://openqa.fedoraproject.org/tests/536350 ID: 536351 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/536351 ID: 536353 Test: x86_64 universal install_scsi_updates_img **GATING** URL: https://openqa.fedoraproject.org/tests/536353 ID: 536354 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/536354 ID: 536355 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/536355 ID: 536356 Test: x86_64 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/536356 ID: 536357 Test: x86_64 universal install_blivet_no_swap URL: https://openqa.fedoraproject.org/tests/536357 ID: 536358 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/536358 ID: 536359 Test: x86_64 universal install_xfs URL: https://openqa.fedoraproject.org/tests/536359 ID: 536360 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/536360 ID: 536361 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/536361 ID: 536362 Test: x86_64 universal install_mirrorlist_graphical **GATING** URL: https://openqa.fedoraproject.org/tests/536362 ID: 536365 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/536365 ID: 536366 Test: x86_64 universal install_multi
[Bug 1811368] New: perl-Log-ger-0.033 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1811368 Bug ID: 1811368 Summary: perl-Log-ger-0.033 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Log-ger Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.033 Current version/release in rawhide: 0.031-1.fc33 URL: http://search.cpan.org/dist/Log-ger/ 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/15741/ -- 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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 571 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 312 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 310 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 20 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fa8a2e97c6 python-waitress-1.4.3-1.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b57b954fde openfortivpn-1.12.0-1.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1f5dbc1cd7 cacti-1.2.10-1.el7 cacti-spine-1.2.10-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-471d8a7abd sympa-6.2.54-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b3684de763 mbedtls-2.7.14-1.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4fdca9429c seamonkey-2.53.1-2.el7 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-fbd804208a monit-5.26.0-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing ansible-2.9.6-1.el7 koji-1.20.1-1.el7 Details about builds: ansible-2.9.6-1.el7 (FEDORA-EPEL-2020-9d0b57e90e) SSH-based configuration management, deployment, and task execution system Update Information: Update to upstream 2.9.6 and fix for 2 CVES: CVE-2020-1737, CVE-2020-1739 Update to bugfix version 2.9.5. See https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst for details ChangeLog: * Fri Mar 6 2020 Kevin Fenzi - 2.9.6-1 - Update to 2.9.6. Fixes bug #1810373 - fixes for CVE-2020-1737, CVE-2020-1739 * Thu Feb 13 2020 Kevin Fenzi - 2.9.5-1 - Update to 2.9.5 * Tue Jan 21 2020 Kevin Fenzi - 2.9.4-1 - Update to 2.9.4 References: [ 1 ] Bug #1805322 - CVE-2020-1739 ansible: svn module leaks password when specified as a parameter [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1805322 [ 2 ] Bug #1810373 - ansible-2.9.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=1810373 [ 3 ] Bug #1805329 - CVE-2020-1737 ansible: Extract-Zip function in win_unzip module does not check extracted path [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1805329 [ 4 ] Bug #1802725 - ansible-2.9.5 is available https://bugzilla.redhat.com/show_bug.cgi?id=1802725 koji-1.20.1-1.el7 (FEDORA-EPEL-2020-8468336499) Build system tools Update Information: Update to 1.20.1 upstream bugfix minor release. ChangeLog: * Fri Mar 6 2020 Kevin Fenzi - 1.20.1-1 - Update to 1.20.1 * Wed Jan 29 2020 Fedora Release Engineering - 1.20.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Re: Two flaws in upcoming Gnome 3.36
On Sat, 7 Mar 2020 at 22:55, Leigh Scott wrote: [..] > > Just checked that patch and looks like still something is wrong because > > test suite is partially failing. > > > I get the same in f31 without the patch Please repeat that test running "xvfb-run -a make check" (test suite needs $DISPLAY) kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1a1caa3eb5 opensmtpd-6.6.4p1-1.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-47a203cb95 openfortivpn-1.12.0-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-9d364c6070 cacti-1.2.10-1.el8 cacti-spine-1.2.10-1.el8 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-8ce58993d7 mbedtls-2.16.5-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing ansible-2.9.6-1.el8 koji-1.20.1-1.el8 vapoursynth-48-7.el8 Details about builds: ansible-2.9.6-1.el8 (FEDORA-EPEL-2020-02f03affd4) SSH-based configuration management, deployment, and task execution system Update Information: Update to upstream 2.9.6 and fix for 2 CVES: CVE-2020-1737, CVE-2020-1739 ChangeLog: * Fri Mar 6 2020 Kevin Fenzi - 2.9.6-1 - Update to 2.9.6. Fixes bug #1810373 - fixes for CVE-2020-1737, CVE-2020-1739 References: [ 1 ] Bug #1805322 - CVE-2020-1739 ansible: svn module leaks password when specified as a parameter [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1805322 [ 2 ] Bug #1810373 - ansible-2.9.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=1810373 [ 3 ] Bug #1805329 - CVE-2020-1737 ansible: Extract-Zip function in win_unzip module does not check extracted path [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1805329 koji-1.20.1-1.el8 (FEDORA-EPEL-2020-c72d211254) Build system tools Update Information: Update to upstream 1.20.1 minor bugfix release. ChangeLog: * Fri Mar 6 2020 Kevin Fenzi - 1.20.1-1 - Update to 1.20.1 * Wed Jan 29 2020 Fedora Release Engineering - 1.20.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild vapoursynth-48-7.el8 (FEDORA-EPEL-2020-cb2d3ef940) Video processing framework with simplicity in mind Update Information: New package. ChangeLog: * Sat Mar 7 2020 Simone Caronni - 48-7 - Fix broken dependency. * Sat Feb 29 2020 Simone Caronni - 48-6 - Make it exclusive for i686/x86_64. - Fix build on RHEL/CentOS 8. * Tue Feb 25 2020 Artem Polishchuk - 48-5 - Add tests - Cosmetic spec file improvements * Thu Feb 20 2020 Simone Caronni - 48-4 - More review fixes. - Use upstream patch for Python 3.8. * Fri Feb 7 2020 Simone Caronni - 48-3 - Review fixes. * Sun Jan 26 2020 Simone Caronni - 48-2 - Move script library into main library package. - Fix build with Python 3.8. * Thu Jan 16 2020 Simone Caronni - 48-1 - First build. References: [ 1 ] Bug #1791588 - Review Request: vapoursynth - A video processing framework with simplicity in mind https://bugzilla.redhat.com/show_bug.cgi?id=1791588 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
[HEADS UP] Fonts packaging guidelines change status
Hi all, WHAT IS IT ALL ABOUT On 2020-02-13, FPC approved a rewrite of our fonts packaging guidelines. The previous guidelines were more than a decade old, technically outdated, relying on packages dropped from Fedora, and badly damaged during wiki to asciidoc migration. The new guidelines took 2 years to design, automate, test and write. The reviewing itself took 4 to 5 months. STATUS The guidelines are now published (grammar fixes welcome as a PR): https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/ Their tech core made the F32 freeze deadline. https://koji.fedoraproject.org/koji/packageinfo?packageID=30775 It has been queued to F31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-296917559c A significant set of pre-existing font packages have been converted in F32 (a few, only in F33). A significant set of new font packages have been added to F32 and F33 (huge thanks to Parag Nemade for a long list of repetitive reviews). No EL8 backport is planned for now, because the redhat-rpm-config version in EL8 is too old, and requires @rh engineering approval to be updated. Ping me if you want to work on EL-ing – I won’t. COMPATIBILITY Existing font packages are unchanged and can still rebuild as-is. Packagers are expected to migrate to new guidelines during F32 and F33. Legacy compatibility logic will be removed in F34. It is not equivalent feature and correctness wise with the new logic. CHANGES FOR OTHER PACKAGES No changes, EXCEPT FOR PACKAGES RELYING ON SPECIFIC FONT FILE PATHS. Unfortunately, some font upstreams can not make up their mind, on whether to publish fonts in dedicated projects, as part of collections, or as part of something else. To limit the effect of such changes, our font file layout has been changed to be completely srpm-independant. The resulting layout should now be more stable. However, users of the previous layout, need to change their symlinks or configuration files. Maintainers of existing font packages, should avoid pushing updates built with the new logic, to previous releases. It is still strongly recommended to migrate apps to fontconfig and harbuzz-ng. OpenType lets upstreams change the way they ventilate data among font files. Sometimes, this relayouting is required to implement new OpenType capabilities. fontconfig and harbuzz-ng isolate applications from a lot of font and text complexities. CHANGES FOR FONT PACKAGE USERS No direct change. However, most converted font packages were updated to the latest upstream version as part of the conversion. This update can include major upstream changes (for example, Google Droid and STIX engineering fonts). Existing fontconfig rules were also streamlined and completed. Both of those can lead to user-visible changes. CHANGES FOR FONT PACKAGERS The font family model to the latest OpenType recommendation. PLEASE DO READ AND APPLY THE GUIDELINES FONT FAMILY DEFINITION. OpenType, CSS and fontconfig are architected around this model, and build new features around it. Font packages that choose a different convention will cause problems in apps. They will need backwards- breaking changes once their upstream implements various OpenType enhancements. The new guidelines no longer assumes upstreams will create a nice dedicated project for each font family. Fonts can be packaged as dedicated projects, as part of a collective project, or as part of something else, with the same spec blocks. Appstream generation and testing is now automated (no more need to write appstream files or synchronise appstream file state with spec state by hand). Primitives are provided to easily create font collection metapackages. Guidelines should now cover a lot more cases, so you don’t need to locate a font expert to create or review font packages. NEXT CHANGES Lots of work with fontconfig upstream and major text users like LibreOffice or Inkscape, to fix more upstream font problems at the fontconfig level, with less fontconfig boilerplate, and better use of the result by apps (IBM Plex Sans requires more the 4000 lines of fontconfig fixes). OpenType and CSS continue to standardise enhancements that assume the previous recommendations were applied strictly. That means that messy upstreams will cause more and more problems application-side unless fontconfig is enhanced to fix more of those by default. In particular, many previously minor transgressions break in presence of variable fonts (variable compatibility mecanisms rely on strict metadata use by fixed fonts). NEW PACKAGES STILL PENDING REVIEW – Some major Google font families: typetogether-literata-fonts A contemporary serif font family for long-form reading https://bugzilla.redhat.com/show_bug.cgi?id=1805992 sorkintype-merriweather-fonts A warm space-saving serif font family https://bugzilla.redhat.com/show_bug.cgi?id=1805974 sorkintype-merriweather-sans-fonts A low-contrast semi-condensed sans-serif font family
Re: Two flaws in upcoming Gnome 3.36
> On Sat, 7 Mar 2020 at 18:35, Leigh Scott > > > Just checked that patch and looks like still something is wrong because > test suite is partially failing. > I get the same in f31 without the patch make[4]: Entering directory '/home/leigh/rpmbuild/BUILD/cogl-1.22.4/tests/conform' Key: ok = Test passed n/a = Driver is missing a feature required for the test FAIL = Unexpected failure FIXME = Test failed, but it was an expected failure PASS! = Unexpected pass Test GL+FF GL+ARBFP GL+GLSL GL-NPTGL3 test_pipeline_user_matrix: FAIL FAILFAIL FAIL FAIL test_blend_strings: FAIL FAILFAIL FAIL FAIL test_blend: FAIL FAILFAIL FAIL FAIL test_premult: FIXMEFIXME FIXME FIXME FIXME test_path: FAIL FAILFAIL FAIL FAIL test_path_clip: FAIL FAILFAIL FAIL FAIL test_depth_test: FAIL FAILFAIL FAIL FAIL test_color_mask: FAIL FAILFAIL FAIL FAIL test_backface_culling: FAIL FAILFAIL FIXME FAIL test_layer_remove: FAIL FAILFAIL FAIL FAIL test_sparse_pipeline: FAIL FAILFAIL FAIL FAIL test_npot_texture: FAIL FAILFAIL FAIL FAIL test_sub_texture: FAIL FAILFAIL FAIL FAIL test_pixel_buffer_map: FAIL FAILFAIL FAIL FAIL test_pixel_buffer_set_data: FAIL FAILFAIL FAIL FAIL test_pixel_buffer_sub_region: FAIL FAILFAIL FAIL FAIL test_texture_3d: FAIL FAILFAIL FAIL FAIL test_wrap_modes: FAIL FAILFAIL FAIL FAIL test_texture_get_set_data: FAIL FAILFAIL FAIL FAIL test_atlas_migration: FAIL FAILFAIL FAIL FAIL test_read_texture_formats: FIXMEFIXME FIXME FIXME FIXME test_write_texture_formats: FAIL FAILFAIL FAIL FAIL test_alpha_textures: FAIL FAILFAIL FAIL FAIL test_wrap_rectangle_textures: FIXMEFIXME FIXME FIXME FIXME test_primitive: FAIL FAILFAIL FAIL FAIL test_just_vertex_shader:n/a FAILFAIL FAIL FAIL test_pipeline_uniforms:n/a FAILFAIL FAIL FAIL test_snippets:n/a FAILFAIL FAIL FAIL test_custom_attributes:n/a FAILFAIL FAIL FAIL test_offscreen: FAIL FAILFAIL FAIL FAIL test_framebuffer_get_bits: FAIL FAILFAIL FAIL FAIL test_point_size: FAIL FAILFAIL FAIL FAIL test_point_size_attribute:n/a FAILFAIL FAIL FAIL test_point_size_attribute_snippet:n/a FAILFAIL FAIL FAIL test_point_sprite: FAIL FAILFAIL FAIL FAIL test_point_sprite_orientation: FIXMEFIXME FIXME FIXME FIXME test_point_sprite_glsl:n/a FAILFAIL FAIL FAIL test_version: FAIL FAILFAIL FAIL FAIL test_alpha_test: FAIL FAILFAIL FAIL FAIL test_map_buffer_range: FAIL FAILFAIL FAIL FAIL test_primitive_and_journal: FAIL FAILFAIL FAIL FAIL test_copy_replace_texture: FAIL FAILFAIL FAIL FAIL test_pipeline_cache_unrefs_texture: FAIL FAILFAIL FAIL FAIL test_pipeline_shader_state:n/a FAILFAIL FAIL FAIL test_gles2_context:n/a n/a n/an/an/a test_gles2_context_fbo:n/a n/a n/an/an/a test_gles2_context_copy_tex_image:n/a n/a n/an/an/a test_euler_quaternion: FAIL FAILFAIL FAIL FAIL test_color_hsl: FAIL FAILFAIL FAIL FAIL test_fence: FAIL FAILFAIL FAIL FAIL test_texture_no_allocate: FAIL FAILFAIL FAIL FAIL test_texture_rg: FAIL FAILFAIL FAIL FAIL make[4]: *** [Makefile:1942: test] Error 133 ___ 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
putting my blog back on Planet Fedora
One of the reasons my contributions to Fedora have slowed down is because my blog was censored from Planet Fedora I'd like to ask if people would like this censorship to stop As this was done shortly after the death of my father, things like this leave a scar. It is very, very wrong and I don't feel I should have to make a public request like this. Nonetheless, there is a certain type of person who wants to humiliate me by forcing me to beg like this and it is time to call them out and end this. Regards, Daniel ___ 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
libqalculate soname change
libqalculate soname bump is happening with v3.8.0. The following packages are affected - - qalculate-gtk - plasma-workspace - step - cantor I will rebuild all these packages on rawhide. qalculate-kde will also affected but this is already FTBFS. So, I won't touch this. Mukundan. 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://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: Two flaws in upcoming Gnome 3.36
On Sat, 7 Mar 2020 at 21:10, Leigh Scott wrote: [..] > > Still some long term cogl nad clutter solution needs to be applied. > > > As I wrote it is now separated (staticly linked) cogl and cutter copy in > > mutter > > It isn't statically linked, they are renamed private libs. > > ldd /usr/bin/cinnamon |grep -e cogl -e clutter > libmuffin-clutter-0.so => /usr/lib64/muffin/libmuffin-clutter-0.so > (0x7f45dbcb1000) > libmuffin-cogl-pango-0.so => > /usr/lib64/muffin/libmuffin-cogl-pango-0.so (0x7f45db12) > libmuffin-cogl-path-0.so => > /usr/lib64/muffin/libmuffin-cogl-path-0.so (0x7f45daf89000) > libmuffin-cogl-0.so => /usr/lib64/muffin/libmuffin-cogl-0.so > (0x7f45dacac000) Hmm .. this potentially makes this even worse because: - it is probably 3rd copy of the cogl (standalone cogl, mutter and - mutter developer told that cogl copy is only cut to be used in mutter. If I'm right it means that private code is used by mutter over library jump table making that code slower than it could be. In all those cases looks like private copies of those libraries are used as DSOs. Just checked and looks like mutter cogl DSOs are used by gnome-shell. [tkloczko@barrel SPECS]$ objdump -x /usr/lib64/libmutter-6.so.0 | grep NEED | grep cogl NEEDED libmutter-cogl-6.so.0 [tkloczko@barrel SPECS]$ objdump -x /usr/bin/gnome-shell | grep NEED | grep cogl NEEDED libmutter-cogl-pango-6.so.0 [tkloczko@barrel SPECS]$ objdump -x /usr/bin/mutter | grep NEED | grep cogl [tkloczko@barrel SPECS]$ [tkloczko@barrel SPECS]$ rpm -qal | grep lib64/ | grep cogl | grep -v pkgconfig /usr/lib64/libcogl-pango.so.20 /usr/lib64/libcogl-pango.so.20.4.2 /usr/lib64/libcogl-path.so.20 /usr/lib64/libcogl-path.so.20.4.2 /usr/lib64/libcogl.so.20 /usr/lib64/libcogl.so.20.4.2 /usr/lib64/libcogl-pango.so /usr/lib64/libcogl-path.so /usr/lib64/libcogl.so /usr/lib64/mutter-6/libmutter-cogl-6.so /usr/lib64/mutter-6/libmutter-cogl-6.so.0 /usr/lib64/mutter-6/libmutter-cogl-6.so.0.0.0 /usr/lib64/mutter-6/libmutter-cogl-pango-6.so /usr/lib64/mutter-6/libmutter-cogl-pango-6.so.0 /usr/lib64/mutter-6/libmutter-cogl-pango-6.so.0.0.0 /usr/lib64/mutter-6/libmutter-cogl-path-6.so /usr/lib64/mutter-6/libmutter-cogl-path-6.so.0 /usr/lib64/mutter-6/libmutter-cogl-path-6.so.0.0.0 So looks like cinamon is using 3rd copy :) kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH ___ 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: Non-responsive maintainer: pocock
On Sat, Mar 7, 2020 at 11:47 AM Daniel Pocock wrote: > > On 07/03/2020 10:32, Julian Sikorski wrote: > > > In any case, Fedora is a more bleeding edge distro than Debian/Ubuntu > > (First one of the foundations), so I am not sure how realistic it is to > > be waiting for Debian/Ubuntu to include something before we can do it in > > Fedora. > > Debian unstable/sid is similarly bleeding edge to rawhide > > Having the same dependencies in Debian sid and Fedora rawhide makes life > easier for everybody: library maintainers, upstreams and package > maintainers. > > I've always tried to work that way, that is the very reason I > volunteered to maintain asio in both Debian and Fedora. I also put the > necessary effort into supporting Debian backports and Fedora EPEL so > these things could be widely available. > Thank you for putting in the effort to making stuff broadly available to the Fedora community. I think you might be doing a slight disservice by holding things back in Fedora, but that is your prerogative. In general, I would advise keeping your packages updated in Fedora unless there's a really good technical reason not to. > >> Is there a convenient way for upstreams to make CI builds on the latest > >> Fedora rawhide in parallel with our travis-ci Ubuntu builds? > >> > > I am not aware of a ci service using Fedora, both appveyor and travis > > appear to be using ubuntu. > > I have some ideas about how to address this > > There is a similar script to use Docker inside travis-ci, using Docker > for a pure Debian sid build, rather than the default Ubuntu environment: > > https://travis.debian.net/ > > Could a Fedora equivalent exist? > We do have the Zuul based CI that the Fedora CI folks are working on: https://fedoraproject.org/wiki/Zuul-based-ci I don't know if they have the ability to support projects from GitHub as well. > Maybe OBS could also be relevant: > https://openbuildservice.org/ > Fedora COPR is designed to integrate well with software CI workflows, and the Packit service is an instance of this: https://packit.dev/ Packit may be able to help for this specific thing you're looking for. -- 真実はいつも一つ！/ 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
[HEADS UP] Fonts packaging guidelines change status
Hi all, WHAT IS IT ALL ABOUT On 2020-02-13, FPC approved a rewrite of our fonts packaging guidelines. The previous guidelines were more than a decade old, technically outdated, relying on packages dropped from Fedora, and badly damaged during wiki to asciidoc migration. The new guidelines took 2 years to design, automate, test and write. The reviewing itself took 4 to 5 months. STATUS The guidelines are now published (grammar fixes welcome as a PR): https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/ Their tech core made the F32 freeze deadline. https://koji.fedoraproject.org/koji/packageinfo?packageID=30775 It has been queued to F31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-296917559c A significant set of pre-existing font packages have been converted in F32 (a few, only in F33). A significant set of new font packages have been added to F32 and F33 (huge thanks to Parag Nemade for a long list of repetitive reviews). No EL8 backport is planned for now, because the redhat-rpm-config version in EL8 is too old, and requires @rh engineering approval to be updated. Ping me if you want to work on EL-ing – I won’t. COMPATIBILITY Existing font packages are unchanged and can still rebuild as-is. Packagers are expected to migrate to new guidelines during F32 and F33. Legacy compatibility logic will be removed in F34. It is not equivalent feature and correctness wise with the new logic. CHANGES FOR OTHER PACKAGES No changes, EXCEPT FOR PACKAGES RELYING ON SPECIFIC FONT FILE PATHS. Unfortunately, some font upstreams can not make up their mind, on whether to publish fonts in dedicated projects, as part of collections, or as part of something else. To limit the effect of such changes, our font file layout has been changed to be completely srpm-independant. The resulting layout should now be more stable. However, users of the previous layout, need to change their symlinks or configuration files. Maintainers of existing font packages, should avoid pushing updates built with the new logic, to previous releases. It is still strongly recommended to migrate apps to fontconfig and harbuzz-ng. OpenType lets upstreams change the way they ventilate data among font files. Sometimes, this relayouting is required to implement new OpenType capabilities. fontconfig and harbuzz-ng isolate applications from a lot of font and text complexities. CHANGES FOR FONT PACKAGE USERS No direct change. However, most converted font packages were updated to the latest upstream version as part of the conversion. This update can include major upstream changes (for example, Google Droid and STIX engineering fonts). Existing fontconfig rules were also streamlined and completed. Both of those can lead to user-visible changes. CHANGES FOR FONT PACKAGERS The font family model to the latest OpenType recommendation. PLEASE DO READ AND APPLY THE GUIDELINES FONT FAMILY DEFINITION. OpenType, CSS and fontconfig are architected around this model, and build new features around it. Font packages that choose a different convention will cause problems in apps. They will need backwards- breaking changes once their upstream implements various OpenType enhancements. The new guidelines no longer assumes upstreams will create a nice dedicated project for each font family. Fonts can be packaged as dedicated projects, as part of a collective project, or as part of something else, with the same spec blocks. Appstream generation and testing is now automated (no more need to write appstream files or synchronise appstream file state with spec state by hand). Primitives are provided to easily create font collection metapackages. Guidelines should now cover a lot more cases, so you don’t need to locate a font expert to create or review font packages. NEXT CHANGES Lots of work with fontconfig upstream and major text users like LibreOffice or Inkscape, to fix more upstream font problems at the fontconfig level, with less fontconfig boilerplate, and better use of the result by apps (IBM Plex Sans requires more the 4000 lines of fontconfig fixes). OpenType and CSS continue to standardise enhancements that assume the previous recommendations were applied strictly. That means that messy upstreams will cause more and more problems application-side unless fontconfig is enhanced to fix more of those by default. In particular, many previously minor transgressions break in presence of variable fonts (variable compatibility mecanisms rely on strict metadata use by fixed fonts). NEW PACKAGES STILL PENDING REVIEW – Some major Google font families: typetogether-literata-fonts A contemporary serif font family for long-form reading https://bugzilla.redhat.com/show_bug.cgi?id=1805992 sorkintype-merriweather-fonts A warm space-saving serif font family https://bugzilla.redhat.com/show_bug.cgi?id=1805974 sorkintype-merriweather-sans-fonts A low-contrast semi-condensed sans-serif font family
Re: Reducing broken dependencies in fedora (32) repositories
On Sat, Mar 7, 2020 at 4:42 PM Fabio Valentini wrote: > > On Sat, Mar 7, 2020, 15:05 Richard Shaw wrote: >> >> Are the broken source dependencies real? >> >> python-pyside2 (src): >> >> qt5-qtwebengine-devel > 5.13 >> >> I just checked koji and qt5-qtwebengine 5.13.2 is in f32 which should meet >> the requirement. > > > This looks like a case of either Caeat 1 or Caveat 2 listed above. Is > python-pyside2 a "noarch package with imported dependencies"? I tried to > whitelist all qtwebengine related false positives, but I might have missed > this one. I am at my PC now, and I verified that python-pyside2 is in fact a false positive (Caveat 2 from my first email). I'll whitelist this package. Fabio > Fabio > > >> >> 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://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: Orphaning most of the ancient Gnome 1 stack
> On Wed, 26 Feb 2020 09:04:07 + > Paul Howarth wrote: > > I've been looking after the ancient Gnome 1 library stack for the last > > decade as I had a local use for the libraries. That is no longer the > > case so I'm planning to orphan the following packages, none of which > > appear to be used by anything else in Fedora (Rawhide): > > > > * libglade > > * gnome-libs > > * ORBit > > * imlib > > * libxml > > * libpng10 > > These are now orphaned. So I've actively retired these as, for at least a few of my packages, they also allowed me to retired a bunch of stuff that I had some how ended up "maintaining". I think these sort of long tail packages should be actively moved to places like copr if people wish to keep them around. I think this should be a subject that FESCo actively addresses. That aside thank you Paul for actively maintaining them as long as you did. Peter ___ 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
M-x browse-at-remote support for Pagure
Hello, recently I've announced on this mailing list, that I implemented Pagure support for :Gbrowse command in Vim. If you are not familiar with this feature, it allows you to open a current file or line selection on a remote hosting platform such as GitHub, GitLab, Pagure, etc. Then you can easily share the link with your coworkers. If you are interested, see more information in this blog post. http://frostyx.cz/posts/vim-gbrowse-support-for-pagure Since I migrated to Emacs, I was really missing this feature, so I finally decided to go ahead and implement Pagure support also for the browse-at-remote package. For more information and a supercool gif demo, please see my newest blog post. http://frostyx.cz/posts/emacs-browse-at-pagure Hopefully, some of you will find it as useful as I do, Jakub ___ 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: Two flaws in upcoming Gnome 3.36
On Sat, 7 Mar 2020 at 18:35, Leigh Scott wrote: > Fixed https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcd6554797 > > > https://src.fedoraproject.org/rpms/cogl/c/a0efb472ea19505f100effde4d60a6182fd3161d?branch=master Just checked that patch and looks like still something is wrong because test suite is partially failing. ``` + xvfb-run -a /usr/bin/make -O -j48 V=1 VERBOSE=1 check Making check in deps make[2]: Nothing to be done for 'check-am'. Making check in test-fixtures make[1]: Nothing to be done for 'check'. Making check in cogl /usr/bin/make check-recursive Making check in cogl-path /usr/bin/make check-am Making check in cogl-pango make[1]: Nothing to be done for 'check'. Making check in tests Making check in conform /usr/bin/make check-am make[3]: Nothing to be done for 'check-am'. Making check in unit /usr/bin/make check-am make[3]: Nothing to be done for 'check-am'. Making check in micro-perf make[2]: Nothing to be done for 'check'. Making check in data make[2]: Nothing to be done for 'check'. /usr/bin/make check-local ( cd ./conform && /usr/bin/make test ) || exit $? make[4]: Entering directory '/home/tkloczko/rpmbuild/BUILD/cogl-1.22.4/tests/conform' Key: ok = Test passed n/a = Driver is missing a feature required for the test FAIL = Unexpected failure FIXME = Test failed, but it was an expected failure PASS! = Unexpected pass Test GL+FF GL+ARBFP GL+GLSL GL-NPTGL3 test_pipeline_user_matrix: FAIL ok ok ok ok test_blend_strings: FAIL ok ok ok ok test_blend: FAIL ok ok ok ok test_premult: FIXMEFIXME FIXME FIXME FIXME test_path: ok ok ok ok ok test_path_clip: FAIL ok ok ok ok test_depth_test: ok ok ok ok ok test_color_mask: FAIL ok ok ok ok test_backface_culling: FAIL ok ok FIXME ok test_layer_remove: FAIL ok ok ok ok test_sparse_pipeline: FAIL ok ok ok ok test_npot_texture: FAIL ok ok ok ok test_sub_texture: FAIL ok ok ok ok test_pixel_buffer_map: FAIL ok ok ok ok test_pixel_buffer_set_data: FAIL ok ok ok ok test_pixel_buffer_sub_region: FAIL ok ok ok ok test_texture_3d: FAIL ok ok ok ok test_wrap_modes: FAIL ok ok ok ok test_texture_get_set_data: ok ok ok ok ok test_atlas_migration: ok ok ok ok ok test_read_texture_formats: FIXMEFIXME FIXME FIXME FIXME test_write_texture_formats: ok ok ok ok ok test_alpha_textures: FAIL ok ok ok ok test_wrap_rectangle_textures: FIXMEFIXME FIXME FIXME FIXME test_primitive: FAIL ok ok ok ok test_just_vertex_shader:n/a ok ok ok ok test_pipeline_uniforms:n/a ok ok ok ok test_snippets:n/a ok ok ok ok test_custom_attributes:n/a ok ok ok ok test_offscreen: FAIL ok ok ok FAIL test_framebuffer_get_bits: ok ok ok ok ok test_point_size: FAIL ok ok ok ok test_point_size_attribute:n/a ok ok ok ok test_point_size_attribute_snippet:n/a ok ok ok ok test_point_sprite: FAIL ok ok ok ok test_point_sprite_orientation: FIXMEFIXME FIXME FIXME FIXME test_point_sprite_glsl:n/a ok ok ok ok test_version: ok ok ok ok ok test_alpha_test: FAIL ok ok ok ok test_map_buffer_range: FAIL ok ok ok ok test_primitive_and_journal: ok ok ok ok ok test_copy_replace_texture: ok ok ok ok ok test_pipeline_cache_unrefs_texture: FAIL ok ok ok ok test_pipeline_shader_state:n/a ok ok ok ok test_gles2_context:n/a n/a n/an/an/a test_gles2_context_fbo:n/a n/a n/an/an/a test_gles2_context_copy_tex_image:n/a n/a n/an/a FAIL test_euler_quaternion: ok ok ok ok
Re: Two flaws in upcoming Gnome 3.36
> On Sat, 7 Mar 2020 at 18:35, Leigh Scott > > > Thx. However as I wrote that is only short term solution. > I agree but I think cogl is considered legacy since the gnome devs moved it to mutter. > Still some long term cogl nad clutter solution needs to be applied. > As I wrote it is now separated (staticly linked) cogl and cutter copy in > mutter It isn't statically linked, they are renamed private libs. ldd /usr/bin/cinnamon |grep -e cogl -e clutter libmuffin-clutter-0.so => /usr/lib64/muffin/libmuffin-clutter-0.so (0x7f45dbcb1000) libmuffin-cogl-pango-0.so => /usr/lib64/muffin/libmuffin-cogl-pango-0.so (0x7f45db12) libmuffin-cogl-path-0.so => /usr/lib64/muffin/libmuffin-cogl-path-0.so (0x7f45daf89000) libmuffin-cogl-0.so => /usr/lib64/muffin/libmuffin-cogl-0.so (0x7f45dacac000) > kloczek ___ 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: Two flaws in upcoming Gnome 3.36
On Sat, 7 Mar 2020 at 18:35, Leigh Scott wrote: > Fixed https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcd6554797 Thx. However as I wrote that is only short term solution. Still some long term cogl nad clutter solution needs to be applied. As I wrote it is now separated (staticly linked) cogl and cutter copy in mutter and looks like those two components development is not well coordinated. kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH ___ 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: Orphaned packages
Il giorno sab, 07/03/2020 alle 10.11 -0800, er...@ericheickmeyer.com ha scritto: > On Sat, 2020-03-07 at 19:04 +0100, Guido Aulisi wrote: > > Hi Erich, > > I took lv2-x42-plugins, because I've been maintaining it for the > > latest > > time, I'm currently maintaining some audio relatede packages, so we > > could collaborate. > > > > Ciao > > Guido > > > > FAS: tartina > > Thanks, Guido > > You beat me to it by mere seconds. I actually have a working > relationship with Robin Gareus (x42) so I was looking forward to > taking > that one. > > Not sure if you knew, but I'm reviving the Fedora Jam project and am > the current leader of Ubuntu Studio. So, I'm no stranger to this > stuff. > :) I added you to the commit group of lv2-x42-plugins, so you can (co)maintain Robin's plugins. Ciao Guido ___ 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: Pantheon is not present in gouplist
On Sat, Mar 07, 2020 at 11:00:40PM +0530, Harsh Jain wrote: > I did dnf grouplist -v and the output was > > Available Environment Groups: >Fedora Custom Operating System (custom-environment) >Minimal Install (minimal-environment) >Fedora Server Edition (server-product-environment) >Fedora Workstation (workstation-product-environment) >Fedora Cloud Server (cloud-server-environment) >KDE Plasma Workspaces (kde-desktop-environment) >Xfce Desktop (xfce-desktop-environment) >LXDE Desktop (lxde-desktop-environment) >LXQt Desktop (lxqt-desktop-environment) >Cinnamon Desktop (cinnamon-desktop-environment) >MATE Desktop (mate-desktop-environment) >Sugar Desktop Environment (sugar-desktop-environment) >Deepin Desktop (deepin-desktop-environment) >Development and Creative Workstation (developer-workstation-environment) >Web Server (web-server-environment) >Infrastructure Server (infrastructure-server-environment) >Basic Desktop (basic-desktop-environment) > > which does not include the Pantheon desktop environment ,how does it work? > how can i fix it ? Groups are controlled from the fedora-comps repo: https://pagure.io/fedora-comps/ The "Pantheon Desktop" is marked: false which is normal, you normally want a regular group that is just the desktop and then an environment group that includes all the other groups needed to make things work... Look at the xfce-desktop group. It has just the base Xfce stuff in it, there's also a xfce-apps and xfce-plugins and so forth. Then, the environment group has base-x, standard, core, xfce-desktop and xfce-apps and xfce-extra-plugins as optional groups. So, to fix this you need an environment group. You can submit a PR on the above project or if you like file a bug on fedora-comps and try and get someone to find the time to create one for you. :) Hope that helps, Side note: you can do 'dnf grouplist -v hidden' to find all the groups, hidden or not. 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: gpg check failure installing from rawhide
On Sat, Mar 07, 2020 at 09:47:03AM -0500, Sam Varshavchik wrote: > Trying to follow the direction for a bug report against kernel, and install > the latest kernel from rawhide. > > The Bugzilla template says: > > 5. Does this problem occur with the latest Rawhide kernel? To install the > Rawhide kernel, run “sudo dnf install fedora-repos-rawhide“ followed by > “sudo dnf update --enablerepo=rawhide kernel“: > > On F31, right now, 'dnf update --enablerepo=rawhide kernel' wants to install > 5.6.0-0.rc4.git0.1.fc33, which fails the gpg check: > > Public key for kernel-core-5.6.0-0.rc4.git0.1.fc33.x86_64.rpm is not > installed. Failing package is: kernel-core-5.6.0-0.rc4.git0.1.fc33.x86_64 > GPG Keys are configured as: > file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64 > > So, something, somewhere, needs to be fixed, either the Bugzilla template, > or something related to signing. Hum, yeah, thats a though one. I guess the better command might be: sudo dnf update --releasever 33 --enablerepo rawhide kernel but of course there's no way to know '33' is right there unless you know. This could be made better moving forward when we land the 'rawhide' is called 'rawhide' and not the number change. 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: Major issues with build overrides
On Sat, Mar 07, 2020 at 02:51:21PM +0100, Vitaly Zaitsev via devel wrote: > Hello all. > > I think Fedora Koji has major issues with build overrides now. > > Previously I waited only 5-10 minutes and then started building my > packages. But during the last month I need to wait more than 2 hours for > a single build override. This is absolutely unacceptable. As noted on irc when you asked there: https://pagure.io/releng/issue/9299 basically Igor has a ton of side tags, so kojira is always regenerating those. It's likely a mistake, but we don't want to just remove them and mess up his work either. So, please have some patience and we will get it sorted out. 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
Fedora-IoT-32-20200307.0 compose check report
Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Soft failed openQA tests: 2/8 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-32-20200305.0): ID: 536139 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/536139 ID: 536140 Test: x86_64 IoT-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/536140 Passed openQA tests: 6/8 (x86_64) Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: 53 services(s) added since previous compose: ModemManager.service, NetworkManager.service, auditd.service, chronyd.service, dbus-broker.service, dracut-shutdown.service, firewalld.service, getty@tty1.service, getty@tty3.service, getty@tty4.service... 54 services(s) removed since previous compose: ModemManager.service, NetworkManager.service, auditd.service, chronyd.service, dbus-broker.service, dracut-shutdown.service, firewalld.service, getty@tty1.service, getty@tty3.service, getty@tty4.service... Previous test data: https://openqa.fedoraproject.org/tests/534129#downloads Current test data: https://openqa.fedoraproject.org/tests/536139#downloads Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default@uefi: 54 services(s) added since previous compose: ModemManager.service, NetworkManager.service, auditd.service, chronyd.service, dbus-broker.service, dbxtool.service, dracut-shutdown.service, firewalld.service, getty@tty1.service, getty@tty3.service... 56 services(s) removed since previous compose: ModemManager.service, NetworkManager.service, auditd.service, chronyd.service, dbus-broker.service, dbxtool.service, dracut-shutdown.service, firewalld.service, getty@tty1.service, getty@tty3.service... Previous test data: https://openqa.fedoraproject.org/tests/534130#downloads Current test data: https://openqa.fedoraproject.org/tests/536140#downloads -- 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://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: Pantheon is not present in gouplist
Sat, Mar 7, 2020 at 6:30 PM Harsh Jain wrote: > > I did dnf grouplist -v and the output was > > Available Environment Groups: >Fedora Custom Operating System (custom-environment) >Minimal Install (minimal-environment) >Fedora Server Edition (server-product-environment) >Fedora Workstation (workstation-product-environment) >Fedora Cloud Server (cloud-server-environment) >KDE Plasma Workspaces (kde-desktop-environment) >Xfce Desktop (xfce-desktop-environment) >LXDE Desktop (lxde-desktop-environment) >LXQt Desktop (lxqt-desktop-environment) >Cinnamon Desktop (cinnamon-desktop-environment) >MATE Desktop (mate-desktop-environment) >Sugar Desktop Environment (sugar-desktop-environment) >Deepin Desktop (deepin-desktop-environment) >Development and Creative Workstation (developer-workstation-environment) >Web Server (web-server-environment) >Infrastructure Server (infrastructure-server-environment) >Basic Desktop (basic-desktop-environment) > > which does not include the Pantheon desktop environment ,how does it work? > how can i fix it ? This is interesting ... "dnf group install 'Pantheon Desktop'" works, but the group is not included with "dnf group list" ... No idea what's going wrong there. 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
Two flaws in upcoming Gnome 3.36
Fixed https://bodhi.fedoraproject.org/updates/FEDORA-2020-bcd6554797 https://src.fedoraproject.org/rpms/cogl/c/a0efb472ea19505f100effde4d60a6182fd3161d?branch=master ___ 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
Fedora-32-20200307.n.0 compose check report
No missing expected images. Failed openQA tests: 18/171 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-32-20200306.n.1): ID: 536042 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/536042 ID: 536094 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/536094 Old failures (same test failed in Fedora-32-20200306.n.1): ID: 535988 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/535988 ID: 536014 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/536014 ID: 536021 Test: x86_64 Workstation-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/536021 ID: 536038 Test: x86_64 KDE-live-iso desktop_background URL: https://openqa.fedoraproject.org/tests/536038 ID: 536045 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/536045 ID: 536054 Test: x86_64 Silverblue-dvd_ostree-iso desktop_background URL: https://openqa.fedoraproject.org/tests/536054 ID: 536057 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/536057 ID: 536073 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/536073 ID: 536074 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/536074 ID: 536083 Test: x86_64 universal install_software_raid URL: https://openqa.fedoraproject.org/tests/536083 ID: 536084 Test: x86_64 universal install_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/536084 ID: 536091 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/536091 ID: 536096 Test: x86_64 universal install_blivet_software_raid URL: https://openqa.fedoraproject.org/tests/536096 ID: 536099 Test: x86_64 universal install_blivet_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/536099 ID: 536124 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/536124 ID: 536132 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/536132 ID: 536137 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/536137 Soft failed openQA tests: 17/171 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-32-20200306.n.1): ID: 536131 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/536131 ID: 536138 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/536138 Old soft failures (same test soft failed in Fedora-32-20200306.n.1): ID: 535966 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/535966 ID: 535967 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/535967 ID: 535969 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/535969 ID: 535971 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/535971 ID: 535974 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/535974 ID: 535975 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/535975 ID: 535995 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/535995 ID: 536024 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/536024 ID: 536026 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/536026 ID: 536058 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/536058 ID: 536067 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/536067 ID: 536085 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/536085 ID: 536120 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/536120 ID: 536123 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/536123 ID: 536130 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/536130 Passed openQA tests: 136/171 (x86_64) New passes (same test not passed in Fedora-32-20200306.n.1): ID: 535990 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/535990 ID: 536047 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL:
[Bug 1797039] Please build perl-Data-Validate-IP for EPEL8
https://bugzilla.redhat.com/show_bug.cgi?id=1797039 Scott Talbert changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|fedora...@rule.lv |s...@techie.net -- 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
Re: Orphaned packages
On Sat, 2020-03-07 at 19:04 +0100, Guido Aulisi wrote: > Hi Erich, > I took lv2-x42-plugins, because I've been maintaining it for the > latest > time, I'm currently maintaining some audio relatede packages, so we > could collaborate. > > Ciao > Guido > > FAS: tartina Thanks, Guido You beat me to it by mere seconds. I actually have a working relationship with Robin Gareus (x42) so I was looking forward to taking that one. Not sure if you knew, but I'm reviving the Fedora Jam project and am the current leader of Ubuntu Studio. So, I'm no stranger to this stuff. :) Thanks, Erich - Erich Eickmeyer Fedora Jam ___ 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: Donate 1 minute of your time to test upgrades from F31 to F32
On Fri, 2020-03-06 at 09:47 -0800, Adam Williamson wrote: > On Fri, 2020-03-06 at 18:07 +0100, jeandet wrote: > > Hello, > > > > I did an upgrade last week, with: > > sudo dnf system-upgrade download --refresh --releasever=32 > > Except for modules everything was ok on my laptop, but I got some > > issues on my desktop. > > On my laptop, from fc32 running: > > sudo dnf module reset '*' > > sudo dnf --releasever=32 --setopt=module_platform_id=platform:f32 \ > > --enablerepo=updates-testing --enablerepo=updates-testing-modular \ > > distro-sync > > did solve the modules warnings. > > > > > > On my desktop: > > > > "/dev/disk/by-uuid" wasn't and still isn't populated with soft raid > > volumes, I had to change fstab to point to /dev/mdXXXpX to mount my > > home and other needed folders. From cockpit it also says "Unrecognized > > Data" for all my mdraid partitions. > > > > I didn't have time to investigate more, so I jump into this mail to ask > > against which package should I report a bug? I have no idea who fills > > "/dev/disk/by-uuid". > > systemd (well, udev, which is part of systemd these days). It should be > done by /usr/lib/udev/rules.d/60-persistent-storage.rules , which is > part of systemd-udev. I wonder if it's possibly an issue that that runs > before /usr/lib/udev/rules.d/65-md-incremental.rules , but I'm just > guessing there... Aha, I think I found your bug: https://bugzilla.redhat.com/show_bug.cgi?id=1809117 that's probably what you're hitting. -- 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://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: Orphaned packages
Il giorno sab, 07/03/2020 alle 09.08 -0800, er...@ericheickmeyer.com ha scritto: > Hi Brendan, > > On Sat, 2020-03-07 at 09:10 +0100, Brendan Jones wrote: > > Hello, > > > > the following packages have been orphaned and require a primary > > maintainer. Feel free to take them over > > > > Add64 > > aj-snapshot > > ambdec > > dssi > > dssi-vst > > gluidsynth > > fluidsynth-dssi > > freq-tweak > > fst > > giada > > gnome-guitar > > harmony-seq > > hexter-dssi > > jackctlmmc > > jmeters > > ladish > > libinstpatch > > lv2-artyfx-plugins > > lv2-avw-plugins > > lv2-c++-tools > > lv2-fabla > > lv2-fomp-plugins > > lv2-mdaEPiano > > lv2-mdala-plugins > > lv2-newtonator > > lv2-sorcer > > lv2-swh-plugins > > lv2-triceratops > > lv2-vocoder-plugins > > lv2-x42-plugins > > meterbridge > > mxml > > nekobee-dssi > > non-daw > > non-session-manager > > portmidi > > radium-compressor > > realTimeConfigQuickScan > > seq24 > > soundtracker > > whysynth-dssi > > xsynth-dssi > > > > I realize we recently had a discussion about me taking just the > fedora-jam-* stuff, but I will likely take all of these. Anything > that is dead upstream and FTBFS I'll likely be retiring. For anything > that is alive upstream and FTBFS I'll work hard to get fixed. Thanks! > > Erich Hi Erich, I took lv2-x42-plugins, because I've been maintaining it for the latest time, I'm currently maintaining some audio relatede packages, so we could collaborate. Ciao Guido FAS: tartina signature.asc Description: This is a digitally signed message part ___ 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
Pantheon is not present in gouplist
I did dnf grouplist -v and the output was Available Environment Groups: Fedora Custom Operating System (custom-environment) Minimal Install (minimal-environment) Fedora Server Edition (server-product-environment) Fedora Workstation (workstation-product-environment) Fedora Cloud Server (cloud-server-environment) KDE Plasma Workspaces (kde-desktop-environment) Xfce Desktop (xfce-desktop-environment) LXDE Desktop (lxde-desktop-environment) LXQt Desktop (lxqt-desktop-environment) Cinnamon Desktop (cinnamon-desktop-environment) MATE Desktop (mate-desktop-environment) Sugar Desktop Environment (sugar-desktop-environment) Deepin Desktop (deepin-desktop-environment) Development and Creative Workstation (developer-workstation-environment) Web Server (web-server-environment) Infrastructure Server (infrastructure-server-environment) Basic Desktop (basic-desktop-environment) which does not include the Pantheon desktop environment ,how does it work? how can i fix it ? ___ 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
Fedora 32 compose report: 20200307.n.0 changes
OLD: Fedora-32-20200306.n.1 NEW: Fedora-32-20200307.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:1 Upgraded packages: 47 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:183.05 MiB Size of upgraded packages: 668.65 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -16.00 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = Package: vegastrike-music-0.5.1-15.r1.fc32 Summary: Music for Vega Strike RPMs:vegastrike-music vegastrike-speech Size:183.05 MiB = UPGRADED PACKAGES = Package: adwaita-icon-theme-3.35.92-1.fc32 Old package: adwaita-icon-theme-3.35.91-1.fc32 Summary: Adwaita icon theme RPMs: adwaita-cursor-theme adwaita-icon-theme adwaita-icon-theme-devel Size: 11.27 MiB Size change: 43.56 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 3.35.92-1 - Update to 3.35.92 Package: anaconda-32.24.2-2.fc32 Old package: anaconda-32.24.2-1.fc32 Summary: Graphical system installer RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui anaconda-install-env-deps anaconda-live anaconda-tui anaconda-widgets anaconda-widgets-devel Size: 19.26 MiB Size change: -167.30 KiB Changelog: * Wed Mar 04 2020 Martin Kolman - 32.24.2-2 - Check free space in the correct device tree (#1807339) (vponcova) - Handle invalid optical install media (#1806520) (vponcova) Package: at-spi2-atk-2.34.2-1.fc32 Old package: at-spi2-atk-2.34.1-2.fc32 Summary: A GTK+ module that bridges ATK to D-Bus at-spi RPMs: at-spi2-atk at-spi2-atk-devel Size: 595.92 KiB Size change: 1.89 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 2.34.2-1 - Update to 2.34.2 Package: at-spi2-core-2.35.92-1.fc32 Old package: at-spi2-core-2.35.1-2.fc32 Summary: Protocol definitions and daemon for D-Bus at-spi RPMs: at-spi2-core at-spi2-core-devel Size: 1.79 MiB Size change: -603 B Changelog: * Mon Mar 02 2020 Kalev Lember - 2.35.92-1 - Update to 2.35.92 Package: clutter-1.26.2-11.fc32 Old package: clutter-1.26.2-10.fc32 Summary: Open Source software library for creating rich graphical user interfaces RPMs: clutter clutter-devel clutter-doc clutter-tests Size: 12.62 MiB Size change: -2.89 KiB Changelog: * Tue Mar 03 2020 Kalev Lember - 1.26.2-11 - Backport fixes for 10-bit color (#1800865) Package: eog-3.35.92-1.fc32 Old package: eog-3.35.91-1.fc32 Summary: Eye of GNOME image viewer RPMs: eog eog-devel eog-tests Size: 20.27 MiB Size change: 4.96 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 3.35.92-1 - Update to 3.35.92 Package: epiphany-1:3.35.92-1.fc32 Old package: epiphany-1:3.35.91-1.fc32 Summary: Web browser for GNOME RPMs: epiphany epiphany-runtime Size: 29.74 MiB Size change: -3.75 MiB Changelog: * Mon Mar 02 2020 Kalev Lember - 1:3.35.92-1 - Update to 3.35.92 Package: fedora-repos-32-0.7 Old package: fedora-repos-32-0.6 Summary: Fedora package repositories RPMs: fedora-gpg-keys fedora-repos fedora-repos-ostree fedora-repos-rawhide Size: 129.60 KiB Size change: 419 B Changelog: * Sat Feb 22 2020 Neal Gompa - 32-0.7 - Enable fedora-cisco-openh264 repo by default - Dont pull in fedora-repos-rawhide (mohanboddu) Package: file-roller-3.35.92-1.fc32 Old package: file-roller-3.35.91-1.fc32 Summary: Tool for viewing and creating archives RPMs: file-roller file-roller-nautilus Size: 4.18 MiB Size change: 7.06 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 3.35.92-1 - Update to 3.35.92 Package: four-in-a-row-3.35.92-1.fc32 Old package: four-in-a-row-3.35.91-1.fc32 Summary: GNOME Four-in-a-row game RPMs: four-in-a-row Size: 2.82 MiB Size change: -46.34 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 3.35.92-1 - Update to 3.35.92 Package: geary-3.35.90-1.fc32 Old package: geary-3.35.2-2.fc32 Summary: A lightweight email program designed around conversations RPMs: geary Size: 21.43 MiB Size change: 3.94 MiB Changelog: * Mon Mar 02 2020 Kalev Lember - 3.35.90-1 - Update to 3.35.90 Package: gjs-1.63.92-1.fc32 Old package: gjs-1.63.91-1.fc32 Summary: Javascript Bindings for GNOME RPMs: gjs gjs-devel gjs-tests Size: 3.46 MiB Size change: 23.89 KiB Changelog: * Mon Mar 02 2020 Kalev Lember - 1.63.92-1 - Update to 1.63.92 Package: glib-networking-2.63.92-1.fc32 Old package: glib-networking-2.63.91-1.fc32 Summary: Networking support for GLib RPMs: glib-networking glib-networking-tests Size: 1.40 MiB Size change: -340 B Changelog: * Mon Mar 02 2020 Kalev Lember - 2.63.92-1
Re: Orphaned packages
Hi Brendan, On Sat, 2020-03-07 at 09:10 +0100, Brendan Jones wrote: > Hello, > the following packages have been orphaned and require a primary > maintainer. Feel free to take them over > > Add64 > aj-snapshot > ambdec > dssi > dssi-vst > gluidsynth > fluidsynth-dssi > freq-tweak > fst > giada > gnome-guitar > harmony-seq > hexter-dssi > jackctlmmc > jmeters > ladish > libinstpatch > lv2-artyfx-plugins > lv2-avw-plugins > lv2-c++-tools > lv2-fabla > lv2-fomp-plugins > lv2-mdaEPiano > lv2-mdala-plugins > lv2-newtonator > lv2-sorcer > lv2-swh-plugins > lv2-triceratops > lv2-vocoder-plugins > lv2-x42-plugins > meterbridge > mxml > nekobee-dssi > non-daw > non-session-manager > portmidi > radium-compressor > realTimeConfigQuickScan > seq24 > soundtracker > whysynth-dssi > xsynth-dssi > I realize we recently had a discussion about me taking just the fedora- jam-* stuff, but I will likely take all of these. Anything that is dead upstream and FTBFS I'll likely be retiring. For anything that is alive upstream and FTBFS I'll work hard to get fixed. Thanks! Erich ___ 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
Two flaws in upcoming Gnome 3.36
Hi,
*Disclaimer*:
The main propose of this email is only to flag some issues or to form some
vectors/conclusions /necessary actions.
*1) cogl does not build*
https://koji.fedoraproject.org/koji/buildinfo?buildID=1434712
Looks like cogl library is more or less dead or at least kind of dead end.
https://gitlab.gnome.org/GNOME/cogl/
cogl is used by at least by clutter, clutter-gst, libchamplain which are
used by cheese, gnome-maps, libchamplain which are then used by
gnome-contacts, gnome-control-center, gnome-initial-setup and so on ..
I've been trying to flag this in
https://gitlab.gnome.org/GNOME/cogl/issues/11
In that ticket, it is possible to find some links to other gnome components
tickets maintainers of which I've been trying to ask about the current
situation/find a workable solution.
So far .. no useful results.
Gnome mutter has own cogl and clutter copies but seems it has been bend not
to be useful outside of the mutter.
I think that it would be good to invest some time to at least bring cogl to
cleanly building state than some desktop developers should discuss on how
to approach to cogl/clutter code from long term perspective.
*2) Almost all gnome translations are not-up-to-date.*
As long as cogl issue is related to only a few gnome components, I just
realised that this issue stretches wy beyond the gnome.
Despite huge effort of all translators around the world almost all gnome
packages have not updated/properly maintained translations :(
All because one small issue that most of the source code maintainers
literally *never* executed "make -C update-po" or in case of meson using
projects "meson -update-po" then commit all changes generated
changes to source tree to inform translators that they have something to
update.
The same is in case of gnome help files ("meson help--update-po"
target).
All this happens because all frameworks helping maintain translations are
basing only on .po files, and all translations updates are maintained
*outside* original source tree.
To update .po files new .pot file needs to be generated (which contains
generated list of untranslated strings to translate) then combining .po and
.pot file new/updated .po file is generated adding new strings or
commenting out all those entries which need to be updated.
More or less current result of above is that almost all projects which have
.mo files after call during build *update-po targets are .. **SMALLER**!!
All this because i most of the cases many strings which are no longer used
in current code version are still in .po files, and they are populated to
end packages .mo files.
When I found the above I've been thinking for a quite long time was only:
**How to solve this class of issue with minimum effort?**
(Because this issue is affecting now thousands of projects .. not only
gnome one).
After many months have yellow post-it card note on the back of my skull I
think that that I have kind of idea what to change/heal this not-so-good
situation instantly with that minimum effort.
That is about "what?" or identification of the issue.
So now next question is only "how?".
*** I think that meson, gettext and cmake need to be changed. ***
*Explanation:*
Part of the execution of the meson "dist" or in case automake "dist" or/and
"distcheck" targets should be IMO calling meson "*-update-po" and automake
"make -C po update-po" bits.
With that whoever will be doing code release will have in VCS trees
modified file which should be committed.
Similar changes it would be good to apply as well for cmake i18n support.
In case of automake/autoconf all files which needs to be updated art part
of the gettext.
With that relatively smalll set changes, I think that chances to have 100%
up-to-date translations in any projects will grow dramatically.
When I've been working on shadow source tree usually few days before actual
release, I've been commuting all .po files updates and sending kind of
broadcast message to all translators to have a look on all current .po
files and send me updates.
I think that something like this should be part of the open-source
development cycle methodology/habits.
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
___
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: Non-responsive maintainer: pocock
On 07/03/2020 10:32, Julian Sikorski wrote: > W dniu 06.03.2020 o 19:21, Daniel Pocock pisze: >> >> >> On 05/03/2020 21:26, Julian Sikorski wrote: >> >>> I would like to take this opportunity to remind about the PR that I have >>> prepared - let us not duplicate the work: >>> https://src.fedoraproject.org/rpms/asio/pull-request/1 >>> I have rebuilt all asio's dependencies and only encountered issues with >>> abiword and OpenSceneGraph - both were complaining about error not being >>> a member of asio::placeholders. Same issues were found by gentoo, I have >>> linked the relevant bug reports in the PR. Is this something you would >>> be able to advise about? I am happy to share full build logs if needed. >> >> I haven't personally looked at asio 1.14.0 yet so I don't have the >> solution off the top of my head. These are the type of issues I >> normally deal with in upstream development. >> >> From a strategic perspective, I feel it is most efficient to try and >> coordinate with the upstreams and other distributions so that everybody >> is supporting the same asio in each of the major distributions. >> >> In any C++ library, there are small API changes from time to time >> leading to the type of problem you describe. >> > If upstreams are using travis-ci, we are testing against version 1.12.2 >> from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even >> if you patch for the issue, it may be completely untested upstream. >> That is why it is so vital to resolve the Debian/Ubuntu lag. >> > I do not know what Debian's issues regarding update to 1.14.0 were, but > from what you are saying it appears someone at Debian lost their cool. Did you know the Debian Project Leader sent an abusive email shortly after my father died? Did you know that this wasn't the first time that I saw abusive communications from somebody in Debian leadership at an acute time of personal tragedy? Just imagine if a Fedora volunteer's family member dies and a Red Hat manager creeps up on them at the funeral and tasers the volunteer while other Red Hat staff record the reaction on a smartphone video and post it online. How long would the repercussions continue after such an abuse? Would it be right to keep hosting the video indefinitely on Fedora platforms? If that volunteer feels their family's privacy is being violated as long as it is perpetuated, would you have no empathy for them? When I saw the UN's recent report[1] on Cybertorture, Debian was the first thing on my mind. Humiliating and shaming people, Debian's go-to solutions, are high on their list of abuses. > In any case, Fedora is a more bleeding edge distro than Debian/Ubuntu > (First one of the foundations), so I am not sure how realistic it is to > be waiting for Debian/Ubuntu to include something before we can do it in > Fedora. Debian unstable/sid is similarly bleeding edge to rawhide Having the same dependencies in Debian sid and Fedora rawhide makes life easier for everybody: library maintainers, upstreams and package maintainers. I've always tried to work that way, that is the very reason I volunteered to maintain asio in both Debian and Fedora. I also put the necessary effort into supporting Debian backports and Fedora EPEL so these things could be widely available. > I was able to fix abiword completely by adding -DASIO_ENABLE_BOOST to > CXXFLAGS, OSG still fails further down the line due to get_io_service() > having been removed. I have filed upstream issues for both projects, > details in the PR. Thanks for your attention to detail with that >> Is there a convenient way for upstreams to make CI builds on the latest >> Fedora rawhide in parallel with our travis-ci Ubuntu builds? >> > I am not aware of a ci service using Fedora, both appveyor and travis > appear to be using ubuntu. I have some ideas about how to address this There is a similar script to use Docker inside travis-ci, using Docker for a pure Debian sid build, rather than the default Ubuntu environment: https://travis.debian.net/ Could a Fedora equivalent exist? Maybe OBS could also be relevant: https://openbuildservice.org/ Regards, Daniel 1. https://www.theguardian.com/law/2020/feb/21/un-rapporteur-warns-of-rise-of-cybertorture-to-bypass-physical-ban ___ 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: Reducing broken dependencies in fedora (32) repositories
On Sat, Mar 7, 2020, 15:05 Richard Shaw wrote: > Are the broken source dependencies real? > > >- python-pyside2 (src): > - qt5-qtwebengine-devel > 5.13 > > I just checked koji and qt5-qtwebengine 5.13.2 is in f32 which should meet > the requirement. > This looks like a case of either Caeat 1 or Caveat 2 listed above. Is python-pyside2 a "noarch package with imported dependencies"? I tried to whitelist all qtwebengine related false positives, but I might have missed this one. Fabio > 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://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] Fedora 32 Branched 20200307.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 32 Branched 20200307.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20200225.n.0: anaconda-32.24.2-1.fc32.src, 20200307.n.0: anaconda-32.24.2-2.fc32.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/32 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200307.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ 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
gpg check failure installing from rawhide
Trying to follow the direction for a bug report against kernel, and install the latest kernel from rawhide. The Bugzilla template says: 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run “sudo dnf install fedora-repos-rawhide“ followed by “sudo dnf update --enablerepo=rawhide kernel“: On F31, right now, 'dnf update --enablerepo=rawhide kernel' wants to install 5.6.0-0.rc4.git0.1.fc33, which fails the gpg check: Public key for kernel-core-5.6.0-0.rc4.git0.1.fc33.x86_64.rpm is not installed. Failing package is: kernel-core-5.6.0-0.rc4.git0.1.fc33.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31- x86_64 So, something, somewhere, needs to be fixed, either the Bugzilla template, or something related to signing. pgpY9zzIiGkep.pgp 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: Non-responsive maintainer: pocock
On Sat, Mar 7, 2020 at 9:02 AM Julian Sikorski wrote: > > W dniu 07.03.2020 o 13:53, Neal Gompa pisze: > > On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: > >> > >> > >> If upstreams are using travis-ci, we are testing against version 1.12.2 > >> from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even > >> if you patch for the issue, it may be completely untested upstream. > >> That is why it is so vital to resolve the Debian/Ubuntu lag. > >> > >> Is there a convenient way for upstreams to make CI builds on the latest > >> Fedora rawhide in parallel with our travis-ci Ubuntu builds? > >> > > > > If you're okay with using containers in your CI, it's relatively > > straightforward to do so. > > > > Here's an example of doing Fedora and CentOS builds in Travis CI: > > https://github.com/rpm-software-management/librpm.rs/blob/master/.travis.yml > > > The problem with this approach is that every downstream dependency of > asio would have to adopt the container approach. Not sure how > practicable that is. > Ideally Travis would adopt Fedora in addition to macOS and Ubuntu. > Well, anyone know anybody at Travis CI that we'd talk to about doing that? Unfortunately, I don't... -- 真実はいつも一つ！/ 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: Reducing broken dependencies in fedora (32) repositories
Are the broken source dependencies real? - python-pyside2 (src): - qt5-qtwebengine-devel > 5.13 I just checked koji and qt5-qtwebengine 5.13.2 is in f32 which should meet the requirement. 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://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: Non-responsive maintainer: pocock
W dniu 07.03.2020 o 13:53, Neal Gompa pisze: On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: If upstreams are using travis-ci, we are testing against version 1.12.2 from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even if you patch for the issue, it may be completely untested upstream. That is why it is so vital to resolve the Debian/Ubuntu lag. Is there a convenient way for upstreams to make CI builds on the latest Fedora rawhide in parallel with our travis-ci Ubuntu builds? If you're okay with using containers in your CI, it's relatively straightforward to do so. Here's an example of doing Fedora and CentOS builds in Travis CI: https://github.com/rpm-software-management/librpm.rs/blob/master/.travis.yml The problem with this approach is that every downstream dependency of asio would have to adopt the container approach. Not sure how practicable that is. Ideally Travis would adopt Fedora in addition to macOS and Ubuntu. Best regards, Julian ___ 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
Major issues with build overrides
Hello all. I think Fedora Koji has major issues with build overrides now. Previously I waited only 5-10 minutes and then started building my packages. But during the last month I need to wait more than 2 hours for a single build override. This is absolutely unacceptable. -- 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://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: Non-responsive maintainer: pocock
On Fri, Mar 6, 2020 at 1:21 PM Daniel Pocock wrote: > > > If upstreams are using travis-ci, we are testing against version 1.12.2 > from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even > if you patch for the issue, it may be completely untested upstream. > That is why it is so vital to resolve the Debian/Ubuntu lag. > > Is there a convenient way for upstreams to make CI builds on the latest > Fedora rawhide in parallel with our travis-ci Ubuntu builds? > If you're okay with using containers in your CI, it's relatively straightforward to do so. Here's an example of doing Fedora and CentOS builds in Travis CI: https://github.com/rpm-software-management/librpm.rs/blob/master/.travis.yml -- 真実はいつも一つ！/ 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
Fedora-Cloud-31-20200307.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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://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: Announcing start of DNF 5 development
> > Hello everyone, > > I'm pleased to announce start of DNF 5 development. We are planning to > > deliver a module stream or a COPR repo during Fedora 33 development for > > early adopters and tool developers and we're hoping in getting a stable > > version into Fedora 34. > > > > Can it be: > 1. faster > 2. have a better dnf history (like one we could interact with) > > > Also I still don't understand why my dnf redownloads the repolist almost > everytime I use it for a search. I thought thiswas supposed to be fixed with > delta repo or zchunk something. This past is the really slow one. It also regularly downloads the entire cache again even if the cache is not very old. Things like a "dnf repoquery --whatrequires" pretty much is guaranteed to re-dowload the cache again even if a repoquery commands was only run a few minutes earlier. ___ 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: Schedule for Mondays's FESCo Meeting (2020-03-09) -- mind the time change in North America
On 07. 03. 20 0:44, Miro Hrončok wrote: Following is the list of topics that will be discussed in the FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on irc.freenode.net. #topic #2346 Python 2 exception for IceCat https://pagure.io/fesco/issue/2346#comment-629268 (blanket Python 2 BuildRequirs exception extension for Fedora 33) The proposal for the blanket exception was withdrawn and will not be on the agenda. -- 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://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: Unannounced SONAME bump: librealsense
Hi Fabio, On 3/6/20 9:13 PM, Fabio Valentini wrote: > Hi everybody, > > librealsense (maintainers in CC) bumped the SONAME of its shipped > library with the latest update, and (at least some) dependent packages > have not been rebuilt (including fawkes, maintainers in CC). Thanks for the reminder, I happen to be maintainer of both. Fawkes is the only package depending on librealsense, announcing an SONAME bump to myself didn't seem like something particularly useful. I've rebuilt fawkes. Kind regards, Till ___ 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: SCons help
On 07.03.20 00:33, Sandro Mani wrote: I highly suspect this is a python3 incompatibility in the SConstruct file shipped by mingw-nsis [1], as even replicating exactly the same commands which are executed for this debian package build [2], I'm stuck with this error. The difference that sticks out is that this debian package was built using python2-scons, whereas I'm using python3-scons. Looks to me like the install targets are not properly registered? I've tracked it down, was indeed a python issue. ___ 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: Non-responsive maintainer: pocock
W dniu 06.03.2020 o 19:21, Daniel Pocock pisze: On 05/03/2020 21:26, Julian Sikorski wrote: I would like to take this opportunity to remind about the PR that I have prepared - let us not duplicate the work: https://src.fedoraproject.org/rpms/asio/pull-request/1 I have rebuilt all asio's dependencies and only encountered issues with abiword and OpenSceneGraph - both were complaining about error not being a member of asio::placeholders. Same issues were found by gentoo, I have linked the relevant bug reports in the PR. Is this something you would be able to advise about? I am happy to share full build logs if needed. I haven't personally looked at asio 1.14.0 yet so I don't have the solution off the top of my head. These are the type of issues I normally deal with in upstream development. From a strategic perspective, I feel it is most efficient to try and coordinate with the upstreams and other distributions so that everybody is supporting the same asio in each of the major distributions. In any C++ library, there are small API changes from time to time leading to the type of problem you describe. > If upstreams are using travis-ci, we are testing against version 1.12.2 from Debian/Ubuntu and may not be aware of issues in asio 1.14.0. Even if you patch for the issue, it may be completely untested upstream. That is why it is so vital to resolve the Debian/Ubuntu lag. I do not know what Debian's issues regarding update to 1.14.0 were, but from what you are saying it appears someone at Debian lost their cool. In any case, Fedora is a more bleeding edge distro than Debian/Ubuntu (First one of the foundations), so I am not sure how realistic it is to be waiting for Debian/Ubuntu to include something before we can do it in Fedora. I was able to fix abiword completely by adding -DASIO_ENABLE_BOOST to CXXFLAGS, OSG still fails further down the line due to get_io_service() having been removed. I have filed upstream issues for both projects, details in the PR. Is there a convenient way for upstreams to make CI builds on the latest Fedora rawhide in parallel with our travis-ci Ubuntu builds? I am not aware of a ci service using Fedora, both appveyor and travis appear to be using ubuntu. Please also note that I have checked both fale and uwog's recent activity with fedora-active-user and neither seem to have been active lately. Thanks for this feedback. Dakota, do you want to be promoted to admin on asio? Is either of you happy to be co-maintainer of resiprocate with me? I opened an issue to unretire it. I do upstream releases and I run the latest version for fedrtc.org (using CentOS/EPEL) so it is important for me that it supports Fedora and any Fedora issues are given the attention they deserve during the release process. Regards, Daniel ___ 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
Fedora-Cloud-30-20200307.0 compose check report
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- 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://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 1811138] perl-Clipboard-0.24 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1811138 --- Comment #4 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perl-Clipboard-0.24-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=42279002 -- 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 1811138] perl-Clipboard-0.24 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1811138 --- Comment #3 from Upstream Release Monitoring --- Created attachment 1668281 --> https://bugzilla.redhat.com/attachment.cgi?id=1668281=edit [patch] Update to 0.24 (#1811138) -- 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 1811138] perl-Clipboard-0.24 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1811138 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Clipboard-0.23 is |perl-Clipboard-0.24 is |available |available --- Comment #2 from Upstream Release Monitoring --- Latest upstream release: 0.24 Current version/release in rawhide: 0.22-1.fc33 URL: http://search.cpan.org/dist/Clipboard/ 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/14091/ -- 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
Orphaned packages
Hello, the following packages have been orphaned and require a primary maintainer. Feel free to take them over Add64 aj-snapshot ambdec dssi dssi-vst gluidsynth fluidsynth-dssi freq-tweak fst giada gnome-guitar harmony-seq hexter-dssi jackctlmmc jmeters ladish libinstpatch lv2-artyfx-plugins lv2-avw-plugins lv2-c++-tools lv2-fabla lv2-fomp-plugins lv2-mdaEPiano lv2-mdala-plugins lv2-newtonator lv2-sorcer lv2-swh-plugins lv2-triceratops lv2-vocoder-plugins lv2-x42-plugins meterbridge mxml nekobee-dssi non-daw non-session-manager portmidi radium-compressor realTimeConfigQuickScan seq24 soundtracker whysynth-dssi xsynth-dssi regards Brendan ___ 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
