[Bug 1888513] New: perl-Math-FFT-1.35 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888513

Bug ID: 1888513
   Summary: perl-Math-FFT-1.35 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Math-FFT
  Keywords: FutureFeature, Triaged
  Assignee: msu...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: msu...@redhat.com, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.35
Current version/release in rawhide: 1.34-15.fc33
URL: http://search.cpan.org/dist/Math-FFT/

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


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


[389-devel] 389 DS nightly 2020-10-15 - 95% PASS

2020-10-14 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2020/10/15/report-389-ds-base-1.4.4.4-20201014git7fd97b1.fc32.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


[389-devel] Re: Roadmap for rust as a requirement in the project

2020-10-14 Thread William Brown
Hi everyone,

I'm once again here to bring up my favourite topic, of rust-in-ds. Slow and 
steady progress has been made, and it would be good to update the situation 
here. 

Completed Items are:

>> - william -> fix the intentional name leak in the rust slapi plugin 
>> interface to use lazy_static. Today this triggers LSAN which breaks basic 
>> test suites.
>> - william -> revive and make on upgrade configs better (see above), 
>> potentially break it out from the v4 plugin patch.

Todo Soon:

>> - everyone -> test that you can build and run tests with --enable-rust 
>> --disable-asan in your development environment so that we can work out and 
>> issues that may exist for us as developers.
> I meant to try this again to confirm, but it worked for me a few weeks ago on 
> Fedora.  The build took a lot longer :-( but it worked ;-)

>> - william -> clean up libsds linking and some of the related elements
>> - william + mark -> check that our respective major distros/releases can 
>> build with --enable-rust in release rpms
> As long as "make -f rpm.mk dist-bz2" does all the cargo building it should 
> work fine on Fedora and RHEL.

Todo a bit later

>> - william + viktor -> check that we can pass with --enable-rust and 
>> --enable-asan, especially in CI
>> - anyone interested -> update wiki contributing guide to include rust as a 
>> requirement
>> - (optional) anyone interested (but not william) -> add a section to the 
>> wiki on using rust in development
>> - team -> agree we are happy, and make configure.ac have --enable-rust by 
>> default
>> - team -> after a few weeks / months, remove the ifdefs, duplicate C 
>> versions of Rust features, and enable/disable features from configure.ac

I'm hoping that if we start to look at some of these items sooner, we could 
think about this for 1.4.4 (?). 

At the moment the major item for all of us would be to test that we can build 
in our development environments with rust, as that's a pretty major thing we 
need to pass for us to continue :)

Thanks!

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org


[389-devel] Re: Mapping tree rework

2020-10-14 Thread William Brown
This has come up because there is a set of customer cases where they have 
configured it incorrectly, due to bugs in lib389. The issues in lib389 arise 
from a lack of validation/constraint in the checking of the 
nsslapd-parent-suffix value in the server, allowing the client to create 
invalid configurations.

So today, our own tools can easily, and trivially cause this situation.

One thought is to either document this issue or to fix lib389 - but neither of 
the actions really fix the underlying problem, which is that our server accepts 
an invalid configuration silently. 

So the best thing for us to do is to make it impossible for the server to get 
it wrong, which means we fix lib389 *and* any other admin tooling/scripts in a 
single pass.

Which is what led to the interest in changing something that has been "working" 
for a long time :)



> On 14 Oct 2020, at 19:47, Ludwig Krispenz  wrote:
> 
> Hi,
> 
> you are right that it is possible to configure suffix hierarchies which are 
> broken, but in my experience this wasn't an issue. people using sub suffixes 
> did get it right.
> 
> So is there really a need to change something that is working for a long time 
> ?
> 
> 
> Regards,
> 
> Ludwig
> 
> 
> On 14.10.20 08:12, William Brown wrote:
>> https://github.com/mreynolds389/389wiki/pull/48
>> 
>> This is a draft design, and probably of interest to thierry whom I discussed 
>> this with last night :)
>> 
>> Thanks!
>> 
>> —
>> Sincerely,
>> 
>> William Brown
>> 
>> Senior Software Engineer, 389 Directory Server
>> SUSE Labs, Australia
>> ___
>> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
>> To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: 
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> ___
> 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

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org


[Bug 1888288] perl-EV in epel8

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888288



--- Comment #2 from Carl George 鸞  ---
I think I accidentally removed myself from this package.  I agreed in bug
1408326 to maintain the epel7 branch because at the time a coworker needed it. 
I have a new job now, so I don't actually have any need for this package
myself, but it's not fair to dump it on Emmanuel after agreeing to maintain it.
 That said, since I don't use this package, I'm not the best person to maintain
even just a branch of it.  Jakub, would you be willing to maintain the epel8
branch, and perhaps even the epel7 branch?  If not, Emmanuel please add me back
to maintain the epel7 branch as I agreed, but I'm not going to maintain the
epel8 branch in any case.

Side point, we now have a new permission level specifically for this called
"collaborator".  You can grant commit access to branches matching a pattern,
e.g. epel7 or epel*.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1870762] EPEL8 Branch Request: perl-SQL-Abstract

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1870762

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2020-6d933da06b has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6d933da06b


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


[Test-Announce] Re: Fedora 33 Candidate RC-1.1 Available Now!

2020-10-14 Thread Adam Williamson
On Wed, 2020-10-14 at 10:43 +, rawh...@fedoraproject.org wrote:
> According to the schedule [1], Fedora 33 Candidate RC-1.1 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan

To clarify this with Ben's post today: we considered this to be a non-
RC compose. In the distant past we had "test composes" (TCs) and
"release candidates" (RCs) and they were actually named differently and
built slightly differently; these days with Pungi 4 the distinction
doesn't really exist as far as the tools and naming conventions are
concerned, but we can still kind of "designate" candidate composes as
being RCs or not. We built this compose with known blockers
outstanding, so it cannot be considered an RC; we built it because we
wanted to test some updates in a compose before pushing them stable,
particularly the os-prober update:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-93c02b1d43

It would be good if folks who have systems with Windows, macOS, other
Linux distros and even other non-Linux but *nix-y OSes can test
installing alongside those, if possible, and check for any problems
that do not occur with recent nightly composes (which don't have the
new os-prober in them).

Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[389-devel] please review: PR 4378 - suffix management in backends is incorrect

2020-10-14 Thread Mark Reynolds

https://github.com/389ds/389-ds-base/pull/4378

--

389 Directory Server Development Team
___
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


Fedora 33 Final is NO-GO, Release Readiness meeting still on

2020-10-14 Thread Ben Cotton
Due to outstanding unresolved blockers, there is no release candidate
for Fedora 33 Final yet. I am cancelling tomorrow's Go/No-Go meeting.
The Release Readiness meeting *will be held* as scheduled[1]. Please
update the Release Readiness wiki page[2] with your team's readiness
if appropriate. We will use that to keep the Release Readiness meeting
short and focused.

The Fedora 33 Final Go/No-Go meeting[3] will be held at 1700 UTC on
Thursday 22 October in #fedora-meeting-1. We will target the Final
target date #1 milestone. The release schedule[5] has been updated
accordingly.

 Help is wanted with any of the outstanding blockers.

[1] https://apps.fedoraproject.org/calendar/meeting/9827/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://apps.fedoraproject.org/calendar/meeting/9831/
[4] https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist
[5] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org


[Test-Announce] Fedora 33 Final is NO-GO, Release Readiness meeting still on

2020-10-14 Thread Ben Cotton
Due to outstanding unresolved blockers, there is no release candidate
for Fedora 33 Final yet. I am cancelling tomorrow's Go/No-Go meeting.
The Release Readiness meeting *will be held* as scheduled[1]. Please
update the Release Readiness wiki page[2] with your team's readiness
if appropriate. We will use that to keep the Release Readiness meeting
short and focused.

