Hello Slavek, Thank you for your quick reply. It's much apreciated.

On Monday 30 March 2015 22:44:04 Slávek Banko wrote:

On Monday 30 of March 2015 23:38:41 Baron wrote:

...

Hello all,

Synaptic complains that I have three broken packages ! How do I identify them, and what do I need to do to fix them. Running Debian Jessie rc2.

See http://bugs.pearsoncomputing.net/show_bug.cgi?id=2406#c4

I should have added that my hardware is dual core P4 and 32 bit. I already have this line in Synaptic.

"http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14"

Since apart from the error message, there does not seem to be any problems, should I just leave it as is for the time being.

Hello,

On Tuesday 31 March 2015 11:34:34 midi-pascal wrote:

Hello,

If you want to know which packages are broken, you may try:

apt-get check

at the command prompt. It will give you the list.

midi-pascal

Thanks ! I didn't know that.

On 15-03-31 06:17 AM, Baron wrote:

...

Hello Slavek, Thank you for your quick reply. It's much apreciated.

On Monday 30 March 2015 22:44:04 Slávek Banko wrote:

...

On Monday 30 of March 2015 23:38:41 Baron wrote:

...

Hello all,

Synaptic complains that I have three broken packages ! How do I identify them, and what do I need to do to fix them. Running Debian Jessie rc2.

See http://bugs.pearsoncomputing.net/show_bug.cgi?id=2406#c4

I should have added that my hardware is dual core P4 and 32 bit. I already have this line in Synaptic.

"http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14"

Since apart from the error message, there does not seem to be any problems, should I just leave it as is for the time being.

On 15-03-31 10:49 AM, Baron wrote:

On Tuesday 31 March 2015 11:52:04 Baron wrote:

...

Hello,

On Tuesday 31 March 2015 11:34:34 midi-pascal wrote:

...

Hello,

If you want to know which packages are broken, you may try:

apt-get check

at the command prompt. It will give you the list.

midi-pascal

Thanks ! I didn't know that.

Unfortunately it tells me nothing ! Now is that good or bad ? Below is a copy & paste of the output from apt-get check.

root@linuxcastle:/home/baron# apt-get check Reading package lists... Done Building dependency tree Reading state information... Done

Thanks

Hello Baron,

An other way to find you broken packages is with the Synaptic Package Manager (which you are already using if I refer to your first mail on this thread) In Synaptic "Edit" menu, there is an option named "Fix broken packages". This option should show you what is going wrong.

Regards, midi-pascal

On 15-03-31 12:23 PM, Baron wrote:

Hi midi-pascal,

On Tuesday 31 March 2015 16:27:36 midi-pascal wrote:

...

On 15-03-31 10:49 AM, Baron wrote:

...

On Tuesday 31 March 2015 11:52:04 Baron wrote:

...

Hello,

On Tuesday 31 March 2015 11:34:34 midi-pascal wrote:

...

Hello,

If you want to know which packages are broken, you may try:

apt-get check

at the command prompt. It will give you the list.

midi-pascal

Thanks ! I didn't know that.

Unfortunately it tells me nothing ! Now is that good or bad ? Below is a copy & paste of the output from apt-get check.

root@linuxcastle:/home/baron# apt-get check Reading package lists... Done Building dependency tree Reading state information... Done

Thanks

Hello Baron,

An other way to find you broken packages is with the Synaptic Package Manager (which you are already using if I refer to your first mail on this thread) In Synaptic "Edit" menu, there is an option named "Fix broken packages". This option should show you what is going wrong.

Regards, midi-pascal

I hadn't found that option. Thanks for pointing it out.

I clicked on it and got "Successfully fixed dependency problems!"

Problem solved. :-) Thanks for your help.

Glad to know I could help :-)

Kind regards, midi-pascal