[Bug 1808002] perl-PPIx-Regexp-0.070 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2020-02-28 07:50:43



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

[Bug 1808002] perl-PPIx-Regexp-0.070 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-PPIx-Regexp-0.070-1.fc
   ||33



--- Comment #1 from Petr Pisar  ---
Major changes. Safer for Rawhide only.

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

[Bug 1808002] perl-PPIx-Regexp-0.070 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

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



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

[Bug 1789040] Missing requires for fusioninventory-agent

[bugzilla]

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

Johan Cwiklinski  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |NOTABUG
Last Closed||2020-02-28 06:50:01



--- Comment #2 from Johan Cwiklinski  ---
Paul is right, this seems ok with PowerTools enabled.

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

[rpms/perl-Acme-Damn] PR #1: Spec file cleanups: Use make_build and make_install macros

[Emmanuel Seyman]

The pull-request: `Spec file cleanups: Use make_build and make_install macros` 
of project: `perl-Acme-Damn` has been assigned to `eseyman` by eseyman.

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

Re: Self Introduction: Dan Shoemaker

[Daniel Shoemaker]

>
> Hi, my name is Dan Shoemaker.  I have been using Fedora since Fedora Core
> 6 for both personal and professional use.  About five years ago I started
> developing bash scripts in order to start automating tasks I was doing
> while maintaining Linux servers for various clients.  Last year I started
> taking Todd McLeod's Udemy class Learning Go and I found much to my delight
> that Fedora has a very active Go SIG.  As a result I would love to become a
> package maintainer for the Go packages on Fedora.
>
> Dan
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[389-devel] 389 DS nightly 2020-02-28 - 96% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2020/02/28/report-389-ds-base-1.4.3.3-20200228git75a51aa.fc31.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[rpms/perl-Acme-Damn] PR #1: Spec file cleanups: Use make_build and make_install macros

[Tom Stellard]

tstellar opened a new pull-request against the project: `perl-Acme-Damn` that 
you are following:
``
Spec file cleanups: Use make_build and make_install macros
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Acme-Damn/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org

[Bug 1807263] perl-Getopt-Long-Descriptive-0.105 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Getopt-Long-Descriptive-0.105-1.fc32 has been pushed to the Fedora 32
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f72d6a2647

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

HEADS UP: setuptools 45.2.0 in rawhide

[Miro Hrončok]

Just a heads up that I am building python-setuptools 45.2.0 in rawhide.

The update is from 41.6.0, so quite a jump. We have been mostly waiting for 
branching + coordination (all Python interpreters and virtualenv unfortunately 
needed patch changes).


https://setuptools.readthedocs.io/en/latest/history.html#v45-2-0

Most important backwards incompatible change is:

"Drop support for Python 3.4. Drop support for Python 2. Setuptools now requires 
Python 3.5 or later."


Python 3.4, Python 2.7, PyPy 2.7 use their own bundled version of setuptools.

Jython Pull Request is pending in
https://src.fedoraproject.org/rpms/jython/pull-request/4

This update is intended for Fedora 33+ only until proven otherwise (but all the 
related changes in other packages are backwards compatible).


Report any problems trough usual channels or here.

Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org

Re: Non-responsive maintainer: pocock

[Dakota Williams via devel]

On 2/26/20 6:59 PM, Daniel Pocock wrote:



On 26/02/2020 22:56, Dakota Williams wrote:

On 2/24/20 5:57 PM, Daniel Pocock wrote:



On 24/02/2020 20:47, Dakota Williams wrote:

Does anyone know how to contact maintainer pocock?

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



Like most developers, I have a backlog of things to deal with and I try
to coordinate fixes for packaging issues into the right part of the
release cycle



Would you like help? I'd be willing to be a co-maintainer to make the
branch.


Yes, I would welcome help with these packages

But there is also an increasing problem of making decisions about trust

In the case of developers who I haven't met or worked with, I don't
really know how to proceed

I've seen several extraordinary examples of developers doing things that
undermine my confidence in them over the last couple of years.  The
fighting within GNU and FSF right now is the latest iteration of that.

Now, whenever I receive a request from somebody I don't know, there is
an extra effort for me to decide how to proceed.

Maybe I can simply resign from maintaining the asio package and then opt
out of the process of choosing a new maintainer.

Please don't take this personally: it is a reflection of the overall
state of free software communities today.

I don't know about the situation with the GNU project and the FSF, but 
if there's something you'd like me to do to prove trust, I could do it.

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

Re: Want to claim vault

[Dave Dykstra]

Yes is there someone with more knowledge on this who could say what the
right procedure is for this case?  If I do need to use a different name
package name, would I at least be able to have 'Provides: vault' in it?
I don't think there's a precedent yet for this package in other Linux
distros so I would try to get an agreement with upstream on what the
packaged name should be.

I did find that someone else has begun working on Fedora packaging for
this, in
https://pagure.io/vault-stack-fedora/blob/master/f/vault

Dave

