date:20210413

[Bug 1949332] New: perl-Crypt-OpenSSL-ECDSA-0.09 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949332
   Summary: perl-Crypt-OpenSSL-ECDSA-0.09 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Crypt-OpenSSL-ECDSA
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.09
Current version/release in rawhide: 0.08-18.fc34
URL: http://search.cpan.org/dist/Crypt-OpenSSL-ECDSA/

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


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

Re: New Fedora Developer Portal release

2021-04-13 Thread Pavel Valena

- Original Message -
> From: "Matthew Miller" 
> To: "Development discussions related to Fedora" 
> 
> Cc: developer-por...@lists.fedoraproject.org
> Sent: Tuesday, April 13, 2021 9:01:40 PM
> Subject: Re: New Fedora Developer Portal release
> 
> On Mon, Apr 12, 2021 at 08:08:29PM -0400, Pavel Valena wrote:
> > long overdue release has landed to: https://developer.fedoraproject.org/
> > Please check the updated website!
> 
> Nice!

Thanks!

> 
> > Detailed info is available on our ML [*].
> 
> I admit I didn't even know there was a mailing list! Would it be worth
> discussing merging that list with the regular docs mailing list?

Well, it's ok, almost noone knows :) ... It's a secret... joking, it simply 
does not get much traffic (statistics, and pre-release info mostly). All 
conversations are on github.com/developer-portal instead.

Merging does not seem like a good idea to me. I can post in CC everything I 
write into docs list if you want me to (but I don't, and won't read it!). I 
wouldn't like replacing it, as, strictly speaking, we don't do docs on 
Developer Portal!

   https://developer-portal.github.io/contributing/write-introduction.html

It's more aimed at existing developers who need a quick-start, simply "install 
this and that", and it doesn't even have to be in Fedora (f.e. build it from 
sources, or install from COPR), but the aim is instead on running it ON Fedora. 
I like to think of it like from developers, to developers [on Fedora]. Just a 
few must-read lines you need to get you started (or discover) the 
tool/tech/language... F.e. some content didn't even make it in, simply because 
it was too long (docs-like).

  https://fedoraproject.org/wiki/Websites/Developer#Target_Audience

I hope this clears it up, at least a bit.

> 
> > Any feedback is welcome!
> 
> Even if we want to leave DevAssistant pages for history, the link on
> https://developer.fedoraproject.org/tools.html should probably go.

You're right, thanks for a catch! I'm thinking of removing the content 
altogether though. Is anyone against?

> 
> On the other side of things, it'd be nice to add one for Toolbox.

Feel free to drop in an issue here: 
https://github.com/developer-portal/content/issues/new

> 
> --
> Matthew Miller
> 
> Fedora Project Leader

Regards,
-- 
Pavel Valena
Software Engineer, Red Hat
Brno, Czech Republic
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1949293] New: perl-Verilog-Perl-3.476 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949293
   Summary: perl-Verilog-Perl-3.476 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Verilog-Perl
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: chitl...@gmail.com, jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 3.476
Current version/release in rawhide: 3.474-2.fc34
URL: http://search.cpan.org/dist/Verilog-Perl/

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


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

[Bug 1949283] New: perl-ExtUtils-MakeMaker-7.62 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949283
   Summary: perl-ExtUtils-MakeMaker-7.62 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-ExtUtils-MakeMaker
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 7.62
Current version/release in rawhide: 7.60-1.fc35
URL: http://search.cpan.org/dist/ExtUtils-MakeMaker/

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


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

[Bug 1949270] Please build perl-Crypt-OpenSSL-X509 for epel8

2021-04-13 Thread bugzilla

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

Xavier Bachelot  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |DUPLICATE
   Doc Type|--- |If docs needed, set a value
Last Closed||2021-04-13 20:35:21



--- Comment #2 from Xavier Bachelot  ---


*** This bug has been marked as a duplicate of bug 1758483 ***


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

[Bug 1758483] perl-Crypt-OpenSSL-X509 for EL8

2021-04-13 Thread bugzilla

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

Xavier Bachelot  changed:

   What|Removed |Added

 CC||heinrich.mis...@univie.ac.a
   ||t



--- Comment #8 from Xavier Bachelot  ---
*** Bug 1949270 has been marked as a duplicate of this bug. ***


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

[Bug 1949278] perl-Net-Stomp-0.61 is available

2021-04-13 Thread bugzilla

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



--- Comment #1 from Upstream Release Monitoring 
 ---
An unexpected error occurred while creating the scratch build and has been
automatically reported. Sorry!


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

[Bug 1949278] New: perl-Net-Stomp-0.61 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949278
   Summary: perl-Net-Stomp-0.61 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Net-Stomp
  Keywords: FutureFeature, Triaged
  Assignee: lkund...@v3.sk
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: fi...@andresovi.net, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org, sce...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.61
Current version/release in rawhide: 0.60-5.fc34
URL: http://search.cpan.org/dist/Net-Stomp/

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


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

[Bug 1949270] Please build perl-Crypt-OpenSSL-X509 for epel8

2021-04-13 Thread bugzilla

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



--- Comment #1 from Heinrich Mislik  ---
Sorry, perl-Crypt-OpenSSL-X509 is already available. Bug can be closed.


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

[Bug 1949270] New: Please build perl-Crypt-OpenSSL-X509 for epel8

2021-04-13 Thread bugzilla

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

Bug ID: 1949270
   Summary: Please build perl-Crypt-OpenSSL-X509 for epel8
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-Crypt-OpenSSL-X509
  Assignee: wjhns...@hardakers.net
  Reporter: heinrich.mis...@univie.ac.at
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
wjhns...@hardakers.net, xav...@bachelot.org
  Target Milestone: ---
Classification: Fedora



Description of problem:

Please build perl-Crypt-OpenSSL-X509 for epel8


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

[Bug 1949266] New: Please build perl-Email-Valid for epel8

2021-04-13 Thread bugzilla

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

Bug ID: 1949266
   Summary: Please build perl-Email-Valid for epel8
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-Email-Valid
  Assignee: spo...@gmail.com
  Reporter: heinrich.mis...@univie.ac.at
QA Contact: extras...@fedoraproject.org
CC: jakub.jedel...@gmail.com,
perl-devel@lists.fedoraproject.org, spo...@gmail.com,
tjczep...@gmail.com
  Target Milestone: ---
Classification: Fedora



Description of problem:

Please build perl-Email-Valid for epel8


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

Re: Podman and docker compose

2021-04-13 Thread Daniel Walsh


Brent Baude, not on this list responds:


Sergio,

Unfortunately Podman can not do network links.  It is something we cannot
support in the API nor docker-compose.  Perhaps the use of the link in
the yaml could be reworked not need it?


On 4/12/21 01:15, Sergio Belkin wrote:



El dom, 11 abr 2021 a las 23:11, Gwyn Ciesla via devel 
(>) escribió:


Have you tried podman-compose? It's in the Fedora repos.


-- 
Gwyn Ciesla

she/her/hers

in your fear, seek only peace
in your fear, seek only love
-d. bowie



Sent from ProtonMail mobile



 Original Message 
On Apr 11, 2021, 7:34 PM, Sergio Belkin < seb...@gmail.com
> wrote:


Hi,
I'm playing around with podman and docker compose, so I've
read the post at
https://www.redhat.com/sysadmin/podman-docker-compose
.

The example with Gitea does not work, this the output:

sudo docker-compose up
descargas_elasticsearch_1 is up-to-date
Creating descargas_skydive-analyzer_1 ... error

ERROR: for descargas_skydive-analyzer_1  Cannot create
container for service skydive-analyzer: bad parameter: Link is
not supported

ERROR: for skydive-analyzer  Cannot create container for
service skydive-analyzer: bad parameter: Link is not supported
ERROR: Encountered errors while bringing up the project.

Am I doing something wrong?

This is the log:

abr 11 21:28:25 munster.belkin.home systemd[1]: Starting
Podman API Service...
abr 11 21:28:25 munster.belkin.home systemd[1]: Started Podman
API Service.
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info
msg="/usr/bin/podman filtering at
log level info"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Error
initializing configured
OCI runtime kata: no valid executable found for OCI runtime
kata: invalid argument"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI
network podman (typ
e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI
network descargas_d
efault (type=bridge) at /etc/cni/net.d/descargas_default.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI
network internet-mo
nitoring_back-tier (type=bridge) at
/etc/cni/net.d/internet-monitoring_back-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI
network internet-mo
nitoring_front-tier (type=bridge) at
/etc/cni/net.d/internet-monitoring_front-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Setting
parallel job count to
25"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="using systemd
socket activati
on to determine API endpoint"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="using API
endpoint: ''"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="API server
listening on \"/ru
n/podman/podman.sock\""
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(87f3d612-9e67-4975
-a52d-e34f8f177998) -- GET /version BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(f6beda6a-42c3-414c
-9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas_default
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(60f23924-261e-41fd
-9e14-459930ec3a0b) -- GET /v1.40/info BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(bd218869-1c22-4faf
-878e-f2bffeaec753) -- GET /v1.40/networks/descargas_default
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info

Re: Packaging new Compiz 0.9 version

2021-04-13 Thread Wolfgang Ulbrich

The problem is that compiz-reloaded (0.88) has several adjustments for MATE 
desktop, eg. gtk-theme reloading during theme switching, desktop shortcuts, 
special theme page in ccsm, etc. 
I don't want lost this for users of mate-compiz spin.
For privat reasons i don't have the time in the next 2 years to help with 
adjustments for MATE desktop in compiz-0.9.
So, i really prefer to leave existing compiz-reoaded like it is in fedora.
Feel free package a compat version of 0.9x.
Keep in mind that you have to rename package names, binaries and libs to avoid 
conflicts.
I recall that compiz was dropped from fedora after the first update to really 
bad first 0.9 versions. I brought it back to fedora after 1 year and users had 
a nearly bug free experience with compiz since fedora18 ;)

Well, you should ask Jaroslav for further information, he the current main 
maintainer of compiz.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Self Introduction: Roman Dementiev

2021-04-13 Thread Matthew Miller

On Tue, Apr 13, 2021 at 11:21:42AM +, Dementiev, Roman wrote:
> I am the main developer of PCM - Processor Counter Monitor
> (https://github.com/opcm/pcm) and would be happy to become a Fedora
> maintainer for PCM. Just submitted PCM srpm for review here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1949058

Cool -- welcome!

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: New Fedora Developer Portal release

2021-04-13 Thread Matthew Miller

On Mon, Apr 12, 2021 at 08:08:29PM -0400, Pavel Valena wrote:
> long overdue release has landed to: https://developer.fedoraproject.org/
> Please check the updated website!

Nice!

> Detailed info is available on our ML [*].

I admit I didn't even know there was a mailing list! Would it be worth
discussing merging that list with the regular docs mailing list?

> Any feedback is welcome!

Even if we want to leave DevAssistant pages for history, the link on 
https://developer.fedoraproject.org/tools.html should probably go.

On the other side of things, it'd be nice to add one for Toolbox.

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Outreachy 2021 applicant

2021-04-13 Thread KUNAL PRAKASH

Hello Lukas Brabec,

I was in quarantine for 12 days because I was tested COVID positive. Due to 
which I was unable to contribute to this project. But from now I want to 
contribute to the project consistently. 

I like to solve the issue which shows on console tab in developers tool.
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Outreachy 2021 applicant

2021-04-13 Thread Kunal Prakash

Hello Sent from Mail for Windows 10 ___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1949183] New: perl-PDF-API2-2.040 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949183
   Summary: perl-PDF-API2-2.040 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-PDF-API2
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 2.040
Current version/release in rawhide: 2.039-1.fc35
URL: http://search.cpan.org/dist/PDF-API2/

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


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

Fedora-34-20210413.n.0 compose check report

2021-04-13 Thread Fedora compose checker

Missing expected images:

Xfce raw-xz armhfp
Minimal raw-xz armhfp

Failed openQA tests: 15/189 (x86_64), 12/127 (aarch64)

New failures (same test not failed in Fedora-34-20210412.n.0):

ID: 854738  Test: x86_64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/854738
ID: 854864  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_master@uefi
URL: https://openqa.fedoraproject.org/tests/854864
ID: 854865  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_replica@uefi
URL: https://openqa.fedoraproject.org/tests/854865
ID: 854868  Test: aarch64 Server-dvd-iso 
server_role_deploy_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/854868
ID: 854873  Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi
URL: https://openqa.fedoraproject.org/tests/854873
ID: 854880  Test: aarch64 Server-dvd-iso 
server_freeipa_replication_client@uefi
URL: https://openqa.fedoraproject.org/tests/854880
ID: 854888  Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi
URL: https://openqa.fedoraproject.org/tests/854888
ID: 854892  Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi
URL: https://openqa.fedoraproject.org/tests/854892
ID: 854911  Test: aarch64 Workstation-raw_xz-raw.xz base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/854911
ID: 854968  Test: x86_64 universal support_server
URL: https://openqa.fedoraproject.org/tests/854968
ID: 854969  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/854969
ID: 854994  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/854994
ID: 855020  Test: aarch64 universal install_blivet_resize_lvm@uefi
URL: https://openqa.fedoraproject.org/tests/855020
ID: 855030  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/855030
ID: 855043  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/855043

Old failures (same test failed in Fedora-34-20210412.n.0):

ID: 854748  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/854748
ID: 854749  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/854749
ID: 854752  Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/854752
ID: 854761  Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/854761
ID: 854773  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/854773
ID: 854779  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/854779
ID: 854780  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/854780
ID: 854795  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/854795
ID: 854814  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/854814
ID: 854824  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/854824
ID: 854926  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/854926
ID: 855001  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/855001

Soft failed openQA tests: 4/189 (x86_64), 5/127 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-34-20210412.n.0):

ID: 854737  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/854737
ID: 854778  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/854778
ID: 854835  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/854835
ID: 854841  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/854841
ID: 854854  Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/854854
ID: 854879  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/854879
ID: 854894  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/854894
ID: 854916  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/854916
ID: 854975  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/854975

Passed openQA tests: 161/189 (x86_64), 110/127 (aarch64)

New passes (same test

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

2021-04-13 Thread tdawson

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2021-04-14 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@irc.freenode.net

The meeting will be about:
This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#meetingname EPEL
#topic Intros
#topic Old Business
#topic EPEL-7
#topic EPEL-8
#topic EPEL-9
#topic Openfloor
#endmeeting




Source: https://calendar.fedoraproject.org//meeting/9854/

___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Getting conman into EPEL8

2021-04-13 Thread Trey Dockendorf

On Tue, Apr 13, 2021 at 10:41 AM Dan Horák  wrote:

> >
> > I have Fedora accounts that I setup many years ago and honestly don't
> > recall if I was ever setup to be a packager for Fedora. If there is a way
> > to verify if I am setup as a packager I'd be happy to check, but most
> > likely I am not a packager in Fedora.
>
> that's a problem we can fix :-) New maintainers are always welcome.
>
>
> Dan
>
>
Would the best place to start be here?
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers. Any
pointers or additional information to get started on eventually becoming
EPEL8 conman maintainer is appreciated.

Thanks,
- Trey
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-IoT-34-20210413.0 compose check report

2021-04-13 Thread Fedora compose checker

No missing expected images.

Failed openQA tests: 3/15 (aarch64)

New failures (same test not failed in Fedora-IoT-34-20210409.1):

ID: 855174  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/855174
ID: 855182  Test: aarch64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi
URL: https://openqa.fedoraproject.org/tests/855182

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

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

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-34-20210409.1):

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

Passed openQA tests: 15/16 (x86_64), 12/15 (aarch64)

New passes (same test not passed in Fedora-IoT-34-20210409.1):

ID: 855162  Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/855162
ID: 855177  Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/855177
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Getting conman into EPEL8

2021-04-13 Thread Dan Horák

On Tue, 13 Apr 2021 10:31:42 -0400
Trey Dockendorf  wrote:

