Re: Non-responsive maintainer

[Michal Srb]

/me sending the email second time as the first attempt bounced back to me

Hi Greg,

Thanks for bringing this to my attention. The package is, unfortunately,
broken in all supported Fedora releases. The version of the package is the
last stable release from 1.x branch, but upstream is now (and has been for
quite some time) on 2.x. Upgrading it to 2.x wouldn't be easy by any means,
it would require a ton of time (weeks, easily...) that unfortunately I
don't have at the moment and most likely won't have in foreseeable future.

So I am going to do what I should have done a long time ago - I am going to
retire the package.

I will send a separate email that I am orphaning it (and its dependencies)
and if nobody takes it over, I will just retire it in a week or so.

Thanks,
Michal

On Fri, Aug 30, 2019 at 7:45 AM Michal Srb  wrote:

> Hi Greg,
>
> Thanks for bringing this to my attention. The package is, unfortunately,
> broken in all supported Fedora releases. The version of the package is the
> last stable release from 1.x branch, but upstream is now (and has been for
> quite some time) on 2.x. Upgrading it to 2.x wouldn't be easy by any means,
> it would require a ton of time (weeks, easily...) that unfortunately I
> don't have at the moment and most likely won't have in foreseeable future.
>
> So I am going to do what I should have done a long time ago - I am going
> to retire the package.
>
> I will send a separate email that I am orphaning it (and its dependencies)
> and if nobody takes it over, I will just retire it in a week or so.
>
> Thanks,
> Michal
>
> On Thu, Aug 29, 2019 at 7:50 PM Greg Hellings 
> wrote:
>
>> The jenkins pacakge is fearfully out of date and seems unmaintained. Does
>> anyone know how to get in touch with the maintainer(s) of the package?
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1560603
>>
>> --Greg
>>
>
___
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 2019-08-30 - 96% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2019/08/30/report-389-ds-base-1.4.1.6-20190829git43f7b99.fc30.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org

[389-devel] Please review 50576 map uid/gid of proc to dm over ldapi

[William Brown]

https://pagure.io/389-ds-base/pull-request/50577
https://pagure.io/389-ds-base/issue/50576

--
Sincerely,

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 3:50:19 AM MST Iñaki Ucar wrote:
> Responding to the first message because I'm not interested in further
> discussion. It's clear to me that there will be no agreement in this
> matter unless there are reasonable potential alternatives. Therefore,
> this message is just to let you all know that I'm at least trying to
> push for better alternatives. In particular, these:
> 
> https://bugs.kde.org/show_bug.cgi?id=411359
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/1550
> https://gitlab.gnome.org/GNOME/gnome-control-center/issues/650
> 
> You are welcome to help with the above, or bring them to other
> desktops. Hopefully, if these proposals get accepted and implemented,
> we could eventually bring back this discussion and reach some
> consensus.

In GNOME, it used to be a dropdown with these default options:
home
public
trusted
work

I don't see how this could possibly be too confusing for "non-power users". 
Just default it to something safe, like "public", is what I'd suggest. That's 
what the default used to be. Additionally, I can't see anything that can be 
enabled using GNOME's GUIs, other than VNC, which would bind ports.

KDE has that as a dropdown right now, and the KDE Spin is not affected by the 
decision of the GNOME folks.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 1:11:02 PM MST Chris Murphy wrote:
> On Thu, Aug 29, 2019 at 12:24 AM Chris Murphy 
> wrote:
> >
> >
> > Debian has a permissive firewall
> > https://wiki.debian.org/DebianFirewall
> 
> 
> And Ubuntu, Mint, elementary, MX Linux, Solus, pop!_OS, as well. By
> permissive, they all accept everything. Nothing is rejected or
> dropped.
> 
> Mageia, and openSUSE do have a fair amount of iptables filtering
> entries. e.g. openSUSE Tumbleweed lastest snapshot,
> https://paste.fedoraproject.org/paste/TOJ1cdZpRWy2150N2O~IOw/raw
> 
> I didn't test Zorin because I couldn't get passed the paywall, and for
> some reason Manjaro boots (kernel and initramfs) but then hangs during
> startup and I don't really want to troubleshoot it.
> 
> Anyway, that rounds out the top ~10 distros, and Fedora Workstation is
> definitely not the most permissive.

That Ubuntu and a handful of obscure distros do something does not mean that's 
a good idea. These systems, except for Debian, also don't have SELinux or 
AppArmor enabled by default.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 8:34:09 AM MST Christophe de Dinechin wrote:
> mcatanz...@gnome.org writes:
> 
> 
> > Well the thing is, blocknig ports tends to break applications that want
> > to use those ports. We're not going to do that, period. It also doesn't
> > really accomplish anything: either your app or service needs network
> > access and you have whitelisted it (in which case the firewall provides
> > no security), or it needs network access and you have not whitelisted
> > it (in which case your firewall breaks your app/service). In no case
> > does it increase your security without breaking your app, right? Unless
> > you have malware installed (in which case, you have bigger problems
> > than the firewall). Or unless you have a vulnerable network service
> > installed that you don't want (in which case, uninstall it).
> >
> >
> >
> > So if you want to change the firewall settings, you'd need to
> > completely rethink how the firewall works. And nobody seems interested
> > in doing that. We could e.g. have a list of apps that are allowed
> > network access, but then we'd need some form of attestation so apps
> > can't impersonate each other. So only sandboxed (flatpaked) apps could
> > use this hypothetical new firewall. And we surely don't want to have
> > yes/no permission prompts, so we can't really ask the user "do you want
> > your app to access the network?" (the user will almost always say
> > yes).
> 
> 
> For what it's worth, macOS started doing exactly that recently.
> I agree it seems useless, except for one thing. Sometimes, you realize
> that some app is opening a port when you don't expect it.
> 
> 
> > I'm not really sure what design would even work.
> >
> >
> >
> > Avoiding unnecessary network services makes more sense.
> >
> >
> >
> > On Mon, Aug 26, 2019 at 3:45 PM, Alexander Ploumistos
> >  wrote:
> > 
> >>
> >>
> >> As a matter of fact, you did:
> >>  >> org/thread/3LHDQD5HCZMPV6O4LZRSKTVEIKEFJIBY/#3LHDQD5HCZMPV6O4LZRSKTVEIKEF
> >> JIBY>
> >>  
> >> >> Products.html#idm225474210784>>
> >
> >
> > Thanks for dredging up these links!
> >
> >
> >
> > Michael
> >
> >
> >
> > ___
> > 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.o
> > rg
> 
> 
> --
> Cheers,
> Christophe de Dinechin (IRC c3d)
> ___
> 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

Thing is, binding a port and expecting it to be open to every network 
interface you've got are two very different things.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 5:29:32 PM MST Christopher wrote:
> Workstation is the primary product. Some choose that not for GNOME...
> but because they want to start with the most base product and
> customize from there. If you start with a Spin, you may get something
> pre-configured in a very weird way... and with a smaller support
> community.

Workstation is only the primary product because somebody decided GNOME was the 
best default. This should be reconsidered, so that the various Spins, the 
GNOME Spin, KDE Spin, XFCE Spin and so on have equal standing. At least the 
most common two. This obviously isn't my decision to make, nor does my 
position on it really matter, but that is my opinion, and I believe it isn't 
so unfounded.

> In any case, what users do with the Workstation product isn't the
> point at all. The point is that the problem at hand is the
> firewalld.conf file, and *NOT* anything to do with the GNOME
> experience itself, or any part of any GNOME packages.

Well, the Workstation product is the GNOME Spin. It is *the* GNOME experience 
in Fedora. I do agree with "what users do with the Workstation product isn't 
the point at all", as it's not like we can predict what people will do with 
their system after it's installed.

> Yikes! Making a particular (graphical or otherwise) environment
> mandatory is a frightening idea for a Linux distro. "Have it your way"
> is what separates Linux from proprietary OSes.

I completely agree. It's what brought me to Fedora.

> Agreed, but nobody suggested that. Writing a kickstart specifically
> for the Workstation product seems like a sane thing to do if you want
> to PXE boot and automate a custom install based on Workstation for
> your entire office / school / library that you support as an IT
> person. And, to loop it back to the main point of this thread... if
> you were to do that, unless you took special steps to clobber
> firewalld.conf with your own, you'd be affected by the firewalld.conf
> default configuration without ever logging in to GNOME on any of those
> workstations. Again, the problem isn't GNOME... it's firewalld's
> default configuration in Workstation.

Writing a kickstart for Workstation would require you to base your package 
list on that of the Workstation kickstart.

The issue is not firewalld.conf, it's the package that Workstation pulls in 
through the group workstation-product, fedora-release-workstation.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 11:17:11 AM MST Japheth Cleaver wrote:
> On 8/29/2019 8:10 AM, Adam Williamson wrote:
> 
> > On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote:
> > 
> >> On Wed, Aug 28, 2019 at 8:56 PM John Harris 
> >> wrote:
> >> 
> >>> It might be okay to be a GNOME-specific thing, as that's the only spin
> >>> of
> >>> Fedora which is affected by this decision.
> >>>
> >>>
> >>>
> >> The default firewall config affects every user of that edition, even
> >> if they never use GNOME (or even use graphical boot). So, I don't know
> >> if this would be adequate.
> > 
> > Why would you install Workstation if you didn't intend to use GNOME?
> 
> 
> That would seem to be a reasonable question, but if it's possible to do 
> so then it is bound to happen... It may be a symptom of unclear definition.
> 
> If Workstation is going to require a graphical environment for 
> reasonable usage/administration/whatever, then it should be made 
> mandatory somehow. It would also help clarify that the Workstation, 
> Server, and  Products must be treated distinctly... and that you 
> shouldn't just point your kickstart file at whatever ISO you happen to 
> have laying around.

It shouldn't matter which ISO you use, as the package wouldn't be installed 
unless the kickstart pulls it in.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

Re: Fedora Workstation and disabled by default firewall

[John Harris]

On Thursday, August 29, 2019 8:12:22 AM MST Dan Book wrote:
> I would agree, but people do install multiple desktops after installing a
> spin. Such a use case needs to be considered (not sure if it matters,
> though).

This is definitely not the ideal scenario, especially not from the case of the 
installer for the GNOME spin. I don't know if there's really any reason to 
consider it, as the user is taking things into their own hands at that point.

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

[Bug 1744361] Please build perl-MIME-tools for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #3 from Fedora Update System  ---
perl-Convert-BinHex-1.125-13.el8, perl-MIME-tools-5.509-9.el8 has been pushed
to the Fedora EPEL 8 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-EPEL-2019-05ebcc9682

-- 
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 1744701] [RFE] EPEL8 branch of perl-Authen-PAM

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-Authen-PAM-0.16-37.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-93041ebd8a

-- 
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 1746531] Please build perl-BerkeleyDB for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-BerkeleyDB-0.63-2.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-8c1c1a8600

