https://bugzilla.redhat.com/show_bug.cgi?id=2065935
Bug ID: 2065935
Summary: asciidoctor package not present
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: rubygem-asciidoctor
Assignee: dan.j.allen(a)gmail.com
Reporter: alexisgandroid(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dan.j.allen(a)gmail.com,
epel-packagers-sig(a)lists.fedoraproject.org,
ktdreyer(a)ktdreyer.com, mjg(a)fedoraproject.org,
tmz(a)pobox.com
Target Milestone: ---
Classification: Fedora
Is rubygem-asciidoctor supposed to exist in epel8?
It's the only package missing for wireshark.
Otherwise, could you add it?
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2065935
https://bugzilla.redhat.com/show_bug.cgi?id=2077980
Vitaly Zaitsev <vitaly(a)easycoding.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(amctagga(a)redhat.c
| |om)
--- Comment #2 from Vitaly Zaitsev <vitaly(a)easycoding.org> ---
Why did you add me to this issue? I'm not maintainer of SCT package.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2077980
https://bugzilla.redhat.com/show_bug.cgi?id=2077980
Kevin Kofler <kevin(a)tigcc.ticalc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|kevin(a)tigcc.ticalc.org |
--- Comment #1 from Kevin Kofler <kevin(a)tigcc.ticalc.org> ---
Why the heck did you add all those CCs? I do not see how this vulnerability
would affect me or any of my packages.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2077980
https://bugzilla.redhat.com/show_bug.cgi?id=2063475
Bug ID: 2063475
Summary: python-libtmux-0.11.0b2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-libtmux
Keywords: FutureFeature, Triaged
Assignee: mail(a)fabian-affolter.ch
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dcavalca(a)fb.com,
epel-packagers-sig(a)lists.fedoraproject.org,
mail(a)fabian-affolter.ch
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.11.0b2
Current version/release in rawhide: 0.10.3-1.fc37
URL: https://pypi.python.org/pypi/libtmux
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/13040/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2063475