The Fedora 33 Final Go/No-Go meeting[3] will be held at 1700 UTC on
Thursday 22 October in #fedora-meeting-1. We will target the Final
target date #1 milestone. The release schedule[5] has been updated
accordingly.

 Help is wanted with any of the outstanding blockers.

[1] https://apps.fedoraproject.org/calendar/meeting/9827/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://apps.fedoraproject.org/calendar/meeting/9831/
[4] https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist
[5] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1888395] perl-Mail-Message-3.010 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888395



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring.org's scratch build of
perl-Mail-Message-3.010-1.fc32.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=53465255


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888116] Please update to >=1.46, to build openssl 1.1.1d an newer

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888116

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2020-58288eadbd has been submitted as an update to Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-58288eadbd


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888395] perl-Mail-Message-3.010 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888395



--- Comment #1 from Upstream Release Monitoring 
 ---
Created attachment 1721554
  --> https://bugzilla.redhat.com/attachment.cgi?id=1721554=edit
[patch] Update to 3.010 (#1888395)


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888395] New: perl-Mail-Message-3.010 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888395

Bug ID: 1888395
   Summary: perl-Mail-Message-3.010 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Mail-Message
  Keywords: FutureFeature, Triaged
  Assignee: spo...@gmail.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 3.010
Current version/release in rawhide: 3.009-4.fc33
URL: http://search.cpan.org/dist/Mail-Message/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Re: new packager asks for help - packaging my first Python package

2020-10-14 Thread Miro Hrončok

On 14. 10. 20 20:29, Vojtěch Polášek wrote:

Hello,

I have some basics of RPM packaging, but I have not created a package from 
scratch yet. I would like to package one Python package called Tesserwrap. I 
used the pyp2rpm program to create a spec file. The file is here:


https://fedorapeople.org/~vpolasek/tesserwrap.spec

Unfortunately the build fails because there are some installed and unpackaged 
files. One of them is some debug file which I would probably discard, one of 
them is a shared library.


/usr/lib/debug/usr/lib64/python3.8/site-packages/libtesserwrap.cpython-38-x86_64-linux-gnu.so-0.1.6-1.fc32.x86_64.debug 


/usr/lib64/python3.8/site-packages/libtesserwrap.cpython-38-x86_64-linux-gnu.so

I have some questions:

1. How to ignore that installed file, e.g. do not package it? This goes for the 
debug file.


The debug file will be handled by magic when you include the normal file with 
Python extension module.


2. Where is some list of macros which I could use for my paths and file names? 
The file name of the library contains python version (cpython38). Can this be 
somehow expressed with macro or do I have to put there the file name manually?


Add this to %files:

%{python3_sitearch}/libtesserwrap%{python3_ext_suffix}

Or this:

%{python3_sitearch}/libtesserwrap.cpython-%{python3_version_nodots}-%{python3_platform_triplet}.so

Or this:

%{python3_sitearch}/libtesserwrap.cpython-*.so

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


new packager asks for help - packaging my first Python package

2020-10-14 Thread Vojtěch Polášek

Hello,

I have some basics of RPM packaging, but I have not created a package 
from scratch yet. I would like to package one Python package called 
Tesserwrap. I used the pyp2rpm program to create a spec file. The file 
is here:


https://fedorapeople.org/~vpolasek/tesserwrap.spec

Unfortunately the build fails because there are some installed and 
unpackaged files. One of them is some debug file which I would probably 
discard, one of them is a shared library.


/usr/lib/debug/usr/lib64/python3.8/site-packages/libtesserwrap.cpython-38-x86_64-linux-gnu.so-0.1.6-1.fc32.x86_64.debug
/usr/lib64/python3.8/site-packages/libtesserwrap.cpython-38-x86_64-linux-gnu.so

I have some questions:

1. How to ignore that installed file, e.g. do not package it? This goes 
for the debug file.


2. Where is some list of macros which I could use for my paths and file 
names? The file name of the library contains python version (cpython38). 
Can this be somehow expressed with macro or do I have to put there the 
file name manually?


Thank you very much,

Vojta
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1888379] perl-User-Identity-1.00 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888379

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
   Doc Type|--- |If docs needed, set a value
Last Closed||2020-10-14 18:06:33



--- Comment #2 from Tom "spot" Callaway  ---
1.00 in rawhide.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888379] New: perl-User-Identity-1.00 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888379

Bug ID: 1888379
   Summary: perl-User-Identity-1.00 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-User-Identity
  Keywords: FutureFeature, Triaged
  Assignee: spo...@gmail.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ser...@serjux.com,
spo...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.00
Current version/release in rawhide: 0.99-11.fc33
URL: http://search.cpan.org/dist/User-Identity/

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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888379] perl-User-Identity-1.00 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888379



--- Comment #1 from Upstream Release Monitoring 
 ---
An HTTP error occurred downloading the package's new Source URLs: Getting
https://cpan.metacpan.org/modules/by-module/User/User-Identity-1.00.tar.gz to
./User-Identity-1.00.tar.gz


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-14 Thread Kevin Fenzi
On Tue, Oct 13, 2020 at 12:14:24PM +0200, Leon Fauster wrote:
> Am 13.10.20 um 10:12 schrieb Christopher Engelhard:
> > On 12.10.20 10:49, Leon Fauster wrote:
> > > Not sure but IIRC EPEL should not depend on software collections ...?
> > 
> > Can someone confirm that? If the package can't depend on php7.2+, then
> > the question of how to deal with EPEL7 is moot.
> > 
> 
> My recall was this
> 
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/DBAQB3V35TXPNUV4UKKHXUC52BENZJUQ/

It's changed a bit since then. 

We now allow scls if: 

* They only need to be used at build time (ie, the rpms produced do not
require users to install/enable any scls)
* They are approved by the epel steering comittee. 

So far we have only enabled devtoolset. (so for example, chromium uses
devtoolset to build with a newer gcc, but does not require users to
install or enable anything to use it). 

In the case of php, this would likely not work because it would require
users to install/enable php to get the webserver module or cmd line. 

kevin


signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org


Re: intending to retire thunderbird-enigmail in F34+

2020-10-14 Thread Vít Ondruch
As a Rawhide use, who is effectively F34 user already, I'd appreciate if
you retired the thunderbird-enigmail in F35+ or mabybe just wait a bit
longer. This is good candidate for inclusion in fedora-obsolete-packages
BTW.

OTOH I'll soon update also my other computer and won't care anymore ;)


Vít


Dne 14. 10. 20 v 14:25 Felix Schwarz napsal(a):
> Hey,
>
> Thunderbird 78 changed its tech stack and integrated OpenPGP support so the
> enigmail plugin does not work anymore.
>
> Enigmail 2.2.x does not contain any OpenPGP functionality besides a migration
> tool which migrates keys to Thunderbird's internal keyring. Since Thunderbird
> 78 was pushed to F31+ I also updated thunderbird-enigmail.
>
> However I'd like to retire the package in rawhide (F34+) as the new version
> does not provide any features once users migrated their keys to Thunderbird.
> (I'll ship enigmail in F33 as a zero-day update as I think we can not remove a
> package anymore from F33 at this point.)
>
> Objections?
>
> Felix
>
> PS: Worst case users can always install the add-on manually via Thunderbird's
> extension manager.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora-IoT-33-20201014.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

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

Old soft failures (same test soft failed in Fedora-IoT-33-20201013.0):

ID: 695479  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/695479

Passed openQA tests: 15/16 (x86_64)

Installed system changes in test x86_64 IoT-dvd_ostree-iso 
install_default@uefi: 
System load changed from 0.14 to 0.39
Previous test data: https://openqa.fedoraproject.org/tests/693438#downloads
Current test data: https://openqa.fedoraproject.org/tests/695482#downloads
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1888288] perl-EV in epel8

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888288

