devel-announce October 2019

devel-announce@lists.fedoraproject.org

7 participants
25 discussions

Fedora 31 Elections: Nomination period open
by Ben Cotton 13 Nov '19

13 Nov '19

Today we are starting the Nomination & Campaign period during which we accept nominations to the "steering bodies" of the following teams: * FESCo (Engineering) (5 seats) [1] * Fedora Council (1 seat) [2] * Mindshare (1 seat) [3] This period is open until 2019-11-13 at 23:59:59 UTC. Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name. The steering bodies are currently selecting interview questions for the candidates. Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period. Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2019-11-20) will be disqualified and removed from the election. As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list. The full schedule of the elections is available on the Elections schedule[4]. For more information about the elections process, see the program management docs[5]. [1] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations [2] https://fedoraproject.org/wiki/Council/Nominations [3] https://fedoraproject.org/wiki/Mindshare/Nominations [4] https://fedorapeople.org/groups/schedule/f-31/f-31-elections.html [5] https://docs.fedoraproject.org/en-US/program_management/elections/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 2

Fedora 29 EOL on 2019-11-26
by Ben Cotton 31 Oct '19

31 Oct '19

With the release of Fedora 31 earlier this week, Fedora 29 will reach end-of-life on 26 November 2019. At that time, all open Bugzilla bugs will be closed and no more package updates will be published. If an open bug applies to Fedora 30, 31, or rawhide, please update the version field in Bugzilla in order to prevent it from being automatically closed on the EOL date. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Reminder: DevConf.CZ CfP open through 1 November
by Ben Cotton 31 Oct '19

31 Oct '19

You may have seen this posted in a few places, but the DevConf.CZ Call for Proposals is open. As in years past, there is a dedicated Fedora track in addition to tracks on Community, IoT, cloud/containers, microservices, networking, desktop, and more. DevConf.CZ is 24–26 Jaunary 2020 in Brno, CZ. Open TestCon's (30–31 March, 2020 in Beijing, CN) CfP is also open through 31 October. You can see more information about both conferences and links to proposal submissions on the Community Blog post: https://communityblog.fedoraproject.org/devconf-cz-and-open-testcon-cfps-op… -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 1

Fedora 32 System-Wide Change proposal: iptables-nft-default
by Ben Cotton 30 Oct '19

30 Oct '19

https://fedoraproject.org/wiki/Changes/iptables-nft-default == Summary == Make iptables-nft the preferred iptables variant. == Owner == * Name: [[User:psutter| Phil Sutter]] * Email: psutter(a)redhat.com == Detailed Description == <code>iptables-nft</code> package provides alternative implementations of iptables, ip6tables, ebtables and arptables and associated save and restore commands. These use nftables internally while providing the same look'n'feel as the original tools. Users may choose between both implementations using <code>alternatives</code> tool. Upstream considers the traditional implementations legacy and therefore renamed the binaries adding '-legacy' suffix. In Fedora, same has been done to <code>arptables</code> and <code>ebtables</code> packages, namely renaming them to <code>arptables-legacy</code> and <code>ebtables-legacy</code>. Legacy <code>iptables</code> and <code>ip6tables</code> remain in <code>iptables</code> package, which in fact is the only one other packages depend upon. To change the status quo, two measures are planned: === Raise priority of nft-variants in <code>alternatives</code> === Currently, legacy variants are installed with priority 10 and nft variants with priority 5. This must be changed as otherwise installing <code>iptables-legacy</code> in a system with <code>iptables-nft</code> installed would change the active alternative (since they are in automatic mode by default). On the other hand, existing systems using legacy variants should not be changed by a system update. Therefore nft variants' priorities should be chosen to match legacy ones. === Rename <code>iptables</code> package === New name should be <code>iptables-legacy</code> which aligns with ebtables and arptables and reflects upstream status. To resolve dependencies, <code>Provides: iptables</code> statement will be added to <code>iptables-nft</code> package. This should automatically change the default variant to nft. == Benefit to Fedora == * RHEL8 ships nft-variants exclusively, make Fedora align with that by default while still providing the option to fall back to legacy tools. * New features and improvements are likely to hit nft-variants due to the possibility nftables backend allows for. Although at this point some legacy features (e.g. ebtables among match) are still missing, others are already there (like, e.g. xtables-monitor tool) or are being upstreamed right now (improved tool performance when dealing with large rulesets). == Scope == * Proposal owners: Changes are rather simple: Rename <code>iptables</code> package, add <code>Provides:</code> line to <code>iptables-nft</code> package, change priorities used when calling <code>alternatives</code>. * Other developers: N/A The changed tools may cause regressions among packages using them and it affects only new installations (or those manually switched over). So while no explicit effort is required from them, they should be made aware of the change so they take a possible regression in iptables into account, quickly test against legacy variant and file a ticket (or complain to the right person) if that fixes the problem. * Release engineering: [https://pagure.io/releng/issue/8934 #8934] * Policies and guidelines: No change required * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Due to the package rename and <code>Provides:</code> line, upgrades will pull in <code>iptables-nft</code> package. But due to the equal alternatives priorities, existing choices won't be changed and so existing installations shouldn't be harmed (apart from forced installation of <code>iptables-nft</code> package). Sadly, there are a few known issues, like e.g. missing support for ebtables broute table or among match and a few iptables targets/matches. Users depending on such features are advised to install <code>iptables-legacy</code> package and switch variants using <code>alternatives</code>. == How To Test == Any users of iptables/ebtables/arptables should switch to nft-variants using alternatives tool (if necessary) and check that everything works as before. Any issues should be reported despite the known compatibility issues described above since knowledge about who uses the missing features is valuable information for both up- and downstream. == User Experience == Ideally look'n'feel shouldn't change. Since iptables-nft does not need a lock file anymore, no problems with stale xtables-lock or parallel iptables calls in different mount namespaces are expected anymore. Given the changes currently being upstreamed, users dealing with large rulesets should see a performance increase when manipulating the ruleset (lower run-times of iptables or iptables-restore, packet processing speed should not really change). == Dependencies == Other packages depending on iptables: * NFStest * clatd * ctdb * fail2ban-server * firewalld * fwsnort * iptstate * libvirt-daemon-driver-network * libvirt-daemon-driver-nwfilter * moby-engine * nfacct * origin * podman * psad * python3-ipatests * ravada * rkt * shorewall * shorewall-init * shorewall-lite * shorewall6 * shorewall6-lite * sshuttle * sslsplit * ufw Since nft-variants are supposed to be drop-in replacements, no outside contribution is needed in order to perform this change. == Contingency Plan == * Contingency mechanism: Nothing needs to be done, the change should be atomic. * Contingency deadline: N/A * Blocks release? No == Documentation == * https://wiki.nftables.org/wiki-nftables/index.php/Legacy_xtables_tools * Man pages: ** [http://man7.org/linux/man-pages/man8/xtables-nft.8.html xtables-nft.8] ** [http://man7.org/linux/man-pages/man8/xtables-legacy.8.html xtables-legacy.8] ** [http://man7.org/linux/man-pages/man8/xtables-monitor.8.html xtables-monitor.8] -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Fedora 32 System-Wide Change proposal: Translation platform migration to Weblate
by Ben Cotton 30 Oct '19

30 Oct '19

https://fedoraproject.org/wiki/Changes/Translation_platform_migration_to_We… = Translation platform migration to Weblate = == Summary == This migration was decided at Flock 2019 in Budapest, it is mandatory as development and maintenance of Zanata — the previous translation platform — ceased in 2018. More information are available here: https://communityblog.fedoraproject.org/fedora-localization-platform-migrat… Link to release process is to make sure the information is spread across all dependent projects, including Documentation and Websites. == Owner ==  * Owner: the [[L10N]] group (#fedora-i18n on freenode) * Primary contact: [[User:jibecfed|Jean-Baptiste Holcroft]] * Email: [https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/ localization mailing list] == Detailed Description == Make sure all existing Zanata project have been informed (upstream ticket created) and that all priority packages have migrated. We created a template for [[L10N_Move_to_Weblate/Message_for_upstream_project]]. The [https://fedora.zanata.org/version-group/view/PriorityPackages list of priority packages is defined in Zanata], it contains websites, anaconda, dnf and many others... == Benefit to Fedora == First objective is to lower the risk of having no translation platform if Zanata crashes. Second objective is to provide a suited tool for localization community to be part of our processes again: * be closer to upstream activity by directly interacting with git repositories ** this also lower upstream requirements to interact with our translation platform (no dependencies required as it interact with git repos) ** this helps upstream to see localization contributions ** this allows translator to get notification when new strings * be able to localize our documentation (we decided to make it compatible with Weblate directly) * the tool will [https://pagure.io/fedora-infrastructure/issue/8291 publish on Fedora messaging] ** allows community statistics ** allows badges creation == Scope == * Proposal owners: Open a ticket for each upstream project. * Other developers: answer the message for upstream project and eventually create appropriate git repositories: {{admon/important | Questions to answer by upstream |{{:L10N_Move_to_Weblate/Message_for_upstream_project}}}} * Release engineering: [https://pagure.io/releng/issue/8947 #8947] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == N/A (this change impacts our processes, not our deliverable) == How To Test == For projects using the translation platform: make sure translation commits are part of the release included in Fedora 32. Example for DNF: * Open the DNF git repository * Find folder containing localization file (usually the '''po''' folder) * Look at commit history and search for, commits will start with: "Translated using Weblate" ([https://github.com/mike-fabian/ibus-typing-booster/pull/57/commits/3ffccedc… example with French language on ibus typing booster] == User Experience == No impact. == Dependencies == N/A (not a System Wide Change) == Contingency Plan == * Contingency mechanism: Localization team will keep using Zanata * Blocks release? Yes, if websites and priority packages do not use the new translation platform. * Blocks product? Yes == Documentation == [[L10N Move to Weblate]] -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Fedora 32 System-Wide Change proposal: Annobin Used By Bodhi
by Ben Cotton 30 Oct '19

30 Oct '19