On Tue, Feb 25, 2020 at 08:59:13AM +, Mattia Verga via devel wrote:
> Il 24/02/20 23:12, Dave Dykstra ha scritto:
> > I made a ticket (bug #1806737) for the maintainer of the existing vault
> > package in Fedora to see if he'd be willing to give it up so it can be
> > used for Hashicorp vault (https://vaultproject.io ) and he decided to
> > mark it EOL so I could claim it.
> >
> > Dave
> > ___
> 
> I don't think it is allowed to reuse the git repo (and the name) of a 
> retired package for a completely different one, even if their name it's 
> the same...
> 
> In my opinion you should file a review ticket for the new package with a 
> name which avoid present and future conflicts, the name 'vault' is just 
> too generic: 
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#_conflicting_package_names
>  
> 
> Maybe someone with more knowledge here can tell you the right procedure 
> for this case.
> 
> Mattia
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines 
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ideas and proposal for removing changelog and release fields from spec file

[clime]

On Thu, 27 Feb 2020 at 16:13, Zbigniew Jędrzejewski-Szmek
 wrote:
>
> Hi,
>
> On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> > For the changelog, we believe we have a potential good solution:
> > - The changelog will be automatically generated using an external 
> > `changelog`
> >   file as well as the commit history
> ...
> > If you wanted to edit the changelog, you would:
> > - Generate the changelog locally via a command like:
> >   `fedpkg generate-changelog > changelog`
> > - Edit `changelog` as desired
> > - Commit and push the changes
>
> This means that a separate commit needs to be done *after* on top
> of the commits doing the actual changes. It's a bit disappointing, but
> on its own would not be too bad, since we can have fedpkg provide a
> higher level command that combines generate-changelog and build...
>
> One important feature will work:
> being able to cherry-pick commit between branches w/o spurious
> conflicts. As long as the "real" change to the spec file are done in
> separate commits, and the changelog commit is another commit on top,
> then when cherry-picking to another branch, the "real" commits would
> be cherry-pickable, and then the changelog commit would be recreated
> using the automation, OK.
>
> But it doesn't work quite as nicely with something similar: merging
> branches. A simple 'git merge' would result in conflicts.
>
> Also, if an amendment to the changelog is done, and the same change
> needs to be done in the changelog in a different branch, trying to
> cherry-pick the fix commit would most likely result in a merge
> conflict.
>
> Considering these three drawbacks (separate commit step and resulting
> log noise, merge conflicts), I'd very much hope for a solution where
> the changelog is never stored in the version control, and is always
> autogenerated at srpm creation time. We should never try to chery-pick
> commits that have changelog entries with actual date or e-v-r texts,
> since this will inevitably lead to merge conflicts.
>
>
> A different approach:
> - we have 'fedpkg generate-changelog' (which does all the git log
>   extraction that was described, I think that part is OK),
> - the output from this command included in the srpm at srpm generation
>   time and never committed to version control,
> - the output is annotated with the source commits hashes, so we can
>   see where each line came from.
>
> At any time, the packager can run 'fedpkg generate-changelog' to see
> how the output looks like. If they see something they don't like, if
> the commits haven't been pushed out yet, they can immediately run
> 'git commit --amend' and recheck. If they have been pushed out, an override
> to the changelog could be committed as part of a commit message text.
>
> Git-changelog-suppress: adb42e
> or
> Git-changelog-suppress: adb42e..efefedeadb
> or
> Git-changelog-replace: adb42e
>   Some other text with typos fixed that completely overrides whatever
>   was generated from adb42e.
> or
> Git-changelog-append: adb42e
>   (additional clarification for commit adb42e, e.g. bug #12345)
>
> This would have the following advantages:
> - git log is the sole source of truth
> - there are no cherry-pick or merge conflicts
> - there is no separate "now I'm done and I need to do another commit
>   before building" thing.
>
> The assumption is that those Git-changelog-* macros would only be
> used occasionally, if the bad changelog entry was not noticed before
> pushing the changes out.
>
> (One nitpick: when cherry-picking between branches, hashes of the
> cherry-picked commits change, so "adb42e" in the example above
> would stop working. This is handled by using 'git cherry-pick -x'.
> 'fedpkg generate-changelog' would look at any hash in a
> "(cherry picked from commit ...)" line.)

Hello Zbyszek,

it's good that it solves conflicts when cherry-picking and merging and
git log is the source of truth but simply dropping a line that i don't
want in the changelog or appending something to it seems to be quite
painful to do.

One advantage you mention is:
> - there is no separate "now I'm done and I need to do another commit
>   before building" thing.
But if you want to modify the automatic product, you would need one or
more additional commits to do that.

Imho, one would prefer to be able to do that simply by editing a text
file (even if temporary). Annotated tags give you that ability by
design - the tag annotation can be prepopulated and then freely
edited, which is much more pleasant in my opinion. It doesn't clutter
commit space and you can point other branches to that particular
annotation by merging if desired. But the cherry-picking workflow, on
the other hand, would require creating a new tag specific for that
branch (that would suggest the tags should contain branchname/%dist at
the end as fedpkg does it now). That's were things start getting
clumsy unless there is something like fedpkg build --annotation-from

Re: Build into < Rawhide side tag fails with "Package ... has already been built"

[Kevin Fenzi]

On Thu, Feb 27, 2020 at 07:50:05PM +0100, Clement Verna wrote:
> On Thu, 27 Feb 2020 at 14:14, Richard W.M. Jones  wrote:
> 
> > Despite earlier concerns, this does in fact appear to all be working fine.
> >
> 
> Yes requesting and building in the side tag should work just fine.
> 
> 
> >
> > There are now F32 builds going through for all OCaml packages in a
> > side tag, and when that's done I'll try to create a Bodhi update.
> >
> 
> This is where you are going to have some problems, the deployed version of
> Bodhi is not yet ready to support side tags for other release than rawhide.
> A new release of Bodhi with that support should arrive soon tho.

In the mean time, you can file a releng ticket when you are ready and we
can retag all your builds from the side-tag into candidate so you can
make a update from them. :( Sorry for the hassle. 

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

Re: taskotron going down for emergency maintenance

[Tim Flink]

Taskotron is back up but we're still having some issues with delays to
the incoming jobs.

We're still investigating but data should be flowing again, even if it
is a bit delayed.

Thanks,

Tim

On Thu, 27 Feb 2020 10:09:33 -0700
Tim Flink  wrote:

> The subject says it all, really.
> 
> Taskotron is having some problems with an internal component, it can't
> wait for a better time and we need some downtime to fix it.
> 
> If all goes well, it should be back up shortly. I'll send another
> email to update once we're done.
> 
> Tim



pgpR7q9Lx1xXj.pgp
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

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

[updates]

The following Fedora EPEL 6 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-91512b5eee   
proftpd-1.3.3g-14.el6


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

gfal2-2.17.2-1.el6
php-pecl-krb5-1.1.3-1.el6
php-phpseclib-2.0.25-1.el6

Details about builds:



 gfal2-2.17.2-1.el6 (FEDORA-EPEL-2020-432311ef2f)
 Grid file access library 2.0

Update Information:

Upgrade to upstream release 2.17.2

ChangeLog:

* Tue Feb 25 2020 Michal Simon  - 2.17.2-1
- Upgrade to upstream release 2.17.2
* Tue Jan 28 2020 Fedora Release Engineering  - 
2.17.1-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild




 php-pecl-krb5-1.1.3-1.el6 (FEDORA-EPEL-2020-3081faa2c4)
 Kerberos authentification extension

Update Information:

**Version 1.1.3**  - [BUG] Keep proper minor status for error reporting in
initSecContex - [BUG] remove some overlooked debugging output - [BUG] fix PECL
package license metadata - [FEATURE] Add API for password expiration information
(MIT >=1.9 only) - [FEATURE] Allow leaving the NegotiateAuth SPN unspecified
(allow all from keytab) - [FEATURE] Add support for gss_acquire_cred_from()
instead of setting the per process keytab (in NegotiateAuth, GSSAPI to follow).
- [FEATURE] Allow overriding SPN for NegotiateAuth.

ChangeLog:

* Thu Feb 27 2020 Remi Collet  - 1.1.3-1
- update to 1.1.3




 php-phpseclib-2.0.25-1.el6 (FEDORA-EPEL-2020-de4cdd0d1a)
 PHP Secure Communications Library

Update Information:

**Version 2.0.25 - 2020-02-24**  * SFTP: re-add buffering (#1455)

ChangeLog:

* Tue Feb 25 2020 Remi Collet  - 2.0.25-1
- update to 2.0.25
* Mon Feb 24 2020 Remi Collet  - 2.0.24-1
- update to 2.0.24


___
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

Revamping the Release Readiness meeting

[Ben Cotton]

(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)


You may have already seen my Community Blog post[1] about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page[2] beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
release.

I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts[3] and the FPgM office hours[4] IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list[5] to discuss
issues and make announcements, so I encourage representatives to join
this list.


[1] https://communityblog.fedoraproject.org/fedora-program-update-2020-08/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://communityblog.fedoraproject.org/category/program-management/
[4] https://apps.fedoraproject.org/calendar/council/#m9570

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

Re: Ideas and proposal for removing changelog and release fields from spec file

[Nicolas Mailhot via devel]

Le jeudi 27 février 2020 à 17:38 +0100, clime a écrit :
> On Thu, 27 Feb 2020 at 16:26, Nicolas Mailhot via devel
>  wrote:
> > Le 2020-02-27 12:59, clime a écrit :
> > Hi,
> > 
> > > can you, please, show an example of such package? I was searching
> > > through some
> > > golang packages because I was curious how it works but couldn't
> > > find
> > > an example
> > 
> > A Go example:
> > https://src.fedoraproject.org/rpms/golang-x-build
> > 
> > A non-Go example:
> > https://src.fedoraproject.org/rpms/impallari-dancing-script-fonts
> > 
> > In both cases the spec calls a macro (not the same one in both
> > specs) that causes one or several distprefixNUMBER variables to be
> > computed
> > 
> > The result then ends in Release via
> > https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/fedora-release.spec#_488
> > 
> > The font spec example calls the macro in redhat-rpm-config directly
> > (%forgemeta), the Go example calls it through a Go-specific macro
> > in go-rpm-macros (%gometa)
> 
> Okay, thanks :)!
> 
> At least my idea was that there should be a spec file preprocessor,
> evaluating the macros that need git context, that would produce valid
> rpm spec that will be evaluated by the rpm engine in the end so
> everything related to %{dist} generation that is used in those
> packages will work unchanged.
> 
> A small tweak in those spec files to allow dynamic release bumping
> could be:
> 
> Release: 0.<>%{?dist}
> 
> or alternatively:
> 
> Release: <>%{?dist} depending on the
> implementation of the dynamic_release macro.

Yes, something like that would be possible, my worry was essentially
about not snipping commit info from automated changelogs.

%{dynrel} should default to 1 if buildsys info is not available

Regards,

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

Re: Build into < Rawhide side tag fails with "Package ... has already been built"

[Clement Verna]

On Thu, 27 Feb 2020 at 14:14, Richard W.M. Jones  wrote:

> Despite earlier concerns, this does in fact appear to all be working fine.
>

Yes requesting and building in the side tag should work just fine.


>
> There are now F32 builds going through for all OCaml packages in a
> side tag, and when that's done I'll try to create a Bodhi update.
>

This is where you are going to have some problems, the deployed version of
Bodhi is not yet ready to support side tags for other release than rawhide.
A new release of Bodhi with that support should arrive soon tho.


>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1795119] Upgrade perl-Time-Local to 1.30

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1793146] perl-Module-CoreList-5.20200120 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1794960] perl-perlfaq-5.20200125 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1787958] perl-DB_File-1.853 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1791932] perl-autodie-2.32 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1788685] perl-autodie-2.30 is available

