Signing key for f31?
Hi, I was browsing getfedora.org looking for the f31 PGP key that DNF is currently prompting me to accept or reject. I found that the old URL [1] is gone and doesn't redirect to the new one [2] that currently shows keys up to f30. Is there a reliable location where I can verify the f31 key today? I tried to browse the Rawhide guide but couldn't find the key fingerprints. Dridi [1] https://getfedora.org/en/keys/ [2] https://getfedora.org/en/security/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Where are armv7hl, i686 and ppc64le Container tar.xz files?
On 5/19/19 9:11 AM, Jun Aruga wrote: > I am suggesting a new feature "podman buildx" like "docker buildx" > that makes a better multi arch build experience. > See below URL if you are interested in it. > > Supporting building multi-platform images (podman buildx) > https://github.com/containers/buildah/issues/1590 > I think this is something that the community would have to address, I don't see it as a huge priority for the core developers at this point. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to submit Root CA to ship with Fedora
On Fri, Apr 26, 2019 at 2:06 AM Stephen Gallagher wrote: > On Thu, Apr 25, 2019 at 1:42 PM Danishka Navin wrote: > > > > > > > > On Wed, Apr 24, 2019 at 6:02 PM Sérgio Basto wrote: > >> > >> On Wed, 2019-04-24 at 11:35 +0530, Danishka Navin wrote: > >> > >> Hi, > >> > >> Sri Lanka Cert is gonna implement local Root CA. > >> How we can submit this Root CA with Fedora? > >> > >> I could not find enough information on this. > >> > >> > >> you can do one custom ca-certificates-2018.2.26-2.fc29.noarch package > and add your certificate to ca-truted in you system > > > > > > Its about officially distributed using formal channels, i.e: Operating > Systems and Browsers. > > This is not about testing locally. > > I mean it required to be in ca-certificates-2018.2.26-2.fc29.noarch > package by default. > > > > > That package comes from Mozilla's collection. If Mozilla approves it, > Fedora will pick it up as soon as an updated ca-certificates package > is released. That said, it sounds like the intent of that CA is for a > government-mandated man-in-the-middle attack to monitor secure > traffic. It is highly unlikely that will be accepted by Mozilla. > Seems government is working with Chinese tech people to run mass online surveillance system. http://www.themorning.lk/china-styled-mass-online-surveillance/ But I am not clear how Root CA can use to SSL MITM attack instead of user cert. -- Danishka Navin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
CORRECTION: Planned Outage - Fedora Core Services 2019-05-22 21:00 UTC
There will be an outage starting at 2019-05-22 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-22 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting productions servers which do require a full outage and downtime. Affected Services: koji.fedoraproject.org src.fedoraproject.org *.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7810 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to predict Python 3 SOABI naming scheme?!?
On Mon, May 20, 2019 at 07:58:09AM -0500, Richard Shaw wrote:
> I'm trying to get FreeCAD back in shape on Fedora[1] and what I hope is the
> last problem is that it's still building against the Python2 library
> (because it's default). I can override the behavior by specifying
> "-DPYTHON_SUFFIX= but it's different for every arch...
>
> $ python3
> Python 3.7.3 (default, Mar 27 2019, 13:41:07)
> [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sysconfig
> >>> sysconfig.get_config_var('SOABI')
> 'cpython-37m-x86_64-linux-gnu'
>
> I cobbled this together for the spec file but it may need work:
>
> %define py_suffix %(%{__python3} -c 'import sysconfig;
> sysconfig.get_config_var("SOABI")')
Erm, I think you'd get better results with a "print" thrown in there;
the interactive REPL interpreter shows you the value, but if you run
this through python3 -c, it will not actually output it to the standard
output unless you tell it to. Maybe try:
... -c 'import sysconfig; print(sysconfig.get_config_var("SOABI"))'
> The weird part is that it's evaluating as blank on Fedora 29 and 30[2]...
This much I'd expect, try with the print() in there.
> ...and working in Rawhide EXCEPT for armv7hl in which it's evaluating to[3]:
>
> -DPYTHON_SUFFIX=.cpython-37m-armv7hl-linux-gnu
I... honestly don't understand how this can happen. I don't understand
why python3 -c 'sysconfig.get_config_var()' would output anything...
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Nonresponsive maintainer mitr (Miloslav Trmač)
Hey all, We try to get some reply from mitr for more than a month. https://bugzilla.redhat.com/show_bug.cgi?id=1606827 I've e-mailed him three weeks ago. No response. Does anybody know how to reach him? Thanks, -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Planned Outage - Fedora Core Services 2019-04-10 21:00 UTC
On 20/05/2019 00:16, Stephen John Smoogen wrote: > > > > There will be an outage starting at 2019-04-10 21:00 UTC , > which will last approximately 5 hours. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/Infrastructure/UTCHowto > or run: > > date -d '2019-04-10 21:00UTC' > Isn't it just a bit late for this? Or, more seriously, what's the actual time? Given that the email doesn't seem to have spent over a month in mail server limbo, I'm assuming this was a copy-paste mistake. -- J. Randall Owens | http://www.GhiaPet.net/ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Planned Outage - Fedora Core Services 2019-04-10 21:00 UTC
My apologies Will fix. On Sun, 19 May 2019 at 19:16, Stephen John Smoogen wrote: > > > > There will be an outage starting at 2019-04-10 21:00 UTC , > which will last approximately 5 hours. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/Infrastructure/UTCHowto > or run: > > date -d '2019-04-10 21:00UTC' > > Reason for outage: > > There have been a number of kernel and low level library updates which > require a system reboot to put into place. We will be rebooting > productions servers which do require a full outage and downtime. > > Affected Services: > > koji.fedoraproject.org > src.fedoraproject.org > *.phx2.fedoraproject.org > > Ticket Link: > > https://pagure.io/fedora-infrastructure/issue/7810 > > Please join #fedora-admin or #fedora-noc on irc.freenode.net > or add comments to the ticket for this outage above. > -- > Stephen J Smoogen. > > -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora and the MDS CVEs
On Thu, May 16, 2019 at 07:27:24AM -0500, Justin Forbes wrote: > If you do not know what the MDS CVEs are, or would like more > infomation on them, there is a good write up at > https://access.redhat.com/security/vulnerabilities/mds Thank you Justin! I very much appreciate your work on this and the update. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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: Disable Root Password Login in SSH
On Fri, May 17, 2019 at 4:35 PM Kevin Fenzi wrote: > > On 5/17/19 5:23 AM, Stephen Gallagher wrote: > > ...snip... > > > 3) Force Anaconda to require the creation of a non-root user that is a > > member of the `wheel` group, so that this user can be used to SSH in > > and administer the system. Essentially, remove the root user creation > > spoke as an option from the interactive install. > > So, this is basically the old cloud-init makes a user that can sudo to > root thing. Can anyone explain in small words how this is more secure? > This is not "force Anaconda to create a specific user", it's "the interactive dialog won't complete the installation without you selecting a non-root administrative user of your choice". It's more secure in that a non-well-known username is less prone to being vulnerable to automated attacks. > I mean, in this case the attacker would need to guess the username in > addition to the password (where in the cloud cause this is known), but > otherwise why not just keep root password access ? > Guessing the username is *hard*. It's not something an average script will do. It protects against casual attacks. Yes, it isn't necessarily helping against targeted attacks, but those are an entirely different ball of wax. > I always found that cloud default anoying and useless and haven't yet > seen a good argument to not do it. > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
How to predict Python 3 SOABI naming scheme?!?
I'm trying to get FreeCAD back in shape on Fedora[1] and what I hope is the
last problem is that it's still building against the Python2 library
(because it's default). I can override the behavior by specifying
"-DPYTHON_SUFFIX= but it's different for every arch...
$ python3
Python 3.7.3 (default, Mar 27 2019, 13:41:07)
[GCC 8.3.1 20190223 (Red Hat 8.3.1-2)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('SOABI')
'cpython-37m-x86_64-linux-gnu'
I cobbled this together for the spec file but it may need work:
%define py_suffix %(%{__python3} -c 'import sysconfig;
sysconfig.get_config_var("SOABI")')
The weird part is that it's evaluating as blank on Fedora 29 and 30[2] and
working in Rawhide EXCEPT for armv7hl in which it's evaluating to[3]:
-DPYTHON_SUFFIX=.cpython-37m-armv7hl-linux-gnu
But the shiboken config file is named:
/usr/lib/cmake/Shiboken-1.2.4/ShibokenConfig.cpython-37m-arm-linux-gnueabi.cmake
Which is very different...
The best answer is probably to rebuild shiboken with Python3 being the
default but there should be a way to predict what the python3 SOABI naming
scheme will be...
Thanks,
Richard
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1709521
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1269159
[3] https://kojipkgs.fedoraproject.org//work/tasks/5021/34945021/build.log
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to predict Python 3 SOABI naming scheme?!?
On 20. 05. 19 14:58, Richard Shaw wrote:
I'm trying to get FreeCAD back in shape on Fedora[1] and what I hope is the last
problem is that it's still building against the Python2 library (because it's
default). I can override the behavior by specifying "-DPYTHON_SUFFIX=SOABI> but it's different for every arch...
$ python3
Python 3.7.3 (default, Mar 27 2019, 13:41:07)
[GCC 8.3.1 20190223 (Red Hat 8.3.1-2)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('SOABI')
'cpython-37m-x86_64-linux-gnu'
I cobbled this together for the spec file but it may need work:
%define py_suffix %(%{__python3} -c 'import sysconfig;
sysconfig.get_config_var("SOABI")')
Or:
$ python3-config --extension-suffix
.cpython-37m-x86_64-linux-gnu.so
(on 3.8: .cpython-38-x86_64-linux-gnu.so)
The weird part is that it's evaluating as blank on Fedora 29 and 30[2] and
working in Rawhide EXCEPT for armv7hl in which it's evaluating to[3]:
-DPYTHON_SUFFIX=.cpython-37m-armv7hl-linux-gnu
But the shiboken config file is named:
/usr/lib/cmake/Shiboken-1.2.4/ShibokenConfig.cpython-37m-arm-linux-gnueabi.cmake
Which is very different...
We do actually change some arch naming in here:
https://github.com/fedora-python/cpython/commit/e9def22e31801d9d75017e6752d3daf4099bc836
But not arm -> armv7hl.
I suspect that the name might be platform specific and the upstream name might
simply not be compatible with what we have in Fedora.
--
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://getfedora.org/code-of-conduct.html
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: Disable Root Password Login in SSH
On Fri, 2019-05-17 at 11:54 -0700, Kevin Fenzi wrote: > On 5/17/19 11:34 AM, Stephen John Smoogen wrote: > > On Fri, 17 May 2019 at 14:02, Chris Adams > > wrote: > ...snip... > > > > Make it a predefined kickstart thing they can do so all they > > > > have to do > > > is > > > > add a line in it that says > > > > > > > > ssh_remote --user= --keyfile= -- > > > > yesIwantrootandIknowitsbad > > > > > > If this is the desired path, I'd go with a couple of additional > > > arguments to existing directives: > > > > > > --enablerootssh (for rootpw or maybe auth?) > > > --sshkey (for both rootpw and user directives) > > > > > > > > Yeah.. --sshkey is a better name than --keyfile > > and --enablerootssh is better than --yesIwantrootandIknowitsbad > > Some may notice this has already happened in Fedora 22: > > https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html?highlight=ssh#sshkey > > I think there were some arm install cases that still needed ssh root > login post install, but those might be covered now (for example, a > host > that needs to join a ipa realm, so you need to login as root to set > that > up). CCing dgillmore here as I think he was the one who had the > example > last time this was brought up. Thank you for all the comments and suggestions. I would like to cover the important options in the change page so they can be used for a reference for anyone trying to figure out a solution for their use case. So far, I added the above link to the "Upgrade/compatibility impact" section, but since I am only a developer here and I do not maintain thousands of machines in the wild spawn by different technologies, I would like to ask you to update the page with your proposed solutions to your problems (it is still a wiki in the end). For anaconda, I filled the following issue [1]. [1] https://github.com/rhinstaller/anaconda/issues/1974 Regards, -- Jakub Jelen Senior Software Engineer Security Technologies Red Hat, Inc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Orphaned packages looking for new maintainers
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. This report is online at: https://churchyard.fedorapeople.org/orphans-2019-05-20.txt Packages retired today but still in this report: Ray cwiid gnue-common jam-control prover9 python-django-notifications-hq python-jabberbot python-port-for Request package ownership via: https://pagure.io/releng/issues Package (co)maintainers Status Change Ray orphan 7 weeks ago aeskulap orphan 5 weeks ago ahkab orphan 6 weeks ago ceph-deploy branto, fsimonce, ktdreyer, 2 weeks ago orphan, trhoden checkstyledbhole, greghellings, lef, 0 weeks ago mizdebsk, nsantos, orphan, rmyers clpbardcantrel, orphan 2 weeks ago compat-openssl10-pkcs11-helperorphan, rdieter 1 weeks ago cwiid orphan 7 weeks ago dvdbackup cicku, orphan5 weeks ago emacs-pymacs orphan 5 weeks ago gnome-dvb-daemon orphan 5 weeks ago gnome-shell-extension-panel-osd orphan 5 weeks ago gnue-common orphan 7 weeks ago gpart dcantrel, orphan 2 weeks ago h2akurtakov, dchen, lef, orphan2 weeks ago jam-control orphan 7 weeks ago json_simple jjelen, mizdebsk, orphan,0 weeks ago pmackinn, stevetraylen jwebunit orphan 1 weeks ago ltspfsenslaver, orphan 4 weeks ago monkeysphere ctubbsii, orphan 0 weeks ago ninja-ide echevemaster, orphan 4 weeks ago plaguedcbw, orphan 3 weeks ago prover9 orphan 7 weeks ago python-cachy orphan 0 weeks ago python-deltasigma orphan 6 weeks ago python-django-notifications-hqorphan 7 weeks ago python-jabberbot orphan 7 weeks ago python-port-for orphan 7 weeks ago python-pylev orphan 0 weeks ago python-pytest-testmon orphan, python-sig 0 weeks ago pywebkitgtk ivazquez, orphan, walters4 weeks ago rubygem-chunky_pngmmorsi, orphan 5 weeks ago rubygem-codemirror-rails orphan 4 weeks ago rubygem-commander maxamillion, orphan, tdawson 2 weeks ago rubygem-compass-960-pluginorphan 5 weeks ago rubygem-jquery-ui-rails orphan 2 weeks ago rubygem-paranoia orphan 1 weeks ago rubygem-sprite-factoryorphan 6 weeks ago rubygem-webratmmorsi, orphan 5 weeks ago system-config-firewallorphan, twoerner 2 weeks ago testoob orphan 1 weeks ago The following packages require above mentioned packages: Depending on: checkstyle (23), status change: 2019-05-14 (0 weeks ago) eclipse-checkstyle (maintained by: akurtakov, eclipse-sig, rmyers) eclipse-checkstyle-7.6.0-7.fc31.src requires checkstyle = 8.0-7.fc31 hadoop (maintained by: ctubbsii, denisarnaud, milleruntime) hadoop-2.7.6-5.fc29.src requires checkstyle = 8.0-7.fc31 hadoop-common-2.7.6-5.fc29.noarch requires
Re: Attempting to contact unresponsive maintainers: dkaspar flaper87
Hi there, On Mon, May 20, 2019 at 5:22 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, May 20, 2019 at 11:51:58AM +1000, Nathan Scott wrote: > > Please feel free to set default dstat BZ assignment to me in this case, > > Kevin. > > I don't think you want this package. dstat was (supposed to be) > retired in favour of pcp-dstat. Maybe the retirement wasn't complete? Yes, the old dstat package was retired. I'm one of the maintainers of pcp-dstat(1) which provides the /usr/bin/dstat symlink now. Users are still opening BZs against the dstat though (e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1711517 today) so they may as well come to me. cheers. -- Nathan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Attempting to contact unresponsive maintainers: dkaspar flaper87
On Mon, May 20, 2019 at 11:51:58AM +1000, Nathan Scott wrote: > Please feel free to set default dstat BZ assignment to me in this case, Kevin. I don't think you want this package. dstat was (supposed to be) retired in favour of pcp-dstat. Maybe the retirement wasn't complete? Zbyszek > > On Tue, May 14, 2019 at 5:21 PM Lukas Nykryn wrote: > > > > Hi, > > sorry for late answer I was on PTO, > > > > David no longer works in Red HAt and he is not interested in maintaining > > those packages anymore. > > Could you please set the main admin of initscripts to me? And I don't think > > we are interested in the rest of those packages. > > > > Lukas > > > > út 7. 5. 2019 v 23:18 odesílatel Kevin Fenzi napsal: > >> > >> I'd like to appologize for the delay in this email. > >> > >> The notices I get were being filtered and I didn't realize I wasn't > >> seeing them for a while. ;( > >> > >> > >> We've been told that the email addresses for these package maintainers > >> are no longer valid. I'm starting the unresponsive maintainer policy to > >> find out if they are still interested in maintaining their packages (and > >> if so, have them update their email addresses in FAS). > >> > >> If they're not interested in maintaining or we can't locate them in 1 > >> week, I'll have FESCo orphan the packages so that others can take them > >> over. > >> > >> If you have a way to contact these maintainers, please let them know > >> that we'd appreciate knowing what to do with their packages. Thanks! > >> > >> dkaspar: > >> > >> "dstat": "dkaspar", > >> "initscripts": "dkaspar", > >> "mtools": "dkaspar", > >> "tcsh": "dkaspar", > >> > >> flaper87: > >> > >> "redis": "flaper87", > >> > >> > >> Thanks, > >> > >> kevin > >> > >> ___ > >> devel mailing list -- devel@lists.fedoraproject.org > >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org > >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > >> 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://getfedora.org/code-of-conduct.html > > 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://getfedora.org/code-of-conduct.html > 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Intent to drop python2-tornado
I intend to drop python2-tornado. There are following dependent packages:
- python-httpretty
build time, for Python 2 tests, tests can be disabled
- python-pika
build time, for Python 2 tests, one file can be skipped
- python-urllib3
build time, for Python 2 tests, tests can be disabled
- salt (and salt-{api,cloud,syndic,ssh,master,minion})
runtime, python 3 switch is blocked by a fixable bug
https://github.com/saltstack/salt/issues/51883
salt is not required by anything
- uwsgi-plugin-python2-tornado (from uwsgi)
runtime, but not required by anything
- bup and bup-web
runtime and buildtime, but not required by anything
If anybody wants to package python2-tornado before we drop it, let me know in 3
weeks.
Reasons below:
Forwarded Message
Subject: Let's update tornado to 6 and drop python2-torando
Date: Wed, 15 May 2019 16:57:57 +0200
From: Miro Hrončok
Reply-To: Fedora Python SIG
Organisation: Red Hat
To: Fedora Python SIG ,
abomp...@fedoraproject.org, or...@fedoraproject.org, toms...@fedoraproject.org
Hi.
Tornado 6 doesn't support Python 2. Let's update the python-torando package to
Python 3 only. There are several consumers of python2-torando and if their
maintainers are interested, they can package it separately.
$ dnf repoquery --repo=compose{,-source} --whatrequires python2-tornado
bup-0:0.29.2-3.fc30.src
bup-web-0:0.29.2-3.fc30.x86_64
python-httpretty-0:0.9.5-5.fc30.src
python-pika-0:1.0.1-1.fc31.src
python-urllib3-0:1.24.2-1.fc31.src
salt-0:2019.2.0-1.fc31.noarch
uwsgi-plugin-python2-tornado-0:2.0.17.1-10.fc31.x86_64
Note that tornado is often used to test things. We can (and should) just skip
such tests from Python 2 httpretty, pika and urllib3.
Is the plan OK? I'll talk to the dependent packages maintainers, but wanted to
check with torando co-maintainers first.
--
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to submit Root CA to ship with Fedora
On Mon, May 20, 2019 at 8:53 AM Danishka Navin wrote: > Seems government is working with Chinese tech people to run mass online > surveillance system. > http://www.themorning.lk/china-styled-mass-online-surveillance/ > > > But I am not clear how Root CA can use to SSL MITM attack instead of user > cert. > If you trust a root CA for signing websites, then they can sign a new certificate for google.com, then modify DNS to send you to a non-Google server presenting their certificate, signed by the corrupt CA. They'd decrypt all of your traffic, read it, re-encrypt it with the real google.com cert and pass it along. You would still see the website you expect to, but in the middle all of your traffic is exposed to the man-in-the-middle server. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to predict Python 3 SOABI naming scheme?!?
On Mon, May 20, 2019 at 8:09 AM Miro Hrončok wrote:
> On 20. 05. 19 14:58, Richard Shaw wrote:
> > I'm trying to get FreeCAD back in shape on Fedora[1] and what I hope is
> the last
> > problem is that it's still building against the Python2 library (because
> it's
> > default). I can override the behavior by specifying
> "-DPYTHON_SUFFIX= > SOABI> but it's different for every arch...
> >
> > $ python3
> > Python 3.7.3 (default, Mar 27 2019, 13:41:07)
> > [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)] on linux
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import sysconfig
> > >>> sysconfig.get_config_var('SOABI')
> > 'cpython-37m-x86_64-linux-gnu'
> >
> > I cobbled this together for the spec file but it may need work:
> >
> > %define py_suffix %(%{__python3} -c 'import sysconfig;
> > sysconfig.get_config_var("SOABI")')
>
> Or:
>
> $ python3-config --extension-suffix
> .cpython-37m-x86_64-linux-gnu.so
>
Potentially a little easier but then I would have to sed out the ".so"...
> The weird part is that it's evaluating as blank on Fedora 29 and 30[2]
> and
> > working in Rawhide EXCEPT for armv7hl in which it's evaluating to[3]:
> >
> > -DPYTHON_SUFFIX=.cpython-37m-armv7hl-linux-gnu
> >
> > But the shiboken config file is named:
> >
> >
> /usr/lib/cmake/Shiboken-1.2.4/ShibokenConfig.cpython-37m-arm-linux-gnueabi.cmake
> >
> > Which is very different...
> We do actually change some arch naming in here:
>
>
> https://github.com/fedora-python/cpython/commit/e9def22e31801d9d75017e6752d3daf4099bc836
>
> But not arm -> armv7hl.
>
> I suspect that the name might be platform specific and the upstream name
> might
> simply not be compatible with what we have in Fedora.
>
Ok, is this a recent change that a simple rebuild would fix? Shouldn't the
shiboken cmake file be generated using the same logic?
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to predict Python 3 SOABI naming scheme?!?
On Mon, May 20, 2019 at 8:10 AM Peter Pentchev wrote:
> On Mon, May 20, 2019 at 07:58:09AM -0500, Richard Shaw wrote:
> >
> > I cobbled this together for the spec file but it may need work:
> >
> > %define py_suffix %(%{__python3} -c 'import sysconfig;
> > sysconfig.get_config_var("SOABI")')
>
> Erm, I think you'd get better results with a "print" thrown in there;
> the interactive REPL interpreter shows you the value, but if you run
> this through python3 -c, it will not actually output it to the standard
> output unless you tell it to. Maybe try:
>
> ... -c 'import sysconfig; print(sysconfig.get_config_var("SOABI"))'
>
Ok, I added that and it appears to be working (running a scratch build now)
but I do seem to inconsistently get a fg: no job control error but it
doesn't seem to hurt anything.
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
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: Disable Root Password Login in SSH
On 5/20/19 9:09 AM, Przemek Klosowski wrote: > On 5/17/19 4:34 PM, Kevin Fenzi wrote: >> So, this is basically the old cloud-init makes a user that can sudo to >> root thing. Can anyone explain in small words how this is more secure? > > In a large system, it allows granular revocation of access (Joe Bow quit > and we disabled his account) but this is not what Cloud images do. They create 1 non root account 'fedora' (or centos or rhel or whatever) for all access (by default). > and accountability (who logged in as root > and installed PHP 1.0?). In this case it was 'fedora' user from ip X.x.x.x. Which is (in my mind) no better or different than it was 'root' from ip x.x.x.x. 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://getfedora.org/code-of-conduct.html 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: Disable Root Password Login in SSH
On 5/20/19 12:19 PM, Kevin Fenzi wrote: On 5/20/19 9:09 AM, Przemek Klosowski wrote: On 5/17/19 4:34 PM, Kevin Fenzi wrote: So, this is basically the old cloud-init makes a user that can sudo to root thing. Can anyone explain in small words how this is more secure? In a large system, it allows granular revocation of access (Joe Bow quit and we disabled his account) but this is not what Cloud images do. They create 1 non root account 'fedora' (or centos or rhel or whatever) for all access (by default). Right, but it's just a stepping stone to a world with universal authentication, and granular authorization based on credentials from that universal authentication. and accountability (who logged in as root and installed PHP 1.0?). In this case it was 'fedora' user from ip X.x.x.x. Which is (in my mind) no better or different than it was 'root' from ip x.x.x.x. Ditto. I'ts necessary but not sufficient. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: two Ceph updates for f28, f29, stuck in pending testing for six days
On 3/22/19 3:07 PM, Kevin Fenzi wrote: On 3/21/19 5:45 PM, Kaleb Keithley wrote: On Tue, Feb 19, 2019 at 3:18 AM Kevin Fenzi wrote: On 2/18/19 12:56 PM, Kaleb Keithley wrote: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1c53f1a6c8 https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a2e72916a Would someone please give them a kick? For some reason autosign likes to not process these correctly. I've retagged them to get it to do another pass... Sorry for not fixing them sooner. Looks like another Ceph build is stuck. https://bodhi.fedoraproject.org/updates/FEDORA-2019-16c36506c1 Would someone kick it please? Thanks Fixed, and I looked and asked upstream and this is fixed in sigul 1.0. So, hopefully we won't have to keep doing this too much longer. kevin Hey Kevin, might I ask what fp.o is using for hosting sigul or package signing these days? I have a private setup that works on EL7 using a special builder-rpms.repo, thanks to your help some years ago, but that version seems to be quite dated now. I've tried recently putting both on F29 but the Server was an absolute no go -- IIRC due to the whole gpgme incompatibilty mess. I can get the Bridge to run on F29 but it goes wonky if left inactive for too long ... something like overnight is enough. Meanwhile, things like [0] make it look orphaned (see Assignee) and FTBFS for F30 [1]. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1701923 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1675996 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to predict Python 3 SOABI naming scheme?!?
On 20. 05. 19 17:04, Richard Shaw wrote> > The weird part is that it's evaluating as blank on Fedora 29 and 30[2] and > working in Rawhide EXCEPT for armv7hl in which it's evaluating to[3]: > > -DPYTHON_SUFFIX=.cpython-37m-armv7hl-linux-gnu > > But the shiboken config file is named: > > /usr/lib/cmake/Shiboken-1.2.4/ShibokenConfig.cpython-37m-arm-linux-gnueabi.cmake > > Which is very different... We do actually change some arch naming in here: https://github.com/fedora-python/cpython/commit/e9def22e31801d9d75017e6752d3daf4099bc836 But not arm -> armv7hl. I suspect that the name might be platform specific and the upstream name might simply not be compatible with what we have in Fedora. Ok, is this a recent change that a simple rebuild would fix? I'm not aware of any recent change to this. I doubt a rebuild would change anything. Shouldn't the shiboken cmake file be generated using the same logic? While I sometimes pretend I understand Python, I'm Jon Snow when cmake is involved (I know nothing). Sorry, but I'm not able to help you here. -- 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://getfedora.org/code-of-conduct.html 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: Disable Root Password Login in SSH
On 5/17/19 4:34 PM, Kevin Fenzi wrote: So, this is basically the old cloud-init makes a user that can sudo to root thing. Can anyone explain in small words how this is more secure? In a large system, it allows granular revocation of access (Joe Bow quit and we disabled his account) and accountability (who logged in as root and installed PHP 1.0?). ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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: 20190520.n.0 changes
OLD: Fedora-Rawhide-20190517.n.0 NEW: Fedora-Rawhide-20190520.n.0 = SUMMARY = Added images:2 Dropped images: 7 Added packages: 1 Dropped packages:0 Upgraded packages: 164 Downgraded packages: 0 Size of added packages: 31.34 MiB Size of dropped packages:0 B Size of upgraded packages: 4.35 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -429.91 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Design_suite live i386 Path: Labs/i386/iso/Fedora-Design_suite-Live-i386-Rawhide-20190520.n.0.iso Image: Design_suite live x86_64 Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20190520.n.0.iso = DROPPED IMAGES = Image: Cloud_Base vmdk s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190517.n.0.s390x.vmdk Image: Cloud_Base qcow2 s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190517.n.0.s390x.qcow2 Image: Mate raw-xz armhfp Path: Spins/armhfp/images/Fedora-Mate-armhfp-Rawhide-20190517.n.0-sda.raw.xz Image: KDE raw-xz armhfp Path: Spins/armhfp/images/Fedora-KDE-armhfp-Rawhide-20190517.n.0-sda.raw.xz Image: Cloud_Base raw-xz s390x Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20190517.n.0.s390x.raw.xz Image: Container_Minimal_Base docker s390x Path: Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20190517.n.0.s390x.tar.xz Image: SoaS live x86_64 Path: Spins/x86_64/iso/Fedora-SoaS-Live-x86_64-Rawhide-20190517.n.0.iso = ADDED PACKAGES = Package: minuet-19.04.1-2.fc31 Summary: A KDE Software for Music Education RPMs:minuet minuet-data minuet-devel Size:31.34 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: MUMPS-5.1.2-10.fc31 Old package: MUMPS-5.1.2-9.fc30 Summary: A MUltifrontal Massively Parallel sparse direct Solver RPMs: MUMPS MUMPS-common MUMPS-devel MUMPS-examples MUMPS-mpich MUMPS-mpich-devel MUMPS-mpich-examples MUMPS-openmp MUMPS-openmp-devel MUMPS-openmp-examples MUMPS-openmpi MUMPS-openmpi-devel MUMPS-openmpi-examples Size: 75.78 MiB Size change: 1.71 MiB Changelog: * Fri May 17 2019 Antonio Trande - 5.1.2-10 - Require scalapack explicity (rhbz #1711291 #1711289) - Disable tests with OpenMPI-4 Package: R-knitr-1.23-1.fc31 Old package: R-knitr-1.22-1.fc31 Summary: A General-Purpose Package for Dynamic Report Generation in R RPMs: R-knitr Size: 1.19 MiB Size change: -44.80 KiB Changelog: * Sat May 18 2019 Elliott Sales de Andrade - 1.23-1 - Update to latest version Package: R-svglite-1.2.2-1.fc31 Old package: R-svglite-1.2.1-1.fc31 Summary: An 'SVG' Graphics Device RPMs: R-svglite Size: 713.20 KiB Size change: 21.70 KiB Changelog: * Fri May 17 2019 Elliott Sales de Andrade - 1.2.2-1 - Update to latest version Package: ShellCheck-0.6.0-4.fc31 Old package: ShellCheck-0.6.0-3.fc30 Summary: Shell script analysis tool RPMs: ShellCheck ghc-ShellCheck ghc-ShellCheck-devel Size: 67.04 MiB Size change: -25.18 MiB Package: Thunar-1.8.6-1.fc31 Old package: Thunar-1.8.4-5.fc31 Summary: Thunar File Manager RPMs: Thunar Thunar-devel Thunar-docs Size: 10.29 MiB Size change: 46.43 KiB Changelog: * Sat May 18 2019 Mukundan Ragavan - 1.8.5-1 - Update to 1.8.5 - Drop patches no longer needed * Sat May 18 2019 Mukundan Ragavan - 1.8.6-1 - Update to 1.8.6 Package: alembic-1.7.11-1.fc31 Old package: alembic-1.7.8-4.fc31 Summary: Open framework for storing and sharing scene data RPMs: alembic alembic-devel alembic-libs Size: 6.15 MiB Size change: 9.16 KiB Changelog: * Sat May 18 2019 Luya Tshimbalanga - 1.7.11-1 - Update to 1.7.11 Package: ansible-2.8.0-2.fc31 Old package: ansible-2.8.0-0.4rc3.fc31 Summary: SSH-based configuration management, deployment, and task execution system RPMs: ansible ansible-doc Size: 22.06 MiB Size change: -754.75 KiB Changelog: * Fri May 17 2019 Kevin Fenzi - 2.8.0-1 - Update to 2.8.0 final. - Add datadirs for other packages to land ansible files in. * Fri May 17 2019 Kevin Fenzi - 2.8.0-2 - Fixes for various releases build/test issues. Package: aqute-bnd-3.5.0-6.fc31 Old package: aqute-bnd-3.5.0-5.fc30 Summary: BND Tool RPMs: aqute-bnd aqute-bnd-javadoc aqute-bndlib bnd-maven-plugin Size: 2.77 MiB Size change: 1.66 KiB Changelog: * Fri Apr 12 2019 Marian Koncek - 3.5.0-6 - Port to OSGI 7.0.0 Package: bacula-9.4.3-2.fc31 Old package: bacula-9.4.3-1.fc31 Summary: Cross platform network backup for Linux, Unix, Mac and Windows RPMs: bacula-client bacula-common bacula-console bacula-console-bat bacula-devel bacula-director bacula-libs bacula-libs-sql bacula-logwatch bacula-storage bacula-traymonitor nagios-plugins-bacula Size: 14.17 MiB Size change: 4.58 KiB Changelog: * Sat May 18 2019
Fedora Rawhide-20190520.n.0 compose check report
Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Compose FAILS proposed Rawhide gating check! 7 of 47 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 19/146 (x86_64), 4/24 (i386), 1/2 (arm) ID: 403104 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/403104 ID: 403121 Test: x86_64 Workstation-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/403121 ID: 403132 Test: x86_64 KDE-live-iso install_default_upload **GATING** URL: https://openqa.fedoraproject.org/tests/403132 ID: 403133 Test: x86_64 KDE-live-iso install_default@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/403133 ID: 403134 Test: x86_64 KDE-live-iso install_no_user **GATING** URL: https://openqa.fedoraproject.org/tests/403134 ID: 403143 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/403143 ID: 403146 Test: i386 KDE-live-iso install_default URL: https://openqa.fedoraproject.org/tests/403146 ID: 403147 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/403147 ID: 403157 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/403157 ID: 403159 Test: x86_64 universal install_anaconda_text **GATING** URL: https://openqa.fedoraproject.org/tests/403159 ID: 403161 Test: x86_64 universal install_repository_http_variation **GATING** URL: https://openqa.fedoraproject.org/tests/403161 ID: 403163 Test: x86_64 universal install_mirrorlist_graphical **GATING** URL: https://openqa.fedoraproject.org/tests/403163 ID: 403178 Test: x86_64 universal install_ext3 URL: https://openqa.fedoraproject.org/tests/403178 ID: 403183 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/403183 ID: 403189 Test: x86_64 universal install_blivet_ext3@uefi URL: https://openqa.fedoraproject.org/tests/403189 ID: 403195 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/403195 ID: 403202 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/403202 ID: 403205 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/403205 ID: 403211 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/403211 ID: 403214 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/403214 ID: 403218 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/403218 ID: 403236 Test: i386 universal install_ext3 URL: https://openqa.fedoraproject.org/tests/403236 ID: 403238 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/403238 ID: 403241 Test: i386 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/403241 Soft failed openQA tests: 3/24 (i386), 5/146 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 403107 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/403107 ID: 403108 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/403108 ID: 403119 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/403119 ID: 403126 Test: x86_64 Workstation-boot-iso memory_check@uefi URL: https://openqa.fedoraproject.org/tests/403126 ID: 403127 Test: x86_64 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/403127 ID: 403131 Test: i386 Workstation-boot-iso memory_check URL: https://openqa.fedoraproject.org/tests/403131 ID: 403215 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/403215 ID: 403217 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/403217 Passed openQA tests: 112/146 (x86_64), 17/24 (i386) Skipped gating openQA tests: 4/146 (x86_64) ID: 403138 Test: x86_64 KDE-live-iso base_update_cli **GATING** URL: https://openqa.fedoraproject.org/tests/403138 ID: 403139 Test: x86_64 KDE-live-iso base_system_logging **GATING** URL: https://openqa.fedoraproject.org/tests/403139 ID: 403141 Test: x86_64 KDE-live-iso desktop_terminal **GATING** URL: https://openqa.fedoraproject.org/tests/403141 ID: 403142 Test: x86_64 KDE-live-iso desktop_browser **GATING** URL: https://openqa.fedoraproject.org/tests/403142 Skipped non-gating openQA tests: 7 of 172 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to
[Fedocal] Reminder meeting : Modularity Team (weekly)
Dear all, You are kindly invited to the meeting: Modularity Team (weekly) on 2019-05-21 from 15:00:00 to 16:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Meeting of the Modularity Team. More information available at: [Modularity Team Docs](https://docs.pagure.org/modularity/) The agenda for the meeting is available as flagged tickets [in the Modularity repository](https://pagure.io/modularity/issues?status=Open=Meeting). Source: https://apps.fedoraproject.org/calendar/meeting/9480/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Self-Contained Change proposal: Track Changes in Taiga
https://fedoraproject.org/wiki/Changes/fedora-change-wrangler = Track Changes in Taiga = The Motivation for this proposal is to propose using the Taiga instance at teams.fedoraproject.org for Change processing. [[User:Bcotton/UsePagureForChanges|Using Pagure]] was previously proposed for this. The new Change Processing workflow aims to simplify the process to improve visibility and ease of management. == Summary == The current process allows contributors to propose changes in upcoming Fedora releases. However, the management of those feature proposals is cumbersome and requires several manual steps. This introduces more opportunity for error and reduces the time available to the Change Wrangler for more valuable contributions to Fedora. In particular, the current process includes artifacts and discussion in the Fedora Wiki, on mailing lists, FESCo tickets, Bugzilla tickets, and Docs tickets. The current process is cumbersome with several manual steps,this introduces more opportunity for error and reduces the time available for the Change Wrangler. A Cli Tool Written in Python that interacts with Taiga,Pagure and Bugzilla.Functionality includes Promoting,announcing,submitting,accepting and updating the changes across the three platforms and over mailing list. The new process will consolidate much of the information in Taiga.Proposed Changes will be submitted as an issue in Taiga. The description of the Issue will include the content with few exceptions: * System-Wide or Self-Contained change will be indicated by a binary in the issue metadata * Fedora release will be indicated by a milestone in the issue metadata * Change status will be indicated by a list selection in the issue metadata == Owner == * Name: [[User:Pac23| Manas Mangaonkar]] * Email: manasmangaon...@gmail.com || pa...@fedoraproject.org * Name: [[User:Bcotton | Ben Cotton]] * Email: bcot...@redhat.com == Detailed Description == As Part of GSoC 2019 the fedora-change-wrangler tool will be developed to smooth out the workflow,reduce Manual Work involved for both the Contributors and the Change-Wrangler(FPgm). The tool makes it easy by covering all the functionality required for the process of moving forward proposals. The tool will be developed using Python 3.6+ and will interact with Taiga/Pagure/Bugzilla via their API and the Mailing List via SMTP. The General Workflow would be : 1. Change Owner opens an issue and fills in the fields. When they are ready to submit the Change proposal, they set the status to"Ready for Wrangler". 2. The Change Wrangler (FPgM) reviews the proposal. If it is incomplete, they set the status back to "New" and inform the Change Owner of what's needed. If it is ready to process, then... Functionality covered 1. Promote * The issue will be promoted to a user story in taiga,copies the contents of the custom fields from the issue to the user story. Closes the issue. 2. Announce * The tool would have the functionality to enable announcing the change proposal to devel and devel-announce lists using smtp. It will also automatically change the story status to announced. 3. fesco-submit * Allowing creation of a new issue in the FESco Pagure repo directly from the command line. 4. Accept * Once the changes are accepted the change-wrangler can create a tracking bug in Bugzilla along with release notes on Pagure.THe status of the user story is updated to accepted aswell. 5. Update * Status can be changed to testable if BZ is "Modified" and to Complete is BZ is "ON_QA" 6. Creation of Report * The user can create a report to provide quick view of changes and their status. It can be in wiki or Html form. Techstack: * Python3.6+ * SMTP * Taiga/Pagure/Bugzilla API's * Nano/Gedit/Vi ( Inbuilt support to edit text) * Kerberos(For authentication) The current sample arg created looks like this [ change-tool convert --taiga ] . The advantage of this the Manager would be able to specify unlimited no of issues to change at once in a single command using the issue no in taiga to convert to user story. == Benefit to Fedora == The proposed change will make the change-process easier for everyone.Everyone would be able to see them in one place with status,id filters. The current wiki process can be bit difficult for formatting,having defined fields would mean easy access without the cumbersome wiki edits. Since changes would be submitted in Issue format on Taiga,pre-submission discussions would be available thus getting suggestions/feedback at the first stage itself would be easy for everyone involved. == Scope == * Proposal owners: I will be working with the Change-Wrangler(Ben Cotton) throughout the summer to create this tool from scratch. * Other developers: N/A (not a System Wide Change) * Release engineering:(no release engineering impact is expected) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == N/A (not a System Wide Change) == How To Test == N/A (not a System Wide
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 --- Comment #12 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc29 has been pushed to the Fedora 29 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-f1c561ba25 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 --- Comment #6 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc29 has been pushed to the Fedora 29 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-f1c561ba25 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 --- Comment #2 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5f45944bf -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 --- Comment #8 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5f45944bf -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 Fedora Update System changed: What|Removed |Added Status|ON_QA |MODIFIED --- Comment #7 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1c561ba25 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 --- Comment #1 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f1c561ba25 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 Jitka Plesnikova changed: What|Removed |Added Status|NEW |MODIFIED Fixed In Version||perl-CPAN-Perl-Releases-4.0 ||2-1.fc31 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 --- Comment #3 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-aff62cdb11 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 --- Comment #9 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-aff62cdb11 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Orphaned packages looking for new maintainers
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. This report is online at: https://churchyard.fedorapeople.org/orphans-2019-05-20.txt Packages retired today but still in this report: Ray cwiid gnue-common jam-control prover9 python-django-notifications-hq python-jabberbot python-port-for Request package ownership via: https://pagure.io/releng/issues Package (co)maintainers Status Change Ray orphan 7 weeks ago aeskulap orphan 5 weeks ago ahkab orphan 6 weeks ago ceph-deploy branto, fsimonce, ktdreyer, 2 weeks ago orphan, trhoden checkstyledbhole, greghellings, lef, 0 weeks ago mizdebsk, nsantos, orphan, rmyers clpbardcantrel, orphan 2 weeks ago compat-openssl10-pkcs11-helperorphan, rdieter 1 weeks ago cwiid orphan 7 weeks ago dvdbackup cicku, orphan5 weeks ago emacs-pymacs orphan 5 weeks ago gnome-dvb-daemon orphan 5 weeks ago gnome-shell-extension-panel-osd orphan 5 weeks ago gnue-common orphan 7 weeks ago gpart dcantrel, orphan 2 weeks ago h2akurtakov, dchen, lef, orphan2 weeks ago jam-control orphan 7 weeks ago json_simple jjelen, mizdebsk, orphan,0 weeks ago pmackinn, stevetraylen jwebunit orphan 1 weeks ago ltspfsenslaver, orphan 4 weeks ago monkeysphere ctubbsii, orphan 0 weeks ago ninja-ide echevemaster, orphan 4 weeks ago plaguedcbw, orphan 3 weeks ago prover9 orphan 7 weeks ago python-cachy orphan 0 weeks ago python-deltasigma orphan 6 weeks ago python-django-notifications-hqorphan 7 weeks ago python-jabberbot orphan 7 weeks ago python-port-for orphan 7 weeks ago python-pylev orphan 0 weeks ago python-pytest-testmon orphan, python-sig 0 weeks ago pywebkitgtk ivazquez, orphan, walters4 weeks ago rubygem-chunky_pngmmorsi, orphan 5 weeks ago rubygem-codemirror-rails orphan 4 weeks ago rubygem-commander maxamillion, orphan, tdawson 2 weeks ago rubygem-compass-960-pluginorphan 5 weeks ago rubygem-jquery-ui-rails orphan 2 weeks ago rubygem-paranoia orphan 1 weeks ago rubygem-sprite-factoryorphan 6 weeks ago rubygem-webratmmorsi, orphan 5 weeks ago system-config-firewallorphan, twoerner 2 weeks ago testoob orphan 1 weeks ago The following packages require above mentioned packages: Depending on: checkstyle (23), status change: 2019-05-14 (0 weeks ago) eclipse-checkstyle (maintained by: akurtakov, eclipse-sig, rmyers) eclipse-checkstyle-7.6.0-7.fc31.src requires checkstyle = 8.0-7.fc31 hadoop (maintained by: ctubbsii, denisarnaud, milleruntime) hadoop-2.7.6-5.fc29.src requires checkstyle = 8.0-7.fc31 hadoop-common-2.7.6-5.fc29.noarch requires
Planned Outage - Fedora Staging Services 2019-05-20 21:00 UTC
There will be an outage starting at 2019-05-20 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-20 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting staging and several non-PHX2 servers which do not require a full outage due to redundancy or low service level expectations. Affected Services: *.stg.fedoraproject.org *.stg.phx2.fedoraproject.org osuosl02.fedoraproject.org pagure-stg01.fedoraproject.org osuosl02.fedoraproject.org proxy09.fedoraproject.org osuosl02.fedoraproject.org smtp-mm-osuosl01.fedoraproject.org osuosl02.fedoraproject.org unbound-osuosl01.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7808 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Planned Outage - Fedora Proxies and Remote Servers Updates/Reboots - 2019-05-21 21:00 UTC
There will be an outage starting at 2019-05-21 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-21 21:00UTC' Reason for outage: We have come to chew gum and reboot servers, and we have all run out of gum. There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting staging and non-PHX2 servers which do not require a full outage due to redundancy or low service level expectations. Affected Services: proxy05.fedoraproject.org coloamer01.fedoraproject.org:proxy08.fedoraproject.org:running:1 dedicatedsolutions01.fedoraproject.org:proxy11.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:download-ib01.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:noc02.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:pagure-proxy01.fedoraproject.org:running:1 ibiblio01.fedoraproject.org:proxy04.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:ns02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:people02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:proxy12.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:smtp-mm-ib01.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:torrent02.fedoraproject.org:running:1 ibiblio05.fedoraproject.org:unbound-ib01.fedoraproject.org:running:1 internetx01.fedoraproject.org:ns05.fedoraproject.org:running:1 internetx01.fedoraproject.org:proxy02.fedoraproject.org:running:1 osuosl01.fedoraproject.org:pagure01.fedoraproject.org:running:1 osuosl01.fedoraproject.org:proxy06.fedoraproject.org:running:1 osuosl01.fedoraproject.org:repospanner-osuosl01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:keys01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:pagure-stg01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:proxy09.fedoraproject.org:running:1 osuosl02.fedoraproject.org:smtp-mm-osuosl01.fedoraproject.org:running:1 osuosl02.fedoraproject.org:unbound-osuosl01.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:ci-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:proxy14.fedoraproject.org:running:1 virthost-cc-rdu01.fedoraproject.org:smtp-mm-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:infinote.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:proxy03.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:repospanner-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu02.fedoraproject.org:unbound-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu03.fedoraproject.org:download-cc-rdu01.fedoraproject.org:running:1 virthost-cc-rdu03.fedoraproject.org:ipv6-test.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:bastion13.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:batcave13.rdu2.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:ns13.rdu2.fedoraproject.org:running:1 virthost-rdu01.fedoraproject.org:proxy13.fedoraproject.org:running:1 data-analysis01.phx2.fedoraproject.org dl.fedoraproject.org (service has multiple front ends so outages should be short per) Ticket Link: https://pagure.io/fedora-infrastructure/issue/7809 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
CORRECTION: Planned Outage - Fedora Core Services 2019-05-22 21:00 UTC
There will be an outage starting at 2019-05-22 21:00 UTC , which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-05-22 21:00UTC' Reason for outage: There have been a number of kernel and low level library updates which require a system reboot to put into place. We will be rebooting productions servers which do require a full outage and downtime. Affected Services: koji.fedoraproject.org src.fedoraproject.org *.phx2.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7810 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Action needed: Recythonize the sources of your packages
Hi there I have rebuilt https://apps.fedoraproject.org/packages/portmidi with cythonizing during build rather than using the project-shipped ancient cython output. Is this change supposed to trickle down to F30? (The package itself needs to go away sooner or later anyways.) MIchael ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
[Bug 1711899] New: perl-CPS-0.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711899 Bug ID: 1711899 Summary: perl-CPS-0.19 is available Product: Fedora Version: rawhide Status: NEW Component: perl-CPS Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.19 Current version/release in rawhide: 0.18-14.fc30 URL: http://search.cpan.org/dist/CPS/ 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/2738/ -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711899] perl-CPS-0.19 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711899 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-CPS-0.19-1.fc31 Resolution|--- |RAWHIDE Last Closed||2019-05-20 12:46:17 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711815] perl-CPS-0.18-14.fc31 FTBFS: Can't resolve method "done_cb" overloading "&{}" in package "CPS::Future"
https://bugzilla.redhat.com/show_bug.cgi?id=1711815 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version||perl-CPS-0.19-1.fc31 Resolution|--- |RAWHIDE Last Closed||2019-05-20 12:53:31 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Action needed: Recythonize the sources of your packages
On 20. 05. 19 14:47, Michael J Gruber wrote: Hi there I have rebuilt https://apps.fedoraproject.org/packages/portmidi with cythonizing during build rather than using the project-shipped ancient cython output. Is this change supposed to trickle down to F30? Thanks, all we need is a rawhide push. -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Action needed: Recythonize the sources of your packages
Hello packagers. During the rebuilds for Python 3.8, we have found out that your package most likely has precythonized C sources. There was an update to Cython and the C sources needs to be regenerated. In line with Fedora packaging policies and guidelines, this should be done anyway. What needs to be done: 1. BR python3-Cython 2. figure out what C sources come from Cython sources look for: /* Generated by Cython */ on the top of them often, all .c files are generated from Cython sources, but not always 3. in %prep, delete those files If you build for Python 2 and Python 3, I recommend to only BR python3-Cython and not python2-Cython, run %py3_build before %py2_build (Cython produces the same sources on both Python versions). Some setup.py files have custom detection whether Cython needs to be run, if the above doesn't work alone, examine setup.py and search for "cython". When you do this, reply to this thread, so we know we should rebuild your package for 3.8 in https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Thank you for you help. Maintainers by package: afflib kwizart rebus mpi4py deji tomspur portmidi bsjones mjg xavierb python-PyMuPDF swt2c python-comprefforathoscr python-cytoolz orion python-http-parser bkabrda ralph python-indexed_gzip ankursinha python-llfusedfateyev maci python-pandaskushal orion sergiopr wakko666 python-pybloomfiltermmap athmane python-pykdtree qulogic python-sep sergiopr python-shapely jcp volter python-ssh2-python ignatenkobrain python-wsaccel jujens scipycstratak jspaleta orion tomspur ttomecek Packages by maintainer: ankursinha python-indexed_gzip athmanepython-pybloomfiltermmap athoscrpython-compreffor bkabrdapython-http-parser bsjonesportmidi cstratak scipy deji mpi4py dfateyev python-llfuse ignatenkobrain python-ssh2-python jcppython-shapely jspaleta scipy jujens python-wsaccel kushal python-pandas kwizartafflib maci python-llfuse mjgportmidi orion python-cytoolz python-pandas scipy qulogicpython-pykdtree ralph python-http-parser rebus afflib sergiopr python-pandas python-sep swt2c python-PyMuPDF tomspurmpi4py scipy ttomecek scipy volter python-shapely wakko666 python-pandas xavierbportmidi -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
[Bug 1711815] New: perl-CPS-0.18-14.fc31 FTBFS: Can't resolve method "done_cb" overloading "&{}" in package "CPS::Future"
https://bugzilla.redhat.com/show_bug.cgi?id=1711815
Bug ID: 1711815
Summary: perl-CPS-0.18-14.fc31 FTBFS: Can't resolve method
"done_cb" overloading "&{}" in package "CPS::Future"
Product: Fedora
Version: rawhide
URL: https://apps.fedoraproject.org/koschei/build/6459116
Status: NEW
Component: perl-CPS
Assignee: jples...@redhat.com
Reporter: ppi...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
Target Milestone: ---
External Bug ID: CPAN 129470
Classification: Fedora
perl-CPS-0.18-14.fc31 fails to build in F31 because a test fails:
t/43kunfold.t ok
BUILDSTDERR: Can't resolve method "done_cb" overloading "&{}" in package
"CPS::Future" at /usr/share/perl5/vendor_perl/Future.pm line 918.
BUILDSTDERR: # Looks like your test exited with 255 before it could output
anything.
t/50future.t .
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 1/1 subtests
A difference between passing and failing build root is at
.
This is triggered by upgrading perl-Future from 0.39-2.fc30 to 0.40-1.fc31.
--
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711558] perl-Test2-Suite-0.000122 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711558 Petr Pisar changed: What|Removed |Added Status|ASSIGNED|MODIFIED Fixed In Version||perl-Test2-Suite-0.000122-1 ||.fc31 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for Fedora ≥ 30. -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711558] perl-Test2-Suite-0.000122 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711558 --- Comment #2 from Fedora Update System --- perl-Test2-Suite-0.000122-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c9cece528f -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Action needed: Recythonize the sources of your packages
On 20. 05. 19 14:47, Michael J Gruber wrote: Hi there I have rebuilt https://apps.fedoraproject.org/packages/portmidi Here's is another thing that needs to be changed in portmidi for Python 3.8: https://src.fedoraproject.org/rpms/portmidi/pull-request/2 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
[Bug 1712142] New: perl-PAR-1.016 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1712142 Bug ID: 1712142 Summary: perl-PAR-1.016 is available Product: Fedora Version: rawhide Status: NEW Component: perl-PAR Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: anon.am...@gmail.com, jples...@redhat.com, mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 1.016 Current version/release in rawhide: 1.015-8.fc30 URL: http://search.cpan.org/dist/PAR/ 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/3188/ -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[389-devel] please review: PR 50395 - maxlogsperdir accepting negative values
https://pagure.io/389-ds-base/pull-request/50395 ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
[389-devel] 389 DS nightly 2019-05-21 - 94% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2019/05/21/report-389-ds-base-1.4.1.2-20190520git0935b8a.fc29.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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing:
Age URL
279 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d
condor-8.6.11-1.el7
87 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2
tor-0.3.5.8-1.el7
55 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294
cinnamon-3.6.7-5.el7
47 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd
afflib-3.7.18-2.el7
21 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80
python-gnupg-0.4.4-1.el7
19 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b
bubblewrap-0.3.3-2.el7
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-04c7455f6a
singularity-3.1.1-1.1.el7
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d44655ca3
mediaconch-18.03.2-7.el7 libmediainfo-19.04-1.el7 mediainfo-19.04-1.el7
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1605b73a09
drupal7-7.67-1.el7
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d96aef0d8f
rust-1.34.2-1.el7
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-87fa8d93b6
drupal7-entity-1.9-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
lua-mmdb-0.2-1.el7
python-rosdep-0.15.2-1.el7
python-vpoller-0.7.3-3.el7
quantum-espresso-6.4.1-1.el7
stlink-1.5.1-0.3.20190513gitd040db5.el7
Details about builds:
lua-mmdb-0.2-1.el7 (FEDORA-EPEL-2019-3ddfd50f73)
MaxMind database parser for Lua
Update Information:
Initial lua-mmdb package
python-rosdep-0.15.2-1.el7 (FEDORA-EPEL-2019-0e1f0065b9)
ROS System Dependency Installer
Update Information:
Update to latest upstream release
ChangeLog:
* Sat May 18 2019 Scott K Logan - 0.15.2-1
- Update to 0.15.2 (rhbz#1711473)
- Handle automatic dependency generation (f30+)
- Switch to Python 3 sphinx
References:
[ 1 ] Bug #1711473 - python-rosdep-0.15.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711473
python-vpoller-0.7.3-3.el7 (FEDORA-EPEL-2019-e7b909634e)
Distributed vSphere API Proxy
Update Information:
intial package, rhbz#1669793 This new package needs the following additional
updates as dependencies: https://bodhi.fedoraproject.org/updates/FEDORA-
EPEL-2019-f8c7028b60 https://bodhi.fedoraproject.org/updates/FEDORA-
EPEL-2019-c0e21e7e78
References:
[ 1 ] Bug #1669793 - Review Request: python-vpoller - Distributed vSphere API
Proxy
https://bugzilla.redhat.com/show_bug.cgi?id=1669793
quantum-espresso-6.4.1-1.el7 (FEDORA-EPEL-2019-ccc54d0bdb)
A suite for electronic-structure calculations and materials modeling
Update Information:
new upstream release
ChangeLog:
* Fri May 17 2019 Marcin Dulak - 6.4.1-1
- new upstream release
- kill hanging tests after timeout
- disable failed architectures: configure fails to find openblas, fftw on other
%{openblas_arches} than x86_64 %{ix86}
* Thu Feb 14 2019 Orion Poplawski - 5.4.0-20
- Rebuild for openmpi 3.1.3
* Sat Feb 2 2019 Fedora Release Engineering -
5.4.0-19
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Sat Jul 14 2018 Fedora Release Engineering -
5.4.0-18
- Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
* Wed May 2 2018 Iryna Shcherbina - 5.4.0-17
- Update Python 2 dependency declarations to new packaging standards
(See https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3)
* Wed Mar 7 2018 Adam Williamson - 5.4.0-16
- Rebuild to fix GCC 8 mis-compilation
See https://da.gd/YJVwk ("GCC 8 ABI change on x86_64")
* Fri Feb 9 2018 Fedora Release Engineering -
5.4.0-15
- Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
* Thu Aug 3 2017 Fedora Release Engineering
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #10 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5f45944bf -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5f45944bf -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711558] perl-Test2-Suite-0.000122 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711558 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- perl-Test2-Suite-0.000122-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c9cece528f -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1711460] perl-CPAN-Perl-Releases-4.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1711460 --- Comment #5 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc28 has been pushed to the Fedora 28 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-aff62cdb11 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708964] perl-CPAN-Perl-Releases-4.00 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708964 --- Comment #11 from Fedora Update System --- perl-CPAN-Perl-Releases-4.02-1.fc28 has been pushed to the Fedora 28 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-aff62cdb11 -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708462] perl-Net-DAVTalk-0.16 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708462 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Net-DAVTalk-0.16-1.fc3 |perl-Net-DAVTalk-0.16-1.fc3 |1 |1 ||perl-Net-DAVTalk-0.16-1.fc3 ||0 Resolution|--- |ERRATA Last Closed||2019-05-21 01:09:05 --- Comment #8 from Fedora Update System --- perl-Net-DAVTalk-0.16-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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708462] perl-Net-DAVTalk-0.16 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708462 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Net-DAVTalk-0.16-1.fc3 |perl-Net-DAVTalk-0.16-1.fc3 |1 |1 |perl-Net-DAVTalk-0.16-1.fc3 |perl-Net-DAVTalk-0.16-1.fc3 |0 |0 ||perl-Net-DAVTalk-0.16-1.fc2 ||8 --- Comment #9 from Fedora Update System --- perl-Net-DAVTalk-0.16-1.fc28 has been pushed to the Fedora 28 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1708462] perl-Net-DAVTalk-0.16 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1708462 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Net-DAVTalk-0.16-1.fc3 |perl-Net-DAVTalk-0.16-1.fc3 |1 |1 |perl-Net-DAVTalk-0.16-1.fc3 |perl-Net-DAVTalk-0.16-1.fc3 |0 |0 |perl-Net-DAVTalk-0.16-1.fc2 |perl-Net-DAVTalk-0.16-1.fc2 |8 |8 ||perl-Net-DAVTalk-0.16-1.fc2 ||9 --- Comment #10 from Fedora Update System --- perl-Net-DAVTalk-0.16-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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Re: Action needed: Recythonize the sources of your packages
On Mon, 20 May 2019, Miro Hrončok wrote: Hello packagers. During the rebuilds for Python 3.8, we have found out that your package most likely has precythonized C sources. There was an update to Cython and the C sources needs to be regenerated. In line with Fedora packaging policies and guidelines, this should be done anyway. What needs to be done: 1. BR python3-Cython 2. figure out what C sources come from Cython sources look for: /* Generated by Cython */ on the top of them often, all .c files are generated from Cython sources, but not always 3. in %prep, delete those files If you build for Python 2 and Python 3, I recommend to only BR python3-Cython and not python2-Cython, run %py3_build before %py2_build (Cython produces the same sources on both Python versions). Some setup.py files have custom detection whether Cython needs to be run, if the above doesn't work alone, examine setup.py and search for "cython". When you do this, reply to this thread, so we know we should rebuild your package for 3.8 in https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ swt2c python-PyMuPDF Actually, for python-PyMuPDF, it's worse. PyMuPDF is a python binding for mupdf, a C library. Unfortunately, mupdf insists on not maintaining a stable API and will not provide shared libraries. Thus, the current problem is that mupdf has been updated in Rawhide to 1.15, but upstream PyMuPDF hasn't updated to the new API yet. So, PyMuPDF FTBFS because of that. :( Scott___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
[Bug 1712216] New: perl-Starman-0.4015 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1712216 Bug ID: 1712216 Summary: perl-Starman-0.4015 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Starman Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.4015 Current version/release in rawhide: 0.4014-12.fc30 URL: http://search.cpan.org/dist/Starman/ 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/6581/ -- 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
