Recherche avancée

Sur d’autres sites (7002)

• ffmpeg have unmet dependencies (Ubuntu20) [closed]

  10 août 2024, par mojiang

  when installing ffmpeg with ubuntu20(fosal), it have conflict dependencies :

  


  # sudo apt-get install ffmpeg
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ffmpeg : Depends: libavdevice58 (= 7:4.2.7-0ubuntu0.1) but it is not going to be installed
          Depends: libavfilter7 (= 7:4.2.7-0ubuntu0.1)
          Depends: libavformat58 (= 7:4.2.7-0ubuntu0.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


  


  I solved it by install the reason of conflit library with a specific version, may be someone will need the solution.

  


  step 1. fix-broken

  


  sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree       
Reading state information... Done


  


  step2. find the reason of unmet dependencies :

  


  # sudo apt install libavdevice58=7:4.2.7-0ubuntu0.1 libavfilter7=7:4.2.7-0ubuntu0.1 libavformat58=7:4.2.7-0ubuntu0.1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libavformat58 : Depends: libchromaprint1 (>= 1.3.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


  


  Here the problem is from libchromaprint1

  


  step3. find candidate versions of libchromaprint1(conflict reason)

  


  # apt-cache policy libchromaprint1
libchromaprint1:
  Installed: (none)
  Candidate: 1.5.1-1~20.04.sav0
  Version table:
     1.5.1-1~20.04.sav0 500
        500 http://ppa.launchpad.net/savoury1/multimedia/ubuntu focal/main amd64 Packages
     1.4.3-3build1 500
        500 http://mirrors.cloud.aliyuncs.com/ubuntu focal/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages


  


  step4. install the old version of libchromaprint1 to solve the conflicts

  


  # sudo apt install libchromaprint1=1.4.3-3build1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  libchromaprint1
0 upgraded, 1 newly installed, 0 to remove and 223 not upgraded.
Need to get 37.6 kB of archives.


  


  step5. reinstall ffmpeg

  


  # sudo apt install ffmpeg
Reading package lists... Done
Building dependency tree       
Reading state information... Done


  


  Done. the reason of conflict is that the latest version of libraries have conflict, by install old version of the conflicted ones to solve it.

  


• Thinking about switching to GeoIP2 for better location detection ? Here’s what you should know

  5 juin 2018, par Matomo Core Team

  In Matomo 3.5.0 we added a new feature to improve the location detection (country, region, city) of your visitors. Especially when it comes to IPv6 addresses, you will see less “Unknown” locations and more accurate results in general. This feature is now enabled for all new installations but needs to be manually enabled for existing Matomo self-hosted users.

  

  Why is the Matomo plugin not enabled for existing users ?

  When you enable the GeoIP2 plugin, a database update will need to be executed on two datatable tables (“log_visit” and “log_conversion”) which stores some of the raw data. Please be aware that this update could take several hours depending on the size of your database.

  If you store many visits in your database, it is recommended to execute the update through the command line by executing the command ./console core:update to avoid the update from timing out. You may also have to put your Matomo into maintenance mode during this time and replay the missed traffic from logs afterwards as explained in the FAQ article.

  GeoIP2 may slow down your tracking

  In the past we have seen that a few Matomo databases with high traffic volumes struggle to handle all the tracking requests after enabling GeoIP2. The reason for this is the location database now contains many more entries because it has to store all the IPv6 addresses and the database itself has a different format. Hence, the location lookup takes longer.

  It is hard to say how much slower the location lookup gets, but we found GeoIP2-PHP is about 20 times slower than GeoIP1-PHP. On a fast CPU the lookup time for an IP with GeoIP2 takes about 1ms, but can also take much longer depending on the server.

  Making location lookups fast again

  There is a PHP extension available that makes lookups very fast, even faster than the old GeoIP1-PHP provider. If you can install additional PHP extensions on your server and have a high traffic website, you may want to install the GeoIP2 extension.

  There is also an Nginx module and an Apache module. Unfortunately, we don’t have any performance metrics for these providers.

  How do I activate the GeoIP2 location provider ?

  As a Super User, log in to your Matomo and go to “Administration => Plugins”. There you can activate the “GeoIP2” plugin. As mentioned, this will trigger a database update which can take a while and you may want to perform this update through the command line.

  Now you can go to “Administration => Geolocation”. Here you will first need to install the GeoIP2 databases at the bottom of the page before you can activate the GeoIP2-PHP provider. To activate any of the other GeoIP2 providers, you will need to install the required modules.

  You will be able to check if the detection works on the right next to location provider. Once you selected one of the available providers, you’re all good to go.

  The post Thinking about switching to GeoIP2 for better location detection ? Here’s what you should know appeared first on Analytics Platform - Matomo.

• avcodec/mpeg2dec : Fix motion vector rounding for chroma components

  11 février 2018, par Nekopanda

  avcodec/mpeg2dec : Fix motion vector rounding for chroma components
  In 16x8 motion compensation, for lower 16x8 region, the input to mpeg_motion() for motion_y was "motion_y + 16", which causes wrong rounding. For 4:2:0, chroma scaling for y is dividing by two and rounding toward zero. When motion_y < 0 and motion_y + 16 > 0, the rounding direction of "motion_y" and "motion_y + 16" is different and rounding "motion_y + 16" would be incorrect.
  We should input "motion_y" as is to round correctly. I add "is_16x8" flag to do that.
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/mpegvideo_motion.c
  • [DH] tests/ref/fate/filter-mcdeint-fast
  • [DH] tests/ref/fate/filter-mcdeint-medium
  • [DH] tests/ref/fate/filter-w3fdif-complex
  • [DH] tests/ref/fate/filter-w3fdif-simple
  • [DH] tests/ref/fate/filter-yadif-mode0
  • [DH] tests/ref/fate/filter-yadif-mode1
  • [DH] tests/ref/fate/filter-yadif10
  • [DH] tests/ref/fate/filter-yadif16
  • [DH] tests/ref/fate/mpeg2-field-enc
  • [DH] tests/ref/fate/mpeg2-ticket6677