> On Tue, Apr 13, 2021 at 10:25 AM Dan Horák  wrote:
> 
> > Hi Trey,
> >
> > On Tue, 13 Apr 2021 14:15:08 -
> > treyd...@gmail.com wrote:
> >
> > > It appears like RHEL8 dropped conman RPMs but they do exist in Fedora
> > and appear to be receiving updates.  I found a wiki page that said to
> > contact the maintainers via email but I was unable to find the emails
> > associated with the maintainers so I opened a bugzilla but wasn't sure if I
> > did this bugzilla in appropriate place:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1947480
> > >
> > > I'd be happy to become the maintainer of conman for EPEL8 if that would
> > help get conman RPMs into EPEL8.  Any pointers on how to go about getting
> > conman into EPEL8 would be appreciated, in case the current approach I took
> > is incorrect.
> >
> > sorry for not replying earlier, but if you are willing to maintain
> > conman in EPEL, then the process should be fast. Are you already a
> > packager in Fedora?
> >
> >
> > Dan
> > ___
> >
> 
> I have Fedora accounts that I setup many years ago and honestly don't
> recall if I was ever setup to be a packager for Fedora. If there is a way
> to verify if I am setup as a packager I'd be happy to check, but most
> likely I am not a packager in Fedora.

that's a problem we can fix :-) New maintainers are always welcome.


Dan
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Package information on ELF objects (System-Wide Change proposal)

2021-04-13 Thread Colin Walters

On Mon, Apr 12, 2021, at 8:44 PM, Matthew Almond via devel wrote:
> 
> I think we should be careful to de-couple these two things. Just
> because $SOURCE_DATE_EPOCH is likely to affect a lot of binaries is not
> proof that all binaries will.

Agreed; it'd be interesting to gather some data here, particularly components 
with large binaries.

> I have just thought of an alternative proposition: for ELF objects (and
> ELF objects only): rpm could automatically, and systematically record
> the metadata in an xattr.