[bugzilla]

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



--- Comment #16 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1793146] perl-Module-CoreList-5.20200120 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1794960] perl-perlfaq-5.20200125 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1793459] perl-ExtUtils-CBuilder-0.280234 is available

[bugzilla]

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



--- Comment #16 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1805554] perl-Module-CoreList-5.20200220 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1786801] perl-Encode-3.02 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1793459] perl-ExtUtils-CBuilder-0.280234 is available

[bugzilla]

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



--- Comment #15 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1792861] perl-Exporter-5.74 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1795119] Upgrade perl-Time-Local to 1.30

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1785827] perl-Module-CoreList-5.20191220 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3120200220085657.a5d38390 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-cc0fdb630a

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

[Bug 1785827] perl-Module-CoreList-5.20191220 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1784658] perl-ExtUtils-MakeMaker-7.42 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1806215] perl-experimental-0.021 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1797226] perl-Archive-Tar-2.36 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1792861] perl-Exporter-5.74 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1784170] perl-ExtUtils-MakeMaker-7.40 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1791036] perl-ExtUtils-MakeMaker-7.44 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1788685] perl-autodie-2.30 is available

[bugzilla]

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



--- Comment #15 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1786801] perl-Encode-3.02 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1787958] perl-DB_File-1.853 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1791932] perl-autodie-2.32 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3120200224141406.a9ea5770 has been pushed to the Fedora 31 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-f5ba9cea28

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

[Bug 1793459] perl-ExtUtils-CBuilder-0.280234 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1787958] perl-DB_File-1.853 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1794960] perl-perlfaq-5.20200125 is available

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1793146] perl-Module-CoreList-5.20200120 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1791932] perl-autodie-2.32 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1788685] perl-autodie-2.30 is available

[bugzilla]

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



--- Comment #14 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1795119] Upgrade perl-Time-Local to 1.30

[bugzilla]

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



--- Comment #9 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1785827] perl-Module-CoreList-5.20191220 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1791036] perl-ExtUtils-MakeMaker-7.44 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1793459] perl-ExtUtils-CBuilder-0.280234 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1795119] Upgrade perl-Time-Local to 1.30

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1794960] perl-perlfaq-5.20200125 is available

[bugzilla]

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



--- Comment #10 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1784658] perl-ExtUtils-MakeMaker-7.42 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1786801] perl-Encode-3.02 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1786801] perl-Encode-3.02 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1792861] perl-Exporter-5.74 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1784170] perl-ExtUtils-MakeMaker-7.40 is available

[bugzilla]

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



--- Comment #7 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1792861] perl-Exporter-5.74 is available

[bugzilla]

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



--- Comment #12 from Fedora Update System  ---
perl-5.28-3020200220085657.eb1b2d95 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-9eb54c7af8

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

[Bug 1793146] perl-Module-CoreList-5.20200120 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1805554] perl-Module-CoreList-5.20200220 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1806215] perl-experimental-0.021 is available

[bugzilla]

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



--- Comment #8 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1785827] perl-Module-CoreList-5.20191220 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1797226] perl-Archive-Tar-2.36 is available

[bugzilla]

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



--- Comment #6 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1787958] perl-DB_File-1.853 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1791932] perl-autodie-2.32 is available

[bugzilla]

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



--- Comment #11 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1788685] perl-autodie-2.30 is available

[bugzilla]

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



--- Comment #13 from Fedora Update System  ---
perl-5.30-3020200224141406.bba63816 has been pushed to the Fedora 30 Modular
testing repository. If problems still persist, please make note of it in this
bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-8fd5ef4509

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

[Bug 1808079] New: perl-Cache-FastMmap for EL8

[bugzilla]

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

Bug ID: 1808079
   Summary: perl-Cache-FastMmap for EL8
   Product: Fedora EPEL
   Version: epel8
Status: NEW
 Component: perl-Cache-FastMmap
  Assignee: jpazdzi...@redhat.com
  Reporter: burnze...@gmail.com
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jpazdzi...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Hi,

Could you please build perl-Cache-FastMmap in EPEL 8 ?
It's in the dependency chain of a package I'd like to build for EPEL 8.

Thank you.

Regards,
BurnZero

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

[Bug 1806724] perl-HTTP-Message-6.22 is available

[bugzilla]

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



--- Comment #5 from Fedora Update System  ---
perl-HTTP-Message-6.22-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ebdc720b76

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

Re: Can not build new package: not in list for tag f33-updates-candidate

[Alejandro Álvarez Ayllón]

It works, thanks a lot!

El jue., 27 feb. 2020 18:02, Mohan Boddu  escribió:

> This should be fixed now, can you give it a try?
>
> On Thu, Feb 27, 2020 at 10:54 AM Alejandro Álvarez Ayllón
>  wrote:
> >
> > Hello all,
> >
> > I am trying to build sourcextractor++, which was accepted yesterday, and
> every time I try I get the following error:
> >
> > BuildError: package sourcextractor++ not in list for tag
> f33-updates-candidate
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=41969086
> >
> > I have seen some packages that were accepted at the same time, or even
> after, already built. And since I have two trailing '+' on the package
> name, I was wondering if this could have caused some kind of issue.
> >
> > Any hints?
> >
> >
> > --
> > Alejandro
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1806724] perl-HTTP-Message-6.22 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
perl-HTTP-Message-6.22-1.fc30 has been pushed to the Fedora 30 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-465920564b

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

[Bug 1804004] perl-PerlIO-Layers-0.012 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-PerlIO-Layers-0.012-1. |perl-PerlIO-Layers-0.012-1.
   |fc32|fc32
   |perl-PerlIO-Layers-0.012-1. |perl-PerlIO-Layers-0.012-1.
   |fc30|fc30
   ||perl-PerlIO-Layers-0.012-1.
   ||fc31



--- Comment #8 from Fedora Update System  ---
perl-PerlIO-Layers-0.012-1.fc31 has been pushed to the Fedora 31 stable
repository. If problems still persist, 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

taskotron going down for emergency maintenance

[Tim Flink]

The subject says it all, really.

Taskotron is having some problems with an internal component, it can't
wait for a better time and we need some downtime to fix it.

