Bug 1868983 - Non-responsive maintainer check for bochecha
Summary: Non-responsive maintainer check for bochecha
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: buildstream
Version: 34
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mathieu Bridon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-14 20:41 UTC by Artem
Modified: 2022-06-08 06:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-08 06:33:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Artem 2020-08-14 20:41:36 UTC
This bug is part of the non-responsive maintainer procedure for bochecha, 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 buildstream.

Comment 1 Ben Cotton 2021-02-09 16:23:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Lumír Balhar 2021-06-18 05:28:16 UTC
Should this bug be still open?

Comment 3 Artem 2021-07-14 11:38:33 UTC
(In reply to Lumír Balhar from comment #2)
> Should this bug be still open?

AFAIK such kind of bugs should closed only by FESCo. But latest Buildstream built successfully for Rawhide (f35) so no issue so far.

Comment 4 Ben Cotton 2022-05-12 15:00:19 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Mathieu Bridon 2022-05-13 17:43:54 UTC
Hi there, I'm not unresponsive, I just spent 2 years in a hospital, and I'm only now starting to come back and start contributing again. :-(

What should I do here ? Let me know and I'll do it whenever I can, as my limited time allows. ;-)

Comment 6 Artem 2022-05-13 19:55:34 UTC
Hi! This is great news. I've added you as admin for buildstream package and will be happy for any help. Recently we made almost all tests work but there is always something to improve or review https://src.fedoraproject.org/rpms/buildstream/pull-request/2.

Also switched to https://fedoraproject.org/wiki/Changes/rpmautospec.

Comment 7 Ben Cotton 2022-06-08 06:33:12 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.