https://fedoraproject.org/wiki/Changes/ANNOBIN-used-by-bodhi = Annobin Used By Bodhi = == Summary == Use the annocheck program from the annobin package to produce an analysis of the security hardening of a compiled package when reviewing a Bodhi update. == Owner == * Name: Nick Clifton [https://fedoraproject.org/wiki/User:Nickc] * Email: nickc(a)redhat.com == Detailed Description == The annobin package provides two components, a plugin for gcc that records details about how a program was compiled and an analyser that uses this information to produce a report on the security hardening status of the compiled program. Currently the plugin is being used as part of the build process for Fedora packages (when they are built using gcc), but the analysing program is not being run. This proposal is to have the analyser (called annocheck) run when creating information for review by the Bodhi update process, possibly allowing an update to be delayed until the security issues are addressed. The analyser currently looks for the following items: * Lazy binding must not have been enabled via the linker option "-z lazy". Instead the @option{-z now} option must have been used. * The program must not have a stack in an executable region of memory. * The relocations for the GOT table must be read only. * No program segment should have all three of the read, write and execute permission bits set. * There should be no relocations against executable code. * The runpath information used to locate shared libraries at runtime must only include directories rooted at /usr. * The program must have been compiled with the -fstack-protector-strong option enabled, and with -D_FORTIFY_SOURCE=2 specified. It must also have been compiled at at least optimisation level 2. * Dynamic executables must have a dynamic segment. * Shared libraries must have been compiled with -fPIC or-fPIE but not -static. * Dynamic executables must have been compiled with -fPIE and linked with -pie. * Program which use exception handling must have been compiled with -fexceptions enabled and with -D_GLIBCXX_ASSERTIONS specified. * If available the -fstack-clash-protection must have been used. * If available the -fcf-protection=full must have been used. * For i686 binaries, the -mstackrealign option must have been specified. * The program must have been compiled with the -D_FORTIFY_SOURCE=2 command line option specified. * The program must have been compiled with at least -O2 optimisation enabled. * The program must not have any relocations that are held in a writable section. * For x86_64 binaries, check that -fcf-protection has been enabled. Note - I do not know *how* to add a run of the annocheck program to the Bodhi process. This change request is about asking that such a thing be added. == Benefit to Fedora == Establishing good security practices when building packages will help Fedora remain a front running Linux distribution. By providing a way to review the security hardening status of packages, this update will help to ensure that these practices continue. Note - the intention is that if this change is successful, and useful, then a future change request would be made to include the security checking as part of the actual package build process, and to have packages fail to complete building if they do not pass the security checks. == Scope == * Proposal owners: In theory there is very little that I can do personally. I do not have the knowledge to change the Bodhi process myself, so I will have to rely upon someone else to do that. I am familiar with the annobin package however, so any changes that are needed to it I will be happy to make. * Other developers: Add an invocation of the annocheck program to the Bodhi build approval process and make its output available to reviewers. Annocheck can be invoked simply as "annocheck <filename>" although there are a set of command line options to extend and modify its behaviour. Annocheck understands the rpm file format, as well as shared and static libraries and executable binaries. It can also be helpful to provide annocheck with access to the debug information for a binary or rpm, if that has been placed into a separate file. * Release engineering: https://pagure.io/fedora-ci/general/issue/78 No mass rebuild is required. * Policies and guidelines: It is desirable that the packaging guidelines be updated to describe the security hardening features examined by annocheck. (If they are not already mentioned in the guidelines). * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == This change should have no effect on upgrading Fedora, nor should it introduce any compatibility problems. == How To Test == Submit a package for Bodhi review and see if the annocheck data is added to the page. No special hardware is needed for this test, but it might involve the use of a dummy package or a dummy instance of Bodhi in order to test the behaviour before going live. == User Experience == This change should not be noticeable by users. == Dependencies == No packages depend upon this change. This change does depend upon the annobin package. == Contingency Plan == Back out any changes made to Bodhi. * Blocks release? No releases are blocked by this change. * Blocks product? No products are blocked by this change. == Documentation == The watermark specification explains the technology underlying annobin: https://fedoraproject.org/wiki/Toolchain/Watermark#Proposed_Specification_f… The annobin package includes its own documentation. On a system where it is installed invoking "info annobin" should produce a searchable information structure. == Release Notes == An update to the Fedora Release Notes should not be needed. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

List of Python 2 packages to be removed mid-November
by Miro Hrončok 29 Oct '19

29 Oct '19

