From: Brian Friday <bfriday@lasierra.edu>
To: Daniel Robbins <drobbins@gentoo.org>
Cc: "Brett I.Holcomb" <brettholcomb@charter.net>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] xfce4-session ebuild problem
Date: Fri, 17 Oct 2003 14:19:52 -0700 [thread overview]
Message-ID: <3F905CF8.2040402@lasierra.edu> (raw)
In-Reply-To: <1066370641.16395.47.camel@ht.gentoo.org>
Hi all,
I'd vote to unmask it, as I and a colleague here at work
have had it running since September 30ish using the official
release of 4 without a problem. Without knowing more about
the RC breakage I can't be sure it won't break for others
but in daily use I've not had problems (bugs doesn't return
any submission relating to xfce4-session).
my lurking 2cents
- Brian
Daniel Robbins wrote:
>
> I unmasked it on amd64, but it was masked on everything before.
> According to the ChangeLog, apparently it conflicted with the xfce4
> beta. Not sure if it should be unmasked or if I should re-mask on amd64,
> so cc'ing bcowan on this for more info.
>
> Regards,
>
> Daniel
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-10-17 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 2:20 [gentoo-dev] xfce4-session ebuild problem Brett I. Holcomb
2003-10-17 6:04 ` Daniel Robbins
2003-10-17 21:19 ` Brian Friday [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=3F905CF8.2040402@lasierra.edu \
--to=bfriday@lasierra.edu \
--cc=brettholcomb@charter.net \
--cc=drobbins@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