-- 
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 1746533] Please build perl-Convert-TNEF for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-Convert-TNEF-0.18-17.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-f23604e655

-- 
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 1744676] [RFE] EPEL8 branch of perl-BSD-Resource

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #8 from Fedora Update System  ---
perl-BSD-Resource-1.291.100-11.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-adad709d1d

-- 
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 1746534] Please build perl-File-LibMagic for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-File-LibMagic-1.16-9.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-218a58cedd

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-de...@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-de...@lists.fedoraproject.org

[Bug 1744692] [RFE] EPEL8 branch of perl-XML-Entities

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-XML-Entities-1.0002-12.el8 has been pushed to the Fedora EPEL 8 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-EPEL-2019-eda1e2ebc4

-- 
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 1744360] Please build perl-Convert-BinHex for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
perl-Convert-BinHex-1.125-13.el8, perl-MIME-tools-5.509-9.el8 has been pushed
to the Fedora EPEL 8 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-EPEL-2019-05ebcc9682

-- 
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: Non-responsive maintainer

[John Harris]

On Thursday, August 29, 2019 11:11:43 AM MST Fabio Valentini wrote:
> On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings 
> wrote:
> >
> >
> > The jenkins pacakge is fearfully out of date and seems unmaintained. Does
> > anyone know how to get in touch with the maintainer(s) of the package?
>
> >
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1560603
> 
> 
> It's not only out of date, but also hilariously broken. Just check this
> page: https://apps.fedoraproject.org/koschei/search?q=jenkins
> 
> Most of the packaged jenkins plugins have already been retired for
> fedora 31+, and jenkins itself is broken because a lot of its
> dependencies have been retired as well.
> 
> Judging by the state of the Java stack in fedora, I'd recommend some
> kind of container workflow that doesn't actually include fedora
> packages for jenkins.
> Another approach might be for you to join the Java SIG and revive
> jenkins in fedora (which would require a lot of work).

I would recommend Jenkins be installed in the vendor supported method. I fail 
to see how containers would be useful here, but the correct way to do that in 
a container would be in the method described here:

https://fedoramagazine.org/container-technologies-fedora-systemd-nspawn/

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

[Bug 1743746] perl-Module-CoreList-5.20190820 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2019 |perl-Module-CoreList-5.2019
   |0820-1.fc31 |0820-1.fc31
   |perl-Module-CoreList-5.2019 |perl-Module-CoreList-5.2019
   |0820-1.fc30 |0820-1.fc30
   ||perl-Module-CoreList-5.2019
   ||0820-1.fc29



--- Comment #7 from Fedora Update System  ---
perl-Module-CoreList-5.20190820-1.fc29 has been pushed to the Fedora 29 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

[Bug 1743742] perl-CPAN-Perl-Releases-4.12 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CPAN-Perl-Releases-4.1 |perl-CPAN-Perl-Releases-4.1
   |2-1.fc32|2-1.fc32
   |perl-CPAN-Perl-Releases-4.1 |perl-CPAN-Perl-Releases-4.1
   |2-1.fc31|2-1.fc31
   |perl-CPAN-Perl-Releases-4.1 |perl-CPAN-Perl-Releases-4.1
   |2-1.fc30|2-1.fc30
   ||perl-CPAN-Perl-Releases-4.1
   ||2-1.fc29



--- Comment #6 from Fedora Update System  ---
perl-CPAN-Perl-Releases-4.12-1.fc29 has been pushed to the Fedora 29 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

[Bug 1740546] Upgrade perl-Getopt-Long to 2.51

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Getopt-Long-2.51-1.fc3 |perl-Getopt-Long-2.51-1.fc3
   |1   |1
   |perl-Getopt-Long-2.51-1.fc3 |perl-Getopt-Long-2.51-1.fc3
   |0   |0
   ||perl-Getopt-Long-2.51-1.fc2
   ||9



--- Comment #7 from Fedora Update System  ---
perl-Getopt-Long-2.51-1.fc29 has been pushed to the Fedora 29 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

Re: Fedora Workstation and disabled by default firewall

[Christopher]

On Thu, Aug 29, 2019 at 2:18 PM Japheth Cleaver  wrote:
>
> On 8/29/2019 8:10 AM, Adam Williamson wrote:
> > On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote:
> >> On Wed, Aug 28, 2019 at 8:56 PM John Harris  wrote:
> >>> It might be okay to be a GNOME-specific thing, as that's the only spin of
> >>> Fedora which is affected by this decision.
> >>>
> >> The default firewall config affects every user of that edition, even
> >> if they never use GNOME (or even use graphical boot). So, I don't know
> >> if this would be adequate.
> > Why would you install Workstation if you didn't intend to use GNOME?
>
> That would seem to be a reasonable question, but if it's possible to do
> so then it is bound to happen... It may be a symptom of unclear definition.

Workstation is the primary product. Some choose that not for GNOME...
but because they want to start with the most base product and
customize from there. If you start with a Spin, you may get something
pre-configured in a very weird way... and with a smaller support
community.

In any case, what users do with the Workstation product isn't the
point at all. The point is that the problem at hand is the
firewalld.conf file, and *NOT* anything to do with the GNOME
experience itself, or any part of any GNOME packages.

>
> If Workstation is going to require a graphical environment for
> reasonable usage/administration/whatever, then it should be made
> mandatory somehow. It would also help clarify that the Workstation,

Yikes! Making a particular (graphical or otherwise) environment
mandatory is a frightening idea for a Linux distro. "Have it your way"
is what separates Linux from proprietary OSes.

> Server, and  Products must be treated distinctly... and that you
> shouldn't just point your kickstart file at whatever ISO you happen to
> have laying around.

Agreed, but nobody suggested that. Writing a kickstart specifically
for the Workstation product seems like a sane thing to do if you want
to PXE boot and automate a custom install based on Workstation for
your entire office / school / library that you support as an IT
person. And, to loop it back to the main point of this thread... if
you were to do that, unless you took special steps to clobber
firewalld.conf with your own, you'd be affected by the firewalld.conf
default configuration without ever logging in to GNOME on any of those
workstations. Again, the problem isn't GNOME... it's firewalld's
default configuration in Workstation.
___
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: svnmailer orphaned

[Nico Kadel-Garcia]

> On Aug 27, 2019, at 8:01 AM, Paul Howarth  wrote:
> 
> Hi all,
> 
> the svnmailer package has recently been orphaned and will be retired if
> nobody picks it up.
> 
> The package provides a tool to email emailed notifications of events in
> subversion repositories. It is written in Python (2) and is dead
> upstream. Anyone looking to take over the package should bear in mind
> that they will not get any help from upstream in porting it to Python 3.
> 
> 

Given the general migration of subversion users to git worldwide, I don’t think 
it’s a significant loss.
___
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: [HEADS-UP]: Mercurial with Python3 on rawhide?

[Nico Kadel-Garcia]

> On Aug 26, 2019, at 7:57 AM, Neal Becker  wrote:
> 
> It is intended for both py2 and py3 packages to be parallel installed, 
> correct?

They are supposed to be entirely distinct binary rpms, even if built from the 
same stone. *By convention*, the non-numbered binary is the linked to the 
system default version of python.

Personally, I’d have been glad to wait a few more years before ending this 
practice. But eagerness to force python3 as a default may force advises to 
demand its removal.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Workstation and disabled by default firewall

[Christopher]

On Thu, Aug 29, 2019 at 4:12 PM Chris Murphy  wrote:
>
> On Thu, Aug 29, 2019 at 12:24 AM Chris Murphy  wrote:
> >
> > Debian has a permissive firewall
> > https://wiki.debian.org/DebianFirewall
>
> And Ubuntu, Mint, elementary, MX Linux, Solus, pop!_OS, as well. By
> permissive, they all accept everything. Nothing is rejected or
> dropped.
>
> Mageia, and openSUSE do have a fair amount of iptables filtering
> entries. e.g. openSUSE Tumbleweed lastest snapshot,
> https://paste.fedoraproject.org/paste/TOJ1cdZpRWy2150N2O~IOw/raw
>
> I didn't test Zorin because I couldn't get passed the paywall, and for
> some reason Manjaro boots (kernel and initramfs) but then hangs during
> startup and I don't really want to troubleshoot it.
>
> Anyway, that rounds out the top ~10 distros, and Fedora Workstation is
> definitely not the most permissive.
>
>
> --
> Chris Murphy

It's my understanding that most of these don't do SELinux either. I
choose Fedora (and RH) products because I like the extra thought put
into security that other distros haven't necessary done. If I wanted
an insecure system, I'd have selected one of the countless ones listed
in this thread that people insist on comparing Fedora's firewall to.
___
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: python38-3.8.0~b3-1.fc30 on my f30 machine? how?

[Miro Hrončok]

On 29. 08. 19 23:54, Kevin Kofler wrote:

Miro Hrončok wrote:

Also this bugzilla was open to let users remove them and not get them
again when the package that recommends them updates, but the dnf team
disagrees:

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


Maybe it would be time for FESCo to require them to implement usable
behavior there? The people who want it (like me) are not familiar with the
code, and the people familiar with the code refuse to do anything.


FESCo cannot require anyone to implement anything. Fedora is a community 
volunteer project after all.



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

Re: Debates/back and forths

[John Harris]

On Thursday, August 29, 2019 2:54:57 AM MST Chris Peters wrote:
> PS I won't take this thread any further. The irony of a back and forth in
> the back and forth thread doesn't escape me!

I couldn't disagree with that any more!!!

-- 
John M. Harris, Jr. 
Splentity
https://splentity.com/

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

[Bug 1397732] CVE-2015-8978 perl-SOAP-Lite: XML exponential entity expansion denial-of-service [epel-all]

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #7 from Fedora Update System  ---
perl-SOAP-Lite-1.10-2.el7 has been pushed to the Fedora EPEL 7 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-EPEL-2019-ca3444781e

-- 
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 1743746] perl-Module-CoreList-5.20190820 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Module-CoreList-5.2019 |perl-Module-CoreList-5.2019
   |0820-1.fc31 |0820-1.fc31
   ||perl-Module-CoreList-5.2019
   ||0820-1.fc30
 Resolution|--- |ERRATA
Last Closed||2019-08-29 22:06:14



--- Comment #6 from Fedora Update System  ---
perl-Module-CoreList-5.20190820-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

[Bug 1743742] perl-CPAN-Perl-Releases-4.12 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-CPAN-Perl-Releases-4.1 |perl-CPAN-Perl-Releases-4.1
   |2-1.fc32|2-1.fc32
   |perl-CPAN-Perl-Releases-4.1 |perl-CPAN-Perl-Releases-4.1
   |2-1.fc31|2-1.fc31
   ||perl-CPAN-Perl-Releases-4.1
   ||2-1.fc30
 Resolution|--- |ERRATA
Last Closed||2019-08-29 22:05:57



