public inbox for gentoo-proxy-maint@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vieri <rentorbuy@yahoo.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>,
	"Gokturk Yuksek" <gokturk@gentoo.org>,
	"Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] dev-libs/libaio: package up for grabs
Date: Fri, 26 Apr 2019 15:03:23 +0000 (UTC)	[thread overview]
Message-ID: <839224231.934433.1556291003955@mail.yahoo.com> (raw)
In-Reply-To: <fcb370dbba118382c6c4a1aa868a0aca1c072b2e.camel@gentoo.org>

 

On Thursday, April 25, 2019, 8:39:56 PM GMT+2, Michał Górny <mgorny@gentoo.org> wrote: 
>
> I'm sorry but we are simply overwhelmed with work.  For this reason,
> we're trying to focus on handling updates for existing packages first. 
> Sadly, this often takes all our time and there's none left for new
> packages.

OK, so I'll take your word for it. Here's a fix for a package that has been marked to be removed within 30 days:

https://github.com/gentoo/gentoo/pull/11833
Just kidding... I know you're overwhelmed. We're all here to pitch in.

This package is mail-filter/mimedefang. If it doesn't get unmarked for removal then it's really too bad. There might not be enough dev time for PR revision, but if there's one then at least the deadline should be removed, don't you think?

The other packages I was referring to were c-icap (https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=900eb89a8818963cf351d27df3e1d198409bf5b9) and squidclamav. Actually, they weren't "new" packages. They were removed because there weren't any PRs on github at the time and because Gentoo had rather old versions compared to upstream, right? However, there were patches/contributions in bugs.gentoo.org that were later moved to github, and the packages per-se weren't a security risk or had serious compilation issues. Am I wrong?
What I'm trying to say is that the definition of "new" here is fuzzy.

Anyway, I'd just like to say once again that if the contributors can do anything to help, please give out clear instructions (for rookies). We'll be more than happy to help.

Thanks,

Vieri



      reply	other threads:[~2019-04-26 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 22:45 [gentoo-proxy-maint] dev-libs/libaio: package up for grabs Gokturk Yuksek
2019-04-25  7:13 ` Vieri
2019-04-25  9:33   ` Dwosky
2019-04-25 18:39   ` Michał Górny
2019-04-26 15:03     ` Vieri [this message]

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=839224231.934433.1556291003955@mail.yahoo.com \
    --to=rentorbuy@yahoo.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-proxy-maint@lists.gentoo.org \
    --cc=gokturk@gentoo.org \
    --cc=mgorny@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