If all goes well, it should be back up shortly. I'll send another email
to update once we're done.

Tim


pgp4sFi8EO6c7.pgp
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

Re: Ideas and proposal for removing changelog and release fields from spec file

[clime]

On Thu, 27 Feb 2020 at 17:29, Nils Philippsen  wrote:
>
> On Thu, 2020-02-27 at 15:10 +0100, clime wrote:
> > Another thing to consider is whether we want a transparent build
> > system where all the description of what will happen when a spec file
> > is sent to it is included in the specfile itself or whether we want
>
> But we don't have that today: think of macros defined externally to the
> SPEC file and RPM which we use, think of "underspecified" build
> dependencies where what happens to be available and fulfil the BRs will
> be used and ultimately influence how the package is built. What happens
> when you build a package is already dependent on outside sources.
>
> > some auto-magic where e.g. 'Release' field or %changelog are
> > automatically inserted when missing (something like that is
> > impossible
> > right now due to rpm constraints but just to make a point).
>
> Again, this is opt-in. And the way this will be made opt-in is that
> people who want to use the feature use a macro, e.g.
> "%automatic_release", so that it is clear that some value will be
> filled in there. The idea isn't to have gutted spec files that don't
> build anywhere else than in our build system, one fixed requirement is
> that local builds using fedpkg or rpmbuild must continue to work.

Yes, that sounds good! I just wouldn't like too much when a build
system would be fiddling with spec files without some explicit macro
that everyone can see _in_ the spec file telling it explicitly to do
it - like e.g. changing values of some fields that packager manually
specified for some reason, e.g. auto correction.

>
> Nils
> --
> Nils Philippsen"Those who would give up Essential Liberty to
> Software Engineer   purchase a little Temporary Safety, deserve neither
> Red Hat Liberty nor Safety."  --  Benjamin Franklin, 1759
> PGP fingerprint:  D0C1 1576 CDA6 5B6E BBAE  95B2 7D53 7FCA E9F6 395D
> old:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ideas and proposal for removing changelog and release fields from spec file

[Zbigniew Jędrzejewski-Szmek]

On Tue, Feb 25, 2020 at 05:42:11PM +0100, Miro Hrončok wrote:
> On 25. 02. 20 9:50, Pierre-Yves Chibon wrote:
> >Upgrade path may be problematic if you update Fn to a version in less commit
> >than the update for Fn-1 (ie: you update F32 to 1.0 in 1 commit and update 
> >F31
> >to 1.0 in 2 commits, suddenly you have F32 with 1.0-1 and F31 with 1.0-2).
> 
> I don't consider that an issue. It's not super elegant, but since we
> do distro-sync on upgrades, it shuld be fine.

Hmm, I don't do distro-sync and in general I think upgrade path is
something that should be preserved.

What about doing --.?
This means that upgrade path not affected by the number of commits or
builds in the older release.

The numbers  in different branches cannot
be meaningfully compared. Those numbers only make sense in the context
of a specific branch, so they should be ordered after .

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

Re: Can not build new package: not in list for tag f33-updates-candidate

[Mohan Boddu]

This should be fixed now, can you give it a try?

On Thu, Feb 27, 2020 at 10:54 AM Alejandro Álvarez Ayllón
 wrote:
>
> Hello all,
>
> I am trying to build sourcextractor++, which was accepted yesterday, and 
> every time I try I get the following error:
>
> BuildError: package sourcextractor++ not in list for tag f33-updates-candidate
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=41969086
>
> I have seen some packages that were accepted at the same time, or even after, 
> already built. And since I have two trailing '+' on the package name, I was 
> wondering if this could have caused some kind of issue.
>
> Any hints?
>
>
> --
> Alejandro
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora rawhide compose report: 20200227.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20200226.n.0
NEW: Fedora-Rawhide-20200227.n.0

= SUMMARY =
Added images:3
Dropped images:  0
Added packages:  9
Dropped packages:1
Upgraded packages:   96
Downgraded packages: 0

Size of added packages:  91.55 MiB
Size of dropped packages:59.90 KiB
Size of upgraded packages:   4.21 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Server-dvd-s390x-Rawhide-20200227.n.0.iso
Image: Comp_Neuro live x86_64
Path: Labs/x86_64/iso/Fedora-Comp_Neuro-Live-x86_64-Rawhide-20200227.n.0.iso
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Server-netinst-s390x-Rawhide-20200227.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: cri-o-2:1.14.12-2.module_f33+8231+1f2b6587
Summary: Kubernetes Container Runtime Interface for OCI-based containers
RPMs:cri-o
Size:59.64 MiB

Package: cri-tools-1.14.0-1.module_f33+8220+3209ce5e
Summary: CLI and validation tools for Container Runtime Interface
RPMs:cri-tools
Size:27.74 MiB

Package: glyphography-newscycle-fonts-0.5.2-3.fc33
Summary: A realist sans-serif font family based on News Gothic
RPMs:glyphography-newscycle-fonts
Size:114.43 KiB

Package: ht-alegreya-sans-fonts-2.008-3.fc33
Summary: Alegreya Sans, a humanist sans serif font family with a calligraphic 
feeling
RPMs:ht-alegreya-sans-fonts
Size:1.45 MiB

Package: impallari-dancing-script-fonts-2.000-3.20200226gitf7f54bc.fc33
Summary: Dancing Script, a friendly, informal and spontaneous cursive font 
family
RPMs:impallari-dancing-script-fonts
Size:114.20 KiB

Package: jetbrains-mono-fonts-1.0.3-2.fc33
Summary: A monospace font family containing coding ligatures
RPMs:jetbrains-mono-fonts
Size:257.17 KiB

Package: nanovna-saver-0.2.2-3.fc33
Summary: Tool for reading, displaying and saving data from the NanoVNA
RPMs:nanovna-saver
Size:191.71 KiB

Package: perl-HarfBuzz-Shaper-0.018.4-2.fc33
Summary: Access to a small subset of the native HarfBuzz library
RPMs:perl-HarfBuzz-Shaper
Size:102.89 KiB

Package: weiweihuanghuang-work-sans-fonts-2.07-4.20200226gitdcd044c.fc33
Summary: Work Sans, a font family in the early grotesque style
RPMs:weiweihuanghuang-work-sans-fonts weiweihuanghuang-work-sans-fonts-doc
Size:1.96 MiB


= DROPPED PACKAGES =
Package: sugar-connect-22-24.fc31
Summary: Connect for Sugar
RPMs:sugar-connect
Size:59.90 KiB


= UPGRADED PACKAGES =
Package:  NetworkManager-l2tp-1.8.0-5.fc33
Old package:  NetworkManager-l2tp-1.8.0-4.fc33
Summary:  NetworkManager VPN plugin for L2TP and L2TP/IPsec
RPMs: NetworkManager-l2tp NetworkManager-l2tp-gnome
Size: 1.08 MiB
Size change:  1.99 KiB
Changelog:
  * Wed Feb 26 2020 Douglas Kosovic  - 1.8.0-4
  - Patch to support libreswan 3.30 which is no longer built with modp1024 
support

  * Thu Feb 27 2020 Douglas Kosovic  - 1.8.0-5
  - Patch for user certificate support fix


Package:  R-knitr-1.28-1.fc33
Old package:  R-knitr-1.26-2.fc32
Summary:  A General-Purpose Package for Dynamic Report Generation in R
RPMs: R-knitr
Size: 1.22 MiB
Size change:  3.43 KiB
Changelog:
  * Mon Feb 24 2020 Elliott Sales de Andrade  - 
1.28-1
  - Update to latest version