Petr Pisar  changed:

   What|Removed |Added

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



--- Comment #1 from Petr Pisar  ---
I think Carl does not maintain this package in EPEL because he has no commit
access to the git repository. Emmanuel could help you including changing the
Bugzilla assignee for EPEL.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #6 from Fedora Update System  ---
FEDORA-2020-54db3ea55d has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-54db3ea55d`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-54db3ea55d

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


[Bug 1888006] perl-DB_File-1.855 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888006

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
FEDORA-2020-506f68c17b has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2020-506f68c17b`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-506f68c17b

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


[Bug 1888288] New: perl-EV in epel8

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888288

Bug ID: 1888288
   Summary: perl-EV in epel8
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-EV
  Assignee: c...@redhat.com
  Reporter: jakub.jedel...@gmail.com
QA Contact: extras...@fedoraproject.org
CC: c...@redhat.com, emman...@seyman.fr,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Hello, could you, please, build perl-EV for EPEL8? It'll help me/us to build
even more perl packages. I'm able to help with it if needed, feel free to add
me as a contributor.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


Fedora-IoT-34-20201014.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 3/16 (x86_64)

Old failures (same test failed in Fedora-IoT-34-20201013.0):

ID: 695446  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/695446
ID: 695464  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/695464
ID: 695478  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/695478

Skipped non-gating openQA tests: 13 of 16
-- 
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


Fedora-33-20201014.n.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 2/181 (x86_64)

New failures (same test not failed in Fedora-33-20201013.n.0):

ID: 695111  Test: x86_64 Workstation-live-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/695111

Old failures (same test failed in Fedora-33-20201013.n.0):

ID: 695128  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/695128

Soft failed openQA tests: 10/181 (x86_64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-33-20201013.n.0):

ID: 695053  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/695053
ID: 695072  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/695072
ID: 695099  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/695099
ID: 695112  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/695112
ID: 695132  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/695132
ID: 695135  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/695135
ID: 695149  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/695149
ID: 695161  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/695161
ID: 695183  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/695183
ID: 695186  Test: x86_64 universal upgrade_2_minimal_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/695186

Passed openQA tests: 169/181 (x86_64)

Installed system changes in test x86_64 Workstation-live-iso 
install_default_upload: 
Used swap changed from 59 MiB to 40 MiB
System load changed from 0.80 to 1.06
Previous test data: https://openqa.fedoraproject.org/tests/693284#downloads
Current test data: https://openqa.fedoraproject.org/tests/695096#downloads

Installed system changes in test x86_64 Workstation-live-iso 
install_default@uefi: 
Used swap changed from 52 MiB to 36 MiB
Previous test data: https://openqa.fedoraproject.org/tests/693286#downloads
Current test data: https://openqa.fedoraproject.org/tests/695098#downloads

Installed system changes in test x86_64 KDE-live-iso install_default_upload: 
Used swap changed from 15 MiB to 17 MiB
System load changed from 1.12 to 1.60
Previous test data: https://openqa.fedoraproject.org/tests/693303#downloads
Current test data: https://openqa.fedoraproject.org/tests/695115#downloads

Installed system changes in test x86_64 KDE-live-iso install_default@uefi: 
Used swap changed from 60 MiB to 15 MiB
System load changed from 2.03 to 1.11
Average CPU usage changed from 48.08571429 to 28.87142857
Previous test data: https://openqa.fedoraproject.org/tests/693304#downloads
Current test data: https://openqa.fedoraproject.org/tests/695116#downloads

Installed system changes in test x86_64 Silverblue-dvd_ostree-iso 
install_default_upload: 
Used swap changed from 28 MiB to 23 MiB
Previous test data: https://openqa.fedoraproject.org/tests/693320#downloads
Current test data: https://openqa.fedoraproject.org/tests/695132#downloads

Installed system changes in test x86_64 Silverblue-dvd_ostree-iso 
install_default@uefi: 
Used swap changed from 29 MiB to 25 MiB
System load changed from 0.32 to 0.58
Previous test data: https://openqa.fedoraproject.org/tests/693323#downloads
Current test data: https://openqa.fedoraproject.org/tests/695135#downloads

Installed system changes in test x86_64 universal install_package_set_kde: 
Used swap changed from 5 MiB to 6 MiB
System load changed from 1.06 to 1.34
Previous test data: https://openqa.fedoraproject.org/tests/693364#downloads
Current test data: https://openqa.fedoraproject.org/tests/695176#downloads

Installed system changes in test x86_64 universal install_package_set_minimal: 
System load changed from 0.21 to 0.10
Previous test data: https://openqa.fedoraproject.org/tests/693411#downloads
Current test data: https://openqa.fedoraproject.org/tests/695223#downloads


-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: fedora net install iso the possibilitie to add espeakup for people like me whome are blind?

2020-10-14 Thread Martin Kolman
On Thu, 2020-10-08 at 12:05 -0500, Michael Catanzaro wrote:
> On Thu, Oct 8, 2020 at 12:43 pm, Robbie Harwood  
> wrote:
> > That's unfortunate, and will hurt adoption with users who need it.  
> > Are
> > there things that could be done to make it easier to add?
> 
> Currently anaconda is not accessible even in the default live 
> Workstation install that runs under gnome-shell and where everything 
> else is accessible. I don't know why, but orca just doesn't read 
> anything from anaconda, whereas it does for everything else.
IIRC the latest findings point to Anaconda GUI running as root likely being teh 
case. Other
GUI apps running as root (gparted) apparently behave the same. CCing Vladimir 
Slavik who has been
looking into this recently.

>  Since that 
> is what the vast majority of our users will be using to install, I 
> would say that's where the greatest benefit lies. Of course netinstall 
> is important too, but realistically it's not very easy to find those 
> images compared with the heavily-promoted live image.
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1883530] Add perl-Curses-UI to EPEL8

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1883530

Pierre Amadio  changed:

   What|Removed |Added

  Flags||needinfo?(davejohansen@gmai
   ||l.com)




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1883530] Add perl-Curses-UI to EPEL8

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1883530

Pierre Amadio  changed:

   What|Removed |Added

 CC||pama...@redhat.com



--- Comment #1 from Pierre Amadio  ---
Would it be possible to get an update on the previous comment from Petr ?


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


What’s new in Fedora CI

2020-10-14 Thread Michal Srb
Hello!

There are some cool new features in Fedora CI that we would like to tell
you about.

First of all, Fedora CI now supports running tests using the new tmt
format. The tmt tool provides better user experience for enabling, creating
and running tests across different environments (e.g. vm, container,
localhost). The same configuration can be used for enabling tests in
Packit, Fedora CI and RHEL CI. See [1] to get a quick start.

This functionality is available for Rawhide and for dist-git pull requests.
The older STI format is, of course, still supported and it takes precedence
over tmt. If you’d want to switch over to tmt, you will need to rename or
delete the tests*.yml files used by STI.

Next there are 3 generic tests that automatically run on all Rawhide
builds. Note not all of them are completely new — you’ve likely seen some
of these tests before. What’s really new is that all these generic tests
run in Testing Farm [2] now. Testing Farm is a new test execution service
that provides an infrastructure that should be much more stable and as a
result, less flakiness overall.

These generic tests are:

   -

   rpmdeplint
   -

   rpminspect
   -

   installability


If you’d want to know more about any of those tests, please check out the
Fedora CI wiki page [3].

And last but not least, here are some real world examples of (potential)
problems that the tests discovered in the recent Rawhide builds:


[rpmdeplint] undeclared file conflicts:

https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpmdeplint-pipeline/job/master/7921/testReport/(root)/tests/

[rpminspect] relaxed permissions:

https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/6461/testReport/junit/(root)/tests/

[installability] package cannot be installed:

https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/installability-pipeline/job/master/5499/testReport/junit/(root)/tests/



All this was a multi-team effort and I'd like to thank everyone who
participated :)


Thanks,

Michal


[1]: https://docs.fedoraproject.org/en-US/ci/tmt/

[2]: https://testing-farm.gitlab.io/api/

[3]: https://docs.fedoraproject.org/en-US/ci/generic_tests/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora 33 compose report: 20201014.n.0 changes

2020-10-14 Thread Fedora Rawhide Report
OLD: Fedora-33-20201013.n.0
NEW: Fedora-33-20201014.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   11
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   377.33 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   979.24 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  bcm283x-firmware-20201008-2.63b1922.fc33
Old package:  bcm283x-firmware-20200928-2.f0eab3a.fc33
Summary:  Firmware for the Broadcom bcm283x/bcm2711 used in the Raspberry Pi
RPMs: bcm2711-firmware bcm2835-firmware bcm283x-firmware 
bcm283x-overlays
Size: 13.66 MiB
Size change:  -2.21 KiB
Changelog:
  * Sat Oct 10 2020 Peter Robinson  
20201008-1.63b1922
  - Latest firmware update

  * Mon Oct 12 2020 Peter Robinson  
20201008-2.63b1922
  - Enable UART for all devices to work around firmware boot issues


Package:  fawkes-1.3.1-0.1.4923a6c.fc33
Old package:  fawkes-1.3.0-12.fc33
Summary:  Robot Software Framework
RPMs: fawkes fawkes-core fawkes-devel fawkes-devenv fawkes-doc 
fawkes-firevision fawkes-firevision-tools fawkes-guis fawkes-lua 
fawkes-plugin-amcl fawkes-plugin-bblogger fawkes-plugin-bbsync 
fawkes-plugin-cedar fawkes-plugin-clips fawkes-plugin-clips-agent 
fawkes-plugin-clips-executive fawkes-plugin-clips-navgraph 
fawkes-plugin-clips-pddl-parser fawkes-plugin-clips-protobuf 
fawkes-plugin-clips-tf fawkes-plugin-colli fawkes-plugin-dynamixel 
fawkes-plugin-execution-time-estimator fawkes-plugin-flite fawkes-plugin-gazebo 
fawkes-plugin-gazsim-comm fawkes-plugin-gazsim-depthcam 
fawkes-plugin-gazsim-laser fawkes-plugin-gazsim-localization 
fawkes-plugin-gazsim-robotino fawkes-plugin-gazsim-timesource 
fawkes-plugin-gazsim-vis-localization fawkes-plugin-gazsim-webcam 
fawkes-plugin-gossip fawkes-plugin-hardware-models fawkes-plugin-imu 
fawkes-plugin-jaco fawkes-plugin-joystick fawkes-plugin-joystick-teleop 
fawkes-plugin-katana fawkes-plugin-laser fawkes-plugin-laser-cluster 
fawkes-plugin-laser-filter fawkes-plugin-laser-lines 
fawkes-plugin-laser-pointclouds fawkes-plugin-luaagent 
fawkes-plugin-map-lasergen fawkes-plugin-navgraph 
fawkes-plugin-navgraph-clusters fawkes-plugin-navgraph-generator 
fawkes-plugin-navgraph-static-constraints fawkes-plugin-openni 
fawkes-plugin-openni-data fawkes-plugin-openni-handtracker 
fawkes-plugin-openni-pcl-frombuf fawkes-plugin-openni-usertracker 
fawkes-plugin-pantilt fawkes-plugin-realsense fawkes-plugin-realsense2 
fawkes-plugin-refboxcomm fawkes-plugin-robot-state-publisher 
fawkes-plugin-robotino fawkes-plugin-robotino-ir-pcl fawkes-plugin-roomba 
fawkes-plugin-rrd fawkes-plugin-skiller fawkes-plugin-skiller-simulator 
fawkes-plugin-static-transforms fawkes-plugin-tabletop-objects 
fawkes-plugin-ttmainloop fawkes-plugin-webview fawkes-plugin-xmlrpc 
fawkes-protobuf
Added RPMs:   fawkes-plugin-execution-time-estimator 
fawkes-plugin-hardware-models
Size: 72.75 MiB
Size change:  882.52 KiB
Changelog:
  * Thu Jun 04 2020 Nicolas Chauvet  - 1.3.0-13
  - Rebuilt for OpenCV 4.3

  * Sun Jun 14 2020 Adrian Reber  - 1.3.0-14
  - Rebuilt for protobuf 3.12

  * Mon Jul 27 2020 Fedora Release Engineering  - 
1.3.0-15
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild

  * Sat Aug 01 2020 Fedora Release Engineering  - 
1.3.0-16
  - Second attempt - Rebuilt for
https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild

  * Fri Oct 09 2020 Till Hofmann  - 
1.3.1-0.1.4923a6c
  - Update to snapshot release to fix FTBFS
  - Add new plugins


