From: Svyatogor <svyatogor@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] getting sus-2.0.1 marked stable
Date: Fri, 1 Aug 2003 22:37:47 +0300 [thread overview]
Message-ID: <20030801223747.25a2f92e.svyatogor@gentoo.org> (raw)
In-Reply-To: <20030801175719.GA19260@kc5eiv.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Fri, 1 Aug 2003 12:57:19 -0500
William Hubbs <kc5eiv@kc5eiv.homeip.net> wrote:
> Hi all,
>
> I'm not sure if this question should go here or to gentoo-user, so if it should go there let me know and I'll refer it there.
>
> I submitted an ebuild for sus-2.0.1, a program similar to sudo, a few weeks ago. It was added to the tree and marked testing. I have been using it and had not problems with it.
>
> What is the procedure for getting it marked stable?
Usually we mark ebuilds stable after they've been in portage for a month with no bugs reported. So it would make sense if before filing bug with request to make it stable, you check if there are any open bugs for it. If there isn't, then (generally) there shouldn't be any problem with changing ~ARCH to ARCH. Everything else is up to the maintainer of the package.
--
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-08-01 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 17:57 [gentoo-dev] getting sus-2.0.1 marked stable William Hubbs
2003-08-01 18:31 ` Kumba
2003-08-01 21:22 ` George Shapovalov
2003-08-01 19:37 ` Svyatogor [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=20030801223747.25a2f92e.svyatogor@gentoo.org \
--to=svyatogor@gentoo.org \
--cc=gentoo-dev@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