Bug 2033707 - Non-responsive maintainer check for bpepple
Summary: Non-responsive maintainer check for bpepple
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gstreamer1-plugins-bad-free
Version: 36
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Scott Talbert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-17 16:44 UTC by Scott Talbert
Modified: 2022-02-18 16:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-18 16:13:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Scott Talbert 2021-12-17 16:44:35 UTC 
This bug is part of the non-responsive maintainer procedure for bpepple, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

Please respond if you are still active in Fedora and want to maintain gstreamer1-plugins-bad-free.

This package has FTBFS in Rawhide for ~1 month.  I submitted a PR with a fix here but no response:
https://src.fedoraproject.org/rpms/gstreamer1-plugins-bad-free/pull-request/7
Comment 1 Brian Pepple 2021-12-17 18:47:29 UTC 
I believe Wim is maintaining the gstreamer stack in Fedora these days, since I haven't been terribly active in Fedora for awhile.
Comment 2 Scott Talbert 2021-12-17 18:53:53 UTC 
(In reply to Brian Pepple from comment #1)
> I believe Wim is maintaining the gstreamer stack in Fedora these days, since
> I haven't been terribly active in Fedora for awhile.

Thanks for responding - could you perhaps make Wim the primary maintainer in dist-git so that is clear?
Comment 3 Fedora Admin user for bugzilla script actions 2022-02-01 01:55:53 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 4 Ben Cotton 2022-02-08 20:23:05 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.
Comment 5 Scott Talbert 2022-02-18 16:13:34 UTC 
This was handled.  bpepple's packages were orphaned and reassigned.
Note You need to log in before you can comment on or make changes to this bug.