Package:  gazebo-10.1.0-11.fc33
Old package:  gazebo-10.1.0-10.fc33
Summary:  3D multi-robot simulator with dynamics
RPMs: gazebo gazebo-common gazebo-devel gazebo-doc gazebo-libs 
gazebo-media gazebo-ode gazebo-ode-devel player-gazebo
Size: 126.95 MiB
Size change:  54.84 KiB
Changelog:
  * Sat Oct 10 2020 Till Hofmann  - 10.1.0-11
  - Rebuilt for protobuf 3.12.4 / ignition-msgs 1.0.0-9 (#1863531)


Package:  gnome-calendar-3.38.1-2.fc33
Old package:  gnome-calendar-3.38.1-1.fc33
Summary:  Simple and beautiful calendar application designed to fit GNOME 3
RPMs: gnome-calendar
Size: 2.21 MiB
Size change:  -113 B
Changelog:
  * Tue Oct 13 2020 Michael Catanzaro  - 3.38.1-2
  - Fix #1883681 crashes in on_calendar_monitor_completed_cb()


Package:  gnome-control-center-3.38.1-2.fc33
Old package:  gnome-control-center-3.38.1-1.fc33
Summary:  Utilities to configure the GNOME desktop
RPMs: gnome-control-center gnome-control-center-filesystem
Size: 28.34 MiB
Size change:  3.66 KiB
Changelog:
  * Tue Oct 13 2020 Kalev Lember  - 3.38.1-2
  - Add Recommends: nm-connection-editor for the network panel (#1887891)


Package

Disk space minimization of Python

2020-10-14 Thread Tomas Orsava

Hi,
I have opened an upstream discussion about disk space minimization of 
Python, take a look:


https://discuss.python.org/t/disk-space-minimization-for-python-distributors/5447

All the best,
Tomas
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org


Fedora-Rawhide-20201014.n.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

Compose FAILS proposed Rawhide gating check!
24 of 43 required tests failed, 17 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 95/181 (x86_64)

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

ID: 694727  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/694727
ID: 694728  Test: x86_64 Server-dvd-iso install_vncconnect_server
URL: https://openqa.fedoraproject.org/tests/694728
ID: 694732  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/694732
ID: 694734  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/694734
ID: 694746  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/694746
ID: 694765  Test: x86_64 Everything-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/694765
ID: 694766  Test: x86_64 Everything-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/694766
ID: 694769  Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/694769
ID: 694787  Test: x86_64 KDE-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/694787
ID: 694828  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/694828
ID: 694855  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/694855
ID: 694856  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/694856
ID: 694873  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/694873
ID: 694876  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/694876
ID: 694889  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/694889
ID: 694906  Test: x86_64 Server-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/694906
ID: 694907  Test: x86_64 Everything-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/694907
ID: 694908  Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694908
ID: 694909  Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694909
ID: 694910  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/694910
ID: 694926  Test: x86_64 Server-dvd-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/694926
ID: 694937  Test: x86_64 Workstation-live-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/694937
ID: 694952  Test: x86_64 Server-dvd-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694952
ID: 694953  Test: x86_64 KDE-live-iso install_default_upload **GATING**
URL: https://openqa.fedoraproject.org/tests/694953
ID: 694969  Test: x86_64 KDE-live-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694969
ID: 694970  Test: x86_64 universal install_multi **GATING**
URL: https://openqa.fedoraproject.org/tests/694970
ID: 694971  Test: x86_64 universal install_mirrorlist_graphical **GATING**
URL: https://openqa.fedoraproject.org/tests/694971
ID: 694972  Test: x86_64 universal install_blivet_resize_lvm
URL: https://openqa.fedoraproject.org/tests/694972
ID: 694973  Test: x86_64 universal install_repository_http_graphical 
**GATING**
URL: https://openqa.fedoraproject.org/tests/694973
ID: 694974  Test: x86_64 universal install_repository_http_variation 
**GATING**
URL: https://openqa.fedoraproject.org/tests/694974
ID: 694975  Test: x86_64 universal install_resize_lvm
URL: https://openqa.fedoraproject.org/tests/694975
ID: 694976  Test: x86_64 universal install_scsi_updates_img **GATING**
URL: https://openqa.fedoraproject.org/tests/694976
ID: 694977  Test: x86_64 universal install_delete_pata **GATING**
URL: https://openqa.fedoraproject.org/tests/694977
ID: 694978  Test: x86_64 KDE-live-iso install_no_user **GATING**
URL: https://openqa.fedoraproject.org/tests/694978
ID: 694979  Test: x86_64 universal install_sata **GATING**
URL: https://openqa.fedoraproject.org/tests/694979
ID: 694980  Test: x86_64 universal install_sata@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694980
ID: 694981  Test: x86_64 universal install_delete_pata@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694981
ID: 694982  Test: x86_64 universal install_multi@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/694982
ID: 694983  Test: x86_64 universal 

intending to retire thunderbird-enigmail in F34+

2020-10-14 Thread Felix Schwarz
Hey,

Thunderbird 78 changed its tech stack and integrated OpenPGP support so the
enigmail plugin does not work anymore.

Enigmail 2.2.x does not contain any OpenPGP functionality besides a migration
tool which migrates keys to Thunderbird's internal keyring. Since Thunderbird
78 was pushed to F31+ I also updated thunderbird-enigmail.

However I'd like to retire the package in rawhide (F34+) as the new version
does not provide any features once users migrated their keys to Thunderbird.
(I'll ship enigmail in F33 as a zero-day update as I think we can not remove a
package anymore from F33 at this point.)

Objections?

Felix

PS: Worst case users can always install the add-on manually via Thunderbird's
extension manager.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora-33-20201014.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 7/181 (x86_64)

ID: 694483  Test: x86_64 Server-dvd-iso release_identification
URL: https://openqa.fedoraproject.org/tests/694483
ID: 694544  Test: x86_64 Silverblue-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/694544
ID: 694690  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/694690
ID: 694691  Test: x86_64 Workstation-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/694691
ID: 694707  Test: x86_64 KDE-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/694707
ID: 694708  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/694708
ID: 694724  Test: x86_64 KDE-live-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/694724

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

ID: 694461  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/694461
ID: 694480  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/694480
ID: 694540  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/694540
ID: 694543  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/694543
ID: 694557  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/694557
ID: 694569  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/694569
ID: 694591  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/694591
ID: 694594  Test: x86_64 universal upgrade_2_minimal_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/694594

Passed openQA tests: 136/181 (x86_64)

Skipped non-gating openQA tests: 30 of 181
-- 
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


Fedora rawhide compose report: 20201014.n.0 changes

2020-10-14 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20201013.n.0
NEW: Fedora-Rawhide-20201014.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  15
Dropped packages:0
Upgraded packages:   87
Downgraded packages: 0

Size of added packages:  759.92 KiB
Size of dropped packages:0 B
Size of upgraded packages:   5.40 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: perl-Test-Snapshot-0.06-1.fc34
Summary: Test against data stored in automatically-named file
RPMs:perl-Test-Snapshot
Size:13.55 KiB

Package: perl-Test2-Tools-PerlCritic-0.03-2.fc34
Summary: Testing tools to enforce Perl::Critic policies
RPMs:perl-Test2-Tools-PerlCritic
Size:20.87 KiB

Package: python-zuul-client-0.0.2-1.fc34
Summary: The zuulclient Python module
RPMs:python-zuul-client-doc python3-zuul-client
Size:177.52 KiB

Package: rust-andrew-0.3.0-1.fc34
Summary: Convenient drawing of shapes, lines and text to buffers
RPMs:rust-andrew+default-devel rust-andrew-devel
Size:25.85 KiB

Package: rust-cedarwood-0.4.4-1.fc34
Summary: Efficiently-updatable double-array trie in Rust (ported from cedar)
RPMs:rust-cedarwood+default-devel rust-cedarwood+reduced-trie-devel 
rust-cedarwood-devel
Size:33.76 KiB

Package: rust-dlv-list-0.2.2-1.fc34
Summary: Semi-doubly linked list implemented using a vector
RPMs:rust-dlv-list+default-devel rust-dlv-list-devel
Size:26.54 KiB

Package: rust-fdlimit-0.2.1-1.fc34
Summary: Utility crate for raising file descriptors limit for OSX and Linux
RPMs:rust-fdlimit+default-devel rust-fdlimit-devel
Size:21.03 KiB

Package: rust-font-kit-0.10.0-1.fc34
Summary: Cross-platform font loading library
RPMs:rust-font-kit+default-devel rust-font-kit+freetype-devel 
rust-font-kit+loader-freetype-default-devel rust-font-kit+loader-freetype-devel 
rust-font-kit+servo-fontconfig-devel rust-font-kit+source-devel 
rust-font-kit+source-fontconfig-default-devel 
rust-font-kit+source-fontconfig-devel rust-font-kit-devel
Size:118.93 KiB

Package: rust-httpdate-0.3.2-1.fc34
Summary: HTTP date parsing and formatting
RPMs:rust-httpdate+default-devel rust-httpdate+unstable-devel 
rust-httpdate-devel
Size:31.91 KiB

Package: rust-ordered-multimap-0.3.0-1.fc34
Summary: Insertion ordered multimap
RPMs:rust-ordered-multimap+default-devel rust-ordered-multimap-devel
Size:32.23 KiB

Package: rust-owned_ttf_parser-0.6.0-1.fc34
Summary: Support for owned data on top of ttf-parser
RPMs:rust-owned_ttf_parser+default-devel rust-owned_ttf_parser+std-devel 
rust-owned_ttf_parser-devel
Size:29.93 KiB

Package: rust-pathfinder_geometry-0.5.1-1.fc34
Summary: Basic SIMD-accelerated geometry/linear algebra
RPMs:rust-pathfinder_geometry+default-devel rust-pathfinder_geometry-devel
Size:26.21 KiB

Package: rust-rusttype-0.9.2-1.fc34
Summary: Pure Rust alternative to libraries like FreeType
RPMs:rust-rusttype+crossbeam-deque-devel 
rust-rusttype+crossbeam-utils-devel rust-rusttype+default-devel 
rust-rusttype+gpu_cache-devel rust-rusttype+has-atomics-devel 
rust-rusttype+libm-devel rust-rusttype+libm-math-devel 
rust-rusttype+linked-hash-map-devel rust-rusttype+num_cpus-devel 
rust-rusttype+rustc-hash-devel rust-rusttype+std-devel rust-rusttype-devel
Size:118.05 KiB

Package: rust-tinyvec0.3-0.3.4-1.fc34
Summary: Just, really the littlest Vec you could need
RPMs:rust-tinyvec0.3+alloc-devel rust-tinyvec0.3+default-devel 
rust-tinyvec0.3+experimental_write_impl-devel 
rust-tinyvec0.3+grab_spare_slice-devel 
rust-tinyvec0.3+nightly_const_generics-devel 
rust-tinyvec0.3+nightly_slice_partition_dedup-devel rust-tinyvec0.3-devel
Size:66.92 KiB

Package: rust-tinyvec_macros-0.1.0-1.fc34
Summary: Some macros for tiny containers
RPMs:rust-tinyvec_macros+default-devel rust-tinyvec_macros-devel
Size:16.62 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  CTL-1.5.2-13.fc34
Old package:  CTL-1.5.2-12.fc34
Summary:  The Color Transformation Language
RPMs: CTL CTL-devel CTL-docs OpenEXR_CTL
Size: 6.88 MiB
Size change:  6.11 KiB
Changelog:
  * Tue Oct 13 2020 Jeff Law  - 1.5.2-13
  - Fix deprecated use of std::istream::streampos


Package:  R-4.0.3-1.fc34
Old package:  R-4.0.2-5.fc34
Summary:  A language for data analysis and graphics
RPMs: R R-core R-core-devel R-devel R-java R-java-devel libRmath 
libRmath-devel libRmath-static
Size: 346.08 MiB
Size change:  2.48 MiB
Changelog:
  * Mon Oct 12 2020 Tom Callaway  - 4.0.3-1
  - update to 4.0.3


Package:  R-bookdown-0.21-1.fc34
Old package:  R-bookdown-0.20-1.fc33
Summary:  Authoring Books and Technical Documents with R Markdown
RPMs: R-bookdown
Size: 906.39 KiB
Size change:  10.95 KiB
Changelog:
  * Tue Oct 13 2020 Elliott Sales de

Re: libtasn1 >= 4.3 provided by libtasn1-4.16.0-1.fc32 ?

2020-10-14 Thread Roman Mohr
On Wed, Oct 14, 2020 at 1:12 PM Daniel P. Berrangé 
wrote:

> On Wed, Oct 14, 2020 at 12:57:54PM +0200, Roman Mohr wrote:
> > Hi,
> >
> > I am playing with RPM dependency resolution and I came across this in the
> > fc32 repos:
> >
> > # dnf -y deplist gnutls | grep libtasn1
> > Last metadata expiration check: 2:04:09 ago on Wed 14 Oct 2020 09:47:12
> > CEST.
> >   dependency: libtasn1 >= 4.3
> >provider: libtasn1-4.16.0-1.fc32.i686
> >provider: libtasn1-4.16.0-1.fc32.x86_64
> >
> > Could someone explain to me why version 4.16.0 satisfies 4.3? Does RPM
> > implicitly add `0.` to the comparison and it effectively compares
> `4.16.0`
> > with `0.4.3`?
>
> IIRC, it will compare each component of the version in turn and stop
> evaluation as soon as it gets an answer. So effectively it has
> compared  4.16 <=> 4.3, the trailing '.0' in 4.16.0 never needed
> evaluating.
>
>
Vitaly, Daniel thanks. My brain permanently makes 4.1.6 out of 4.16. It is
obviously correct.

Best regards,
Roman


> Regards,
> Daniel
> --
> |: https://berrange.com  -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org-o-
> https://www.instagram.com/dberrange :|
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: our containers with alias vim=vi

2020-10-14 Thread Jonathan Wakely

On 13/10/20 16:04 +0200, Zdenek Dohnal wrote:

On 10/13/20 12:34 PM, Jonathan Wakely wrote:

On 13/10/20 07:45 +0200, Zdenek Dohnal wrote:


On 10/12/20 5:15 PM, Joe Doss wrote:

On 10/12/20 1:50 AM, Zdenek Dohnal wrote:

This would break using Vim when vim-minimal and vim-enhanced are
installed (it would start Vi instead of typed Vim). To make it work,
vim-minimal would have to conflict with vim-enhanced, which doesn't
make
sense - Vi and Vim binaries can exist together just fine.


I have vim-enhanced and vim-minimal installed

# rpm -qa |grep vim
vim-common-8.2.1770-1.fc33.x86_64
vim-filesystem-8.2.1770-1.fc33.noarch
vim-minimal-8.2.1770-1.fc33.x86_64
vim-enhanced-8.2.1770-1.fc33.x86_64

and when I type vi it launches vim.

I'm sorry I forgot about this alias - yes, there is an alias which is
applied when both - vim-minimal and vim-enhanced - are installed so it
launches 'vim' when you type 'vi'. I would say less people will complain
if something has more features than if it has less, so I'm content with
this alias.


# whereis vi
vi: /usr/bin/vi /usr/share/man/man1p/vi.1p.gz
/usr/share/man/man1/vi.1.gz
# /usr/bin/vi --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 29 2020 00:00:00)

It doesn't look like these are existing together just fine. It seems
that vim takes over vi. Shouldn't these conflict and only one can be
installed over the other?

'Vi' as the original project is no longer (I'm not sure for how long)
shipped in Fedora. 'Vi' we ship is just 'VIM' compiled with 'small' set
of features (f.e. without syntax highlighting) to mimic the original
'Vi'. So if you run 'vi --version' it always shows 'VIM'.



In the end I find it incorrect to mislead users by default by telling
them 'Vim works' but Vi is run instead - Vi and Vim don't have the
same
set of features, which may lead into bug reports caused by this
mistake.


Isn't that the reverse behavior detailed above? I type vi on Fedora
Workstation it launches vim? I assume this isn't causing bug reports.

You're right, as I wrote above - aliasing vi->vim doesn't seem as a
problem to me, but aliasing vim->vi as clime suggested can cause mislead
for users.


I would also appreciate if "vim" ran the executable installed by
vim-minimal. I frequently type "vim" on servers I don't own and then
grumble that it fails and I have to run "vi" instead. It **is** vim,
it's just not installed with that name.  Insisting that users call it
vi when we know it's vim and they know it's vim seems unnecessary.


It's Vim but with a different set of features - VIM compiled as Vi
binary is trying to be small, kind of simulate Vi behavior without
setting 'compatible'.

Since you know it has less features, good for you. But unfortunately,
not all users know - there was already a report about Vim missing
highlighting, and the reporter was running /usr/bin/vi. So my aim is to
prevent such a report.



$ rpm -qf /usr/bin/vi
vim-minimal-8.2.1770-1.fc32.x86_64

Could vim-minimal and vim-enhanced both install the same
/etc/profile.d/vim.sh file that did something like this?

Installing the same file would mean to set conflicts between those two
package, wouldn't it? Or would you mind explaining how to achieve it?


RPM allows a file to be owned by more than one package. Fedora has
allowed this for eight years:
https://pagure.io/packaging-committee/issue/138
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_file_and_directory_ownership

The file would be owned by both packages, and only removed if both
packages get removed. That means it would be present if at least one
of them was installed.



if [ -n "${BASH_VERSION-}" -o -n "${KSH_VERSION-}" -o -n
"${ZSH_VERSION-}" ]; then
  [ "`/usr/bin/id -u 2>/dev/null || echo 0`" -le 200 ] && return
  # for bash and and ksh and zsh
  case "$(type -t vim)-$(type -t vi)" in
    file-file)
      # both vim and vi are present
      alias vi=vim
      alias view="vim -R"
      ;;
    -file)
      # only vim-minimal is installed, expose it as 'vim' too
      alias vim=vi
      ;;
  esac
fi


Looks good, although it doesn't touch the problem mistaking Vi and Vim
as I said before. I tried to come up with a little bash script which
will mention it really runs vi instead of typed vim (just the important
snippet):

alias vim="read -rep $'No vim found, using vi, press ENTER to
continue\n' -n1 -t 20 -s && vi"

This can be add into bash profile instead of 'alias vim=vi' when only
vim-minimal is installed.

Does it work for our case? IMO only problem would be with scripting, but
scripts which depend on vim and run on machine without vim-enhanced are
broken even now, so it shouldn't be a problem here.


That would work for me.
___
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 

Re: our containers with alias vim=vi

2020-10-14 Thread Jonathan Wakely

On 13/10/20 07:38 -0500, Chris Adams wrote:

Once upon a time, Jonathan Wakely  said:

Could vim-minimal and vim-enhanced both install the same
/etc/profile.d/vim.sh file that did something like this?

if [ -n "${BASH_VERSION-}" -o -n "${KSH_VERSION-}" -o -n "${ZSH_VERSION-}" ]; 
then
  [ "`/usr/bin/id -u 2>/dev/null || echo 0`" -le 200 ] && return


Why this?  Why not alias vi=vim for root?  We don't block root from
running vim (so it doesn't appear to be for security - vim already
ignores some things when running as root).


That was already there, I just copied what is in /etc/profile.d/vim.sh
today.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: libtasn1 >= 4.3 provided by libtasn1-4.16.0-1.fc32 ?

2020-10-14 Thread Daniel P . Berrangé
On Wed, Oct 14, 2020 at 12:57:54PM +0200, Roman Mohr wrote:
> Hi,
> 
> I am playing with RPM dependency resolution and I came across this in the
> fc32 repos:
> 
> # dnf -y deplist gnutls | grep libtasn1
> Last metadata expiration check: 2:04:09 ago on Wed 14 Oct 2020 09:47:12
> CEST.
>   dependency: libtasn1 >= 4.3
>provider: libtasn1-4.16.0-1.fc32.i686
>provider: libtasn1-4.16.0-1.fc32.x86_64
> 
> Could someone explain to me why version 4.16.0 satisfies 4.3? Does RPM
> implicitly add `0.` to the comparison and it effectively compares `4.16.0`
> with `0.4.3`?

IIRC, it will compare each component of the version in turn and stop
evaluation as soon as it gets an answer. So effectively it has
compared  4.16 <=> 4.3, the trailing '.0' in 4.16.0 never needed
evaluating.

Regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: libtasn1 >= 4.3 provided by libtasn1-4.16.0-1.fc32 ?

2020-10-14 Thread Vitaly Zaitsev via devel

On 14.10.2020 12:57, Roman Mohr wrote:

dependency: libtasn1 >= 4.3
provider: libtasn1-4.16.0-1.fc32.x86_64
Could someone explain to me why version 4.16.0 satisfies 4.3?


Version 4.16.0 is higher than 4.3, that's why the expression X >= 4.3 
will be TRUE.


$ rpmdev-vercmp 4.16.0 4.3
4.16.0 > 4.3

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


libtasn1 >= 4.3 provided by libtasn1-4.16.0-1.fc32 ?

2020-10-14 Thread Roman Mohr
Hi,

I am playing with RPM dependency resolution and I came across this in the
fc32 repos:

# dnf -y deplist gnutls | grep libtasn1
Last metadata expiration check: 2:04:09 ago on Wed 14 Oct 2020 09:47:12
CEST.
  dependency: libtasn1 >= 4.3
   provider: libtasn1-4.16.0-1.fc32.i686
   provider: libtasn1-4.16.0-1.fc32.x86_64

Could someone explain to me why version 4.16.0 satisfies 4.3? Does RPM
implicitly add `0.` to the comparison and it effectively compares `4.16.0`
with `0.4.3`?

Best Regards,
Roman
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Test-Announce] Fedora 33 Candidate RC-1.1 Available Now!