Dear maintainers, here is a list of packages that (transitively, at build or run time) require Python 2 and have not yet got a FESCo exception to do so. If you were bcced on this e-mail, it affects one or more of your packages. The default action will be to remove such packages mid-November. If this took you by surprise, don't panic. It's possible to change the default. Let us know and we'll work things out. The mid-November deadline is not for removing *all* of Python 2, but for getting exceptions. If you are already working to port to Python 3, sorry for the spam! But, time is running out. Consider getting an exception so the package isn't removed in November. Or remove the package (if nothing depends on it) and re-introduce it when it's ported. (We'll be happy to help, with reviews or otherwise.) If you want to remove the Python 2 package, but you're waiting for something that depends on it, please make sure you know what the maintainer(s) of the dependent package are planning to do. (Hopefully you have fewer dependents than "python27" or "python2-setuptools", and your questions can be more targeted than this e-mail.) If you want to continue using Python 2, please let us know ASAP. We can guide you through filing the FESCo exception. If you talked to us (on e-mail or Bugzilla) and think your package is fine as it is, but you don't have a FESCo exception, then there was a misunderstanding. We're sorry for our side of it. Please get a FESCo exception for your package. Note: Packages that BuildRequire python27, and have no other Python 2 dependencies, have a blanket exception for Fedora 32: https://pagure.io/fesco/issue/2250 They aren't listed below. Also note: Orphaned Python 2 packages also aren't listed below, but will be removed unless someone adopts them and gets an exception. ## Why the FESCo exception? It's a bit of process meant to ensure all the relevant people know that a package *and its dependencies* will stay in Fedora, despite using an (upstream-)unmaintained interpreter. With hundreds of packages, all different, we unfortunately do need a bit of bureaucracy. Due to the volume, the Python 2 removal will be *automated*, so if you have an "obvious exception", it's still important to let *humans* know, so they can adapt their automation. ## Why now? The current maintainers of python27 don't want to maintain it forever, without upstream support. But we also don't want to just drop it and let everything burn, hence all this fuss. The policy and messaging around deprecating and removing Python 2 has been getting stronger and stronger ever since the Python 3.0 release in 2008. If you still need more time, please let us know. ## What exactly is happening? The formal change proposal is here: https://fedoraproject.org/wiki/Changes/RetirePython2 Packages requiring Python 2 will be removed starting November 15 (unless they have an exception). Components with all essential subpackages removed will be retired. The removal will be (semi-)automated. Source package only BuildRequiring removed packages will fail to build, and will be removed according to the regular FTBFS policy. https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails… ## The list Here is the package breakdown sorted by maintainers. The list contains the shortest dependency path to Python 2. The arrow means "depends on". The data is based on the latest rawhide compose, so it might be a bit out of date. If you find a bogus dependency, such as a dependency that can be resolved in a non-Python 2 way, please let us know, so we can blacklist it. aarem pdf-stapler (→ PY2) python2-staplelib (→ PY2) python-PyPDF2 python2-PyPDF2 (→ PY2) python2-more-itertools (→ PY2) abbot protobuf python2-protobuf (→ PY2) abompard python-coverage python2-coverage (→ PY2) python-httplib2 python2-httplib2 (→ PY2) python-mako python2-mako (→ PY2) python-pysocks python2-pysocks (→ PY2) python-urllib3 python2-urllib3 (→ PY2) python-zope-event python2-zope-event (→ PY2) ajmitchell NFStest (→ PY2) alexl dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) alexlan graphviz graphviz-python2 (→ PY2) alsadi dumb-init (BuildRequires: python2-mock → PY2) amigadave dbus (BuildRequires: python2-gobject → PY2) amluto python-musicbrainzngs python2-musicbrainzngs (→ PY2) andreamanzi dynafed (→ PY2) dynafed-dmlite-frontend (→ dynafed → PY2) dynafed-dmlite-plugin (→ dynafed → PY2) dynafed-http-plugin (→ dynafed → PY2) dynafed-lfc-plugin (→ dynafed → PY2) dynafed-private-devel (→ dynafed → PY2) dynafed-tpc-gfal2 (→ dynafed → PY2) anishpatil gnome-transliteration (→ python2-gobject → PY2) ankursinha python-tasklib (BuildRequires: python2-pytz → PY2) anyremote ganyremote (→ pybluez → PY2) kanyremote (→ pybluez → PY2) aperezbios sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) telepathy-salut (BuildRequires: python2-dbus → PY2) apevec pyparsing python2-pyparsing (→ PY2) python-distutils-extra python2-distutils-extra (→ PY2) python-netifaces python2-netifaces (→ PY2) python-pbr python2-pbr (→ PY2) python-prettytable python2-prettytable (→ PY2) python-six python2-six (→ PY2) aruiz fleet-commander-client (→ python2-gobject → PY2) ausil uboot-tools (BuildRequires: python2-setuptools → PY2) averi trac-batchmodify-plugin (→ PY2) trac-navadd-plugin (→ PY2) trac-themeengine-plugin (→ PY2) trac-tocmacro-plugin (→ PY2) trac-vatar-plugin (→ PY2) trac-workflowadmin-plugin (→ PY2) aviso python-configparser python2-configparser (→ PY2) python-dns python2-dns (→ PY2) python-scandir python2-scandir (→ PY2) awjb fbdesk (→ fluxbox → PY2) libopensync-plugin-moto (→ pybluez → PY2) python-httplib2 python2-httplib2 (→ PY2) beckerde miniupnpc python2-miniupnpc (→ PY2) besser82 dbus-python python2-dbus (→ PY2) xed (BuildRequires: python2-gobject-base → PY2) bkabrda python-six python2-six (→ PY2) bkearney sugar-moon (→ PY2) sugar-turtleart (→ PY2) bowlofeggs python-mako python2-mako (→ PY2) python-nose python2-nose (→ PY2) python-pycodestyle python2-pycodestyle (→ PY2) python-simplejson python2-simplejson (→ PY2) python-sqlalchemy python2-sqlalchemy (→ PY2) rocket-depot (→ PY2) bpepple python-telepathy python2-telepathy (→ PY2) telepathy-idle (BuildRequires: python2-dbus → PY2) telepathy-mission-control (BuildRequires: python2-dbus → PY2) telepathy-rakia (BuildRequires: python2-dbus → PY2) bressers gqrx (→ gnuradio → PY2) bronhaim ioprocess python2-ioprocess (→ PY2) brouhaha gr-iio (→ gnuradio → PY2) gr-iio-devel (→ gnuradio-devel → gnuradio → PY2) python-attrs python2-attrs (→ PY2) python-enum34 python2-enum34 (→ PY2) bruno qgis (BuildRequires: python2-sip-devel → PY2) bsjones frescobaldi (→ lilypond → PY2) lilv (BuildRequires: python2-numpy → PY2) python-poppler-qt4 (BuildRequires: PyQt4-devel → python2-sip-devel → PY2) caillon dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) callkalpa sugar-abacus (→ PY2) sugar-browse (→ PY2) sugar-calculator (→ PY2) sugar-castle (→ PY2) sugar-chat (→ PY2) sugar-clock (→ PY2) sugar-colordeducto (→ PY2) sugar-connect (→ PY2) sugar-countries (→ PY2) sugar-distance (→ PY2) sugar-finance (→ PY2) sugar-flip (→ sugar → PY2) sugar-flipsticks (→ PY2) sugar-fototoon (→ PY2) sugar-fractionbounce (→ PY2) sugar-getiabooks (→ PY2) sugar-hello-world (→ PY2) sugar-imageviewer (→ PY2) sugar-implode (→ PY2) sugar-infoslicer (→ PY2) sugar-jukebox (→ PY2) sugar-kuku (→ PY2) sugar-labyrinth (→ PY2) sugar-locosugar (→ PY2) sugar-log (→ PY2) sugar-maze (→ PY2) sugar-measure (→ PY2) sugar-memorize (→ PY2) sugar-nutrition (→ PY2) sugar-paint (→ PY2) sugar-physics (→ PY2) sugar-pippy (→ PY2) sugar-playgo (→ PY2) sugar-portfolio (→ PY2) sugar-pukllanapac (→ PY2) sugar-read (→ PY2) sugar-recall (→ PY2) sugar-record (→ PY2) sugar-ruler (→ PY2) sugar-speak (→ PY2) sugar-srilanka (→ PY2) sugar-starchart (→ PY2) sugar-stopwatch (→ PY2) sugar-terminal (→ PY2) sugar-typing-turtle (→ PY2) sugar-view-slides (→ PY2) sugar-visualmatch (→ PY2) sugar-words (→ PY2) sugar-write (→ PY2) sugar-xoeditor (→ PY2) sugar-xoirc (→ PY2) sugar-xomail (→ PY2) sugar-yupana (→ PY2) caolanm dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) carlwgeorge python-subprocess32 python2-subprocess32 (→ PY2) chandankumar python2-typing (→ PY2) cheese freeorion (→ PY2) churchyard Cython python2-Cython (→ PY2) python-certifi python2-certifi (→ PY2) python-chardet python2-chardet (→ PY2) python-hypothesis python2-hypothesis (→ PY2) python-markupsafe python2-markupsafe (→ PY2) python-nose python2-nose (→ PY2) python-pygments python2-pygments (→ PY2) python-six python2-six (→ PY2) python2-more-itertools (→ PY2) python2-pluggy (→ PY2) python2-pytest (→ PY2) python2-setuptools (→ PY2) cicku exaile (→ PY2) hg-git (→ PY2) lilypond (→ PY2) offlineimap (→ PY2) python-mutagen python2-mutagen (→ PY2) cjb olpc-switch-desktop (→ PY2) olpc-update (→ PY2) clalance python-prettytable python2-prettytable (→ PY2) corsepiu k3d (→ PY2) k3d-devel (→ k3d → PY2) cottsay gr-osmosdr (→ PY2) gr-osmosdr-devel (→ gr-osmosdr → PY2) gr-osmosdr-doc (→ gr-osmosdr → PY2) cstratak python-pytest-cov python2-pytest-cov (→ PY2) python-setuptools_scm python2-setuptools_scm (→ PY2) scipy python2-scipy (→ PY2) ctria configsnap (→ PY2) cverna python-mako python2-mako (→ PY2) daveisfera qgis (BuildRequires: python2-sip-devel → PY2) trac (→ PY2) trac-mercurial-plugin (→ PY2) daveo gqrx (→ gnuradio → PY2) dcallagh python-formencode python2-formencode (→ PY2) dchen fluxbox (→ PY2) fluxbox-pulseaudio (→ fluxbox → PY2) fluxbox-vim-syntax (→ fluxbox → PY2) python-httplib2 python2-httplib2 (→ PY2) defolos pyxattr python2-pyxattr (→ PY2) deji exaile (→ PY2) mpich python2-mpich (→ PY2) openmpi python2-openmpi (→ PY2) denisarnaud boost boost-mpich-python2 (→ PY2) boost-mpich-python2-devel (→ boost-mpich-python2 → PY2) boost-numpy2 (→ PY2) boost-openmpi-python2 (→ PY2) boost-openmpi-python2-devel (→ boost-openmpi-python2 → PY2) boost-python2 (→ PY2) boost-python2-devel (→ boost-numpy2 → PY2) xapian-bindings python2-xapian (→ PY2) dfateyev backupninja (→ rdiff-backup → PY2) dledford openmpi python2-openmpi (→ PY2) dmalcolm squeal (→ PY2) dmaphy terminator (→ PY2) dodji offlineimap (→ PY2) dougsland ioprocess python2-ioprocess (→ PY2) drago01 xapian-bindings python2-xapian (→ PY2) dsd olpc-switch-desktop (→ PY2) olpc-update (→ PY2) sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-datastore (→ PY2) sugar-toolkit-gtk3 (→ PY2) sugar-toolkit-gtk3-devel (→ sugar-toolkit-gtk3 → PY2) dvratil telepathy-logger-qt (BuildRequires: python2-dbus → PY2) dwrobel dxf2gcode (BuildRequires: python2-qt5-base → PY2) erikos gwebsockets python2-gwebsockets (→ PY2) sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-artwork (BuildRequires: python2-empy → PY2) sugar-base (→ PY2) sugar-browse (→ PY2) sugar-calculator (→ PY2) sugar-chat (→ PY2) sugar-datastore (→ PY2) sugar-imageviewer (→ PY2) sugar-log (→ PY2) sugar-read (→ PY2) sugar-terminal (→ PY2) sugar-toolkit (→ PY2) sugar-toolkit-gtk3 (→ PY2) sugar-toolkit-gtk3-devel (→ sugar-toolkit-gtk3 → PY2) sugar-turtleart (→ PY2) sugar-write (→ PY2) ersin ddiskit (→ PY2) ewalsh termy-qt (BuildRequires: python2-jinja2 → PY2) fab captcp (→ PY2) klavaro (BuildRequires: python2-docutils → PY2) python-astral (BuildRequires: python2-pytz → PY2) python-distutils-extra python2-distutils-extra (→ PY2) python-dulwich python2-dulwich (→ PY2) python-olpcgames python2-olpcgames (→ PY2) scons python2-scons (→ PY2) fale python-decorator python2-decorator (→ PY2) python-lxml python2-lxml (→ PY2) farnz python-gstreamer1 python2-gstreamer1 (→ PY2) fcami scribus (→ PY2) filabrazilska python-scales python2-scales (→ PY2) filiperosset bakefile (→ PY2) python-empy python2-empy (→ PY2) firewing python-crypto python2-crypto (→ PY2) frankcrawford rdiff-backup (→ PY2) safekeep safekeep-client (→ safekeep-common → rdiff-backup → PY2) safekeep-common (→ rdiff-backup → PY2) safekeep-server (→ safekeep-common → rdiff-backup → PY2) fschwarz babel python2-babel (→ PY2) python-genshi python2-genshi (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) shiboken (→ shiboken-python2-libs → PY2) shiboken-python2-devel (→ PY2) shiboken-python2-libs (→ PY2) trac (→ PY2) fujiwara ibus-input-pad (→ input-pad → python2-gobject → PY2) input-pad (→ python2-gobject → PY2) input-pad-devel (→ input-pad → python2-gobject → PY2) gbcox oggify (→ PY2) geertj pyside-tools (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) genodeftest exaile (→ PY2) greghellings python-enum34 python2-enum34 (→ PY2) herczy libuser python2-libuser (→ PY2) herrold abiword python2-abiword (→ PY2) hguemar python-dateutil python2-dateutil (→ PY2) python-funcsigs python2-funcsigs (→ PY2) hhorak PyGreSQL python2-pygresql (→ PY2) hobbes1069 pyside-tools (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) shiboken (→ shiboken-python2-libs → PY2) shiboken-python2-devel (→ PY2) shiboken-python2-libs (→ PY2) huzaifas abiword python2-abiword (→ PY2) ignatenkobrain Cython python2-Cython (→ PY2) libxml2 python2-libxml2 (→ PY2) protobuf python2-protobuf (→ PY2) python-blist python2-blist (→ PY2) python-hypothesis python2-hypothesis (→ PY2) python-iniparse python2-iniparse (→ PY2) python-lxml python2-lxml (→ PY2) python-mako python2-mako (→ PY2) python-mutagen python2-mutagen (→ PY2) python-setuptools_scm python2-setuptools_scm (→ PY2) python-simplejson python2-simplejson (→ PY2) ilianaw python-backports python2-backports (→ PY2) imcleod python-prettytable python2-prettytable (→ PY2) irina qpid-proton python2-qpid-proton (→ PY2) ishcherb python-pydispatcher python2-pydispatcher (→ PY2) itamarjp asterisk (→ PY2) asterisk-ael (→ asterisk → PY2) asterisk-alembic (→ asterisk → PY2) asterisk-alsa (→ asterisk → PY2) asterisk-calendar (→ asterisk → PY2) asterisk-corosync (→ asterisk → PY2) asterisk-curl (→ asterisk → PY2) asterisk-dahdi (→ asterisk → PY2) asterisk-devel (→ asterisk → PY2) asterisk-fax (→ asterisk → PY2) asterisk-festival (→ asterisk → PY2) asterisk-hep (→ asterisk → PY2) asterisk-iax2 (→ asterisk → PY2) asterisk-ices (→ asterisk → PY2) asterisk-ldap (→ asterisk → PY2) asterisk-lua (→ asterisk → PY2) asterisk-mgcp (→ asterisk → PY2) asterisk-minivm (→ asterisk → PY2) asterisk-mobile (→ asterisk → PY2) asterisk-mwi-external (→ asterisk → PY2) asterisk-mysql (→ asterisk → PY2) asterisk-odbc (→ asterisk → PY2) asterisk-ooh323 (→ asterisk → PY2) asterisk-oss (→ asterisk → PY2) asterisk-pjsip (→ asterisk → PY2) asterisk-portaudio (→ asterisk → PY2) asterisk-postgresql (→ asterisk → PY2) asterisk-radius (→ asterisk → PY2) asterisk-sip (→ asterisk → PY2) asterisk-skinny (→ asterisk → PY2) asterisk-snmp (→ asterisk → PY2) asterisk-sqlite (→ asterisk → PY2) asterisk-tds (→ asterisk → PY2) asterisk-unistim (→ asterisk → PY2) asterisk-voicemail (→ asterisk → PY2) asterisk-voicemail-imap (→ asterisk → PY2) asterisk-voicemail-odbc (→ asterisk → PY2) asterisk-voicemail-plain (→ asterisk → PY2) asterisk-sounds-core asterisk-sounds-core-* (→ asterisk → PY2) python-configparser python2-configparser (→ PY2) ivaxer gflags (BuildRequires: python2-setuptools → PY2) ivazquez python-sqlalchemy python2-sqlalchemy (→ PY2) jamatos pyparsing python2-pyparsing (→ PY2) python-configparser python2-configparser (→ PY2) jamielinux docco (→ python2-pygments → PY2) nodejs-snockets (BuildRequires: docco → python2-pygments → PY2) nodejs-watchit (BuildRequires: docco → python2-pygments → PY2) jchaloup kubernetes-ansible (→ python2-netaddr → PY2) kubernetes-ansible-vagrant (→ kubernetes-ansible → python2-netaddr → PY2) jcholast certmonger (BuildRequires: python2-dbus → PY2) python-netaddr python2-netaddr (→ PY2) jcline python-chardet python2-chardet (→ PY2) python-idna python2-idna (→ PY2) python-urllib3 python2-urllib3 (→ PY2) jcpunk xed (BuildRequires: python2-gobject-base → PY2) jdekloe grib_api (BuildRequires: python2-numpy → PY2) hg-git (→ PY2) jdornak mod_wsgi python2-mod_wsgi (→ PY2) python-mysql python2-mysql (→ PY2) jdulaney lilypond (→ PY2) jeckersb PyYAML python2-pyyaml (→ PY2) python-netaddr python2-netaddr (→ PY2) jfilak python-inotify python2-inotify (→ PY2) python2-inotify-examples (→ PY2) jgrulich lokalize (→ python2-dbus → PY2) telepathy-logger-qt (BuildRequires: python2-dbus → PY2) telepathy-qt (BuildRequires: python2-dbus → PY2) jgu python-netifaces python2-netifaces (→ PY2) vtk (BuildRequires: python2-sip-devel → PY2) jhladky openmpi python2-openmpi (→ PY2) jhrozek libuser python2-libuser (→ PY2) python-netaddr python2-netaddr (→ PY2) jkaluza mod_wsgi python2-mod_wsgi (→ PY2) jmlich PyGreSQL python2-pygresql (→ PY2) jmontleon python-certifi python2-certifi (→ PY2) johnp dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) pygobject3 python2-gobject (→ PY2) python2-gobject-base (→ PY2) python2-gobject-devel (→ python2-gobject → PY2) sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-datastore (→ PY2) telepathy-salut (BuildRequires: python2-dbus → PY2) jorton mod_wsgi python2-mod_wsgi (→ PY2) jpopelka python-utmp python2-utmp (→ PY2) jraber gourmet (→ PY2) jreznik kig (→ PY2) pyside-tools (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) shiboken (→ shiboken-python2-libs → PY2) shiboken-python2-devel (→ PY2) shiboken-python2-libs (→ PY2) telepathy-logger-qt (BuildRequires: python2-dbus → PY2) telepathy-qt (BuildRequires: python2-dbus → PY2) jridky asciidoc asciidoc-music (→ lilypond → PY2) jskarvad gnuradio (→ PY2) gnuradio-devel (→ gnuradio → PY2) gnuradio-doc (→ gnuradio → PY2) gnuradio-examples (→ PY2) gqrx (→ gnuradio → PY2) gr-air-modes (→ PY2) gr-air-modes-devel (→ gr-air-modes → PY2) gr-air-modes-doc (→ gr-air-modes → PY2) gr-fcdproplus (→ PY2) gr-fcdproplus-devel (→ gr-fcdproplus → PY2) gr-fcdproplus-doc (→ gr-fcdproplus → PY2) gr-hpsdr (→ PY2) gr-hpsdr-devel (→ gr-hpsdr → PY2) gr-hpsdr-doc (→ gr-hpsdr → PY2) gr-iqbal (→ PY2) gr-iqbal-devel (→ gr-iqbal → PY2) gr-iqbal-doc (→ gr-iqbal → PY2) gr-osmosdr (→ PY2) gr-osmosdr-devel (→ gr-osmosdr → PY2) gr-osmosdr-doc (→ gr-osmosdr → PY2) gr-rds (→ PY2) gr-rds-devel (→ gr-rds → PY2) gr-rds-doc (→ gr-rds → PY2) graphviz graphviz-python2 (→ PY2) pygame pygame-devel (→ python2-pygame → PY2) python2-pygame (→ PY2) python-pyobd python2-pyobd (→ PY2) python-pyrtlsdr python2-pyrtlsdr (→ PY2) python-visvis python2-visvis (→ PY2) quisk (→ PY2) rtlsdr-scanner (→ PY2) rtlsdr-scanner-doc (→ rtlsdr-scanner → PY2) uhd (→ PY2) uhd-devel (→ uhd → PY2) uhd-firmware (→ uhd → PY2) uhd-tools (→ uhd → PY2) urh (→ uhd → PY2) jsmith asterisk (→ PY2) asterisk-ael (→ asterisk → PY2) asterisk-alembic (→ asterisk → PY2) asterisk-alsa (→ asterisk → PY2) asterisk-calendar (→ asterisk → PY2) asterisk-corosync (→ asterisk → PY2) asterisk-curl (→ asterisk → PY2) asterisk-dahdi (→ asterisk → PY2) asterisk-devel (→ asterisk → PY2) asterisk-fax (→ asterisk → PY2) asterisk-festival (→ asterisk → PY2) asterisk-hep (→ asterisk → PY2) asterisk-iax2 (→ asterisk → PY2) asterisk-ices (→ asterisk → PY2) asterisk-ldap (→ asterisk → PY2) asterisk-lua (→ asterisk → PY2) asterisk-mgcp (→ asterisk → PY2) asterisk-minivm (→ asterisk → PY2) asterisk-mobile (→ asterisk → PY2) asterisk-mwi-external (→ asterisk → PY2) asterisk-mysql (→ asterisk → PY2) asterisk-odbc (→ asterisk → PY2) asterisk-ooh323 (→ asterisk → PY2) asterisk-oss (→ asterisk → PY2) asterisk-pjsip (→ asterisk → PY2) asterisk-portaudio (→ asterisk → PY2) asterisk-postgresql (→ asterisk → PY2) asterisk-radius (→ asterisk → PY2) asterisk-sip (→ asterisk → PY2) asterisk-skinny (→ asterisk → PY2) asterisk-snmp (→ asterisk → PY2) asterisk-sqlite (→ asterisk → PY2) asterisk-tds (→ asterisk → PY2) asterisk-unistim (→ asterisk → PY2) asterisk-voicemail (→ asterisk → PY2) asterisk-voicemail-imap (→ asterisk → PY2) asterisk-voicemail-odbc (→ asterisk → PY2) asterisk-voicemail-plain (→ asterisk → PY2) asterisk-sounds-core asterisk-sounds-core-* (→ asterisk → PY2) jspaleta gourmet (→ PY2) python-dateutil python2-dateutil (→ PY2) python-httplib2 python2-httplib2 (→ PY2) python-xlib python2-xlib (→ PY2) safekeep safekeep-client (→ safekeep-common → rdiff-backup → PY2) safekeep-common (→ rdiff-backup → PY2) safekeep-server (→ safekeep-common → rdiff-backup → PY2) scipy python2-scipy (→ PY2) jstanley trac-customfieldadmin-plugin (→ PY2) trac-privateticketsplugin (→ PY2) trac-watchlist-plugin (→ PY2) jsynacek python-pycurl python2-pycurl (→ PY2) jujens ccnet (→ PY2) ccnet-devel (→ ccnet → PY2) libsearpc (→ PY2) libsearpc-devel (→ libsearpc → PY2) seafile (→ PY2) seafile-devel (→ seafile → PY2) seafile-client (→ seafile → PY2) junghans votca-csg (→ votca-csg-common → PY2) votca-csg-bash (→ votca-csg → votca-csg-common → PY2) votca-csg-common (→ PY2) votca-csg-doc (→ votca-csg-common → PY2) votca-xtp (→ PY2) votca-xtp-doc (→ votca-csg-common → PY2) jwakely boost boost-mpich-python2 (→ PY2) boost-mpich-python2-devel (→ boost-mpich-python2 → PY2) boost-numpy2 (→ PY2) boost-openmpi-python2 (→ PY2) boost-openmpi-python2-devel (→ boost-openmpi-python2 → PY2) boost-python2 (→ PY2) boost-python2-devel (→ boost-numpy2 → PY2) jwrdegoede magicor (→ PY2) seahorse-adventures (→ PY2) kdudka python-pycurl python2-pycurl (→ PY2) kevin pylibacl (→ PY2) python-decorator python2-decorator (→ PY2) python-httplib2 python2-httplib2 (→ PY2) python-pysocks python2-pysocks (→ PY2) pyxattr python2-pyxattr (→ PY2) rdiff-backup (→ PY2) trac-authopenid-plugin (→ PY2) trac-git-plugin (→ PY2) trac-iniadmin-plugin (→ PY2) trac-mercurial-plugin (→ PY2) kiilerix hgview (→ PY2) hgview-common (→ PY2) hgview-curses (→ PY2) tortoisehg (→ PY2) tortoisehg-nautilus (→ tortoisehg → PY2) kkofler kig (→ PY2) konradm pyifp (→ PY2) kumarpraveen python-mock python2-mock (→ PY2) kushal python-chardet python2-chardet (→ PY2) kwizart python-BeautifulSoup python2-beautifulsoup (→ PY2) kylev python-formencode python2-formencode (→ PY2) python-mako python2-mako (→ PY2) python-simplejson python2-simplejson (→ PY2) landgraf mailman (→ PY2) laxathom python-gammu python2-gammu (→ PY2) lbalhar python-scales python2-scales (→ PY2) lbazan archmage (→ PY2) trac-blackmagictickettweaks-plugin (→ PY2) leigh123linux xed (BuildRequires: python2-gobject-base → PY2) lennart dbus (BuildRequires: python2-gobject → PY2) lfield glue-validator (→ PY2) limb angrydd (→ PY2) archivemail (→ PY2) findthatword (→ PY2) frescobaldi (→ lilypond → PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) gonvert (→ PY2) lilypond (→ PY2) monsterz (→ PY2) pybluez (→ PY2) pygame pygame-devel (→ python2-pygame → PY2) python2-pygame (→ PY2) python-dateutil python2-dateutil (→ PY2) python-easygui python2-easygui (→ PY2) python-gattlib python2-gattlib (→ PY2) python2-numpy (→ PY2) python2-numpy-doc (→ python2-numpy → PY2) python2-numpy-f2py (→ PY2) pytz python2-pytz (→ PY2) slimdata (BuildRequires: python2-numpy → PY2) slingshot (→ PY2) trac (→ PY2) trac-git-plugin (→ PY2) trac-iniadmin-plugin (→ PY2) trac-mercurial-plugin (→ PY2) linkdupont freeorion (→ PY2) lkundrak python-scales python2-scales (→ PY2) system-config-rootpassword (→ python2-libuser → PY2) lmacken mod_wsgi python2-mod_wsgi (→ PY2) python-coverage python2-coverage (→ PY2) python-formencode python2-formencode (→ PY2) python-mako python2-mako (→ PY2) python-sqlalchemy python2-sqlalchemy (→ PY2) trac (→ PY2) lotharlutz getmail (→ PY2) louizatakk python-dns python2-dns (→ PY2) lupinix python-iniparse python2-iniparse (→ PY2) python-mistune python2-mistune (→ PY2) luya scribus-generator (→ scribus → PY2) lzap pagekite (→ PY2) python-socksipychain python2-socksipychain (→ PY2) manuq sugar-browse (→ PY2) martinlanghoff olpc-update (→ PY2) pybox2d python2-pybox2d (→ PY2) mathstuf python-atomicwrites python2-atomicwrites (→ PY2) mattrose terminator (→ PY2) mayorga trac-blackmagictickettweaks-plugin (→ PY2) mbaldessari python-atomicwrites python2-atomicwrites (→ PY2) python-dpkt python2-dpkt (→ PY2) python-mutagen python2-mutagen (→ PY2) mbarnes dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) mbriza lokalize (→ python2-dbus → PY2) mcepl vim-vimoutliner (→ PY2) mck182 telepathy-qt (BuildRequires: python2-dbus → PY2) melmorabity nicotine+ (→ PY2) python-pycryptodomex python2-pycryptodomex (→ PY2) x-tile (→ PY2) mharmsen certmonger (BuildRequires: python2-dbus → PY2) mikeb python-cheetah python2-cheetah (→ PY2) miminar python-pillow python2-pillow (→ PY2) python2-pillow-devel (→ PY2) mitr audit-viewer (→ gnome-python2-gnome → PY2) libuser python2-libuser (→ PY2) python-gtkextra python2-gtkextra (→ PY2) mizdebsk protobuf python2-protobuf (→ PY2) python-lxml python2-lxml (→ PY2) mmahut gnuradio (→ PY2) gnuradio-devel (→ gnuradio → PY2) gnuradio-doc (→ gnuradio → PY2) gnuradio-examples (→ PY2) wxPython python2-wxpython (→ PY2) python2-wxpython-webview (→ PY2) wxPython-devel (→ python2-wxpython → PY2) wxPython-docs (→ python2-wxpython → PY2) moceap scons python2-scons (→ PY2) tuxcut (→ PyQt4 → PY2) moezroy fslint (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) python-mutagen python2-mutagen (→ PY2) mrceresa vtk (BuildRequires: python2-sip-devel → PY2) mrunge mod_wsgi python2-mod_wsgi (→ PY2) python-coverage python2-coverage (→ PY2) python-pbr python2-pbr (→ PY2) python-py python2-py (→ PY2) python-simplejson python2-simplejson (→ PY2) python-six python2-six (→ PY2) python2-pluggy (→ PY2) python2-pytest (→ PY2) mruszczyk whipper (→ PY2) mschorm python-mysql python2-mysql (→ PY2) msekleta python-pycurl python2-pycurl (→ PY2) mskalick python-cheetah python2-cheetah (→ PY2) scons python2-scons (→ PY2) mstuchli python-docutils python2-docutils (→ PY2) mtasaka comix (→ PY2) mcomix (→ PY2) python-mecab python2-mecab (→ PY2) skf python2-skf (→ PY2) nacho pygobject3 python2-gobject (→ PY2) python2-gobject-base (→ PY2) python2-gobject-devel (→ python2-gobject → PY2) nalin certmonger (BuildRequires: python2-dbus → PY2) nbecker Cython python2-Cython (→ PY2) git-remote-hg (→ PY2) tortoisehg (→ PY2) tortoisehg-nautilus (→ tortoisehg → PY2) nforro python-m2r python2-m2r (→ PY2) notting offlineimap (→ PY2) nphilipp asciidoc asciidoc-music (→ lilypond → PY2) babel python2-babel (→ PY2) lilv (BuildRequires: python2-numpy → PY2) python-sqlalchemy python2-sqlalchemy (→ PY2) nrhodes configsnap (→ PY2) nsoffer ioprocess python2-ioprocess (→ PY2) python-subprocess32 python2-subprocess32 (→ PY2) oddshocks python-docutils python2-docutils (→ PY2) python-q python2-q (→ PY2) odubaj PyGreSQL python2-pygresql (→ PY2) ogutierrez fleet-commander-client (→ python2-gobject → PY2) ohaessler terminator (→ PY2) okeeble dynafed (→ PY2) dynafed-dmlite-frontend (→ dynafed → PY2) dynafed-dmlite-plugin (→ dynafed → PY2) dynafed-http-plugin (→ dynafed → PY2) dynafed-lfc-plugin (→ dynafed → PY2) dynafed-private-devel (→ dynafed → PY2) dynafed-tpc-gfal2 (→ dynafed → PY2) ooprala git-remote-hg (→ PY2) orion grib_api (BuildRequires: python2-numpy → PY2) openmpi python2-openmpi (→ PY2) python-pycodestyle python2-pycodestyle (→ PY2) python-pypandoc python2-pypandoc (→ PY2) python-pytest-cov python2-pytest-cov (→ PY2) python-setuptools_scm python2-setuptools_scm (→ PY2) python-xlib python2-xlib (→ PY2) scipy python2-scipy (→ PY2) vtk (BuildRequires: python2-sip-devel → PY2) panovotn PyGreSQL python2-pygresql (→ PY2) python-cheetah python2-cheetah (→ PY2) scons python2-scons (→ PY2) parasense uboot-tools (BuildRequires: python2-setuptools → PY2) patches docco (→ python2-pygments → PY2) nodejs-snockets (BuildRequires: docco → python2-pygments → PY2) nodejs-watchit (BuildRequires: docco → python2-pygments → PY2) pbrady fslint (→ PY2) pbrobinson gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gwebsockets python2-gwebsockets (→ PY2) hippo-canvas python2-hippo-canvas (→ PY2) olpc-switch-desktop (→ PY2) olpc-update (→ PY2) pybox2d python2-pybox2d (→ PY2) python-elements python2-elements (→ PY2) python-olpcgames python2-olpcgames (→ PY2) python-telepathy python2-telepathy (→ PY2) sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-abacus (→ PY2) sugar-artwork (BuildRequires: python2-empy → PY2) sugar-base (→ PY2) sugar-browse (→ PY2) sugar-calculator (→ PY2) sugar-chat (→ PY2) sugar-clock (→ PY2) sugar-connect (→ PY2) sugar-datastore (→ PY2) sugar-distance (→ PY2) sugar-finance (→ PY2) sugar-flipsticks (→ PY2) sugar-getiabooks (→ PY2) sugar-imageviewer (→ PY2) sugar-implode (→ PY2) sugar-infoslicer (→ PY2) sugar-jukebox (→ PY2) sugar-labyrinth (→ PY2) sugar-maze (→ PY2) sugar-memorize (→ PY2) sugar-paint (→ PY2) sugar-physics (→ PY2) sugar-pippy (→ PY2) sugar-playgo (→ PY2) sugar-record (→ PY2) sugar-runner (→ PY2) sugar-runner-devel (→ sugar-runner → PY2) sugar-speak (→ PY2) sugar-stopwatch (→ PY2) sugar-terminal (→ PY2) sugar-toolkit-gtk3 (→ PY2) sugar-toolkit-gtk3-devel (→ sugar-toolkit-gtk3 → PY2) sugar-view-slides (→ PY2) sugar-write (→ PY2) sugar-xoirc (→ PY2) sugar-xomail (→ PY2) telepathy-mission-control (BuildRequires: python2-dbus → PY2) uboot-tools (BuildRequires: python2-setuptools → PY2) xapian-bindings python2-xapian (→ PY2) pcahyna git-remote-hg (→ PY2) pcpa miniupnpc python2-miniupnpc (→ PY2) python-pathlib2 python2-pathlib2 (→ PY2) peter b43-openfwwf (BuildRequires: b43-tools → PY2) gflags (BuildRequires: python2-setuptools → PY2) protobuf python2-protobuf (→ PY2) pghmcfc bluefish (→ PY2) bluefish-shared-data (→ PY2) python-crypto python2-crypto (→ PY2) python2-typing (→ PY2) trac-accountmanager-plugin (→ PY2) trac-spamfilter-plugin (→ PY2) pgordon gourmet (→ PY2) phuang dbus-python python2-dbus (→ PY2) pingou python-GeoIP python2-GeoIP (→ PY2) python-hypothesis python2-hypothesis (→ PY2) pjp python-dateutil python2-dateutil (→ PY2) python-oauth2 python2-oauth2 (→ PY2) pkajaba PyGreSQL python2-pygresql (→ PY2) pkfed openmpi python2-openmpi (→ PY2) pkubat PyGreSQL python2-pygresql (→ PY2) plambri sx (→ PY2) poros ddiskit (→ PY2) potty python-xlib python2-xlib (→ PY2) praiskup PyGreSQL python2-pygresql (→ PY2) pspacek python-dns python2-dns (→ PY2) pstodulk git-remote-hg (→ PY2) hg-git (→ PY2) puiterwijk trac-CGit-plugin (→ PY2) trac-authopenid-plugin (→ PY2) trac-sensitivetickets-plugin (→ PY2) trac-xmlrpc-plugin (→ PY2) pviktori python-six python2-six (→ PY2) pwalter b43-tools (→ PY2) miniupnpc python2-miniupnpc (→ PY2) scribus (→ PY2) pwouters python-dns python2-dns (→ PY2) python-pydns python2-pydns (→ PY2) python-pymilter python2-pymilter (→ PY2) qulogic git-cinnabar (→ PY2) ralph python-GeoIP python2-GeoIP (→ PY2) python-decorator python2-decorator (→ PY2) python-formencode python2-formencode (→ PY2) python-funcsigs python2-funcsigs (→ PY2) python-pysocks python2-pysocks (→ PY2) python-q python2-q (→ PY2) python-zmq python2-zmq (→ PY2) python2-zmq-tests (→ PY2) python-zope-event python2-zope-event (→ PY2) raphgro pdf-stapler (→ PY2) python2-staplelib (→ PY2) rcritten certmonger (BuildRequires: python2-dbus → PY2) rdieter PyQt4 (→ PY2) PyQt4-devel (→ python2-sip-devel → PY2) PyQt4-webkit (→ PY2) dbus-python python2-dbus (→ PY2) kig (→ PY2) lokalize (→ python2-dbus → PY2) pyside-tools (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) python-qt5 python2-qt5 (→ PY2) python2-qt5-base (→ PY2) python2-qt5-devel (→ python2-sip-devel → PY2) python2-qt5-webkit (→ PY2) qscintilla python2-qscintilla (→ PY2) python2-qscintilla-devel (→ PyQt4-devel → python2-sip-devel → PY2) python2-qscintilla-qt5 (→ PY2) python2-qscintilla-qt5-devel (→ python2-qt5-devel → python2-sip-devel → PY2) shiboken (→ shiboken-python2-libs → PY2) shiboken-python2-devel (→ PY2) shiboken-python2-libs (→ PY2) sip python2-pyqt4-sip (→ PY2) python2-pyqt5-sip (→ PY2) python2-sip-devel (→ PY2) python2-wx-siplib (→ PY2) telepathy-logger-qt (BuildRequires: python2-dbus → PY2) telepathy-qt (BuildRequires: python2-dbus → PY2) reaperzn configsnap (→ PY2) rebus python-olefile python2-olefile (→ PY2) python-oletools python2-oletools (→ PY2) python-volatility python2-volatility (→ PY2) remi glpi (→ macromilter → PY2) php-horde-horde (→ macromilter → PY2) php-horde-imp (→ php-horde-horde → macromilter → PY2) php-horde-ingo (→ php-horde-horde → macromilter → PY2) php-horde-kronolith (→ php-horde-horde → macromilter → PY2) php-horde-mnemo (→ php-horde-horde → macromilter → PY2) php-horde-nag (→ php-horde-horde → macromilter → PY2) php-horde-passwd (→ php-horde-horde → macromilter → PY2) php-horde-turba (→ php-horde-horde → macromilter → PY2) php-horde-wicked (→ php-horde-horde → macromilter → PY2) rhughes dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) ricky getmail (→ PY2) rmattes fawkes fawkes-devenv (→ PyQt4-devel → python2-sip-devel → PY2) gazebo (BuildRequires: python2-pyopengl → PY2) robert macromilter (→ PY2) python-olefile python2-olefile (→ PY2) python-oletools python2-oletools (→ PY2) robled rocket-depot (→ PY2) ron samtools (→ PY2) rrankin denemo (→ lilypond → PY2) rrix python-netifaces python2-netifaces (→ PY2) rstrode dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) rtsisyk tarantool (BuildRequires: python2-pyyaml → PY2) russellb asterisk (→ PY2) asterisk-ael (→ asterisk → PY2) asterisk-alembic (→ asterisk → PY2) asterisk-alsa (→ asterisk → PY2) asterisk-calendar (→ asterisk → PY2) asterisk-corosync (→ asterisk → PY2) asterisk-curl (→ asterisk → PY2) asterisk-dahdi (→ asterisk → PY2) asterisk-devel (→ asterisk → PY2) asterisk-fax (→ asterisk → PY2) asterisk-festival (→ asterisk → PY2) asterisk-hep (→ asterisk → PY2) asterisk-iax2 (→ asterisk → PY2) asterisk-ices (→ asterisk → PY2) asterisk-ldap (→ asterisk → PY2) asterisk-lua (→ asterisk → PY2) asterisk-mgcp (→ asterisk → PY2) asterisk-minivm (→ asterisk → PY2) asterisk-mobile (→ asterisk → PY2) asterisk-mwi-external (→ asterisk → PY2) asterisk-mysql (→ asterisk → PY2) asterisk-odbc (→ asterisk → PY2) asterisk-ooh323 (→ asterisk → PY2) asterisk-oss (→ asterisk → PY2) asterisk-pjsip (→ asterisk → PY2) asterisk-portaudio (→ asterisk → PY2) asterisk-postgresql (→ asterisk → PY2) asterisk-radius (→ asterisk → PY2) asterisk-sip (→ asterisk → PY2) asterisk-skinny (→ asterisk → PY2) asterisk-snmp (→ asterisk → PY2) asterisk-sqlite (→ asterisk → PY2) asterisk-tds (→ asterisk → PY2) asterisk-unistim (→ asterisk → PY2) asterisk-voicemail (→ asterisk → PY2) asterisk-voicemail-imap (→ asterisk → PY2) asterisk-voicemail-odbc (→ asterisk → PY2) asterisk-voicemail-plain (→ asterisk → PY2) s4504kr scons python2-scons (→ PY2) sagarun python-urllib3 python2-urllib3 (→ PY2) sagitter avogadro (BuildRequires: python2-sip-devel → PY2) scons python2-scons (→ PY2) seqan2 (BuildRequires: python2-jinja2 → PY2) salimma python-blist python2-blist (→ PY2) python-hypothesis python2-hypothesis (→ PY2) python-scandir python2-scandir (→ PY2) sdgathman python-pymilter python2-pymilter (→ PY2) sdz pybox2d python2-pybox2d (→ PY2) python-elements python2-elements (→ PY2) python-olpcgames python2-olpcgames (→ PY2) python-telepathy python2-telepathy (→ PY2) sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-artwork (BuildRequires: python2-empy → PY2) sugar-base (→ PY2) sugar-datastore (→ PY2) sugar-imageviewer (→ PY2) sugar-jukebox (→ PY2) sugar-labyrinth (→ PY2) sugar-paint (→ PY2) sugar-physics (→ PY2) sugar-read (→ PY2) sugar-toolkit (→ PY2) sugar-turtleart (→ PY2) sugar-typing-turtle (→ PY2) sugar-visualmatch (→ PY2) telepathy-mission-control (BuildRequires: python2-dbus → PY2) xapian-bindings python2-xapian (→ PY2) sergiomb gdesklets (→ PY2) gflags (BuildRequires: python2-setuptools → PY2) python-GeoIP python2-GeoIP (→ PY2) python-gammu python2-gammu (→ PY2) sergiopr trac-doxygen-plugin (→ PY2) trac-xmlrpc-plugin (→ PY2) sgrubb audit python2-audit (→ PY2) sham1 ledger (BuildRequires: boost-python2-devel → boost-numpy2 → PY2) sharkcz gr-rds (→ PY2) gr-rds-devel (→ gr-rds → PY2) gr-rds-doc (→ gr-rds → PY2) pyparsing python2-pyparsing (→ PY2) scribus (→ PY2) tryton (→ PY2) uboot-tools (BuildRequires: python2-setuptools → PY2) wxPython python2-wxpython (→ PY2) python2-wxpython-webview (→ PY2) wxPython-devel (→ python2-wxpython → PY2) wxPython-docs (→ python2-wxpython → PY2) smani python-olefile python2-olefile (→ PY2) python-pillow python2-pillow (→ PY2) python2-pillow-devel (→ PY2) smilner python-pygments python2-pygments (→ PY2) smizrahi ioprocess python2-ioprocess (→ PY2) snavin sugar-castle (→ PY2) sugar-colordeducto (→ PY2) sugar-deducto (→ PY2) sugar-kuku (→ PY2) sugar-srilanka (→ PY2) sugar-starchart (→ PY2) sugar-story (→ PY2) sugar-xoeditor (→ PY2) sugar-yupana (→ PY2) sochotni asciidoc asciidoc-music (→ lilypond → PY2) spot pyrit (→ PY2) python-coverage python2-coverage (→ PY2) python-oauth2 python2-oauth2 (→ PY2) pyxdg python2-pyxdg (→ PY2) winpdb (BuildRequires: wxPython-devel → python2-wxpython → PY2) ssp dbus (BuildRequires: python2-gobject → PY2) dbus-python python2-dbus (→ PY2) gnome-python2 gnome-python2-canvas (→ PY2) gnome-python2-devel (→ PY2) gnome-python2-gconf (→ PY2) gnome-python2-gnome (→ PY2) gnome-python2-gnomevfs (→ PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) stefanok dbus-python python2-dbus (→ PY2) steved NFStest (→ PY2) stevetraylen Cython python2-Cython (→ PY2) glue-validator (→ PY2) python-inotify python2-inotify (→ PY2) python2-inotify-examples (→ PY2) stingray pyserial python2-pyserial (→ PY2) sundaram gif2png web2png (→ PY2) python-oauth2 python2-oauth2 (→ PY2) swt2c bakefile (→ PY2) python-pyopengl python2-pyopengl (→ PY2) wxPython python2-wxpython (→ PY2) python2-wxpython-webview (→ PY2) wxPython-devel (→ python2-wxpython → PY2) wxPython-docs (→ python2-wxpython → PY2) szpak pylibacl (→ PY2) pyxattr python2-pyxattr (→ PY2) talcite qcint (BuildRequires: python2-numpy → PY2) tartina lilv (BuildRequires: python2-numpy → PY2) tdabasin python-zope-event python2-zope-event (→ PY2) terjeros pyparsing python2-pyparsing (→ PY2) python-BeautifulSoup python2-beautifulsoup (→ PY2) python-futures python2-futures (→ PY2) python-inotify python2-inotify (→ PY2) python2-inotify-examples (→ PY2) teuf offlineimap (→ PY2) than PyQt4 (→ PY2) PyQt4-devel (→ python2-sip-devel → PY2) PyQt4-webkit (→ PY2) lokalize (→ python2-dbus → PY2) pyside-tools (→ PY2) python-pyside python-pyside-devel (→ python2-pyside → PY2) python2-pyside (→ PY2) python-qt5 python2-qt5 (→ PY2) python2-qt5-base (→ PY2) python2-qt5-devel (→ python2-sip-devel → PY2) python2-qt5-webkit (→ PY2) shiboken (→ shiboken-python2-libs → PY2) shiboken-python2-devel (→ PY2) shiboken-python2-libs (→ PY2) sip python2-pyqt4-sip (→ PY2) python2-pyqt5-sip (→ PY2) python2-sip-devel (→ PY2) python2-wx-siplib (→ PY2) thl mailnag (→ PY2) thm email2trac (→ PY2) etckeeper etckeeper-bzr (→ PY2) python-jinja2 python2-jinja2 (→ PY2) python-py python2-py (→ PY2) python2-pluggy (→ PY2) python2-pytest (→ PY2) trac-monotone-plugin (→ PY2) trac-tracnav-plugin (→ PY2) viewmtn (→ python2-mod_wsgi → PY2) thofmann fawkes fawkes-devenv (→ PyQt4-devel → python2-sip-devel → PY2) tibbs python2-numpy (→ PY2) python2-numpy-doc (→ python2-numpy → PY2) python2-numpy-f2py (→ PY2) python2-pytest (→ PY2) python2-setuptools (→ PY2) tieugene lumina-desktop (→ fluxbox → PY2) timn fawkes fawkes-devenv (→ PyQt4-devel → python2-sip-devel → PY2) tmz asciidoc asciidoc-music (→ lilypond → PY2) tnorth python-blosc (BuildRequires: python2-numpy → PY2) tomeu sugar-artwork (BuildRequires: python2-empy → PY2) sugar-base (→ PY2) sugar-datastore (→ PY2) sugar-toolkit (→ PY2) tommi pynag (→ PY2) pynag-examples (→ PY2) tomspur python-dateutil python2-dateutil (→ PY2) python-zmq python2-zmq (→ PY2) python2-zmq-tests (→ PY2) scipy python2-scipy (→ PY2) shedskin (→ PY2) toshio python-q python2-q (→ PY2) trasher glpi (→ macromilter → PY2) iipsrv (→ macromilter → PY2) iipsrv-httpd-fcgi (→ iipsrv → macromilter → PY2) tremble graphviz graphviz-python2 (→ PY2) tripledes scribus (→ PY2) ttomecek python-pytest-cov python2-pytest-cov (→ PY2) scipy python2-scipy (→ PY2) ttorling python-mock python2-mock (→ PY2) python-pysocks python2-pysocks (→ PY2) tuju python-utmp python2-utmp (→ PY2) tuxbrewr sugar (→ PY2) sugar-cp-all (→ sugar → PY2) sugar-cp-background (→ sugar → PY2) sugar-cp-backup (→ sugar → PY2) sugar-cp-datetime (→ sugar → PY2) sugar-cp-frame (→ sugar → PY2) sugar-cp-keyboard (→ sugar → PY2) sugar-cp-language (→ sugar → PY2) sugar-cp-modemconfiguration (→ sugar → PY2) sugar-cp-network (→ sugar → PY2) sugar-cp-power (→ sugar → PY2) sugar-cp-updater (→ sugar → PY2) sugar-cp-webaccount (→ sugar → PY2) sugar-calculator (→ PY2) sugar-chat (→ PY2) sugar-clock (→ PY2) sugar-connect (→ PY2) sugar-distance (→ PY2) sugar-finance (→ PY2) sugar-flipsticks (→ PY2) sugar-getiabooks (→ PY2) sugar-imageviewer (→ PY2) sugar-implode (→ PY2) sugar-infoslicer (→ PY2) sugar-log (→ PY2) sugar-maze (→ PY2) sugar-memorize (→ PY2) sugar-pippy (→ PY2) sugar-playgo (→ PY2) sugar-read (→ PY2) sugar-record (→ PY2) sugar-speak (→ PY2) sugar-stopwatch (→ PY2) sugar-terminal (→ PY2) sugar-view-slides (→ PY2) sugar-write (→ PY2) sugar-xoirc (→ PY2) uggla python-colorclass python2-colorclass (→ PY2) uwog abiword python2-abiword (→ PY2) valtri kiss-fft (BuildRequires: python2-numpy → PY2) vascom klavaro (BuildRequires: python2-docutils → PY2) veillard libxml2 python2-libxml2 (→ PY2) verdurin minicomputer (BuildRequires: python2-scons → PY2) mmseq (→ samtools → PY2) samtools (→ PY2) volter qgis (BuildRequires: python2-sip-devel → PY2) vrutkovs python-pytest-runner python2-pytest-runner (→ PY2) walters dbus (BuildRequires: python2-gobject → PY2) gnome-python2-desktop (→ gnome-python2-canvas → PY2) gnome-python2-gnomekeyring (→ PY2) gnome-python2-libwnck (→ PY2) gnome-python2-rsvg (→ PY2) pygobject3 python2-gobject (→ PY2) python2-gobject-base (→ PY2) python2-gobject-devel (→ python2-gobject → PY2) wcohen sediment (→ graphviz-python2 → PY2) wtaymans python-gstreamer1 python2-gstreamer1 (→ PY2) xaeth python-augeas python2-augeas (→ PY2) zbyszek mpich python2-mpich (→ PY2) python-blosc (BuildRequires: python2-numpy → PY2) python-music21 python3-music21 (→ lilypond → PY2) python-pypandoc python2-pypandoc (→ PY2) systemd-coredump-python python2-systemd-coredump (→ PY2) The code that generates this list is inspectable at: https://github.com/frenzymadness/Fedora_Py2_removal/blob/master/dependencie… -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 0