--- Comment #5 from Fedora Update System  ---
perl-CPAN-Perl-Releases-4.12-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

[Bug 1740546] Upgrade perl-Getopt-Long to 2.51

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-Getopt-Long-2.51-1.fc3 |perl-Getopt-Long-2.51-1.fc3
   |1   |1
   ||perl-Getopt-Long-2.51-1.fc3
   ||0
 Resolution|--- |ERRATA
Last Closed||2019-08-29 22:05:10



--- Comment #6 from Fedora Update System  ---
perl-Getopt-Long-2.51-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

[Bug 1742782] perl-PPIx-Regexp-0.066 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
   Fixed In Version|perl-PPIx-Regexp-0.066-1.fc |perl-PPIx-Regexp-0.066-1.fc
   |31  |31
   ||perl-PPIx-Regexp-0.066-1.fc
   ||30
 Resolution|--- |ERRATA
Last Closed||2019-08-29 22:05:31



--- Comment #4 from Fedora Update System  ---
perl-PPIx-Regexp-0.066-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

Re: python38-3.8.0~b3-1.fc30 on my f30 machine? how?

[Kevin Kofler]

Miro Hrončok wrote:
> Also this bugzilla was open to let users remove them and not get them
> again when the package that recommends them updates, but the dnf team
> disagrees:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1699672

Maybe it would be time for FESCo to require them to implement usable 
behavior there? The people who want it (like me) are not familiar with the 
code, and the people familiar with the code refuse to do anything.

Kevin Kofler
___
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: [Test-Announce] Fedora 31 Beta Freeze

[Kevin Kofler]

Kevin Fenzi wrote:
> If I say:
> 
> 2019-08-20 at 00:00UTC I think I can guess this to be the very start of
> that day, perhaps?
> 
> 2019-08-29 at 24:00UTC is... what? the last miliseconds of that day and
> thus really right next to 2019-08-30 00:00UTC?

2019-08-29 24:00UTC = 2019-08-30 00:00UTC

The idea of the 24:00 (or 23:59 if you prefer) deadlines is that if the 
deadline is given as 2019-08-29, you actually have until 2019-08-29 included 
to publish your change, whereas using the 00:00 formulation means that the 
exact same deadline would be listed as 2019-08-30, but 2019-08-30 is already 
too late for your changes.

E.g., KDE Applications uses 23:59 UTC deadlines:
https://community.kde.org/Schedules/Applications/19.08_Release_Schedule

> If I say: 2019-09-29 at 18:00UTC we all know what time I mean I think,
> or at least it's more clear than 00:00 and 24:00.

