[EPEL-devel] Re: rpmautospec deployment into production

[Michel Alexandre Salim]

On Fri, Jun 18, 2021 at 05:30:28PM +0200, Nils Philippsen wrote:
> Hi everybody,
> 
> rpmautospec[1] is now deployed on the Koji builders. It took a little
> longer than expected, but went smoothly otherwise—at most, you should
> have noticed any currently running builds of yours being restarted
> when we restarted the kojid processes.
> 
> We invite you to use automatic releases and changelogs in your RPM
> packages from now on, refer to [2] for details. Please hit us up on
> #fedora-apps (on Libera.chat) if you have questions. If you encounter
> any issues, please file them in the project tracker[3].
> 
Now that this is in the Koji builders... would this be sufficient to
have it enabled for EPEL8 specs as well?

- branch and build python-rpmautospec for EPEL8
- add Requires: rpmautospec-rpm-macros to epel-rpm-macros in EPEL8

Given that EPEL8 will be around for a while, it sounds like it would be
of benefits if we can keep the same spec between Rawhide and it. e.g.
python-TestSlide now uses rpmautospec in the Rawhide branch, and so any
update in EPEL8 will have to diverge.

cc:ing the EPEL devel list so we can discuss if we want to do this

Thanks,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


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

[Bug 1814107] Please make perl-Text-Iconv available on EPEL8

[bugzilla]

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



--- Comment #5 from Marc Dequènes (Duck)  ---
Thank you for working on this.


-- 
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 1982022] New: perl-DBIx-Class-Schema-Config-0.001014 is available

[bugzilla]

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

Bug ID: 1982022
   Summary: perl-DBIx-Class-Schema-Config-0.001014 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-DBIx-Class-Schema-Config
  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: 0.001014
Current version/release in rawhide: 0.001013-8.fc35
URL: http://search.cpan.org/dist/DBIx-Class-Schema-Config/

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


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

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

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
  47  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef   
openjpeg2-2.3.1-11.el7
  13  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-bd790583ee   
seamonkey-2.53.8-1.el7
  11  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4cfaa8ab63   
djvulibre-3.5.25.3-24.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ddb4fcb22a   
opendmarc-1.4.1.1-3.el7


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

xrdp-0.9.16-2.el7

Details about builds:



 xrdp-0.9.16-2.el7 (FEDORA-EPEL-2021-9683589bf4)
 Open source remote desktop protocol (RDP) server

Update Information:

Fix bug #1977175.

ChangeLog:

* Wed Jul 14 2021 Bojan Smojver  - 1:0.9.16-2
- Bring logrotate file in line with defaults (BZ #1977175).

References:

  [ 1 ] Bug #1977175 - Default log rotation too fast
https://bugzilla.redhat.com/show_bug.cgi?id=1977175


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

[Bug 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
FEDORA-EPEL-2021-78746edd3f has been pushed to the Fedora EPEL 8 testing
repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-78746edd3f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1136745] perl-Convert-PEM-0.08-13.fc22 FTBFS randomly: 'errstr matches decrypt failed' t/02-encode.t test fails

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Convert-PEM-0.08-14.fc |perl-Convert-PEM-0.08-14.fc
   |22  |22
   ||perl-Convert-PEM-0.08-14.el
   ||7
 Resolution|RAWHIDE |ERRATA



--- Comment #3 from Fedora Update System  ---
FEDORA-EPEL-2021-976a98491a has been pushed to the Fedora EPEL 7 stable
repository.
If problem still persists, please make note of it in this bug report.


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

[Bug 1976330] ctstream-30 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|ctstream-30-1.fc35  |ctstream-30-1.fc35
   |ctstream-30-1.fc34  |ctstream-30-1.fc34
   |ctstream-30-1.fc33  |ctstream-30-1.fc33
   ||ctstream-30-1.el7



--- Comment #10 from Fedora Update System  ---
FEDORA-EPEL-2021-88812aa095 has been pushed to the Fedora EPEL 7 stable
repository.
If problem still persists, please make note of it in this bug report.


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

[Bug 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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



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

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1971305] perl-Dist-Zilla-6.023 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2021-7ca1547aa0 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-7ca1547aa0`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-7ca1547aa0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

[Bug 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
FEDORA-2021-30554e7461 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-30554e7461`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-30554e7461

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


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

Re: rpmautospec deployment into production

[Michel Alexandre Salim via devel]

On Fri, Jun 18, 2021 at 05:30:28PM +0200, Nils Philippsen wrote:
> Hi everybody,
> 
> rpmautospec[1] is now deployed on the Koji builders. It took a little
> longer than expected, but went smoothly otherwise—at most, you should
> have noticed any currently running builds of yours being restarted
> when we restarted the kojid processes.
> 
> We invite you to use automatic releases and changelogs in your RPM
> packages from now on, refer to [2] for details. Please hit us up on
> #fedora-apps (on Libera.chat) if you have questions. If you encounter
> any issues, please file them in the project tracker[3].
> 
Now that this is in the Koji builders... would this be sufficient to
have it enabled for EPEL8 specs as well?

- branch and build python-rpmautospec for EPEL8
- add Requires: rpmautospec-rpm-macros to epel-rpm-macros in EPEL8

Given that EPEL8 will be around for a while, it sounds like it would be
of benefits if we can keep the same spec between Rawhide and it. e.g.
python-TestSlide now uses rpmautospec in the Rawhide branch, and so any
update in EPEL8 will have to diverge.

cc:ing the EPEL devel list so we can discuss if we want to do this

Thanks,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


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

[Bug 1814107] Please make perl-Text-Iconv available on EPEL8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


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

Review swaps

[Jerry James]

A new version of python-networkx is out.  In order to keep building
documentation for it, the following new packages are needed.  I am
willing to swap reviews, or help out with fixing a bug in exchange for
a review.

python-bash-kernel: https://bugzilla.redhat.com/show_bug.cgi?id=1981993

python-jupyter-sphinx:
https://bugzilla.redhat.com/show_bug.cgi?id=1981994, requires
python-bash-kernel

python-pytest-datadir: https://bugzilla.redhat.com/show_bug.cgi?id=1981995

python-pytest-regressions:
https://bugzilla.redhat.com/show_bug.cgi?id=1981996, requires
python-pytest-datadir

python-pydata-sphinx-theme:
https://bugzilla.redhat.com/show_bug.cgi?id=1981997, requires
python-jupyter-sphinx and python-pytest-regressions

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

[EPEL-devel] Re: Neovim 0.5 for EPEL8 (FAO Andreas Schneider... I think)

[Michel Alexandre Salim]

Hullo!

On Tue, Jul 13, 2021 at 02:06:59PM -, David  wrote:
> Hi, I see Neovim 0.5 stable has come to Fedora 34. Is it possible it could be 
> released for EPEL8? Thanks.
> 
> At the moment there is only a very old version:
> 
> ```
> Available Packages
> Name : neovim
> Version  : 0.3.8
> Release  : 1.el8.1
> Architecture : x86_64
> Size : 5.1 M
> Source   : neovim-0.3.8-1.el8.1.src.rpm
> Repository   : epel
> Summary  : Vim-fork focused on extensibility and agility
> URL  : http://neovim.io
> License  : ASL 2.0
> Description  : Neovim is a refactor - and sometimes redactor - in the 
> tradition of
>  : Vim, which itself derives from Stevie. It is not a rewrite, 
> but a
>  : continuation and extension of Vim. Many rewrites, clones, 
> emulators
>  : and imitators exist; some are very clever, but none are Vim. 
> Neovim
>  : strives to be a superset of Vim, notwithstanding some 
> intentionally
>  : removed misfeatures; excepting those few and 
> carefully-considered
>  : excisions, Neovim is Vim. It is built for users who want the 
> good
>  : parts of Vim, without compromise, and more.
> ```
Yep, that's on my todo list. I did the EPEL8 build back when Fedora was
on 0.4.x ... and was stuck on 0.3.8 because some of the dependencies
(that are in RHEL/CentOS proper) were too out of date.

I think libuv was one of them, and it's been updated for RHEL 8.4 after
I requested it, so I'll see if I can do an update later this week. Busy
wrapping up at work until then.

Cheers,

-- 
Michel Alexandre Salim
profile: https://keyoxide.org/mic...@michel-slm.name


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

Re: ibus-setup error for typing-boster

[Per Bothner]

On 7/13/21 12:47 PM, Elliott Sales de Andrade wrote:

There's an update in testing that should fix that:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-d3ba1c0d71

Or you can directly install python3-packaging.


Thanks - that got typing-booster working again.
--
--Per Bothner
p...@bothner.com   http://per.bothner.com/
___
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: tzdata-minimal (Self-Contained Change proposal)

[Carlos O'Donell]

On 7/13/21 8:12 AM, Petr Viktorin wrote:
> On 12. 07. 21 18:31, Carlos O'Donell wrote:
>> If you can minimally provide the tables of possible zones, and
>> provide an easy way to detect a zone is missing, then the APIs can
>> determine: "Yes you could do that, but your system is missing the
>> data." vs. "That is an invalid zone." Which is a useful
>> distinction.
> 
> Sure, we can provide such an API, but that alone won't make consumers
> use it. Especially if it's specific to Fedora (and Clear Linux --
> AFAIK, people expect missing bits and pieces are there.)
> 
> I think the best place to discuss and document this would be the tz.
> If their README (or just a mail thread) said the data can be split
> this way, and hinted at what should be done when it is, we wouldn't
> need this conversation. Without that, I don't think it's OK to allow
> Fedora systems with only tzdata-minimal.

That's a fair point. We'll get clarification from upstream and Paul Eggert.

-- 
Cheers,
Carlos.
___
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: tzdata-minimal (Self-Contained Change proposal)

[Carlos O'Donell]

On 7/13/21 11:17 AM, Petr Viktorin wrote:
> On 13. 07. 21 16:31, Carlos O'Donell wrote:
>> It's possible to remove all tzdata.
>>
>> However, without *some* data it is not easy to distinguish between these
>> two scenarios if you want to offer a different error message:
>>
>> - Is this zone provided and correct but missing? e.g. exists but is not 
>> installed.
>>    - zone table exists, lists the zone, but the zone is missing.
>>
>> - Is this zone not correct? e.g. doesn't exist in the current version.
>>    - zone table doesn't list the zone.
> 
> True. But I don't see a use case where this would be important
> enough: when is an error message like "tzdata is not installed, so
> the zone can't be used *or* checked" not enough?

It may be enough.

If it turns out to be not enough would we be ready to reconsider the
packaging decision?

> The problem with making it possible to distinguish between these two
> scenarios is that *every* consumer of tzdata must now distinguish
> between them. If they assume tzdata is never split (as many do,
> AFAIK), their error messages will be wrong. That's not every consumer
> we distribute in a RPM (we could handle that I guess), but also any
> third-party one people will build/install on their systems.

Understood.

(1) Missing files vs. No /usr/share/zoneinfo.

All existing third-party software must handle zone name changes today,
so there must be some way to handle the error that a given zone is
missing (changed names).

Let me talk a bit about the new C++ time zone API I have been looking
at with Jonathan Wakely.

Errors based on this will be likely correct e.g. get_tz_dir() from the
currently proposed C++ API for this (see (2)):

 353 CONSTDATA auto tz_dir_default = "/usr/share/zoneinfo";
 354 CONSTDATA auto tz_dir_buildroot = "/usr/share/zoneinfo/uclibc";
 355 
 356 // Check special path which is valid for buildroot with uclibc builds
 357 if(stat(tz_dir_buildroot, ) == 0 && S_ISDIR(sb.st_mode))
 358 return tz_dir_buildroot;
 359 else if(stat(tz_dir_default, ) == 0 && S_ISDIR(sb.st_mode))
 360 return tz_dir_default;
 361 else
 362 throw runtime_error("discover_tz_dir failed to find zoneinfo\n");

Having tzdata uninstalled will throw the generic error as on line 362.

But having tzdata-minimal will instead throw a specific error from line 3624:

3624 throw std::runtime_error(std::string(tz_name) + " not found in 
timezone database");

This probably supports having tzdata removed entirely, since the latter
error makes it seems as-if the zone name is wrong (it's not, it's just
not installed).

Notes:
https://github.com/HowardHinnant/date

(2) Non-rpm packaging.

We have C++ users using Howard Hinnart's 'date' package that implements
 header and it can process complete IANA tzdb files.

Currently Howard's API is being proposed for inclusion 
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0355r7.html

So the error returned in the runtime_error can have an explanatory string,
so it could be tailored to a system with a partially installed tzdata-minimal,
but it could likewise detect the entire tzdata is uninstalled (no files)
and just say that (as you note, and the code supports today).

So there may not be a strong case for making the distinction between the
two error modes.

>>> We could theoretically patch Python to give reasonable error
>>> messages. But since the consumer of the tz data (the zoneinfo module)
>>> was only added in Python 3.9 (last year), existing applications
>>> mainly use third-party modules instead of the standard library. I
>>> assume that like Python, these modules expect tzinfo to either be
>>> missing entirely or be all there. And I expect this is the case for
>>> more than just Python modules.
>>   Over time some zones become deprecated and invalid names.
>>
>> One must already handle zone name changes, so if the code can handle
>> name deprecation then it will report the same error for missing zoneinfo. >
>>> Is it reasonable for glibc to hardcode the +0 fallback timezone,
>>> rather than needing the zoneinfo file for it? If so, we could remove
>>> tzdata from minimal containers entirely. Or is that too naive?
>>
>> It is not naive.
>>
>> glibc already falls back to UTC with no data present (and we need to cleanup
>> what we print).
>>
>> The question is what kind of errors we want to be able to express to users.
>>  
> == Benefit to Fedora ==
> This change will reduce the size of base container installations.
>
> == Scope ==
> * Proposal owners: Implement the proposal.
> * Other developers: Developers need to ensure that their packages
> continue to build and install with the new split tzdata/tzdata-minimal
> package changes.
>
> * Release engineering: No coordination required with Release Engineering.
> * Policies and guidelines: The policies and guidelines do not need to
> be updated.
> * Trademark approval: N/A (not needed 

[389-devel] please review: PR 4834 - Unindexed searches in retro changelog

[Mark Reynolds]

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

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

Re: Permanent Updates Policy exception for PrusaSlicer, Cura, Black, tox, HTTPie and ownCloud Desktop Client

[Otto Urpelainen]

Miro Hrončok kirjoitti 12.7.2021 klo 14.30:

Hello,

I happen to maintain some applications in Fedora where I am strongly 
confident our users would prefer "latest and greatest" over 100 % 
"stability" of the user interface and/or results.


For some of them, I've been more or less silently breaking the Updates 
Policy hoping that nothing would break (nothing did so far). For others, 
I've requested FESCo exceptions for individual updates. I'd like to 
request a *permanent exception* to allow upgrading the following tools 
and apps to latest versions in stable Fedora releases.


For transparency reasons, I've decided to share the list of packages on 
this mailing list before approaching FESCo. If you see potential 
problems, do let me know.


(snip)


ownCloud Desktop Client
===

- owncloud-client

As OwnCloud serves are updated, users might need the latest version of 
the client installed to be able to use them. Hence, I'd like to be able 
to update this package freely.


OTOH I don't actually plan to do that often, because I maintain the 
package "to scratch my own itch" and I would only do that if the server 
used by our university requires client updates. However, if 
co-maintainers appear, this could happen more often.


I wonder if Updates Policy should have general wording that would allow 
you to update this package without asking for exceptions, or at least 
"make it more likely to grant a request"? It does not make much sense to 
disallow client program updates because they contain "new features" when 
the remote backends it is connecting to require those features.


Web browsers are another example of this, and maybe also your 3d printer 
control apps.


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

Re: Python package and "vendorize"

[Tony Asleson]

On Mon, Jul 12, 2021 at 7:04 PM Kevin Fenzi  wrote:
>
> On Mon, Jul 12, 2021 at 01:26:19PM -0500, Tony Asleson wrote:
> > Upstream pywbem project took 2 internal libraries and broke them out
> > into separate libraries.  I asked if they would be OK with maintaining
> > these new packages in fedora and they said yes[1].  They followed the
> > process and asked for a sponsor and got no response [2].
>
> Sorry about that.

No worries

> You could add them in as co-maintainers, provided you are willing to
> show them how packaging works, etc.
>
> See: 
> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer

This seems to imply co-maintaining an existing package, not a new package?

> Did they or you ever submit the packages for review?

Looks like this is for one of them:
https://bugzilla.redhat.com/show_bug.cgi?id=1880953

It looks like a review comment was made, but no response yet from
Andreas (Andy).
CC'ing him on this email.  IIRC after it looks good is when you can
get a sponsor?

> They (or you) may also want to post to the python-sig list instead of
> the main devel list. Sometimes things get really busy here and people
> miss posts.

Andy CC'd

> > They have now pitched the idea of using "vendorize" to meet this
> > requirement [3].  However, I believe the answer to this from a fedora
> > packaging standpoint is no.  Is this correct?
>
> I'd say it's much better not to, yes.

Yeah, otherwise all the stuff being done for rust packages wouldn't be
occurring :-)

Thank you for your response

-Tony
___
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: ibus-setup error for typing-boster

[Elliott Sales de Andrade]

On Tue, 13 Jul 2021 at 13:29, Per Bothner  wrote:
>
> This is a follow-up to "ibus-typing-boster - testcase instruction error".
>
> Run ibus-setup in a terminal;
> select the "Input Method" tab;
> click on "Other - Typing Booster" to select it;
> click "Preferences".
>
> I get:
>
> Traceback (most recent call last):
> File "/usr/share/ibus-typing-booster/setup/main.py", line 87, in 
>   import itb_emoji
>  File "/usr/share/ibus-typing-booster/setup/../engine/itb_emoji.py", line 
> 44, in 
>   from packaging import version
> ModuleNotFoundError: No module named 'packaging'
>

There's an update in testing that should fix that:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-d3ba1c0d71

Or you can directly install python3-packaging.

> (It is plausible this is related to why typing-booster is no longer working 
> for me.)
>
> This is on an up-to-date Fedora 34.  I have not tried Rawhide or fresh 
> install.
> --
> --Per Bothner
> p...@bothner.com   http://per.bothner.com/

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

Re: Triggering fedora-ci tests

[Michal Srb]

Hello,

On Tue, Jul 13, 2021 at 6:07 PM Mark Wielaard  wrote:

> On Tue, 2021-07-13 at 14:52 +0200, Petr Pisar wrote:
> > V Tue, Jul 13, 2021 at 02:27:57PM +0200, Mark Wielaard napsal(a):
> > > Or How do you trigger a fedora-ci.koji-build.tier0.functional run for a
> > > package?
> > >
> >
> > $ bodhi updates trigger-tests UPDATE_ID
>
> Thanks! That worked, the test were run, CI passed and the package was
> added to stable.
>
> Is there are place to see which tests are pending? Or do you just have
> to run trigger-tests after some time if they haven't yet?
>

The information which tests are queued/running should be visible in Bodhi,
once [1] is resolved.

In the meantime, don't hesitate to hit that "Re-trigger tests" button in
Bodhi if you don't see the results there after some time. And if it still
doesn't work, then please open a ticket in [2].

Thanks,
Michal

[1]: https://pagure.io/fedora-infrastructure/issue/8989
[2]: https://pagure.io/fedora-ci/general/




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

[Bug 1814107] Please make perl-Text-Iconv available on EPEL8

[bugzilla]

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

Robert Scheck  changed:

   What|Removed |Added

Summary|Please make it available on |Please make perl-Text-Iconv
   |EPEL8   |available on 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 1814107] Please make it available on EPEL8

[bugzilla]

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

Robert Scheck  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|andr...@bawue.net   |redhat-bugzilla@linuxnetz.d
   ||e
  Flags|needinfo?(andr...@bawue.net |
   |)   |



--- Comment #3 from Robert Scheck  ---
Thank you for adding me as co-maintainer!

I've created https://pagure.io/releng/fedora-scm-requests/issue/35743


-- 
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 1814107] Please make it available on EPEL8

[bugzilla]

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

Robert Scheck  changed:

   What|Removed |Added

   Keywords||Triaged
Version|33  |rawhide
  Flags||needinfo?(andr...@bawue.net
   ||)



--- Comment #2 from Robert Scheck  ---
Andreas, may I kindly ask you to either branch EPEL 8 or to add me as
co-maintainer, so that I can take care of this branch?


-- 
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 1981927] New: APC::ThreadMutex is not available on x86_64 mod_perl