Package:  R-tinytex-0.20-1.fc33
Old package:  R-tinytex-0.19-1.fc33
Summary:  Helper Functions to Install and Maintain 'TeX Live', and Compile 
'LaTeX' Documents
RPMs: R-tinytex
Size: 115.49 KiB
Size change:  1.52 KiB
Changelog:
  * Wed Feb 26 2020 Elliott Sales de Andrade  - 
0.20-1
  - Update to latest version


Package:  R-uuid-0.1.4-1.fc33
Old package:  R-uuid-0.1.2-9.fc32
Summary:  Tools for generating and handling of UUIDs
RPMs: R-uuid
Size: 117.18 KiB
Size change:  3.72 KiB
Changelog:
  * Wed Feb 26 2020 Elliott Sales de Andrade  - 
0.1.4-1
  - Update to latest version


Package:  
arbor-0.2.2-6.20200225gitfb5d4ea736282dce14c3284bc5db748b082db957.fc33
Old package:  
arbor-0.2.2-5.20200223gitf12f934f365d9e68f01bfd857982be80da2ddd10.fc33
Summary:  Multi-compartment neural network simulation library
RPMs: arbor arbor-devel arbor-doc arbor-mpich arbor-mpich-devel 
arbor-openmpi arbor-openmpi-devel
Size: 312.04 MiB
Size change:  281.58 MiB
Changelog:
  * Wed Feb 26 2020 Ankur Sinha  - 
0.2.2-5.20200226gitfb5d4ea736282dce14c3284bc5db748b082db957
  - Use new snapshot that fixes errors on 32 bit systems
  - No longer excludes i686 and armv7hl
  - Drop unneeded patch.


Package:  avogadro2-1.93.0-1.fc33
Old package:  avogadro2-1.93.0-1.fc32
Summary:  Advanced molecular editor
RPMs: avogadro2
Size: 11.37 MiB
Size change:  -1.03 KiB

Package:  avogadro2-libs-1.93.0-1.fc33
Old package:  avogadro2-libs-1.93.0-1.fc32
Summary:  Avogadro2 libraries
RPMs

Re: OCaml 4.10.0 build in Fedora 32 and 33

[Kevin Fenzi]

On Thu, Feb 27, 2020 at 12:04:42PM +0100, Fabio Valentini wrote:
> 
> Yeah, because the updates-testing activation happened, which means
> that just submitting builds is not enough anymore.
> If you did things "normally", you'd need to create buildroot overrides
> for each build, wait, submit the next build, and repeat - which is
> obviously a painful process.
> 
> But since you're using a side tag, you should not need to create
> either buildroot overrides or individual updates, but just build
> everything in the side tag and create an update from the side tag
> contents. However, I'm not sure if bodhi can do that for non-rawhide
> branches yet. I also think this is only possible with the bodhi CLI,
> not from the web interface ... I hope somebody else can fill in the
> details here, this is all pretty new stuff and I haven't yet had a
> chance to create side-tag updates in bodhi myself.

Yeah, I think they work in "stable" releases, but I am not 100% sure
either. :) 

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

Re: OCaml 4.10.0 build in Fedora 32 and 33

[Kevin Fenzi]

On Thu, Feb 27, 2020 at 10:46:27AM +, Richard W.M. Jones wrote:
> 
> This is where I might need help.  I have a few questions:
> 
>  - There was something go on with Bodhi a few days ago which meant
>that you didn't want me to start this.  Can I start now?

We were enabling it on tuesday and entering into Beta freeze.

>  - Do I need to submit Bodhi updates for each build?  (Note I'll be
>building into an f32 side tag)

If you do a side tag it should get put into 1 big bodhi update. 

>  - If yes to the previous, can I short-circuit the need to wait for
>Bodhi updates?  I really hope I don't have to wait for each update
>to go through.

Right now it would need a accepted Freeze exception or an accepted
Blocker bug to get through bodhi to stable. 

https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
and you can propose them on:
https://qa.fedoraproject.org/blockerbugs/milestone/32/beta/buglist

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

[Bug 1804004] perl-PerlIO-Layers-0.012 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-PerlIO-Layers-0.012-1. |perl-PerlIO-Layers-0.012-1.
   |fc32|fc32
   ||perl-PerlIO-Layers-0.012-1.
   ||fc30
 Resolution|--- |ERRATA
Last Closed||2020-02-27 16:44:21



--- Comment #7 from Fedora Update System  ---
perl-PerlIO-Layers-0.012-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, 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

Fedora-32-20200227.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 25/160 (x86_64), 1/2 (arm)

New failures (same test not failed in Fedora-32-20200226.n.0):

ID: 528837  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/528837
ID: 528871  Test: x86_64 universal install_blivet_lvmthin
URL: https://openqa.fedoraproject.org/tests/528871
ID: 528896  Test: x86_64 universal install_blivet_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/528896

Old failures (same test failed in Fedora-32-20200226.n.0):

ID: 528801  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/528801
ID: 528803  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/528803
ID: 528824  Test: x86_64 Workstation-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528824
ID: 528827  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/528827
ID: 528834  Test: x86_64 Workstation-live-iso desktop_background
URL: https://openqa.fedoraproject.org/tests/528834
ID: 528842  Test: x86_64 KDE-live-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528842
ID: 528851  Test: x86_64 KDE-live-iso desktop_background
URL: https://openqa.fedoraproject.org/tests/528851
ID: 528858  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/528858
ID: 528870  Test: x86_64 universal install_simple_encrypted@uefi
URL: https://openqa.fedoraproject.org/tests/528870
ID: 528873  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/528873
ID: 528875  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/528875
ID: 528876  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/528876
ID: 528885  Test: x86_64 universal install_software_raid
URL: https://openqa.fedoraproject.org/tests/528885
ID: 528886  Test: x86_64 universal install_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/528886
ID: 528893  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/528893
ID: 528898  Test: x86_64 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/528898
ID: 528901  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/528901
ID: 528914  Test: x86_64 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/528914
ID: 528926  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/528926
ID: 528933  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/528933
ID: 528934  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/528934
ID: 528939  Test: x86_64 universal upgrade_2_realmd_client
URL: https://openqa.fedoraproject.org/tests/528939
ID: 528940  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/528940

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

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

ID: 528805  Test: x86_64 Server-dvd-iso realmd_join_sssd
URL: https://openqa.fedoraproject.org/tests/528805

Old soft failures (same test soft failed in Fedora-32-20200226.n.0):

ID: 528779  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/528779
ID: 528780  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528780
ID: 528782  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/528782
ID: 528784  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528784
ID: 528787  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/528787
ID: 528788  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/528788
ID: 528808  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/528808
ID: 528839  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/528839
ID: 528860  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/528860
ID: 528869  Test: x86_64 universal install_serial_console
URL: https://openqa.fedoraproject.org/tests/528869
ID: 528887  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/528887
ID: 528922  Test: x86_64 universal upgrade_2_kde_64bit
URL: 

Re: Ideas and proposal for removing changelog and release fields from spec file

[clime]

On Thu, 27 Feb 2020 at 16:26, Nicolas Mailhot via devel
 wrote:
>
> Le 2020-02-27 12:59, clime a écrit :
> Hi,
>
> >
> > can you, please, show an example of such package? I was searching
> > through some
> > golang packages because I was curious how it works but couldn't find
> > an example
>
> A Go example:
> https://src.fedoraproject.org/rpms/golang-x-build
>
> A non-Go example:
> https://src.fedoraproject.org/rpms/impallari-dancing-script-fonts
>
> In both cases the spec calls a macro (not the same one in both specs)
> that causes one or several disprefixNUMBER variables to be computed
>
> The result then ends in Release via
> https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/fedora-release.spec#_488
>
> The font spec example calls the macro in redhat-rpm-config directly, the
> go example calls it through a Go-specific macro in fonts-rpm-macros