OSTree would be affected in the same way as your "RPM CoW" proposal by the 
approach of having it in the binary directly.  Unless we did this, because 
ostree is based on hardlinking which works on every filesystem, but shares an 
inode and hence the extended attributes are included in the ostree checksum.  
(There is some support for adding an additional "payload" i.e. content checksum 
in ostree but it adds another mapping and so we don't enable it by default).

But on reflink-capable filesystems in theory if this content is just in the ELF 
header we could skip it and reflink just the remainder which would be most of 
the binary.  (But, this would necessitate a strategy other than checksumming 
the whole binary of course, something more like rsync-style "rollsum" windows 
that we use for ostree static deltas, e.g.)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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

2021-04-13 Thread updates

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d0a9c2bf03   
chromium-89.0.4389.90-3.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-857a9f7853   
openssl11-1.1.1g-3.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-dda757d4a5   
libopenmpt-0.5.7-1.el7
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-93d78fa1a6   
perl-Net-CIDR-Lite-0.22-1.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f08dc6b4c1   
gnuchess-6.2.7-5.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-13ed778e19   
singularity-3.7.3-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3f9b6786f4   
clamav-0.103.2-1.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9daa9fc0b1   
seamonkey-2.53.7-3.el7


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

siege-4.0.8-1.el7
ssldump-1.4-1.el7

Details about builds:



 siege-4.0.8-1.el7 (FEDORA-EPEL-2021-4bd675d36f)
 HTTP regression testing and benchmarking utility

Update Information:

2021/03/17 Jeffrey Fulmer http://www.joedog.org/support/   * src/hash.c
Added explicit include of sys/types.h  * src/version.c  Version
increment: 4.0.8; Copyright 2021  2021/03/16 Zosecer https://github.com/zosecer
* src/parser.c   Added handling for null pointer detection

ChangeLog:

* Mon Apr 12 2021 Denis Fateyev  - 4.0.8-1
- Update to 4.0.8 (#1940056)
* Wed Jan 27 2021 Fedora Release Engineering  - 
4.0.7-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Wed Jul 29 2020 Fedora Release Engineering  - 
4.0.7-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Thu Jul 16 2020 Fabian Affolter  - 4.0.7-1
- Update to new upstream release 4.0.7 (rhbz#1855989)
* Mon Jul 13 2020 Fabian Affolter  - 4.0.6-1
- Update to new upstream release 4.0.6 (rhbz#1855989)

References:

  [ 1 ] Bug #1940056 - siege-4.0.8 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1940056




 ssldump-1.4-1.el7 (FEDORA-EPEL-2021-7c8753cd51)
 SSL/TLS network protocol analyzer

Update Information:

ssldump 1.4 ===   - IPv6 support added  - JA3 hashes added  - Various
bugs fixed

ChangeLog:

* Tue Apr 13 2021 Robert Scheck  1.4-1
- Upgrade to 1.4 (#1948756)

References:

  [ 1 ] Bug #1948756 - ssldump-1.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948756


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Getting conman into EPEL8

2021-04-13 Thread Trey Dockendorf

On Tue, Apr 13, 2021 at 10:25 AM Dan Horák  wrote:

> Hi Trey,
>
> On Tue, 13 Apr 2021 14:15:08 -
> treyd...@gmail.com wrote:
>
> > It appears like RHEL8 dropped conman RPMs but they do exist in Fedora
> and appear to be receiving updates.  I found a wiki page that said to
> contact the maintainers via email but I was unable to find the emails
> associated with the maintainers so I opened a bugzilla but wasn't sure if I
> did this bugzilla in appropriate place:
> https://bugzilla.redhat.com/show_bug.cgi?id=1947480
> >
> > I'd be happy to become the maintainer of conman for EPEL8 if that would
> help get conman RPMs into EPEL8.  Any pointers on how to go about getting
> conman into EPEL8 would be appreciated, in case the current approach I took
> is incorrect.
>
> sorry for not replying earlier, but if you are willing to maintain
> conman in EPEL, then the process should be fast. Are you already a
> packager in Fedora?
>
>
> Dan
> ___
>

I have Fedora accounts that I setup many years ago and honestly don't
recall if I was ever setup to be a packager for Fedora. If there is a way
to verify if I am setup as a packager I'd be happy to check, but most
likely I am not a packager in Fedora.

Thanks,
- Trey
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Getting conman into EPEL8

2021-04-13 Thread Qiyu Yan

在 2021-04-13星期二的 14:15 +，treyd...@gmail.com写道：
> It appears like RHEL8 dropped conman RPMs but they do exist in Fedora
> and appear to be receiving updates.  I found a wiki page that said to
> contact the maintainers via email but I was unable to find the emails
> associated with the maintainers so I opened a bugzilla but wasn't
You don't need to find the mail address, fedora already has mail alias 
package-ow...@fedoraproject.org or
package-maintain...@fedoraproject.org to contact maintainers.
> sure if I did this bugzilla in appropriate place:
> https://bugzilla.redhat.com/show_bug.cgi?id=1947480
> 
> I'd be happy to become the maintainer of conman for EPEL8 if that would
> help get conman RPMs into EPEL8.  Any pointers on how to go about
> getting conman into EPEL8 would be appreciated, in case the current
> approach I took is incorrect.
> 
> Thanks,
> - Trey
> ___
> 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-
> de...@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-
> infrastructure



signature.asc
Description: This is a digitally signed message part


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

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

2021-04-13 Thread updates

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b26bce013a   
chromium-89.0.4389.90-3.el8
  12  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-58127424cd   
perl-Net-Netmask-2.0001-1.el8
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4ceb7b7897   
libopenmpt-0.5.7-1.el8
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-125be1ea97   
perl-Net-CIDR-Lite-0.22-1.el8
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d8aad094e9   
singularity-3.7.3-1.el8
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-aa018d2e2a   
clamav-0.103.2-1.el8
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-781b228611   
seamonkey-2.53.7-3.el8


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

holland-1.2.4-2.el8
siege-4.0.8-1.el8
ssldump-1.4-1.el8

Details about builds:



 holland-1.2.4-2.el8 (FEDORA-EPEL-2021-0824198b8f)
 Pluggable Backup Framework

Update Information:

Corrected dependency issue in spec file.

ChangeLog:

* Mon Apr 12 2021 Sam P  - 1.2.4-2
- Updated spec file consistency issue.




 siege-4.0.8-1.el8 (FEDORA-EPEL-2021-8e6d2bcd99)
 HTTP regression testing and benchmarking utility

Update Information:

2021/03/17 Jeffrey Fulmer http://www.joedog.org/support/   * src/hash.c
Added explicit include of sys/types.h  * src/version.c  Version
increment: 4.0.8; Copyright 2021  2021/03/16 Zosecer https://github.com/zosecer
* src/parser.c   Added handling for null pointer detection

ChangeLog:

* Mon Apr 12 2021 Denis Fateyev  - 4.0.8-1
- Update to 4.0.8 (#1940056)
* Wed Jan 27 2021 Fedora Release Engineering  - 
4.0.7-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Wed Jul 29 2020 Fedora Release Engineering  - 
4.0.7-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Thu Jul 16 2020 Fabian Affolter  - 4.0.7-1
- Update to new upstream release 4.0.7 (rhbz#1855989)
* Mon Jul 13 2020 Fabian Affolter  - 4.0.6-1
- Update to new upstream release 4.0.6 (rhbz#1855989)

References:

  [ 1 ] Bug #1940056 - siege-4.0.8 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1940056




 ssldump-1.4-1.el8 (FEDORA-EPEL-2021-9478848524)
 SSL/TLS network protocol analyzer

Update Information:

ssldump 1.4 ===   - IPv6 support added  - JA3 hashes added  - Various
bugs fixed

ChangeLog:

* Tue Apr 13 2021 Robert Scheck  1.4-1
- Upgrade to 1.4 (#1948756)

References:

  [ 1 ] Bug #1948756 - ssldump-1.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1948756


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Re: Getting conman into EPEL8

2021-04-13 Thread Dan Horák

Hi Trey,

On Tue, 13 Apr 2021 14:15:08 -
treyd...@gmail.com wrote:

> It appears like RHEL8 dropped conman RPMs but they do exist in Fedora and 
> appear to be receiving updates.  I found a wiki page that said to contact the 
> maintainers via email but I was unable to find the emails associated with the 
> maintainers so I opened a bugzilla but wasn't sure if I did this bugzilla in 
> appropriate place: https://bugzilla.redhat.com/show_bug.cgi?id=1947480
> 
> I'd be happy to become the maintainer of conman for EPEL8 if that would help 
> get conman RPMs into EPEL8.  Any pointers on how to go about getting conman 
> into EPEL8 would be appreciated, in case the current approach I took is 
> incorrect.

sorry for not replying earlier, but if you are willing to maintain
conman in EPEL, then the process should be fast. Are you already a
packager in Fedora?


Dan
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[EPEL-devel] Getting conman into EPEL8

2021-04-13 Thread treydock

It appears like RHEL8 dropped conman RPMs but they do exist in Fedora and 
appear to be receiving updates.  I found a wiki page that said to contact the 
maintainers via email but I was unable to find the emails associated with the 
maintainers so I opened a bugzilla but wasn't sure if I did this bugzilla in 
appropriate place: https://bugzilla.redhat.com/show_bug.cgi?id=1947480

I'd be happy to become the maintainer of conman for EPEL8 if that would help 
get conman RPMs into EPEL8.  Any pointers on how to go about getting conman 
into EPEL8 would be appreciated, in case the current approach I took is 
incorrect.

Thanks,
- Trey
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Podman and docker compose

2021-04-13 Thread Daniel Walsh


On 4/11/21 22:10, Gwyn Ciesla via devel wrote:

Have you tried podman-compose? It's in the Fedora repos.

Podman APIV2 is supposed to support docker-compose, if this fails an 
Issue or Bugzilla should be opened.  Podman-compose is an alternative 
open source project for compose, which we are not sure is going to 
continue into the future.


--
Gwyn Ciesla
she/her/hers

in your fear, seek only peace
in your fear, seek only love
-d. bowie



Sent from ProtonMail mobile



 Original Message 
On Apr 11, 2021, 7:34 PM, Sergio Belkin < seb...@gmail.com> wrote:


Hi,
I'm playing around with podman and docker compose, so I've read
the post at https://www.redhat.com/sysadmin/podman-docker-compose
.

The example with Gitea does not work, this the output:

sudo docker-compose up
descargas_elasticsearch_1 is up-to-date
Creating descargas_skydive-analyzer_1 ... error

ERROR: for descargas_skydive-analyzer_1  Cannot create container
for service skydive-analyzer: bad parameter: Link is not supported

ERROR: for skydive-analyzer  Cannot create container for service
skydive-analyzer: bad parameter: Link is not supported
ERROR: Encountered errors while bringing up the project.

Am I doing something wrong?

This is the log:

abr 11 21:28:25 munster.belkin.home systemd[1]: Starting Podman
API Service...
abr 11 21:28:25 munster.belkin.home systemd[1]: Started Podman API
Service.
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="/usr/bin/podman
filtering at
log level info"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Error
initializing configured
OCI runtime kata: no valid executable found for OCI runtime kata:
invalid argument"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network
podman (typ
e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network
descargas_d
efault (type=bridge) at /etc/cni/net.d/descargas_default.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network
internet-mo
nitoring_back-tier (type=bridge) at
/etc/cni/net.d/internet-monitoring_back-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network
internet-mo
nitoring_front-tier (type=bridge) at
/etc/cni/net.d/internet-monitoring_front-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="Setting parallel
job count to
25"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="using systemd
socket activati
on to determine API endpoint"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="using API
endpoint: ''"
abr 11 21:28:25 munster.belkin.home podman[282]:
time="2021-04-11T21:28:25-03:00" level=info msg="API server
listening on \"/ru
n/podman/podman.sock\""
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(87f3d612-9e67-4975
-a52d-e34f8f177998) -- GET /version BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(f6beda6a-42c3-414c
-9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas_default BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(60f23924-261e-41fd
-9e14-459930ec3a0b) -- GET /v1.40/info BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(bd218869-1c22-4faf
-878e-f2bffeaec753) -- GET /v1.40/networks/descargas_default BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(25b1c622-5f7d-47c6
-8d81-cf0f0a497a2f) -- GET

/v1.40/containers/json?limit=-1=0=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp
ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]:
time="2021-04-11T21:28:28-03:00" level=info
msg="APIHandler(7af0b0a3-1e79-4f66
-8e4d-afe5f21a336d) -- GET

/v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp

Re: What do we think about always autoreconfing?

2021-04-13 Thread Florian Weimer

* Neal Gompa:

> As I said previously[1], I think doing autoconf upgrades would be less
> painful if we always did that.
>
> [1]: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZZG3SNLFS7BSXQ3JFJDOWUS3WWGTGLR2/

I think that's not actually true: If we do not build from source, it
doesn't matter if the compiler produces a working executable program
from the old sources.

Apart from the build-from-source principle, there are other advantages.
It may be easier to adopt new architectures and toolchain versions.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Test-Announce] Fedora-IoT 34 RC 20210413.0 nightly compose nominated for testing

2021-04-13 Thread rawhide

Announcing the creation of a new nightly release validation test event
for Fedora-IoT 34 RC 20210413.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/34iot

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-IoT_34_RC_20210413.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_34_RC_20210413.0_General

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

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

2021-04-13 Thread Fedora compose checker

No missing expected images.

Compose PASSES proposed Rawhide gating check!
All required tests passed

Failed openQA tests: 11/189 (x86_64), 9/127 (aarch64)

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

ID: 854504  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/854504
ID: 854510  Test: x86_64 Silverblue-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/854510
ID: 854586  Test: aarch64 Workstation-raw_xz-raw.xz 
desktop_update_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/854586
ID: 854618  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/854618
ID: 854646  Test: x86_64 universal install_btrfs
URL: https://openqa.fedoraproject.org/tests/854646

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

ID: 854447  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/854447
ID: 854495  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/854495
ID: 854565  Test: aarch64 Server-dvd-iso modularity_tests@uefi
URL: https://openqa.fedoraproject.org/tests/854565
ID: 854656  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/854656
ID: 854663  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/854663
ID: 854678  Test: x86_64 universal upgrade_2_realmd_client
URL: https://openqa.fedoraproject.org/tests/854678
ID: 854679  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/854679
ID: 854682  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/854682
ID: 854694  Test: aarch64 universal install_european_language@uefi
URL: https://openqa.fedoraproject.org/tests/854694
ID: 854711  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/854711
ID: 854712  Test: aarch64 universal upgrade_minimal_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/854712
ID: 854714  Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/854714
ID: 854724  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/854724
ID: 854725  Test: aarch64 universal upgrade_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/854725
ID: 854727  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/854727

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

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

ID: 854410  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/854410
ID: 854411  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/854411
ID: 854418  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/854418
ID: 854459  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/854459
ID: 854516  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/854516
ID: 854522  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/854522
ID: 854530  Test: aarch64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/854530
ID: 854535  Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/854535
ID: 854560  Test: aarch64 Server-dvd-iso install_vnc_client@uefi
URL: https://openqa.fedoraproject.org/tests/854560
ID: 854575  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/854575
ID: 854597  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/854597
ID: 854609  Test: x86_64 universal install_kickstart_hdd
URL: https://openqa.fedoraproject.org/tests/854609
ID: 854619  Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/854619
ID: 854626  Test: x86_64 universal install_kickstart_user_creation
URL: https://openqa.fedoraproject.org/tests/854626
ID: 854648  Test: x86_64 universal install_kickstart_firewall_disabled
URL: https://openqa.fedoraproject.org/tests/854648
ID: 854664  Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/854664
ID: 854674  Test: x86_64 universal install_kickstart_nfs
URL: https://openqa.fedoraproject.org/tests/854674
ID: 854681  Test: aarch64

Re: What do we think about always autoreconfing?

2021-04-13 Thread Sérgio Basto

On Tue, 2021-04-13 at 08:33 -0400, Neal Gompa wrote:
> On Tue, Apr 13, 2021 at 8:24 AM Florian Weimer 
> wrote:
> > * Richard W. M. Jones:
> > 
> > > Hijacking this thread originally about
> > > https://fedoraproject.org/wiki/Changes/Autoconf_271
> > > 
> > > What is the current thinking in Fedora about always running
> > > "autoreconf -i" during builds that use autotools?
> > 
> > I would prefer to do it because it aligns with Fedora's goal to
> > build
> > from sources.  But I expect it to be quite a bit of work.  Maybe
> > not for
> > each package on its own, but certainly across the entire
> > distribution.
> > 
> 
> I'd advocate for that as well. It brings us in-line with other build
> scripts and guarantees that everything actually works.

I'd advocate for that also, just add that sometimes we may have
bootstrap or autogen.sh script in upstream source and IMO we should use
it. 

For example: 
https://github.com/twaugh/patchutils/blob/master/bootstrap

https://github.com/sergiomb2/ufraw/blob/master/autogen.sh


> As I said previously[1], I think doing autoconf upgrades would be
> less
> painful if we always did that.
> 
> [1]: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZZG3SNLFS7BSXQ3JFJDOWUS3WWGTGLR2/
> 
> 
> 
> -- 
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Podman and docker compose

2021-04-13 Thread Daniel Walsh


Brent PTAL


On 4/11/21 20:34, Sergio Belkin wrote:

Hi,
I'm playing around with podman and docker compose, so I've read the 
post at https://www.redhat.com/sysadmin/podman-docker-compose 
.


The example with Gitea does not work, this the output:

sudo docker-compose up
descargas_elasticsearch_1 is up-to-date
Creating descargas_skydive-analyzer_1 ... error

ERROR: for descargas_skydive-analyzer_1  Cannot create container for 
service skydive-analyzer: bad parameter: Link is not supported


ERROR: for skydive-analyzer  Cannot create container for service 
skydive-analyzer: bad parameter: Link is not supported

ERROR: Encountered errors while bringing up the project.

Am I doing something wrong?

This is the log:

abr 11 21:28:25 munster.belkin.home systemd[1]: Starting Podman API 
Service...
abr 11 21:28:25 munster.belkin.home systemd[1]: Started Podman API 
Service.
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="/usr/bin/podman 
filtering at

log level info"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Error initializing 
configured
OCI runtime kata: no valid executable found for OCI runtime kata: 
invalid argument"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network 
podman (typ

e=bridge) at /etc/cni/net.d/87-podman-bridge.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network 
descargas_d

efault (type=bridge) at /etc/cni/net.d/descargas_default.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network 
internet-mo
nitoring_back-tier (type=bridge) at 
/etc/cni/net.d/internet-monitoring_back-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Found CNI network 
internet-mo
nitoring_front-tier (type=bridge) at 
/etc/cni/net.d/internet-monitoring_front-tier.conflist"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="Setting parallel job 
count to

25"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="using systemd socket 
activati

on to determine API endpoint"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="using API endpoint: ''"
abr 11 21:28:25 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:25-03:00" level=info msg="API server listening 
on \"/ru

n/podman/podman.sock\""
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(87f3d612-9e67-4975

-a52d-e34f8f177998) -- GET /version BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(f6beda6a-42c3-414c

-9d8c-0314e00c86d7) -- GET /v1.40/networks/descargas_default BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(60f23924-261e-41fd

-9e14-459930ec3a0b) -- GET /v1.40/info BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(bd218869-1c22-4faf

-878e-f2bffeaec753) -- GET /v1.40/networks/descargas_default BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(25b1c622-5f7d-47c6
-8d81-cf0f0a497a2f) -- GET 
/v1.40/containers/json?limit=-1=0=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp
ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D 
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(7af0b0a3-1e79-4f66
-8e4d-afe5f21a336d) -- GET 
/v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp
ose.project%3Ddescargas%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D 
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(ad9f4acb-47ac-4699
-aa65-e542a59912e9) -- GET 
/v1.40/containers/c519bbe7f21e7c01729d62237b819b84b3bf364784a115fa536ad45153224ffc/json 
BEGIN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(000638a6-ac24-403b
-81d2-a41f4ec0cde0) -- GET 
/v1.40/containers/json?limit=-1=1=0_cmd=0=%7B%22label%22%3A+%5B%22com.docker.comp
ose.project%3Ddescargas%22%2C+%22com.docker.compose.service%3Delasticsearch%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D 
BEG

IN"
abr 11 21:28:28 munster.belkin.home podman[282]: 
time="2021-04-11T21:28:28-03:00" level=info 
msg="APIHandler(2f67caff-4f06-496f
-8abe-f7c5c698d8a9) -- GET

Fedora 34 compose report: 20210413.n.0 changes

2021-04-13 Thread Fedora Rawhide Report

OLD: Fedora-34-20210412.n.0
NEW: Fedora-34-20210413.n.0

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

Size of added packages:  128.09 KiB
Size of dropped packages:3.05 MiB
Size of upgraded packages:   721.31 MiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: rust-cryptoki-0.1.1-1.fc34
Summary: Rust-native wrapper around the PKCS #11 API
RPMs:rust-cryptoki+default-devel rust-cryptoki+generate-bindings-devel 
rust-cryptoki+psa-crypto-conversions-devel rust-cryptoki+psa-crypto-devel 
rust-cryptoki-devel
Size:68.60 KiB

Package: rust-cryptoki-sys-0.1.1-2.fc34
Summary: FFI wrapper around the PKCS #11 API
RPMs:rust-cryptoki-sys+bindgen-devel rust-cryptoki-sys+default-devel 
rust-cryptoki-sys+generate-bindings-devel rust-cryptoki-sys-devel
Size:59.49 KiB


= DROPPED PACKAGES =
Package: gr-fcdproplus-3.8.0-3.20200807git06069c2e.fc34
Summary: GNURadio support for FUNcube Dongle Pro+
RPMs:gr-fcdproplus gr-fcdproplus-devel gr-fcdproplus-doc
Size:3.05 MiB


= UPGRADED PACKAGES =
Package:  clevis-pin-tpm2-0.3.0-1.fc34
Old package:  clevis-pin-tpm2-0.2.0-1.fc34
Summary:  Clevis PIN for unlocking with TPM2 supporting Authorized Policies
RPMs: clevis-pin-tpm2
Size: 2.07 MiB
Size change:  73.09 KiB
Changelog:
  * Tue Jan 26 2021 Fedora Release Engineering  - 
0.2.0-2
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild

  * Tue Apr 06 2021 Peter Robinson  - 0.3.0-1
  - Update to 0.3.0


Package:  dbus-parsec-0.3.1-3.fc34
Old package:  dbus-parsec-0.3.1-2.fc34
Summary:  DBus PARSEC interface
RPMs: dbus-parsec
Size: 1.99 MiB
Size change:  445.65 KiB
Changelog:
  * Mon Mar 22 2021 Peter Robinson  - 0.3.1-3
  - Rebuild for new parsec-client


Package:  deepin-session-ui-5.3.35-2.fc34
Old package:  deepin-session-ui-5.3.35-1.fc34
Summary:  Deepin desktop-environment - Session UI module
RPMs: deepin-session-ui
Size: 3.42 MiB
Size change:  2.90 KiB
Changelog:
  * Tue Apr 06 2021 Robin Lee  - 5.3.35-2
  - Requires deepin-session-shell


Package:  dracut-053-2.fc34
Old package:  dracut-053-1.fc34
Summary:  Initramfs generator using udev
RPMs: dracut dracut-caps dracut-config-generic dracut-config-rescue 
dracut-live dracut-network dracut-squash dracut-tools
Size: 2.27 MiB
Size change:  5.47 KiB
Changelog:
  * Thu Apr 08 2021 Adam Williamson  - 053-2
  - Backport upstream change reported to fix boot on some encrypted LVM setups 
(#1946074)


Package:  fedora-obsolete-packages-34-20
Old package:  fedora-obsolete-packages-34-19
Summary:  A package to obsolete retired packages
RPMs: fedora-obsolete-packages
Size: 35.62 KiB
Size change:  368 B
Changelog:
  * Wed Apr 07 2021 Miro Hron??ok  - 34-20
  - Update the list of obsoleted Python 3.8 packages (#1856098)


Package:  glib2-2.68.1-1.fc34
Old package:  glib2-2.68.0-2.fc34
Summary:  A library of handy utility functions
RPMs: glib2 glib2-devel glib2-doc glib2-static glib2-tests
Size: 39.18 MiB
Size change:  -85.93 KiB
Changelog:
  * Thu Apr 08 2021 Kalev Lember  - 2.68.1-1
  - Update to 2.68.1


Package:  kde-settings-34.2-1.fc34
Old package:  kde-settings-34.1-1.fc34
Summary:  Config files for kde
RPMs: kde-settings kde-settings-plasma kde-settings-pulseaudio 
qt-settings
Size: 65.87 KiB
Size change:  462 B
Changelog:
  * Thu Apr 08 2021 Rex Dieter  - 34.2-1
  - -plasma: explicitly use BreezeTwilight lookandfeel elements (#1947446)


Package:  kernel-5.11.12-300.fc34
Old package:  kernel-5.11.11-300.fc34
Summary:  The Linux kernel
RPMs: kernel kernel-core kernel-debug kernel-debug-core 
kernel-debug-devel kernel-debug-modules kernel-debug-modules-extra 
kernel-debug-modules-internal kernel-devel kernel-lpae kernel-lpae-core 
kernel-lpae-devel kernel-lpae-modules kernel-lpae-modules-extra 
kernel-lpae-modules-internal kernel-modules kernel-modules-extra 
kernel-modules-internal
Size: 493.23 MiB
Size change:  48.57 KiB
Changelog:
  * Wed Apr 07 2021 Justin M. Forbes  [5.11.12-14]
  - Backport of SOF audio hang fix for X1 Carbon 9 (Mark Pearson)
  - drm/amdgpu: check alignment on CPU page for bo map (X??? Ruoyao)
  - drm/amdgpu: Set a suitable dev_info.gart_page_size (Huacai Chen)
  - drm/amdgpu: fix offset calculation in amdgpu_vm_bo_clear_mappings() (Nirmoy 
Das)
  - Set CONFIG_XEN_MEMORY_HOTPLUG_LIMIT as required by 5.11.11 (Justin M. 
Forbes)


Package:  parsec-0.7.0-2.fc34
Old package:  parsec-0.6.0-1.fc34
Summary:  The PARSEC daemon
RPMs: parsec
Size: 3.59 MiB
Size change:  177.82 KiB
Changelog:
  * Sun Jan 24 2021 Peter Robinson

Re: What do we think about always autoreconfing?

2021-04-13 Thread Richard W.M. Jones


On Tue, Apr 13, 2021 at 02:24:20PM +0200, Florian Weimer wrote:
> * Richard W. M. Jones:
> 
> > Hijacking this thread originally about
> > https://fedoraproject.org/wiki/Changes/Autoconf_271
> >
> > What is the current thinking in Fedora about always running
> > "autoreconf -i" during builds that use autotools?
> 
> I would prefer to do it because it aligns with Fedora's goal to build
> from sources.  But I expect it to be quite a bit of work.  Maybe not for
> each package on its own, but certainly across the entire distribution.

(I believe ...) For Debian it's a recommendation rather than a
requirement.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: What do we think about always autoreconfing?

2021-04-13 Thread Neal Gompa

On Tue, Apr 13, 2021 at 8:24 AM Florian Weimer  wrote:
>
> * Richard W. M. Jones:
>
> > Hijacking this thread originally about
> > https://fedoraproject.org/wiki/Changes/Autoconf_271
> >
> > What is the current thinking in Fedora about always running
> > "autoreconf -i" during builds that use autotools?
>
> I would prefer to do it because it aligns with Fedora's goal to build
> from sources.  But I expect it to be quite a bit of work.  Maybe not for
> each package on its own, but certainly across the entire distribution.
>

I'd advocate for that as well. It brings us in-line with other build
scripts and guarantees that everything actually works.

As I said previously[1], I think doing autoconf upgrades would be less
painful if we always did that.

[1]: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ZZG3SNLFS7BSXQ3JFJDOWUS3WWGTGLR2/



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Package information on ELF objects (System-Wide Change proposal)

2021-04-13 Thread Neal Gompa

On Tue, Apr 13, 2021 at 8:09 AM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> On Mon, Apr 12, 2021 at 10:57:30PM +0200, Lennart Poettering wrote:
> > On Mo, 12.04.21 16:14, David Malcolm (dmalc...@redhat.com) wrote:
> >
> > > So I want to push back on the idea that a single package can be
> > > associated with a coredump, or be the one responsible for the crash:
> > > any or all of the ELF objects linked into the process could be at
> > > fault.
> >
> > The example in the feature page shows how we handle this: you'll see
> > the packaging metadata of all involved ELF objects in coredumpctl's
> > output. i.e. we should be nicely covered on this, and we are fully
> > aware that the "main" ELF objects is the culprit of crashes only in a
> > fraction of cases.
>
> This is true.
>
> OTOH, this new metadata doesn't really change the situation here.
> Before, we already had build-ids for all the packages "involved" in
> the stack trace. And our processing tools already could do the
> conversion to package nevras. (They have to have network access to
> create a report.) The only thing that changes is *how* this conversion
> happens, but for online reports such conversion was always possible.
>

The new metadata guarantees that the ELF data churns, though. For
example, if I bump the Release in a spec file for something unrelated
to the build, all the ELF blobs change. The current state means that
this is deduplicated in RPM CoW and a very cheap upgrade, since the
binaries weren't all touched.



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[CANCELLED] Schedule for Tuesdays's FESCo Meeting (2021-04-13)

2021-04-13 Thread Zbigniew Jędrzejewski-Szmek

We would have the meeting today, but there are no tickets on the
agenda. The meeting is cancelled. The next meeting is scheduled a
week from now.

I'll chair the next meeting.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: What do we think about always autoreconfing?

2021-04-13 Thread Florian Weimer

* Richard W. M. Jones:

> Hijacking this thread originally about
> https://fedoraproject.org/wiki/Changes/Autoconf_271
>
> What is the current thinking in Fedora about always running
> "autoreconf -i" during builds that use autotools?

I would prefer to do it because it aligns with Fedora's goal to build
from sources.  But I expect it to be quite a bit of work.  Maybe not for
each package on its own, but certainly across the entire distribution.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F35 Change: Package information on ELF objects (System-Wide Change proposal)

2021-04-13 Thread Zbigniew Jędrzejewski-Szmek

On Mon, Apr 12, 2021 at 10:57:30PM +0200, Lennart Poettering wrote:
> On Mo, 12.04.21 16:14, David Malcolm (dmalc...@redhat.com) wrote:
> 
> > So I want to push back on the idea that a single package can be
> > associated with a coredump, or be the one responsible for the crash:
> > any or all of the ELF objects linked into the process could be at
> > fault.
> 
> The example in the feature page shows how we handle this: you'll see
> the packaging metadata of all involved ELF objects in coredumpctl's
> output. i.e. we should be nicely covered on this, and we are fully
> aware that the "main" ELF objects is the culprit of crashes only in a
> fraction of cases.

This is true.

OTOH, this new metadata doesn't really change the situation here.
Before, we already had build-ids for all the packages "involved" in
the stack trace. And our processing tools already could do the
conversion to package nevras. (They have to have network access to
create a report.) The only thing that changes is *how* this conversion
happens, but for online reports such conversion was always possible.

That said, it *is* strange that abrt prints just one package nevra
in bugzilla reports [1].

Zbyszek

[1] completely arbitrary example I happened to have open in a tab:
https://bugzilla.redhat.com/show_bug.cgi?id=1895937
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1949065] New: perl-Mojolicious-9.17 is available

2021-04-13 Thread bugzilla

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

Bug ID: 1949065
   Summary: perl-Mojolicious-9.17 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Mojolicious
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr,
perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com, yan...@declera.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 9.17
Current version/release in rawhide: 9.16-1.fc35
URL: https://metacpan.org/release/Mojolicious

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/5966/


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

Re: What do we think about always autoreconfing? (was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))

2021-04-13 Thread Tomasz Kłoczko

On Tue, 13 Apr 2021 at 11:27, Richard W.M. Jones  wrote:

> Hijacking this thread originally about
> https://fedoraproject.org/wiki/Changes/Autoconf_271
>
> What is the current thinking in Fedora about always running
> "autoreconf -i" during builds that use autotools?
>

1) "autoreconf -i" is not enough. It needs to be executed "autoreconf -fi"
and to have proper visibility reconfigure issues should be
executed "autoreconf -fiv"

2) Looks like still no one performed experiment of rebuilding all
existing packages with %configure macro in spec by execute:

$ for i in *.src.rpm; do rpmbuild --rebuild -D "_configure 'autoreconf
-fiv; configure'" $i; done

To check which Fedora packages are failing in the build environment with
autoconf 2.71.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Self Introduction: Roman Dementiev

2021-04-13 Thread Dementiev, Roman

Hi,

I am the main developer of PCM - Processor Counter Monitor 
(https://github.com/opcm/pcm) and would be happy to become a Fedora maintainer 
for PCM. Just submitted PCM srpm for review here: 
https://bugzilla.redhat.com/show_bug.cgi?id=1949058

Thanks,
Roman

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de 
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: What do we think about always autoreconfing? (was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))

2021-04-13 Thread Ralf Corsepius


On 4/13/21 12:26 PM, Richard W.M. Jones wrote:

Hijacking this thread originally about
https://fedoraproject.org/wiki/Changes/Autoconf_271

What is the current thinking in Fedora about always running
"autoreconf -i" during builds that use autotools?


IMO, it's naive wishful thinking, applicable to trivial packages.

Most non-trivial packages require specific versions.

Also, in general, it's not advisable to regenerate auto*tools generated 
sources at all. I am aware, this thought has become unpopular, because 
the autotools have been mostly "dormant" in recent years, so people are 
not used to face such problems, anymore.



In Debian it's been recommended for a long time:
https://wiki.debian.org/Autoreconf


Well, ... Debian's mistake.


It also could fail - I noticed that autoconf
2.71 has several incompatibilities with the most widely used autoconf
(2.69).

This is only the tip of the proverbial "iceberg".

autoconf > 2.69 is pretty imcompatible and bugged.

Ralf

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora rawhide compose report: 20210413.n.0 changes

2021-04-13 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20210412.n.0
NEW: Fedora-Rawhide-20210413.n.0

= SUMMARY =
Added images:5
Dropped images:  0
Added packages:  2
Dropped packages:7
Upgraded packages:   100
Downgraded packages: 0

Size of added packages:  12.67 MiB
Size of dropped packages:29.84 MiB
Size of upgraded packages:   7.41 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Xfce raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Xfce-Rawhide-20210413.n.0.armhfp.raw.xz
Image: Workstation raw-xz armhfp
Path: 
Workstation/armhfp/images/Fedora-Workstation-Rawhide-20210413.n.0.armhfp.raw.xz
Image: Minimal raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Minimal-Rawhide-20210413.n.0.armhfp.raw.xz
Image: Design_suite live x86_64
Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20210413.n.0.iso
Image: Server raw-xz armhfp
Path: Server/armhfp/images/Fedora-Server-Rawhide-20210413.n.0.armhfp.raw.xz

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: libucl-0.8.1-7.fc35
Summary: Universal configuration library parser
RPMs:libucl libucl-devel python3-libucl
Size:703.23 KiB

Package: weldr-client-35.1-1.fc35
Summary: Command line utility to control osbuild-composer
RPMs:weldr-client
Size:11.98 MiB


= DROPPED PACKAGES =
Package: CuraEngine-lulzbot-1:3.6.21-8.fc34
Summary: Engine for processing 3D models into G-code instructions for 3D 
printers
RPMs:CuraEngine-lulzbot
Size:3.53 MiB

Package: cura-lulzbot-1:3.6.22-3.fc34
Summary: 3D printer control software
RPMs:cura-lulzbot
Size:17.77 MiB

Package: gr-fcdproplus-3.8.0-3.20200807git06069c2e.fc34
Summary: GNURadio support for FUNcube Dongle Pro+
RPMs:gr-fcdproplus gr-fcdproplus-devel gr-fcdproplus-doc
Size:3.05 MiB

Package: libarcus-lulzbot-3.6.21-11.fc35
Summary: Communication library between Cura components, Lulzbot fork
RPMs:libarcus-lulzbot libarcus-lulzbot-devel python3-arcus-lulzbot
Size:513.35 KiB

Package: lulzbot-marlin-firmware-1:1.1.9.34-13.fc34
Summary: Marlin firmware files for the Lulzbot family of 3D printers
RPMs:lulzbot-marlin-firmware lulzbot-marlin-firmware-bio 
lulzbot-marlin-firmware-pro
Size:3.71 MiB

Package: phpwapmail-0.9.5-5.fc34
Summary: WAP-based e-mail client
RPMs:phpwapmail
Size:30.03 KiB

Package: python-uranium-lulzbot-3.6.21-5.fc34
Summary: A Python framework for building desktop applications (Lulzbot fork)
RPMs:python-uranium-lulzbot-doc python3-uranium-lulzbot
Size:1.25 MiB


= UPGRADED PACKAGES =
Package:  NetworkManager-1:1.32.0-0.1.fc35
Old package:  NetworkManager-1:1.30.0-1.fc35
Summary:  Network connection manager and user applications
RPMs: NetworkManager NetworkManager-adsl NetworkManager-bluetooth 
NetworkManager-cloud-setup NetworkManager-config-connectivity-fedora 
NetworkManager-config-server NetworkManager-dispatcher-routing-rules 
NetworkManager-libnm NetworkManager-libnm-devel NetworkManager-ovs 
NetworkManager-ppp NetworkManager-team NetworkManager-tui NetworkManager-wifi 
NetworkManager-wwan
Size: 29.23 MiB
Size change:  153.39 KiB
Changelog:
  * Fri Mar 12 2021 Beniamino Galvani  - 1:1.30.2-1
  - update to 1.30.2 release

  * Thu Mar 25 2021 Beniamino Galvani  - 1:1.32.0-0.1
  - update to an early 1.32 snapshot (1.31.2)


Package:  anaconda-35.12-1.fc35
Old package:  anaconda-35.11-1.fc35
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 21.96 MiB
Size change:  -342.32 KiB
Changelog:
  * Mon Apr 12 2021 Martin Kolman  - 35.12-1
  - Remove patches to avoid forcing inst. prefix on RHEL 9 (jkonecny)
  - Allow to exclude the kernel-lpae package (vponcova)
  - Remove the pwpolicy kickstart command (vponcova)
  - Do not generate dracut arguments multiple times for some storage devices
(rvykydal)
  - Run RHEL8 contributor tests on kstest runners (vslavik)
  - Add support for comps to the DNF manager (vponcova)
  - Add DBus structures for comps data (vponcova)
  - Add the is_cdn_registration_required function (vponcova)
  - Use the default_environment property in UI (vponcova)
  - Add the default_environment property to the DNF manager (vponcova)
  - Create the substitute method (vponcova)
  - Rename tests-owners to just tests (jkonecny)
  - Use GitHub environment gating for kstests workflow (jkonecny)
  - Replace our Fedora owners check by GH environments for our workflows
(jkonecny)
  - Fix a small typo in common bugs (jkonecny)


Package:  apr-1.7.0-9.fc35
Old package:  apr-1.7.0-8.fc34
Summary:  Apache Portable Runtime library
RPMs: apr apr-devel
Size: 1.83 MiB
Size change:  469 B
Changelog:
  * Mon Apr 12 2021 Lubos Uhliarik  - 1.7.0-9
  - Resolves

What do we think about always autoreconfing? (was: Re: Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal))

2021-04-13 Thread Richard W.M. Jones

Hijacking this thread originally about
https://fedoraproject.org/wiki/Changes/Autoconf_271

What is the current thinking in Fedora about always running
"autoreconf -i" during builds that use autotools?

In Debian it's been recommended for a long time:
https://wiki.debian.org/Autoreconf

I maintain a few packages where I attempt to toggle autoreconfing
based on whether patches touch build files.  If a downstream patch is
applied which touches any of configure.ac, Makefile.am, or several
other files, then the build will attempt to run autoconf/automake and
usually fail.  These packages have:

  # If there are patches which touch autotools files, set this to 1.
  %global patches_touch_autotools %{nil}

  %if 0%{patches_touch_autotools}
  BuildRequires:  autoconf, automake, libtool
  %endif

  %prep
  ...
  %if 0%{patches_touch_autotools}
  autoreconf -i
  %endif

This is a kind of optimal solution, but also hard to get right - I
often find myself forgetting to set the %global correctly after
applying or removing downstream patches.

The cons of always autoreconfing are that it slows down builds,
sometimes considerably.  It also could fail - I noticed that autoconf
2.71 has several incompatibilities with the most widely used autoconf
(2.69).

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Heads up: vala 0.52.x with soname bump coming to rawhide

2021-04-13 Thread Kalev Lember



I'm about to start building vala 0.52.2 in rawhide that has a soname 
bump compared to vala 0.48.x that we have in rawhide right now.


I'll take care of the rebuilds in a side tag and merge when everything 
is sorted out.


--
Kalev
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-32-20210413.0 compose check report

2021-04-13 Thread Fedora compose checker

No missing expected images.

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

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

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

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

[Test-Announce] Fedora 34 Virtualization Test Day 2021-04-13

2021-04-13 Thread Sumantro Mukherjee

Hey All,

We are going to test all forms of virtualization possible in Fedora.
The test day [0] will focus on testing Fedora or your favorite distro
inside a bare-metal implementation of Fedora running Boxes, KVM,
VirtualBox, and whatever you have.
The general features of installing the OS and working with it are
outlined in the test cases which you will find on the results page
[1].

[0] http://fedoraproject.org/wiki/Test_Day:2021-04-13_Virtualization
[1] https://testdays.fedoraproject.org/events/109

Thanks

-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-33-20210413.0 compose check report

2021-04-13 Thread Fedora compose checker

No missing expected images.

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

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

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

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

Re: Need feedback on ocaml-atd review request

2021-04-13 Thread Richard W.M. Jones

On Thu, Apr 08, 2021 at 03:02:30PM -0700, Michel Alexandre Salim wrote:
> This is a single project that ends up generating several related OPAM
> packages. The automatic requires/provides seem to identify the modules
> it provides correctly, so... do I need to split the packaging to
> individual modules, or is it fine to ship only ocaml-atd and ocaml-atd-
> devel?

Looking at the spec it seems to be doing the right thing.  As long as
there is a single source (as is the case) the fact that it generates
several OCaml modules is immaterial in my opinion, so this is fine.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Need feedback on ocaml-atd review request

2021-04-13 Thread Richard W.M. Jones

On Thu, Apr 08, 2021 at 03:02:30PM -0700, Michel Alexandre Salim wrote:
> On a related note, the packaging guidelines is rather out of date:
> https://docs.fedoraproject.org/en-US/packaging-guidelines/OCaml/

Yes, they desperately need to be updated.  At the moment it's better
to look at existing practise as you have done.

> I have a minor PR for fixing the link back to the main guidelines:
> https://pagure.io/packaging-committee/pull-request/1065

I'm not sure if I'm able to merge this.  The "merge" button just shows
an empty box when clicked, so maybe not.  However I added a comment
saying it looks OK.

> but found the example spec there really obsolete; I ended up basing my
> spec on jjames' ocaml-menhir.
> 
> Likewise, the spec generated by `rpmdev-newspec -t ocaml` is out of
> date and roughly corresponds with the spec in the packaging guidelines.
> 
> Is there an interest in revamping the documentation and template? Maybe
> ship a separate template for ocaml-dune for projects that use dune as
> as its build system?

Sure.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1948957] New: perl-Crypt-CBC-3.02 requires perl-Math-Int128 which does not exist on 32-bit platforms

2021-04-13 Thread bugzilla

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

Bug ID: 1948957
   Summary: perl-Crypt-CBC-3.02 requires perl-Math-Int128 which
does not exist on 32-bit platforms
   Product: Fedora
   Version: rawhide
  Hardware: i686
Status: NEW
 Component: perl-Crypt-CBC
  Keywords: Regression
  Assignee: andr...@bawue.net
  Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: andr...@bawue.net, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



This commit added a hard-dependency on perl(Math::Int128):

commit 83ca22c6b56fadcbf8914ec52cdb381dc2efb88d (HEAD -> rawhide,
origin/rawhide, origin/main, origin/HEAD)
Author: Paul Howarth 
Date:   Mon Apr 12 09:39:41 2021 +0100

Update to 3.02

- New upstream release 3.02
  - CTR mode now requires the Math::Int128 module, which gives a ~5x
performance boost over Math::BigInt

diff --git a/perl-Crypt-CBC.spec b/perl-Crypt-CBC.spec
index 436c3cf..caffc3c 100644
--- a/perl-Crypt-CBC.spec
+++ b/perl-Crypt-CBC.spec
@@ -1,6 +1,6 @@
 Summary:Encrypt Data with Cipher Block Chaining Mode
 Name:   perl-Crypt-CBC
-Version:3.01
+Version:3.02
 Release:1%{?dist}
 # Upstream confirms that they're under the same license as perl.
 # Wording in CBC.pm is less than clear, but still.
@@ -24,7 +24,7 @@ BuildRequires:  perl(Crypt::PBKDF2)
 BuildRequires:  perl(Digest::MD5) >= 2.00
 BuildRequires:  perl(Digest::SHA)
 BuildRequires:  perl(File::Basename)
-BuildRequires:  perl(Math::BigInt)
+BuildRequires:  perl(Math::Int128)

But perl(Math::Int128) is not available on 32-bit platforms
. You should
relax the dependency.


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

[389-devel] 389 DS nightly 2021-04-13 - 95% PASS

2021-04-13 Thread vashirov

https://fedorapeople.org/groups/389ds/ci/nightly/2021/04/13/report-389-ds-base-2.0.4-20210413gite542902ae.fc33.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

57 matches

Mail list logo