[bugzilla]

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

Bug ID: 1981927
   Summary: APC::ThreadMutex is not available on x86_64 mod_perl
   Product: Fedora EPEL
   Version: epel8
  Hardware: x86_64
Status: NEW
 Component: mod_perl
  Assignee: ppi...@redhat.com
  Reporter: nat...@bravenet.com
QA Contact: extras...@fedoraproject.org
CC: jkal...@redhat.com, jor...@redhat.com,
perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Description of problem:
'use APR::ThreadMutex ();' results in

 [Tue Jul 13 09:19:11.762106 2021] [perl:error] [pid 1065808:tid
140400020277568] Can't locate APR/ThreadMutex.pm in @INC (you may need to
install the APR::ThreadMutex module) (@INC contains: /usr/local/lib64/perl5
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 /etc/httpd
/usr/share/puh/apache/perl) at /home/Test.pm line 40.\nBEGIN
failed--compilation aborted at /home/test.pm line 40.\nCompilation failed in
require at /home/startup.pl line 10.\nBEGIN failed--compilation aborted at
/home/startup.pl line 10.\nCompilation failed in require at (eval 2) line 1.\n

There is also no /usr/lib64/perl5/vendor_perl/APR/ThreadMutex.pm on x86_64's
variant of mod_perl, but I do see this existing in aarch64's variant.


Version-Release number of selected component (if applicable):
2.0.11-1

How reproducible:
always

Steps to Reproduce:
ncoulson@home:~/z/y$ rpm -qpl mod_perl-2.0.11-1.el8.x86_64.rpm | grep
ThreadMutex

Actual results:
ncoulson@home:~/z/y$ rpm -qpl mod_perl-2.0.11-1.el8.x86_64.rpm | grep
ThreadMutex
/usr/share/doc/mod_perl/docs/api/APR/ThreadMutex.pod
/usr/share/man/man3/APR::ThreadMutex.3pm.gz