Fedora 31 is officially here!
by Matthew Miller 29 Oct '19

29 Oct '19

Thank you to the entire community of Fedora contributors who collaborated to create, once again, our best operating system release yet. Read the official announcement at: * https://fedoramagazine.org/announcing-fedora-31/ or just go ahead and grab it from: * https://getfedora.org/ -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ announce mailing list -- announce(a)lists.fedoraproject.org To unsubscribe send an email to 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/announce@lists.fedoraproject.…

1 0

Fedora Modularity: What's the Problem?
by Stephen Gallagher 28 Oct '19

28 Oct '19

One of the recurring themes in the ongoing Modularity threads has been that we've made references to the problems we're trying to solve, but we haven't done a good job of gathering those requirements and use-cases into a single place. To resolve this, I've written a (fairly long) blog post describing the set of problems that we are trying to solve. You can read it with nice formatting over at https://communityblog.fedoraproject.org/fedora-modularity-whats-the-problem/ or the mediocre copy-and-paste I'm including in this message. (Apologies for the HTML mail; I want to preserve the hyperlinks and formatting from the blog post) --- Fedora Modularity: What’s the Problem? <https://communityblog.fedoraproject.org/fedora-modularity-whats-the-problem/> Much has been said <https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…> about Fedora Modularity over the past couple weeks. Much of it has been constructive; some of it the expected resistance to change that all large features encounter. Some, however, is the result of our not having painted a good picture of the problems that Modularity aims to solve. Numerous suggestions have been made on the Fedora Development mailing list that sound good on the surface but that ultimately fail to address some important use-cases. This blog post will attempt to enumerate these cases in detail so as to serve as a common reference point for the ongoing discussions. Please note as well that these are goals. There are numerous places where the implementation of Modularity at the time of this writing is not yet fully adherent to them. It’s all about the apps! Though many of the readers of this blog might be of a different mind, it’s important to remember that very few people install a Linux distribution for its own sake. Ultimately, the goal is to “scratch a particular itch” that the user is experiencing. The solutions may take many forms, but ultimately this user wants to deploy some software that solves a problem for them. This leads us to a classic problem that Linux distributions have faced: the “Too Fast/Too Slow” problem. Linux distributions are traditionally quite monolithic. The package collections they ship are generally self-consistent, providing generally whatever the latest stable major release of the software at the time of the distribution release. As the release ages, it will receive bugfixes and enhancements, but usually will remain on the same major version. This is excellent for the maintainers of the distribution, because it allows them to test that everything works together as a cohesive whole. It means that there’s one authoritative version to align to. Users, on the other hand, are most concerned about solving their problem. It matters less to them that the distribution is cohesive and more that the tools they need are available to them. The “Too Fast/Too Slow” problem is basically this: users want a solid, stable, reliable, *unchanging* system. They want it to stay that way for the life of their application. However, they also want their application to run using the set of dependencies it was designed for. If that doesn’t happen to be the same version (newer or older) as the one selected for the monolithic distribution, the user will now have to resort to alternative means to get up and running. This may be as simple as bundling a dependency or as drastic as selecting an entirely different distribution that better fits their specific need. A little background One of the precursors to Fedora Modularity was Software Collections <https://www.softwarecollections.org/> (SCLs). This was a first try at solving the Too Fast/Too Slow” problem in the Fedora/Red Hat ecosystem. provides two basic advantages: *Parallel Availability* and *Parallel Installability*. *Parallel Availability* means that more than one major release of a popular software project is available for installation. For example, the “Developer Toolset” SCLs provide access to newer versions of GCC and its related toolchain for building software. There are Python and Ruby SCLs that provide assorted runtimes for those languages and so on. *Parallel Installability* means that more than one major release of a software project can be installed on the same userspace. A few years back, the Product Management team inside Red Hat performed a large-scale survey of customers and potential customers about the user experience of Red Hat Enterprise Linux. In particular, they asked about their level of satisfaction with the software available from the enterprise distribution and their opinion on these Software Collections. Perhaps unsurprisingly, the overwhelming majority of respondents were thrilled to have supported versions of software beyond what had shipped with the base operating system. What the survey team did come away with that was an epiphany was that the respondents generally did not care about the parallel installability of the SCLs. For the most part, they maintained individual userspaces (using bare metal, traditional virtualization or containers) for each of the applications they cared about. The most common problem reported for Software Collections was that using them required changes to the applications they wanted to run. SCLs install to a separate filesystem location from more traditional RPMs and applications that rely on them need to know where to look for them. (In SCL parlance, this is called “activating” the collection.) The consequence of this relocation on disk is that users were unable to take existing applications (either FOSS or proprietary) and simply use them. Instead, they had to modify the projects to first activate the collections. This was a consistent pain point. Given this feedback, Red Hat came to the conclusion that parallel installability, while nice to have, was not a critical user requirement. Instead, the focus would be on the parallel *availability*. By dropping this requirement, it became possible to create a solution that allowed the different versions to be swapped in and take over the standard locations on the disk. Meanwhile in Fedora Of course, it’s not just Red Hat — people in Fedora are also concerned with solving this Too Fast / Too Slow problem for our users. Efforts around this kicked off in seriousness with the Fedora.next initiative <https://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-upd…> and Fedora Project Leader Matthew Miller’s “Rings <https://lwn.net/Articles/563395/>” talk at the first Flock conference in 2013. This led to the proposal and approval by the Fedora Council of the Modularity Prototype Fedora Objective <https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_…> and its follow-up Modularity Release Fedora Objective <https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_T…> . Critical use cases for consumers First and foremost, our primary driving goal is to make it easy for our users to understand and interact with alternative software versions. In any instance where choosing between the packager experience and the user experience is in conflict, we elect to improve things for the user. Standard Locations In order to make deployment of users’ applications simpler, we need to make sure that software can be installed into the common, expected locations on the system. This includes (but is not limited to): - Libraries must be installed to /usr/lib[64]. - Headers must be installed to /usr/include. - Executables must be installed to a location in the default system $PATH - Other -devel functionality such as pkgconfig files must be installed in their standard lookup locations. - Installed services may own a well-known DBUS address. - Services may own the appropriate standard TCP/UDP ports or local socket paths. *Requirement*: Installation must occur in the same locations as traditional RPM software delivery. Don’t break the app! It is very common for Fedora to update to the latest major version of packages at each new semiannual release. This ensures that Fedora remains at the leading edge of software development, but it can wreak havoc on anyone trying to maintain a deployment on Fedora. If they are running an app that is built for PostgreSQL 9.6 and Fedora switches to carrying PostgreSQL 10 in the next major release, upgrading to that release may break their app (possibly in ways undetectable by the upgrade process). However, staying on an old version of Fedora forever has its own problems. Not least of these is the problem of security updates: Once a release has been out for about 13 months, it stops receiving errata. Moreover, new releases of the Fedora platform may have other useful enhancements (better security defaults, increased performance thanks to compiler improvements, etc.). *Requirement*: We need to allow users to “lock” themselves onto certain dependencies as long as the packager is maintaining them. These dependencies must continue to receive updates. *Requirement*: There must be appropriate and helpful UX for dealing with when those dependencies go EOL. Support the developers Developers often want to build their applications using the latest-and-greatest version of their dependencies. However, that may not have been released until after the most recent Fedora release. In non-Modular Fedora, that means waiting up to six months to be able to work on it there. *Requirement*: It must be possible to gain access to newer software than was available at the Fedora release GA. Additionally, Dev/Ops people are rapidly switching to a new paradigm of development and deployment (containers) to solve the above issue. However, most containers today are retrieved from public repositories. The public repositories are generally user-managed and have not been verified and validated for security. *Requirement*: Provide a mechanism for building *trusted* container base and application images with content alternatives. Keep it updated It’s not enough that other versions of software are available to install. They also need to be kept up to date with bug fixes and security updates. In non-Modular Fedora, users had the ability to force DNF to lock to a specific RPM NEVRA, but they wouldn’t get updates from it. *Requirement*: Alternative software must receive be able to recieve and apply updates. Make it discoverable Having alternative versions available is important but not sufficient. It is also necessary for users to be able to locate these alternatives. Some of our early explorations into this area failed this ease-of-use test because they require the user to have knowledge of external sites and then to search those sites for what they think they want. *Requirement*: Users must be able to discover what alternative software versions are available with tools that are shipped with the OS by default. Ideally, these should be the same tools that they are already comfortable with. Don’t break existing package management workflows Users are slow to adapt to changes in the way they need to behave. Requiring them to learn a new set of commands to interact with their system will likely result in frustration and possibly exodus to other distributions. *Requirement*: It must remain possible to continue to operate with only the package management commands used in traditional Fedora. We may provide additional commands to support new functionality, but we must not break the previous workflow. *Requirement*: Existing automation tools such as anaconda’s kickstart and Ansible must continue to work. Critical use-cases for packagersDependencies Because very little software today is wholly self-contained, it must be possible for Modules to depend on each other. *Requirement*: There must be a mechanism for packagers to explicitly list dependencies on other software, including alternative versions. This mechanism must support both build-time and run-time dependencies. Alternative dependencies Some software is very restrictive about which dependencies it can work with. Other software may work with several different major releases of a dependency. For example, a user may ship two Ruby-based web applications, one which is capable of running on Ruby 2.5 and the other that can run on either Ruby 2.5 or Ruby 2.6. In non-modular Fedora, only one version of Ruby would be available. If the system version was 2.5, then both applications could run fine. But if in the next release of Fedora the Ruby 2.6 release becomes the system copy, one of those applications will have to be dropped (or patched) to work with it. *Requirement*: It must be possible to build software that can be run against multiple versions of its dependencies. *Requirement*: The packaging process for creating software that supports multiple versions of their dependencies must not be significantly more difficult than packaging for a single dependency. As more and more things become modules, there is concern that such things will grow into an unbounded matrix. For this, we need to establish policies on when the use of alternative dependencies is preferable or when it is better to constrain it to a single version or small set. *Requirement*: Packaging guidelines need to provide advice on when to use multiple alternative dependencies or to select a single one. Managing private dependencies When a person decides that they want Fedora to carry a particular package and decides to do the work to accomplish this, it is not uncommon to discover that the package they care about has additional dependencies that are not yet packaged in Fedora. Traditionally, this has meant that the packager has needed to package up those dependencies and then continue to maintain them for anyone who may be using them for other purposes. This can sometimes be a significant investment in time and energy, all to support a package they don’t necessarily care about except for how it supports the primary package. Build-time Dependencies Sometimes, a package is needed only to build the software and is not required at run-time. In such cases, Modularity should offer the ability to keep those build-time dependencies entirely private and not exposed to the Fedora Package Collection at large. *Requirement*: Build-time only dependencies for an alternative version may be excluded from the installable output artifacts. These excluded artifacts may be preserved by the build-system for other purposes. *Requirement*: All sources used for generating alternative versions, regardless of final visibility, must be available to the community for purposes of modification and reproducibility. Defining the public API Similarly, there are times when an application the packager cares about depends on another package that is required at runtime, but sufficiently complex that the packager would not want to maintain it for general use. (For example, an application that links to a complicated library but only uses a few functions.) In this case, we want there to be a standard mechanism for the packager to be able to indicate that some of the output artifacts are not supported for use outside this module. If they are needed by others, they should package it themselves and/or help maintain it in a shared place. *Requirement*: Packagers must be able to encode whether their output artifacts are intended for use by other projects or if they are effectively private to the alternative version. Packagers must also have a way of finding this information out so they understand what they can and cannot rely on as a dependency. Use-case-based installation Since the earliest days of Linux, the “package” has been the fundamental unit of installable software. If you want to have some functionality on the system, you need to learn the name of the individual packages that provide that functionality (not all of which are named obviously). As we build modules, one of the goals is to try to focus installation around use-cases rather than around upstream projects. A big piece of this is that we want to have a way to install a subset of a module that supports specific use-cases. A common example being “server” and “client” cases. *Requirement*: It must be possible to install a subset of artifacts from an alternative version. These installation groups should be easily discoverable. *Recommendation*: Installation groups should be named based on the use-case they are intended to solve. This will provide a better user experience. Lifecycle isolation Another of the major issues faced by Fedora is maintaining a release schedule when all of the components within it follow vastly differing schedules. There are two main aspects to this problem: - A major version of a popular piece of software is released just after a Fedora release, so it doesn’t land in Fedora for six months. - Some software does frequent major revisions (Django, Node.js, etc.) and swapping them out every six months for the latest one means that dependent projects are constantly needing to adapt to the new breakage or find alternative mechanisms for retaining the older, working version - Some software does not handle multiple-version upgrades (Nextcloud, for example). Attempting to go from version 15 to verison 19 requires first upgrading through 16, 17, and 18. *Requirement*: It must be possible for new alternative versions of software to become available to the Fedora Package Collection between release dates. *Requirement*: It must be possible for alternative versions of software to go end-of-life during a Fedora release. This does not mean that the software must disappear from the repositories, merely that an assertion exists somewhere that after a certain date, the package will not receive updates. *Requirement*: For alternative versions whose lifecycle will continue through at least part of the next Fedora release, it must be possible to upgrade from one release to the next and remain with the fully-compatible version. Third-party additions Some third-party add-on repositories (particularly EPEL) have been limited in the past by relying on the system copies of packages in the base distribution of the release. In the particular case of EPEL, little can be done to upgrade these system copies. In order to be able to package much of the available FOSS software out there, it may be necessary to override some of the content shipped in the base system with packages known to work properly. *Requirement*: It must be possible for third party repositories to create alternative versions that override base distribution content at the user’s explicit choice. *Requirement*: It must be possible for third party repositories to create alternative versions of software that exist in the base distribution. Reduce duplication in packaging work There is plenty of software out in the wild that maintains compatibility over time and is therefore useful to carry in multiple releases of Fedora. With traditional packaging, this means carrying and building separate branches of the packages for each release of Fedora. In the case of software “stacks” which are tightly bound, this means also manually building each of its dependencies in each release of Fedora. *Requirement*: It must be possible to build multiple component software packages in the same build process. *Requirement*: It must be possible for the packager to specify the order in which packages must be built (and to indicate which ones can be built in parallel). *Requirement*: It must be possible to be build for all supported platforms using the same specification and with a single build command. Non-GoalsParallel installability As mentioned in the Background section, the goals of Modularity are specifically to *not* implement parallel-installability. We recommend instead that users should rely on other mechanisms such as virtualization or containerization to accomplish this. If parallel-installation is unavoidable, then Modularity is not the correct tool for this job. Arbitrary stream switching Module streams are intended to be compatible update streams. That means they must follow the same rules regarding RPM package-level updates within the stream. By definition, two streams of the same module exist because upgrades (or downgrades or cross-grades…) are not capable of being done in a safe, automated fashion. That does not mean that stream switching should be impossible, but it does mean that we will not build any tools intended to handle such switching in a generic manner. Stream switches should be handled on a module-by-module basis and detailed instructions and/or tools written for each such case.

1 0

Fedora 31 Final is GO
by Ben Cotton 24 Oct '19

24 Oct '19

The Fedora 31 Final RC1.9 compose [1] is GO and will be shipped live on Tuesday, 29 October 2019. For more information please check the Go/No-Go meeting minutes [2] or logs [3]. Thank you to everyone who has worked on this release and getting it out on time. [1] https://dl.fedoraproject.org/pub/alt/stage/31_RC-1.9/ [2] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… [3] https://meetbot.fedoraproject.org/fedora-meeting/2019-10-24/f31-final-go_no… -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce October 2019