Making sense of a package with almost no files included

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















$ uname -a
Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux


I need to use cv::face::createLBPHFaceRecognizer(), which is not a part of the core OpenCV but rather a contributed module.



$ dpkg -l libopencv-contrib-dev
ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2


everything fine ... no:



 src/cmd.cpp:150: error: ‘cv::face’ has not been declared
const auto model = cv::face::createLBPHFaceRecognizer();
^~~~


OK. Let's then include the needed headers manually:



$ dpkg -S libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian


Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.










share|improve this question






























    1















    $ uname -a
    Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux


    I need to use cv::face::createLBPHFaceRecognizer(), which is not a part of the core OpenCV but rather a contributed module.



    $ dpkg -l libopencv-contrib-dev
    ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2


    everything fine ... no:



     src/cmd.cpp:150: error: ‘cv::face’ has not been declared
    const auto model = cv::face::createLBPHFaceRecognizer();
    ^~~~


    OK. Let's then include the needed headers manually:



    $ dpkg -S libopencv-contrib-dev
    libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
    libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
    libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
    libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian


    Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.










    share|improve this question


























      1












      1








      1








      $ uname -a
      Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux


      I need to use cv::face::createLBPHFaceRecognizer(), which is not a part of the core OpenCV but rather a contributed module.



      $ dpkg -l libopencv-contrib-dev
      ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2


      everything fine ... no:



       src/cmd.cpp:150: error: ‘cv::face’ has not been declared
      const auto model = cv::face::createLBPHFaceRecognizer();
      ^~~~


      OK. Let's then include the needed headers manually:



      $ dpkg -S libopencv-contrib-dev
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian


      Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.










      share|improve this question
















      $ uname -a
      Linux laptop 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux


      I need to use cv::face::createLBPHFaceRecognizer(), which is not a part of the core OpenCV but rather a contributed module.



      $ dpkg -l libopencv-contrib-dev
      ii libopencv-contrib-dev:amd64 3.2.0+dfsg-6 amd64 development files for libopencv-contrib3.2


      everything fine ... no:



       src/cmd.cpp:150: error: ‘cv::face’ has not been declared
      const auto model = cv::face::createLBPHFaceRecognizer();
      ^~~~


      OK. Let's then include the needed headers manually:



      $ dpkg -S libopencv-contrib-dev
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/changelog.Debian.gz
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/copyright
      libopencv-contrib-dev:amd64: /usr/share/doc/libopencv-contrib-dev/README.Debian


      Nothing! Is this a packager's mistake (this is Debian testing after all)? An OpenCV peculiarity? A minor oversight on my side? I would like to continue using the package manager, instead of compiling the whole thing myself.







      package-management opencv






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 16 at 9:47









      Stephen Kitt

      181k25415494




      181k25415494










      asked Mar 16 at 9:37









      VoracVorac

      1,04831834




      1,04831834




















          2 Answers
          2






          active

          oldest

          votes


















          5














          The package is fine, you’re using the wrong dpkg option:



          dpkg -L libopencv-contrib-dev


          will list all the files in the libopencv-contrib-dev, which is what you’re after (and will show all the files listed here), whereas



          dpkg -S libopencv-contrib-dev


          searches all installed packages for files with libopencv-contrib-dev in their path, which only matches the four files you’ve listed.






          share|improve this answer






























            1














            It was an oversight.



            #include <opencv2/opencv.hpp>
            #include <opencv2/face.hpp>


            The first include is insufficient, the second one is needed as well.



            Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S.






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506660%2fmaking-sense-of-a-package-with-almost-no-files-included%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              5














              The package is fine, you’re using the wrong dpkg option:



              dpkg -L libopencv-contrib-dev


              will list all the files in the libopencv-contrib-dev, which is what you’re after (and will show all the files listed here), whereas



              dpkg -S libopencv-contrib-dev


              searches all installed packages for files with libopencv-contrib-dev in their path, which only matches the four files you’ve listed.






              share|improve this answer



























                5














                The package is fine, you’re using the wrong dpkg option:



                dpkg -L libopencv-contrib-dev


                will list all the files in the libopencv-contrib-dev, which is what you’re after (and will show all the files listed here), whereas



                dpkg -S libopencv-contrib-dev


                searches all installed packages for files with libopencv-contrib-dev in their path, which only matches the four files you’ve listed.






                share|improve this answer

























                  5












                  5








                  5







                  The package is fine, you’re using the wrong dpkg option:



                  dpkg -L libopencv-contrib-dev


                  will list all the files in the libopencv-contrib-dev, which is what you’re after (and will show all the files listed here), whereas



                  dpkg -S libopencv-contrib-dev


                  searches all installed packages for files with libopencv-contrib-dev in their path, which only matches the four files you’ve listed.






                  share|improve this answer













                  The package is fine, you’re using the wrong dpkg option:



                  dpkg -L libopencv-contrib-dev


                  will list all the files in the libopencv-contrib-dev, which is what you’re after (and will show all the files listed here), whereas



                  dpkg -S libopencv-contrib-dev


                  searches all installed packages for files with libopencv-contrib-dev in their path, which only matches the four files you’ve listed.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 16 at 9:46









                  Stephen KittStephen Kitt

                  181k25415494




                  181k25415494























                      1














                      It was an oversight.



                      #include <opencv2/opencv.hpp>
                      #include <opencv2/face.hpp>


                      The first include is insufficient, the second one is needed as well.



                      Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S.






                      share|improve this answer



























                        1














                        It was an oversight.



                        #include <opencv2/opencv.hpp>
                        #include <opencv2/face.hpp>


                        The first include is insufficient, the second one is needed as well.



                        Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S.






                        share|improve this answer

























                          1












                          1








                          1







                          It was an oversight.



                          #include <opencv2/opencv.hpp>
                          #include <opencv2/face.hpp>


                          The first include is insufficient, the second one is needed as well.



                          Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S.






                          share|improve this answer













                          It was an oversight.



                          #include <opencv2/opencv.hpp>
                          #include <opencv2/face.hpp>


                          The first include is insufficient, the second one is needed as well.



                          Although this solves the problem, I would appreciate an explaination why don't any useful files show up in dpkg -S.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Mar 16 at 9:37









                          VoracVorac

                          1,04831834




                          1,04831834



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Unix & Linux Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506660%2fmaking-sense-of-a-package-with-almost-no-files-included%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown






                              Popular posts from this blog

                              Peggy Mitchell

                              Palaiologos

                              The Forum (Inglewood, California)