Okay, thanks :)!

At least my idea was that there should be a spec file preprocessor,
evaluating the macros that need git context, that would produce valid
rpm spec that will be evaluated by the rpm engine in the end so
everything related to %{dist} generation that is used in those
packages will work unchanged.

A small tweak in those spec files to allow dynamic release bumping could be:

Release: 0.<>%{?dist}

or alternatively:

Release: <>%{?dist} depending on the
implementation of the dynamic_release macro.

clime

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

Re: Ideas and proposal for removing changelog and release fields from spec file

[Nils Philippsen]

On Wed, 2020-02-26 at 23:07 -0500, Neal Gompa wrote:
> On Wed, Feb 26, 2020 at 8:05 PM Robert-André Mauchin <
> zebo...@gmail.com> wrote:
> > On Monday, 24 February 2020 17:48:36 CET Pierre-Yves Chibon wrote:
> > > However, for the release field, we are struggling a little bit
> > > more, two
> > > options are more appealing to us:
> > > 
> > > A) The release field is automatically generated using two
> > > elements:
> > >   - the number of commits at this version
> > >   - the number of builds at this commit
> > >   - the dist-tag being added after them
> > >   The release field would thus look like:
> > > ``. > > commit>%{dist}``
> > > 
> > > So we could have:  (A, B, C and D being different commits)
> > >  A -- version: 0.9 -- release: ?
> > > 
> > >  |
> > > 
> > >  B -- version: 1.0 -- release: 1.0
> > > 
> > >  |
> > > 
> > >  C -- version: 1.0 -- release: 2.0
> > > 
> > >  |
> > > 
> > >  D -- version: 1.1 -- release: 1.0
> > > 
> > > A rebuild of the commit D, would lead to a release 1.1 (assuming
> > > the first
> > > one succeeded)/
> > > 
> > > Pros:
> > >  - Easy to replicate locally
> > >  - Every changelog entry can be mapped to a `version-release` (No
> > > changes to
> > > the packaging guidelines)
> > >  - Allows triggering two builds from the same commit without any
> > > manual
> > > change (simplifies mass-rebuilds)
> > >  - Easy to link a certain build with a specific commit
> > >  - Easy to “guess” the next release value before triggering the
> > > build
> > > 
> > > Cons:
> > >   - Old packages which are no longer receiving upstream releases
> > > may need
> > > special care (for example if they are at the release -48 but
> > > only had
> > > 45 commits leading to this)
> > >   -  Relies on information from the build system for the build
> > > number (but
> > > can be closely simulated locally since the  info is only
> > > used for
> > > rebuilds)
> > >   -  Upgrade path may be problematic if Fn is upgraded to version
> > > X with
> > > one commit while Fn-1 is upgrade to version X with 2 commits (or
> > > more)
> > > 
> > > B) The release field is automatically generated taking existing
> > > builds in
> > > all current Fedora releases (ie: rawhide, Fn, Fn-1...) into
> > > account. This
> > > means for builds of the same epoch:version, find a new release
> > > that (if at
> > > all possible) ensures upgradability from older Fedora versions to
> > > newer
> > > ones, adhering to the structure of a release tag documented in
> > > the
> > > Versioning Guidelines[1]. Going from the (RPM-wise) "latest
> > > build" that the
> > > new one should surpass, this can mean bumping in the front
> > > (`pkgrel`) or
> > > the back (`minorbump`).
> > > 
> > > This allows packages from "very stable" upstreams who haven't
> > > released in
> > > years to still benefit from automatically generated releases.
> > > 
> > > The following examples would use a macro for the release field as
> > > outlined
> > > in a separate document[2].
> > > 
> > > Example #1 ("normal" release progression):
> > >  Rawhide has: 2.0-1.fc32
> > >  F31 has: 1.0-1.fc31
> > >  F30 has: 1.0-1.fc30
> > > 
> > >  Next release in F31: 1.0-2.fc32
> > > 
> > > 
> > > Example #2 ("hotfix" in an older release, selected by an
> > > alternative macro
> > > (or option) in the spec file):
> > >  Rawhide has: 2.0-1.fc32
> > >  F31 has: 1.0-1.fc31
> > >  F30 has: 1.0-1.fc30
> > > 
> > >  Next release in F30: 1.0-1.fc30.1
> > > 
> > > Example #3 (pre-release, selected by an alternative macro (or
> > > option) in
> > > the spec file):
> > >  Rawhide has: 2.0-1.fc32
> > >  F31 has: 1.0-1.fc31
> > >  F30 has: 1.0-1.fc30
> > > 
> > >  Next release in Rawhide: 3.0-0.1.20200224git1234abcd
> > > 
> > > 
> > > Pros:
> > >   - Allows triggering two builds from the same commit without
> > > manual
> > > intervention
> > >   - Emulates what many maintainers do manually today for most use
> > > cases
> > >   - Can cater for pre-releases (e.g.: by offering different
> > > macros or macro
> > > options for the different use cases)
> > > 
> > > Cons:
> > >   - Needs the build system for information about builds in this
> > > and other
> > > Fedora versions
> > >   - Not easy to reproduce locally because we don’t have machine-
> > > consumable
> > > knowledge about other builds in e.g. the dist-git repo
> > >   - Does not allow to generate changelog entries with `version-
> > > release`
> > > information for all commits (and this will require a change
> > > in our
> > > packaging guidelines)
> > > 
> > > 
> > > So these are the results of our current investigations, we are
> > > very much
> > > eager  to get your feedback on them and even more eager if you
> > > have ideas
> > > on how to approach/solve some of the challenges mentioned here.
> > > 
> > > 
> > > Looking forward for the discussion,
> > > 
> > > Pierre
> > >   For Adam, Nils and myself
> > > 
> > > 
> > > 
> > 
> > How would that work with "complex" releases? For example 

Re: Ideas and proposal for removing changelog and release fields from spec file

[Nils Philippsen]

On Thu, 2020-02-27 at 15:10 +0100, clime wrote:
> Another thing to consider is whether we want a transparent build
> system where all the description of what will happen when a spec file
> is sent to it is included in the specfile itself or whether we want

But we don't have that today: think of macros defined externally to the
SPEC file and RPM which we use, think of "underspecified" build
dependencies where what happens to be available and fulfil the BRs will
be used and ultimately influence how the package is built. What happens
when you build a package is already dependent on outside sources.

> some auto-magic where e.g. 'Release' field or %changelog are
> automatically inserted when missing (something like that is
> impossible
> right now due to rpm constraints but just to make a point).

Again, this is opt-in. And the way this will be made opt-in is that
people who want to use the feature use a macro, e.g.
"%automatic_release", so that it is clear that some value will be
filled in there. The idea isn't to have gutted spec files that don't
build anywhere else than in our build system, one fixed requirement is
that local builds using fedpkg or rpmbuild must continue to work.

Nils
-- 
Nils Philippsen"Those who would give up Essential Liberty to
Software Engineer   purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety."  --  Benjamin Franklin, 1759
PGP fingerprint:  D0C1 1576 CDA6 5B6E BBAE  95B2 7D53 7FCA E9F6 395D
old:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1808002] New: perl-PPIx-Regexp-0.070 is available

[bugzilla]

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

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



Latest upstream release: 0.070
Current version/release in rawhide: 0.069-1.fc32
URL: http://search.cpan.org/dist/PPIx-Regexp/

Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/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/3288/

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

rpminspect Copr repository moving

[David Cantrell]