2020-10-14 Thread rawhide
According to the schedule [1], Fedora 33 Candidate RC-1.1 is now
available for testing. Please help us complete all the validation
testing! For more information on release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Test coverage information for the current release can be seen at:
https://www.happyassassin.net/testcase_stats/33

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.1_Security_Lab

All RC priority test cases for each of these test pages [2] must
pass in order to meet the RC Release Criteria [3].

Help is available on #fedora-qa on irc.freenode.net [4], or on the
test list [5].

Current Blocker and Freeze Exception bugs:
http://qa.fedoraproject.org/blockerbugs/current

[1] http://fedorapeople.org/groups/schedule/f-33/f-33-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
[3] https://fedoraproject.org/wiki/Fedora_33_RC_Release_Criteria
[4] irc://irc.freenode.net/fedora-qa
[5] https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora-Cloud-31-20201014.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

Passed openQA tests: 7/7 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


rlottie license change

2020-10-14 Thread Vitaly Zaitsev via devel

Hello all.

License changed from "LGPLv2+ and MIT and FTL and BSD and MPLv1.1" to 
"MIT and FTL and BSD and MPLv1.1".


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora 33: pcscd and xrdp issue

2020-10-14 Thread Marius Schwarz
Am 13.10.20 um 13:30 schrieb Nikos Mavrogiannopoulos:
> On Mon, Oct 12, 2020 at 3:55 PM Nikos Mavrogiannopoulos  
> wrote:
>
>>> Second thing to chance: just ask, if a usable hw is found. Asking 
>>> permission for an impossible task is the definition of madnes
>>>
>>> Back to your request to change the policy:
>>>
>>> I don't see any restrictions for remote access.  ( F33 has same as 
>>> https://pastebin.com/Mn8mzjVp )
>>>
>>> auth_admin
>>> auth_admin
>>> yes
>>>
>>> and I have no clue, besides setting those above to "no", which had the 
>>> hoped result(tested), how to change the file to ignore or skip the request 
>>> it generates via polkit when gnome starts.But I'm pretty sure, changing the 
>>> policy file, just makes thing unusable in case a smartcardread is really 
>>> available in the system.
>> Try setting the access daemon part from auth_admin to yes. Does it
>> address the issue?
> btw. Have you tried that on the systems that fail? Does it improve the
> usability?
>
>

