public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Fish <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] package conflict on update
Date: Thu, 5 Jan 2006 09:14:56 -0700	[thread overview]
Message-ID: <7573e9640601050814q583f3afds1de915a965e21fd7@mail.gmail.com> (raw)
In-Reply-To: <20060105160804.5274ec08@pohl.lj.net>

On 1/5/06, Tom Martin <slarti@gentoo.org> wrote:
> It would be more useful if some information was provided:
>
> if blocked_by >=x11-libs/openmotif-1.2.3 ; then
>         eblockinfo "Due to changes with blah, it is recommended that"
>         eblockinfo "you foobar. See http://bugs.gentoo.org/123456."
> fi

Sounds more like information that should be available in the coming
emerge --news system.

-Richard

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-01-05 16:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05  7:29 [gentoo-user] package conflict on update Trenton Adams
2006-01-05  7:32 ` [gentoo-user] " Trenton Adams
2006-01-05 11:10 ` [gentoo-user] " Tom Martin
2006-01-05 11:25   ` Trenton Adams
2006-01-05 11:35     ` Holly Bostick
2006-01-05 11:41   ` Neil Bothwick
2006-01-05 15:16     ` Devon Miller
2006-01-05 16:08     ` Tom Martin
2006-01-05 16:14       ` Richard Fish [this message]
2006-01-05 17:51       ` Neil Bothwick
2006-01-05 23:43         ` Trenton Adams
2006-01-05 23:54         ` Trenton Adams
2006-01-06  0:56           ` Richard Fish
2006-01-06  2:51             ` Trenton Adams
2006-01-05 23:32     ` Trenton Adams
2006-01-06  0:16       ` Neil Bothwick
2006-01-06  2:48         ` Trenton Adams
2006-01-07  2:00           ` Holly Bostick
2006-01-07  4:35             ` Trenton Adams
2006-01-07  5:13             ` Trenton Adams
2006-01-07 12:51               ` Holly Bostick
2006-01-07 16:33                 ` Trenton Adams
2006-01-07 14:16               ` Abhay Kedia
2006-01-07 16:30                 ` Trenton Adams
2006-01-07 19:17                   ` Abhay Kedia
2006-01-07 21:55                     ` Trenton Adams
2006-01-08  0:12                       ` Holly Bostick
2006-01-08  1:06                         ` Trenton Adams
2006-01-08  1:08                           ` Trenton Adams
2006-01-08  8:10                           ` Abhay Kedia
2006-01-08  8:27                             ` Trenton Adams
2006-01-08  8:49                               ` Abhay Kedia
2006-01-08  9:03                                 ` Trenton Adams
2006-01-08  9:23                                   ` Abhay Kedia
2006-01-08  9:58                                     ` Trenton Adams
2006-01-08  8:02                       ` Abhay Kedia
2006-01-08  8:23                         ` Trenton Adams
2006-01-08 15:14                           ` Ernie Schroder
2006-01-08 20:58                             ` Trenton Adams
2006-01-09  7:07                               ` Abhay Kedia
2006-01-10  3:21                                 ` Ernie Schroder
2006-01-06  1:14     ` Zac Medico
2006-01-06  7:27       ` Abhay Kedia
2006-01-06  9:09         ` Neil Bothwick
2006-01-06  9:13       ` Neil Bothwick
2006-01-07  4:55         ` Trenton Adams

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=7573e9640601050814q583f3afds1de915a965e21fd7@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@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