License tag of rpms/base64coder was changed
from: "EPL or LGPLv2+ or GPLv2+ or ASL 2.0 or BSD"
to: "EPL-1.0 or EPL-2.0 or LGPLv2+ or GPLv2+ or ASL 2.0 or BSD"
--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
Epylog is a python27 program and I have not had the time to convert it
to python3 and won't until later this fall. As I don't want this to be
a FTBFS during rebuilds.. I see the following:
1. Retire it in rawhide
2. Make it a python27 module?
I am looking for advise on which people would recommend.
Thank you
--
Stephen J Smoogen.
2018-06-28 20:41 GMT+02:00 Miro Hrončok <mhroncok(a)redhat.com>:
> This is a reminder that your package FTBFS with Python 3.7. Please fix it.
> We'd like to merge the side tag soon and your package will likely get broken
> deps afterwards. Chances are your package blocks others.
>
> If nothing depends on your package and upstream is dead, consider removing
> it.
>
> Rebuild your package with: fedpkg build --target=f29-python
>
> The list:
> Maintainers by package:
<snip>
> python-seqdiag dridi
<snip>
>
> Packages by maintainer:
<snip>
> dridi python-seqdiag
<snip>
I sent a trivial patch upstream [1] and adapted it for the release
currently packaged in Fedora but then I ran into a different failure
(reported upstream [2]) that will require more thinking.
I think it's safe to assume that the python-{act,block,nw,seq}diag
packages are currently used as leaf packages though, but please yell
at me if I break things further downstream because I'm not sure to get
this fixed before 3.7 lands in Rawhide.
Dridi
[1] https://github.com/blockdiag/seqdiag/pull/24
[2] https://github.com/blockdiag/blockdiag/issues/93
I somehow wound up owning python-sphinx_rtd_theme, I think probably because
I was the first person to attempt to do a build that needed it. :-)
Anyhow, I am not at all sure that I am competent to be the maintainer. I
need some advice. There is a new upstream version available, 0.4.0. I am
looking at it right now, and my attempts at unbundling fonts from this
package seem to be unraveling.
Three font families are bundled: fontawesome, Roboto Slab, and Lato. We
have all 3 of these in Fedora, but the problem is that this package wants
the web versions of these fonts, too. We have fontawesome-fonts-web, but
we do not have .eot, .woff, or .woff2 files available for the other 2
fonts, so far as I am able to determine. Since the .ttf files of those
fonts are not byte-equivalent to the ones we ship ... I'm not sure what is
safe to do here. I am not any kind of font expert.
The upstream tarball is here:
https://files.pythonhosted.org/packages/source/s/sphinx_rtd_theme/sphinx_rt….
Any advice on how to deal with those fonts is most welcome. Any offers
from someone more competent than me to maintain this package would be
gratefully received.
Regards,
--
Jerry James
http://www.jamezone.org/
# Fedora Quality Assurance Meeting
# Date: 2018-07-02
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet for a few weeks, so let's get together tomorrow. Fedora
29 development is getting to an interesting phase, and we can check in
on test days too.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 29 status (DNF 3, Python 3.7...)
3. Test Day / Onboarding status
4. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
_______________________________________________
test-announce mailing list -- test-announce(a)lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave(a)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/test-announce@lists.fedorapro…