As i already wrote, the same systems from last week that failed, did not
show the error this week. No clue why.

So, no , i did not test for "yes" as the testcase vanished :)

Best regards,
Marius
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora 33: pcscd and xrdp issue

2020-10-14 Thread Marius Schwarz
Am 13.10.20 um 13:17 schrieb Jakub Jelen:
> On 10/13/20 12:22 PM, Marius Schwarz wrote:
>>
>> captured with a brute force watch ps auxf >> log
>>
>> marius  5396  0.0  0.5 535000 10360 ?    Ssl  03:34   0:00  \_
>> /usr/libexec/gsd-smartcard
>>
>>
>> btw.  Boxen seems to simulate a reader:
>>
>> ccid_usb.c:659:OpenUSBByName() Found Vendor/Product: 08E6/4433 (Gemalto
>> Gemplus USB SmartCard Reader 433-Swap)
>
> Yeah, this is the virtual smart card driver, which is enabled if you
> configure your vm/remote-viewer to do so. Not sure if this is by default.
>
>> which changes the behaviour without altering the policy.
>>
>> I will repeat it with a real device.
>>
>> ** Surprise **
>>
>> Today, it does not show the requester at all.  Not on Boxen, not on the
>> real hw device I tested it last week with.
>>
>> But, the error message appears and several processes lite it up:
>>
>> 2x /usr/libexec/gsd-smartcard
>>
>> !!! 48x /usr/libexec/gstreamer-1.0/gst-plugin-scanner -l
>> /usr/bin/gjs-console
>>
>> The policy file was untouched, the image was the same as last week, the
>> device is the same as last week. Is there any OTA shenanigans at work?
>>
>> I mean, 2 devices tested on several days over the last week, and all
>> produce the same message and than, a week later, with an unalterted
>> ISOIMAGE it does no longer happen??? Something is very suspicious here!
>>
>
> Whether virtual smart card and reader is created depends on the VM
> configuration & remote-viewer configuration. Did you update/change
> that in your client system?
>
> Regards,