If you are using rpminspect and rpminspect-data-fedora from my Copr
repository, please note that it is moving.  The move is tied to my username
change that happened internally at Red Hat and then I mirrored in Fedora.  The
short story is that I can now have "dcantrell" as my username and discontinue
using "dcantrel".

THE NEW COPR REPO:

https://copr.fedorainfracloud.org/coprs/dcantrell/rpminspect

The previous one will be removed next week.  No new builds are happening in
the old repo.

Thanks,

--
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
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

Can not build new package: not in list for tag f33-updates-candidate

[Alejandro Álvarez Ayllón]

Hello all,

I am trying to build sourcextractor++, which was accepted yesterday, and
every time I try I get the following error:

BuildError: package sourcextractor++ not in list for tag
f33-updates-candidate

https://koji.fedoraproject.org/koji/taskinfo?taskID=41969086

I have seen some packages that were accepted at the same time, or even
after, already built. And since I have two trailing '+' on the package
name, I was wondering if this could have caused some kind of issue.

Any hints?


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

Fedora 32 compose report: 20200227.n.0 changes

[Fedora Branched Report]

OLD: Fedora-32-20200226.n.0
NEW: Fedora-32-20200227.n.0

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

Size of added packages:  0 B
Size of dropped packages:59.90 KiB
Size of upgraded packages:   0 B
Size of downgraded packages: 0 B

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

= ADDED IMAGES =

= DROPPED IMAGES =
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Server-netinst-s390x-32-20200226.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-32-20200226.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: sugar-connect-22-24.fc31
Summary: Connect for Sugar
RPMs:sugar-connect
Size:59.90 KiB


= UPGRADED PACKAGES =

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

Re: Ideas and proposal for removing changelog and release fields from spec file

[Nicolas Mailhot via devel]

Le 2020-02-27 12:59, clime a écrit :
Hi,



can you, please, show an example of such package? I was searching 
through some

golang packages because I was curious how it works but couldn't find
an example


A Go example:
https://src.fedoraproject.org/rpms/golang-x-build

A non-Go example:
https://src.fedoraproject.org/rpms/impallari-dancing-script-fonts

In both cases the spec calls a macro (not the same one in both specs) 
that causes one or several disprefixNUMBER variables to be computed


The result then ends in Release via
https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/fedora-release.spec#_488

The font spec example calls the macro in redhat-rpm-config directly, the 
go example calls it through a Go-specific macro in fonts-rpm-macros


Regards,

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

Re: Ideas and proposal for removing changelog and release fields from spec file

[Zbigniew Jędrzejewski-Szmek]

Hi,

On Mon, Feb 24, 2020 at 05:48:36PM +0100, Pierre-Yves Chibon wrote:
> For the changelog, we believe we have a potential good solution:
> - The changelog will be automatically generated using an external `changelog`
>   file as well as the commit history
...
> If you wanted to edit the changelog, you would:
> - Generate the changelog locally via a command like: 
>   `fedpkg generate-changelog > changelog`
> - Edit `changelog` as desired
> - Commit and push the changes

This means that a separate commit needs to be done *after* on top 
of the commits doing the actual changes. It's a bit disappointing, but
on its own would not be too bad, since we can have fedpkg provide a
higher level command that combines generate-changelog and build...

One important feature will work:
being able to cherry-pick commit between branches w/o spurious
conflicts. As long as the "real" change to the spec file are done in
separate commits, and the changelog commit is another commit on top,
then when cherry-picking to another branch, the "real" commits would
be cherry-pickable, and then the changelog commit would be recreated
using the automation, OK.

But it doesn't work quite as nicely with something similar: merging
branches. A simple 'git merge' would result in conflicts.

Also, if an amendment to the changelog is done, and the same change
needs to be done in the changelog in a different branch, trying to
cherry-pick the fix commit would most likely result in a merge
conflict.

Considering these three drawbacks (separate commit step and resulting
log noise, merge conflicts), I'd very much hope for a solution where
the changelog is never stored in the version control, and is always
autogenerated at srpm creation time. We should never try to chery-pick
commits that have changelog entries with actual date or e-v-r texts,
since this will inevitably lead to merge conflicts. 


A different approach:
- we have 'fedpkg generate-changelog' (which does all the git log
  extraction that was described, I think that part is OK),
- the output from this command included in the srpm at srpm generation
  time and never committed to version control,
- the output is annotated with the source commits hashes, so we can
  see where each line came from.

At any time, the packager can run 'fedpkg generate-changelog' to see
how the output looks like. If they see something they don't like, if
the commits haven't been pushed out yet, they can immediately run
'git commit --amend' and recheck. If they have been pushed out, an override
to the changelog could be committed as part of a commit message text.

Git-changelog-suppress: adb42e
or
Git-changelog-suppress: adb42e..efefedeadb
or
Git-changelog-replace: adb42e
  Some other text with typos fixed that completely overrides whatever
  was generated from adb42e.
