[389-devel] 389 DS nightly 2021-05-14 - 95% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2021/05/14/report-389-ds-base-2.0.4-20210514git2a12316b7.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
Re: Fedora for WSL
Hi Neal, Neal Gompa writes: > On Thu, May 13, 2021 at 12:44 PM Matthew Miller > wrote: >> >> On Sun, May 09, 2021 at 12:32:00AM -0500, Greg Hellings wrote: >> > I may be hair-brained to do this, but I've put together an installer for >> > Fedora on WSL. >> >> Hi Greg! Not hair-brained at all -- this is awesome! >> > > A couple of years back, I was working on porting WSL-DistroLauncher to > be cross compiled with Fedora's MinGW stack. I stopped because of > *reasons*, but it'd be nice to have the WSL stuff in Fedora and I > could probably pick that back up and make it a package in Fedora for > people to trivially generate their own WSL bundles. Have you looked at openSUSE's patches: https://github.com/openSUSE/WSL-DistroLauncher ? It works with their MinGW stack, at the expense of adding autotools into the mix… Cheers, Dan 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: Bodhi critpath package updates now gated on openQA results
Hello, On Fri, May 14, 2021 at 2:19 AM Adam Williamson wrote: > On Thu, 2021-05-13 at 19:29 +, Mattia Verga via devel wrote: > > > Hey folks! > > > > > > Just wanted to flag up that, now the new Bodhi version has been > > > deployed to production, critpath updates are gated on openQA test > > > results. If any openQA test for your critpath update failed, the > > > gating > > > status will be marked as 'failed' and you will not be able to push > > > it > > > stable. > > > > > > Waivers can be issued for failed tests where appropriate: > > > > > > https://docs.fedoraproject.org/en-US/ci/gating/#_waive > > > > > > But in almost all cases a failure indicates either a genuine bug or > > > an > > > opportunity to improve the test, so I'd prefer to avoid use of > > > waivers > > > where possible. I am trying to keep an eye on all failed tests, but > > > if > > > you have a blocked update and you don't understand the failure and > > > I > > > haven't yet commented on it, please do poke me and I'll take a > > > look. > > > > > > If a failure looks like some kind of transient issue, several folks > > > have the power to rerun tests: myself, lruzicka, kparal, tflink, > > > abokovoy (abbra / ab), pwhalen, and sumantrom. You can ask one of > > > us to > > > do it. There have been plans in the past to implement some sort of > > > rerun request system in Bodhi but no-one's quite had the roundtuits > > > to > > > work it out yet; sorry about that. > > > > A "re-run tests" button should be displayed in this case if the > > logged in user has the power to edit the update (commit access or > > provenpackager). Do you mean that it doesn't work? > > I believe that's strictly wired up to Fedora CI. It doesn't do anything > for openQA. > I thought, under the hood, the button is just telling Bodhi to send the "bodhi.update.status.testing.koji-build-group.build.complete" [1] message again, so all CI systems listening should trigger? This isn't the case for openQA? Thanks, Michal [1]: https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.bodhi.update.status.testing.koji-build-group.build.complete=18000 > -- > 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 > ___ 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: Bodhi critpath package updates now gated on openQA results
On Thu, 2021-05-13 at 19:29 +, Mattia Verga via devel wrote: > > Hey folks! > > > > Just wanted to flag up that, now the new Bodhi version has been > > deployed to production, critpath updates are gated on openQA test > > results. If any openQA test for your critpath update failed, the > > gating > > status will be marked as 'failed' and you will not be able to push > > it > > stable. > > > > Waivers can be issued for failed tests where appropriate: > > > > https://docs.fedoraproject.org/en-US/ci/gating/#_waive > > > > But in almost all cases a failure indicates either a genuine bug or > > an > > opportunity to improve the test, so I'd prefer to avoid use of > > waivers > > where possible. I am trying to keep an eye on all failed tests, but > > if > > you have a blocked update and you don't understand the failure and > > I > > haven't yet commented on it, please do poke me and I'll take a > > look. > > > > If a failure looks like some kind of transient issue, several folks > > have the power to rerun tests: myself, lruzicka, kparal, tflink, > > abokovoy (abbra / ab), pwhalen, and sumantrom. You can ask one of > > us to > > do it. There have been plans in the past to implement some sort of > > rerun request system in Bodhi but no-one's quite had the roundtuits > > to > > work it out yet; sorry about that. > > A "re-run tests" button should be displayed in this case if the > logged in user has the power to edit the update (commit access or > provenpackager). Do you mean that it doesn't work? I believe that's strictly wired up to Fedora CI. It doesn't do anything for openQA. -- 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
Re: F34 pkg.spec rpmbuild OK on local dev; same spec fails @ my COPR. why?
hi,
On 5/13/21 6:06 PM, Sérgio Basto wrote:
mock -r fedora-34-x86_64 --rebuild
lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
also fails in my machine, %forgesetup -z 0 is where it fails
hm. whereas a non-isolated, local rpmbuild works, as per my OP,
a *mock* build here fails similarly to @ COPR:
wget
https://download.copr.fedorainfracloud.org/results/pgfed/nginx-mainline/fedora-34-x86_64/02184528-lua-resty-luajit2/lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
mock \
-r fedora-34-x86_64 \
--rebuild \
--addrepo=https://download.copr.fedorainfracloud.org/results/pgfed/pgnd-rpmbuild-macros/fedora-34-x86_64
\
./lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
...
Packaging variables read or set by %forgemeta
forgeurl0: https://github.com/openresty/luajit2
forgesource0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
forgesetupargs0: -n luajit2-2.1-agentzh
archivename0: luajit2-2.1-agentzh
archiveext0: tar.gz
archiveurl0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
topdir0: luajit2-2.1-agentzh
extractdir0: luajit2-2.1-agentzh
repo0: luajit2
scm0: git
branch0: v2.1-agentzh
distprefix0: .20210513gitv2.1-agentzh
dist: .20210513gitv2.1-agentzh.fc34
(snapshot date is either manually supplied or computed once
%{_sourcedir}/%{archivename0}.%{archiveext0} is available)
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.9O1tue
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf luajit2-2.1-agentzh
+ /usr/bin/gzip -dc /builddir/build/SOURCES/luajit2-2.1-agentzh.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd luajit2-2.1-agentzh
/var/tmp/rpm-tmp.9O1tue: line 38: cd: luajit2-2.1-agentzh: No such file
or directory
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.9O1tue (%prep)
Setting %{branch} = v2.1-agentzh
Setting %{forgeurl0} = https://github.com/openresty/luajit2
Setting %{fileref0} = 2.1-agentzh
Setting %{ref0} = v2.1-agentzh
Setting %{archivename0} = %{repo0}-2.1-agentzh
Setting %{archiveext0} = tar.gz
Setting %{archiveurl0} =
https://github.com/openresty/luajit2/archive/v2.1-agentzh/%{repo0}-2.1-agentzh.tar.gz
Setting %{scm0} = git
Setting %{topdir0} = %{repo0}-2.1-agentzh
Setting %{repo0} = luajit2
Setting %{forgesource0} =
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
Setting %{forgesetupargs0} = -n %{extractdir0}
Setting %{extractdir0} = luajit2-2.1-agentzh
Setting %{distprefix0} = .20210513gitv2.1-agentzh
Setting %{forgesource} =
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
Setting %{forgesetupargs} = -n luajit2-2.1-agentzh
Setting %{archivename} = luajit2-2.1-agentzh
Setting %{archiveext} = tar.gz
Setting %{archiveurl} =
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
Setting %{topdir} = luajit2-2.1-agentzh
Setting %{extractdir} = luajit2-2.1-agentzh
Setting %{repo} = luajit2
Setting %{scm} = git
Setting %{distprefix} = .20210513gitv2.1-agentzh
Bad exit status from /var/tmp/rpm-tmp.9O1tue (%prep)
Finish: rpmbuild
lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
Finish: build phase for
lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
ERROR:
Exception(./lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm)
Config(fedora-34-x86_64) 0 minutes 19 seconds
INFO: Results and/or logs in: /home/mock/resultdir
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
Finish: clean chroot
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M a5a65f56173f44919d9e4890b40b3e55 -D
/var/lib/mock/fedora-34-x86_64/root -a -u mockbuild --capability=cap_ipc_lock
--bind=/dev/btrfs-control --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1
--bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6
--bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11
--console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir
--setenv=HOSTNAME=mock
Re: F34 pkg.spec rpmbuild OK on local dev; same spec fails @ my COPR. why?
mock -r fedora-34-x86_64 --rebuild
lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212639.fc34.src.rpm
also fails in my machine, %forgesetup -z 0 is where it fails, have you a
different or custom /usr/lib/rpm/macros.d/macros.forge ?
On Thu, 2021-05-13 at 17:43 -0400, PGNet Dev wrote:
I've a package .spec, that uses forgemeta macros, that builds locally
just fine on F34.
Same spec @ COPR, F34 chroot, fails.
Something's either missing on my end, or broken @COPR. Likely obvious
pebkac, but I'm not seeing it.
Any insights as to why the same spec, @COPR, is failing would be
appreciated.
With this spec,
cat ~/rpmbuild/SPECS/lua-resty-luajit2.spec
---
%{?_pgnd_macros}
%define _owner pgnd
%define _build_timestamp %( date +%%Y%%m%%d_%%H%%M%%S -
-utc )
%define _lua_resty_luajit2_name lua-resty-
luajit2
%define _lua_resty_luajit2_comment OpenResty's
maintained branch of LuaJIT
%define _lua_resty_luajit2_checkout_dirname luajit2
%define _lua_resty_luajit2_branch v2.1-
agentzh
%define _lua_resty_luajit2_shortbranch HEAD
%define compat_lua_ver 5.1
%define compat_lua_ext 5.2
%global forgeurl0
https://github.com/openresty/luajit2
%global branch0 %{_lua_resty_luajit2_branch}
%forgemeta -i -v -a
%global dist .%{_owner}_%{_build_timestamp}.fc%{fedora}
Name: %{_lua_resty_luajit2_name}
Version:
%{scm0}.%{_lua_resty_luajit2_shortbranch}
Release: 0%{?dist}
Summary: %{_lua_resty_luajit2_comment}
License: MIT
URL: %{forgeurl0}
Source0: %{forgesource0}
BuildRequires: compat-lua
BuildRequires: compat-lua-devel
BuildRequires: coreutils
BuildRequires: gcc
BuildRequires: git
BuildRequires: gzip
BuildRequires: openssl-devel
Requires: compat-lua >= %{compat_lua_ver}
Requires: compat-lua < %{compat_lua_ext}
Requires: compat-lua-devel >=
%{compat_lua_ver}
Requires: compat-lua-devel <
%{compat_lua_ext}
Requires: openssl
Requires: gzip
Requires: unzip
Requires: zip
Provides: %{_lua_resty_luajit2_name}
Conflicts: luajit
Conflicts: luajit-devel
%description
%{_lua_resty_luajit2_comment}
%prep
%forgesetup -z 0
%build
perl -pi -e '\
s|^(export PREFIX=).*|${1}
/usr/local/%{_lua_resty_luajit2_name}|g; \
s|^(export MULTILIB=).*|${1} lib64|g' \
Makefile
make %{?_smp_mflags}
%install
make DESTDIR=%{buildroot} install
%post
%preun
%files
/usr/local/%{_lua_resty_luajit2_name}/
%changelog
---
a local build
cd ~/rpmbuild/SPECS/
rpmbuild -bb ./lua-resty-luajit2.spec
builds OK, no error
...
Packaging variables read or set by %forgemeta
forgeurl0: https://github.com/openresty/luajit2
forgesource0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
forgesetupargs0: -n luajit2-2.1-agentzh
archivename0: luajit2-2.1-agentzh
archiveext0: tar.gz
archiveurl0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
topdir0: luajit2-2.1-agentzh
extractdir0: luajit2-2.1-agentzh
repo0: luajit2
scm0: git
branch0: v2.1-agentzh
distprefix0: .gitv2.1-agentzh
dist: .gitv2.1-agentzh.fc34
(snapshot date is either manually supplied or computed once
%{_sourcedir}/%{archivename0}.%{archiveext0} is available)
warning: Downloading
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
to /root/rpmbuild/SOURCES/luajit2-2.1-agentzh.tar.gz
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.2DphWx
...
Wrote: /root/rpmbuild/RPMS/x86_64/lua-resty-luajit2-git.HEAD-
0.pgnd_20210513_212124.fc34.x86_64.rpm
the resultant rpm's install-/use-able
pushing the same
F34 pkg.spec rpmbuild OK on local dev; same spec fails @ my COPR. why?
I've a package .spec, that uses forgemeta macros, that builds locally just fine
on F34.
Same spec @ COPR, F34 chroot, fails.
Something's either missing on my end, or broken @COPR. Likely obvious pebkac,
but I'm not seeing it.
Any insights as to why the same spec, @COPR, is failing would be appreciated.
With this spec,
cat ~/rpmbuild/SPECS/lua-resty-luajit2.spec
---
%{?_pgnd_macros}
%define _owner pgnd
%define _build_timestamp %( date +%%Y%%m%%d_%%H%%M%%S --utc )
%define _lua_resty_luajit2_name lua-resty-luajit2
%define _lua_resty_luajit2_comment OpenResty's
maintained branch of LuaJIT
%define _lua_resty_luajit2_checkout_dirname luajit2
%define _lua_resty_luajit2_branch v2.1-agentzh
%define _lua_resty_luajit2_shortbranch HEAD
%define compat_lua_ver 5.1
%define compat_lua_ext 5.2
%global forgeurl0 https://github.com/openresty/luajit2
%global branch0 %{_lua_resty_luajit2_branch}
%forgemeta -i -v -a
%global dist .%{_owner}_%{_build_timestamp}.fc%{fedora}
Name: %{_lua_resty_luajit2_name}
Version: %{scm0}.%{_lua_resty_luajit2_shortbranch}
Release: 0%{?dist}
Summary: %{_lua_resty_luajit2_comment}
License: MIT
URL: %{forgeurl0}
Source0: %{forgesource0}
BuildRequires: compat-lua
BuildRequires: compat-lua-devel
BuildRequires: coreutils
BuildRequires: gcc
BuildRequires: git
BuildRequires: gzip
BuildRequires: openssl-devel
Requires: compat-lua >= %{compat_lua_ver}
Requires: compat-lua < %{compat_lua_ext}
Requires: compat-lua-devel >= %{compat_lua_ver}
Requires: compat-lua-devel < %{compat_lua_ext}
Requires: openssl
Requires: gzip
Requires: unzip
Requires: zip
Provides: %{_lua_resty_luajit2_name}
Conflicts: luajit
Conflicts: luajit-devel
%description
%{_lua_resty_luajit2_comment}
%prep
%forgesetup -z 0
%build
perl -pi -e '\
s|^(export PREFIX=).*|${1}
/usr/local/%{_lua_resty_luajit2_name}|g; \
s|^(export MULTILIB=).*|${1} lib64|g' \
Makefile
make %{?_smp_mflags}
%install
make DESTDIR=%{buildroot} install
%post
%preun
%files
/usr/local/%{_lua_resty_luajit2_name}/
%changelog
---
a local build
cd ~/rpmbuild/SPECS/
rpmbuild -bb ./lua-resty-luajit2.spec
builds OK, no error
...
Packaging variables read or set by %forgemeta
forgeurl0: https://github.com/openresty/luajit2
forgesource0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
forgesetupargs0: -n luajit2-2.1-agentzh
archivename0: luajit2-2.1-agentzh
archiveext0: tar.gz
archiveurl0:
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
topdir0: luajit2-2.1-agentzh
extractdir0: luajit2-2.1-agentzh
repo0: luajit2
scm0: git
branch0: v2.1-agentzh
distprefix0: .gitv2.1-agentzh
dist: .gitv2.1-agentzh.fc34
(snapshot date is either manually supplied or computed once
%{_sourcedir}/%{archivename0}.%{archiveext0} is available)
warning: Downloading
https://github.com/openresty/luajit2/archive/v2.1-agentzh/luajit2-2.1-agentzh.tar.gz
to /root/rpmbuild/SOURCES/luajit2-2.1-agentzh.tar.gz
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.2DphWx
...
Wrote:
/root/rpmbuild/RPMS/x86_64/lua-resty-luajit2-git.HEAD-0.pgnd_20210513_212124.fc34.x86_64.rpm
the resultant rpm's install-/use-able
pushing the same spec to COPR, fails @ %prep
@,
https://download.copr.fedorainfracloud.org/results/pgfed/nginx-mainline/fedora-34-x86_64/02184528-lua-resty-luajit2/builder-live.log.gz
Packaging variables read or set by %forgemeta
forgeurl0: https://github.com/openresty/luajit2
Re: Update "ejected from the push"
Hi Kevin, On Thu, May 13, 2021 at 10:55 PM Kevin Fenzi wrote: > > Did you by chance add them to the update during the upgrade this > morning? (starting at 10UTC)? It doesn't look like bodhi did the right > thing with the tagging here... I can try and correct things. It was towards the end of the outage window, around 12 UTC. I usually take note of outages that might affect me, but in all honesty this was unplanned and I had completely forgotten about the bodhi upgrade. > In the furture, please do file a releng issue for things like this > (https://pagure.io/releng) I will do my best to remember that, thanks a lot! ___ 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 1950383] please build perl-Archive-Extract for EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1950383 --- Comment #1 from Michal Josef Spacek --- Request for branch: https://pagure.io/releng/fedora-scm-requests/issue/33949 -- 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: Update "ejected from the push"
On Thu, May 13, 2021 at 10:09:32PM +0200, Alexander Ploumistos wrote: > Hello, > > Can anyone help me figure out what's going on with this update? > https://bodhi.fedoraproject.org/updates/FEDORA-2021-b8551abae2 > > It says that the side-tag is not among a bunch of other tags. It does > exist though. > > What I did was build a package and its dependencies in side-tags for > F33, F34 and F35 (in hindsight that last one was unnecessary). I > submitted the updates in bodhi and after being made aware of the > issue, the F33 update was stopped from moving to stable and I unpushed > the one for F34. I built new versions of the package in the same > side-tags and edited both updates and pushed them to testing again. > > Will this be a problem for this one as well? > https://bodhi.fedoraproject.org/updates/FEDORA-2021-41405921ae > > What should I do? Did you by chance add them to the update during the upgrade this morning? (starting at 10UTC)? It doesn't look like bodhi did the right thing with the tagging here... I can try and correct things. In the furture, please do file a releng issue for things like this (https://pagure.io/releng) kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1960398] Upgrade perl-V to 0.15
https://bugzilla.redhat.com/show_bug.cgi?id=1960398 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2021-5dbf99ea4b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5dbf99ea4b -- 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
Update "ejected from the push"
Hello, Can anyone help me figure out what's going on with this update? https://bodhi.fedoraproject.org/updates/FEDORA-2021-b8551abae2 It says that the side-tag is not among a bunch of other tags. It does exist though. What I did was build a package and its dependencies in side-tags for F33, F34 and F35 (in hindsight that last one was unnecessary). I submitted the updates in bodhi and after being made aware of the issue, the F33 update was stopped from moving to stable and I unpushed the one for F34. I built new versions of the package in the same side-tags and edited both updates and pushed them to testing again. Will this be a problem for this one as well? https://bodhi.fedoraproject.org/updates/FEDORA-2021-41405921ae What should I do? ___ 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: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Thu, May 13, 2021 at 05:48:07PM +0300, Juha Tuomala wrote: > Virtual machine installation is hopefully a special use case and majority of > installations are bare metal end users. Most likely the exact opposite of this, but I don't have the numbers. (On _my_ systems it's likely to be 100:1 virtual:physical) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bodhi critpath package updates now gated on openQA results
> Hey folks! > > Just wanted to flag up that, now the new Bodhi version has been > deployed to production, critpath updates are gated on openQA test > results. If any openQA test for your critpath update failed, the gating > status will be marked as 'failed' and you will not be able to push it > stable. > > Waivers can be issued for failed tests where appropriate: > > https://docs.fedoraproject.org/en-US/ci/gating/#_waive > > But in almost all cases a failure indicates either a genuine bug or an > opportunity to improve the test, so I'd prefer to avoid use of waivers > where possible. I am trying to keep an eye on all failed tests, but if > you have a blocked update and you don't understand the failure and I > haven't yet commented on it, please do poke me and I'll take a look. > > If a failure looks like some kind of transient issue, several folks > have the power to rerun tests: myself, lruzicka, kparal, tflink, > abokovoy (abbra / ab), pwhalen, and sumantrom. You can ask one of us to > do it. There have been plans in the past to implement some sort of > rerun request system in Bodhi but no-one's quite had the roundtuits to > work it out yet; sorry about that. A "re-run tests" button should be displayed in this case if the logged in user has the power to edit the update (commit access or provenpackager). Do you mean that it doesn't work? > > Thanks everyone, please be patient with any kinks while we see how this > goes :) ___ 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 1960398] New: Upgrade perl-V to 0.15
https://bugzilla.redhat.com/show_bug.cgi?id=1960398 Bug ID: 1960398 Summary: Upgrade perl-V to 0.15 Product: Fedora Version: rawhide Status: NEW Component: perl-V Assignee: jvrom...@squirrel.nl Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: jvrom...@squirrel.nl, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest Fedora delivers 0.13 version. Upstream released 0.15. When you have free time, please upgrade 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
[Bug 1960396] New: Upgrade perl-Test-Script to 1.29
https://bugzilla.redhat.com/show_bug.cgi?id=1960396 Bug ID: 1960396 Summary: Upgrade perl-Test-Script to 1.29 Product: Fedora Version: rawhide Status: NEW Component: perl-Test-Script Assignee: rc040...@freenet.de Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org, rc040...@freenet.de Target Milestone: --- Classification: Fedora Latest Fedora delivers 1.27 version. Upstream released 1.29. When you have free time, please upgrade 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
[Bug 1960392] New: Upgrade perl-File-Which to 1.27
https://bugzilla.redhat.com/show_bug.cgi?id=1960392 Bug ID: 1960392 Summary: Upgrade perl-File-Which to 1.27 Product: Fedora Version: rawhide Status: NEW Component: perl-File-Which Assignee: spo...@gmail.com Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: jose.p.oliveira@gmail.com, perl-devel@lists.fedoraproject.org, spo...@gmail.com Target Milestone: --- Classification: Fedora Latest Fedora delivers 1.24 version. Upstream released 1.27. When you have free time, please upgrade 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
[Bug 1959553] perl-HTTP-Message-6.31 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1959553 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED CC||jples...@redhat.com Fixed In Version||perl-HTTP-Message-6.31-1.fc ||35 Resolution|--- |RAWHIDE Last Closed||2021-05-13 18:39:00 --- Comment #1 from Jitka Plesnikova --- Built by mspacek -- 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 1958694] perl-Term-ReadLine-Gnu-1.42 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1958694 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED CC||jples...@redhat.com Fixed In Version||perl-Term-ReadLine-Gnu-1.42 ||-1.fc35 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2021-05-13 18:34:45 --- Comment #1 from Jitka Plesnikova --- Built by eseyman -- 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 1955451] Upgrade perl-Crypt-X509 to 0.54
https://bugzilla.redhat.com/show_bug.cgi?id=1955451 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Crypt-X509-0.54-1.fc35 ||perl-Crypt-X509-0.54-1.fc34 Resolution|--- |RAWHIDE Last Closed||2021-05-13 18:31:43 --- Comment #1 from Jitka Plesnikova --- Built by corsepiu -- 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 1950798] perl-Dancer2-0.301002 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1950798 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED CC||jples...@redhat.com Fixed In Version||perl-Dancer2-0.301002-1.fc3 ||5 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2021-05-13 18:30:07 --- Comment #1 from Jitka Plesnikova --- Built by eseyman -- 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 1947316] Upgrade perl-Config-Model to 2.142
https://bugzilla.redhat.com/show_bug.cgi?id=1947316 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Config-Model-2.142-1.f ||c35 Resolution|--- |RAWHIDE Last Closed||2021-05-13 18:27:42 --- Comment #1 from Jitka Plesnikova --- Built by eseyman -- 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 1921135] Upgrade perl-Test-Inline to 2.214
https://bugzilla.redhat.com/show_bug.cgi?id=1921135 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Test-Inline-2.214-2.fc ||35 Resolution|--- |RAWHIDE Last Closed||2021-05-13 18:24:04 --- Comment #2 from Jitka Plesnikova --- Built by corsepiu -- 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 1892743] Upgrade perl-Type-Tiny to 1.012003
https://bugzilla.redhat.com/show_bug.cgi?id=1892743 Jitka Plesnikova changed: What|Removed |Added Summary|Upgrade perl-Type-Tiny to |Upgrade perl-Type-Tiny to |1.012001|1.012003 --- Comment #3 from Jitka Plesnikova --- Latest Fedora delivers 1.012001 version. Upstream released 1.012003. When you have free time, please upgrade 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
[Bug 1929021] perl-ExtUtils-F77-1.26 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1929021 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-ExtUtils-F77-1.26-1.fc ||35 ||perl-ExtUtils-F77-1.26-1.fc ||34 Resolution|--- |RAWHIDE Doc Type|--- |If docs needed, set a value Last Closed||2021-05-13 18:18:35 --- Comment #2 from Jitka Plesnikova --- Built by orion -- 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 1927663] Upgrade perl-POE-Component-Client-Ping to 1.177
https://bugzilla.redhat.com/show_bug.cgi?id=1927663 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-POE-Component-Client-P ||ing-1.177-1.fc35 Resolution|--- |RAWHIDE Assignee|maria...@tuxette.fr |jples...@redhat.com Last Closed||2021-05-13 18:09:46 -- 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: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
> Am 12.05.2021 um 22:35 schrieb Ben Cotton : > > == Summary == > Since 2019 the Anaconda installer GUI hosted an option called "Allow > SSH root login with password", that made it possible to enable > password based root logins over SSH on the installed system. ... And > after two years of transition period it is now time to drop the option > from the GUI. > We discussed that in the Fedora Server Edition Working Group and opted to leave it as is for the Server installation iso. A lot of servers are running in a protected environment. And there are situations when you need urgent access but do not sit at your desktop and don’t have the key available. So let the server admin decide what is best in a given installation context. In most cases it is the current default (disallow password login) ___ 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
Bodhi critpath package updates now gated on openQA results
Hey folks! Just wanted to flag up that, now the new Bodhi version has been deployed to production, critpath updates are gated on openQA test results. If any openQA test for your critpath update failed, the gating status will be marked as 'failed' and you will not be able to push it stable. Waivers can be issued for failed tests where appropriate: https://docs.fedoraproject.org/en-US/ci/gating/#_waive But in almost all cases a failure indicates either a genuine bug or an opportunity to improve the test, so I'd prefer to avoid use of waivers where possible. I am trying to keep an eye on all failed tests, but if you have a blocked update and you don't understand the failure and I haven't yet commented on it, please do poke me and I'll take a look. If a failure looks like some kind of transient issue, several folks have the power to rerun tests: myself, lruzicka, kparal, tflink, abokovoy (abbra / ab), pwhalen, and sumantrom. You can ask one of us to do it. There have been plans in the past to implement some sort of rerun request system in Bodhi but no-one's quite had the roundtuits to work it out yet; sorry about that. Thanks everyone, please be patient with any kinks while we see how this goes :) -- 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
Re: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Thu, May 13, 2021 at 9:46 AM Simo Sorce wrote: > > On Wed, 2021-05-12 at 16:35 -0400, Ben Cotton wrote: > > == Benefit to Fedora == > > This change makes the Fedora systems installed by Anaconda more secure > > from remote password guessing attacks targeting the root account as it > > would no longer be possible to configure a system that allows root to > > login via SSH with password. > > > > A smaller benefit is making the root password configuration screen > > less confusing by removing the "Allow SSH root login with password" & > > Anaconda code cleanup related removing code related to setting up the > > override in sshd. > > To be honest I object to this characterization. > > There is no added security given the default is not changed. This only > removes a valid option that users that install images for testing > locally on their computer use. It just makes it harder but does not > change the security of Fedora one yota, as uses can still log in after > install and re-enable root login with passwords, or use a kickstart > file to do the same. > > If this is being done because maintaining the option for Anaconda > developers then just say that. Otherwise do not do this change and let > people that need it for convenience have it. > > Simo. It also deletes from the GUI options that are available in anaconda itself. Thati violates one of the guidelines of Eric Raymond's guidelines for open source GUI's, from the "Luxury of Ignorance" essay. Well, OK, he added that guideline after the original essay as a PS at my suggestion. ___ 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 1960347] perl-Crypt-OpenSSL-X509-1.908 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1960347 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perl-Crypt-OpenSSL-X509-1.908-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=67840744 -- 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 1960347] New: perl-Crypt-OpenSSL-X509-1.908 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1960347 Bug ID: 1960347 Summary: perl-Crypt-OpenSSL-X509-1.908 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Crypt-OpenSSL-X509 Keywords: FutureFeature, Triaged Assignee: wjhns...@hardakers.net Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, wjhns...@hardakers.net, xav...@bachelot.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.908 Current version/release in rawhide: 1.907-1.fc35 URL: http://search.cpan.org/dist/Crypt-OpenSSL-X509/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/2749/ -- 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: Fedora for WSL
On Thu, May 13, 2021 at 12:44 PM Matthew Miller wrote: > > On Sun, May 09, 2021 at 12:32:00AM -0500, Greg Hellings wrote: > > I may be hair-brained to do this, but I've put together an installer for > > Fedora on WSL. > > Hi Greg! Not hair-brained at all -- this is awesome! > A couple of years back, I was working on porting WSL-DistroLauncher to be cross compiled with Fedora's MinGW stack. I stopped because of *reasons*, but it'd be nice to have the WSL stuff in Fedora and I could probably pick that back up and make it a package in Fedora for people to trivially generate their own WSL bundles. -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora for WSL
On Sun, May 09, 2021 at 12:32:00AM -0500, Greg Hellings wrote: > I may be hair-brained to do this, but I've put together an installer for > Fedora on WSL. Hi Greg! Not hair-brained at all -- this is awesome! -- Matthew Miller Fedora Project Leader ___ 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 1926912] Upgrade perl-Class-Observable to 2.000
https://bugzilla.redhat.com/show_bug.cgi?id=1926912 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Class-Observable-2.000 ||-1.fc35 Resolution|--- |RAWHIDE Assignee|andr...@bawue.net |jples...@redhat.com Last Closed||2021-05-13 16:04:44 -- 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: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On 5/13/21 10:48 AM, Juha Tuomala wrote: Virtual machine installation is hopefully a special use case and majority of installations are bare metal end users. hardly. here, for any given single bare-metal install, between cloud & local VMs, there are typically *many*/*frequent* VM installs -- of all shapes-n-sizes. it's FAR more frequent (among devs/ops, even some end-users) than bare-metal installs. a bog-simple, not-uncommon workflow is: launch VirtualBox, drop in an OS iso, run the UI install. for that, a simple password option is more than sufficient. again, why not simply 'leave it be'. ___ 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 1917555] Upgrade perl-Set-Object to 1.41
https://bugzilla.redhat.com/show_bug.cgi?id=1917555 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-Set-Object-1.41-1.fc35 Resolution|--- |RAWHIDE Assignee|kra...@redhat.com |jples...@redhat.com Last Closed||2021-05-13 15:40:08 -- 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: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Thursday, 13 May 2021 15:11:19 EEST Roberto Ragusa wrote: > > Make a plugin interface for adding additional methods to obtain public > > keys as there are a lot different sources for those. Fedora itself has > > tools for PKI and public key based security and it would be quite low > > hanging fruit to fill the gap between those components, in cases like > > this. > > In this case before doing advanced cloud based things, PKI nor LDAP have nothing to do with "clouds" Those were created at 1970s and are still in use. L stands for lightweight, could not be further from clouds. https://en.wikipedia.org/wiki/Public_key_infrastructure#History > Developments in PKI occurred in the early 1970s at the British > intelligence agency GCHQ https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol#History > These companies introduced the concept of directory services to information > technology and computer networking, their input culminating in the > comprehensive X.500 specification,[6] a suite of protocols produced by the > International Telecommunication Union (ITU) in the 1980s. > let's try to also have a simple "paste your key here" textarea, Having a plugin interface in place, the first plugin can be the "text area", the simplest of all. Having base64 coded carbage in the end user interface is another question, I'm pretty sure that whoever decided ssh pubkeyformat, did not intend it to be used like this. Hence there is a command % ssh-copy-id Usage: /usr/bin/ssh-copy-id [-h|-?|-f|-n] [-i [identity_file]] [-p port] [-F alternative ssh_config file] [[-o ] ...] [user@]hostname -f: force mode -- copy keys without trying to check if they are already installed -n: dry run-- no keys are actually copied -h|-?: print this help Those plugins would be written by someone else, outside the Anaconda codebase. That's why the only needed is to define the plugin interface. > which is the only sane method I would want to use when > creating a virtual machine. Virtual machine installation is hopefully a special use case and majority of installations are bare metal end users. Tuju -- ___ 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: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On 5/13/21 10:09 AM, Richard W.M. Jones wrote: Not everyone is installing a public facing server. On my isolated, non-networked test instances I want to put up a short-lived VM with a root password of "123456" quickly and no user account, and this option lets me do that. this^^ is a _very_ frequent use case here, as well. it's been mentioned, and seconded b4. i'll do it again: +10 'use kickstart' isn't a simplifying solution. 'leave it be', otoh, is. ___ 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: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Wed, May 12, 2021 at 04:35:44PM -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Drop_Rootpw_SSH_From_Installer I don't understand why you want to remove this, since it defaults to off. Sure, add a warning if you like (probably there's one already?) Not everyone is installing a public facing server. On my isolated, non-networked test instances I want to put up a short-lived VM with a root password of "123456" quickly and no user account, and this option lets me do that. > Now fast forward to today, it's 2021, any use cases that needed > password based root login via SSH had 2 more years to migrate while the > amount of password guessing attacks certainly didn't get any lower. The trouble is there isn't a practical, lightweight migration available for the test use case, and these aren't exposed anywhere that password-guessing attacks would succeed. The option is not enabled by default (and shouldn't be) so leave it be. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ ___ 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: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Wed, 2021-05-12 at 16:35 -0400, Ben Cotton wrote: > == Benefit to Fedora == > This change makes the Fedora systems installed by Anaconda more secure > from remote password guessing attacks targeting the root account as it > would no longer be possible to configure a system that allows root to > login via SSH with password. > > A smaller benefit is making the root password configuration screen > less confusing by removing the "Allow SSH root login with password" & > Anaconda code cleanup related removing code related to setting up the > override in sshd. To be honest I object to this characterization. There is no added security given the default is not changed. This only removes a valid option that users that install images for testing locally on their computer use. It just makes it harder but does not change the security of Fedora one yota, as uses can still log in after install and re-enable root login with passwords, or use a kickstart file to do the same. If this is being done because maintaining the option for Anaconda developers then just say that. Otherwise do not do this change and let people that need it for convenience have it. Simo. -- Simo Sorce RHEL Crypto Team Red Hat, Inc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://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-20210513.n.0 compose check report
Missing expected images: Xfce raw-xz armhfp Compose FAILS proposed Rawhide gating check! 1 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 10/194 (x86_64), 9/133 (aarch64) New failures (same test not failed in Fedora-Rawhide-20210512.n.2): ID: 885676 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4 URL: https://openqa.fedoraproject.org/tests/885676 ID: 885741 Test: x86_64 Workstation-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/885741 ID: 885852 Test: aarch64 Workstation-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/885852 ID: 885898 Test: x86_64 universal install_blivet_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/885898 ID: 885957 Test: aarch64 universal install_anaconda_text@uefi URL: https://openqa.fedoraproject.org/tests/885957 Old failures (same test failed in Fedora-Rawhide-20210512.n.2): ID: 885756 Test: x86_64 KDE-live-iso desktop_terminal **GATING** URL: https://openqa.fedoraproject.org/tests/885756 ID: 885767 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/885767 ID: 885818 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/885818 ID: 885907 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/885907 ID: 885924 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/885924 ID: 885943 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/885943 ID: 885947 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/885947 ID: 885950 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/885950 ID: 885959 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/885959 ID: 885977 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/885977 ID: 885978 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/885978 ID: 885991 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/885991 ID: 885994 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/885994 ID: 885995 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/885995 Soft failed openQA tests: 1/194 (x86_64), 3/133 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Rawhide-20210512.n.2): ID: 885786 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/885786 ID: 885787 Test: aarch64 Minimal-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/885787 ID: 885843 Test: aarch64 Server-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/885843 ID: 885874 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/885874 Passed openQA tests: 183/194 (x86_64), 107/133 (aarch64) Skipped non-gating openQA tests: 14 of 327 Installed system changes in test x86_64 Server-boot-iso install_default: 1 packages(s) removed since previous compose: libtextstyle Previous test data: https://openqa.fedoraproject.org/tests/885294#downloads Current test data: https://openqa.fedoraproject.org/tests/885669#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: 1 packages(s) removed since previous compose: libtextstyle Previous test data: https://openqa.fedoraproject.org/tests/885295#downloads Current test data: https://openqa.fedoraproject.org/tests/885670#downloads Installed system changes in test x86_64 Server-dvd-iso install_default@uefi: System load changed from 0.38 to 0.15 Previous test data: https://openqa.fedoraproject.org/tests/885317#downloads Current test data: https://openqa.fedoraproject.org/tests/885692#downloads Installed system changes in test x86_64 Everything-boot-iso install_default: 1 packages(s) removed since previous compose: libtextstyle System load changed from 0.04 to 0.18 Previous test data: https://openqa.fedoraproject.org/tests/885351#downloads Current test data: https://openqa.fedoraproject.org/tests/885726#downloads Installed system changes in test x86_64 Everything-boot-iso install_default@uefi: 1 packages(s) removed since previous compose: libtextstyle System load changed from 0.10 to 0.46 Previous test data: https://openqa.fedoraproject.org/tests/885352#downloads Current test data:
rpkg-3.rc2 built into rawhide
Hello, I have built rpkg-3.rc2 (package sources: https://src.fedoraproject.org/rpms/rpkg-util) into rawhide yesterday. It should be now available for installation. It is a complete rewrite of version 2. It aims to be a tool with minimal deps that allows people to easily transform git repositories containing spec files into rpm packages. Historically, the goal of this tool was to provide a single client to all dist-git instances (i.e Fedora, CentOS, maybe something else too). This was the idea when I started to work on it still in RedHat under the lead of Miroslav Suchý. We wanted to tweak the rpkg script provided by python-rpkg lib (https://pagure.io/rpkg) for that purpose. However, that script was soon being discontinued. There I created a separate project (rpkg-util) which would be providing the script so that I can continue in my goal. Eventually, I realized that some steps rather need to be taken server-side (https://github.com/release-engineering/dist-git) for a generic client to exist so that I did and then it was about adoption of the dist-git package (which provides the unified interface) by various dist-git instances. Meanwhile, I was thinking what to do next with rpkg while being heavily influenced by Copr that I primarily worked on at that time and also by discussion on devel list about automatically generating changelog and release from git. I realized there is an opportunity to provide a solution for this in the generic dist-git client (rpkg executable) and that it was not a bad place for it. This problem was then and even today solved by basically sedding spec file with regexps which I thought is kind of hacky and that it could be useful to have a library for common substitutions anyway so that people can reuse it. So a simple spec templating language was born (https://docs.pagure.org/rpkg-util/v3/spec_templates_from_scratch.html) and also a simple library of macros (https://docs.pagure.org/rpkg-util/v3/macro_reference.html) that use git content and metadata to render spec file content or parts of it. It now allows not only to generate changelog or release but also e.g. to generate a source tarball from a git submodule placed next to the spec file. There is also the possibility for users to define their own macros and therefore customize git->rpm transform in any way. You can try this now in rawhide (`dnf install rpkg`) or also in Copr (SCM rpkg build method) but note that in Copr, there is still v2 so there might be some differences. You might also need to install python3-setuptools - that package seems to be required by python3-munch but is not being brought in automatically at the moment. You can use rpkg tool similarly to fedpkg to work with Fedora dist-git packages (except that `rpkg build` command builds in Copr and the command set is mostly trimmed-down) or you can use it to work with those git layouts that contain unpackaged sources together with spec file (or rather spec file template) or link to the upstream sources through a git submodule. Best regards clime P.S.: the project is hosted here: https://pagure.io/rpkg-util ___ 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] Re: Postgrey packaging issue
On Thu, 13 May 2021, Nick Howitt wrote:
On 13/05/2021 10:21, Nick Howitt wrote:
On 13/05/2021 09:55, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 13 May 2021 at 10:21, Nick Howitt wrote:
Hi,
This app recently updated and I've noticed that it stomped on my
/etc/sysconfig/postrgey file isn't this wrong? Looking at the spec file,
in
the %files section it has:
%{_sysconfdir}/sysconfig/postgrey
Shouldn't this be:
%config(noreplace) %{_sysconfdir}/sysconfig/postgrey
It most probably should. This looks like a packaging bug and I'd suggest
opening a bug report, with a patch or even a pull request against the
spec file.
Regards,
Dominik
I've found the bug tracker and filed
https://bugzilla.redhat.com/show_bug.cgi?id=1960184. I'm lousy at creating
patch files so I've ducked it.
Ugh not an easy bug. The unit file has changed (or the requirements for
startup options have) so the sysconfig file needs more options in it. It is a
pity there was not a "%config noreplace" but with a smart %post to add the
extra parameters needed.
I think I'll mark the bug as invalid.
In that case, shouldn't we change the line to
%config %{_sysconfdir}/sysconfig/postgrey
so that the old file is saved at
%{_sysconfdir}/sysconfig/postgrey.rpmsave
?
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
___
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
Re: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On 5/13/21 12:13 PM, Juha Tuomala wrote: Make a plugin interface for adding additional methods to obtain public keys as there are a lot different sources for those. Fedora itself has tools for PKI and public key based security and it would be quite low hanging fruit to fill the gap between those components, in cases like this. In this case before doing advanced cloud based things, let's try to also have a simple "paste your key here" textarea, which is the only sane method I would want to use when creating a virtual machine. Regards. -- Roberto Ragusamail at robertoragusa.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
Fedora rawhide compose report: 20210513.n.0 changes
OLD: Fedora-Rawhide-20210512.n.2 NEW: Fedora-Rawhide-20210513.n.0 = SUMMARY = Added images:1 Dropped images: 2 Added packages: 0 Dropped packages:1 Upgraded packages: 12 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:230.11 KiB Size of upgraded packages: 2.52 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 11.27 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Mate live x86_64 Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20210513.n.0.iso = DROPPED IMAGES = Image: Xfce raw-xz armhfp Path: Spins/armhfp/images/Fedora-Xfce-Rawhide-20210512.n.2.armhfp.raw.xz Image: Workstation raw-xz armhfp Path: Workstation/armhfp/images/Fedora-Workstation-Rawhide-20210512.n.2.armhfp.raw.xz = ADDED PACKAGES = = DROPPED PACKAGES = Package: python2-dns-1.16.0-15.fc34 Summary: DNS toolkit for Python RPMs:python2-dns Size:230.11 KiB = UPGRADED PACKAGES = Package: asterisk-18.4.0-1.fc35 Old package: asterisk-18.3.0-1.fc35.2 Summary: The Open Source PBX RPMs: asterisk asterisk-ael asterisk-alembic asterisk-alsa asterisk-calendar asterisk-corosync asterisk-curl asterisk-dahdi asterisk-devel asterisk-fax asterisk-festival asterisk-hep asterisk-iax2 asterisk-ldap asterisk-lua asterisk-mgcp asterisk-minivm asterisk-mobile asterisk-mwi-external asterisk-mysql asterisk-odbc asterisk-oss asterisk-pjsip asterisk-portaudio asterisk-postgresql asterisk-radius asterisk-sip asterisk-skinny asterisk-snmp asterisk-sqlite asterisk-tds asterisk-unistim asterisk-voicemail asterisk-voicemail-odbc asterisk-voicemail-plain Size: 43.19 MiB Size change: 86.21 KiB Changelog: * Mon May 10 2021 Jared K. Smith - 18.4.0-1 - Update to upstream 18.4.0 release for bug fixes Package: buildah-1.20.2-0.11.dev.git5119393.fc35 Old package: buildah-1.20.2-0.10.dev.gita0853c3.fc35 Summary: A command line tool used for creating OCI Images RPMs: buildah buildah-tests Size: 75.75 MiB Size change: 134.86 KiB Changelog: * Thu May 13 2021 RH Container Bot - 1.20.2-0.11.dev.git5119393 - autobuilt 5119393 Package: crun-0.19.1.31-0.6.gitb83eda7.fc35 Old package: crun-0.19.1.26-0.5.git029e0ed.fc35 Summary: OCI runtime written in C RPMs: crun Size: 856.54 KiB Size change: 1.05 KiB Changelog: * Thu May 13 2021 RH Container Bot - 0.19.1.31-0.6.gitb83eda7 - bump to 0.19.1.31 - autobuilt b83eda7 Package: dotnet3.1-3.1.115-1.fc35 Old package: dotnet3.1-3.1.114-1.fc35 Summary: .NET Core Runtime and SDK RPMs: aspnetcore-runtime-3.1 aspnetcore-targeting-pack-3.1 dotnet-apphost-pack-3.1 dotnet-hostfxr-3.1 dotnet-runtime-3.1 dotnet-sdk-3.1 dotnet-sdk-3.1-source-built-artifacts dotnet-targeting-pack-3.1 dotnet-templates-3.1 Size: 1.26 GiB Size change: 10.84 MiB Changelog: * Wed May 12 2021 Omair Majid - 3.1.115-1 - Update to .NET SDK 3.1.115 and Runtime 3.1.15 Package: dummy-test-package-gloster-0-3701.fc35 Old package: dummy-test-package-gloster-0-3698.fc35 Summary: Dummy Test Package called Gloster RPMs: dummy-test-package-gloster Size: 229.39 KiB Size change: 183 B Changelog: * Wed May 12 2021 packagerbot - 0-3699 - rebuilt * Wed May 12 2021 packagerbot - 0-3700 - rebuilt * Thu May 13 2021 packagerbot - 0-3701 - rebuilt Package: google-noto-fonts-20201206-2.fc35 Old package: google-noto-fonts-20201206-1.fc35 Summary: Hinted and Non Hinted OpenType fonts for Unicode scripts RPMs: google-noto-fonts-common google-noto-kufi-arabic-fonts google-noto-kufi-arabic-vf-fonts google-noto-music-fonts google-noto-naskh-arabic-fonts google-noto-naskh-arabic-ui-fonts google-noto-naskh-arabic-ui-vf-fonts google-noto-naskh-arabic-vf-fonts google-noto-nastaliq-urdu-fonts google-noto-rashi-hebrew-fonts google-noto-rashi-hebrew-vf-fonts google-noto-sans-adlam-fonts google-noto-sans-adlam-unjoined-fonts google-noto-sans-adlam-unjoined-vf-fonts google-noto-sans-adlam-vf-fonts google-noto-sans-anatolian-hieroglyphs-fonts google-noto-sans-anatolian-hieroglyphs-vf-fonts google-noto-sans-arabic-fonts google-noto-sans-arabic-ui-fonts google-noto-sans-arabic-ui-vf-fonts google-noto-sans-arabic-vf-fonts google-noto-sans-armenian-fonts google-noto-sans-armenian-vf-fonts google-noto-sans-avestan-fonts google-noto-sans-avestan-vf-fonts google-noto-sans-balinese-fonts google-noto-sans-balinese-vf-fonts google-noto-sans-bamum-fonts google-noto-sans-bamum-vf-fonts google-noto-sans-bassa-vah-fonts google-noto-sans-bassa-vah-vf-fonts google-noto-sans-batak-fonts google-noto-sans-bengali-fonts google-noto-sans-bengali-ui-fonts google-noto-sans-bengali-ui-vf-fonts google-noto-sans-bengali-vf-fonts google-noto-sans-bhaiksuki-fonts google-noto-sans-brahmi-fonts google-noto-sans-buginese-fonts google-noto
[EPEL-devel] Re: Postgrey packaging issue
On 13/05/2021 10:21, Nick Howitt wrote:
On 13/05/2021 09:55, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 13 May 2021 at 10:21, Nick Howitt wrote:
Hi,
This app recently updated and I've noticed that it stomped on my
/etc/sysconfig/postrgey file isn't this wrong? Looking at the spec
file, in
the %files section it has:
%{_sysconfdir}/sysconfig/postgrey
Shouldn't this be:
%config(noreplace) %{_sysconfdir}/sysconfig/postgrey
It most probably should. This looks like a packaging bug and I'd suggest
opening a bug report, with a patch or even a pull request against the
spec file.
Regards,
Dominik
I've found the bug tracker and filed
https://bugzilla.redhat.com/show_bug.cgi?id=1960184. I'm lousy at
creating patch files so I've ducked it.
___
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
Ugh not an easy bug. The unit file has changed (or the requirements for
startup options have) so the sysconfig file needs more options in it. It
is a pity there was not a "%config noreplace" but with a smart %post to
add the extra parameters needed.
I think I'll mark the bug as invalid.
___
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
Re: F35 Change: Drop the the "Allow SSH root login with password" option from the installer GUI (Self-Contained Change proposal)
On Wednesday, 12 May 2021 23:35:44 EEST Ben Cotton wrote: > * it has been suggested that making it easier to import SSH keys from > popular code hosting platforms (Pagure, GitHub, GitLab, etc.) could > provide a nice alternative to the dropped option - Make a plugin interface for adding additional methods to obtain public keys as there are a lot different sources for those. Fedora itself has tools for PKI and public key based security and it would be quite low hanging fruit to fill the gap between those components, in cases like this. Problem itself is old one and there are known solutions for it: https://en.wikipedia.org/wiki/Public_key_infrastructure Maybe that plugin slot should have some callbacks to information for user interface - like hierarchial selection of country/organization and UI-labels to build an user interface for user, allowing to select right source of keys. For example, my public key is available from public source: ldapsearch -x -h ldap.fineid.fi -b dmdName=fineid,c=fi serialnumber=1350X usercertificate and response: usercertificate;binary:: MIIHMjCCBRqgAwIBAgIEO8QJwTANBgkqhkiG9w0BAQsFADCBlDELM AkGA1UEBhMCRkkxITAfBgNVBAoTGFZhZXN0b3Jla2lzdGVyaWtlc2t1cyBDQTEkMCIGA1UECxMbVm FsdGlvbiBrYW5zYWxhaXN2YXJtZW50ZWV0MTwwOgYDVQQDEzNWUksgR292LiBDQSBmb3IgQ2l0aXp lbiBRdWFsaWZpZWQgQ2VydGlmaWNhdGVzIC0gRzIwHhcNMTYwNjE0MDkxMzAxWhcNMjEwNjEzMjA1 . . . Ideally I would just choose country, trust provider and insert my unique serial number, and tadaa - a root access granted. Now I have to do that manually. The change itself is needed, take a look what happens at your network connected host's /var/log/secure - it's a constant flow of intrusion attempts. Tuju -- ___ 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-20210513.0 compose check report
No missing expected images. Failed openQA tests: 1/8 (x86_64) Old failures (same test failed in Fedora-Cloud-34-20210512.0): ID: 885660 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/885660 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-20210512.0): ID: 885668 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/885668 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
Fedora-Cloud-32-20210513.0 compose check report
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-32-20210512.0): ID: 885644 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/885644 ID: 885652 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/885652 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
[EPEL-devel] Re: Postgrey packaging issue
On 13/05/2021 09:55, Dominik 'Rathann' Mierzejewski wrote:
On Thursday, 13 May 2021 at 10:21, Nick Howitt wrote:
Hi,
This app recently updated and I've noticed that it stomped on my
/etc/sysconfig/postrgey file isn't this wrong? Looking at the spec file, in
the %files section it has:
%{_sysconfdir}/sysconfig/postgrey
Shouldn't this be:
%config(noreplace) %{_sysconfdir}/sysconfig/postgrey
It most probably should. This looks like a packaging bug and I'd suggest
opening a bug report, with a patch or even a pull request against the
spec file.
Regards,
Dominik
I've found the bug tracker and filed
https://bugzilla.redhat.com/show_bug.cgi?id=1960184. I'm lousy at
creating patch files so I've ducked it.
___
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
[EPEL-devel] Re: Postgrey packaging issue
On Thursday, 13 May 2021 at 10:21, Nick Howitt wrote:
> Hi,
> This app recently updated and I've noticed that it stomped on my
> /etc/sysconfig/postrgey file isn't this wrong? Looking at the spec file, in
> the %files section it has:
>
> %{_sysconfdir}/sysconfig/postgrey
>
> Shouldn't this be:
>
> %config(noreplace) %{_sysconfdir}/sysconfig/postgrey
It most probably should. This looks like a packaging bug and I'd suggest
opening a bug report, with a patch or even a pull request against the
spec file.
Regards,
Dominik
--
Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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 1959929] perl-Test2-Suite-0.000140 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1959929 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
[EPEL-devel] Postgrey packaging issue
Hi,
This app recently updated and I've noticed that it stomped on my
/etc/sysconfig/postrgey file isn't this wrong? Looking at the spec file,
in the %files section it has:
%{_sysconfdir}/sysconfig/postgrey
Shouldn't this be:
%config(noreplace) %{_sysconfdir}/sysconfig/postgrey
Regards,
Nick
___
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
Fedora-Cloud-33-20210513.0 compose check report
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-20210512.0): ID: 885628 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/885628 ID: 885636 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/885636 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: plocate?
On Wed, May 12, 2021 at 12:22:46PM +0200, Michal Sekletar wrote: > On Tue, May 4, 2021 at 1:25 PM Zbigniew Jędrzejewski-Szmek < > zbys...@in.waw.pl> wrote: > > > > > I agree. Plocate/mlocate is useful technology, but it's not important > > enough to justify maintaining two or three different implementations. > > If we can make plocate cover all bases, and it's faster, I'd just make > > it *the* implementation. Let's get the agreement of mlocate maintainer > > first though. Michal, wdyt? > > > > > Hi everyone, > > I agree that we should transition to the newer (faster and well maintained) > implementation and in the long run we should have only one locate > implementation in the distribution. However, I think we should have some > transition period (e.g. two Fedora release cycles), during which both > packages will be present. Introducing alternatives scaffolding seems like > an overkill for something that is going away in a year, hence plain > Conflits: tag would be enough. As for maintenance, I think that having an > older (mlocate) package available for a year or so while we iron out > potential compat issues or bugs shouldn't add too much work. > > Zbigniew, please take plocate through the review process and once it is > included in the distro I am willing to take up (co)maintenance of the > package. I updated the .spec file in the review request https://bugzilla.redhat.com/show_bug.cgi?id=1931141, but I can't review my own work ;) 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
[389-devel] 389 DS nightly 2021-05-13 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2021/05/13/report-389-ds-base-2.0.4-20210513git2a12316b7.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