No, nothing changed, neither Boxens config ( silently updated by dnf is
possible), but the USB drive with Fedora 33 livedisc is unaltered and
the hw is the same as ever. So at least the HW test  should have
produced the bug, as it did a week before.

best regards,
Marius
___
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


[389-devel] Re: Mapping tree rework

2020-10-14 Thread Ludwig Krispenz

Hi,

you are right that it is possible to configure suffix hierarchies which 
are broken, but in my experience this wasn't an issue. people using sub 
suffixes did get it right.


So is there really a need to change something that is working for a long 
time ?



Regards,

Ludwig


On 14.10.20 08:12, William Brown wrote:

https://github.com/mreynolds389/389wiki/pull/48

This is a draft design, and probably of interest to thierry whom I discussed 
this with last night :)

Thanks!

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

___
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


Fedora-Cloud-32-20201014.0 compose check report

2020-10-14 Thread Fedora compose checker
No missing expected images.

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

Old soft failures (same test soft failed in Fedora-Cloud-32-20201013.0):

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

Passed openQA tests: 6/7 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-14 Thread Christopher Engelhard
On 13.10.20 12:14, Leon Fauster wrote:
> My recall was this
> 
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/DBAQB3V35TXPNUV4UKKHXUC52BENZJUQ/

OK, thanks, that clears that up. So I'll go ahead and retire the EPEL7
package. Maybe I can put an updated one on Copr instead.

Thanks to all of you, you helped tremendously.

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


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366



--- Comment #5 from Fedora Update System  ---
FEDORA-2020-5608fa4a78 has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-5608fa4a78


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366



--- Comment #4 from Fedora Update System  ---
FEDORA-2020-174525f97d has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-174525f97d


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-Pod-Usage-2.01-1.fc34



--- Comment #2 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


Re: nodejs-svgo dependencies

2020-10-14 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Oct 14, 2020 at 12:13:18AM -0700, Luya Tshimbalanga wrote:
> Hello team,
> 
> I took over the maintenance of nodejs-svgo needed for Inkscape.
> Unfortunately, two dependencies were retired due to lack of
> maintenance: sax and js-ymal. The attempt to rebuild those packages
> failed but the guideline for nodejs packages seems unclear with that
> line [1]:

I seems quite a few more deps have been retired...
npm(mocha)
npm(supports-color)
...

This will be a big task to support all that :(

> %prep
> %setup -q -n package
> %nodejs_fixdep foomodule
...
> + cd package

This directory is called 'js-yaml-3.14.0' in the new version:
 %prep
-%setup -q -n package
-%setup -q -T -D -a 1 -n package
-%setup -q -T -D -a 2 -n package
+%autosetup -n js-yaml-%{version}
+%setup -q -T -D -a 1 -n js-yaml-%{version}
+%setup -q -T -D -a 2 -n js-yaml-%{version}

Unfortunately the build fails later because 'fast-check' is missing...

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


[EPEL-devel] Re: [EPEL7] Celery stack update & Python 3 enablement

2020-10-14 Thread Frantisek Zatloukal
On Mon, Oct 5, 2020 at 7:09 PM Kevin Fenzi  wrote:

> How big are the changes between 4.2.2 and 4.3?
>

So, I finally got back to this, sorry for the late reply. After reading
through kombu 4.3 changelog [0], it seems the only truly breaking change is
in SQLAlchemy transport ( I can be wrong, of course) which would require
manual intervention in the database:

"Added an index to the Message table for the SQLAlchemy transport."


>From what I understand, using SQLAlchemy for celery/kombu is pretty niche
and documentation mentions and most applications around the world I was
able to find are using different backends for celery (RabbitMQ, Redis).

The plan will be to leave the upgraded stack for a long time in testing, I
was thinking about something like a month or two. I'll definitely send an
announcement once the stack is in testing repo and then (week or two)
before pushing it to epel stable.

[0] https://docs.celeryproject.org/projects/kombu/en/v4.3.0/changelog.html
___
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


[Bug 1888006] perl-DB_File-1.855 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888006



--- Comment #2 from Fedora Update System  ---
FEDORA-2020-506f68c17b has been submitted as an update to Fedora 33.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-506f68c17b


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888006] perl-DB_File-1.855 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888006



--- Comment #1 from Fedora Update System  ---
FEDORA-2020-9374ba063f has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-9374ba063f


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1888006] perl-DB_File-1.855 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888006

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-DB_File-1.855-1.fc34




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org


[Bug 1887366] perl-Pod-Usage-2.01 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1887366

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|jples...@redhat.com |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


nodejs-svgo dependencies

2020-10-14 Thread Luya Tshimbalanga

Hello team,

I took over the maintenance of nodejs-svgo needed for Inkscape. 
Unfortunately, two dependencies were retired due to lack of maintenance: 
sax and js-ymal. The attempt to rebuild those packages failed but the 
guideline for nodejs packages seems unclear with that line [1]:



%prep
%setup -q -n package
%nodejs_fixdep foomodule


Yet the resulting failure:

+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf package
+ /usr/bin/gzip -dc /builddir/build/SOURCES/js-yaml-3.14.0.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd package
/var/tmp/rpm-tmp.N0bzEw: line 39: cd: package: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.N0bzEw (%prep)

Those packages are hosted on COPR [2] and a help will be greatly 
appreciated to update the specs. Thanks in advance.



References

---

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/Node.js/

[2] https://copr.fedorainfracloud.org/coprs/luya/svgo/builds/

--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Schedule for Wednesday's FESCo Meeting (2020-10-14) + Proposal to Cancel

2020-10-14 Thread Clement Verna
On Tue, 13 Oct 2020 at 21:49, Neal Gompa  wrote:

> On Tue, Oct 13, 2020 at 3:01 PM Fabio Valentini 
> wrote:
> >
> > Since there are no open tickets that are tagged with "meeting" and no new
> > tickets are in need of synchronous discussion IMO, I propose to cancel
> > tomorrow's meeting, and would chair next week's meeting instead.
> >
> > The usual (empty) schedule and announcements are listed below.
> >
>
> I'm fine with that.
>
>
>
Works for me too


> --
> 真実はいつも一つ!/ 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
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[Bug 1888006] perl-DB_File-1.855 is available

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888006

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


[Bug 1888116] New: Please update to >=1.46, to build openssl 1.1.1d an newer

2020-10-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1888116

Bug ID: 1888116
   Summary: Please update to >=1.46, to build openssl 1.1.1d an
newer
   Product: Fedora EPEL
   Version: epel7
Status: NEW
 Component: perl-Text-Template
  Assignee: spo...@gmail.com
  Reporter: bugzi...@terrortux.de
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com,
perl-devel@lists.fedoraproject.org, spo...@gmail.com
  Target Milestone: ---
   Link ID: Github openssl/openssl/issues/11367
Classification: Fedora



Description of problem:
Version 1.45 seem to have an bug, which will stop to build openssl 1.1.1d and
newer.

Version-Release number of selected component (if applicable):
perl-Text-Template-1.45-12.el7

See the bug link for more information.


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


[389-devel] Mapping tree rework

2020-10-14 Thread William Brown
https://github.com/mreynolds389/389wiki/pull/48

This is a draft design, and probably of interest to thierry whom I discussed 
this with last night :) 

Thanks! 

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org


Re: 389ds making a local dns server for local web app.

2020-10-14 Thread Samuel Sieb

On 10/13/20 10:55 PM, rodents...@gmail.com wrote:

Btw sir, if I use freeipa. I won't be needing 389ds anymore?
I freeipa is made using 389ds. Am I correct?


Yes, freeipa uses 389ds as its backend database.
___
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