Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

"Dominic Reich" mailto:domi...@mm.st>> wrote:

> You should be able to print without any additional software (except the 
> driver that macOS retrieves from its Servers). But you won't need any 
> package from MacPorts for printing.
> 
> Besides that, postgresql83-server is a database. You won't need a 
> database to print stuff.

This is going to be long, boring and somewhat irrelevant. If you’re busy, move 
on to the next thread.

Bottom line is that when you have an old, ignorant and naive person like me 
trying to use something like MacPorts, this stuff is going to happen.

Let’s examine the timeline.

On Tuesday morning the first thing I did was print a mailing label I needed to 
return a failed disk drive to Western Digital for warranty replacement. That 
print job executed without issue.

The next thing I did was to update MacPorts. That’s when I got the error 
message on postgresql83. After exchanging a few messages with other members of 
this list I decided to delete postgresql83. That was sometime after lunch. 
After that I didn’t do anything on the iMac. I watched some TV, read a novel, 
worked in the garden, had a beer for happy hour and ate dinner. (I’m retired.)

The next morning the first thing I did was try to print something. I’m both 
surprised and shocked that the print system has simply disappeared. In my mind 
I associate the last thing I did on Tuesday (delete postgresql83) with the 
first thing I tried to do on Wednesday morning (print something). So I assume 
(wrongly, I guess) that deleting postgresql83 had something to do with the 
disappearance of the printing system. What else could it have been? I’m the 
only one who uses this computer and I didn’t do anything between deleting 
postgresql83 on Tuesday afternoon and trying to print something on Wednesday 
morning.

Anyway, I apologize for the error. As always, I appreciate the help and advice 
I receive here.

Mike Newman
Korat, Thailand

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Dominic Reich]

On 23 Oct 2019, at 8:04, Michael Newman wrote:

>> On Oct 22, 2019, at 16:00, Ryan Schmidt > wrote:


Yes, looks like nothing depended on postgresql83-server.


Except the Mac printing system.


I managed to get the printers back by resetting the printer system.


You should be able to print without any additional software (except the 
driver that macOS retrieves from its Servers). But you won't need any 
package from MacPorts for printing.


Besides that, postgresql83-server is a database. You won't need a 
database to print stuff.

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

>> On Oct 22, 2019, at 16:00, Ryan Schmidt > > wrote:
>>> 
>>> Yes, looks like nothing depended on postgresql83-server.
> 
> Except the Mac printing system.

I managed to get the printers back by resetting the printer system.

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 16:00, Ryan Schmidt  > wrote:
>> 
>> Yes, looks like nothing depended on postgresql83-server.

Except the Mac printing system.

After deleting postgresql83-server I can no longer print.

My printer has disappeared from the "Printers & Scanners System" Preferences 
and when I try to add the printer again, all the printer drivers have 
disappeared.

It’s hard for me to understand how the Mac printing system could depend on a 
database server installed via MacPorts, but it appears that’s the case.

I tried to reinstall postgresql83, but that failed with the same error that 
started this thread: Error: Failed to configure postgresql83: configure 
failure: command execution failed

Any ideas as to how to fix this?

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

On Oct 22, 2019, at 16:00, Ryan Schmidt  wrote:
> 
> Yes, looks like nothing depended on postgresql83-server.
> 
> 
>> Any way of finding out why this got installed in the first place? It didn't 
>> seem to have any dependencies, so why was it there?
> 
> It was installed either because you requested that it be installed, or 
> because some other port that you installed depended on it at one time.
> 
> You can see the ports that you directly requested to be installed using:
> 
> port installed requested
> 
> If the list is inaccurate (if ports are listed that you don't specifically 
> want), you can unmark them using:
> 
> sudo port unsetrequested thePortName
> 
> You can remove ports that you did not request and that are no longer needed 
> by other ports, as well as perform other cleanup activities, by running:
> 
> sudo port reclaim

Thank you very much for your help. I appreciate your taking the time to explain 
things so clearly.

Mike

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Ryan Schmidt]

Remember to Reply All so the conversation stays on the list.


