Comments page #1 of 200 pages

• Page 1 of 200
• «
• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• »

• pwalter on xdg-desktop-portal-1.2.0-2.fc29 2 days ago

  Works

  karma: +1
• pwalter on rpm-ostree-2019.2-1.fc29 2 days ago

  Works

  karma: +1
• pwalter on python-bugzilla-2.2.0-3.fc29 2 days ago

  Works

  karma: +1
• pwalter on pyOpenSSL-19.0.0-1.fc29 2 days ago

  Works

  karma: +1
• pwalter on plymouth-0.9.4-2.fc29 2 days ago

  Works

  karma: +1
• pwalter on perl-Module-Load-0.34-1.fc29 2 days ago

  Works

  karma: +1
• pwalter on osbs-client-0.52-1.fc29 2 days ago

  Works

  karma: +1
• pwalter on linux-firmware-20190213-93.git710963fe.fc29 2 days ago

  Works

  karma: +1
• pwalter on libgit2-glib-0.27.8-1.fc29 2 days ago

  Works

  karma: +1
• pwalter on flatpak-1.2.3-2.fc29 2 days ago

  Works

  karma: +1
• pwalter on devscripts-2.19.2-3.fc29 2 days ago

  Works

  karma: +1
• pwalter on clang-7.0.1-2.fc29 2 days ago

  Works

  karma: +1
• pwalter on mesa-18.3.3-1.fc29 2 days ago

  OK, we did get the libva update in the end, so the mesa update can now go back to testing: https://bodhi.fedoraproject.org/updates/FEDORA-2019-de14f07001
• pwalter on mesa-18.3.3-1.fc29 2 days ago

  This update has been unpushed.
• pwalter on mesa-18.3.3-1.fc29 2 days ago

  rpmfusion people say it's too much work to update libva (see https://github.com/rpmfusion/libva-intel-driver/pull/2) so looks like the mesa update is no go. Sorry guys.
• pwalter on mesa-18.3.3-1.fc29 3 days ago

  I opened a PR for rpmfusion libva-intel-driver that should fix this: https://github.com/rpmfusion/libva-intel-driver/pull/2
• pwalter on webkit2gtk3-2.22.6-1.fc29 3 days ago

  Works

  karma: +1
• pwalter on samba-4.9.4-1.fc29 3 days ago

  Works

  karma: +1
• pwalter on nss-pem-1.0.5-1.fc29 3 days ago

  Works

  karma: +1
• pwalter on nss-3.42.1-1.fc29 3 days ago

  Works

  karma: +1

• Page 1 of 200
• «
• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• »