date:20210621

Fwd: glibc gconv package split

2021-06-21 Thread Siddhesh Poyarekar

[Fixing up my mailing list settings and re-sending]

Hello,

Apologies for the delayed announcement but as of
glibc-2.34.9000-13.fc35, the glibc package has been split to create a
new package glibc-gconv-extra to hold most converter modules into a
separate package.  The common converters such as those for UTF-*,
ISO8859-1, ISO8859-15 and CP1252 remain in the core package. This
change allows users that do not have use for the extra modules to save
space as well as harden their systems; many of the infrequently used
modules have historically had bugs with security impact.

glibc-gconv-extra is recommended by glibc, so a regular update or
default installation should pull in glibc-gconv-extra and there should
be no noticeable change unless a user explicitly removes
glibc-gconv-extra at some point.

One user visible problem we discovered[1][2] was that buildroots do
not install weak dependencies because of which glibc-gconv-extra goes
missing from them.  This may result in testing failures when
applications try to test uncommon character set conversions.  The fix
to get that working again is to add a build dependency on
glibc-gconv-extra.

Please file bugs against glibc for any other issues you come across in
charset conversions due to this split.  We'll be happy to help resolve
them.

Siddhesh

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1973663
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1974466
___
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

[EPEL-devel] Fedora EPEL 7 updates-testing report

2021-06-21 Thread updates

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  25  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef   
openjpeg2-2.3.1-11.el7
  25  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9eaea6f65c   
audacious-plugins-4.0.5-4.el7 fluidsynth-2.1.8-4.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-c4678a5e4b   
radare2-5.3.1-1.el7
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-49226a1ff0   
aom-3.1.1-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-92a8baa028   
tor-0.3.5.15-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

llvm11-11.1.0-1.el7
rust-1.53.0-1.el7

Details about builds:



 llvm11-11.1.0-1.el7 (FEDORA-EPEL-2021-beb7c88f5f)
 The Low Level Virtual Machine

Update Information:

Update to Rust 1.53.0:  - `IntoIterator` for arrays - Or patterns - Unicode
identifiers - `HEAD` branch name support in Cargo - Incremental Compilation
remains off by default - Stabilized APIs  See the [blog post](https://blog.rust-
lang.org/2021/06/17/Rust-1.53.0.html) and [release
notes](https://github.com/rust-
lang/rust/blob/master/RELEASES.md#version-1530-2021-06-17) for more details.

ChangeLog:





 rust-1.53.0-1.el7 (FEDORA-EPEL-2021-beb7c88f5f)
 The Rust Programming Language

Update Information:

Update to Rust 1.53.0:  - `IntoIterator` for arrays - Or patterns - Unicode
identifiers - `HEAD` branch name support in Cargo - Incremental Compilation
remains off by default - Stabilized APIs  See the [blog post](https://blog.rust-
lang.org/2021/06/17/Rust-1.53.0.html) and [release
notes](https://github.com/rust-
lang/rust/blob/master/RELEASES.md#version-1530-2021-06-17) for more details.

ChangeLog:

* Thu Jun 17 2021 Josh Stone  - 1.53.0-1
- Update to 1.53.0.
* Wed Jun  2 2021 Josh Stone  - 1.52.1-2
- Set rust.codegen-units-std=1 for all targets again.
- Add rust-std-static-wasm32-unknown-unknown.
- Rebuild f34 with LLVM 12.


___
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 to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-a208f35688 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-a208f35688`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-a208f35688

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 1973977] perl-Pod-Weaver-4.018 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973977



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-b58f75f46b 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-b58f75f46b`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-b58f75f46b

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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-14dd399ce6 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-14dd399ce6`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-14dd399ce6

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 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2021-1c8320e115 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-1c8320e115`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-1c8320e115

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 1973977] perl-Pod-Weaver-4.018 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973977

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2021-2d004ae6b9 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-2d004ae6b9`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2d004ae6b9

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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2021-2656950f5d 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-2656950f5d`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2656950f5d

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 1974136] F35FailsToInstall: perl-Email-Sender

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974136

Miro Hrončok  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |WORKSFORME
Last Closed||2021-06-21 23:43:38



--- Comment #1 from Miro Hrončok  ---
Hello,

Please note that this comment was generated automatically. If you feel that
this output has mistakes, please contact me via email (mhron...@redhat.com).

All subpackages of a package against which this bug was filled are now
installable or removed from Fedora 35.

Thanks for taking care of it!


-- 
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

Orphaned python-sure

2021-06-21 Thread Miro Hrončok


I've orphaned python-sure.

I've only maintained it because python-freezegun used it, but the dependency 
was bogus, see:

https://src.fedoraproject.org/rpms/python-freezegun/pull-request/13

--
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Updating sources file using fedpkg

2021-06-21 Thread Otto Urpelainen


Ewoud Kohl van Wijngaarden kirjoitti 21.6.2021 klo 14.50:

On Thu, Jun 17, 2021 at 09:02:12PM +0300, Otto Urpelainen wrote:
I am a bit confused about this discussion. My fedpkg does not care 
about the 'sources' file or the lookaside cache at all on 'fedpkg 
mockbuild'. It simply looks up the expected filename of downloaded 
Source, grabs it from the local working directory and uses that. So 
for me this works:


   rpmdev-bumpspec -D -n 1.2.3 *.spec
   # Update specfile as needed
   spectool -g *.spec
   fedpkg mockbuild


Now it also downloads the old files mentioned in sources. In my 
experience it certainly does care about it.


Maybe my request can be reduced to: mockbuild should not download files 
not mentioned in the spec file. Ken did give a good workaround. Taking 
that a step further I think something like this would suffice for me:


spectool -l *.spec | awk '/https?:/ { print $2 }' | xargs -n 1 basename 
| xargs sha512sum --tag > sources


Ah, you are right. Since I settled on my current workflow, I did not 
even notice those useless files being downloaded. I guess I have not 
encounters are very large one, then.


I filed an issue about this: https://pagure.io/rpkg/issue/559

Otto
___
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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Adam Williamson

On Mon, 2021-06-21 at 10:48 +0100, Ankur Sinha wrote:
> On Sun, Jun 20, 2021 11:41:41 -0700, Kevin Fenzi wrote:
> > On Sun, Jun 20, 2021 at 03:26:52PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > > 
> > > Yeah. I'm looking a the original ticket in
> > > https://pagure.io/fesco/issue/2228, and I think this was a mistake.
> > > We shouldn't have approved a bot that packages snapshot commits for
> > > rawhide. In the discussion, we talked about load on the infra, and ability
> > > to contact the maintainers, and even cooperation withb packit, but somehow
> > > the question whether we want this at all didn't come up.
> > > 
> > > I guess the effort to make rawhide palatable hadn't really sunk in
> > > deep enough back then ;)
> > 
> > Well, it's still not clear to me if these builds are not suitable for
> > rawhide, or if the bot that is pushing them just has bugs.
> 
> A few podman updates have now caused major breakages for users even in
> stable releases. Here's a recent example:
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-fc15685f73
> https://bugzilla.redhat.com/show_bug.cgi?id=1958546
> https://github.com/containers/podman/issues/10274

Well, this at least we can do something about fairly easily.

We have an openQA podman test already (a pair of tests actually), which
check podman can pull from the registry, then build a basic image which
runs a web server, run a container with that image, and test the web
server is reachable. We'd only been running those on IoT and CoreOS
images, but there's no reason we can't run them in other contexts too.

So as of now they will also run on critpath updates and any non-
critpath updates containing podman, containernetworking-plugins, crun,
fuse-overlayfs or slirp4netns (other suggestions welcome):

https://pagure.io/fedora-qa/os-autoinst-distri-fedora/c/9174472
https://pagure.io/fedora-qa/fedora_openqa/c/d861f94

https://src.fedoraproject.org/rpms/podman/pull-request/43 is a PR which
would cause updates for podman for F33 and F34 to be gated on those
tests. We could do the same for the other packages easily, I just filed
one PR for now to see what the feedback will be.

The tests at present don't exercise the toolbox container at all, but
it'd be fairly easy to add that if it's a good idea.
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1973319] perl-libwww-perl-6.55 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973319



--- Comment #1 from Michal Josef Spacek  ---
Packages created:
perl-libwww-perl-6.55-1.fc35
perl-libwww-perl-6.55-1.fc34
perl-libwww-perl-6.55-1.fc33


-- 
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

ntl soname bump

2021-06-21 Thread Jerry James

Just in time to miss the big pile of package rebuilds I did last week
for various mathematical packages, ntl 11.5.0 is out and comes with an
soname bump.  In a few days, I will build the new version of ntl for
Rawhide only and rebuild dependent packages:

eclib
flint
giac
latte-integrale
Macaulay2
sagemath
Singular

Regards,
-- 
Jerry James
http://www.jamezone.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: Forbidden to download EPEL packages?

2021-06-21 Thread Ron Olson

Yep, removing —enablerepo=local did the trick. Thanks!


On 21 Jun 2021, at 13:06, Stephen John Smoogen wrote:

> OK I was able to replicate it. My apologies I had a 'local' local on
> the machine I was 'duplicating' and my laptop had a
> [local]
> name=local
> baseurl=https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/
> cost=2000
> enabled=0
> skip_if_unavailable=False
>
> so the laptop broke while the buildbox worked.
>
> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code:
> 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> (IP: 38.145.60.16)
>
> and yep.. there is my ip address trying to download that file
>
> access_log:blach.foo.bar - - [21/Jun/2021:17:39:15 +] "GET
> /repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/redhat-release-8.4-0.6.el8.x86_64.rpm
> HTTP/1.1" 403
>  199 "-" "Mock (epel-8-x86_64; x86_64)"
>
> remove --enablerepo=local and the rebuild works. So the problem must
> be with kojiplgs OR something in mock
>
> Downloading I find kojipkgs is giving a file with
> 7dfe04833c8f1bd0fc85c5168764a9b682e13bb714ef88a2bf22b04593f9ac07-primary.xml.gz
> which contains
>
> 7dfe04833c8f1bd0fc85c5168764a9b682e13bb714ef88a2bf22b04593f9ac07-primary.xml.gz:
>   xml:base="https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001;
> href="non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm"/>
>
> Looking at the contents of the stuff local is giving.. it is only
> those files which are local to IAD2 and nothing else.. as such I would
> not use it in your builds.
>
> On Mon, 21 Jun 2021 at 13:25, Ron Olson  wrote:
>>
>> Funny enough, neither did I.
>>
>> On 21 Jun 2021, at 11:58, Stephen John Smoogen wrote:
>>
>>> I don't know.
>>>
>>> on my systems I did a find /etc/mock/ -type f -print | xargs grep
>>> infrastructure.fedoraproject.org and did not have any hits.
>>>
>>> On Mon, 21 Jun 2021 at 10:35, Ron Olson  wrote:

 Hmm, but why would it be pulling those? I’m merely trying to run mock on 
 my own machine in a script:

 BUILD=epel-8-x86_64
 #echo Cleaning $BUILD
 #mock -r $BUILD --scrub=all
 mock --clean -r $BUILD --enablerepo=local --spec=swift-lang.spec 
 --sources=../SOURCES --resultdir=$MYDIR/mock-results --buildsrpm --rebuild 
 --rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee 
 $MYDIR/mock-results/build-output.txt



 On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:

> On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:
>>
>> Hey all-
>>
>> I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails 
>> with:
>>
>>
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>> 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>> 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 
>> 00:02
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>> 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>> 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>> 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> Error: Error downloading packages:
>>   Status code: 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>>
>
> I believe the problem is that you have
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
> listed in some mock file versus
> https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'
>
> The infrastructure URL is only available to Fedoraproject builders
> while the kojipkgs should be available everywhere.
>
>
>
> --
> Stephen J Smoogen.
> I've seen things you people wouldn't believe. Flame wars in

