Your message dated Thu, 3 Feb 2022 01:39:04 +0100
with message-id <[email protected]>
and subject line Re: Bug#1004879: acpitool: New upstream development?
has caused the Debian Bug report #1004879,
regarding acpitool: New upstream development?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1004879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004879
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: acpitool
Source-Version: 0.5.1-6
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: Al Stone <[email protected]>

Hi!

I just noticed that Al Stone forked the upstream of this project
at <https://pagure.io/acpitool>, collected several of the distro
patches and prepared a 0.5.2 release. Although no more activity
happened since 3 years ago, so I'm not sure what the current status
is there. I'm CCing Al to try to clarify whether this is abandoned
or in maintenance mode, and further patches and similar would be
accepted (we have some in the Debian Bug Tracking System). Which
means we could switch to use that as our upstream.

Thanks,
Guillem

--- End Message ---
--- Begin Message ---
On Wed, 2022-02-02 at 16:00:07 -0700, Al Stone wrote:
> On 02 Feb 2022 22:25, Guillem Jover wrote:
> > Source: acpitool
> > Source-Version: 0.5.1-6
> > Severity: wishlist
> > Tags: upstream
> > X-Debbugs-Cc: Al Stone <[email protected]>

> > I just noticed that Al Stone forked the upstream of this project
> > at <https://pagure.io/acpitool>, collected several of the distro
> > patches and prepared a 0.5.2 release. Although no more activity
> > happened since 3 years ago, so I'm not sure what the current status
> > is there. I'm CCing Al to try to clarify whether this is abandoned
> > or in maintenance mode, and further patches and similar would be
> > accepted (we have some in the Debian Bug Tracking System). Which
> > means we could switch to use that as our upstream.

> I resigned from Debian some time ago.  Do with this whatever you'd
> like.
> 
> I am no longer willing to volunteer my time to this distro.

Oh, when I noticed that project on pagure.io, and given your commits
as @redhat.com I assumed that was a RedHat initiative, and was
contacting you in your capacity as upstream, given that many other
distributions seem to be stuck with the same old version with various
amounts of local patching, according to repology.org.

But, in any case, sorry for bothering you. I'm closing this report as
I assume that fork is not going anywhere (regardless of the distro
involved).

Sorry,
Guillem

--- End Message ---

Reply via email to