public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: orbea <orbea@riseup.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Packages up for grabs: x11-misc/lightdm-mini-greeter and x11-misc/xautolock
Date: Wed, 21 Jun 2023 09:36:15 -0700	[thread overview]
Message-ID: <20230621093615.13565c11@Akita> (raw)
In-Reply-To: <876bad6e-6ebc-719c-ba44-69fb5d0fa14c@uls.co.za>

On Wed, 21 Jun 2023 16:23:38 +0200
Jaco Kroon <jaco@uls.co.za> wrote:

> Hi Hans,
> 
> On 2023/06/17 10:12, Hans de Graaff wrote:
> > After migrating to Wayland I no longer have a need for these X
> > packages. I have already removed myself as maintainer.
> >
> > x11-misc/xautolock
> >
> > Has one open bug that should be addressed upstream, but upstream is
> > pretty much dead: https://bugs.gentoo.org/634766  
> 
> I refer to an email 2022/07/19 where you took over xautolock from
> Jonas, now you're dropping it.  Doesn't look like much work was
> required since

I use xautolock and am willing to look at any pressing build issues if
they arise.

> 
> I'm still using this - you have moved to wayland so no longer a
> problem for you.
> 
>  From the referenced bug report it looks like there isn't much "care" 
> for the package any more?
> 
> Assuming mce@scarlet.be is no longer responsive either?
> 
>  From commit 0da382f0a5c38cce6e70a3724471a6c7981730d7 it looks like 
> there's some possible compile/build issues.

This commit talks about how using imake is problematic and while I
entirely agree with that, it may not be trivial to write a new build
system. I'll take a look later if I find time and motivation.

> 
> Kind regards,
> Jaco
> 
> 


  reply	other threads:[~2023-06-21 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  8:12 [gentoo-dev] Packages up for grabs: x11-misc/lightdm-mini-greeter and x11-misc/xautolock Hans de Graaff
2023-06-21 14:23 ` Jaco Kroon
2023-06-21 16:36   ` orbea [this message]
2023-06-24  7:47     ` Jaco Kroon
2023-06-23 17:17   ` Hans de Graaff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230621093615.13565c11@Akita \
    --to=orbea@riseup.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox