Re: Weirdness with two packages.........

2016-11-28 Thread The Wanderer
On 2016-11-28 at 07:40, Charlie wrote:

> On Mon, 28 Nov 2016 07:22:23 -0500 The Wanderer sent:
> 
>> My best guess is that at some point, you installed some package from a
>> different repository, which depended on these higher-epoch package
>> versions, and thus got them upgraded without upgrading the rest of
>> your libav* package ecosystem.
> 
>   After contemplation, my reply is:
> 
> You may be right.
> 
> I might have used a different mirror, but Chromium and Goldendict
> worked last week. I didn't need to change the mirror just before or
> after that? Will see how I go with removing these that are giving me
> problems and see where I go from there.

Most likely, in the meantime a new version of the lower-epoch libav*
package(s) became available, you upgraded to that new version, and that
new version introduced a symbols mismatch against the higher-epoch ones.

> Thank you again for your help. It's very much appreciated.

You're quite welcome.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Weirdness with two packages.........

2016-11-28 Thread Charlie
On Mon, 28 Nov 2016 07:22:23 -0500 The Wanderer sent:

> My best guess is that at some point, you installed some package from a
> different repository, which depended on these higher-epoch package
> versions, and thus got them upgraded without upgrading the rest of
> your libav* package ecosystem.

After contemplation, my reply is:

You may be right.

I might have used a different mirror, but Chromium and Goldendict
worked last week. I didn't need to change the mirror just before or
after that? Will see how I go with removing these that are giving me
problems and see where I go from there.

Thank you again for your help. It's very much appreciated.

Stay well,
Charlie

-- 
Registered Linux User:- 329524
***

The Great Way is not difficult for those who have no
preferences. --Sengstan Third Zen Patriarch

***

Debian GNU/Linux - Magic indeed.

-



Re: Weirdness with two packages.........

2016-11-28 Thread The Wanderer
On 2016-11-28 at 07:27, Charlie wrote:

> On Mon, 28 Nov 2016 00:19:38 -0500 The Wanderer sent:
> 
>> This is almost certainly your problem. The version of libavutil which
>> you have is from a different source, with a higher epoch version but a
>> lower upstream version, and is no longer available from your selected
>> repositories. In particular, it is not the same version as your other
>> libav* libraries (as the snipped version information for libavformat
>> indicates), and that mismatch is probably the source of the problem.
> 
>   After contemplation, my reply is:
> 
> Further to this:
> 
> I have another machine:
> 
> Linux taogypsy 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64
> GNU/Linux
> 
> This has:
> 
> $ apt-cache policy libavformat57
> libavformat57:
>   Installed: 10:3.1.1-dmo2
>   Candidate: 10:3.1.1-dmo2
>   Version table:
>  *** 10:3.1.1-dmo2 100
> 100 /var/lib/dpkg/status
>  7:3.2-2 500
> 500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
> 
> So attempted to look for that with the machine that is:
> 
> In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
>   (2015-08-04) x86_64 GNU/Linux
> 
> Attempting to install that - Produced the error code:
> 
> # apt-get install libavformat57=10:3.1.1-dmo2
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> E: Version '10:3.1.1-dmo2' for 'libavformat57' was not found

That's not a surprise.

The location source '/var/lib/dpkg/status' indicates that that version
of the package is found in the list of installed packages on your
machine, rather than in a package list from an upstream repository. (For
most packages, you will see _two_ location source lines under the
installed version: one from /var/lib/dpkg/status, and the other from a
configured repository.)

Since the list of installed packages on your machine doesn't include an
indication of where to obtain the .deb file for installation, apt-get
can't find the file it needs to carry out the install, so it can't proceed.

That said, the .deb file in question is probably located on the machine
where the package _is_ installed, under /var/cache/apt/archives/ - but
there will almost certainly be a _lot_ of .deb files there, and sorting
through them may be confusing.

I would recommend that you either proceed with downgrading all of the
libav* packages (which includes libswsample*) - probably on both
machines - or figure out what repository you got them from, re-enable
it, and see how you can proceed from there.

In the latter vein, you might find it worthwhile to check
/etc/apt/sources.list and see whether you have any commented-out
repositories.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Weirdness with two packages.........

2016-11-28 Thread Charlie
On Mon, 28 Nov 2016 00:19:38 -0500 The Wanderer sent:

> This is almost certainly your problem. The version of libavutil which
> you have is from a different source, with a higher epoch version but a
> lower upstream version, and is no longer available from your selected
> repositories. In particular, it is not the same version as your other
> libav* libraries (as the snipped version information for libavformat
> indicates), and that mismatch is probably the source of the problem.

After contemplation, my reply is:

Further to this:

I have another machine:

Linux taogypsy 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64
GNU/Linux

This has:

$ apt-cache policy libavformat57
libavformat57:
  Installed: 10:3.1.1-dmo2
  Candidate: 10:3.1.1-dmo2
  Version table:
 *** 10:3.1.1-dmo2 100
100 /var/lib/dpkg/status
 7:3.2-2 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages

So attempted to look for that with the machine that is:

In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
(2015-08-04) x86_64 GNU/Linux

Attempting to install that - Produced the error code:

# apt-get install libavformat57=10:3.1.1-dmo2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Version '10:3.1.1-dmo2' for 'libavformat57' was not found

Thanks again for your help.

Charlie

-- 
Registered Linux User:- 329524
***

However mean your life is, meet it and live it; do not shun it
and call it hard names. It is not so bad as you are. It looks
poorest when you are the richest. -Henry David Thoreau

***

Debian GNU/Linux - Magic indeed.

-



Re: Weirdness with two packages.........

2016-11-28 Thread The Wanderer
On 2016-11-28 at 01:10, Charlie wrote:

> On Mon, 28 Nov 2016 00:19:38 -0500 The Wanderer sent:
> 
> 
> 
>> I have - different from your own:
>>> 
>>> $ apt-cache policy libavutil55
>>> libavutil55:
>>>   Installed: 10:3.1.2-dmo2
>>>   Candidate: 10:3.1.2-dmo2
>>>   Version table:
>>>  *** 10:3.1.2-dmo2 100
>>> 100 /var/lib/dpkg/status
>>>  7:3.2-2 500
>>> 500 http://ftp.us.debian.org/debian stretch/main amd64
>>> Packages  
>> 
>> This is almost certainly your problem. The version of libavutil which
>> you have is from a different source, with a higher epoch version but a
>> lower upstream version, and is no longer available from your selected
>> repositories. In particular, it is not the same version as your other
>> libav* libraries (as the snipped version information for libavformat
>> indicates), and that mismatch is probably the source of the problem.
>> 
>> Do you have any idea how this mismatched package version may have come
>> about?
>> 
>> I recommend that you explicitly install the "lower" version listed
>> here (7:3.2-2), and see if your problem goes away.
>> 
>> I don't know what tools you normally use for package installation and
>> upgrade, but I would do that with the following command (in a root
>> terminal):
>> 
>> apt-get install libavutil55=7:3.2-2
> 
>   After contemplation, my reply is:
> 
> I'm on a different machine now, at a different place when sending this.
> 
> I only ever use apt-get for updates, upgrades, installs and purges.
> 
> But before I left that machine I attempted your excellent suggestion
> and received this error message:
> 
> The following packages have unmet dependencies:
>  libswresample2 : Depends: libavutil55 (>= 10:3.1.2) but 7:3.2-2 is to
> be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
> 
> I assume that I might have missed a bug report on a update/upgrade? So
> I will just have to purge libswresample2, and libavutil55 (>= 10:3.1.2)

Actually, it looks like libswresample2 has the same problem: the
installed version has a higher epoch but lower actual version.

My best guess is that at some point, you installed some package from a
different repository, which depended on these higher-epoch package
versions, and thus got them upgraded without upgrading the rest of your
libav* package ecosystem.

I would just add libswresample2 to your explicit-version install
command, and see what result you get. It may give further
unmet-dependencies errors; if you pursue the cascade far enough (I'd
advise checking each new package with 'apt-cache policy' to see
available versions before proceeding), you may be able to identify the
package(s) which depend or depended on the higher-epoch libav* packages
to begin with.