Expected results: (Noted this existing in aarch64)
ncoulson@home:~/z/y$ rpm -qpl mod_perl-2.0.11-1.el8.aarch64.rpm  | grep
ThreadMutex
/usr/lib64/perl5/vendor_perl/APR/ThreadMutex.pm
/usr/lib64/perl5/vendor_perl/auto/APR/ThreadMutex
/usr/lib64/perl5/vendor_perl/auto/APR/ThreadMutex/ThreadMutex.so
/usr/share/doc/mod_perl/docs/api/APR/ThreadMutex.pod
/usr/share/man/man3/APR::ThreadMutex.3pm.gz


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

Re: buildSRPMFromSCM stuck

[davidsch]

On 7/13/21 5:48 PM, Kevin Fenzi wrote:
> On Tue, Jul 13, 2021 at 08:10:05AM +0200, David wrote:
>> Hi,
>>
>> I have been trying to build git-cola for EPEL8, but the buildSRPMFromSCM
>> is stuck for over 5 hours:
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=71779476
>>
>> It is already the second try, the first I have canceled after 20 hours.
>>
>> Is the autochangelog feature the cause?
>>
>> Is there something else I did wrong?
> 
> Well, I can easily duplicate this here locally with a 'fedpkg srpm' in
> the epel8 branch. 
> 
> It looks like git is looping: 
> 
> ...
> 163004 newfstatat(AT_FDCWD, 
> "/home/kevin/git/pkgs/git-cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = 
> -1 ENOENT (No such file or directory)
> 163004 newfstatat(AT_FDCWD, 
> "/home/kevin/git/pkgs/git-cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = 
> -1 ENOENT (No such file or directory)
> 163004 newfstatat(AT_FDCWD, 
> "/home/kevin/git/pkgs/git-cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = 
> -1 ENOENT (No such file or directory)
> 163004 newfstatat(AT_FDCWD, 
> "/home/kevin/git/pkgs/git-cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = 
> -1 ENOENT (No such file or directory)
> ...
> 
> So, I guess this is a rpmautospec bug? 
> 
> Can you file it on the rpmautospec project?
> 
> kevin

Thanks a lot for analysing.

I have filed https://pagure.io/fedora-infra/rpmautospec/issue/202

Cheers,
David
___
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

ibus-setup error for typing-boster

[Per Bothner]

This is a follow-up to "ibus-typing-boster - testcase instruction error".

Run ibus-setup in a terminal;
select the "Input Method" tab;
click on "Other - Typing Booster" to select it;
click "Preferences".

I get:

Traceback (most recent call last):
   File "/usr/share/ibus-typing-booster/setup/main.py", line 87, in 
 import itb_emoji
File "/usr/share/ibus-typing-booster/setup/../engine/itb_emoji.py", line 44, in 

 from packaging import version
ModuleNotFoundError: No module named 'packaging'

(It is plausible this is related to why typing-booster is no longer working for 
me.)

This is on an up-to-date Fedora 34.  I have not tried Rawhide or fresh install.
--
--Per Bothner
p...@bothner.com   http://per.bothner.com/
___
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: Permanent Updates Policy exception for PrusaSlicer, Cura, Black, tox, HTTPie and ownCloud Desktop Client

[Kevin Fenzi]

On Mon, Jul 12, 2021 at 01:30:19PM +0200, Miro Hrončok wrote:
> Hello,
> 
> I happen to maintain some applications in Fedora where I am strongly
> confident our users would prefer "latest and greatest" over 100 %
> "stability" of the user interface and/or results.
> 
> For some of them, I've been more or less silently breaking the Updates
> Policy hoping that nothing would break (nothing did so far). For others,
> I've requested FESCo exceptions for individual updates. I'd like to request
> a *permanent exception* to allow upgrading the following tools and apps to
> latest versions in stable Fedora releases.
> 
> For transparency reasons, I've decided to share the list of packages on this
> mailing list before approaching FESCo. If you see potential problems, do let
> me know.
...snip...

I think these are all reasonable and make sense why they need to be
excepted from the normal policy. 

kevin


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

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

[tdawson]

Dear all,

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

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

Re: Triggering fedora-ci tests

[Mark Wielaard]

On Tue, 2021-07-13 at 14:52 +0200, Petr Pisar wrote:
> V Tue, Jul 13, 2021 at 02:27:57PM +0200, Mark Wielaard napsal(a):
> > Or How do you trigger a fedora-ci.koji-build.tier0.functional run for a
> > package?
> > 
> 
> $ bodhi updates trigger-tests UPDATE_ID

Thanks! That worked, the test were run, CI passed and the package was
added to stable.

Is there are place to see which tests are pending? Or do you just have
to run trigger-tests after some time if they haven't yet?

Cheers,

Mark
___
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 1981581] perl-bignum-0.53 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-bignum-0.53-1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-07-13 15:40:17




-- 
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: buildSRPMFromSCM stuck

[Kevin Fenzi]

On Tue, Jul 13, 2021 at 08:10:05AM +0200, David wrote:
> Hi,
> 
> I have been trying to build git-cola for EPEL8, but the buildSRPMFromSCM
> is stuck for over 5 hours:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=71779476
> 
> It is already the second try, the first I have canceled after 20 hours.
> 
> Is the autochangelog feature the cause?
> 
> Is there something else I did wrong?

Well, I can easily duplicate this here locally with a 'fedpkg srpm' in
the epel8 branch. 

It looks like git is looping: 

...
163004 newfstatat(AT_FDCWD, 
"/home/kevin/git/pkgs/git-cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = -1 
ENOENT (No such file or directory)
163004 newfstatat(AT_FDCWD, 
"/home/kevin/git/pkgs/git-cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = -1 
ENOENT (No such file or directory)
163004 newfstatat(AT_FDCWD, 
"/home/kevin/git/pkgs/git-cola/epel8/.git/objects/f4/", 0x7fffb9ce9d70, 0) = -1 
ENOENT (No such file or directory)
163004 newfstatat(AT_FDCWD, 
"/home/kevin/git/pkgs/git-cola/epel8/.git/objects/71/", 0x7fffb9ce9d70, 0) = -1 
ENOENT (No such file or directory)
...

So, I guess this is a rpmautospec bug? 

Can you file it on the rpmautospec project?

kevin


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

Re: List of long term FTBFS packages to be retired in August

[Miro Hrončok]

On 13. 07. 21 17:18, Miro Hrončok wrote:

...
If you see a package that can be rebuilt, please do so.

  Package  (co)maintainers    Latest build
=
...
proxyfuzz    psklenar    Fedora 32


Fixed.

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

List of long term FTBFS packages to be retired in August

[Miro Hrončok]

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package  (co)maintainersLatest build
=
cardpeek kalev   Fedora 32
percona-xtrabackup   slaanesh, slankes   Fedora 32
proxyfuzzpsklenarFedora 32
sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31

The following packages require above mentioned packages:
Depending on: percona-xtrabackup (1)
holland (maintained by: immanetize, jeffreyness, survient)
holland-xtrabackup.noarch requires /usr/bin/xtrabackup

Affected (co)maintainers
callkalpa: sugar-view-slides
chimosky: sugar-view-slides
immanetize: percona-xtrabackup
jeffreyness: percona-xtrabackup
kalev: cardpeek
pbrobinson: sugar-view-slides
psklenar: proxyfuzz
slaanesh: percona-xtrabackup
slankes: percona-xtrabackup
survient: percona-xtrabackup
tuxbrewr: sugar-view-slides
___
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: tzdata-minimal (Self-Contained Change proposal)

[Petr Viktorin]

On 13. 07. 21 16:31, Carlos O'Donell wrote:

On 7/12/21 12:16 PM, Petr Viktorin wrote:

On 06. 07. 21 20:38, David Cantrell wrote:

On Tue, Jul 06, 2021 at 01:20:47PM -0400, Ben Cotton wrote:

https://fedoraproject.org/wiki/Changes/tzdata-minimal

== Summary ==
Split the tzdata package into two parts - tzdata and tzdata-minimal.
tzdata will require tzdata-minimal.  tzdata-minimal provides the
minimal files needed to support UTC on containers.

[...]



Python should work well without *any* tzdata installed. But having
only a small subset of timezones would result in issues unique to
Fedora-based systems (assuming those are the only systems that split
tzdata).


It's possible to remove all tzdata.

However, without *some* data it is not easy to distinguish between these
two scenarios if you want to offer a different error message:

- Is this zone provided and correct but missing? e.g. exists but is not 
installed.
   - zone table exists, lists the zone, but the zone is missing.

- Is this zone not correct? e.g. doesn't exist in the current version.
   - zone table doesn't list the zone.


True. But I don't see a use case where this would be important enough: 
when is an error message like "tzdata is not installed, so the zone 
can't be used *or* checked" not enough?


The problem with making it possible to distinguish between these two 
scenarios is that *every* consumer of tzdata must now distinguish 
between them. If they assume tzdata is never split (as many do, AFAIK), 
their error messages will be wrong.
That's not every consumer we distribute in a RPM (we could handle that I 
guess), but also any third-party one people will build/install on their 
systems.



We could theoretically patch Python to give reasonable error
messages. But since the consumer of the tz data (the zoneinfo module)
was only added in Python 3.9 (last year), existing applications
mainly use third-party modules instead of the standard library. I
assume that like Python, these modules expect tzinfo to either be
missing entirely or be all there. And I expect this is the case for
more than just Python modules.
  
Over time some zones become deprecated and invalid names.


One must already handle zone name changes, so if the code can handle
name deprecation then it will report the same error for missing zoneinfo. >

Is it reasonable for glibc to hardcode the +0 fallback timezone,
rather than needing the zoneinfo file for it? If so, we could remove
tzdata from minimal containers entirely. Or is that too naive?


It is not naive.

glibc already falls back to UTC with no data present (and we need to cleanup
what we print).

The question is what kind of errors we want to be able to express to users.
  

== Benefit to Fedora ==
This change will reduce the size of base container installations.

== Scope ==
* Proposal owners: Implement the proposal.
* Other developers: Developers need to ensure that their packages
continue to build and install with the new split tzdata/tzdata-minimal
package changes.

* Release engineering: No coordination required with Release Engineering.
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A

== Upgrade/compatibility impact ==
The only visible change will be a new package tzdata-minimal required by tzdata.


== How To Test ==
Run a dnf upgrade of tzdata and observe that tzdata-minimal is now
also installed as a dependency.


== User Experience ==
Users will see that new updates to tzdata include a new package
dependency on tzdata-minimal.


== Dependencies ==
This change does not require or depend on changes to other packages.
However, we hope that dependent packages will work towards
recommending tzdata for builds and installs rather than requiring it.


== Contingency Plan ==
* Contingency mechanism: If we are unable to complete this feature by
the final development freeze, we will revert to the shipped
configuration.
* Contingency deadline: 100% Code complete deadline
* Blocks release? No

== Documentation ==
No documentation changes are needed at this time.


== Release Notes ==
The tzdata package is now divided into a UTC only package,
tzdata-minimal, and tzdata.


What is supposed to be in tzdata-minimal?  Is it
/usr/share/zoneinfo/UTC or that and more?


Slightly more (based on experience).

* UTC
/usr/share/zoneinfo/UTC

* Zone tables (which can be used to determine what is valid).
/usr/share/zoneinfo/iso3166.tab
/usr/share/zoneinfo/zone.tab
/usr/share/zoneinfo/zone1970.tab

* License file
/usr/share/licenses/tzdata/LICENSE

It saves ~5MiB for base container image sizes in a supportable way
(as opposed to what is done today which is to delete the zoneinfo data).



Forcibly removing tzdata on a fresh Fedora VM that I just set up has
the system fall back to UTC, as expected.  On this incredibly small
install, tzdata is required glibc-common, python3-libs, and
python3-dateutil.  The 

Re: F35 Change: tzdata-minimal (Self-Contained Change proposal)

[Carlos O'Donell]

On 7/12/21 12:16 PM, Petr Viktorin wrote:
> On 06. 07. 21 20:38, David Cantrell wrote:
>> On Tue, Jul 06, 2021 at 01:20:47PM -0400, Ben Cotton wrote:
>>> https://fedoraproject.org/wiki/Changes/tzdata-minimal
>>>
>>> == Summary ==
>>> Split the tzdata package into two parts - tzdata and tzdata-minimal.
>>> tzdata will require tzdata-minimal.  tzdata-minimal provides the
>>> minimal files needed to support UTC on containers.
>>>
>>> == Owner ==
>>> * Name: Patsy Griffin (Franklin)
>>> * Email: pa...@redhat.com
>>>
>>>
>>> == Detailed Description ==
>>> This is the first step towards providing support for a minimal, UTC
>>> only, version of tzdata for containers.  The tzdata-minimal package
>>> will be a stand-alone, UTC only, subset of tzdata. The tzdata package
>>> will require tzdata-minimal.
>>>
>>> With this framework in place, other packages can develop code to
>>> detect a minimal tzdata installation.  These packages will also need
>>> to provide appropriate messages when users request timezone
>>> information not available when only tzdata-minimal is installed.
>>>
>>> == Feedback ==
>>> We have had requests for this functionality in order to support
>>> minimal container installations.  Currently some container kickstart
>>> installations already ad hoc remove most of the timezone information
>>> provided by tzdata, leaving only UTC support available.  This change
>>> provides a formal method of providing this support.
>>>
>>> Both the glibc and python teams are aware of this proposed change.
>>> This change does not currently require changes in their code.  The
>>> goal is for those packages that currently require tzdata as part of
>>> their build or install, move towards recommending tzdata instead.
> 

> Python should work well without *any* tzdata installed. But having
> only a small subset of timezones would result in issues unique to
> Fedora-based systems (assuming those are the only systems that split
> tzdata).

It's possible to remove all tzdata.

However, without *some* data it is not easy to distinguish between these
two scenarios if you want to offer a different error message:

- Is this zone provided and correct but missing? e.g. exists but is not 
installed.
  - zone table exists, lists the zone, but the zone is missing.

- Is this zone not correct? e.g. doesn't exist in the current version.
  - zone table doesn't list the zone.
 
> We could theoretically patch Python to give reasonable error
> messages. But since the consumer of the tz data (the zoneinfo module)
> was only added in Python 3.9 (last year), existing applications
> mainly use third-party modules instead of the standard library. I
> assume that like Python, these modules expect tzinfo to either be
> missing entirely or be all there. And I expect this is the case for
> more than just Python modules.
 
Over time some zones become deprecated and invalid names.

One must already handle zone name changes, so if the code can handle
name deprecation then it will report the same error for missing zoneinfo.
 
> Is it reasonable for glibc to hardcode the +0 fallback timezone,
> rather than needing the zoneinfo file for it? If so, we could remove
> tzdata from minimal containers entirely. Or is that too naive?

It is not naive.

glibc already falls back to UTC with no data present (and we need to cleanup
what we print).

The question is what kind of errors we want to be able to express to users.
 
>>> == Benefit to Fedora ==
>>> This change will reduce the size of base container installations.
>>>
>>> == Scope ==
>>> * Proposal owners: Implement the proposal.
>>> * Other developers: Developers need to ensure that their packages
>>> continue to build and install with the new split tzdata/tzdata-minimal
>>> package changes.
>>>
>>> * Release engineering: No coordination required with Release Engineering.
>>> * Policies and guidelines: The policies and guidelines do not need to
>>> be updated.
>>> * Trademark approval: N/A (not needed for this Change)
>>> * Alignment with Objectives: N/A
>>>
>>> == Upgrade/compatibility impact ==
>>> The only visible change will be a new package tzdata-minimal required by 
>>> tzdata.
>>>
>>>
>>> == How To Test ==
>>> Run a dnf upgrade of tzdata and observe that tzdata-minimal is now
>>> also installed as a dependency.
>>>
>>>
>>> == User Experience ==
>>> Users will see that new updates to tzdata include a new package
>>> dependency on tzdata-minimal.
>>>
>>>
>>> == Dependencies ==
>>> This change does not require or depend on changes to other packages.
>>> However, we hope that dependent packages will work towards
>>> recommending tzdata for builds and installs rather than requiring it.
>>>
>>>
>>> == Contingency Plan ==
>>> * Contingency mechanism: If we are unable to complete this feature by
>>> the final development freeze, we will revert to the shipped
>>> configuration.
>>> * Contingency deadline: 100% Code complete deadline
>>> * Blocks release? No
>>>
>>> == Documentation ==
>>> No 

[EPEL-devel] Neovim 0.5 for EPEL8 (FAO Andreas Schneider... I think)

[David]

Hi, I see Neovim 0.5 stable has come to Fedora 34. Is it possible it could be 
released for EPEL8? Thanks.

At the moment there is only a very old version:

```
Available Packages
Name : neovim
Version  : 0.3.8
Release  : 1.el8.1
Architecture : x86_64
Size : 5.1 M
Source   : neovim-0.3.8-1.el8.1.src.rpm
Repository   : epel
Summary  : Vim-fork focused on extensibility and agility
URL  : http://neovim.io
License  : ASL 2.0
Description  : Neovim is a refactor - and sometimes redactor - in the tradition 
of
 : Vim, which itself derives from Stevie. It is not a rewrite, but a
 : continuation and extension of Vim. Many rewrites, clones, 
emulators
 : and imitators exist; some are very clever, but none are Vim. 
Neovim
 : strives to be a superset of Vim, notwithstanding some 
intentionally
 : removed misfeatures; excepting those few and carefully-considered
 : excisions, Neovim is Vim. It is built for users who want the good
 : parts of Vim, without compromise, and more.
```
___
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-Rawhide-20210713.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Compose PASSES proposed Rawhide gating check!
All required tests passed

Failed openQA tests: 4/199 (x86_64), 10/129 (aarch64)

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

ID: 926740  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/926740
ID: 926749  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/926749
ID: 926759  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/926759
ID: 926798  Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/926798
ID: 926848  Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi
URL: https://openqa.fedoraproject.org/tests/926848
ID: 926857  Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing@uefi
URL: https://openqa.fedoraproject.org/tests/926857
ID: 926860  Test: aarch64 Workstation-raw_xz-raw.xz desktop_background@uefi
URL: https://openqa.fedoraproject.org/tests/926860
ID: 926861  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/926861

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

ID: 926777  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/926777
ID: 926805  Test: aarch64 Server-dvd-iso anaconda_help@uefi
URL: https://openqa.fedoraproject.org/tests/926805
ID: 926814  Test: aarch64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/926814
ID: 926952  Test: aarch64 universal install_repository_http_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/926952
ID: 926954  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/926954
ID: 926976  Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/926976

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

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

ID: 926794  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/926794
ID: 926795  Test: aarch64 Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/926795
ID: 926852  Test: aarch64 Workstation-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/926852
ID: 926873  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/926873
ID: 926967  Test: aarch64 universal upgrade_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/926967

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

ID: 926898  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/926898
ID: 926905  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/926905
ID: 926950  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/926950
ID: 926972  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/926972

Passed openQA tests: 182/199 (x86_64), 114/129 (aarch64)

New passes (same test not passed in Fedora-Rawhide-20210712.n.0):

ID: 926673  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/926673
ID: 926674  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/926674
ID: 926675  Test: x86_64 Server-dvd-iso anaconda_help
URL: https://openqa.fedoraproject.org/tests/926675
ID: 926676  Test: x86_64 Server-dvd-iso install_repository_hd_variation
URL: https://openqa.fedoraproject.org/tests/926676
ID: 926677  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/926677
ID: 926678  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/926678
ID: 926680  Test: x86_64 Server-dvd-iso install_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/926680
ID: 926681  Test: x86_64 Server-dvd-iso install_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/926681
ID: 926682  Test: x86_64 Server-dvd-iso install_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/926682
ID: 926683  Test: x86_64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/926683
ID: 926685  Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/926685
ID: 926686  Test: x86_64 Server-dvd-iso 

Re: rust2rpm 18 available with new features, including rpmautospec support

[Rémi Lauzier via devel]

Thanks for your work! That should help a lot.

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

Le mardi 13 juillet 2021 à 08:10, Fabio Valentini  a 
écrit :

> Hi everybody,
> 

> The Rust SIG has recently worked on a few new features and fixes for
> 

> rust2rpm, and they are now available with version 18 for fedora 34 and
> 

> rawhide.
> 

> New features include:
> 

> -   Add simple %license and %doc file auto-detection
> 

> This should reduce the amount of busy-work for version updates.
> -   Add optional support for rpmautospec (autorelease, autochangelog)
> 

> rpmautospec is deployed and working fine, and rust2rpm 18 can now
> 

> optionally generate compatible .spec files with the "--rpmautospec" /
> 

> "-a" CLI flag.
> -   Use changelog timestamp format without time and timezone on Fedora
> 

> rust2rpm was the last (?) tool in Fedora which used the "new"
> 

> changelog timestamp format that includes the time and timezone, which
> 

> is not well supported by older RPM releases, and its use is
> 

> discouraged by RPM upstream. Now rust2rpm uses the same format as all
> 

> other tools again.
> 

> With rpmautospec support and automatic detection of %license and %doc
> 

> files, most version updates for Rust packages now should require
> 

> either little or no manual .spec file editing.
> 

> The rawhide update is already stable, and the update for Fedora 34 is
> 

> in updates-testing since today:
> 

> https://bodhi.fedoraproject.org/updates/FEDORA-2021-0cd0c4ed88
> 

> Please test and let us know if there are any problems, or if you like
> 

> new busywork-reducing features :)
> 

> Fabio
> 

> devel mailing list -- devel@lists.fedoraproject.org
> 

> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 

> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> 

> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> 

> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 

> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

publickey - remilauzier@protonmail.com - 0xC69091A8.asc
Description: application/pgp-keys


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

[Bug 1971305] perl-Dist-Zilla-6.023 is available

[bugzilla]

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



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


-- 
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 1971305] perl-Dist-Zilla-6.023 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||jples...@redhat.com
   Fixed In Version||perl-Dist-Zilla-6.023-1.fc3
   ||5
 Resolution|--- |RAWHIDE
   Assignee|psab...@redhat.com  |jples...@redhat.com
   Doc Type|--- |If docs needed, set a value
Last Closed||2021-07-13 12:50:14




-- 
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: Triggering fedora-ci tests

[Petr Pisar]

V Tue, Jul 13, 2021 at 02:27:57PM +0200, Mark Wielaard napsal(a):
> For example the last rawhide build just says that fedora-ci.koji-
> build.tier0.functional didn't have any results:
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-5d732932ff
> 
> Is there a place where I can inspect why a run seems to be stuck?

I have been also missing tests results for my builds recently. Few minutes ago
I was asked by astepano from CI team on details of my builds. So guess CI has
some difficulties now and the adminstrators are trying to locate the cause.

> Or How do you trigger a fedora-ci.koji-build.tier0.functional run for a
> package?
> 
$ bodhi updates trigger-tests UPDATE_ID

-- Petr


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

Fedora rawhide compose report: 20210713.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20210712.n.0
NEW: Fedora-Rawhide-20210713.n.0

= SUMMARY =
Added images:2
Dropped images:  2
Added packages:  6
Dropped packages:2
Upgraded packages:   164
Downgraded packages: 0

Size of added packages:  2.32 MiB
Size of dropped packages:133.06 KiB
Size of upgraded packages:   3.01 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -25.20 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Workstation raw-xz armhfp
Path: 
Workstation/armhfp/images/Fedora-Workstation-Rawhide-20210713.n.0.armhfp.raw.xz
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-Rawhide-20210713.n.0.armhfp.raw.xz

= DROPPED IMAGES =
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-Rawhide-20210712.n.0.aarch64.raw.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20210712.n.0.ppc64le.tar.xz

= ADDED PACKAGES =
Package: dropwatch-1.5.3-5.fc35
Summary: Kernel dropped packet monitor
RPMs:dropwatch
Size:176.76 KiB

Package: exaile-4.1.1-3.fc35
Summary: Simple but powerful Amarok-style music player for GTK users
RPMs:exaile
Size:1.27 MiB

Package: monocypher-3.1.2-1.fc35
Summary: Boring crypto that simply works
RPMs:monocypher monocypher-devel
Size:539.29 KiB

Package: perl-GooCanvas2-CairoTypes-0.001-5.fc35
Summary: Bridge between GooCanvas2 and Cairo types
RPMs:perl-GooCanvas2-CairoTypes
Size:119.67 KiB

Package: python-azure-mgmt-applicationinsights-1.0.0-1.fc35
Summary: Microsoft Azure Application Insights Management Client Library for 
Python
RPMs:python3-azure-mgmt-applicationinsights
Size:210.10 KiB

Package: rust-field-offset-0.3.4-1.fc35
Summary: Safe pointer-to-member implementation
RPMs:rust-field-offset+default-devel rust-field-offset-devel
Size:24.97 KiB


= DROPPED PACKAGES =
Package: python-cliapp-1.20180121-10.fc35
Summary: Python framework for Unix command line programs
RPMs:python3-cliapp
Size:100.31 KiB

Package: python-coverage-test-runner-1.15-11.fc35
Summary: Python module for enforcing code coverage completeness
RPMs:python3-coverage-test-runner
Size:32.75 KiB


= UPGRADED PACKAGES =
Package:  acpica-tools-20210604-1.fc35
Old package:  acpica-tools-20200925-2.fc34
Summary:  ACPICA tools for the development and debug of ACPI tables
RPMs: acpica-tools
Size: 4.64 MiB
Size change:  -6.89 KiB
Changelog:
  * Sun Jul 11 2021 Al Stone  - 20210604-1
  - Update to 20210604 source tree (please note that tarballs for versions
between 20200925 and 20210604 have been uploaded for archival reasons
but no packaged version of these has been commited to the Fedora project)
  - Bring the big-endian patches up-to-date with what has been submitted
upstream (not accepted currently).


Package:  anaconda-35.19-1.fc35
Old package:  anaconda-35.18-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.66 MiB
Size change:  64.24 KiB
Changelog:
  * Mon Jul 12 2021 Martin Kolman  - 35.19-1
  - Don't return None from is_supported_filesystem (#1979854) (vponcova)
  - Configure the multilib policy of the target system (vponcova)
  - Reorder imports to reduce linter warnings (vslavik)
  - Ignore falsy pylint missing member warning in dnf code (vslavik)
  - Silence false pylint warning (vslavik)
  - Don't use deprecated imp module in dracut test (vslavik)
  - Fix typo in docs (vslavik)
  - Replace (vslavik)
  - Ignore pylint mistakes about missing members in test (vslavik)
  - Remove the productVariant variable (vponcova)
  - Document the profile configuration files (vponcova)
  - Add support for the profile configuration files (#1974819) (vponcova)
  - Replace inst.product and inst.variant with inst.profile (vponcova)
  - Replace product configuration files with profiles (vponcova)
  - Appease pylint's belief that this is not a string (vslavik)
  - Update pylint directive for new warning name (vslavik)
  - Revert "Fix unit test for previous commit" (lveyde)
  - Revert "ovirt / rhv: drop swap partition" (lveyde)


Package:  anthy-unicode-1.0.0.20201109-6.fc35
Old package:  anthy-unicode-1.0.0.20201109-4.fc35
Summary:  Japanese character set input library for Unicode
RPMs: anthy-unicode anthy-unicode-devel emacs-anthy-unicode 
xemacs-anthy-unicode
Size: 34.19 MiB
Size change:  -114.92 KiB
Changelog:
  * Mon Jul 12 2021 Takao Fujiwara  1.0.0.20201109-5
  - Fix covscan report

  * Tue Jul 13 2021 Takao Fujiwara  1.0.0.20201109-6
  - Fix covscan report


Package:  awscli-1.19.110-1.fc35
Old package:  awscli-1.19.109-1.fc35
Summary:  Universal Command Line Envi

Triggering fedora-ci tests

[Mark Wielaard]

Hi,

For valgrind we added some integration tests, and they seem useful (for
example they caught a change in gdb breakpoint location when set after
attaching to the valgrind gdbserver). But sometimes they don't trigger
and then the package is just stuck waiting till the CI tests are ran.

For example the last rawhide build just says that fedora-ci.koji-
build.tier0.functional didn't have any results:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-5d732932ff

Is there a place where I can inspect why a run seems to be stuck?
Or How do you trigger a fedora-ci.koji-build.tier0.functional run for a
package?

Thanks,

Mark
___
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: tzdata-minimal (Self-Contained Change proposal)

[Petr Viktorin]

On 12. 07. 21 18:31, Carlos O'Donell wrote:

On 7/6/21 2:38 PM, David Cantrell wrote:

On Tue, Jul 06, 2021 at 01:20:47PM -0400, Ben Cotton wrote:

https://fedoraproject.org/wiki/Changes/tzdata-minimal

== Summary ==
Split the tzdata package into two parts - tzdata and tzdata-minimal.
tzdata will require tzdata-minimal.  tzdata-minimal provides the
minimal files needed to support UTC on containers.

== Owner ==
* Name: Patsy Griffin (Franklin)
* Email: pa...@redhat.com


== Detailed Description ==
This is the first step towards providing support for a minimal, UTC
only, version of tzdata for containers.  The tzdata-minimal package
will be a stand-alone, UTC only, subset of tzdata. The tzdata package
will require tzdata-minimal.

With this framework in place, other packages can develop code to
detect a minimal tzdata installation.  These packages will also need
to provide appropriate messages when users request timezone
information not available when only tzdata-minimal is installed.

== Feedback ==
We have had requests for this functionality in order to support
minimal container installations.  Currently some container kickstart
installations already ad hoc remove most of the timezone information
provided by tzdata, leaving only UTC support available.  This change
provides a formal method of providing this support.

Both the glibc and python teams are aware of this proposed change.
This change does not currently require changes in their code.  The
goal is for those packages that currently require tzdata as part of
their build or install, move towards recommending tzdata instead.

== Benefit to Fedora ==
This change will reduce the size of base container installations.

== Scope ==
* Proposal owners: Implement the proposal.
* Other developers: Developers need to ensure that their packages
continue to build and install with the new split tzdata/tzdata-minimal
package changes.

* Release engineering: No coordination required with Release Engineering.
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A

== Upgrade/compatibility impact ==
The only visible change will be a new package tzdata-minimal required by tzdata.


== How To Test ==
Run a dnf upgrade of tzdata and observe that tzdata-minimal is now
also installed as a dependency.


== User Experience ==
Users will see that new updates to tzdata include a new package
dependency on tzdata-minimal.


== Dependencies ==
This change does not require or depend on changes to other packages.
However, we hope that dependent packages will work towards
recommending tzdata for builds and installs rather than requiring it.


== Contingency Plan ==
* Contingency mechanism: If we are unable to complete this feature by
the final development freeze, we will revert to the shipped
configuration.
* Contingency deadline: 100% Code complete deadline
* Blocks release? No

== Documentation ==
No documentation changes are needed at this time.


== Release Notes ==
The tzdata package is now divided into a UTC only package,
tzdata-minimal, and tzdata.


What is supposed to be in tzdata-minimal?  Is it
/usr/share/zoneinfo/UTC or that and more?


A little more is provided.

You need some of the name tables for certain use cases.


What are the use cases (and why are they needed for minimal containers)?


This is based on Intel's clear linux work in splitting the data.
  

Forcibly removing tzdata on a fresh Fedora VM that I just set up has
the system fall back to UTC, as expected.  On this incredibly small
install, tzdata is required glibc-common, python3-libs, and
python3-dateutil.  The last one is reasonable, but for all of them I
ask if tzdata is actually a hard dependency or if it can become a weak
dependency and this change proposal could become "make tzdata
something easily removable" rather than creating more tzdata packages.


If you can minimally provide the tables of possible zones, and provide
an easy way to detect a zone is missing, then the APIs can determine:
"Yes you could do that, but your system is missing the data."
vs.
"That is an invalid zone."
Which is a useful distinction.


Sure, we can provide such an API, but that alone won't make consumers 
use it. Especially if it's specific to Fedora (and Clear Linux -- AFAIK, 
people expect missing bits and pieces are there.)


I think the best place to discuss and document this would be the tz. If 
their README (or just a mail thread) said the data can be split this 
way, and hinted at what should be done when it is, we wouldn't need this 
conversation.
Without that, I don't think it's OK to allow Fedora systems with only 
tzdata-minimal.


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

Re: Self Introduction: Lukas Zaoral

[Miroslav Suchý]

Dne 13. 07. 21 v 11:33 Lukáš Zaoral napsal(a):

My name's Lukas Zaoral (FAS: lzaoral) and I work for Red Hat on automated 
formal analysis


Welcome Lukas.



of RPM packages. I've created a review request for a tool called KLEE that can 
be, besides
other things, used for exhaustive generation of tests:
https://bugzilla.redhat.com/show_bug.cgi?id=1981739
Thank you for taking a look!


I have taken this one.

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

rust2rpm 18 available with new features, including rpmautospec support

[Fabio Valentini]

Hi everybody,

The Rust SIG has recently worked on a few new features and fixes for
rust2rpm, and they are now available with version 18 for fedora 34 and
rawhide.

New features include:

- Add simple %license and %doc file auto-detection
  This should reduce the amount of busy-work for version updates.

- Add optional support for rpmautospec (autorelease, autochangelog)
  rpmautospec is deployed and working fine, and rust2rpm 18 can now
optionally generate compatible .spec files with the "--rpmautospec" /
"-a" CLI flag.

- Use changelog timestamp format without time and timezone on Fedora
  rust2rpm was the last (?) tool in Fedora which used the "new"
changelog timestamp format that includes the time and timezone, which
is not well supported by older RPM releases, and its use is
discouraged by RPM upstream. Now rust2rpm uses the same format as all
other tools again.

With rpmautospec support and automatic detection of %license and %doc
files, most version updates for Rust packages now should require
either little or no manual .spec file editing.

The rawhide update is already stable, and the update for Fedora 34 is
in updates-testing since today:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-0cd0c4ed88

Please test and let us know if there are any problems, or if you like
new busywork-reducing features :)

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

[Bug 1979815] perl-DateTime-Format-Flexible-0.34 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

Link ID||CPAN 137397



--- Comment #10 from Petr Pisar  ---
This breaks perl-DateTimeX-Easy-0.089 tests
.


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

[Test-Announce] Fedora 35 Rawhide 20210713.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 35 Rawhide 20210713.n.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

Notable package version changes:
anaconda - 20210709.n.1: anaconda-35.18-1.fc35.src, 20210713.n.0: 
anaconda-35.19-1.fc35.src

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

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_35_Rawhide_20210713.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210713.n.0_Security_Lab

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

[Bug 1973919] perl-Text-CSV-2.01 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||jples...@redhat.com
   Fixed In Version||perl-Text-CSV-2.01-1.fc35
 Resolution|--- |RAWHIDE
   Assignee|jvrom...@squirrel.nl|jples...@redhat.com
   Doc Type|--- |If docs needed, set a value
Last Closed||2021-07-13 11:10:59




-- 
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 1970393] Upgrade perl-Time-Duration-Parse to 0.16

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |CLOSED
   Fixed In Version||perl-Time-Duration-Parse-0.
   ||16-1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-07-13 10:20:21



--- Comment #1 from Jitka Plesnikova  ---
Built by corsepiu


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

[Bug 1981581] perl-bignum-0.53 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

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




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

[Bug 1981578] perl-Math-BigRat-0.2616 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Math-BigRat-0.2616-1.f
   ||c35
 Resolution|--- |RAWHIDE
Last Closed||2021-07-13 10:03:42




-- 
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 1981577] perl-Math-BigInt-1.999823 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Math-BigInt-1.9998.23-
   ||1.fc35
 Resolution|--- |RAWHIDE
