License change: golang-tinygo-x-llvm: NCSA -> ASL 2.0 and NCSA
Since this package is basically a copy of some sources in LLVM, this change is a reflection of the ongoing efforts to relicense LLVM to ASL 2.0, which are only partially complete. -- Elliott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938401] ack-3.5.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938401 --- Comment #7 from Fedora Update System --- FEDORA-2021-dba0a1e900 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-dba0a1e900` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-dba0a1e900 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-fc2f1ff74c x11vnc-0.9.16-3.el8 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1073219045 privoxy-3.0.32-1.el8 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-94317ce911 suricata-5.0.6-1.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6b1b1f9053 python-django-2.2.19-1.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-58f4d56777 zabbix40-4.0.29-1.el8 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-e9c2beec98 nagios-4.4.6-4.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-cd16d1b0bf upx-3.96-8.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9ca5d37fa8 chromium-89.0.4389.82-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing ansible-2.9.18-2.el8 goaccess-1.4.6-1.el8 t1lib-5.1.2-28.el8 ttf2pt1-3.4.4-32.el8 xwm-0.1.8-1.el8 Details about builds: ansible-2.9.18-2.el8 (FEDORA-EPEL-2021-e6533c0f44) SSH-based configuration management, deployment, and task execution system Update Information: Add rpm macros and generators ChangeLog: * Fri Mar 12 2021 Orion Poplawski - 2.9.18-2 - Add rpm macros and generators for collections goaccess-1.4.6-1.el8 (FEDORA-EPEL-2021-b789fb73bc) Real-time web log analyzer and interactive viewer Update Information: Update to 1.4.6 ChangeLog: References: [ 1 ] Bug #1933580 - goaccess-1.4.6 is available https://bugzilla.redhat.com/show_bug.cgi?id=1933580 t1lib-5.1.2-28.el8 (FEDORA-EPEL-2021-51f717630a) PostScript Type 1 font rasterizer Update Information: Add package t1lib to epel8. ChangeLog: References: [ 1 ] Bug #1891943 - Please build t1lib for EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1891943 ttf2pt1-3.4.4-32.el8 (FEDORA-EPEL-2021-cdbfc77592) TrueType to Adobe Type 1 font converter Update Information: First build for EPEL8 ChangeLog: References: [ 1 ] Bug #1891660 - Please build ttf2pt1 for EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1891660 xwm-0.1.8-1.el8 (FEDORA-EPEL-2021-f5766f5ea9) Tiny XCB floating window manager Update Information: Initial package Initial package ChangeLog: References: [ 1 ] Bug #1919701 - Review Request: xwm - Tiny XCB floating window manager https://bugzilla.redhat.com/show_bug.cgi?id=1919701 [ 2 ] Bug #1938587 - xwm-0.1.8 is available https://bugzilla.redhat.com/show_bug.cgi?id=1938587 ___ 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 Do not reply
[Bug 1938401] ack-3.5.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938401 --- Comment #6 from Fedora Update System --- FEDORA-2021-e76aea8efb has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e76aea8efb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e76aea8efb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1918130] perl-Gtk3-0.038 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1918130 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Gtk3-0.038-1.fc32 Resolution|RAWHIDE |ERRATA --- Comment #8 from Fedora Update System --- FEDORA-2021-5dac05f9c8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938614] New: perl-URI-Find-Simple-1.07 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938614 Bug ID: 1938614 Summary: perl-URI-Find-Simple-1.07 is available Product: Fedora Version: rawhide Status: NEW Component: perl-URI-Find-Simple 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: 1.07 Current version/release in rawhide: 1.06-19.fc34 URL: http://search.cpan.org/dist/URI-Find-Simple/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3486/ -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[389-devel] Re: 389 DS nightly 2021-03-14 - 95% PASS
You can unsubscribe by following the links at the bottom of these emails. > On 14 Mar 2021, at 20:47, JMM wrote: > > Stop > > Sent from my iPhone > >> On Mar 13, 2021, at 10:29 PM, vashi...@redhat.com wrote: >> >> https://fedorapeople.org/groups/389ds/ci/nightly/2021/03/14/report-389-ds-base-2.0.3-20210314gitd5fdea905.fc33.x86_64.html >> ___ >> 389-devel mailing list -- 389-devel@lists.fedoraproject.org >> To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure > ___ > 389-devel mailing list -- 389-devel@lists.fedoraproject.org > To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs, Australia ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
libravatar ported to Fedora's AWS
Hello, I have just finished port of libravatar.org service to server provided by Fedora. Big thanks to the Fedora project for sponsoring libravatar. Avatars in pagure.io, src.fp.o, Bodhi should now load much faster. Best regards! clime ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ELN composes on mirrors
On Sun, 2021-03-14 at 13:47 -0700, Kevin Fenzi wrote: > The eln composes (at least as far as I know) are done via ODCS > (on demand compose service) and are already available on the master > mirrors: > > https://dl.fedoraproject.org/odcs/production/ > (Although not via rsync currently). > > The big problem with mirroring them back in the past was that they > changed too quick. There's a compose every 3 hours I think. That > wouldn't be nearly enough time for our mirror network to keep up. > > Given that I expect the number of people who would sync this content is > so small, perhaps we could just leave them on master mirrors? > (we can enable rsync if you want... just put in a ticket). > If that proves to be too much load, we could perhaps try and sync them > to a s3 bucket or some other location? I just dont think our normal > mirror network would be a good fit here. Thanks! I'm ok with consuming these from the master mirror. I've filed https://pagure.io/fedora-infrastructure/issue/9730 to get rsync enabled for that endpoint. Once that's sorted out I'll setup a periodic sync, (daily or weekly, at least at the beginning), and republish the composes on https://mirror.facebook.net. Cheers Davide ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On 3/14/21 1:50 AM, Sandro Mani wrote: On 14.03.21 01:39, Orion Poplawski wrote: On 3/6/21 4:52 PM, Sandro Mani wrote: Hi I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. I'll rebuild the following dependent packages: gdl vtk I've added patches for proj 8 support to these packages and submitted builds in the side tag. Thanks a lot! Quick status update: Still needing porting are gdl, qmapshack and python-cartopy (and possibly pcl, which depends on VTK). I'm currently working on gdl which I believe does not require too much work to port. qmapshack OTOH is a very heavy proj user and I'll probably look at bundling proj for that one. python-cartopy has a small autogenerated Proj API via Cython files, I'll need to look into this into more detail (not familiar with Cython). Sandro - gdl should be all set. -- Orion Poplawski he/him/his - surely the least important thing about me Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938391] perl-App-Cmd-0.333 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938391 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-App-Cmd-0.332 is |perl-App-Cmd-0.333 is |available |available --- Comment #1 from Upstream Release Monitoring --- Latest upstream release: 0.333 Current version/release in rawhide: 0.332-1.fc35 URL: http://search.cpan.org/dist/App-Cmd/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/7401/ -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ELN composes on mirrors
On Sun, Mar 14, 2021 at 05:07:06PM +, Davide Cavalca via devel wrote: > I had filed https://github.com/fedora-eln/eln/issues/33 a while ago to > track documentation improvements around how to consume ELN composes. > > I'd like to take a step back and propose adding them to the mirror > network, akin to what we already do for Rawhide. This would make it > trivial to consume or mirror them locally (e.g. via rsync), without > having to hit ODCS directly. The only downside I can think of is that > it'd consume a bit more storage on the mirrors themselves. Thoughts? The eln composes (at least as far as I know) are done via ODCS (on demand compose service) and are already available on the master mirrors: https://dl.fedoraproject.org/odcs/production/ (Although not via rsync currently). The big problem with mirroring them back in the past was that they changed too quick. There's a compose every 3 hours I think. That wouldn't be nearly enough time for our mirror network to keep up. Given that I expect the number of people who would sync this content is so small, perhaps we could just leave them on master mirrors? (we can enable rsync if you want... just put in a ticket). If that proves to be too much load, we could perhaps try and sync them to a s3 bucket or some other location? I just dont think our normal mirror network would be a good fit here. 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ELN SIG First Meeting
On Sat, Mar 13, 2021 at 05:09:44PM -0800, Troy Dawson wrote:
>
> Sorry for coming late to the discussion. I took a week off and all
> sorts of things happened while I was gone.
That fast paced open source development. :)
> I believe Kevin and Smooge, and possibly even you Davide got this
> backwards. And I think if we do this right, this can be a thing.
>
> When we started ELN, one of the major promises was that it wouldn't
> interfere with regular Fedora work. That your average Fedora packager
> that didn't care about ELN, could continue to not care about ELN and
> nothing would change.
> I believe we (ELN SIG) should extend the same courtesy to EPEL and the
> EPEL community and packagers.
Do note that this isn't really the case currently, although I agree
thats the goal. Due to limitations of our notification system, Fedora
maintainers are getting build notices and such from ELN builds.
Or course hopefully we can fix that.
> The email discussion went in the direction of all the work that EPEL
> would need to do to create an ELN EPEL. But we (ELN SIG) shouldn't
> have expected that. We should have expected to do all the work.
>
> So, if we flip this around, where everything is on ELN, how would that work.
>
> We create a new Fedora target and tag: eln-extra (so people do NOT
> confuse it with real EPEL)
> eln-extra-build inherits from itself and eln-build
> If a package is built against the eln-extra target, and it is
> successful, it gets tagged with the eln-extra tag.
> There is a daily (or some other time period) repo creation. No
> images, just a repo, like epel.
Could be composed with eln? I think eln composes every 4 hours or
something?
> There is a list of packages, similar to the list of packages used to
> create the ELN list, on some github/gitlab/pagure repo. If you put a
> package on that list, you associate your name with that package.
> Just like ELN, when a package on the eln-extra list gets built in
> rawhide, it get's built in eln-extra. In fact, it would be best if we
> just altered the ELN trigger/periodic scripts to look at this list
> along with the regular ELN list.
>
> What are people's thoughts on this?
> No extra work on EPEL.
> If someone, or some company wants to test ELN and need packages not in
> ELN, they can add the packages to the list, with their name/company
> associated with that package.
> It would get built, put in the repo, and they can then run their ELN
> test with the package they need.
>
> Thoughts?
My concern is again maintainers/maintainace.
If there's problems building in eln-extra it either means the Fedora
maintainer(s) have to fix or at least review PR's for rawhide to fix the build
or the eln-extra maintainer(s) have to be co-maintainers or
provenpackagers.
ok, lets fast forward to when CentOS 10 stream exists. I'm guessing
there's going to be a push to mass branch all the things in eln-extra
for epel10-next? Again, who's maintainer there, the eln-extra maintainer(s),
or the fedora/epel maintainers?
And then there's when RHEL10 is released, and epel10 can exist. Mass
branch those? who is maintainer?
I'm not sure this is all a super big deal, but I'd really like to make
sure we make _very_ clear who is responsible for what. Some maintainers
would be happy to maintain for that long cycle (from landing in
eln-extra now, to epel 10 next, to epel10... thats what... 13 years?),
but some may not, and some might be happy for part of it but not the
entire thing.
Anyhow, I like this proposal much more than early epel10{next}
branching. :)
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
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
[Bug 1938597] perl-Getopt-Long-Descriptive-0.107 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938597 --- Comment #1 from Upstream Release Monitoring --- An HTTP error occurred downloading the package's new Source URLs: Getting https://cpan.metacpan.org/modules/by-module/Getopt/Getopt-Long-Descriptive-0.107.tar.gz to ./Getopt-Long-Descriptive-0.107.tar.gz -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938597] New: perl-Getopt-Long-Descriptive-0.107 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938597 Bug ID: 1938597 Summary: perl-Getopt-Long-Descriptive-0.107 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Getopt-Long-Descriptive Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.107 Current version/release in rawhide: 0.106-1.fc35 URL: http://search.cpan.org/dist/Getopt-Long-Descriptive Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/7110/ -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-IoT-34-20210314.0 compose check report
No missing expected images. Failed openQA tests: 1/16 (x86_64), 2/15 (aarch64) Old failures (same test failed in Fedora-IoT-34-20210313.0): ID: 814567 Test: x86_64 IoT-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/814567 ID: 814576 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/814576 ID: 814583 Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/814583 Soft failed openQA tests: 3/16 (x86_64), 1/15 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-34-20210313.0): ID: 814559 Test: x86_64 IoT-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/814559 ID: 814560 Test: x86_64 IoT-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/814560 ID: 814561 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/814561 ID: 814575 Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi URL: https://openqa.fedoraproject.org/tests/814575 Passed openQA tests: 12/16 (x86_64), 12/15 (aarch64) -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938015] perl-Mojolicious-9.09 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938015 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-Mojolicious-9.08 is|perl-Mojolicious-9.09 is |available |available --- Comment #2 from Upstream Release Monitoring --- Latest upstream release: 9.09 Current version/release in rawhide: 9.08-1.fc35 URL: https://metacpan.org/release/Mojolicious Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/5966/ -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1938401] ack-3.5.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1938401 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- FEDORA-2021-f4bf099bb4 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f4bf099bb4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f4bf099bb4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-IoT-35-20210314.0 compose check report
Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 2/16 (x86_64), 5/15 (aarch64) New failures (same test not failed in Fedora-IoT-35-20210313.0): ID: 814480 Test: x86_64 IoT-dvd_ostree-iso iot_rpmostree_rebase URL: https://openqa.fedoraproject.org/tests/814480 Old failures (same test failed in Fedora-IoT-35-20210313.0): ID: 814483 Test: x86_64 IoT-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/814483 ID: 814492 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/814492 ID: 814494 Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi URL: https://openqa.fedoraproject.org/tests/814494 ID: 814499 Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/814499 ID: 814502 Test: aarch64 IoT-dvd_ostree-iso podman@uefi URL: https://openqa.fedoraproject.org/tests/814502 ID: 814503 Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi URL: https://openqa.fedoraproject.org/tests/814503 Soft failed openQA tests: 1/16 (x86_64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-IoT-35-20210313.0): ID: 814477 Test: x86_64 IoT-dvd_ostree-iso iot_clevis URL: https://openqa.fedoraproject.org/tests/814477 Passed openQA tests: 13/16 (x86_64), 10/15 (aarch64) New passes (same test not passed in Fedora-IoT-35-20210313.0): ID: 814486 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server URL: https://openqa.fedoraproject.org/tests/814486 ID: 814490 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition URL: https://openqa.fedoraproject.org/tests/814490 Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default@uefi: System load changed from 0.32 to 0.15 Previous test data: https://openqa.fedoraproject.org/tests/813148#downloads Current test data: https://openqa.fedoraproject.org/tests/814475#downloads Installed system changes in test x86_64 IoT-dvd_ostree-iso install_default_upload: System load changed from 0.35 to 0.20 Previous test data: https://openqa.fedoraproject.org/tests/813149#downloads Current test data: https://openqa.fedoraproject.org/tests/814476#downloads Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: System load changed from 0.67 to 0.38 Previous test data: https://openqa.fedoraproject.org/tests/813164#downloads Current test data: https://openqa.fedoraproject.org/tests/814491#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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On Sun, 14 Mar 2021 19:10:03 +0100 Sandro Mani wrote: > > On 14.03.21 10:15, Dan Horák wrote: > > On Sun, 14 Mar 2021 09:50:42 +0100 > > Sandro Mani wrote: > > > >> On 14.03.21 01:39, Orion Poplawski wrote: > >>> On 3/6/21 4:52 PM, Sandro Mani wrote: > Hi > > I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. > > I'll rebuild the following dependent packages: > > gdl > vtk > >>> I've added patches for proj 8 support to these packages and submitted > >>> builds in the side tag. > >> Thanks a lot! > >> > >> Quick status update: Still needing porting are gdl, qmapshack and > >> python-cartopy (and possibly pcl, which depends on VTK). > > I haven't checked the details yet, but there is some work being done on > > proj usage in qmapshack in their git. > > Thanks, the latest git snapshot builds successfully with proj 8. thanks for checking, I can take care of updating qmapshack with the cherry-picked patches. I need to do an update to 1.15.2 anyway. Dan ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On 14.03.21 19:24, Fabio Valentini wrote: On Sun, Mar 14, 2021 at 7:10 PM Sandro Mani wrote: On 14.03.21 10:15, Dan Horák wrote: On Sun, 14 Mar 2021 09:50:42 +0100 Sandro Mani wrote: On 14.03.21 01:39, Orion Poplawski wrote: On 3/6/21 4:52 PM, Sandro Mani wrote: Hi I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. I'll rebuild the following dependent packages: gdl vtk I've added patches for proj 8 support to these packages and submitted builds in the side tag. Thanks a lot! Quick status update: Still needing porting are gdl, qmapshack and python-cartopy (and possibly pcl, which depends on VTK). I haven't checked the details yet, but there is some work being done on proj usage in qmapshack in their git. Thanks, the latest git snapshot builds successfully with proj 8. Please don't take this the wrong way - I do not want to tell you how to do your work. That said, wouldn't it have been easier and less stressful for everybody involved to figure out the compatibility issues and necessary patches to dependent packages *before* starting to submit package builds, e.g. in a COPR? Keeping side tags around for weeks takes up precious resources in koji, and increases the likelihood of conflicts when merging the side tag back into rawhide (and it's a *bit* late to do big updates like this for F34, too). I accept the blame here, I didn't closely enough follow the proj developments to realize that the old API was not removed in proj-7, but in proj-8. I'm not going to land this in F34 at this point given how intrusive this change is. Apologies for not doing my homework properly and thanks to all of you who have helped out! Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On Sun, Mar 14, 2021 at 7:10 PM Sandro Mani wrote: > > > On 14.03.21 10:15, Dan Horák wrote: > > On Sun, 14 Mar 2021 09:50:42 +0100 > > Sandro Mani wrote: > > > >> On 14.03.21 01:39, Orion Poplawski wrote: > >>> On 3/6/21 4:52 PM, Sandro Mani wrote: > Hi > > I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. > > I'll rebuild the following dependent packages: > > gdl > vtk > >>> I've added patches for proj 8 support to these packages and submitted > >>> builds in the side tag. > >> Thanks a lot! > >> > >> Quick status update: Still needing porting are gdl, qmapshack and > >> python-cartopy (and possibly pcl, which depends on VTK). > > I haven't checked the details yet, but there is some work being done on > > proj usage in qmapshack in their git. > > Thanks, the latest git snapshot builds successfully with proj 8. Please don't take this the wrong way - I do not want to tell you how to do your work. That said, wouldn't it have been easier and less stressful for everybody involved to figure out the compatibility issues and necessary patches to dependent packages *before* starting to submit package builds, e.g. in a COPR? Keeping side tags around for weeks takes up precious resources in koji, and increases the likelihood of conflicts when merging the side tag back into rawhide (and it's a *bit* late to do big updates like this for F34, too). 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On 14.03.21 10:15, Dan Horák wrote: On Sun, 14 Mar 2021 09:50:42 +0100 Sandro Mani wrote: On 14.03.21 01:39, Orion Poplawski wrote: On 3/6/21 4:52 PM, Sandro Mani wrote: Hi I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. I'll rebuild the following dependent packages: gdl vtk I've added patches for proj 8 support to these packages and submitted builds in the side tag. Thanks a lot! Quick status update: Still needing porting are gdl, qmapshack and python-cartopy (and possibly pcl, which depends on VTK). I haven't checked the details yet, but there is some work being done on proj usage in qmapshack in their git. Thanks, the latest git snapshot builds successfully with proj 8. Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: American Fuzzy Lop (fuzzer) upstream fork
On Sun, Mar 14, 2021 at 05:30:18PM +0100, Kevin Kofler via devel wrote: > Richard W.M. Jones wrote: > > If we switch it's likely that we won't easily be able to go back. > > If you use properly versioned Obsoletes, then going back is as easy as > unretiring the original package, increasing EVR above the version in the > Obsoletes, and adding a versioned Obsoletes the other way round. In case I wasn't clear, I would like to change the upstream (ie. URL/Source) of the current american-fuzzy-lop package. If we consider this to be a new package and it has to go through review then I'll leave that work to someone else. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] 2021-03-15 @ **16:00** UTC - Fedora 34 Blocker Review Meeting
# F34 Blocker Review meeting # Date: 2021-03-15 # Time: **16:00** UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 3 proposed Beta freeze exception issues, and 5 proposed Final blockers to review (as of now), so we'll have a Fedora 34 blocker review meeting tomorrow. Note that daylight savings time started in most places that observe it today, so the meeting time in UTC has been changed. If your clocks went forward this weekend, the meeting time in your local time will be the same as it was before. If your area does not observe daylight savings, or starts later, the meeting will be an hour *earlier* in your local time than it was before. You can use 'date -u' to check the current UTC time and make sure you head to the meeting at the right time. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F34 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Proposal to CANCEL: 2021-03-15 Fedora QA Meeting
Hi folks! I'm proposing we cancel the QA meeting tomorrow. I don't have anything urgent this week, and we'll be doing a blocker meeting for F34. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-34-20210314.n.0 compose check report
No missing expected images. Failed openQA tests: 7/187 (x86_64), 15/126 (aarch64) New failures (same test not failed in Fedora-34-20210313.n.0): ID: 814190 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/814190 ID: 814195 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/814195 ID: 814237 Test: aarch64 Server-dvd-iso install_repository_hd_variation@uefi URL: https://openqa.fedoraproject.org/tests/814237 ID: 814260 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/814260 ID: 814266 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/814266 ID: 814288 Test: aarch64 Cloud_Base-qcow2-qcow2 base_system_logging@uefi URL: https://openqa.fedoraproject.org/tests/814288 ID: 814384 Test: aarch64 universal install_repository_http_variation@uefi URL: https://openqa.fedoraproject.org/tests/814384 ID: 814395 Test: aarch64 universal install_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/814395 Old failures (same test failed in Fedora-34-20210313.n.0): ID: 814172 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/814172 ID: 814181 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/814181 ID: 814192 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/814192 ID: 814218 Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/814218 ID: 814219 Test: aarch64 Minimal-raw_xz-raw.xz base_selinux@uefi URL: https://openqa.fedoraproject.org/tests/814219 ID: 814220 Test: aarch64 Minimal-raw_xz-raw.xz base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/814220 ID: 814221 Test: aarch64 Minimal-raw_xz-raw.xz release_identification@uefi URL: https://openqa.fedoraproject.org/tests/814221 ID: 814232 Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/814232 ID: 814299 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/814299 ID: 814348 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/814348 ID: 814376 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/814376 ID: 814405 Test: aarch64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/814405 ID: 814410 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/814410 ID: 814415 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/814415 Soft failed openQA tests: 54/126 (aarch64), 90/187 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-34-20210313.n.0): ID: 814274 Test: aarch64 Workstation-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/814274 ID: 814320 Test: x86_64 universal install_delete_pata@uefi URL: https://openqa.fedoraproject.org/tests/814320 ID: 814347 Test: x86_64 universal install_simple_encrypted URL: https://openqa.fedoraproject.org/tests/814347 ID: 814381 Test: aarch64 universal install_blivet_xfs@uefi URL: https://openqa.fedoraproject.org/tests/814381 ID: 814391 Test: aarch64 universal install_kickstart_nfs@uefi URL: https://openqa.fedoraproject.org/tests/814391 ID: 814394 Test: aarch64 universal install_mirrorlist_graphical@uefi URL: https://openqa.fedoraproject.org/tests/814394 Old soft failures (same test soft failed in Fedora-34-20210313.n.0): ID: 814104 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/814104 ID: 814105 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/814105 ID: 814107 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/814107 ID: 814110 Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home URL: https://openqa.fedoraproject.org/tests/814110 ID: 814111 Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/814111 ID: 814112 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4 URL: https://openqa.fedoraproject.org/tests/814112 ID: 814113 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/814113 ID: 814114 Test: x86_64 Server-dvd-iso install_blivet_standard_partition_ext4 URL: https://openqa.fedoraproject.org/tests/814114 ID: 814115 Test: x86_64 Server-dvd-iso
Fedora-Rawhide-20210314.n.0 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 2 of 43 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 13/187 (x86_64), 26/126 (aarch64) New failures (same test not failed in Fedora-Rawhide-20210313.n.0): ID: 813807 Test: x86_64 Server-dvd-iso server_cockpit_updates URL: https://openqa.fedoraproject.org/tests/813807 ID: 813830 Test: x86_64 Workstation-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/813830 ID: 813876 Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal URL: https://openqa.fedoraproject.org/tests/813876 ID: 813927 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/813927 ID: 813937 Test: aarch64 Server-raw_xz-raw.xz release_identification@uefi URL: https://openqa.fedoraproject.org/tests/813937 ID: 813941 Test: aarch64 Server-raw_xz-raw.xz base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/813941 ID: 814065 Test: aarch64 universal install_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/814065 ID: 814097 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/814097 ID: 814420 Test: aarch64 Server-dvd-iso install_repository_nfsiso_variation@uefi URL: https://openqa.fedoraproject.org/tests/814420 Old failures (same test failed in Fedora-Rawhide-20210313.n.0): ID: 813816 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/813816 ID: 813831 Test: x86_64 Workstation-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/813831 ID: 813888 Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/813888 ID: 813889 Test: aarch64 Minimal-raw_xz-raw.xz base_selinux@uefi URL: https://openqa.fedoraproject.org/tests/813889 ID: 813890 Test: aarch64 Minimal-raw_xz-raw.xz base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/813890 ID: 813891 Test: aarch64 Minimal-raw_xz-raw.xz release_identification@uefi URL: https://openqa.fedoraproject.org/tests/813891 ID: 813902 Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/813902 ID: 813926 Test: aarch64 Server-dvd-iso modularity_tests@uefi URL: https://openqa.fedoraproject.org/tests/813926 ID: 813930 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/813930 ID: 813942 Test: aarch64 Server-raw_xz-raw.xz base_selinux@uefi URL: https://openqa.fedoraproject.org/tests/813942 ID: 813943 Test: aarch64 Server-raw_xz-raw.xz base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/813943 ID: 813945 Test: aarch64 Workstation-raw_xz-raw.xz release_identification@uefi URL: https://openqa.fedoraproject.org/tests/813945 ID: 813949 Test: aarch64 Workstation-raw_xz-raw.xz base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/813949 ID: 813950 Test: aarch64 Workstation-raw_xz-raw.xz base_selinux@uefi URL: https://openqa.fedoraproject.org/tests/813950 ID: 813951 Test: aarch64 Workstation-raw_xz-raw.xz base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/813951 ID: 813953 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/813953 ID: 813955 Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi URL: https://openqa.fedoraproject.org/tests/813955 ID: 813968 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/813968 ID: 813969 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/813969 ID: 813982 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/813982 ID: 813991 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/813991 ID: 814018 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/814018 ID: 814045 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/814045 ID: 814046 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/814046 ID: 814053 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/814053 ID: 814057 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/814057 ID: 814075 Test: aarch64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/814075 ID: 814081 Test: aarch64 universal upgrade_minimal_64bit@uefi URL: https://openqa.fedoraproject.org/tests/814081 ID: 814088 Test:
ELN composes on mirrors
I had filed https://github.com/fedora-eln/eln/issues/33 a while ago to track documentation improvements around how to consume ELN composes. I'd like to take a step back and propose adding them to the mirror network, akin to what we already do for Rawhide. This would make it trivial to consume or mirror them locally (e.g. via rsync), without having to hit ODCS directly. The only downside I can think of is that it'd consume a bit more storage on the mirrors themselves. Thoughts? Cheers Davide ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ELN SIG First Meeting
On Sat, 2021-03-13 at 17:09 -0800, Troy Dawson wrote: > Sorry for coming late to the discussion. I took a week off and all > sorts of things happened while I was gone. > > I believe Kevin and Smooge, and possibly even you Davide got this > backwards. And I think if we do this right, this can be a thing. > > When we started ELN, one of the major promises was that it wouldn't > interfere with regular Fedora work. That your average Fedora > packager > that didn't care about ELN, could continue to not care about ELN and > nothing would change. > I believe we (ELN SIG) should extend the same courtesy to EPEL and > the > EPEL community and packagers. > > The email discussion went in the direction of all the work that EPEL > would need to do to create an ELN EPEL. But we (ELN SIG) shouldn't > have expected that. We should have expected to do all the work. > > So, if we flip this around, where everything is on ELN, how would > that work. > > We create a new Fedora target and tag: eln-extra (so people do NOT > confuse it with real EPEL) > eln-extra-build inherits from itself and eln-build > If a package is built against the eln-extra target, and it is > successful, it gets tagged with the eln-extra tag. > There is a daily (or some other time period) repo creation. No > images, just a repo, like epel. > There is a list of packages, similar to the list of packages used to > create the ELN list, on some github/gitlab/pagure repo. If you put a > package on that list, you associate your name with that package. > Just like ELN, when a package on the eln-extra list gets built in > rawhide, it get's built in eln-extra. In fact, it would be best if > we > just altered the ELN trigger/periodic scripts to look at this list > along with the regular ELN list. > > What are people's thoughts on this? > No extra work on EPEL. > If someone, or some company wants to test ELN and need packages not > in > ELN, they can add the packages to the list, with their name/company > associated with that package. > It would get built, put in the repo, and they can then run their ELN > test with the package they need. > > Thoughts? Thanks Troy for taking time to put this together. I like this plan: it solves my usecase and it doesn't put undue burden onto EPEL or the individual packagers, while also leaving open the possibility of leveraging eln-extra to seed the next EPEL release if a packager so desires. How would be manage in practice the maintainership of packages in eln- extra? Would it be recorded in dist-git (coupled with the relevant ACLs to allow pushing fixes if needed), or somewhere else? Cheers Davide ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: American Fuzzy Lop (fuzzer) upstream fork
Richard W.M. Jones wrote: > If we switch it's likely that we won't easily be able to go back. If you use properly versioned Obsoletes, then going back is as easy as unretiring the original package, increasing EVR above the version in the Obsoletes, and adding a versioned Obsoletes the other way round. Kevin Kofler ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: American Fuzzy Lop (fuzzer) upstream fork
On Sun, Mar 14, 2021 at 11:04 AM Richard W.M. Jones wrote: > > I'm packaging American Fuzzy Loop (AFL) a fuzzing tool in Fedora. > > https://src.fedoraproject.org/rpms/american-fuzzy-lop > > This is the upstream we're using: > > https://lcamtuf.coredump.cx/afl/ > https://github.com/google/AFL > > Upstream is dead. -ish. To be more precise there's some but not a > great deal of work going on at this upstream. Original author Michal > Zalewski left Google a few years back. > > However there is a fork called AFL++: > > https://aflplus.plus/ > https://github.com/AFLplusplus/AFLplusplus > > This fork is certainly a lot more active, and has made some > significant improvments. > > Debian has switched upstreams, or to be more precise (again) they have > added a new afl++ package, and created a transitional package to > replace the original afl which if I'm understanding things correctly > will replace afl with afl++ on upgrades: > > https://packages.debian.org/sid/afl > > Anyway I'm wondering if we should switch upstreams. I think if the > old upstream was truly dead then I wouldn't even bother asking. It's > because old upstream is still making occasional releases that the > problem arises. If we switch it's likely that we won't easily be able > to go back. > > On the "pro-switch" side, Google themselves seem to have switched to > AFL++ for their hosted OSS-Fuzz service, if I'm reading this page right: > > https://google.github.io/oss-fuzz/ > > I would like to do this without re-reviewing, ie. just replace the > Source/URL and go. If a full review is required then I'll let someone > else take over the effort. > > Thoughts? Just replace it in the existing package and add Provides for the other name. We've done this before for other packages, and it's fine since it's a fork. -- 真実はいつも一つ！/ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
American Fuzzy Lop (fuzzer) upstream fork
I'm packaging American Fuzzy Loop (AFL) a fuzzing tool in Fedora. https://src.fedoraproject.org/rpms/american-fuzzy-lop This is the upstream we're using: https://lcamtuf.coredump.cx/afl/ https://github.com/google/AFL Upstream is dead. -ish. To be more precise there's some but not a great deal of work going on at this upstream. Original author Michal Zalewski left Google a few years back. However there is a fork called AFL++: https://aflplus.plus/ https://github.com/AFLplusplus/AFLplusplus This fork is certainly a lot more active, and has made some significant improvments. Debian has switched upstreams, or to be more precise (again) they have added a new afl++ package, and created a transitional package to replace the original afl which if I'm understanding things correctly will replace afl with afl++ on upgrades: https://packages.debian.org/sid/afl Anyway I'm wondering if we should switch upstreams. I think if the old upstream was truly dead then I wouldn't even bother asking. It's because old upstream is still making occasional releases that the problem arises. If we switch it's likely that we won't easily be able to go back. On the "pro-switch" side, Google themselves seem to have switched to AFL++ for their hosted OSS-Fuzz service, if I'm reading this page right: https://google.github.io/oss-fuzz/ I would like to do this without re-reviewing, ie. just replace the Source/URL and go. If a full review is required then I'll let someone else take over the effort. Thoughts? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora mirrors, some returning 404
On Fri, Mar 12, 2021 at 09:49:13AM -0800, Kevin Fenzi wrote:
> On Fri, Mar 12, 2021 at 10:21:45AM +, Richard W.M. Jones wrote:
> > AIUI end users are typing in these URLs and we download them on
> > demand.
> >
> > (I only wrote a very low-level component in this huge stack of cloud
> > stuff so I don't have the full picture, but the additional
> > complication I didn't mention is that we're using libcurl to download
> > ranges of the file, and it seems to get redirected to different
> > mirrors on every range, so it can still fail even if the first range
> > succeeded.)
>
> Fun. ;(
I think we've settled on "resolving" the location to the mirror before
passing it to nbdkit to do the downloading bit. The code is fairly
simple (see attached) and it gives us the opportunity to catch a 404
cleanly and early, as well as to sanity-check the size.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
/* gcc test.c -o test -lcurl */
#include
#include
#include
#include
int
main ()
{
CURL *curl;
CURLcode r;
char *url;
curl_off_t len;
curl = curl_easy_init ();
assert (curl != NULL);
curl_easy_setopt (curl, CURLOPT_URL,
"https://download.fedoraproject.org/pub/fedora/linux/releases/33/Cloud/x86_64/images/Fedora-Cloud-Base-33-1.2.x86_64.raw.xz;);
curl_easy_setopt (curl, CURLOPT_NOBODY, 1); /* No Body, not nobody! */
curl_easy_setopt (curl, CURLOPT_FOLLOWLOCATION, 1);
curl_easy_setopt (curl, CURLOPT_FAILONERROR, 1);
r = curl_easy_perform (curl);
if (r != CURLE_OK) {
fprintf (stderr, "error getting HEAD of URL: %d\n", r);
exit (EXIT_FAILURE);
}
/* Resolve effective URL. */
r = curl_easy_getinfo (curl, CURLINFO_EFFECTIVE_URL, );
if (r != CURLE_OK) {
fprintf (stderr, "error resolving URL: %d\n", r);
exit (EXIT_FAILURE);
}
printf ("resolved URL: %s\n", url);
/* Get content length. */
r = curl_easy_getinfo (curl, CURLINFO_CONTENT_LENGTH_DOWNLOAD_T, );
if (r != CURLE_OK) {
fprintf (stderr, "error getting content length: %d\n", r);
exit (EXIT_FAILURE);
}
printf ("content length: %ld\n", (long) len);
curl_easy_cleanup (curl);
}
___
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
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Fedora 34 compose report: 20210314.n.0 changes
OLD: Fedora-34-20210313.n.0 NEW: Fedora-34-20210314.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 2 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 29.38 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 16.30 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: graphene-1.10.4-2.fc34 Old package: graphene-1.10.4-1.fc34 Summary: Thin layer of types for graphic libraries RPMs: graphene graphene-devel graphene-tests Size: 2.18 MiB Size change: 3.67 KiB Changelog: * Tue Mar 09 2021 Nicolas Chauvet - 1.10.4-2 - Disable neon for graphene on armv7hl - Add meson_test Package: lorax-34.9-4.fc34 Old package: lorax-34.9-1.fc34 Summary: Tool for creating the anaconda install images RPMs: composer-cli lorax lorax-docs lorax-lmc-novirt lorax-lmc-virt lorax-templates-generic Size: 27.21 MiB Size change: 12.62 KiB Changelog: * Tue Mar 09 2021 Peter Hutterer 34.9-2 - Add patch downstream to replace retired/blocked xorg-x11-server-utils package (cherry-picked from rawhide) * Wed Mar 10 2021 Adam Williamson - 34.9-3 - Backport patch to not cleanup report-cli and fix text mode crash reporting Resolves: rhbz#1937550 * Wed Mar 10 2021 Adam Williamson - 34.9-4 - Disable the xorg-x11-server-utils patch for now (that split is stuck in u-t) = DOWNGRADED PACKAGES = ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20210314.n.0 changes
OLD: Fedora-Rawhide-20210313.n.0 NEW: Fedora-Rawhide-20210314.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 4 Dropped packages:0 Upgraded packages: 59 Downgraded packages: 0 Size of added packages: 326.13 KiB Size of dropped packages:0 B Size of upgraded packages: 1.61 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 3.17 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: python-openpaperwork-core-2.0.2-1.fc35 Summary: OpenPaperwork's core RPMs:python3-openpaperwork-core Size:143.21 KiB Package: python-openpaperwork-gtk-2.0.2-1.fc35 Summary: OpenPaperwork GTK plugins RPMs:python3-openpaperwork-gtk Size:97.87 KiB Package: python-wcmatch-8.1.2-3.fc35 Summary: Wildcard/glob file name matcher RPMs:python3-wcmatch Size:69.90 KiB Package: sway-systemd-0.1.1-1.fc35 Summary: Systemd integration for Sway session RPMs:sway-systemd Size:15.16 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: ack-3.5.0-1.fc35 Old package: ack-3.4.0-2.fc34 Summary: Grep-like text finder RPMs: ack Size: 81.52 KiB Size change: 49 B Changelog: * Sat Mar 13 2021 Robin Lee - 3.5.0-1 - Update to 3.5.0 Package: azote-1.9.0-1.fc35 Old package: azote-1.8.2-2.fc34 Summary: Wallpaper and color manager for Sway, i3 and some other WMs RPMs: azote Size: 647.77 KiB Size change: 1.70 KiB Changelog: * Sat Mar 13 2021 Bob Hepple - 1.9.0-1 - new version Package: bcm283x-firmware-20210310-1.0591568.fc35 Old package: bcm283x-firmware-20210225-1.5985247.fc35 Summary: Firmware for the Broadcom bcm283x/bcm2711 used in the Raspberry Pi RPMs: bcm2711-firmware bcm2835-firmware bcm283x-firmware bcm283x-overlays Size: 13.66 MiB Size change: 1.03 KiB Changelog: * Fri Mar 12 2021 Peter Robinson 20210310-1.0591568 - Update to latest firmware - Put back nasty config hack as some usecases are still broken Package: bottles-3.0.9-1.fc35 Old package: bottles-3.0.8-1.fc35 Summary: Easily manage Wine prefix in a new way RPMs: bottles Size: 121.92 KiB Size change: 1.76 KiB Changelog: * Sat Mar 13 2021 Artem Polishchuk - 3.0.9-1 - build(update): 3.0.9 Package: clamtk-6.10-1.fc35 Old package: clamtk-6.09-1.fc35 Summary: Easy to use graphical user interface for Clam anti virus RPMs: clamtk Size: 199.95 KiB Size change: 1.37 KiB Changelog: * Sat Mar 13 2021 Dave M. - 6.10-1 - Updated to release 6.10. - Add appdata.xml. Package: deepin-api-5.3.2-1.fc35 Old package: deepin-api-5.3.0.12-2.fc34 Summary: Go-lang bingding for dde-daemon RPMs: deepin-api golang-deepin-api-devel Size: 62.43 MiB Size change: 87.95 KiB Changelog: * Tue Mar 02 2021 Zbigniew J??drzejewski-Szmek - 5.3.0.12-3 - Rebuilt for updated systemd-rpm-macros See https://pagure.io/fesco/issue/2583. * Thu Mar 11 2021 Robin Lee - 5.3.2-1 - chore(calendar): ??2021??? (lichangze) - chore(coverage): test coverage statistics (hubenchang0515) - chore: debian abi.json ?? (wubowen) - chore: fix lintian (lichangze) Package: deepin-calculator-5.6.0.10-1.fc35 Old package: deepin-calculator-5.6.0.1-2.fc34 Summary: An easy to use calculator for ordinary users RPMs: deepin-calculator Size: 2.37 MiB Size change: 20.63 KiB Changelog: * Fri Mar 12 2021 Robin Lee - 5.6.0.10-1 - fix: fix bug--57861 (jingzhou) - fix: fix bug--55167 (jingzhou) - chore: ??? (jingzhou) - chore: (jingzhou) - chore: UT test (jingzhou) Package: deepin-calendar-5.7.0.26-1.fc35 Old package: deepin-calendar-5.7.0.18-2.fc34 Summary: Calendar for Deepin Desktop Environment RPMs: deepin-calendar Size: 3.30 MiB Size change: 3.25 KiB Changelog: * Fri Mar 12 2021 Robin Lee - 5.7.0.26-1 - fix: ? (chenhaifeng) - fix: bug54123 ???8???9 (chenhaifeng) Package: deepin-daemon-5.12.52-1.fc35 Old package: deepin-daemon-5.11.0.36-3.fc34 Summary: Daemon handling the DDE session settings RPMs: deepin-daemon Size: 67.12 MiB Size change: -4.52 MiB Changelog: * Tue Jan 26 2021 Fedora Release Engineering - 5.11.0.36-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Thu Mar 11 2021 Robin Lee - 5.12.52-1 - feat(network): GetActiveConnectionInfo adds the SpecificObject property (zsien) - feat: activeConnection adds the SpecificPath property (zsien) - chore(timedate
[389-devel] Re: 389 DS nightly 2021-03-14 - 95% PASS
Stop Sent from my iPhone > On Mar 13, 2021, at 10:29 PM, vashi...@redhat.com wrote: > > https://fedorapeople.org/groups/389ds/ci/nightly/2021/03/14/report-389-ds-base-2.0.3-20210314gitd5fdea905.fc33.x86_64.html > ___ > 389-devel mailing list -- 389-devel@lists.fedoraproject.org > To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-32-20210314.0 compose check report
No missing expected images. Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-32-20210313.0): ID: 813657 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/813657 ID: 813664 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/813664 Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64) -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On Sun, 14 Mar 2021 09:50:42 +0100 Sandro Mani wrote: > > On 14.03.21 01:39, Orion Poplawski wrote: > > On 3/6/21 4:52 PM, Sandro Mani wrote: > >> Hi > >> > >> I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. > >> > >> I'll rebuild the following dependent packages: > >> > >> gdl > >> vtk > > > > I've added patches for proj 8 support to these packages and submitted > > builds in the side tag. > > Thanks a lot! > > Quick status update: Still needing porting are gdl, qmapshack and > python-cartopy (and possibly pcl, which depends on VTK). I haven't checked the details yet, but there is some work being done on proj usage in qmapshack in their git. Dan ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Heads Up: Update to proj-8.0.0 in F35 and F34
On 14.03.21 01:39, Orion Poplawski wrote: On 3/6/21 4:52 PM, Sandro Mani wrote: Hi I'll be updating proj to 8.0.0, first in F35 in a side tag and then F34. I'll rebuild the following dependent packages: gdl vtk I've added patches for proj 8 support to these packages and submitted builds in the side tag. Thanks a lot! Quick status update: Still needing porting are gdl, qmapshack and python-cartopy (and possibly pcl, which depends on VTK). I'm currently working on gdl which I believe does not require too much work to port. qmapshack OTOH is a very heavy proj user and I'll probably look at bundling proj for that one. python-cartopy has a small autogenerated Proj API via Cython files, I'll need to look into this into more detail (not familiar with Cython). Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: ELN SIG First Meeting
On Sat, Mar 13, 2021, at 8:09 PM, Troy Dawson wrote: > On Mon, Mar 1, 2021 at 11:49 AM Davide Cavalca via devel > wrote: > > > > On Mon, 2021-03-01 at 09:26 -0500, Stephen Gallagher wrote: > > > I'd like to encourage anyone interested in this meeting to submit > > > agenda topics by replying to this email. Currently the agenda > > > > One thing I'd be interested in exploring is the feasibility of > > extending ELN to cover EPEL as well. This would make it easier to keep > > EPEL consistent between major releases (as packages would get branched > > automatically). It would also make it possible to test the combined ELN > > + EPEL snapshot and find potential issues early on in the process. > > > > Sorry for coming late to the discussion. I took a week off and all > sorts of things happened while I was gone. > > I believe Kevin and Smooge, and possibly even you Davide got this > backwards. And I think if we do this right, this can be a thing. > > When we started ELN, one of the major promises was that it wouldn't > interfere with regular Fedora work. That your average Fedora packager > that didn't care about ELN, could continue to not care about ELN and > nothing would change. > I believe we (ELN SIG) should extend the same courtesy to EPEL and the > EPEL community and packagers. > > The email discussion went in the direction of all the work that EPEL > would need to do to create an ELN EPEL. But we (ELN SIG) shouldn't > have expected that. We should have expected to do all the work. > > So, if we flip this around, where everything is on ELN, how would that work. > > We create a new Fedora target and tag: eln-extra (so people do NOT > confuse it with real EPEL) > eln-extra-build inherits from itself and eln-build > If a package is built against the eln-extra target, and it is > successful, it gets tagged with the eln-extra tag. > There is a daily (or some other time period) repo creation. No > images, just a repo, like epel. > There is a list of packages, similar to the list of packages used to > create the ELN list, on some github/gitlab/pagure repo. If you put a > package on that list, you associate your name with that package. > Just like ELN, when a package on the eln-extra list gets built in > rawhide, it get's built in eln-extra. In fact, it would be best if we > just altered the ELN trigger/periodic scripts to look at this list > along with the regular ELN list. > > What are people's thoughts on this? > No extra work on EPEL. > If someone, or some company wants to test ELN and need packages not in > ELN, they can add the packages to the list, with their name/company > associated with that package. > It would get built, put in the repo, and they can then run their ELN > test with the package they need. > This is exactly how it should be done! Otherwise, have a list of packages to exclude and include everything else. V/r, James Cassell ___ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
