Bug#769581: libwebkitgtk-1.0-0 not instabllable since 2.4.7-2

[Thilo Six]

fixed 769581 2.4.7-2
thanks
--

Alberto Garcia schrieb am 14.11.2014 um 21:57:
> On Fri, Nov 14, 2014 at 09:30:05PM +0100, Thilo Six wrote:
> 
>> I already waited 2 days, since the upload of 2.4.7-2
>>
>> following mirrors have been tried with same problem:
>> ftp2.de.debian.org/debian
>> ftp.de.debian.org/debian
>> ftp.fi.debian.org/debian
>> ftp.jp.debian.org/debian
> 
> # apt-get update
> Get:1 http://ftp.de.debian.org sid InRelease [242 kB]
> Get:2 http://ftp.de.debian.org sid/main Translation-en [4819 kB]
> Get:3 http://ftp.de.debian.org sid/main amd64 Packages [7097 kB]
> Fetched 12.2 MB in 6s (1879 kB/s)
> Reading package lists... Done
> 
> # apt-get install libwebkitgtk-1.0-0
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following extra packages will be installed:
>  [...]
> Need to get 0 B/46.5 MB of archives.
> After this operation, 180 MB of additional disk space will be used.
> Do you want to continue? [Y/n]
> debconf: delaying package configuration, since apt-utils is not installed
> Selecting previously unselected package libudev1:amd64.
> (Reading database ... 12158 files and directories currently installed.)
> Preparing to unpack .../libudev1_215-5+b1_amd64.deb ...
> Unpacking libudev1:amd64 (215-5+b1) ...
>  [...]
> Setting up libxslt1.1:amd64 (1.1.28-2+b2) ...
> Setting up libxt6:amd64 (1:1.1.4-1+b1) ...
> Setting up libwebkitgtk-1.0-common (2.4.7-2) ...
> Setting up libwebkitgtk-1.0-0:amd64 (2.4.7-2) ...
> 
> # dpkg -l | grep -F 2.4.7-2
> ii  libjavascriptcoregtk-1.0-0:amd64     2.4.7-2                  amd64        JavaScript engine library from WebKitGTK+
> ii  libwebkitgtk-1.0-0:amd64             2.4.7-2                  amd64        Web content engine library for GTK+
> ii  libwebkitgtk-1.0-common              2.4.7-2                  all          Web content engine library for GTK+ - data files
> 
> Berto

Hello

i do now understand what happing here.
I do have (had) a local repo which was overwriting official repos.
So this is not Debians nor your fault but mine, only mine.

I am sorry for wasting your time and also thank you for your timely support.


kind regards,

     Thilo