On Tue, Apr 25, 2006 at 09:42:44AM +0930, Ian Moore wrote:
> So to sum up, it's a problem with the way the ports system detects wether the
> mysql-client port is installed that caused the problem (I thought it just
> used the ports database), and/or it's a problem with the mysql-client port
> no
On Monday 24 April 2006 23:56, Matthew Seaman wrote:
> Ian Moore wrote:
> > Hi, I've got a question about portupgrade and something that's happened
> > with it a couple of times now. The last 2 times libgda has been upgraded,
> > I've run portupgrade -a to upgrade a bunch of ports, including libgda
On Monday 24 April 2006 21:29, Garrett Cooper wrote:
> RW wrote:
> >On Monday 24 April 2006 12:50, Richard Collyer wrote:
> >>On Mon, April 24, 2006 12:16 pm, Ian Moore wrote:
> >>>On Monday 24 April 2006 20:43, Ian Moore wrote:
> Hi, I've got a question about portupgrade and something that's h
Ian Moore wrote:
On Monday 24 April 2006 22:38, Kevin Kinsey wrote:
Ian Moore wrote:
Yes, that would fix the problem, but I'm just curious about what causes
the problem in the first place, given that portupgrade rarely seems to
have these kind of problems.
Cheers,
ls -l /var/d
RW wrote:
On Monday 24 April 2006 12:50, Richard Collyer wrote:
On Mon, April 24, 2006 12:16 pm, Ian Moore wrote:
On Monday 24 April 2006 20:43, Ian Moore wrote:
Hi, I've got a question about portupgrade and something that's happened
with it a couple of times now. The last 2 ti
On Monday 24 April 2006 12:50, Richard Collyer wrote:
> On Mon, April 24, 2006 12:16 pm, Ian Moore wrote:
> > On Monday 24 April 2006 20:43, Ian Moore wrote:
> >> Hi, I've got a question about portupgrade and something that's happened
> >> with it a couple of times now. The last 2 times libgda has
Ian Moore wrote:
> Hi, I've got a question about portupgrade and something that's happened with
> it a couple of times now. The last 2 times libgda has been upgraded, I've run
> portupgrade -a to upgrade a bunch of ports, including libgda.
>
> The libgda upgrade has caused a re-install of mysql
On Monday 24 April 2006 22:38, Kevin Kinsey wrote:
> Ian Moore wrote:
> >Yes, that would fix the problem, but I'm just curious about what causes
> > the problem in the first place, given that portupgrade rarely seems to
> > have these kind of problems.
> >
> >Cheers,
>
> ls -l /var/db/pkg/mysql-cli
Ian Moore wrote:
Yes, that would fix the problem, but I'm just curious about what causes the
problem in the first place, given that portupgrade rarely seems to have these
kind of problems.
Cheers,
ls -l /var/db/pkg/mysql-client*??
Kevin Kinsey
--
A method of solution is perfect if
I have:
FORCE_PKG_REGISTER=YES
in /etc/make.conf
for portupgrade or if I need to re-install a port manually.
-Derek
At 06:16 AM 4/24/2006, Ian Moore wrote:
On Monday 24 April 2006 20:43, Ian Moore wrote:
> Hi, I've got a question about portupgrade and something that's happened
> w
On Monday 24 April 2006 21:20, Richard Collyer wrote:
> On Mon, April 24, 2006 12:16 pm, Ian Moore wrote:
> >> Hi, I've got a question about portupgrade and something that's happened
> >> with it a couple of times now. The last 2 times libgda has been
> >> upgraded,
> >> I've run portupgrade -a to
On Mon, April 24, 2006 12:16 pm, Ian Moore wrote:
> On Monday 24 April 2006 20:43, Ian Moore wrote:
>> Hi, I've got a question about portupgrade and something that's happened
>> with it a couple of times now. The last 2 times libgda has been
>> upgraded,
>> I've run portupgrade -a to upgrade a bun
On Monday 24 April 2006 20:43, Ian Moore wrote:
> Hi, I've got a question about portupgrade and something that's happened
> with it a couple of times now. The last 2 times libgda has been upgraded,
> I've run portupgrade -a to upgrade a bunch of ports, including libgda.
>
Sorry, I forgot to add the
13 matches
Mail list logo
