public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: happysmash27 <happysmash27@protonmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-misc/utimer
Date: Wed, 22 Jan 2025 12:46:47 +0000	[thread overview]
Message-ID: <KWW5u5o06YH8INMm2FTFooWamgGgasq81RaAHrFuIe1Uj29CS25MRQ3u3UMHYhhyeO0RIlhSSNqXxDAedE8qPGGLKW3e1dIlh_ql7q3FnEI=@protonmail.com> (raw)
In-Reply-To: <999ebcfade6af92ddf7c13090ca04ee7e1a651bc.camel@gentoo.org>

I am EXTREMELY reliant on this package (for my alarm every morning) and just now have noticed it broken right as I was about to go to bed (due to continuing to work on a VERY large system update for the new profile version from mid-2024, which has been taking a very very long time due to the large amount of legacy packages on my system).

It seems to still work fine after tracking down all the old ebuild files and the workaround Maciej S. Szmigiero posted – though, my system is about 6 months out of date due to the profile migration blocking `emerge --sync`, so hopefully nothing has changed about this since then.

What would be the process for maintaining it to get it in the repositories again? It seems to be a relatively simple program, so hopefully not too hard to maintain in a working state – and is also one of THE most mission-critical packages for me, so worth it for me to go through the effort to keep it working at any cost.

On Sunday, December 31st, 2023 at 08:00, Michał Górny <mgorny@gentoo.org> wrote:

> # Michał Górny mgorny@gentoo.org (2023-12-31)
> 
> # Unmaintained.  A number of serious bugs reported.  Homepage gone.
> # No release since at least 2010.
> # Removal on 2024-01-30.  Bug #915827.
> app-misc/utimer
> 
> --
> Best regards,
> Michał Górny


  reply	other threads:[~2025-01-22 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 16:00 [gentoo-dev] Last rites: app-misc/utimer Michał Górny
2025-01-22 12:46 ` happysmash27 [this message]
2025-01-22 13:07   ` Agostino Sarubbo

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='KWW5u5o06YH8INMm2FTFooWamgGgasq81RaAHrFuIe1Uj29CS25MRQ3u3UMHYhhyeO0RIlhSSNqXxDAedE8qPGGLKW3e1dIlh_ql7q3FnEI=@protonmail.com' \
    --to=happysmash27@protonmail.com \
    --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