On Oct 22, 2019, at 02:39, Michael Newman wrote:
> On Oct 22, 2019, at 13:51, Ryan Schmidt wrote:
> 
>> Ok, so there were two versions of postgresql83 installed. You told MacPorts 
>> to uninstall them both, MacPorts told you this would break the 
>> postgresql83-server port, and you indicated that was ok, so it proceeded and 
>> uninstalled them.
>> 
>> You should now also uninstall the postgresql83-server port, since it's now 
>> broken due to its dependency having been uninstalled and since you 
>> presumably don't need it either.
> 
> All done, I guess:
> 
> MrMuscle:~ mnewman$ sudo port uninstall postgresql83-server
> Password:
> --->  Deactivating postgresql83-server @8.3.23_0
> --->  Cleaning postgresql83-server
> --->  Uninstalling postgresql83-server @8.3.23_0
> --->  Cleaning postgresql83-server

Yes, looks like nothing depended on postgresql83-server.


> Any way of finding out why this got installed in the first place? It didn't 
> seem to have any dependencies, so why was it there?

It was installed either because you requested that it be installed, or because 
some other port that you installed depended on it at one time.

You can see the ports that you directly requested to be installed using:

port installed requested

If the list is inaccurate (if ports are listed that you don't specifically 
want), you can unmark them using:

sudo port unsetrequested thePortName

You can remove ports that you did not request and that are no longer needed by 
other ports, as well as perform other cleanup activities, by running:

sudo port reclaim

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Ryan Schmidt]

On Oct 22, 2019, at 01:48, Michael Newman wrote:

>> PostgreSQL is a database server. If you don't think you need it (or any 
>> port), try uninstalling it. ("sudo port uninstall postgresql83"). MacPorts 
>> will either let you uninstall it, or it will tell that uninstalling it will 
>> break some other port. If it does the latter, look at the variants of the 
>> other port ("port variants theOtherPortsName") and see if there is a variant 
>> for using a newer postgresql instead. If so, reinstall the port using that 
>> other variant. ("sudo port install theOtherPortsName +postgresql12" for 
>> example.) If not, let us know what the other port is.
> 
> Did I do the right thing?
> 
> MrMuscle:~ mnewman$ sudo port uninstall postgresql83
> Password:
> The following versions of postgresql83 are currently installed:
> 1) postgresql83 @8.3.23_2
> 2) postgresql83 @8.3.23_3 (active)
> Enter option(s) [1-2/all]: all
> --->  Uninstalling postgresql83 @8.3.23_2
> Note: It is not recommended to uninstall/deactivate a port that has 
> dependents as it breaks the dependents.
> The following ports will break: postgresql83-server @8.3.23_0
> Continue? [y/N]: y
> Warning: Uninstall forced.  Proceeding despite dependencies.
> --->  Deactivating postgresql83 @8.3.23_3
> --->  Cleaning postgresql83
> --->  Uninstalling postgresql83 @8.3.23_3

Ok, so there were two versions of postgresql83 installed. You told MacPorts to 
uninstall them both, MacPorts told you this would break the postgresql83-server 
port, and you indicated that was ok, so it proceeded and uninstalled them.

You should now also uninstall the postgresql83-server port, since it's now 
broken due to its dependency having been uninstalled and since you presumably 
don't need it either.

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 13:45, Ryan Schmidt  wrote:
> 
> 
> 
> On Oct 22, 2019, at 00:50, Michael Newman wrote:
> 
>>> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote:
>>> 
 Michael Newman kirjoitti 22.10.2019 kello 7.19:
 
 I have no idea. I don’t even know what it is. It must have been installed 
 by some other port that I requested.
>>> 
>>> Hi,
>>> can you find out, what it was you requested. I looked at the port 
>>> collection and found some that are not actively maintained at the moment 
>>> depending on too old versions of postgres. If you can find that, I can try 
>>> to update that port. Then, it will take a few moments, especially if the 
>>> port is otherwise outdated.
>> 
>> How would I find out? I got this error message for the first time after 
>> updating to the most recent MacPorts release. I haven’t installed anything 
>> new in quite some time. 
> 
> PostgreSQL is a database server. If you don't think you need it (or any 
> port), try uninstalling it. ("sudo port uninstall postgresql83"). MacPorts 
> will either let you uninstall it, or it will tell that uninstalling it will 
> break some other port. If it does the latter, look at the variants of the 
> other port ("port variants theOtherPortsName") and see if there is a variant 
> for using a newer postgresql instead. If so, reinstall the port using that 
> other variant. ("sudo port install theOtherPortsName +postgresql12" for 
> example.) If not, let us know what the other port is.

Did I do the right thing?