A deadline within the day is the other alternative (used, e.g., by KDE 
Plasma: https://community.kde.org/Schedules/Plasma_5 – I presume "midday 
UTC" means 12:00 noon UTC), but IMHO it is more confusing than a 23:59/24:00 
deadline, and for Fedora, it would actually mean a procedure change contrary 
to my proposal.

For academic paper submissions, I have also seen both kinds of deadlines 
(23:59/24:00 deadlines and mid-day (12:00 noon or some other arbitrary time) 
deadlines), but never the confusing 00:00 deadlines used by Fedora.

Kevin Kofler
___
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

Please fix the aarch64 g++ pic problems in f32 rawhide

[Philip Kovacs via devel]

Several of us are getting errors in our c++ packages related to missing PIC 
flags in aarch64.
Something is amiss there.  A small snippet from openmpi:
make[2]: Entering directory 
'/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx'
/bin/sh ../../../libtool  --tag=CXX   --mode=link g++  -DNDEBUG -O2 -g -pipe 
-Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS 
-fexceptions -fstack-protector-strong -grecord-gcc-switches 
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables 
-fstack-clash-protection -finline-functions -pthread -version-info 60:1:20 
-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now 
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld-o libmpi_cxx.la -rpath 
/usr/lib64/openmpi/lib mpicxx.lo intercepts.lo comm.lo datatype.lo file.lo 
win.lo cxx_glue.lo ../../../ompi/libmpi.la -lrt -lm -lutil  -lz  -lhwloc  
-levent -levent_pthreads
libtool: link: g++  -shared -nostdlib 
/usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64/crti.o 
/usr/lib/gcc/aarch64-redhat-linux/9/crtbeginS.o  .libs/mpicxx.o 
.libs/intercepts.o .libs/comm.o .libs/datatype.o .libs/file.o .libs/win.o 
.libs/cxx_glue.o-Wl,-rpath 
-Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/.libs -Wl,-rpath 
-Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs -Wl,-rpath 
-Wl,/builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs -Wl,-rpath 
-Wl,/usr/lib64/openmpi/lib -L/builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs 
-L/builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs 
../../../ompi/.libs/libmpi.so 
/builddir/build/BUILD/openmpi-4.0.2rc1/orte/.libs/libopen-rte.so 
/builddir/build/BUILD/openmpi-4.0.2rc1/opal/.libs/libopen-pal.so -ldl -lrt 
-lutil -lz -lhwloc -levent -levent_pthreads 
-L/usr/lib/gcc/aarch64-redhat-linux/9 
-L/usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64 -L/lib/../lib64 
-L/usr/lib/../lib64 -L/usr/lib/gcc/aarch64-redhat-linux/9/../../.. -lstdc++ -lm 
-lpthread -lc -lgcc_s /usr/lib/gcc/aarch64-redhat-linux/9/crtendS.o 
/usr/lib/gcc/aarch64-redhat-linux/9/../../../../lib64/crtn.o  -O2 -g 
-fstack-protector-strong -grecord-gcc-switches -pthread -Wl,-z -Wl,relro 
-Wl,--as-needed -Wl,-z -Wl,now   -pthread -Wl,-soname -Wl,libmpi_cxx.so.40 -o 
.libs/libmpi_cxx.so.40.20.1
make[2]: Leaving directory '/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx'
BUILDSTDERR: /usr/bin/ld: .libs/mpicxx.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_ZTVN3MPI5GroupE' which may bind externally can not be used 
when making a shared object; recompile with -fPIC
BUILDSTDERR: .libs/mpicxx.o: in function `MPI::Group::Group(ompi_group_t*)':
BUILDSTDERR: 
/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx/../../../ompi/mpi/cxx/group.h:62:(.text._ZNK3MPI3Win9Get_groupEv[_ZNK3MPI3Win9Get_groupEv]+0x34):
 dangerous relocation: unsupported relocation
BUILDSTDERR: /usr/bin/ld: .libs/mpicxx.o: relocation R_AARCH64_ADR_PREL_PG_HI21 
against symbol `_ZTVN3MPI10ErrhandlerE' which may bind externally can not be 
used when making a shared object; recompile with -fPIC
BUILDSTDERR: .libs/mpicxx.o: in function 
`MPI::Errhandler::Errhandler(ompi_errhandler_t*)':
BUILDSTDERR: 
/builddir/build/BUILD/openmpi-4.0.2rc1/ompi/mpi/cxx/../../../ompi/mpi/cxx/errhandler.h:30:(.text._ZNK3MPI3Win14Get_errhandlerEv[_ZNK3MPI3Win14Get_errhandlerEv]+0x34):
 dangerous relocation: unsupported relocation
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

[Nico Kadel-Garcia]

Sent from my iPhone

> On Aug 29, 2019, at 12:58 PM, Kamil Dudka  wrote:
> 
>> On Tuesday, June 4, 2019 9:43:53 AM CEST Panu Matilainen wrote:
>>> On 6/4/19 9:56 AM, Daniel Mach wrote:
>>> 
>>> Dne 31. 05. 19 v 2:15 Pavel Raiskup napsal(a):
>>> 
> On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote:
> 
> Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a):
> 
>> If we did this, wouldn't it make it very difficult to use tools like
>> mock on RHEL / CentOS 7 to build for Fedora 3x?
> 
> 
> 
> Speaking of Mock:
> Either the RPM on host need to understand the new format/compression 
> **or**
> the packages in @buildsys group (including transitional deps) have to 
> be in
> old format - then you can build for Fedora 3x using bootstrap feature.
 
 
 
 I need to underline this, it would be really really really bad if we
 were
 not able to --installroot fedora chroots at least on RHEL 8.  How likely
 is a backport of zstd support into RPM in EL7+?
>>> 
>>> RHEL 8 should be quite easy - get zstd package into RHEL and recompile 
>>> rpm with zstd support.
>>> 
>>> RHEL 7 is a different story. The patch doesn't apply directly and a 
>>> backport would be needed.
>>> 
>>> Panu,
>>> how difficult it would be to backport the zstd support to RHEL 7 RPM?
>> 
>> 
>> Technically, backporting rpmio backends is almost trivial, even to much 
>> older rpm versions.
>> 
>> Getting new features into older RHEL is a much bigger problem.
>> 
>>- Panu -
> 
> Has there been any progress on this?
> 
> What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 

With “mock”, available from EPEL.
___
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: [HEADS-UP] snakeyaml 1.25 update

[Fabio Valentini]

On Mon, Aug 26, 2019 at 10:36 AM Vít Ondruch  wrote:
>
>
> Dne 25. 08. 19 v 14:06 Fabio Valentini napsal(a):
> > Hi everybody,
> >
> > Right now, the snakeyaml package in fedora is out of date by more than
> > three years (1.17, released in February 2016). We plan to merge the PR
> > rebasing it to the latest version (1.25, released this month) into
> > master / rawhide and f31. The new versions include *a lot of bug
> > fixes*, and some minor backwards-incompatible changes.
> >
> > https://src.fedoraproject.org/rpms/snakeyaml/pull-request/3
> >
> > I ran test rebuilds of dependent packages in a COPR repository, and
> > every package that isn't already broken built successfully, except
> > jruby:
> >
> > https://copr.fedorainfracloud.org/coprs/decathorpe/snakeyaml-pr/monitor/
> >
> > I checked JRuby upstream vs. the jruby package in fedora, and the
> > version we ship was released in August 2015 (!). I think compatibility
> > with the latest snakeyaml versions should be fixed with 9.2.0.0 and
> > newer, according to the upstream changelog (the versioning jumped from
> > 1.7.x series to "jruby 9000", with 9.x.y.z).
> >
> > If I ran the repoqueries correctly, JRuby is also only required by two
> > packages in fedora, both related to JRuby itself (joni and
> > jruby-maven-plugins).
>
>
> Well, JRuby is Ruby interpreter and in theory can run whatever Ruby code
> available in Fedora. And better integration with other Ruby packages in
> Fedora was always the plan.

Yeah, that's what I assumed after skimming the Ruby packaging guidelines.

> However, the problem of JRuby is that it is written in Java and I don't
> have enough expertise, together with different priorities, to properly
> maintain the package. Given this, the situation around java and another
> dependency (properties-maven-plugin) which is currently orphaned, it is
> probably time to orphan/retire the package from Fedora 

According to the snakeyaml changelog, the "minor
backwards-incompatible changes" should be either slightly changed
method signatures or renamed methods. So, *in theory*, it shouldn't be
too difficult to adapt jruby to these changes.

But I agree - if none of the people who are interested in (j)ruby have
enough Java expertise to fix this, it might really be time to orphan
or eventually retire the package.
I'm sad to say that I don't have the Java skills (nor the time) to
tackle this myself - the Java code I had to write for university
courses didn't prepare me for dealing with this ;)

Fabio

> Of course any volunteers who could help are welcome.
>
>
> Vít
>
>
> ___
> 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 1745562] Upgrade perl-Test-TrailingSpace to 0.0302

[bugzilla]

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



--- Comment #3 from Fedora Update System  ---
perl-Test-TrailingSpace-0.0302-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-2019-9f3278d9c8

-- 
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: hwloc update with so-bump and mpich rebuild

[Philip Kovacs via devel]

 Thanks Jerry -- what you describe is exactly what I am seeing in the build.log 
 Phil
On Thursday, August 29, 2019, 04:20:22 PM EDT, Jerry James 
 wrote:  
 
 On Thu, Aug 29, 2019 at 2:05 PM Philip Kovacs via devel
 wrote:
> Is there something odd going on with arch aarch64 -- openmpi builds are 
> failing on that arch.

There sure is.  I had the same thing happen with a qd build.  Look for
this in your build log:

checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... no

and then configure decides not to add -fPIC to the compiler flags, and
the library fails to build due to invalid relocations for a shared
object.  It only happens with g++, not gcc, and it only happens in
Rawhide.  I messed around with the qd build for awhile, and
accidentally found that adding -mabi=lp64 to CXXFLAGS makes that
configure test pass.  That shouldn't be necessary, as -mabi=lp64 is
already the default.  So, yes, something strange is going on with
aarch64 in Rawhide.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
  ___
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: hwloc update with so-bump and mpich rebuild

[Jerry James]

On Thu, Aug 29, 2019 at 2:05 PM Philip Kovacs via devel
 wrote:
> Is there something odd going on with arch aarch64 -- openmpi builds are 
> failing on that arch.

There sure is.  I had the same thing happen with a qd build.  Look for
this in your build log:

checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... no

and then configure decides not to add -fPIC to the compiler flags, and
the library fails to build due to invalid relocations for a shared
object.  It only happens with g++, not gcc, and it only happens in
Rawhide.  I messed around with the qd build for awhile, and
accidentally found that adding -mabi=lp64 to CXXFLAGS makes that
configure test pass.  That shouldn't be necessary, as -mabi=lp64 is
already the default.  So, yes, something strange is going on with
aarch64 in Rawhide.
-- 
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Bug 1747182] New: perl-Locale-Codes-3.62 is available

[bugzilla]

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

Bug ID: 1747182
   Summary: perl-Locale-Codes-3.62 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Locale-Codes
  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: 3.62
Current version/release in rawhide: 3.61-2.fc31
URL: http://search.cpan.org/dist/Locale-Codes/

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

-- 
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: Fedora Workstation and disabled by default firewall

[Chris Murphy]

On Thu, Aug 29, 2019 at 12:24 AM Chris Murphy  wrote:
>
> Debian has a permissive firewall
> https://wiki.debian.org/DebianFirewall

And Ubuntu, Mint, elementary, MX Linux, Solus, pop!_OS, as well. By
permissive, they all accept everything. Nothing is rejected or
dropped.

Mageia, and openSUSE do have a fair amount of iptables filtering
entries. e.g. openSUSE Tumbleweed lastest snapshot,
https://paste.fedoraproject.org/paste/TOJ1cdZpRWy2150N2O~IOw/raw

I didn't test Zorin because I couldn't get passed the paywall, and for
some reason Manjaro boots (kernel and initramfs) but then hangs during
startup and I don't really want to troubleshoot it.

Anyway, that rounds out the top ~10 distros, and Fedora Workstation is
definitely not the most permissive.


-- 
Chris Murphy
___
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: hwloc update with so-bump and mpich rebuild

[Philip Kovacs via devel]

 Is there something odd going on with arch aarch64 -- openmpi builds are 
failing on that arch.
On Thursday, August 29, 2019, 04:37:55 AM EDT, Zbigniew Jędrzejewski-Szmek 
 wrote:  
 
 Packages are now built. Update is submitted for F31
[https://bodhi.fedoraproject.org/updates/FEDORA-2019-af50f19b83].

On Wed, Aug 28, 2019 at 08:08:23AM +, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> I started doing the rebuilds now. I'll submit buildroot overrides
> as I go. (I was hoping to do this before the bodhi enablement in F31,
> but I got confused about the deadline). Unfortunately mpich now failed,
> so there'll be some delay. I'll submit one big update for F31 at the
> end.
> 
> Zbyszek
> 
> 
> On Wed, Aug 28, 2019 at 06:19:36AM +, Philip Kovacs wrote:
> >  
> > Are you going to submit f31 bodhi updates for these rebuilds?  Am watching 
> > the notifications    On Sunday, August 25, 2019, 09:01:05 PM EDT, Orion 
> > Poplawski  wrote:  
> >  
> >  On 8/25/19 1:17 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > Hi,
> > > 
> > > I made a minor mess in the mpich world and instead of upgrading to
> > > 3.3.1 from 3.2.1., I built 3.1.1. I was a bit surprised when I got
> > > a bug [1] that mpich in Fedora is from 2014 :(
> > > 
> > > I'd like to update to 3.3.1, but that needs newer hwloc which has an
> > > so-bump.
> > > 
> > > There's a number of users of hwloc:
> > > 
> > > mpich
> > > pmix
> > > openmpi
> > > pocl
> > > slurm
> > > hpx
> > > legion
> > > aircrack-ng
> > > gromacs
> > > 
> > > They all build fine with hwloc 2.0.4, except from legion.
> > > Legion is incompatible.
> > > I came up with a patch to partially disable hwloc use [2],
> > > and after reporting the issue upstream, I got the feedback
> > > that this is the correct approach [3].
> > > 
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1745252
> > > [2] https://src.fedoraproject.org/rpms/legion/pull-request/1
> > > [3] https://github.com/StanfordLegion/legion/issues/575
> > > 
> > > As a stop-gap measure, I rebuilt mpich-3.2.1 again today in
> > > rawhide and F31. I'd like to do the update though.
> > > 
> > > I plan to build hwloc-2.0 and the packages listed above, incl. legion
> > > with the patch on Wednesday.
> > > 
> > > Zbyszek
> > 
> > Sounds good to me.  Thanks for taking this on.
> > 
> > 
> > -- 
> > Orion Poplawski
> > Manager of NWRA Technical Systems          720-772-5637
> > NWRA, Boulder/CoRA Office            FAX: 303-415-9702
> > 3380 Mitchell Lane                      or...@nwra.com
> > Boulder, CO 80301                https://www.nwra.com/
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >  
___
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 1747071] perl-Gtk2-1.24993 is available

[bugzilla]

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

Tom "spot" Callaway  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2019-08-29 19:56:21



--- Comment #3 from Tom "spot" Callaway  ---
Updated to 1.24993 in rawhide and f31.

-- 
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 1747170] New: perl-Date-Manip-6.78 is available

[bugzilla]

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

Bug ID: 1747170
   Summary: perl-Date-Manip-6.78 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Date-Manip
  Keywords: FutureFeature, Triaged
  Assignee: jpazdzi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: huzai...@redhat.com, jpazdzi...@redhat.com,
ka...@ucw.cz, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 6.78
Current version/release in rawhide: 6.77-2.fc31
URL: http://search.cpan.org/dist/Date-Manip/

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

-- 
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: [Test-Announce] Fedora 31 Beta Freeze

[Chris Murphy]

On Thu, Aug 29, 2019 at 12:44 PM Kevin Fenzi  wrote:
>
> On 8/29/19 11:05 AM, Ben Cotton wrote:
> > On Thu, Aug 29, 2019 at 1:31 PM Kevin Fenzi  wrote:
> >>
> >> 24:00 does not exist? Or to me it makes as little sense as 00:00.
> >>
> > You're technically correct, which Futurama taught me is the best kind
> > of correct. I've seen it to mean "midnight at the end of the day" in
> > order to distinguish from "midnight at the beginning of the day". It's
> > functionally equivalent to 23:59:59.99.
> >
> well, but more importantly, what day is it on?
>
> If I say:
>
> 2019-08-20 at 00:00UTC I think I can guess this to be the very start of
> that day, perhaps?
>
> 2019-08-29 at 24:00UTC is... what? the last miliseconds of that day and
> thus really right next to 2019-08-30 00:00UTC?
>
> If I say: 2019-09-29 at 18:00UTC we all know what time I mean I think,
> or at least it's more clear than 00:00 and 24:00.

I can't say I ever came across 2400Z in aviation, but from reading
military stuff,  hours and 2400 hours are the exact same moment in
time and which gets used is determined by context. I'd say "my shift
ends August 29 at 2400 hours, and Joe's starts August 30 at 
hours" and it's the exact same moment in time (assuming UTC, zulu, or
the same time zone).

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

[Test-Announce] Official Fedora QA Telegram Group

[Geoffrey Marr]

Hello testers!

After Flock 2019 this year, it became apparent that there are several folks
who would like to join the testing effort, but do not want to use IRC and
would prefer to communicate over Telegram. Consequently, we have started a
Telegram group that testers can join to communicate with one another!
Please find the link below and add yourself to the group [0].

Note also that the #fedora-qa IRC channel and the Fedora QA Telegram group
have been bridged together, so traffic from one service will appear
seamlessly in the other. This allows current users of IRC to continue to
use their IRC clients as they have been, without missing out on any of the
conversations happening in #fedora-qa, and vice-versa.

Geoff Marr
IRC: coremodule

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

[Bug 1745563] Upgrade perl-WWW-Mechanize to 1.92

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |DUPLICATE
Last Closed||2019-08-29 18:55:02



--- Comment #1 from Emmanuel Seyman  ---


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

-- 
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 1746993] perl-WWW-Mechanize-1.92 is available

[bugzilla]

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

Emmanuel Seyman  changed:

   What|Removed |Added

 CC||jples...@redhat.com



--- Comment #1 from Emmanuel Seyman  ---
*** Bug 1745563 has been marked as a duplicate of this bug. ***

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

Re: [Test-Announce] Fedora 31 Beta Freeze

[Kevin Fenzi]

On 8/29/19 11:05 AM, Ben Cotton wrote:
> On Thu, Aug 29, 2019 at 1:31 PM Kevin Fenzi  wrote:
>>
>> 24:00 does not exist? Or to me it makes as little sense as 00:00.
>>
> You're technically correct, which Futurama taught me is the best kind
> of correct. I've seen it to mean "midnight at the end of the day" in
> order to distinguish from "midnight at the beginning of the day". It's
> functionally equivalent to 23:59:59.99.
> 
well, but more importantly, what day is it on?

If I say:

2019-08-20 at 00:00UTC I think I can guess this to be the very start of
that day, perhaps?

2019-08-29 at 24:00UTC is... what? the last miliseconds of that day and
thus really right next to 2019-08-30 00:00UTC?

If I say: 2019-09-29 at 18:00UTC we all know what time I mean I think,
or at least it's more clear than 00:00 and 24:00.

kevin




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

Re: Best practice for local files in a package

[Stephen John Smoogen]

On Thu, 29 Aug 2019 at 14:26, Bruno Wolff III  wrote:
>
> I got a warning about not having urls for a couple of files in the
> squashfs-tools package from release monitoring.
> The bug which has the comment is:
> https://bugzilla.redhat.com/show_bug.cgi?id=1747102
>
> These are based on some man pages used in Debian at one time, but do not
> track changes in the originals. I need to look at these again since 4.4
> has a number of new options. And I'm wondering what I should do to not
> break test release monitoring builds for files in the package that are local
> and not derived from (on an ongoing basis) an upstream?

I got a similar one for nagios. I am wondering if it would make sense
to put these in some git repo and just point the source to that but no
idea

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



-- 
Stephen J Smoogen.
___
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

Best practice for local files in a package

[Bruno Wolff III]

I got a warning about not having urls for a couple of files in the
squashfs-tools package from release monitoring.
The bug which has the comment is:
https://bugzilla.redhat.com/show_bug.cgi?id=1747102

These are based on some man pages used in Debian at one time, but do not
track changes in the originals. I need to look at these again since 4.4
has a number of new options. And I'm wondering what I should do to not
break test release monitoring builds for files in the package that are local
and not derived from (on an ongoing basis) an upstream?
___
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: What projects can we highlight for Hacktoberfest?

[Neal Gompa]

On Thu, Aug 29, 2019 at 1:27 PM Kevin Fenzi  wrote:
>
> On 8/26/19 3:43 PM, Fabio Valentini wrote:
> > On Mon, Aug 26, 2019 at 10:46 PM Ben Cotton  wrote:
> >>
> >> We're just over a month away from Hacktoberfest[1], a month-long event
> >> where people can earn a t-shirt by contributing to open source
> >> projects (or at least ones hosted on GitHub). It occurs to me that we
> >> could have a post on the Community Blog (or maybe Fedora Magazine)
> >> that directs folks toward Fedora or Fedora-adjacent projects on
> >> GitHub. This is a good opportunity to get meaningful drive-by
> >> contributions and perhaps add a few consistent contributors.
> >>
> >> So if you were going to point the Fedora community at a GitHub-hosted
> >> project, what would you choose?
> >
> > Well, I think the obvious choice would probably be a subset of
> > projects from https://github.com/fedora-infra - something like bodhi,
> > python-fedora, fas, and fedora-packages.
>
> Sure, but do check with us first, since fas and fedora-packages are both
> in maint mode/zombie walking. bodhi is a good active one, there's
> probibly others.
>

What about noggin? Can we get some Hacktoberfest-qualifying issues for
people to work on there?

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

Re: No longer supporting mailing lists:

[Przemek Klosowski via devel]

On 8/27/19 8:36 PM, Gerald B. Cox wrote:

Regarding NNTP I've haven't used newsreaders in years and to be honest dealing 
with yet another tool isn't something I would want to do


I forgot what email client you use, but all clients I ever used (Emacs 
and Thunderbird) also do NNTP. After all, it's just another stream of 
messages.

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

Re: Fedora Workstation and disabled by default firewall

[Japheth Cleaver]

On 8/29/2019 8:10 AM, Adam Williamson wrote:

On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote:

On Wed, Aug 28, 2019 at 8:56 PM John Harris  wrote:

It might be okay to be a GNOME-specific thing, as that's the only spin of
Fedora which is affected by this decision.


The default firewall config affects every user of that edition, even
if they never use GNOME (or even use graphical boot). So, I don't know
if this would be adequate.

Why would you install Workstation if you didn't intend to use GNOME?


That would seem to be a reasonable question, but if it's possible to do 
so then it is bound to happen... It may be a symptom of unclear definition.


If Workstation is going to require a graphical environment for 
reasonable usage/administration/whatever, then it should be made 
mandatory somehow. It would also help clarify that the Workstation, 
Server, and  Products must be treated distinctly... and that you 
shouldn't just point your kickstart file at whatever ISO you happen to 
have laying around.


-jc
___
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: Non-responsive maintainer

[Fabio Valentini]

On Thu, Aug 29, 2019 at 7:51 PM Greg Hellings  wrote:
>
> The jenkins pacakge is fearfully out of date and seems unmaintained. Does 
> anyone know how to get in touch with the maintainer(s) of the package?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1560603

It's not only out of date, but also hilariously broken. Just check this page:
https://apps.fedoraproject.org/koschei/search?q=jenkins

Most of the packaged jenkins plugins have already been retired for
fedora 31+, and jenkins itself is broken because a lot of its
dependencies have been retired as well.

Judging by the state of the Java stack in fedora, I'd recommend some
kind of container workflow that doesn't actually include fedora
packages for jenkins.
Another approach might be for you to join the Java SIG and revive
jenkins in fedora (which would require a lot of work).

Fabio

> --Greg
> ___
> 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: [Test-Announce] Fedora 31 Beta Freeze

[Ben Cotton]

On Thu, Aug 29, 2019 at 1:31 PM Kevin Fenzi  wrote:
>
> 24:00 does not exist? Or to me it makes as little sense as 00:00.
>
You're technically correct, which Futurama taught me is the best kind
of correct. I've seen it to mean "midnight at the end of the day" in
order to distinguish from "midnight at the beginning of the day". It's
functionally equivalent to 23:59:59.99.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
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

Non-responsive maintainer

[Greg Hellings]

The jenkins pacakge is fearfully out of date and seems unmaintained. Does
anyone know how to get in touch with the maintainer(s) of the package?

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

--Greg
___
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: [Test-Announce] Fedora 31 Beta Freeze

[Kevin Fenzi]

On 8/27/19 5:31 PM, Kevin Kofler wrote:
> Vít Ondruch wrote:
>> I think that all the major milestones happen typically on Tuesday, so
>> this must have been (unfortunate) typo IMO.
> 
> But the point is that this was corrected less than 24 hours before the 
> freeze kicks in. This is a completely unacceptably short notice.
> 
> It is already bad enough that Fedora freezes happen on 00:00 UTC on the 
> announced day as opposed to 24:00 UTC as used in almost all other projects 

24:00 does not exist? Or to me it makes as little sense as 00:00.

> (and fixing that would not even require any kind of procedure or policy 
> change, it would just require subtracting 1 from all the freeze dates that 
> get posted on the wiki!), which caught several of us off guard more than 
> once (yet, nobody even bothered replying to my requests to fix that), but 
> now even that can no longer be trusted because the posted dates get "fixed" 
> with a 0-day notice.

I'd support changing the freeze dates to be something more like 18:00UTC
the date they are listed. That would give people more time/be actually
on the date when people are awake. I'll float the idea to releng and
then fesco.

> 
> IMHO, the right thing to do would be to quickly postpone the freeze (i.e., 
> unfreeze where necessary) by a whole week, then it's still on midnight from 
> Monday to Tuesday as usual, but people will have gotten a reasonable 
> advanced notice.

I'm not sure thats very possible (at least it would be difficult to undo
some things).

I'd suppport doing another stable push before we go into freeze tho...
there's a fesco ticket where I suggested that.

kevin




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

[Bug 1747071] perl-Gtk2-1.24993 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring@fedoraproject.org's scratch build of
perl-Gtk2-1.24993-1.fc29.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=37339174

-- 
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 1747059] perl-Gtk3-0.036 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring@fedoraproject.org's scratch build of
perl-Gtk3-0.036-1.fc29.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=37339136

-- 
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 1747079] perl-File-Next-1.18 is available

[bugzilla]

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



--- Comment #2 from Upstream Release Monitoring 
 ---
the-new-hotness/release-monitoring@fedoraproject.org's scratch build of
perl-File-Next-1.18-1.fc29.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=37339201

-- 
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: What projects can we highlight for Hacktoberfest?

[Kevin Fenzi]

On 8/26/19 3:43 PM, Fabio Valentini wrote:
> On Mon, Aug 26, 2019 at 10:46 PM Ben Cotton  wrote:
>>
>> We're just over a month away from Hacktoberfest[1], a month-long event
>> where people can earn a t-shirt by contributing to open source
>> projects (or at least ones hosted on GitHub). It occurs to me that we
>> could have a post on the Community Blog (or maybe Fedora Magazine)
>> that directs folks toward Fedora or Fedora-adjacent projects on
>> GitHub. This is a good opportunity to get meaningful drive-by
>> contributions and perhaps add a few consistent contributors.
>>
>> So if you were going to point the Fedora community at a GitHub-hosted
>> project, what would you choose?
> 
> Well, I think the obvious choice would probably be a subset of
> projects from https://github.com/fedora-infra - something like bodhi,
> python-fedora, fas, and fedora-packages.

Sure, but do check with us first, since fas and fedora-packages are both
in maint mode/zombie walking. bodhi is a good active one, there's
probibly others.

> I don't know how approachable those projects are for newcomers, but
> since they're written in python, it can't be too bad, and there are
> some issues marked as "EasyFix" as well.
> 
> (Im also working on rust bindings for bodhi and koji at
> https://github.com/ironthree, which could also use some help.
> )

Cool!

kevin




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

[Bug 1747118] New: perl-HTTP-Daemon-6.06 is available

[bugzilla]

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

Bug ID: 1747118
   Summary: perl-HTTP-Daemon-6.06 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-Daemon
  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: 6.06
Current version/release in rawhide: 6.05-1.fc31
URL: http://search.cpan.org/dist/HTTP-Daemon/

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

-- 
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 1747079] New: perl-File-Next-1.18 is available

[bugzilla]

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

Bug ID: 1747079
   Summary: perl-File-Next-1.18 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-File-Next
  Keywords: FutureFeature, Triaged
  Assignee: robinlee.s...@gmail.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
robinlee.s...@gmail.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.18
Current version/release in rawhide: 1.16-10.fc31
URL: http://search.cpan.org/dist/File-Next/

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

-- 
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 1747079] perl-File-Next-1.18 is available

[bugzilla]

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



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

-- 
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 1747071] perl-Gtk2-1.24993 is available

[bugzilla]

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



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

-- 
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 1747071] New: perl-Gtk2-1.24993 is available

[bugzilla]

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

Bug ID: 1747071
   Summary: perl-Gtk2-1.24993 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Gtk2
  Keywords: FutureFeature, Triaged
  Assignee: tcall...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com,
perl-devel@lists.fedoraproject.org,
tcall...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.24993
Current version/release in rawhide: 1.24992-10.fc31
URL: http://search.cpan.org/dist/Gtk2/

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

-- 
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 1747059] perl-Gtk3-0.036 is available

[bugzilla]

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



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

-- 
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 1747059] New: perl-Gtk3-0.036 is available

[bugzilla]

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

Bug ID: 1747059
   Summary: perl-Gtk3-0.036 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Gtk3
  Keywords: FutureFeature, Triaged
  Assignee: berra...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: berra...@redhat.com, dd...@cpan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 0.036
Current version/release in rawhide: 0.035-3.fc31
URL: http://search.cpan.org/dist/Gtk3/

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

-- 
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 1746993] New: perl-WWW-Mechanize-1.92 is available

[bugzilla]

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

Bug ID: 1746993
   Summary: perl-WWW-Mechanize-1.92 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-WWW-Mechanize
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, jose.p.oliveira@gmail.com,
ktdre...@ktdreyer.com,
perl-devel@lists.fedoraproject.org,
trem...@tremble.org.uk
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 1.92
Current version/release in rawhide: 1.91-4.fc31
URL: http://search.cpan.org/dist/WWW-Mechanize/

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

-- 
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: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

[Kamil Dudka]

On Tuesday, June 4, 2019 9:43:53 AM CEST Panu Matilainen wrote:
> On 6/4/19 9:56 AM, Daniel Mach wrote:
> 
> > Dne 31. 05. 19 v 2:15 Pavel Raiskup napsal(a):
> > 
> >> On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote:
> >> 
> >>> Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a):
> >>> 
>  If we did this, wouldn't it make it very difficult to use tools like
>  mock on RHEL / CentOS 7 to build for Fedora 3x?
> >>>
> >>>
> >>>
> >>> Speaking of Mock:
> >>> Either the RPM on host need to understand the new format/compression 
> >>> **or**
> >>> the packages in @buildsys group (including transitional deps) have to 
> >>> be in
> >>> old format - then you can build for Fedora 3x using bootstrap feature.
> >>
> >>
> >>
> >> I need to underline this, it would be really really really bad if we
> >> were
> >> not able to --installroot fedora chroots at least on RHEL 8.  How likely
> >> is a backport of zstd support into RPM in EL7+?
> > 
> > RHEL 8 should be quite easy - get zstd package into RHEL and recompile 
> > rpm with zstd support.
> > 
> > RHEL 7 is a different story. The patch doesn't apply directly and a 
> > backport would be needed.
> > 
> > Panu,
> > how difficult it would be to backport the zstd support to RHEL 7 RPM?
> 
> 
> Technically, backporting rpmio backends is almost trivial, even to much 
> older rpm versions.
> 
> Getting new features into older RHEL is a much bigger problem.
> 
>   - Panu -

Has there been any progress on this?

What is the recommended way to build Fedora 31+ RPMs on a RHEL-7 host?

Kamil

___
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: Error with fedpkg update

[Iñaki Ucar]

On Thu, 29 Aug 2019 at 18:06, Gerald B. Cox  wrote:
>
> Thanks all for the replies... I was under the impression from the previous 
> response I needed to submit to bodhi, but I believe I misinterpreted and that 
> was intended for future changes going forward.  Looking at bodhi now it's a 
> little confusing seeing f29, f30 and f32 there but no f31.

Yeap, it's confusing because Bodhi shows pre-branching and
post-activation updates. But every build between those two dates
directly landed in f31 stable, as always, including your package. :)

Iñaki
___
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: Error with fedpkg update

[Gerald B. Cox]

Thanks all for the replies... I was under the impression from the previous
response I needed to submit to bodhi, but I believe I misinterpreted and
that was intended for future changes going forward.  Looking at bodhi now
it's a little confusing seeing f29, f30 and f32 there but no f31.

On Thu, Aug 29, 2019 at 12:52 PM Iñaki Ucar  wrote:

> On Thu, 29 Aug 2019 at 17:36, Gerald B. Cox  wrote:
> >
> > If I do that, I believe I get into a situation where the other builds
> f29, f30 and F32 are behind, which if I remember correctly causes other
> issues - and shouldn't we understand what is wrong with the system rather
> than just trying to hack around it?
>
> copyq was in the Fedora 31 compose report three days ago:
>
>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/G5I2FHHMBBIGHCW4RZIUMBSXAKNNZHCW/
>
> Iñaki
> ___
> 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: Error with fedpkg update

[Iñaki Ucar]

On Thu, 29 Aug 2019 at 17:36, Gerald B. Cox  wrote:
>
> If I do that, I believe I get into a situation where the other builds f29, 
> f30 and F32 are behind, which if I remember correctly causes other issues - 
> and shouldn't we understand what is wrong with the system rather than just 
> trying to hack around it?

copyq was in the Fedora 31 compose report three days ago:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/G5I2FHHMBBIGHCW4RZIUMBSXAKNNZHCW/

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

Re: Fedora Workstation and disabled by default firewall

[Christophe de Dinechin]

mcatanz...@gnome.org writes:

> Well the thing is, blocknig ports tends to break applications that want
> to use those ports. We're not going to do that, period. It also doesn't
> really accomplish anything: either your app or service needs network
> access and you have whitelisted it (in which case the firewall provides
> no security), or it needs network access and you have not whitelisted
> it (in which case your firewall breaks your app/service). In no case
> does it increase your security without breaking your app, right? Unless
> you have malware installed (in which case, you have bigger problems
> than the firewall). Or unless you have a vulnerable network service
> installed that you don't want (in which case, uninstall it).
>
> So if you want to change the firewall settings, you'd need to
> completely rethink how the firewall works. And nobody seems interested
> in doing that. We could e.g. have a list of apps that are allowed
> network access, but then we'd need some form of attestation so apps
> can't impersonate each other. So only sandboxed (flatpaked) apps could
> use this hypothetical new firewall. And we surely don't want to have
> yes/no permission prompts, so we can't really ask the user "do you want
> your app to access the network?" (the user will almost always say
> yes).

For what it's worth, macOS started doing exactly that recently.
I agree it seems useless, except for one thing. Sometimes, you realize
that some app is opening a port when you don't expect it.

> I'm not really sure what design would even work.
>
> Avoiding unnecessary network services makes more sense.
>
> On Mon, Aug 26, 2019 at 3:45 PM, Alexander Ploumistos
>  wrote:
>>
>> As a matter of fact, you did:
>> 
>> 
>
> Thanks for dredging up these links!
>
> Michael
>
> ___
> 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


--
Cheers,
Christophe de Dinechin (IRC c3d)
___
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: Error with fedpkg update

[Gerald B. Cox]

If I do that, I believe I get into a situation where the other builds f29,
f30 and F32 are behind, which if I remember correctly causes other issues -
and shouldn't we understand what is wrong with the system rather than just
trying to hack around it?

On Thu, Aug 29, 2019 at 12:17 PM Adam Williamson 
wrote:

> On Thu, 2019-08-29 at 07:56 -0700, Gerald B. Cox wrote:
> > Guys, I'm still getting this message:
> > fedpkg update
> > Could not execute update: Could not generate update request: Cannot find
> > release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
> > A copy of the filled in template is saved as bodhi.template.last
>
> I mean, as a simple fix why not just bump it and do a -2 build and see
> if you can send an update for that?
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
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: [Test-Announce] Fedora 31 Beta Freeze

[Paul Howarth]

On Wed, 28 Aug 2019 09:47:49 -0700
"Gerald B. Cox"  wrote:

> I'm still getting these messages when I try to do "fedpkg update" for
> F31:
> 
> fedpkg update
> Could not execute update: Could not generate update request: Cannot
> find release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
> A copy of the filled in template is saved as bodhi.template.last

The package was built on the 25th, before the Beta freeze. Hence it
went straight into the repo (it is there already, check for yourself:
https://dl.fedoraproject.org/pub/fedora/linux/development/31/Everything/source/tree/Packages/c/copyq-3.9.2-1.fc31.src.rpm)
and hence there's no need to create an update for it.

Paul.
___
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: Error with fedpkg update

[Adam Williamson]

On Thu, 2019-08-29 at 07:56 -0700, Gerald B. Cox wrote:
> Guys, I'm still getting this message:
> fedpkg update
> Could not execute update: Could not generate update request: Cannot find
> release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
> A copy of the filled in template is saved as bodhi.template.last

I mean, as a simple fix why not just bump it and do a -2 build and see
if you can send an update for that?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Workstation and disabled by default firewall

[Dan Book]

On Thu, Aug 29, 2019 at 11:11 AM Adam Williamson 
wrote:

> On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote:
> > On Wed, Aug 28, 2019 at 8:56 PM John Harris 
> wrote:
> > > On Wednesday, August 28, 2019 5:46:58 PM MST Christopher wrote:
> > > > A similar idea that would keep it separate from the installer might
> be
> > > > to offer a dialogue as a "first-boot" action, but that seems like
> it'd
> > > > be a very GNOME-specific thing, and firewalld is not specific to the
> > > > WM/Desktop.
> > >
> > > It might be okay to be a GNOME-specific thing, as that's the only spin
> of
> > > Fedora which is affected by this decision.
> > >
> >
> > The default firewall config affects every user of that edition, even
> > if they never use GNOME (or even use graphical boot). So, I don't know
> > if this would be adequate.
>
> Why would you install Workstation if you didn't intend to use GNOME?
>

I would agree, but people do install multiple desktops after installing a
spin. Such a use case needs to be considered (not sure if it matters,
though).

-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

Re: Fedora Workstation and disabled by default firewall

[Adam Williamson]

On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote:
> On Wed, Aug 28, 2019 at 8:56 PM John Harris  wrote:
> > On Wednesday, August 28, 2019 5:46:58 PM MST Christopher wrote:
> > > A similar idea that would keep it separate from the installer might be
> > > to offer a dialogue as a "first-boot" action, but that seems like it'd
> > > be a very GNOME-specific thing, and firewalld is not specific to the
> > > WM/Desktop.
> > 
> > It might be okay to be a GNOME-specific thing, as that's the only spin of
> > Fedora which is affected by this decision.
> > 
> 
> The default firewall config affects every user of that edition, even
> if they never use GNOME (or even use graphical boot). So, I don't know
> if this would be adequate.

Why would you install Workstation if you didn't intend to use GNOME?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Error with fedpkg update

[Gerald B. Cox]

Guys, I'm still getting this message:
fedpkg update
Could not execute update: Could not generate update request: Cannot find
release associated with build: copyq-3.9.2-1.fc31, tags: ['f31']
A copy of the filled in template is saved as bodhi.template.last

I just checked bodhi and other packages are being accepted for testing for
f31.  What is going on?



On Fri, Aug 23, 2019 at 12:20 PM Kevin Fenzi  wrote:

> On 8/23/19 11:10 AM, Adam Williamson wrote:
> >
> > It won't appear in Bodhi at all, but it will get the koji tag 'f31' and
> > so appear in Fedora 31 composes.
> >
> > This is how Rawhide and Branched-pre-Bodhi-enablement *always* worked -
> > it just feels a bit odd now because we have the gating stuff enabled
> > for Rawhide, but it wasn't set up for the short time between Branch
> > point and Bodhi enablement for the branch; so right now Rawhide is
> > working the 'new' way with auto-created Bodhi updates, but F31 is
> > working the 'old' way with no Bodhi at all.
>
> NOTE: for next branching I think the idea is to enable gating for it as
> well as rawhide. This will be less confusing for everyone and make more
> sense... we just weren't ready for it this time.
>
> kevin
>
>
> ___
> 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 1746531] Please build perl-BerkeleyDB for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2019-8c1c1a8600 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8c1c1a8600

-- 
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 1746531] Please build perl-BerkeleyDB for EPEL 8

[bugzilla]

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

Jitka Plesnikova  changed:

   What|Removed |Added

   Fixed In Version||perl-BerkeleyDB-0.63-2.el8



-- 
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 1746534] Please build perl-File-LibMagic for EPEL 8

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2019-218a58cedd has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-218a58cedd

-- 
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: python38-3.8.0~b3-1.fc30 on my f30 machine? how?

[Miro Hrončok]

On 29. 08. 19 15:31, Kaleb Keithley wrote:


Also python36, python35, and python34.

I'm 100% confident that I never explicitly installed these.

Having python38 broke my devel setup due to there being no Cython in 
/usr/lib64/python3.8/site-packages/...  I don't know how long it was broken. 
Very annoying to discover this.


How do I prevent this from happening again?  (Yes, I know I can put explicit 
excludes in my /etc/yum.repos.d/fedora-updates.repo file.) Seems like I 
shouldn't need to and that it shouldn't have happened in the first place.


python3-tox recommends them. maybe that is how they were installed?

Also this bugzilla was open to let users remove them and not get them again when 
the package that recommends them updates, but the dnf team disagrees:


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

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

Re: python38-3.8.0~b3-1.fc30 on my f30 machine? how?

[Jerry James]

On Thu, Aug 29, 2019 at 7:32 AM Kaleb Keithley  wrote:
> Also python36, python35, and python34.

They could have been pulled in via Recommends:

$ dnf repoquery --whatrecommends python38
python3-tox-0:3.5.3-3.fc30.noarch
$ dnf repoquery --whatrecommends python36
asv-0:0.3.1-7.fc30.x86_64
asv-0:0.4.1-2.fc30.x86_64
python3-tox-0:3.5.3-3.fc30.noarch
$ dnf repoquery --whatrecommends python35
asv-0:0.3.1-7.fc30.x86_64
asv-0:0.4.1-2.fc30.x86_64
python3-tox-0:3.5.3-3.fc30.noarch
$ dnf repoquery --whatrecommends python34
asv-0:0.3.1-7.fc30.x86_64
asv-0:0.4.1-2.fc30.x86_64
python3-tox-0:3.5.3-3.fc30.noarch

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

python38-3.8.0~b3-1.fc30 on my f30 machine? how?

[Kaleb Keithley]

Also python36, python35, and python34.

I'm 100% confident that I never explicitly installed these.

Having python38 broke my devel setup due to there being no Cython in
/usr/lib64/python3.8/site-packages/...  I don't know how long it was
broken. Very annoying to discover this.

How do I prevent this from happening again?  (Yes, I know I can put
explicit excludes in my /etc/yum.repos.d/fedora-updates.repo file.) Seems
like I shouldn't need to and that it shouldn't have happened in the first
place.

--

Kaleb
___
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: 20190829.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20190828.n.0
NEW: Fedora-Rawhide-20190829.n.0

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

Size of added packages:  209.44 MiB
Size of dropped packages:11.72 MiB
Size of upgraded packages:   5.08 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: SoaS live x86_64
Path: Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20190829.n.0.iso
Image: SoaS raw-xz armhfp
Path: Spins/armhfp/images/Fedora-SoaS-armhfp-Rawhide-20190829.n.0-sda.raw.xz

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: R-gargle-0.3.1-1.fc32
Summary: Utilities for Working with Google APIs
RPMs:R-gargle
Size:284.75 KiB

Package: R-lifecycle-0.1.0-1.fc32
Summary: Manage the Life Cycle of your Package Functions
RPMs:R-lifecycle
Size:89.54 KiB

Package: gnome-python2-2.28.1-27.fc32
Summary: PyGNOME Python extension module
RPMs:gnome-python2 gnome-python2-bonobo gnome-python2-canvas 
gnome-python2-devel gnome-python2-gconf gnome-python2-gnome 
gnome-python2-gnomevfs
Size:2.16 MiB

Package: gnome-python2-desktop-2.32.0-38.fc32
Summary: The sources for additional PyGNOME Python extension modules
RPMs:gnome-python2-desktop gnome-python2-gnomekeyring gnome-python2-libwnck 
gnome-python2-rsvg
Size:591.76 KiB

Package: gtksourceview2-2.11.2-30.fc32
Summary: A library for viewing source files
RPMs:gtksourceview2 gtksourceview2-devel
Size:4.62 MiB

Package: jolokia-jvm-agent-1.6.2-1.fc32
Summary: Jolokia JVM Agent
RPMs:jolokia-jvm-agent
Size:421.11 KiB

Package: mingw-fribidi-1.0.5-1.fc32
Summary: MinGW Windows fribidi library
RPMs:mingw32-fribidi mingw32-fribidi-static mingw64-fribidi 
mingw64-fribidi-static
Size:197.76 KiB

Package: mingw-qt5-qtwebchannel-5.12.4-1.fc32
Summary: Qt5 for Windows - QtWebChannel component
RPMs:mingw32-qt5-qtwebchannel mingw64-qt5-qtwebchannel
Size:201.95 KiB

Package: nodejs-dateformat-3.0.3-5.fc32
Summary: Steven Levithan's excellent dateFormat() function for Node.js
RPMs:nodejs-dateformat
Size:13.79 KiB

Package: nodejs-grunt-contrib-nodeunit-2.0.0-1.fc32
Summary: Run Nodeunit unit tests with grunt
RPMs:nodejs-grunt-contrib-nodeunit
Size:15.50 KiB

Package: nodeunit-0.13.0-1.fc32
Summary: Easy asynchronous unit testing framework for Node.js
RPMs:nodeunit
Size:47.95 KiB

Package: prometheus-jmx-exporter-0.12.0-1.fc32
Summary: Prometheus JMX Exporter
RPMs:prometheus-jmx-exporter
Size:438.07 KiB

Package: prometheus-simpleclient-java-0.6.0-1.fc32
Summary: Prometheus JVM Client
RPMs:prometheus-simpleclient-java
Size:96.14 KiB

Package: python-aexpect-1.5.1-5.module_f32+6098+36e6978f
Summary: A python library to control interactive applications
RPMs:python3-aexpect
Size:51.09 KiB

Package: python-avocado-71.0-1.module_f32+6098+36e6978f
Summary: Framework with tools and libraries for Automated Testing
RPMs:python-avocado-bash python-avocado-common python-avocado-examples 
python3-avocado python3-avocado-plugins-glib python3-avocado-plugins-golang 
python3-avocado-plugins-loader-yaml python3-avocado-plugins-output-html 
python3-avocado-plugins-result-upload python3-avocado-plugins-resultsdb 
python3-avocado-plugins-varianter-cit python3-avocado-plugins-varianter-pict 
python3-avocado-plugins-varianter-yaml-to-mux
Size:771.50 KiB

Package: python-ifcfg-0.18-1.fc32
Summary: Python cross-platform network interface discovery 
(ifconfig/ipconfig/ip)
RPMs:python3-ifcfg
Size:22.85 KiB

Package: python-tw2-core-2.2.6-2.fc32
Summary: Web widget creation toolkit based on TurboGears widgets
RPMs:python2-tw2-core python3-tw2-core
Size:239.03 KiB

Package: python27-2.7.16-8.fc32
Summary: Version 2.7 of the Python interpreter
RPMs:python27
Size:64.55 MiB

Package: python37-3.7.4-5.fc32
Summary: Version 3.7 of the Python interpreter
RPMs:python37
Size:99.94 MiB

Package: qd-2.3.22-1.fc32
Summary: Double-Double and Quad-Double Arithmetic
RPMs:qd qd-devel
Size:2.38 MiB

Package: rubygem-sassc-2.2.0-1.fc32
Summary: Use libsass with Ruby!
RPMs:rubygem-sassc rubygem-sassc-doc
Size:533.18 KiB

Package: swig-4.0.1-1.module_f32+6102+7b5a9978
Summary: Connects C/C++/Objective C to some high-level programming languages
RPMs:ccache-swig swig swig-doc swig-gdb
Size:12.92 MiB

Package: xtl-0.6.5-1.fc32
Summary: QuantStack tools library
RPMs:xtl-devel xtl-doc
Size:18.94 MiB


= DROPPED PACKAGES =
Package: ailurus-10.10.3-19.fc31
Summary: A simple application installer and GNOME tweaker
RPMs:ailurus
Size:1.80 MiB

Package: bleachbit-2.2-2.fc31
Summary: Python utility to free disk space and improve privacy
RPMs:bleachbit
Size:532.58 KiB

Package: cherrytree-0.38.5-5.fc30
Summary

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

[Fedora compose checker]

No missing expected images.

Compose FAILS proposed Rawhide gating check!
9 of 45 required tests failed, 6 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
MISSING: fedora.Workstation-boot-iso.x86_64.64bit - compose.install_default
MISSING: fedora.Workstation-boot-iso.x86_64.uefi - compose.install_default

Failed openQA tests: 30/152 (x86_64), 1/2 (arm)

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

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

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

ID: 438149  Test: x86_64 Server-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/438149
ID: 438150  Test: x86_64 Server-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/438150
ID: 438166  Test: x86_64 Server-dvd-iso 
server_role_deploy_domain_controller **GATING**
URL: https://openqa.fedoraproject.org/tests/438166
ID: 438167  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart 
**GATING**
URL: https://openqa.fedoraproject.org/tests/438167
ID: 438170  Test: x86_64 Server-dvd-iso realmd_join_cockpit
URL: https://openqa.fedoraproject.org/tests/438170
ID: 438171  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/438171
ID: 438172  Test: x86_64 Server-dvd-iso server_freeipa_replication_master
URL: https://openqa.fedoraproject.org/tests/438172
ID: 438173  Test: x86_64 Server-dvd-iso server_freeipa_replication_replica
URL: https://openqa.fedoraproject.org/tests/438173
ID: 438174  Test: x86_64 Server-dvd-iso server_freeipa_replication_client
URL: https://openqa.fedoraproject.org/tests/438174
ID: 438181  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/438181
ID: 438183  Test: x86_64 Everything-boot-iso install_default **GATING**
URL: https://openqa.fedoraproject.org/tests/438183
ID: 438184  Test: x86_64 Everything-boot-iso install_default@uefi **GATING**
URL: https://openqa.fedoraproject.org/tests/438184
ID: 438185  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/438185
ID: 438187  Test: x86_64 Workstation-live-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/438187
ID: 438216  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/438216
ID: 438218  Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/438218
ID: 438220  Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/438220
ID: 438278  Test: x86_64 universal upgrade_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/438278
ID: 438280  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/438280
ID: 438281  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/438281
ID: 438283  Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/438283
ID: 438284  Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/438284
ID: 438285  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/438285
ID: 438287  Test: x86_64 universal upgrade_2_desktop_64bit
URL: https://openqa.fedoraproject.org/tests/438287
ID: 438288  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/438288
ID: 438289  Test: x86_64 universal upgrade_2_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/438289
ID: 438292  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/438292
ID: 438293  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/438293
ID: 438294  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/438294
ID: 438299  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/438299

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

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

ID: 438282  Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/438282

Passed openQA tests: 101/152 (x86_64)

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

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

Skipped gating openQA tests: 4/152 (x86_64)

Old skipped gating tests 

Re: Fedora Workstation and disabled by default firewall

[Iñaki Ucar]

Responding to the first message because I'm not interested in further
discussion. It's clear to me that there will be no agreement in this
matter unless there are reasonable potential alternatives. Therefore,
this message is just to let you all know that I'm at least trying to
push for better alternatives. In particular, these:

https://bugs.kde.org/show_bug.cgi?id=411359
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1550
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/650

You are welcome to help with the above, or bring them to other
desktops. Hopefully, if these proposals get accepted and implemented,
we could eventually bring back this discussion and reach some
consensus.

Iñaki


On Mon, 26 Aug 2019 at 14:40, Vitaly Zaitsev via devel
 wrote:
>
> Hello all.
>
> Is it okay that firewall is completely disabled by default (opened all
> ports 1025-65535) on Fedora Workstation?
>
> I think that this is a major vulnerability and it must be fixed by
> changing default zone to public.
>
> firewall-cmd --list-all
> FedoraWorkstation (active)
>   target: default
>   icmp-block-inversion: no
>   interfaces: enp1s0
>   sources:
>   services: dhcpv6-client mdns samba-client ssh
>   ports: 1025-65535/udp 1025-65535/tcp
>   protocols:
>   masquerade: no
>   forward-ports:
>   source-ports:
>   icmp-blocks:
>   rich rules:
>
> --
> Sincerely,
>   Vitaly Zaitsev (vit...@easycoding.org)
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



--
Iñaki Úcar
___
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: Debates/back and forths

[Florian Weimer]

* John Harris:

> On Wednesday, August 28, 2019 9:27:56 AM MST Chris Peters wrote:
>> Maybe the code of conduct could politely nudge people towards *quality* over
>> quantity (so that voices don't get drowned and big threads aren't so
>> tiresome to keep up with)
>
> Such a rule would make it very difficult indeed to address all
> concerns.

In some cases, it may be necessary to refute something every time it is
brought up.  But most matters are not *that* critical, and you can
assume that anyone reviewing the thread will read it in context, and not
just a single message with an dubious (but unrefuted) claim.

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: Debates/back and forths

[Chris Peters]

Aug 29, 2019, 00:23 by joh...@splentity.com:

> On Wednesday, August 28, 2019 9:27:56 AM MST Chris Peters wrote:
>
>> Maybe the code of conduct could politely nudge people towards *quality* over
>> quantity (so that voices don't get drowned and big threads aren't so
>> tiresome to keep up with)
>>
>
> Such a rule would make it very difficult indeed to address all concerns.
>

There are large threads where it would be natural for one person to answer 
questions and provide rebuttals, such as a Change owner.

In other large threads, healthy debate doesn't usually look like one person 
"addressing all concerns". A dominant voice is usually someone so passionate 
they inadvertently drown a debate with their opinion without realizing it might 
be inconsiderate.

 There's good reasons why moderated debates don't let the loudest person keep 
hold of the microphone. I'm not advocating moderation, but just saying it's 
possible to be passionate, objectively correct, and considerate all at the same 
time.  =)

Chris

PS I won't take this thread any further. The irony of a back and forth in the 
back and forth thread doesn't escape me!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [HEADS UP] Retiring python2 and introducing python27 later this week

[Miro Hrončok]

On 29. 08. 19 10:19, Miro Hrončok wrote:

On 29. 08. 19 5:25, Scott Talbert wrote:

On 27. 08. 19 22:20, Miro Hrončok wrote:

python27 build in progress.

Will retire python2 later tomorrow or on Friday (in case something is terribly
broken I want to have some maneuvering space).

Hey Miro,

I can't rebuild python-wxpython4 with the new python27.  This is what I'm 
seeing in the logs but it seems that the root cause is that 
/usr/include/python2.7/pyconfig-64.h is missing?


I've noticed this as well today. It is a packaging bug with excludes and I'm 
working on a hotfix. Will push ASAP, testing locally.


python27-2.7.16-9.fc32 appears to be fixed. Thanks for the report.

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

[Bug 1746739] Upgrade perl-Test2-Suite to 0.000126

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
   Fixed In Version||perl-Test2-Suite-0.000126-1
   ||.fc32
 Resolution|--- |RAWHIDE
Last Closed||2019-08-29 09:18:04



--- Comment #1 from Petr Pisar  ---
An enhancement release suitable for Fedora ≥ 32.

-- 
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 1746739] Upgrade perl-Test2-Suite to 0.000126

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC|ppi...@redhat.com   |
 Blocks||1746731




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1746731
[Bug 1746731] Upgrade perl-Test2-Harness to 0.001086
-- 
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: Open NeuroFedora team meeting: 1500 UTC on Thursday, 29th August.

[Ankur Sinha]

Hello,

A reminder of today's meeting at 1500UTC in #fedora-neuro on Freenode
(details below).

Please inform me if you'd like to add new items to the agenda. I'll see
you there!

On Mon, Aug 26, 2019 15:57:46 +0100, Ankur Sinha wrote:
> Hello everyone,
> 
> You are invited to attend the Open NeuroFedora team meeting this week
> on Thursday at 1500UTC in #fedora-neuro on IRC (Freenode):
> 
> https://webchat.freenode.net/?channels=#fedora-neuro
> 
> You can convert the meeting time to your local time using:
> $ date --date='TZ="UTC" 1500 next Thu'
> 
> or use this link:
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+team+meeting=20190829T15=1440=1
> 
> The agenda for the meeting is:
> 
> - Introductions and roll call.
> - Pagure tickets related to our progress on computational neuroscience
>   tools:
>   
> https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open=S%3A+Next+meeting
> - Planning for the next phase of NeuroFedora tasks: focus on neuro-imaging?
> - Neuroscience query of the week.
> - Next meeting day, and chair.
> - Open floor.
> 
> In the "Neuroscience query of the week" section, we hope to provide
> attendees with the chance to ask about a neuroscience topic that they
> are curious about.
> 
> Please go through the tickets on Pagure, and mark any other tickets that
> need to be discussed with the "S: Next meeting" tag.
> 
> We hope to see you there!
> 
> -- 
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) | 
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London



-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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: hwloc update with so-bump and mpich rebuild

[Zbigniew Jędrzejewski-Szmek]

Packages are now built. Update is submitted for F31
[https://bodhi.fedoraproject.org/updates/FEDORA-2019-af50f19b83].

On Wed, Aug 28, 2019 at 08:08:23AM +, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> I started doing the rebuilds now. I'll submit buildroot overrides
> as I go. (I was hoping to do this before the bodhi enablement in F31,
> but I got confused about the deadline). Unfortunately mpich now failed,
> so there'll be some delay. I'll submit one big update for F31 at the
> end.
> 
> Zbyszek
> 
> 
> On Wed, Aug 28, 2019 at 06:19:36AM +, Philip Kovacs wrote:
> >  
> > Are you going to submit f31 bodhi updates for these rebuilds?  Am watching 
> > the notificationsOn Sunday, August 25, 2019, 09:01:05 PM EDT, Orion 
> > Poplawski  wrote:  
> >  
> >  On 8/25/19 1:17 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > Hi,
> > > 
> > > I made a minor mess in the mpich world and instead of upgrading to
> > > 3.3.1 from 3.2.1., I built 3.1.1. I was a bit surprised when I got
> > > a bug [1] that mpich in Fedora is from 2014 :(
> > > 
> > > I'd like to update to 3.3.1, but that needs newer hwloc which has an
> > > so-bump.
> > > 
> > > There's a number of users of hwloc:
> > > 
> > > mpich
> > > pmix
> > > openmpi
> > > pocl
> > > slurm
> > > hpx
> > > legion
> > > aircrack-ng
> > > gromacs
> > > 
> > > They all build fine with hwloc 2.0.4, except from legion.
> > > Legion is incompatible.
> > > I came up with a patch to partially disable hwloc use [2],
> > > and after reporting the issue upstream, I got the feedback
> > > that this is the correct approach [3].
> > > 
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1745252
> > > [2] https://src.fedoraproject.org/rpms/legion/pull-request/1
> > > [3] https://github.com/StanfordLegion/legion/issues/575
> > > 
> > > As a stop-gap measure, I rebuilt mpich-3.2.1 again today in
> > > rawhide and F31. I'd like to do the update though.
> > > 
> > > I plan to build hwloc-2.0 and the packages listed above, incl. legion
> > > with the patch on Wednesday.
> > > 
> > > Zbyszek
> > 
> > Sounds good to me.  Thanks for taking this on.
> > 
> > 
> > -- 
> > Orion Poplawski
> > Manager of NWRA Technical Systems          720-772-5637
> > NWRA, Boulder/CoRA Office            FAX: 303-415-9702
> > 3380 Mitchell Lane                      or...@nwra.com
> > Boulder, CO 80301                https://www.nwra.com/
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> >   
___
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: [HEADS UP] Retiring python2 and introducing python27 later this week

[Miro Hrončok]

On 29. 08. 19 5:25, Scott Talbert wrote:

On 27. 08. 19 22:20, Miro Hrončok wrote:

python27 build in progress.

Will retire python2 later tomorrow or on Friday (in case something is terribly
broken I want to have some maneuvering space).

Hey Miro,

I can't rebuild python-wxpython4 with the new python27.  This is what I'm 
seeing in the logs but it seems that the root cause is that 
/usr/include/python2.7/pyconfig-64.h is missing?


I've noticed this as well today. It is a packaging bug with excludes and I'm 
working on a hotfix. Will push ASAP, testing locally.


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

[Bug 1746739] New: Upgrade perl-Test2-Suite to 0.000126

[bugzilla]

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

Bug ID: 1746739
   Summary: Upgrade perl-Test2-Suite to 0.000126
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Test2-Suite
  Assignee: ppi...@redhat.com
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.000125 version. Upstream released 0.000126. When you
have free time, please upgrade it.

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