Last Closed||2021-07-13 09:55:18




-- 
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 1981578] perl-Math-BigRat-0.2616 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

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




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

[Bug 1981577] perl-Math-BigInt-1.999823 is available

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

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




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

Self Introduction: Lukas Zaoral

[Lukáš Zaoral]

Hello!
My name's Lukas Zaoral (FAS: lzaoral) and I work for Red Hat on automated 
formal analysis
of RPM packages. I've created a review request for a tool called KLEE that can 
be, besides
other things, used for exhaustive generation of tests:
https://bugzilla.redhat.com/show_bug.cgi?id=1981739
Thank you for taking a look!

Regards,
Lukas
___
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: libmemcached-awesome (Self-Contained Change proposal)

[Remi Collet]

FYI

https://fedoraproject.org/wiki/Changes/libmemcached-awesome


libmemcached 1.0.18 have been retired from Rawhide

libmemcached-awesome 1.1.0 is now available



Remi
___
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 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



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


-- 
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 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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



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


-- 
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 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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



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


-- 
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 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

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



--- Comment #3 from Petr Pisar  ---
An enhancement release suitable for all Fedoras and EPEL ≥ 8.


-- 
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: Can't log into release-monitoring.org?

[Adam Saleh]

Ok, this is exactly the kind of issue we track in the
https://pagure.io/fedora-infrastructure/issues.
As I suppose you can't log-in, I took the liberty to create one for you :-)

https://pagure.io/fedora-infrastructure/issue/10096

Adam
___
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 1981476] perl-ExtUtils-CChecker-0.11 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Blocks||1981565





Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1981565
[Bug 1981565] perl-XS-Parse-Keyword-0.09 is available
-- 
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

buildSRPMFromSCM stuck

[David]

Hi,

I have been trying to build git-cola for EPEL8, but the buildSRPMFromSCM
is stuck for over 5 hours:
https://koji.fedoraproject.org/koji/taskinfo?taskID=71779476

It is already the second try, the first I have canceled after 20 hours.

Is the autochangelog feature the cause?

Is there something else I did wrong?

Thanks for your time,
David
___
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