MrMuscle:~ mnewman$ sudo port uninstall postgresql83
Password:
The following versions of postgresql83 are currently installed:
 1) postgresql83 @8.3.23_2
 2) postgresql83 @8.3.23_3 (active)
Enter option(s) [1-2/all]: all
--->  Uninstalling postgresql83 @8.3.23_2
Note: It is not recommended to uninstall/deactivate a port that has dependents 
as it breaks the dependents.
The following ports will break: postgresql83-server @8.3.23_0
Continue? [y/N]: y
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating postgresql83 @8.3.23_3
--->  Cleaning postgresql83
--->  Uninstalling postgresql83 @8.3.23_3

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Ryan Schmidt]

On Oct 22, 2019, at 00:50, Michael Newman wrote:

>> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote:
>> 
>>> Michael Newman kirjoitti 22.10.2019 kello 7.19:
>>> 
>>> I have no idea. I don’t even know what it is. It must have been installed 
>>> by some other port that I requested.
>> 
>> Hi,
>> can you find out, what it was you requested. I looked at the port collection 
>> and found some that are not actively maintained at the moment depending on 
>> too old versions of postgres. If you can find that, I can try to update that 
>> port. Then, it will take a few moments, especially if the port is otherwise 
>> outdated.
> 
> How would I find out? I got this error message for the first time after 
> updating to the most recent MacPorts release. I haven’t installed anything 
> new in quite some time. 

PostgreSQL is a database server. If you don't think you need it (or any port), 
try uninstalling it. ("sudo port uninstall postgresql83"). MacPorts will either 
let you uninstall it, or it will tell that uninstalling it will break some 
other port. If it does the latter, look at the variants of the other port 
("port variants theOtherPortsName") and see if there is a variant for using a 
newer postgresql instead. If so, reinstall the port using that other variant. 
("sudo port install theOtherPortsName +postgresql12" for example.) If not, let 
us know what the other port is.

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki  wrote:
> 
>> Michael Newman  kirjoitti 22.10.2019 kello 7.19:
>> 
>> I have no idea. I don’t even know what it is. It must have been installed by 
>> some other port that I requested.
> 
> Hi,
> can you find out, what it was you requested. I looked at the port collection 
> and found some that are not actively maintained at the moment depending on 
> too old versions of postgres. If you can find that, I can try to update that 
> port. Then, it will take a few moments, especially if the port is otherwise 
> outdated.

How would I find out? I got this error message for the first time after 
updating to the most recent MacPorts release. I haven’t installed anything new 
in quite some time. 

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Wahlstedt Jyrki]

> Michael Newman  kirjoitti 22.10.2019 kello 7.19:
> 
> I have no idea. I don’t even know what it is. It must have been installed by 
> some other port that I requested.

Hi,
can you find out, what it was you requested. I looked at the port collection 
and found some that are not actively maintained at the moment depending on too 
old versions of postgres. If you can find that, I can try to update that port. 
Then, it will take a few moments, especially if the port is otherwise outdated.


!
! Jyrki

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

> On Oct 22, 2019, at 11:06, Wahlstedt Jyrki  wrote:
> 
> Hi,
> just being curious, why postgresql83? It was EOL’d several years ago, so it 
> is obsolete. If you want PostgreSQL, the current version is postgresql12.

I have no idea. I don’t even know what it is. It must have been installed by 
some other port that I requested. 

Re: MacPorts 2.6.2: Failed to configure postgresql83

[Wahlstedt Jyrki]

> Michael Newman via macports-users  
> kirjoitti 22.10.2019 kello 2.40:
> 
> I have no idea what to do about this. The error message includes:
> 
> Error: Failed to configure postgresql83, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/work/postgresql-8.3.23/config.log
> Error: Failed to configure postgresql83: configure failure: command execution 
> failed
> Error: See 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/main.log
>  for details.
> 
> I looked at the log files referred to, but they are way above my ability 
> level.
> 
> 
Hi,
just being curious, why postgresql83? It was EOL’d several years ago, so it is 
obsolete. If you want PostgreSQL, the current version is postgresql12.


!
! Jyrki

MacPorts 2.6.2: Failed to configure postgresql83

[Michael Newman via macports-users]

I have no idea what to do about this. The error message includes:

Error: Failed to configure postgresql83, consult 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/work/postgresql-8.3.23/config.log
Error: Failed to configure postgresql83: configure failure: command execution 
failed
Error: See 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/main.log
 for details.

I looked at the log files referred to, but they are way above my ability level.