(Purging the libav* packages will probably result in trying to uninstall
various packages which depend on them, possibly including quite a few
things you may actually want. Although you could always do that and
reinstall the appropriate packages afterwards, "down"grading is almost
certainly the superior solution.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Weirdness with two packages.........

2016-11-27 Thread Charlie
On Mon, 28 Nov 2016 00:19:38 -0500 The Wanderer sent:



>  I have - different from your own:
> > 
> > $ apt-cache policy libavutil55
> > libavutil55:
> >   Installed: 10:3.1.2-dmo2
> >   Candidate: 10:3.1.2-dmo2
> >   Version table:
> >  *** 10:3.1.2-dmo2 100
> > 100 /var/lib/dpkg/status
> >  7:3.2-2 500
> > 500 http://ftp.us.debian.org/debian stretch/main amd64
> > Packages  
> 
> This is almost certainly your problem. The version of libavutil which
> you have is from a different source, with a higher epoch version but a
> lower upstream version, and is no longer available from your selected
> repositories. In particular, it is not the same version as your other
> libav* libraries (as the snipped version information for libavformat
> indicates), and that mismatch is probably the source of the problem.
> 
> Do you have any idea how this mismatched package version may have come
> about?
> 
> I recommend that you explicitly install the "lower" version listed
> here (7:3.2-2), and see if your problem goes away.
> 
> I don't know what tools you normally use for package installation and
> upgrade, but I would do that with the following command (in a root
> terminal):
> 
> apt-get install libavutil55=7:3.2-2


After contemplation, my reply is:

I'm on a different machine now, at a different place when sending this.

I only ever use apt-get for updates, upgrades, installs and purges.

But before I left that machine I attempted your excellent suggestion
and received this error message:

The following packages have unmet dependencies:
 libswresample2 : Depends: libavutil55 (>= 10:3.1.2) but 7:3.2-2 is to
be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.

I assume that I might have missed a bug report on a update/upgrade? So
I will just have to purge libswresample2, and libavutil55 (>= 10:3.1.2)

Thank you for your help.
Charlie

-- 
Registered Linux User:- 329524
***

If you argue for your limitations, you get to keep
them. .Richard Bach

***

Debian GNU/Linux - Magic indeed.

-



Re: Weirdness with two packages.........

2016-11-27 Thread The Wanderer
On 2016-11-27 at 22:14, Charlie wrote:

> The sent: Re: Weirdness with two packages.
> 
> Wrote this:
>   >On 2016-11-27 at 18:57, Charles Schroeder wrote:
>>
>>> Hello Everyone,
>>> 
>>> In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
>>> (2015-08-04) x86_64 GNU/Linux
>>> 
>>> I get this message when I attempt to use Chromium:
>>> 
>>> $ chromium
>>> /usr/lib/chromium/chromium: relocation
>>> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
>>> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
>>> libavutil.so.55 with link time reference
>>> 
>>> Much the same when I attempt to use goldendict:
>>> 
>>> $ goldendict
>>> goldendict: relocation
>>> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
>>> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
>>> libavutil.so.55 with link time reference
>>> 
>>> I have no idea what is happening here or how I work round it?
>>> 
>>> I can't find those files in my: /usr/lib/x86_64-linux-gnu/
>>> directory?  
>>
>>They should be there, not as files, but as symlinks.
>>
>>> Trying to install both those packages tells me they are "already
>>> the newest version" so nothing to install?
>>> 
>>> Update, upgrade and reboot doesn't fix it.  
>>
>>What versions are those packages at, according to e.g. 'apt-cache
>>policy [packagename]'?
>>
>>What about the libavutil55 and libavformat57 packages?
>>
>>I have:

>>$ apt-cache policy libavutil55
>>libavutil55:
>>  Installed: 7:3.2-2
>>  Candidate: 7:3.2-2
>>  Version table:
>> *** 7:3.2-2 500
>>500 http://ftp.us.debian.org/debian testing/main amd64 Packages
>>100 /var/lib/dpkg/status
> 
> I have - different from your own:
> 
> $ apt-cache policy libavutil55
> libavutil55:
>   Installed: 10:3.1.2-dmo2
>   Candidate: 10:3.1.2-dmo2
>   Version table:
>  *** 10:3.1.2-dmo2 100
> 100 /var/lib/dpkg/status
>  7:3.2-2 500
> 500 http://ftp.us.debian.org/debian stretch/main amd64 Packages

This is almost certainly your problem. The version of libavutil which
you have is from a different source, with a higher epoch version but a
lower upstream version, and is no longer available from your selected
repositories. In particular, it is not the same version as your other
libav* libraries (as the snipped version information for libavformat
indicates), and that mismatch is probably the source of the problem.

Do you have any idea how this mismatched package version may have come
about?

I recommend that you explicitly install the "lower" version listed here
(7:3.2-2), and see if your problem goes away.

I don't know what tools you normally use for package installation and
upgrade, but I would do that with the following command (in a root
terminal):

apt-get install libavutil55=7:3.2-2

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Weirdness with two packages.........

2016-11-27 Thread Charlie


From my keyboard

The sent: Re: Weirdness with two packages.

Wrote this:
  >On 2016-11-27 at 18:57, Charles Schroeder wrote:
>
>> Hello Everyone,
>> 
>>  In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
>>  (2015-08-04) x86_64 GNU/Linux
>> 
>> I get this message when I attempt to use Chromium:
>> 
>> $ chromium
>> /usr/lib/chromium/chromium: relocation
>> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
>> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
>> libavutil.so.55 with link time reference
>> 
>> Much the same when I attempt to use goldendict:
>> 
>> $ goldendict
>> goldendict: relocation
>> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
>> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
>> libavutil.so.55 with link time reference
>> 
>> I have no idea what is happening here or how I work round it?
>> 
>> I can't find those files in my: /usr/lib/x86_64-linux-gnu/
>> directory?  
>
>They should be there, not as files, but as symlinks.
>
>> Trying to install both those packages tells me they are "already
>> the newest version" so nothing to install?
>> 
>> Update, upgrade and reboot doesn't fix it.  
>
>What versions are those packages at, according to e.g. 'apt-cache
>policy [packagename]'?
>
>What about the libavutil55 and libavformat57 packages?
>
>I have:
>
>$ apt-cache policy chromium
>chromium:
>  Installed: 53.0.2785.143-1
>  Candidate: 53.0.2785.143-1
>  Version table:
> *** 53.0.2785.143-1 500
>500 http://ftp.us.debian.org/debian testing/main amd64 Packages
>100 /var/lib/dpkg/status
> 53.0.2785.143-1~deb8u1 500
>500 http://security.debian.org stable/updates/main amd64
> Packages 53.0.2785.89-1~deb8u1 500
>500 http://ftp.us.debian.org/debian stable/main amd64 Packages

I have:

$ apt-cache policy chromium
chromium:
  Installed: 53.0.2785.143-1
  Candidate: 53.0.2785.143-1
  Version table:
 *** 53.0.2785.143-1 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

>
>$ apt-cache policy libavutil55
>libavutil55:
>  Installed: 7:3.2-2
>  Candidate: 7:3.2-2
>  Version table:
> *** 7:3.2-2 500
>500 http://ftp.us.debian.org/debian testing/main amd64 Packages
>100 /var/lib/dpkg/status

I have - different from your own:

$ apt-cache policy libavutil55
libavutil55:
  Installed: 10:3.1.2-dmo2
  Candidate: 10:3.1.2-dmo2
  Version table:
 *** 10:3.1.2-dmo2 100
100 /var/lib/dpkg/status
 7:3.2-2 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages

>
>$ apt-cache policy libavformat57
>libavformat57:
>  Installed: 7:3.2-2
>  Candidate: 7:3.2-2
>  Version table:
> *** 7:3.2-2 500
>500 http://ftp.us.debian.org/debian testing/main amd64 Packages
>100 /var/lib/dpkg/status

I have:

$ apt-cache policy libavformat57
libavformat57:
  Installed: 7:3.2-2
  Candidate: 7:3.2-2
  Version table:
 *** 7:3.2-2 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status

>
>and I don't have goldendict installed.

~$ apt-cache policy goldendict
goldendict:
  Installed: 1.5.0~git20160508.g92b5485-1.1
  Candidate: 1.5.0~git20160508.g92b5485-1.1
  Version table:
 *** 1.5.0~git20160508.g92b5485-1.1 500
500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status
>
>When I launch chromium from a terminal, I don't get the error you
>report. (I do get a different message, but it looks like "normal"
>Chromium console spam; I'm not sure I've ever had a nontrivial Chromium
>session with no console messages.)
>
>-- 
>   The Wanderer
>
>The reasonable man adapts himself to the world; the unreasonable one
>persists in trying to adapt the world to himself. Therefore all
>progress depends on the unreasonable man. -- George Bernard
>Shaw
>
 
Thank you for your reply.

Charlie





http://www.egwildlife.com.au/

-- 
Registered Linux User:- 329524
***

Let each one turn his gaze inward and regard himself with awe
and wonder, with mystery and reverence; let each one work his
own influence, his own havoc, his own miracles. ---Henry
Miller

***

Debian GNU/Linux - just the best way to create magic

-


Am sending this through webmail.




Re: Weirdness with two packages.........

2016-11-27 Thread The Wanderer
On 2016-11-27 at 18:57, Charles Schroeder wrote:

> Hello Everyone,
> 
>   In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
>   (2015-08-04) x86_64 GNU/Linux
> 
> I get this message when I attempt to use Chromium:
> 
> $ chromium
> /usr/lib/chromium/chromium: relocation
> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
> libavutil.so.55 with link time reference
> 
> Much the same when I attempt to use goldendict:
> 
> $ goldendict
> goldendict: relocation
> error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
> avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
> libavutil.so.55 with link time reference
> 
> I have no idea what is happening here or how I work round it?
> 
> I can't find those files in my: /usr/lib/x86_64-linux-gnu/ directory?

They should be there, not as files, but as symlinks.

> Trying to install both those packages tells me they are "already
> the newest version" so nothing to install?
> 
> Update, upgrade and reboot doesn't fix it.

What versions are those packages at, according to e.g. 'apt-cache policy
[packagename]'?

What about the libavutil55 and libavformat57 packages?

I have:

$ apt-cache policy chromium
chromium:
  Installed: 53.0.2785.143-1
  Candidate: 53.0.2785.143-1
  Version table:
 *** 53.0.2785.143-1 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
 53.0.2785.143-1~deb8u1 500
500 http://security.debian.org stable/updates/main amd64 Packages
 53.0.2785.89-1~deb8u1 500
500 http://ftp.us.debian.org/debian stable/main amd64 Packages

$ apt-cache policy libavutil55
libavutil55:
  Installed: 7:3.2-2
  Candidate: 7:3.2-2
  Version table:
 *** 7:3.2-2 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy libavformat57
libavformat57:
  Installed: 7:3.2-2
  Candidate: 7:3.2-2
  Version table:
 *** 7:3.2-2 500
500 http://ftp.us.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status

and I don't have goldendict installed.

When I launch chromium from a terminal, I don't get the error you
report. (I do get a different message, but it looks like "normal"
Chromium console spam; I'm not sure I've ever had a nontrivial Chromium
session with no console messages.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Weirdness with two packages.........

2016-11-27 Thread Charles Schroeder

Hello Everyone,

In  3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3
(2015-08-04) x86_64 GNU/Linux

I get this message when I attempt to use Chromium:

$ chromium
/usr/lib/chromium/chromium: relocation
error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
libavutil.so.55 with link time reference

Much the same when I attempt to use goldendict:

$ goldendict
goldendict: relocation
error: /usr/lib/x86_64-linux-gnu/libavformat.so.57: symbol
avpriv_dict_set_timestamp, version LIBAVUTIL_55 not defined in file
libavutil.so.55 with link time reference

I have no idea what is happening here or how I work round it?

I can't find those files in my: /usr/lib/x86_64-linux-gnu/ directory?

Trying to install both those packages tells me they are "already
the newest version" so nothing to install?

Update, upgrade and reboot doesn't fix it.

Any clues please.

TIA,
Charlie