or
Git-changelog-append: adb42e
  (additional clarification for commit adb42e, e.g. bug #12345)

This would have the following advantages:
- git log is the sole source of truth
- there are no cherry-pick or merge conflicts
- there is no separate "now I'm done and I need to do another commit
  before building" thing.

The assumption is that those Git-changelog-* macros would only be
used occasionally, if the bad changelog entry was not noticed before
pushing the changes out.

(One nitpick: when cherry-picking between branches, hashes of the
cherry-picked commits change, so "adb42e" in the example above
would stop working. This is handled by using 'git cherry-pick -x'.
'fedpkg generate-changelog' would look at any hash in a
"(cherry picked from commit ...)" line.)


As how to hook this up with rpm,
looking at 
https://pagure.io/packaging-committee/pull-request/942#comment-108542,
a macro like %generate_changelog could be provided that would 
simply shell out to 'fedpkg generate-changelog'.


I'll comment separate on the -release part.

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

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

[Fedora compose checker]

No missing expected images.

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

Failed openQA tests: 24/171 (x86_64), 1/2 (arm)

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

ID: 528630  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/528630
ID: 528632  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/528632
ID: 528635  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/528635
ID: 528653  Test: x86_64 Workstation-live-iso desktop_browser **GATING**
URL: https://openqa.fedoraproject.org/tests/528653
ID: 528657  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/528657
ID: 528700  Test: x86_64 universal install_blivet_lvmthin
URL: https://openqa.fedoraproject.org/tests/528700

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

ID: 528619  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/528619
ID: 528621  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/528621
ID: 528645  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/528645
ID: 528676  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/528676
ID: 528699  Test: x86_64 universal install_simple_encrypted@uefi
URL: https://openqa.fedoraproject.org/tests/528699
ID: 528702  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/528702
ID: 528704  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/528704
ID: 528705  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/528705
ID: 528714  Test: x86_64 universal install_software_raid
URL: https://openqa.fedoraproject.org/tests/528714
ID: 528715  Test: x86_64 universal install_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/528715
ID: 528722  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/528722
ID: 528727  Test: x86_64 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/528727
ID: 528730  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/528730
ID: 528743  Test: x86_64 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/528743
ID: 528755  Test: x86_64 universal upgrade_2_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/528755
ID: 528762  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/528762
ID: 528763  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/528763
ID: 528768  Test: x86_64 universal upgrade_2_realmd_client
URL: https://openqa.fedoraproject.org/tests/528768
ID: 528769  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/528769

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

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

ID: 528597  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/528597
ID: 528598  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528598
ID: 528600  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/528600
ID: 528602  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/528602
ID: 528605  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/528605
ID: 528606  Test: x86_64 Server-dvd-iso install_vnc_client
URL: https://openqa.fedoraproject.org/tests/528606
ID: 528626  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/528626
ID: 528655  Test: x86_64 Workstation-live-iso desktop_printing
URL: https://openqa.fedoraproject.org/tests/528655
ID: 528689  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/528689
ID: 528698  Test: x86_64 universal install_serial_console
URL: https://openqa.fedoraproject.org/tests/528698
ID: 528716  Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/528716
ID: 528751  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/528751
ID: 528754  Test: x86_64 universal upgrade_2_server_64bit
URL: 

Re: State of FMN (FedMSG Notifications) and Replacement

[Jeremy Cline]

On Wed, 2020-02-26 at 13:03 -0800, Kevin Fenzi wrote:
> On Wed, Feb 26, 2020 at 02:45:24PM +, Jeremy Cline wrote:
> > FYI before I left the team I started hacking up a replacement[0].
> > My
> > design focused on how to get as rich a feature set as I could using
> > only AMQPs currently available filtering features. There's a couple
> > feature differences for end-users:
> > 
> > * Users can filter on message importance based on
> >   fedora_messaging_severity and any documented optional header[1].
> >   Users can also provide AMQP-formatted topics they'd like to
> > receive
> >   notifications for (again, with a severity filter). There's no
> > running
> >   arbitrary regex over messages to filter.
> 
> That may be enough. I guess we will need to look at the use cases
> here
> and see if there's other ones that need some kind of regex... 

My recommendation for that is if there are things that can't be matched
with current topics, change the topic (you can publish the message
twice with different topics to retain compatibility for some period of
time). Topics are entirely designed for filtering messages, ours just
aren't very good.

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

Re: Ideas and proposal for removing changelog and release fields from spec file

[clime]

On Thu, 27 Feb 2020 at 13:23, clime  wrote:
>
> On Thu, 27 Feb 2020 at 12:42, David Kaufmann  wrote:
> >
> > On Thu, Feb 27, 2020 at 12:21:48PM +0100, clime wrote:
> > > On Thu, 27 Feb 2020 at 10:00, David Kaufmann  wrote:
> > >> Another idea would be generating a changelog-entry from git history when
> > >> creating an update in bodhi, and there is no pre-existing
> > >> changelog-entry for the current version.
> > >
> > > But Bodhi changelogs is not what user can read on his/her machine when
> > > examining e.g. dnf check-update --changelogs. These are imho rpm
> > > changelogs. So the rpm spec changelogs are the most important.
> >
> > Ah, sorry, what I meant to say is bodhi modifying the .spec file, adding
> > the changelog line, and committing it, before building the package.
> > (similarly like the releng commits when rebuilding stuff for new
> > releases)
> >
> > But when I am thinking more about it I think it won't work, as bodhi
> > would need to rebuild the package then. (afaik it does not, as koji
> > built it already)
>
> Ah, right, I understand now. Thank you for the explanation!
>
> >
> > An alternative might be something like modifying "fedpkg build" to check
> > for missing changelogs and ask something like:
> >
> > "your package does not contain a changelog entry for . should
> > we add the following entryies to the changelog for ?:  > commit-messages>"
> >
> > maybe even with the option of modifying the lines?
>
> That would be possible, yes, but then fedpkg build would need
> to create additional commit to maintain what user have inputed
> so that it is remembered somewhere and present in the resulting rpm,
> i.e. it would probably need to change repository and do a push during
> the build launching.
>
> I had a similar idea but executed earlier. When` fedpkg tag` is invoked
> (packagers usually don't invoke it today), a test-editor window is opened that
> can be prepopulated from commit message but it could also be prepopulated
> from an external file depending on configuration. Here user can compose
> the final changelog record for the given release and this record is then 
> stored
> in the newly created tag (in its annotation) and from there it is 
> automatically
> (through a dedicated macro if used) rendered into spec file when needed
> (e.g. when srpm is built).
>
> It requires one more step (i.e. fepkg commit -> fedpkg tag -> fedpkg
> push -> fedpkg build)
> but the build can be also launched automatically if a new tag is
> pushed so the number
> of steps would be the same.

Actually, I thought about your idea doing it during `fedpkg build`
(create the changelog record and push) and I started to like it more
and more because people wouldn't need to run any extra
commands compared to today when they would like to use the new macros.

This could be only an opt-in feature
(create_changelog_and_push_before_build or similar) cause some people
will not want this.

There are two ways how to create such record and push it without
actually changing HEAD commit (which would be good cause otherwise we
would be building different commit then we launched the command on,
which would lead to confusion)

1) git notes: mutable text records that can be attached to any commit
probably or tag in a git repo (see $ man git notes) and they have a
separate history
2) git's annoted tags: tags with immutable text records and timestamps
that can be signed and are checksummed.

This is a direction of thought where the changelog is stored in git
metadata. Proposal with the external changelog file in the repository
is, instead, a direction where the changelog is stored in git data
(well partially data and partially metadata because of the commit
message fallback) - it's a bit different.

Another thing to consider is whether we want a transparent build
system where all the description of what will happen when a spec file
is sent to it is included in the specfile itself or whether we want
some auto-magic where e.g. 'Release' field or %changelog are
automatically inserted when missing (something like that is impossible
right now due to rpm constraints but just to make a point).

>
> A disadvantage is that the spec file is not standalone with respect to
> important information.
> It can be, however, made standalone at any time by "rendering" it,
> i.e. process when the
> macros are replaced by the actual information pulled from git (the
> command to do it
> could be e.g. fedpkg spec).
>
> >
> > All the best,
> > Astra
> > ___
> > 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
___

Schedule for Thursday's FPC Meeting (2020-02-27 17:00 UTC)

[James Antill]

 Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2020-02-27 17:00 UTC in #fedora-meeting-1 on 
irc.freenode.net.

 Local time information (via. uitime):

= Day: Thursday ==
2020-02-27 09:00 PST  US/Pacific
2020-02-27 12:00 EST  --> US/Eastern <--
2020-02-27 17:00 GMT  Europe/London 
2020-02-27 17:00 UTC  UTC   
2020-02-27 18:00 CET  Europe/Berlin 
2020-02-27 18:00 CET  Europe/Paris  
2020-02-27 22:30 IST  Asia/Calcutta 
 New Day: Friday -
2020-02-28 01:00 HKT  Asia/Hong_Kong
2020-02-28 01:00 +08  Asia/Singapore
2020-02-28 02:00 JST  Asia/Tokyo
2020-02-28 03:00 AEST Australia/Brisbane


 Links to all tickets below can be found at: 

https://pagure.io/packaging-committee/issues?status=Open=meeting

= Followups =

#topic #907 Which %__foo macros for executables are acceptable? 
.fpc 907
https://pagure.io/packaging-committee/issue/907

#topic #909 Suggest that linting/measuring-coverage is not for %check
.fpc 909
https://pagure.io/packaging-committee/issue/909

= Pull Requests =

#topic #pr-814 Add SELinux Independent Policy Guidelines 
https://pagure.io/packaging-committee/pull-request/814

#topic #pr-938 Add Package Review Process page 
https://pagure.io/packaging-committee/pull-request/938

= Open Floor = 

 For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at:

https://pagure.io/packaging-committee/issues?status=Open=meeting

 If you would like to add something to this agenda, you can:
  * Reply to this e-mail
  * File a new ticket at: https://pagure.io/packaging-committee
  * E-mail me directly
  * Bring it up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Cross-arch dependencies for plugins (NSS and others)

[Florian Weimer]

I submitted a patch for redhat-rpm-config:

  

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

Re: Build into < Rawhide side tag fails with "Package ... has already been built"

[Richard W.M. Jones]

Despite earlier concerns, this does in fact appear to all be working fine.

There are now F32 builds going through for all OCaml packages in a
side tag, and when that's done I'll try to create a Bodhi update.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
___
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