F35 Change: Libvirt Modular Daemons (Self-Contained Change proposal)

2021-06-21 Thread Ben Cotton

https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons


== Summary ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Primarily this
provides better robustness as a flaw in a secondary daemon will not
affect the QEMU daemon and vica-versa. It should also have slightly
lower host startup overhead, because only the installed hypervisor
daemon(s) will need to be fully started on boot, the other daemons can
be socket activated on demand.

== Owner ==
* Name: [[User:berrange| Daniel Berrange]]
* Email: berra...@redhat.com

== Detailed Description ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Daemons include
virtqemud, virtlxcd, virtnetworkd, virtnodedevd, virtsecretd, etc, one
for each libvirt stateful hypervisor driver and secondary support
driver. The new daemons listen on new socket paths and only support
UNIX sockets. For remote off-host TCP/TLS access and for backwards
compatibility with clients expecting the libvirtd UNIX socket paths, a
virtproxyd daemon is also provided. The latter accepts RPC requests
and forwards to the appropriate modular daemon.  Further information
is available in the [https://libvirt.org/daemons.html Upstream
documentation]

The work will primarily involve changes in the systemd presets related
to libvirt. Currently the Fedora systemd presets enable
libvirtd.service. While libvirtd does support socket activation this
is not used during host startup, because the libvirtd daemon needs to
be fully started in order to auto-start QEMU guests that may be
configured. The current libvirtd.service uses a timeout, however, that
causes libvirtd to shutdown after 2 minutes if no VM is running.

This requirement for fully starting the service on boot still exists
in the modular daemons, however, we do not need to start all the
modular daemons on boot. It is sufficient to enable just the service
units for the hypervisor drivers QEMU, Xen and LXC. These will again
this will use a 2 minute timeout so they shut down if no
guest/container are running. Further, a default install of libvirt in
Fedora is only expected to provide the QEMU libvirt daemon.

The remaining modular daemons for libvirt non-hypervisor drivers can
exclusively rely on socket activation, because while they do provide
autostart capabilities for non-VM resources, these resources are only
needed when a VM actually starts.

The current '/usr/lib/systemd/system-preset/90-default.preset' config has

  libvirtd.service

and due to dependencies, this implies libvirtd.socket,
libvirtd-ro.socket, libvirtd-admin.socket, virtlogd.socket,
virtlockd.socket also get enabled by default

The intended change is to remove libvirtd.service and instead add

  virtqemud.service
  virtxend.service
  virtlxcd.service

  virtinterfaced.socket
  virtnetworkd.socket
  virtnodedevd.socket
  virtnwfilterd.socket
  virtproxyd.socket
  virtsecretd.socket
  virtstoraged.socket


== Benefit to Fedora ==
The primary benefit of the modular daemons is robustness of the
management stack. There are times when libvirt code has exhibited
hangs or crashes. By having one daemon per libvirt driver, the impact
of these bugs is limited. The most important benefit of this is that a
bug in the node device / storage daemons will not impact management of
any running QEMU VMs.

The secondary benefit of the modular daemons is improved host startup
overhead. When the libvirtd daemon starts, all drivers are initialized
and this can take a significant amount of CPU time. This is
particularly true for the node device driver as it extracts
information about all host hardware.

The third potential future benefit is that it enables development of
more useful SELinux policy. The current policy for libvirtd is no
better than unconfined due to the broad range of features that must be
allowed. At least some of the modular daemons can potentially have
useful SELinux policy written. Note there is no active work on this
aspect.

== Scope ==
* Proposal owners:

  Rebuild libvirt to prefer connecting to modular daemons by default
  Submit a patch updating 90-defaults.preset in the fedora-release
package to enable modular daemons by default

* Other developers:

  Review the proposal for fedora-release  preset change

* Release engineering: N/A

* Policies and guidelines: N/A

* Trademark approval: N/A

* Alignment with Objectives: N/A

== Upgrade/compatibility impact ==

Existing Fedora installs using libvirtd will be unaffected by the
change in presets and will continue to use monolithic libvirtd. To
opt-in to using the new modular daemons follow instructions at
https://libvirt.org/daemons.html#switching-to-modular-daemons

New Fedora installs will get modular daemons instead of libvirtd. This
is

F35 Change: Libvirt Modular Daemons (Self-Contained Change proposal)

2021-06-21 Thread Ben Cotton

https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons


== Summary ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Primarily this
provides better robustness as a flaw in a secondary daemon will not
affect the QEMU daemon and vica-versa. It should also have slightly
lower host startup overhead, because only the installed hypervisor
daemon(s) will need to be fully started on boot, the other daemons can
be socket activated on demand.

== Owner ==
* Name: [[User:berrange| Daniel Berrange]]
* Email: berra...@redhat.com

== Detailed Description ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Daemons include
virtqemud, virtlxcd, virtnetworkd, virtnodedevd, virtsecretd, etc, one
for each libvirt stateful hypervisor driver and secondary support
driver. The new daemons listen on new socket paths and only support
UNIX sockets. For remote off-host TCP/TLS access and for backwards
compatibility with clients expecting the libvirtd UNIX socket paths, a
virtproxyd daemon is also provided. The latter accepts RPC requests
and forwards to the appropriate modular daemon.  Further information
is available in the [https://libvirt.org/daemons.html Upstream
documentation]

The work will primarily involve changes in the systemd presets related
to libvirt. Currently the Fedora systemd presets enable
libvirtd.service. While libvirtd does support socket activation this
is not used during host startup, because the libvirtd daemon needs to
be fully started in order to auto-start QEMU guests that may be
configured. The current libvirtd.service uses a timeout, however, that
causes libvirtd to shutdown after 2 minutes if no VM is running.

This requirement for fully starting the service on boot still exists
in the modular daemons, however, we do not need to start all the
modular daemons on boot. It is sufficient to enable just the service
units for the hypervisor drivers QEMU, Xen and LXC. These will again
this will use a 2 minute timeout so they shut down if no
guest/container are running. Further, a default install of libvirt in
Fedora is only expected to provide the QEMU libvirt daemon.

The remaining modular daemons for libvirt non-hypervisor drivers can
exclusively rely on socket activation, because while they do provide
autostart capabilities for non-VM resources, these resources are only
needed when a VM actually starts.

The current '/usr/lib/systemd/system-preset/90-default.preset' config has

  libvirtd.service

and due to dependencies, this implies libvirtd.socket,
libvirtd-ro.socket, libvirtd-admin.socket, virtlogd.socket,
virtlockd.socket also get enabled by default

The intended change is to remove libvirtd.service and instead add

  virtqemud.service
  virtxend.service
  virtlxcd.service

  virtinterfaced.socket
  virtnetworkd.socket
  virtnodedevd.socket
  virtnwfilterd.socket
  virtproxyd.socket
  virtsecretd.socket
  virtstoraged.socket


== Benefit to Fedora ==
The primary benefit of the modular daemons is robustness of the
management stack. There are times when libvirt code has exhibited
hangs or crashes. By having one daemon per libvirt driver, the impact
of these bugs is limited. The most important benefit of this is that a
bug in the node device / storage daemons will not impact management of
any running QEMU VMs.

The secondary benefit of the modular daemons is improved host startup
overhead. When the libvirtd daemon starts, all drivers are initialized
and this can take a significant amount of CPU time. This is
particularly true for the node device driver as it extracts
information about all host hardware.

The third potential future benefit is that it enables development of
more useful SELinux policy. The current policy for libvirtd is no
better than unconfined due to the broad range of features that must be
allowed. At least some of the modular daemons can potentially have
useful SELinux policy written. Note there is no active work on this
aspect.

== Scope ==
* Proposal owners:

  Rebuild libvirt to prefer connecting to modular daemons by default
  Submit a patch updating 90-defaults.preset in the fedora-release
package to enable modular daemons by default

* Other developers:

  Review the proposal for fedora-release  preset change

* Release engineering: N/A

* Policies and guidelines: N/A

* Trademark approval: N/A

* Alignment with Objectives: N/A

== Upgrade/compatibility impact ==

Existing Fedora installs using libvirtd will be unaffected by the
change in presets and will continue to use monolithic libvirtd. To
opt-in to using the new modular daemons follow instructions at
https://libvirt.org/daemons.html#switching-to-modular-daemons

New Fedora installs will get modular daemons instead of libvirtd. This
is

Re: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Mohan Boddu

On Sun, Jun 20, 2021 at 7:09 AM Peter Robinson  wrote:
>
> > With things like [0] (TL;DR: bots submitting broken builds to rawhide)
> > becoming a more regular occurrence, I propose that we extend the
> > existing Updates Policy [1] to make it explicit that bots are not
> > allowed to submit builds / updates - even to rawhide - unattended:
> > "Rawhide is not your CI environment."
>
> I don't think that's good for either the packages that are using bots
> or for Fedora as a whole.
>
> While the bots certainly don't always get it right nor do the humans
> and I would garner that there's a lot more problems introduced in this
> way by humans, over the years I've spent considerable time fixing
> issues like this introduced by humans. Do we ban humans too? Do we ban
> RHBZ bots as well because they don't always get it right either?
> Ultimately automation is hard, but ultimately I feel it generally gets
> it wrong no less than humans do, and generally in a consistent way at
> least.

I definitely agree here, we want automation to evolve rather than
simply banning it. I understand the problem with automation, but
anyone can make mistakes. We should definitely have a contact person
responsible for the bot. And we can just ban the bot if it does
something unusual.
>
>
> 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
> 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

Re: Forbidden to download EPEL packages?

2021-06-21 Thread Kevin Fenzi

From what I can recall, the local repo was never intended to be used by
epel. It was to allow fedora builds to use the existing koji buildroot,
but that would never work for epel as we cannot publish all the rhel
rpms in the buildroot. 

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: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)

2021-06-21 Thread Marcin Juszkiewicz


W dniu 21.06.2021 o 17:43, Chris Murphy pisze:

Please make first partition at least 4MB in size. Those Arm/AArch64
systems which store bootloaders on boot media will have a space for it
(as some already read from around that area).

I'm confused what image(s) you're referring


Sorry, my mistake. I used too many images recently and missed 'cloud' in 
name.

___
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

1974358 – Review Request: fdr - Flight Data Recorder

2021-06-21 Thread Steve Dickson


Hello,

Anybody interested in doing a "review swap" or just a review??
Here is my review request [1]. I would like to get this into f35.

tia,

steved.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1974358
___
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: Forbidden to download EPEL packages?

2021-06-21 Thread Stephen John Smoogen

OK I was able to replicate it. My apologies I had a 'local' local on
the machine I was 'duplicating' and my laptop had a
[local]
name=local
baseurl=https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/
cost=2000
enabled=0
skip_if_unavailable=False

so the laptop broke while the buildbox worked.

[MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code:
403 for 
https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
(IP: 38.145.60.16)

and yep.. there is my ip address trying to download that file

access_log:blach.foo.bar - - [21/Jun/2021:17:39:15 +] "GET
/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/redhat-release-8.4-0.6.el8.x86_64.rpm
HTTP/1.1" 403
 199 "-" "Mock (epel-8-x86_64; x86_64)"

remove --enablerepo=local and the rebuild works. So the problem must
be with kojiplgs OR something in mock

Downloading I find kojipkgs is giving a file with
7dfe04833c8f1bd0fc85c5168764a9b682e13bb714ef88a2bf22b04593f9ac07-primary.xml.gz
which contains

7dfe04833c8f1bd0fc85c5168764a9b682e13bb714ef88a2bf22b04593f9ac07-primary.xml.gz:
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001;
href="non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm"/>

Looking at the contents of the stuff local is giving.. it is only
those files which are local to IAD2 and nothing else.. as such I would
not use it in your builds.

On Mon, 21 Jun 2021 at 13:25, Ron Olson  wrote:
>
> Funny enough, neither did I.
>
> On 21 Jun 2021, at 11:58, Stephen John Smoogen wrote:
>
> > I don't know.
> >
> > on my systems I did a find /etc/mock/ -type f -print | xargs grep
> > infrastructure.fedoraproject.org and did not have any hits.
> >
> > On Mon, 21 Jun 2021 at 10:35, Ron Olson  wrote:
> >>
> >> Hmm, but why would it be pulling those? I’m merely trying to run mock on 
> >> my own machine in a script:
> >>
> >> BUILD=epel-8-x86_64
> >> #echo Cleaning $BUILD
> >> #mock -r $BUILD --scrub=all
> >> mock --clean -r $BUILD --enablerepo=local --spec=swift-lang.spec 
> >> --sources=../SOURCES --resultdir=$MYDIR/mock-results --buildsrpm --rebuild 
> >> --rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee 
> >> $MYDIR/mock-results/build-output.txt
> >>
> >>
> >>
> >> On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:
> >>
> >>> On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:
> 
>  Hey all-
> 
>  I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails 
>  with:
> 
> 
>  [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>  403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
>  [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>  403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
>  (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 
>  00:02
>  [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>  403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
>  [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>  403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
>  [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 
>  403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
>  Error: Error downloading packages:
>    Status code: 403 for 
>  https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>   (IP: 38.145.60.16)
> 
> >>>
> >>> I believe the problem is that you have
> >>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
> >>> listed in some mock file versus
> >>> https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'
> >>>
> >>> The infrastructure URL is only available to Fedoraproject builders
> >>> while the kojipkgs should be available everywhere.
> >>>
> >>>
> >>>
> >>> --
> >>> Stephen J Smoogen.
> >>> I've seen things you people wouldn't believe. Flame wars in
> >>> sci.astro.orion. I have seen SPAM filters overload because of Godwin's
> >>> Law. All those moments will be lost in time... like posts on  BBS...
> >>> time to reboot.
> >>>

[rpms/perl-libwww-perl] PR #4: Bump 6.54 and 6.55

2021-06-21 Thread Michal Josef Špaček


mspacek merged a pull-request against the project: `perl-libwww-perl` that you 
are following.

Merged pull-request:

``
Bump 6.54 and 6.55
``

https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/4
___
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: Forbidden to download EPEL packages?

2021-06-21 Thread Ron Olson

Funny enough, neither did I.

On 21 Jun 2021, at 11:58, Stephen John Smoogen wrote:

> I don't know.
>
> on my systems I did a find /etc/mock/ -type f -print | xargs grep
> infrastructure.fedoraproject.org and did not have any hits.
>
> On Mon, 21 Jun 2021 at 10:35, Ron Olson  wrote:
>>
>> Hmm, but why would it be pulling those? I’m merely trying to run mock on my 
>> own machine in a script:
>>
>> BUILD=epel-8-x86_64
>> #echo Cleaning $BUILD
>> #mock -r $BUILD --scrub=all
>> mock --clean -r $BUILD --enablerepo=local --spec=swift-lang.spec 
>> --sources=../SOURCES --resultdir=$MYDIR/mock-results --buildsrpm --rebuild 
>> --rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee 
>> $MYDIR/mock-results/build-output.txt
>>
>>
>>
>> On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:
>>
>>> On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:

 Hey all-

 I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails 
 with:


 [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)
 [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)
 (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 00:02
 [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)
 [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)
 [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)
 Error: Error downloading packages:
   Status code: 403 for 
 https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
  (IP: 38.145.60.16)

>>>
>>> I believe the problem is that you have
>>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
>>> listed in some mock file versus
>>> https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'
>>>
>>> The infrastructure URL is only available to Fedoraproject builders
>>> while the kojipkgs should be available everywhere.
>>>
>>>
>>>
>>> --
>>> Stephen J Smoogen.
>>> I've seen things you people wouldn't believe. Flame wars in
>>> sci.astro.orion. I have seen SPAM filters overload because of Godwin's
>>> Law. All those moments will be lost in time... like posts on  BBS...
>>> time to reboot.
>>> ___
>>> 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
>> ___
>> 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
>
>
>
> -- 
> Stephen J Smoogen.
> I've seen things you people wouldn't believe. Flame wars in
> sci.astro.orion. I have seen SPAM filters overload because of Godwin's
> Law. All those moments will be lost in time... like posts on  BBS...
> time to reboot.
> ___
> 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: 
>

Re: Forbidden to download EPEL packages?

2021-06-21 Thread Stephen John Smoogen

I don't know.

on my systems I did a find /etc/mock/ -type f -print | xargs grep
infrastructure.fedoraproject.org and did not have any hits.

On Mon, 21 Jun 2021 at 10:35, Ron Olson  wrote:
>
> Hmm, but why would it be pulling those? I’m merely trying to run mock on my 
> own machine in a script:
>
> BUILD=epel-8-x86_64
> #echo Cleaning $BUILD
> #mock -r $BUILD --scrub=all
> mock --clean -r $BUILD --enablerepo=local --spec=swift-lang.spec 
> --sources=../SOURCES --resultdir=$MYDIR/mock-results --buildsrpm --rebuild 
> --rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee 
> $MYDIR/mock-results/build-output.txt
>
>
>
> On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:
>
> > On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:
> >>
> >> Hey all-
> >>
> >> I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails 
> >> with:
> >>
> >>
> >> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
> >> for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
> >> for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >> (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 00:02
> >> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
> >> for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
> >> for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >> [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
> >> for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >> Error: Error downloading packages:
> >>   Status code: 403 for 
> >> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
> >>  (IP: 38.145.60.16)
> >>
> >
> > I believe the problem is that you have
> > https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
> > listed in some mock file versus
> > https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'
> >
> > The infrastructure URL is only available to Fedoraproject builders
> > while the kojipkgs should be available everywhere.
> >
> >
> >
> > --
> > Stephen J Smoogen.
> > I've seen things you people wouldn't believe. Flame wars in
> > sci.astro.orion. I have seen SPAM filters overload because of Godwin's
> > Law. All those moments will be lost in time... like posts on  BBS...
> > time to reboot.
> > ___
> > 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
> ___
> 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



-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on  BBS...
time to reboot.
___
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

[rpms/perl-libwww-perl] PR #4: Bump 6.54 and 6.55

2021-06-21 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-libwww-perl` that 
you are following:
``
Bump 6.54 and 6.55
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/4
___
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: Orphaned packages looking for new maintainers

2021-06-21 Thread Mikolaj Izdebski

On Mon, Jun 21, 2021 at 2:54 PM Andrew Bauer
 wrote:
>
> Looks like jakarta-mail affects quite a few packages. I have taken it.

You can transfer jakarta-mail package to me if you like. It's a
dependency of Ant which I'm maintainer of .

--
Mikolaj Izdebski

> ___
> 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
___
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: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)

2021-06-21 Thread Chris Murphy

On Mon, Jun 21, 2021 at 9:43 AM Chris Murphy  wrote:
>I don't think GRUB has exclusivity over this guid,
> and was always intended to be generic, I'm just not aware of any
> bootloader that uses it.

any ^other bootloader

-- 
Chris Murphy
___
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: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)

2021-06-21 Thread Peter Robinson

On Thu, Jun 3, 2021 at 10:47 PM Neal Gompa  wrote:
>
> On Thu, Jun 3, 2021 at 4:53 PM Marcin Juszkiewicz
>  wrote:
> >
> > W dniu 03.06.2021 o 22:35, Ben Cotton pisze:
> > > https://fedoraproject.org/wiki/Changes/FedoraCloudHybridBoot
> > >
> > > == Summary ==
> > >
> > > With recent changes in public cloud widely accepting the
> > > use of UEFI boot, it would be consistent to add hybrid boot in support of
> > > both unifying the legacy (BIOS) and UEFI boot to the Fedora Linux
> > > cloud base images.
> > >
> >
> > > == Detailed Description ==
> > > The Fedora Cloud Edition image will be updated to be configured with
> > > multiple partitions and a GPT label instead of one single partition
> > > and implicit MBR.
> > >
> > > The partition order will be:
> > >
> > > # A BIOS boot partition
> > > # An EFI System partition
> > > # A general data partition
> >
> > Please make first partition at least 4MB in size. Those Arm/AArch64
> > systems which store bootloaders on boot media will have a space for it
> > (as some already read from around that area).
>
> Sure we can, but for AArch64 images, wouldn't we just be UEFI only
> anyway? I think we already produce these images as UEFI only for
> AArch64...

Correct.
___
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: F35 Change: Broken RPATH will fail rpmbuild (System-Wide Change proposal)

2021-06-21 Thread Charalampos Stratakis

On Thu, Jun 17, 2021 at 5:46 PM Michael Catanzaro 
wrote:

>
> Hi, the script is failing the glib2 build due to an invalid rpath, but
> unless I'm missing something obvious, I think it's valid. Reported:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1973304
>
>
>
I've sent an upstream PR for that case as well:
https://github.com/rpm-software-management/rpm/pull/1721

-- 
Regards,

Charalampos Stratakis
Senior Software Engineer
Python Maintenance Team, Red Hat
___
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: F35 Change: Broken RPATH will fail rpmbuild (System-Wide Change proposal)

2021-06-21 Thread Charalampos Stratakis

On Thu, Jun 17, 2021 at 5:17 PM Tom Stellard  wrote:

> On 6/16/21 10:58 PM, Tom Stellard wrote:
> > On 6/16/21 2:11 PM, Charalampos Stratakis wrote:
> >> On Wed, Jun 16, 2021 at 1:56 AM Tom Stellard  > wrote:
> >>
> >> On 5/7/21 10:48 AM, Ben Cotton wrote:
> >>  >
> https://fedoraproject.org/wiki/Changes/Broken_RPATH_will_fail_rpmbuild <
> https://fedoraproject.org/wiki/Changes/Broken_RPATH_will_fail_rpmbuild>
> >>  >
> >>  > == Summary ==
> >>  > Enable broken RPATH detection
> >>  > [
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_brp_buildroot_policy_scripts
> <
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_brp_buildroot_policy_scripts
> >
> >>  > buildroot policy] script by default. This will make the RPM
> build fail
> >>  > once a broken RPATH was detected within a binary or a shared
> library
> >>  > file. An opt-out mechanism will be provided as well.
> >>  >
> >>  > == Owner ==
> >>  > * Name: [[User:cstratak| Charalampos Stratakis]]
> >>  > * Email: cstratak AT redhat.com 
> >>  >
> >>  >
> >>
> >> Hi,
> >>
> >> Was there any testing done to determine how much this script would
> increase
> >> build times?  I've noticed it takes quite a while on the kernel
> builds, and
> >> I'm curious what factors influence how long the script takes.  Is it
> >> number of binaries, binary sizes, etc?
> >>
> >> -Tom
> >> ___
> >> devel mailing list -- devel@lists.fedoraproject.org  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/ <
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> >> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines <
> https://fedoraproject.org/wiki/Mailing_list_guidelines>
> >> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> <
> 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 <
> https://pagure.io/fedora-infrastructure>
> >>
> >>
> >> Hey Tom,
> >>
> >> Unfortunately no, a potential increase in build time was not taken into
> account at the time of the implementation of this change, as it never came
> up when considering other buildroot policy scripts as well.
> >>
> >> Here is the actual script that runs:
> https://github.com/rpm-software-management/rpm/blob/rpm-4.16.x/scripts/check-rpaths-worker
> <
> https://github.com/rpm-software-management/rpm/blob/rpm-4.16.x/scripts/check-rpaths-worker
> >
> >>
> >> Could you try and compare two scratch builds? One as is and one by
> adding |%global __brp_check_rpaths %{nil} |at the SPEC?|
> >> |
> >>
> >
> > Instead of doing two scratch builds, I just added:
> > %global __brp_check_rpaths time /usr/lib/rpm/check-rpaths to the spec
> file
> > and did a scratch build[1].
> >
> > The results on x86_64 were:
> >
> > real13m51.517s
> > user8m53.216s
> > sys7m34.105s
> >
> > Overall build time for the scratch build was 88m37s, so  that means
> check-rpaths
> > accounted for 15% of the build time.  I'm going to do some more tests on
> some
> > of the larger packages I maintain (llvm and clang) and see what the
> impact is.
> >
>
> LLVM was ~2 minutes and clang ~30 seconds, so not that big of an impact.
> The
> kernel build might just be an outlier.
>
> -Tom
>
> > I do think it would be worth trying to profile the script and see if
> there is
> > room for optimization.
> >
> > - Tom
> >
> > [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=70270039
> >
> >
> >
> >> Also adding here for completion that the script will also check for
> RUNPATH as of rpm 4.17:
> https://github.com/rpm-software-management/rpm/pull/1487/files <
> https://github.com/rpm-software-management/rpm/pull/1487/files>
> >>
> >> --
> >> Regards,
> >>
> >> Charalampos Stratakis
> >> Senior Software Engineer
> >> Python Maintenance Team, Red Hat
> >>
> >> ___
> >> 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
> >>
> >
>
>
Optimization PR upstream:
https://github.com/rpm-software-management/rpm/pull/1714

-- 
Regards,

Charalampos Stratakis
Senior Software Engineer
Python

Re: F35 Change: Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support (System-Wide Change)

2021-06-21 Thread Chris Murphy

On Thu, Jun 3, 2021 at 2:53 PM Marcin Juszkiewicz
 wrote:
>

> > The partition order will be:
> >
> > # A BIOS boot partition
> > # An EFI System partition
> > # A general data partition
>
> Please make first partition at least 4MB in size. Those Arm/AArch64
> systems which store bootloaders on boot media will have a space for it
> (as some already read from around that area).

I'm confused what image(s) you're referring to because, e.g.
Fedora-Cloud-Base-Rawhide-20210621.n.0.aarch64.raw has this partition
scheme:

Number  Start (sector)End (sector)  Size   Code  Name
   12048 1230847   600.0 MiB   EF00  EFI System Partition
   2 1230848 3327999   1024.0 MiB  8300
   3 332800010483711   3.4 GiB 8300

Do you want the 1st partition to also have BIOS Boot? (partition type
guid 21686148-6449-6E6F-744E-65656445464)   GRUB maintainers have said
1 MiB is sufficient in the past; so I just want to make sure the first
partition you're referring to should have both this particular type
GUID and be 4 MiB? I don't think GRUB has exclusivity over this guid,
and was always intended to be generic, I'm just not aware of any
bootloader that uses it.

Also, the scope of the hybrid UEFI/BIOS change is limited to x86_64,
while we could incidentally add BIOS Boot to the aarch64 images, I
don't expect we'd actually put anything there. It'd be outside the
scope of the change proposal.

-- 
Chris Murphy
___
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: x86_64-v2 in Fedora

2021-06-21 Thread PGNet Dev


On 6/18/21 1:42 AM, Mark Otaris wrote:

For Fedora, linux-hardware.org says 78% use EFI and 16% have Secure Boot 
enabled. Not a very good data set, though Fedora telemetry wouldn’t be either.

Of ~ 1K linux boxes in my env -- bare metal & VM, servers & desktops -- 
~ 550 are now running fully updated F34.

Of those, ~ 95% are AMD; remainder are Intel.  No ARM.

Of the total, per a quick survey,

~ 15% have _no_ avx/avx2 support
~ 40% have avx-only support
rest have avx/avx2 support

NONE of the no-avx or avx-only machines are "suffering" from any performance 
problems for their current business/technical usage.

Here, the 1st response to "my OS suddenly no longer supports this hardware" 
will seldom-if-ever be to replace the hardware.

At best, I'll freeze the machine's s/w base @ last-supported, and look to 
replace the OS.

There are real/significant costs to H/W upgrade/replacement -- both capital & 
expense;  Planning & budgeting for them is often on a multi-year timeframe.  
Particularly at scale.  And my env is relatively quite small on the global stage.

This seemingly endless stream of drop-the-old-hardware discussions, even if 
reasonable for some, is a cause for tangible concern that I've gotten myself 
into a tactical, eggs-in-one-basket mess.  Again.

With RockyLinux today at GA, time to explore/compare a 'plan B' & whether it 
provides some differently sensible support planning.
Or whether YA-x-distro firedrill is inevitable.


( "fun fact" for me:

my own laptop that sits ~ 3 ft from me as I type this, serves as my 
diagnostic/troubleshooting box on my LAN, and when traveling, obviously falls 
into the currently discussed 'decrepit' pile, lacking modern flags

egrep "model name|flags" /proc/cpuinfo | head -n2
model name  : Intel(R) Core(TM) i3 CPU   M 370  
@ 2.40GHz
flags   : fpu vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm 
pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 
ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid dtherm arat flush_l1d

but _very_ capably runs

lsb_release -rd
Description:Fedora release 34 (Thirty Four)
Release:34

uname -rm
5.12.11-300.fc34.x86_64 x86_64

with

KDE 5.82.0 / Plasma 5.21.5

and, although I don't use, or plan to use, it as a networked build farm 
anytime soon ... bind9 certainly builds from source well enough on it; though, 
admittedly, takes awhile.

)
___
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-20210621.n.0 compose check report

2021-06-21 Thread Fedora compose checker

No missing expected images.

Compose FAILS proposed Rawhide gating check!
2 of 43 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 22/134 (aarch64), 12/199 (x86_64)

New failures (same test not failed in Fedora-Rawhide-20210620.n.0):

ID: 913359  Test: aarch64 Server-dvd-iso server_remote_logging_server@uefi
URL: https://openqa.fedoraproject.org/tests/913359
ID: 913364  Test: aarch64 Server-dvd-iso server_remote_logging_client@uefi
URL: https://openqa.fedoraproject.org/tests/913364
ID: 913384  Test: aarch64 Workstation-raw_xz-raw.xz unwanted_packages@uefi
URL: https://openqa.fedoraproject.org/tests/913384
ID: 913489  Test: aarch64 universal install_cyrillic_language@uefi
URL: https://openqa.fedoraproject.org/tests/913489
ID: 913497  Test: aarch64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/913497
ID: 913502  Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/913502
ID: 913519  Test: aarch64 universal upgrade_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/913519

Old failures (same test failed in Fedora-Rawhide-20210620.n.0):

ID: 913194  Test: x86_64 Server-dvd-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/913194
ID: 913217  Test: x86_64 Server-dvd-iso 
server_role_deploy_domain_controller **GATING**
URL: https://openqa.fedoraproject.org/tests/913217
ID: 913220  Test: x86_64 Server-dvd-iso server_remote_logging_server
URL: https://openqa.fedoraproject.org/tests/913220
ID: 913234  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/913234
ID: 913235  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/913235
ID: 913236  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/913236
ID: 913239  Test: x86_64 Server-dvd-iso server_remote_logging_client
URL: https://openqa.fedoraproject.org/tests/913239
ID: 913242  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/913242
ID: 913247  Test: x86_64 Workstation-live-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/913247
ID: 913268  Test: x86_64 KDE-live-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/913268
ID: 913279  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/913279
ID: 913289  Test: x86_64 Silverblue-dvd_ostree-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/913289
ID: 913322  Test: aarch64 Server-dvd-iso 
server_role_deploy_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/913322
ID: 913325  Test: aarch64 Server-dvd-iso anaconda_help@uefi
URL: https://openqa.fedoraproject.org/tests/913325
ID: 913350  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/913350
ID: 913351  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/913351
ID: 913352  Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi
URL: https://openqa.fedoraproject.org/tests/913352
ID: 913365  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/913365
ID: 913377  Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing@uefi
URL: https://openqa.fedoraproject.org/tests/913377
ID: 913380  Test: aarch64 Workstation-raw_xz-raw.xz 
desktop_update_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/913380
ID: 913388  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/913388
ID: 913389  Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi
URL: https://openqa.fedoraproject.org/tests/913389
ID: 913482  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/913482
ID: 913488  Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/913488
ID: 913510  Test: aarch64 universal install_european_language@uefi
URL: https://openqa.fedoraproject.org/tests/913510
ID: 913553  Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/913553
ID: 913554  Test: aarch64 Server-dvd-iso install_vncconnect_server@uefi
URL: https://openqa.fedoraproject.org/tests/913554

Soft failed openQA tests: 7/199 (x86_64), 4/134 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Rawhide-20210620.n.0):

ID: 913307  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/913307
ID: 913309

[Bug 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142



--- Comment #3 from Fedora Update System  ---
FEDORA-2021-a208f35688 has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-a208f35688


-- 
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 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142



--- Comment #2 from Fedora Update System  ---
FEDORA-2021-1c8320e115 has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-1c8320e115


-- 
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 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Config-INI-Reader-Orde
   ||red-0.021-1.fc35



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.


-- 
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-20210621.0 compose check report

2021-06-21 Thread Fedora compose checker

No missing expected images.

Failed openQA tests: 7/15 (aarch64), 2/16 (x86_64)

New failures (same test not failed in Fedora-IoT-35-20210620.0):

ID: 913545  Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_rebase@uefi
URL: https://openqa.fedoraproject.org/tests/913545

Old failures (same test failed in Fedora-IoT-35-20210620.0):

ID: 913528  Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server
URL: https://openqa.fedoraproject.org/tests/913528
ID: 913537  Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition
URL: https://openqa.fedoraproject.org/tests/913537
ID: 913538  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/913538
ID: 913540  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/913540
ID: 913544  Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi
URL: https://openqa.fedoraproject.org/tests/913544
ID: 913546  Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/913546
ID: 913551  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/913551
ID: 913552  Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi
URL: https://openqa.fedoraproject.org/tests/913552

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-35-20210620.0):

ID: 913522  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/913522
ID: 913523  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/913523
ID: 913524  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/913524
ID: 913539  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/913539

Passed openQA tests: 10/16 (x86_64), 7/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

[rpms/perl-Config-INI-Reader-Ordered] PR #1: Tests

2021-06-21 Thread Petr Pisar


ppisar merged a pull-request against the project: 
`perl-Config-INI-Reader-Ordered` that you are following.

Merged pull-request:

``
Tests
``

https://src.fedoraproject.org/rpms/perl-Config-INI-Reader-Ordered/pull-request/1
___
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

[rpms/perl-Config-INI-Reader-Ordered] PR #1: Tests

2021-06-21 Thread Petr Pisar


ppisar opened a new pull-request against the project: 
`perl-Config-INI-Reader-Ordered` that you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Config-INI-Reader-Ordered/pull-request/1
___
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: Forbidden to download EPEL packages?

2021-06-21 Thread Ron Olson

Hmm, but why would it be pulling those? I’m merely trying to run mock on my own 
machine in a script:

BUILD=epel-8-x86_64
#echo Cleaning $BUILD
#mock -r $BUILD --scrub=all
mock --clean -r $BUILD --enablerepo=local --spec=swift-lang.spec 
--sources=../SOURCES --resultdir=$MYDIR/mock-results --buildsrpm --rebuild 
--rpmbuild-opts=--noclean --no-cleanup-after 2>&1 | tee 
$MYDIR/mock-results/build-output.txt



On 21 Jun 2021, at 6:48, Stephen John Smoogen wrote:

> On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:
>>
>> Hey all-
>>
>> I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails with:
>>
>>
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
>> for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
>> for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 00:02
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
>> for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
>> for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 
>> for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>> Error: Error downloading packages:
>>   Status code: 403 for 
>> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>>  (IP: 38.145.60.16)
>>
>
> I believe the problem is that you have
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
> listed in some mock file versus
> https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'
>
> The infrastructure URL is only available to Fedoraproject builders
> while the kojipkgs should be available everywhere.
>
>
>
> -- 
> Stephen J Smoogen.
> I've seen things you people wouldn't believe. Flame wars in
> sci.astro.orion. I have seen SPAM filters overload because of Godwin's
> Law. All those moments will be lost in time... like posts on  BBS...
> time to reboot.
> ___
> 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
___
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 1974142] perl-Config-INI-Reader-Ordered-0.021 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974142

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
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: [HEADS UP] Moving to sip 5 in Rawhide

2021-06-21 Thread Scott Talbert


On Wed, 16 Jun 2021, Scott Talbert wrote:

Just a heads-up, I've been working on converting packages from sip 4 to sip 5 
in Rawhide.  (sip is the Python bindings generation system used by PyQt and 
wxPython.)


I'm planning on opening pull requests against the affected packages soon. 
Please DO NOT merge these PRs yet - they need to be merged and built in a 
side tag in order to build them in the correct order.  Please DO review and 
comment on the PRs though.  Kevin and Rex will be helping merge and build 
once the changes are reviewed.


The sip 5 changes are planned for F35+ only.  Please let me know in the PR if 
you prefer the changes to be fast-forwardable to older releases and I'll %if 
guard them.


The affected packages are:
python-pyqt5-sip -> NEW package
calibre
krita
plplot
pyqtwebengine
python-pyqtchart
python-qt5
python3-poppler-qt5
qgis
qhexedit2
qscintilla
scidavis
sip
veusz


All, I opened all the relevant PRs a few days ago.  Please review and 
comment if you haven't already (thanks for the feedback thus far).


I'd like to get these changes completed this week if possible.

Thanks,
Scott
___
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

python-connection_pool Review Swap

2021-06-21 Thread Aniket Pradhan

Hello everyone!

I was packaging up some deps for a tool which would be useful in
NeuroFedora [0].

A package review for python-connection_pool is still pending to
proceed further, and I would be happy to swap them with other
developers here :D

Review: https://bugzilla.redhat.com/show_bug.cgi?id=1973934

To know more about NeuroFedora, please checkout our documentation [0]
or Labs page [1].

[0]: https://docs.fedoraproject.org/en-US/neurofedora/overview/
[1]: https://labs.fedoraproject.org/en/comp-neuro/


-- 
Thanks
Regards

Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
___
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

pghmcfc pushed to perl-Params-ValidationCompiler (rawhide). "Rename .rpmlint ??? perl-Params-ValidationCompiler.rpmlintrc"

2021-06-21 Thread notifications

Notification time stamped 2021-06-21 12:34:43 UTC

From d7ad7a9c8a487c0966ae8c9eef8f20f57d669848 Mon Sep 17 00:00:00 2001
From: Paul Howarth 
Date: Jun 21 2021 12:34:25 +
Subject: Rename .rpmlint ⇒ perl-Params-ValidationCompiler.rpmlintrc


---

diff --git a/.rpmlint b/.rpmlint
deleted file mode 100644
index b53aedf..000
--- a/.rpmlint
+++ /dev/null
@@ -1,3 +0,0 @@
-from Config import *
-addFilter("spelling-error %description -l en_US uncompromised -> ");
-addFilter("spelling-error Summary\(en_US\) validator -> ");
diff --git a/perl-Params-ValidationCompiler.rpmlintrc 
b/perl-Params-ValidationCompiler.rpmlintrc
new file mode 100644
index 000..b53aedf
--- /dev/null
+++ b/perl-Params-ValidationCompiler.rpmlintrc
@@ -0,0 +1,3 @@
+from Config import *
+addFilter("spelling-error %description -l en_US uncompromised -> ");
+addFilter("spelling-error Summary\(en_US\) validator -> ");



https://src.fedoraproject.org/rpms/perl-Params-ValidationCompiler/c/d7ad7a9c8a487c0966ae8c9eef8f20f57d669848?branch=rawhide
___
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

Orphaned packages looking for new maintainers

2021-06-21 Thread Miro Hrončok


The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets 
retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-06-21.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

 Package  (co)maintainers  Status Change

HdrHistogramacaringi, almac, hhorak, jvanek,   0 weeks ago
orphan
JSCookMenu  orphan 0 weeks ago
WebCalendar orphan 0 weeks ago
ant-antunit cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orion, orphan
apache-commons-daemon   cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orphan, spike
apache-commons-lang cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orphan, spike
automaton   orphan 2 weeks ago
biboumi louizatakk, orphan 0 weeks ago
directory-maven-plugin  almac, orphan, sasiddiq0 weeks ago
dpsearchcodeblock, jam3s, orphan   3 weeks ago
electrumorphan 1 weeks ago
erlang-riak_pipebowlofeggs, erlang-maint-sig, orphan   1 weeks ago
felix-scr   jerboaa, orphan0 weeks ago
git-cal codeblock, orphan  3 weeks ago
jakarta-activation  java-maint-sig, orphan 0 weeks ago
jakarta-mailjava-maint-sig, orphan 0 weeks ago
java-atk-wrapperomajid, orphan 1 weeks ago
jboss-annotations-1.2-api   cfu, cipherboy, ckelley, dmoluguw, 0 weeks ago
jmagne, mharmsen, orphan
jboss-jms-1.1-api   cipherboy, dmoluguw, jmagne, lef,  4 weeks ago
orphan
jboss-logmanagercipherboy, dmoluguw, gil, jmagne,  2 weeks ago
lef, orphan
jmc almac, orphan, sasiddiq0 weeks ago
jmc-corealmac, orphan, sasiddiq0 weeks ago
luitajax, ofourdan, orphan 2 weeks ago
lz4-javaorphan 0 weeks ago
mate-applet-softupd orphan 0 weeks ago
maven-javadoc-pluginjava-maint-sig, mizdebsk, orphan   5 weeks ago
mvelorphan 0 weeks ago
owasp-java-encoder  almac, orphan, sasiddiq0 weeks ago
paranamer   cipherboy, jmagne, orphan  4 weeks ago
perl-Debug-Client   orphan, ppisar 1 weeks ago
perl-Hardware-Vhdl-Tidy orphan 6 weeks ago
perl-Padre  orphan, ppisar 1 weeks ago
php-PHPMailer   orphan, remi   0 weeks ago
php-captchaphp  orphan 0 weeks ago
php-hkitorphan 0 weeks ago
php-pear-Auth-Yubicoorphan 0 weeks ago
php-rmccue-requests orphan 1 weeks ago
python-fn   codeblock, orphan  3 weeks ago
python-glusterfs-apihumble, orphan 0 weeks ago
python-pytest-relaxed   orphan 1 weeks ago
python-tempita  kylev, orphan  0 weeks ago
qtpass  marcindulak, orphan, vascom4 weeks ago
robodoc orphan 0 weeks ago
rubygem-ditzorphan 3 weeks ago

Re: Orphaned packages looking for new maintainers

2021-06-21 Thread Andrew Bauer

Looks like jakarta-mail affects quite a few packages. I have taken 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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

RE: Self Introduction: Anatoly Vildemanov

2021-06-21 Thread Anatoly Vildemanov

Hi,

Could you please add me to 'packages' group
I will support package process for ucx  https://src.fedoraproject.org/rpms/ucx

Thanks

-Original Message-
From: Anatoly Vildemanov 
Sent: Wednesday, April 28, 2021 10:47 AM
To: Development discussions related to Fedora 
Cc: Vitaly Zaitsev 
Subject: RE: Self Introduction: Anatoly Vildemanov

Hi,

I following this instructions, create fedora/Bugzilla account , join to all 
important mail list , and will support ucx package 
https://src.fedoraproject.org/rpms/ucx
What's else shall I do for join to packages group and ucx group for create ucx 
package 

Thanks

-Original Message-
From: Vitaly Zaitsev via devel 
Sent: Tuesday, April 27, 2021 1:32 PM
To: devel@lists.fedoraproject.org
Cc: Vitaly Zaitsev 
Subject: Re: Self Introduction: Anatoly Vildemanov

External email: Use caution opening links or attachments


On 27.04.2021 12:11, Anatoly Vildemanov wrote:
> And I will do packages UCX for fedora
> For this could you please add me to "packager" group like member

Hello and welcome to Fedora. Please follow this procedure:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FJoin_the_package_collection_maintainersdata=04%7C01%7Canatolyv%40nvidia.com%7Cefccae2d4eb44a6ea0f508d90967d029%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637551163746854074%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=nXY5hVu2j4%2BSQWCYHaLz77kJsSZbB4HfLv%2FkTZTOegQ%3Dreserved=0

--
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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.fedoraproject.org%2Fen-US%2Fproject%2Fcode-of-conduct%2Fdata=04%7C01%7Canatolyv%40nvidia.com%7Cefccae2d4eb44a6ea0f508d90967d029%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637551163746854074%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=TvsI40%2F8RBExCUPd5ShvHF8g1Z4FT0ys3mrBd%2FBnFyY%3Dreserved=0
List Guidelines: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffedoraproject.org%2Fwiki%2FMailing_list_guidelinesdata=04%7C01%7Canatolyv%40nvidia.com%7Cefccae2d4eb44a6ea0f508d90967d029%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637551163746854074%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Y8t4rLCO1bOfUREtHFBrFZUl%2Bn8bKRVjGO26DcZLt5Q%3Dreserved=0
List Archives: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.fedoraproject.org%2Farchives%2Flist%2Fdevel%40lists.fedoraproject.orgdata=04%7C01%7Canatolyv%40nvidia.com%7Cefccae2d4eb44a6ea0f508d90967d029%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637551163746854074%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ZqrM4ny90AduCfygFX8z8r87ke77S5vwaCpXsBQP%2FH8%3Dreserved=0
Do not reply to spam on the list, report it: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpagure.io%2Ffedora-infrastructuredata=04%7C01%7Canatolyv%40nvidia.com%7Cefccae2d4eb44a6ea0f508d90967d029%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637551163746864066%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=eiWxYA%2Baajyl%2Big3P3J3lYGK4oT%2BCaYmwp%2Bx0V2HmL4%3Dreserved=0
___
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: 20210621.n.0 changes

2021-06-21 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20210620.n.0
NEW: Fedora-Rawhide-20210621.n.0

= SUMMARY =
Added images:0
Dropped images:  2
Added packages:  0
Dropped packages:1
Upgraded packages:   31
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:871.42 KiB
Size of upgraded packages:   536.46 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   3.46 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Cloud_Base vagrant-libvirt x86_64
Path: 
Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-Rawhide-20210620.n.0.x86_64.vagrant-libvirt.box
Image: Cloud_Base vagrant-virtualbox x86_64
Path: 
Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-Rawhide-20210620.n.0.x86_64.vagrant-virtualbox.box

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: python-langdetect-1.0.8-2.fc35
Summary: Language detection library ported from Google's language-detection
RPMs:python3-langdetect
Size:871.42 KiB


= UPGRADED PACKAGES =
Package:  COPASI-4.33.246-1.fc35
Old package:  COPASI-4.31.243-2.fc35
Summary:  Biochemical network simulator
RPMs: COPASI COPASI-data COPASI-doc COPASI-gui python3-COPASI
Size: 66.63 MiB
Size change:  -738.99 KiB
Changelog:
  * Sun Jun 20 2021 Antonio Trande  - 4.33.246-1
  - Release 4.33 build-246


Package:  We10X-icon-theme-0-14.20210617git8738028b.fc35
Old package:  We10X-icon-theme-0-13.20210409git89d8aa7b.fc35
Summary:  Colorful icon theme inspired by Microsoft Windows 10 aesthetic
RPMs: We10X-icon-theme
Size: 4.31 MiB
Size change:  -1.24 MiB
Changelog:
  * Sun Jun 20 2021 Artur Frenszek-Iwicki  - 
0-14.20210617git8738028b
  - Update to latest upstream git snapshot


Package:  apt-2.3.6-1.fc35
Old package:  apt-2.3.5-1.fc35
Summary:  Command-line package manager for Debian packages
RPMs: apt apt-apidoc apt-devel apt-doc apt-libs apt-utils
Size: 16.65 MiB
Size change:  -3.10 KiB
Changelog:
  * Wed Jun 09 2021 Fedora Release Monitoring 
 - 2.3.6-1
  - Update to 2.3.6 (#1969935)


Package:  ddnet-15.5.4-1.fc35
Old package:  ddnet-15.5.2-1.fc35
Summary:  DDraceNetwork, a cooperative racing mod of Teeworlds
RPMs: ddnet ddnet-data ddnet-server
Size: 31.56 MiB
Size change:  -6.33 KiB
Changelog:
  * Sun Jun 20 2021 mockbuilder - 15.5.3-1
  - Update to version 15.5.3.

  * Sun Jun 20 2021 mockbuilder - 15.5.4-1
  - Update to 15.5.4.


Package:  dippi-3.1.0-1.fc35
Old package:  dippi-2.7.4-6.fc35
Summary:  Calculate display info like DPI and aspect ratio
RPMs: dippi
Size: 623.35 KiB
Size change:  22.11 KiB
Changelog:
  * Sun Jun 20 2021 Benjamin A. Beasley  - 3.1.0-1
  - Update to 3.1.0 (closes RHBZ#1974022)
  - Upstream license is now clearly GPLv3+ with CC0 AppStream metadata file;
updated License to GPLv3+ effective license
  - Updated Portuguese (pt) translation, and added Turkish (tr) translation


Package:  dmlite-1.15.0-4.fc35
Old package:  dmlite-1.15.0-2.fc35
Summary:  Lcgdm grid data management and storage framework
RPMs: dmlite-apache-httpd dmlite-devel dmlite-docs dmlite-dome 
dmlite-dpm-dsi dmlite-dpm-tester dmlite-dpm-xrootd dmlite-dpmdisk-domeonly 
dmlite-dpmhead-domeonly dmlite-libs dmlite-plugins-domeadapter 
dmlite-plugins-librarian dmlite-plugins-memcache dmlite-plugins-mysql 
dmlite-plugins-profiler dmlite-private-devel dmlite-puppet-dpm dmlite-shell 
python3-dmlite
Size: 21.29 MiB
Size change:  -2.19 KiB

Package:  dummy-test-package-gloster-0-4131.fc35
Old package:  dummy-test-package-gloster-0-4110.fc35
Summary:  Dummy Test Package called Gloster
RPMs: dummy-test-package-gloster
Size: 254.99 KiB
Size change:  1.24 KiB
Changelog:
  * Sun Jun 20 2021 packagerbot  - 0-4111
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4112
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4113
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4114
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4115
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4116
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4117
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4118
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4119
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4120
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4121
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4122
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4123
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4124
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4125
  - rebuilt

  * Sun Jun 20 2021 packagerbot  - 0-4126
  - rebuilt

  * Mon Jun 21 2021 packagerbot  - 0-4127
  - rebuilt

  * Mon Jun 21 2021 packagerbot  - 0-4128
  - rebuilt

  * Mon Jun 21 2021 packagerbot  - 0-4129
  - rebuilt

  * Mon Jun 21 2021 packagerbot  - 0-4130
  - rebuilt

  * Mon Jun 21 2021 packagerbot  - 0-4131
  - rebuilt


Package

Re: intent to orphan notice: python-nss

2021-06-21 Thread Alexander Scheel

This has been orphaned. 

- A
___
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: Updating sources file using fedpkg

2021-06-21 Thread Ewoud Kohl van Wijngaarden


On Thu, Jun 17, 2021 at 09:02:12PM +0300, Otto Urpelainen wrote:

Ken Dreyer kirjoitti 17.6.2021 klo 19.04:

On Thu, Jun 17, 2021 at 8:33 AM Richard Shaw  wrote:


On Thu, Jun 17, 2021 at 7:22 AM Ewoud Kohl van Wijngaarden 
 wrote:



To be clear: I don't want to fiddle with the sources file, hence this
email. However, I would like to at least complete a local mockbuild
before uploading to the lookaside cache. It is my understanding that
new-sources always does this.



That's actually a nit I've been tempted to complain about. If I'm upgrading a 
package to a new version I update the spec file:

rpmdev-bumpspec -n  -c "Update to ." *.spec

And download the new source:

spectool -g *.spec

But then I have to upload the new source with 'fedpkg new-sources' if I don't 
want it to download the old version.


Yeah, the way I deal with this is I zero out the sources file, like ">
sources". Or another alternative that I use sometimes is "sha512sum
--tag", like:

  sha512sum --tag kstart-4.2.tar.gz > sources


This is really helpful! I did not know it's the output of the --tag 
parameter.




Hi Ewould and everybody,

I am a bit confused about this discussion. My fedpkg does not care 
about the 'sources' file or the lookaside cache at all on 'fedpkg 
mockbuild'. It simply looks up the expected filename of downloaded 
Source, grabs it from the local working directory and uses that. So 
for me this works:


   rpmdev-bumpspec -D -n 1.2.3 *.spec
   # Update specfile as needed
   spectool -g *.spec
   fedpkg mockbuild


Now it also downloads the old files mentioned in sources. In my 
experience it certainly does care about it.


Maybe my request can be reduced to: mockbuild should not download files 
not mentioned in the spec file. Ken did give a good workaround. Taking 
that a step further I think something like this would suffice for me:


spectool -l *.spec | awk '/https?:/ { print $2 }' | xargs -n 1 basename | xargs 
sha512sum --tag > sources

After that is done, the rpm is available at results_mypackage, I 
install it locally and see that everything works. At that point it is 
a good time do 'fedpkg new-sources'.


This I understand.

This also means that non-packagers actually *can* properly test their 
changes. The maintainer has to do new-sources, commit, push and build 
after merging the pull request, so annoyingly there are those steps to 
remember. But at least the pull request author does not have to submit 
their changes blindly.


A simple test to make sure that it really uses the local download:

   $ sed -i 's/^Source.*/Source:https:\/\/example.com\/foo/' *.spec
   $ fedpkg mockbuild
   SOME_OUTPUT
   error: Bad file: SOMEPATH/foo: No such file or directory
   $ touch foo
   $ fedpkg mockbuild
   LOTS_OF_OUTPUT
   SOME_ERROR_DUE_TO_EMPTY_SOURCE

When I started, I was having exactly the same trouble, so wrote 
something in the wiki:


https://fedoraproject.org/wiki/Package_maintenance_guide#Using_fedpkg_anonymously


That's certainly a good start. I'm hoping to remove even more obstackles 
for new contributors.

___
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: Forbidden to download EPEL packages?

2021-06-21 Thread Stephen John Smoogen

On Sun, 20 Jun 2021 at 18:25, Ron Olson  wrote:
>
> Hey all-
>
> I’m trying to run a mock build with EPEL-8 (epel-8-x86_64) and it fails with:
>
>
> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
> (230/232): gcc-c++-8.4.1-1.el8.x86_64.rpm   5.9 MB/s |  12 MB 00:02
> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
> [MIRROR] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
> [FAILED] kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm: Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
> Error: Error downloading packages:
>   Status code: 403 for 
> https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/kernel-headers-4.18.0-305.3.1.el8_4.x86_64.rpm
>  (IP: 38.145.60.16)
>

I believe the problem is that you have
https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest
listed in some mock file versus
https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/$basearch/\n'

The infrastructure URL is only available to Fedoraproject builders
while the kojipkgs should be available everywhere.



-- 
Stephen J Smoogen.
I've seen things you people wouldn't believe. Flame wars in
sci.astro.orion. I have seen SPAM filters overload because of Godwin's
Law. All those moments will be lost in time... like posts on  BBS...
time to reboot.
___
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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Zbigniew Jędrzejewski-Szmek

On Mon, Jun 21, 2021 at 07:34:03AM +, Mattia Verga via devel wrote:
> Bodhi has a config setting ('automatic_updates_blacklist') which can
> avoid specific users/bots to automatically create updates.
> 
> If those bots are supposed to only test Koji builds, but not pushing
> updates we can list them out using that setting.

I don't think we would go in this direction.
First, our Update Guidelines say that builds which are not intended to
become submitted as updates should not be done in koji.
Second, there are better ways to do scratch builds, doing them 
as real builds but then ignoring would be just confusing.
Third, to do a real build in koji, the changes need to be pushed to
dist-git, and the assumption is that an unrelated build might be
triggered at any time by other packagers (mass rebuilds, so-version
bumps, etc.), and this would then build that snapshot commit.

Zbyszek
___
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

[rpms/perl-libwww-perl] PR #3: 6.54 and 6.55 bump

2021-06-21 Thread Michal Josef Špaček


mspacek merged a pull-request against the project: `perl-libwww-perl` that you 
are following.

Merged pull-request:

``
6.54 and 6.55 bump
``

https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/3
___
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 1973977] perl-Pod-Weaver-4.018 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973977



--- Comment #3 from Fedora Update System  ---
FEDORA-2021-b58f75f46b has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-b58f75f46b


-- 
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 1973977] perl-Pod-Weaver-4.018 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973977



--- Comment #2 from Fedora Update System  ---
FEDORA-2021-2d004ae6b9 has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2d004ae6b9


-- 
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 1973319] perl-libwww-perl-6.55 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973319

Michal Josef Spacek  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
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

[rpms/perl-libwww-perl] PR #3: 6.54 and 6.55 bump

2021-06-21 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-libwww-perl` that 
you are following:
``
6.54 and 6.55 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-libwww-perl/pull-request/3
___
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 1973977] perl-Pod-Weaver-4.018 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973977

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value
 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Pod-Weaver-4.018-1.fc3
   ||5



--- Comment #1 from Petr Pisar  ---
An enhancement suitable for all Fedoras.


-- 
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

[rpms/perl-Test2-Suite] PR #4: F33: 0.000140 bump and package tests

2021-06-21 Thread Michal Josef Špaček


mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
F33: 0.000140 bump and package tests
``

https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/4
___
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

Next Open NeuroFedora Meeting: 1300 UTC on Monday, 21st June (Today)

2021-06-21 Thread Ankur Sinha

Hello everyone,

Please join us at the next Open NeuroFedora team meeting on Monday 21st
June (today!) at 1300UTC in #fedora-neuro on IRC (Freenode). The meeting
is a public meeting, and open for everyone to attend. You can join us
over:

IRC:
https://webchat.libera.chat/?channels=#fedora-neuro

Matrix: https://tinyurl.com/matrix-neurofedora

You can convert the meeting time to your local time using this command
in a terminal:
$ date --date='TZ="UTC" 1300 today'

or you can use this link:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting=20210621T13=%3A=1

The meeting will be chaired by @ankursinha. The agenda for the
meeting is:

- New introductions and roll call.
- Tasks from last week's meeting:
https://meetbot.fedoraproject.org/teams/neurofedora/neurofedora.2021-06-07-13.03.html
- Open Pagure tickets:
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
- Package health check:
 https://packager-dashboard.fedoraproject.org/neuro-sig
- Open package reviews check:
https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro
- Koschei packages check:
https://koschei.fedoraproject.org/groups/neuro-sig
- CompNeuro lab compose status check for F35:
https://koji.fedoraproject.org/koji/packageinfo?packageID=30691
- Neuroscience query of the week
- Next meeting day, and chair.
- Open floor.

We hope to see you there!

You can learn more about NeuroFedora here:
https://neuro.fedoraproject.org

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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

[rpms/perl-Test2-Suite] PR #4: F33: 0.000140 bump and package tests

2021-06-21 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
F33: 0.000140 bump and package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/4
___
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 1974137] F35FailsToInstall: perl-Pinto

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974137

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2021-06-21 10:18:13



--- Comment #2 from Jitka Plesnikova  ---
It should be fixed by perl-Throwable-0.201-3.fc35.


-- 
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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Fabio Valentini

On Mon, Jun 21, 2021 at 11:50 AM Ankur Sinha  wrote:
>
> On Sun, Jun 20, 2021 11:41:41 -0700, Kevin Fenzi wrote:
> > On Sun, Jun 20, 2021 at 03:26:52PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > >
> > > Yeah. I'm looking a the original ticket in
> > > https://pagure.io/fesco/issue/2228, and I think this was a mistake.
> > > We shouldn't have approved a bot that packages snapshot commits for
> > > rawhide. In the discussion, we talked about load on the infra, and ability
> > > to contact the maintainers, and even cooperation withb packit, but somehow
> > > the question whether we want this at all didn't come up.
> > >
> > > I guess the effort to make rawhide palatable hadn't really sunk in
> > > deep enough back then ;)
> >
> > Well, it's still not clear to me if these builds are not suitable for
> > rawhide, or if the bot that is pushing them just has bugs.
>
> A few podman updates have now caused major breakages for users even in
> stable releases. Here's a recent example:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-fc15685f73
> https://bugzilla.redhat.com/show_bug.cgi?id=1958546
> https://github.com/containers/podman/issues/10274
>
> ^ In this an RC went out all the way to the updates repo, but it seems
> like pushing RCs to testing is very common for podman:
> https://bodhi.fedoraproject.org/updates/?search==podman=F34=F33=2
>
> (This is not OK in my book either---volunteers using updates-testing to
> help test updates should not have to deal with updates that are not
> intended for distribution to users, but yet somehow do make it through
> from time to time.)
>
> It has now happened a couple of times (in my experience) that an update
> went out, *very* quickly reached stable (sometimes before it was even
> pushed to testing), and so reached users---where it was found that the
> update broke core functionality. Because it was already marked stable,
> by the time folks tested it out and gave negative karma, it could no
> longer be un-pushed.
>
> I don't think there's a policy against this, but apart from podman, I
> cannot recall seeing maintainers/dev teams give karma to their own
> packages' updates.  I don't think that works---the idea of Bodhi is to
> allow ample opportunity for *others* to test the update, no? If
> maintainers smoke test, push updates, and then again give karma based on
> the smoke test, they're hardly likely to catch issues? Here's one where
> an essentially broken update got 3 positive karma from folks involved in
> podman development:
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-cd7e382e0c
>
> Here's another where folks related to podman development said "works"
> (but gave negative karma to prevent it from going to stable) and then,
> it turned out that the update was actually broken:
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-ad5899f2c3
>
> I think bots are great but only as long as they continue to implement
> the packaging policies that we've all agreed on. The bot isn't doing
> that very well here.

I agree. The Updates Policy even states that packagers should only
ever push builds / updates if they're expected to be pushed to stable,
and letting things sit in "updates-testing" for extended periods of
time is forbidden.

Even the current, latest podman update in rawhide is stuck, and nobody
seems to be aware of this situation:

- FEDORA-2021-147a47d0f8 : stuck in "testing" due to failed gating
tests, obsoleted by:
- FEDORA-2021-d963d68cb7 : stuck in "testing" due to failed gating
tests, obsoleted by:
- FEDORA-2021-a710045a4c : stuck in "testing" due to failed gating
tests, obsoleted by:
- https://bodhi.fedoraproject.org/updates/FEDORA-2021-b255b5da0d :
stuck in "testing" due to failed gating tests

At this point, that's just a waste of resources, when builds are
submitted but never even reach repositories.

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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Miro Hrončok


On 21. 06. 21 11:48, Ankur Sinha wrote:

I don't think there's a policy against this, but apart from podman, I
cannot recall seeing maintainers/dev teams give karma to their own
packages' updates.  I don't think that works---the idea of Bodhi is to
allow ample opportunity for*others*  to test the update, no? If
maintainers smoke test, push updates, and then again give karma based on
the smoke test, they're hardly likely to catch issues?


For the record: I do that with the alternate Pythons. If a teammate pushes a 
bodhi update I've already reviewed during the pull request process, I karma it 
up to expedite it to stable.


(OTOH For the "main" Python version, we intentionally set the karma limits high 
enough to prevent "LGTM" karma pushing the the update to stable even before it 
reaches testing.)


--
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
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1974288] New: perl-5.34.0-479.fc35 FTBFS with gdbm-devel-1.20-1.fc35: ext/GDBM_File/t/gdbm.t: gdbm_firstkey: Item not found at ../../t/lib/dbmt_common.pl line 52.

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974288

Bug ID: 1974288
   Summary: perl-5.34.0-479.fc35 FTBFS with
gdbm-devel-1.20-1.fc35: ext/GDBM_File/t/gdbm.t:
gdbm_firstkey: Item not found at
../../t/lib/dbmt_common.pl line 52.
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl
  Assignee: jples...@redhat.com
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: caillon+fedoraproj...@gmail.com, iarn...@gmail.com,
jples...@redhat.com, ka...@ucw.cz,
mmasl...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com,
psab...@redhat.com, rhug...@redhat.com,
sandm...@redhat.com, spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



perl-5.34.0-479.fc35 fails to build in Fedora 35 if gdbm-devel-1.20-1.fc35 is
installed because a gdbm test fails:

../ext/FileCache/t/02maxopen.t ... ok
gdbm_firstkey: Item not found at ../../t/lib/dbmt_common.pl line 52.
Compilation failed in require at t/gdbm.t line 6.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 5.
../ext/GDBM_File/t/gdbm.t 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 5 subtests passed

This is probably triggered by upgrading gdbm from 1.19 to 1.20. From a GDBM
changelog:


Version 1.20, 2021-06-17

* New bucket cache

The bucket cache support has been rewritten from scratch.  The new
bucket cache code provides for significant speed up of search
operations.

* Change mmap prereading strategy

Pre-reading of the memory mapper regions, introduced in version 1.19
can be advantageous only when doing intensive look-ups on a read-only
database.  It degrades performance otherwise, especially if doing
multiple inserts.  Therefore, this version introduces a new flag
to gdbm_open: GDBM_PREREAD.  When given, it enables pre-reading of
memory mapped regions.

See https://github.com/Perl/perl5/issues/18884 for details.


-- 
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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Ankur Sinha

On Sun, Jun 20, 2021 11:41:41 -0700, Kevin Fenzi wrote:
> On Sun, Jun 20, 2021 at 03:26:52PM +, Zbigniew Jędrzejewski-Szmek wrote:
> > 
> > Yeah. I'm looking a the original ticket in
> > https://pagure.io/fesco/issue/2228, and I think this was a mistake.
> > We shouldn't have approved a bot that packages snapshot commits for
> > rawhide. In the discussion, we talked about load on the infra, and ability
> > to contact the maintainers, and even cooperation withb packit, but somehow
> > the question whether we want this at all didn't come up.
> > 
> > I guess the effort to make rawhide palatable hadn't really sunk in
> > deep enough back then ;)
> 
> Well, it's still not clear to me if these builds are not suitable for
> rawhide, or if the bot that is pushing them just has bugs.

A few podman updates have now caused major breakages for users even in
stable releases. Here's a recent example:

https://bodhi.fedoraproject.org/updates/FEDORA-2021-fc15685f73
https://bugzilla.redhat.com/show_bug.cgi?id=1958546
https://github.com/containers/podman/issues/10274

^ In this an RC went out all the way to the updates repo, but it seems
like pushing RCs to testing is very common for podman:
https://bodhi.fedoraproject.org/updates/?search==podman=F34=F33=2

(This is not OK in my book either---volunteers using updates-testing to
help test updates should not have to deal with updates that are not
intended for distribution to users, but yet somehow do make it through
from time to time.)

It has now happened a couple of times (in my experience) that an update
went out, *very* quickly reached stable (sometimes before it was even
pushed to testing), and so reached users---where it was found that the
update broke core functionality. Because it was already marked stable,
by the time folks tested it out and gave negative karma, it could no
longer be un-pushed.

I don't think there's a policy against this, but apart from podman, I
cannot recall seeing maintainers/dev teams give karma to their own
packages' updates.  I don't think that works---the idea of Bodhi is to
allow ample opportunity for *others* to test the update, no? If
maintainers smoke test, push updates, and then again give karma based on
the smoke test, they're hardly likely to catch issues? Here's one where
an essentially broken update got 3 positive karma from folks involved in
podman development:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-cd7e382e0c

Here's another where folks related to podman development said "works"
(but gave negative karma to prevent it from going to stable) and then,
it turned out that the update was actually broken:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ad5899f2c3

I think bots are great but only as long as they continue to implement
the packaging policies that we've all agreed on. The bot isn't doing
that very well here.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

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

Fedora-Cloud-34-20210621.0 compose check report

2021-06-21 Thread Fedora compose checker

No missing expected images.

Failed openQA tests: 8/8 (x86_64)

Old failures (same test failed in Fedora-Cloud-34-20210620.0):

ID: 913118  Test: x86_64 Cloud_Base-qcow2-qcow2 base_reboot_unmount
URL: https://openqa.fedoraproject.org/tests/913118
ID: 913119  Test: x86_64 Cloud_Base-qcow2-qcow2 base_services_start
URL: https://openqa.fedoraproject.org/tests/913119
ID: 913120  Test: x86_64 Cloud_Base-qcow2-qcow2 base_update_cli
URL: https://openqa.fedoraproject.org/tests/913120
ID: 913121  Test: x86_64 Cloud_Base-qcow2-qcow2 base_package_install_remove
URL: https://openqa.fedoraproject.org/tests/913121
ID: 913122  Test: x86_64 Cloud_Base-qcow2-qcow2 base_system_logging
URL: https://openqa.fedoraproject.org/tests/913122
ID: 913123  Test: x86_64 Cloud_Base-qcow2-qcow2 base_service_manipulation
URL: https://openqa.fedoraproject.org/tests/913123
ID: 913124  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/913124
ID: 913125  Test: x86_64 Cloud_Base-qcow2-qcow2 base_selinux
URL: https://openqa.fedoraproject.org/tests/913125

Soft failed openQA tests: 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-34-20210620.0):

ID: 913130  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/913130

Passed openQA tests: 7/8 (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

[rpms/perl-Test2-Suite] PR #3: 0.000140 bump and package tests

2021-06-21 Thread Michal Josef Špaček


mspacek merged a pull-request against the project: `perl-Test2-Suite` that you 
are following.

Merged pull-request:

``
0.000140 bump and package tests
``

https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/3
___
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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Dist-Zilla-Plugin-PodW
   ||eaver-4.009-1.fc35




-- 
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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968



--- Comment #3 from Fedora Update System  ---
FEDORA-2021-14dd399ce6 has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-14dd399ce6


-- 
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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-2021-2656950f5d has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-2656950f5d


-- 
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

[rpms/perl-Test2-Suite] PR #3: 0.000140 bump and package tests

2021-06-21 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Test2-Suite` that 
you are following:
``
0.000140 bump and package tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test2-Suite/pull-request/3
___
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

Orphaned packages looking for new maintainers

2021-06-21 Thread Miro Hrončok


The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets 
retired.

Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-06-21.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

 Package  (co)maintainers  Status Change

HdrHistogramacaringi, almac, hhorak, jvanek,   0 weeks ago
orphan
JSCookMenu  orphan 0 weeks ago
WebCalendar orphan 0 weeks ago
ant-antunit cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orion, orphan
apache-commons-daemon   cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orphan, spike
apache-commons-lang cipherboy, dmoluguw, jmagne,   4 weeks ago
mizdebsk, orphan, spike
automaton   orphan 2 weeks ago
biboumi louizatakk, orphan 0 weeks ago
directory-maven-plugin  almac, orphan, sasiddiq0 weeks ago
dpsearchcodeblock, jam3s, orphan   3 weeks ago
electrumorphan 1 weeks ago
erlang-riak_pipebowlofeggs, erlang-maint-sig, orphan   1 weeks ago
felix-scr   jerboaa, orphan0 weeks ago
git-cal codeblock, orphan  3 weeks ago
jakarta-activation  java-maint-sig, orphan 0 weeks ago
jakarta-mailjava-maint-sig, orphan 0 weeks ago
java-atk-wrapperomajid, orphan 1 weeks ago
jboss-annotations-1.2-api   cfu, cipherboy, ckelley, dmoluguw, 0 weeks ago
jmagne, mharmsen, orphan
jboss-jms-1.1-api   cipherboy, dmoluguw, jmagne, lef,  4 weeks ago
orphan
jboss-logmanagercipherboy, dmoluguw, gil, jmagne,  2 weeks ago
lef, orphan
jmc almac, orphan, sasiddiq0 weeks ago
jmc-corealmac, orphan, sasiddiq0 weeks ago
luitajax, ofourdan, orphan 2 weeks ago
lz4-javaorphan 0 weeks ago
mate-applet-softupd orphan 0 weeks ago
maven-javadoc-pluginjava-maint-sig, mizdebsk, orphan   5 weeks ago
mvelorphan 0 weeks ago
owasp-java-encoder  almac, orphan, sasiddiq0 weeks ago
paranamer   cipherboy, jmagne, orphan  4 weeks ago
perl-Debug-Client   orphan, ppisar 1 weeks ago
perl-Hardware-Vhdl-Tidy orphan 6 weeks ago
perl-Padre  orphan, ppisar 1 weeks ago
php-PHPMailer   orphan, remi   0 weeks ago
php-captchaphp  orphan 0 weeks ago
php-hkitorphan 0 weeks ago
php-pear-Auth-Yubicoorphan 0 weeks ago
php-rmccue-requests orphan 1 weeks ago
python-fn   codeblock, orphan  3 weeks ago
python-glusterfs-apihumble, orphan 0 weeks ago
python-pytest-relaxed   orphan 1 weeks ago
python-tempita  kylev, orphan  0 weeks ago
qtpass  marcindulak, orphan, vascom4 weeks ago
robodoc orphan 0 weeks ago
rubygem-ditzorphan 3 weeks ago

[rpms/perl-Dist-Zilla-Plugin-PodWeaver] PR #1: Tests

2021-06-21 Thread Petr Pisar


ppisar merged a pull-request against the project: 
`perl-Dist-Zilla-Plugin-PodWeaver` that you are following.

Merged pull-request:

``
Tests
``

https://src.fedoraproject.org/rpms/perl-Dist-Zilla-Plugin-PodWeaver/pull-request/1
___
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: Updating sources file using fedpkg

2021-06-21 Thread Vít Ondruch



Dne 17. 06. 21 v 20:02 Otto Urpelainen napsal(a):

Ken Dreyer kirjoitti 17.6.2021 klo 19.04:
On Thu, Jun 17, 2021 at 8:33 AM Richard Shaw  
wrote:


On Thu, Jun 17, 2021 at 7:22 AM Ewoud Kohl van Wijngaarden 
 wrote:



To be clear: I don't want to fiddle with the sources file, hence this
email. However, I would like to at least complete a local mockbuild
before uploading to the lookaside cache. It is my understanding that
new-sources always does this.



That's actually a nit I've been tempted to complain about. If I'm 
upgrading a package to a new version I update the spec file:


rpmdev-bumpspec -n  -c "Update to ." *.spec

And download the new source:

spectool -g *.spec

But then I have to upload the new source with 'fedpkg new-sources' 
if I don't want it to download the old version.


Yeah, the way I deal with this is I zero out the sources file, like ">
sources". Or another alternative that I use sometimes is "sha512sum
--tag", like:

   sha512sum --tag kstart-4.2.tar.gz > sources


Hi Ewould and everybody,

I am a bit confused about this discussion. My fedpkg does not care 
about the 'sources' file or the lookaside cache at all on 'fedpkg 
mockbuild'. 



I am not using `fedpkg mockbuild`, but `fedpkg srpm` certainly cares 
about 'sources' file. Prior creating the SRPM, it download files listed 
in 'sources' file from lookaside cache. However, later it uses whatever 
is available in the directory.



Vít


It simply looks up the expected filename of downloaded Source, grabs 
it from the local working directory and uses that. So for me this works:


    rpmdev-bumpspec -D -n 1.2.3 *.spec
    # Update specfile as needed
    spectool -g *.spec
    fedpkg mockbuild

After that is done, the rpm is available at results_mypackage, I 
install it locally and see that everything works. At that point it is 
a good time do 'fedpkg new-sources'.


This also means that non-packagers actually *can* properly test their 
changes. The maintainer has to do new-sources, commit, push and build 
after merging the pull request, so annoyingly there are those steps to 
remember. But at least the pull request author does not have to submit 
their changes blindly.


A simple test to make sure that it really uses the local download:

    $ sed -i 's/^Source.*/Source:https:\/\/example.com\/foo/' *.spec
    $ fedpkg mockbuild
    SOME_OUTPUT
    error: Bad file: SOMEPATH/foo: No such file or directory
    $ touch foo
    $ fedpkg mockbuild
    LOTS_OF_OUTPUT
    SOME_ERROR_DUE_TO_EMPTY_SOURCE

When I started, I was having exactly the same trouble, so wrote 
something in the wiki:


https://fedoraproject.org/wiki/Package_maintenance_guide#Using_fedpkg_anonymously 



Otto
___
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

___
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

[rpms/perl-HTTP-Message] PR #5: 6.32 bump

2021-06-21 Thread Michal Josef Špaček


mspacek merged a pull-request against the project: `perl-HTTP-Message` that you 
are following.

Merged pull-request:

``
6.32 bump
``

https://src.fedoraproject.org/rpms/perl-HTTP-Message/pull-request/5
___
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: The future of legacy BIOS support in Fedora.

2021-06-21 Thread Richard W.M. Jones

On Wed, Jul 01, 2020 at 12:49:17AM +0200, Kevin Kofler wrote:
> Jóhann B. Guðmundsson wrote:
> > Given Hans proposal [1] introduced systemd/grub2/Gnome upstream changes
> > it beg the question if now would not be the time to stop supporting
> > booting in legacy bios mode and move to uefi only supported boot which
> > has been available on any common intel based x86 platform since atleast
> > 2005.
> 
> No, it would not.
> 
> It would mean desupporting a wide range of existing hardware and some VM 
> environments (even with QEMU/KVM, I found the SeaBIOS legacy BIOS to be much 
> less quirky than the OVMF UEFI implementation, and other VM environments 
> might not support UEFI at all, including older QEMU versions that may still 
> be in use as hosts for modern Fedora guests). And for what gain?

Also SeaBIOS boot is much faster than OVMF, and that matters in many
cases (libguestfs for one).

Rich.

> I do not think switching from GRUB-EFI to systemd-boot as you propose would 
> be of any benefit for UEFI users. (It would actually mean fewer features for 
> no tangible benefit.) Hence, we are dealing with GRUB in both enviroments. 
> So I do not see the maintenance burden of continued BIOS support, also 
> considering that, in my experience, the environment that keeps causing 
> problems is actually UEFI, not BIOS.
> 
> > This post is just to gather feed back why Fedora should still continue
> > to support legacy BIOS boot as opposed to stop supporting it and
> > potentially drop grub2 and use sd-boot instead.
> 
> Fedora should still continue to support legacy BIOS boot.
> 
> 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

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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

[rpms/perl-HTTP-Message] PR #5: 6.32 bump

2021-06-21 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-HTTP-Message` that 
you are following:
``
6.32 bump
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-HTTP-Message/pull-request/5
___
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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for all Fedoras.


-- 
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

[rpms/perl-Dist-Zilla-Plugin-PodWeaver] PR #1: Tests

2021-06-21 Thread Petr Pisar


ppisar opened a new pull-request against the project: 
`perl-Dist-Zilla-Plugin-PodWeaver` that you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Dist-Zilla-Plugin-PodWeaver/pull-request/1
___
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 1973889] perl-Throwable-0.200014 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973889

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Throwable-0.201-2.fc35
   ||perl-Throwable-0.201000-1.f
   ||c35
 Resolution|--- |RAWHIDE
   Doc Type|--- |If docs needed, set a value
Last Closed||2021-06-21 07:49:02




-- 
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 1973968] perl-Dist-Zilla-Plugin-PodWeaver-4.009 is available

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973968

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
   Doc Type|--- |If docs needed, set a value




-- 
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 1974137] F35FailsToInstall: perl-Pinto

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1974137

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #1 from Jitka Plesnikova  ---
The module Throwable changed the numbering from 0.200013 to 0.201. 

# rpm -qp -P perl-Throwable-0.201000-1.fc35.noarch.rpm
perl(StackTrace::Auto) = 0.201
perl(Throwable) = 0.201
perl(Throwable::Error) = 0.201
perl-Throwable = 0.201000-1.fc35

The rpm does not determine correctly newer version.
# rpmdev-vercmp 0.201 0.200013
0.201 < 0.200013

I will add epoch to perl-Throwable to prevent the issue.


-- 
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-Cloud-33-20210621.0 compose check report

2021-06-21 Thread Fedora compose checker

No missing expected images.

Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210620.0):

ID: 913108  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/913108
ID: 913114  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/913114

Passed openQA tests: 7/8 (x86_64), 7/8 (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: RFC: Banning bots from submitting automated koji builds

2021-06-21 Thread Mattia Verga via devel

Bodhi has a config setting ('automatic_updates_blacklist') which can
avoid specific users/bots to automatically create updates.

If those bots are supposed to only test Koji builds, but not pushing
updates we can list them out using that setting.

Mattia

___
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 1973623] F35FailsToInstall: perl-RDF-Trine-redland

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1973623



--- Comment #6 from Petr Pisar  ---
Obsoleted in fedora-obsolete-packages-35-10.


-- 
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 1967544] perl-SDL-2.548-11.fc35 skips all video tests with sdl12-compat-devel-0.0.1~git.20210602.cc5826a-1.fc35: Failed to init video

2021-06-21 Thread bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1967544



--- Comment #10 from Petr Pisar  ---
Thanks.


-- 
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] 389 DS nightly 2021-06-21 - 95% PASS

2021-06-21 Thread vashirov

https://fedorapeople.org/groups/389ds/ci/nightly/2021/06/21/report-389-ds-base-2.0.5-20210621git59d889ad1.fc34.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

89 matches

Mail list logo