Aptly: package in repo but can't be installed

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








up vote
3
down vote

favorite
1












I'm setting up a repo by doing the following:



aptly repo create sample_repo
aptly repo add sample_repo neuboxdb-0.9.0-amd64.deb
aptly snapshot create sample_snapshot from repo sample_repo
aptly publish snapshot sample_snapshot
aptly serve


The web server starts on port 8080.



I then add the following to sources.list on a x86-64 machine:



deb [arch=amd64] http://[ip address of server:8080/ xenial universe


Next I run:



sudo apt-get update


Which returns:



W: http://[server ip]:8080/dists/xenial/InRelease: Signature by key EB45DBC87E77FEA9CB66C1D13FB76626D9985912 uses weak digest algorithm (SHA1)


But when I run:



sudo apt-get install neuboxdb


I get:



E: Unable to locate package neuboxdb


Looking in /var/lib/apt/lists on the machine I'm installing onto, I see an InRelease file corresponding to the server, but no amd64_Packages file.



On the repo machine, ~/.aptly/public/dists/xenial/main/binary-amd64 contains an entry for neuboxdb.



What's not right with this?







share|improve this question


























    up vote
    3
    down vote

    favorite
    1












    I'm setting up a repo by doing the following:



    aptly repo create sample_repo
    aptly repo add sample_repo neuboxdb-0.9.0-amd64.deb
    aptly snapshot create sample_snapshot from repo sample_repo
    aptly publish snapshot sample_snapshot
    aptly serve


    The web server starts on port 8080.



    I then add the following to sources.list on a x86-64 machine:



    deb [arch=amd64] http://[ip address of server:8080/ xenial universe


    Next I run:



    sudo apt-get update


    Which returns:



    W: http://[server ip]:8080/dists/xenial/InRelease: Signature by key EB45DBC87E77FEA9CB66C1D13FB76626D9985912 uses weak digest algorithm (SHA1)


    But when I run:



    sudo apt-get install neuboxdb


    I get:



    E: Unable to locate package neuboxdb


    Looking in /var/lib/apt/lists on the machine I'm installing onto, I see an InRelease file corresponding to the server, but no amd64_Packages file.



    On the repo machine, ~/.aptly/public/dists/xenial/main/binary-amd64 contains an entry for neuboxdb.



    What's not right with this?







    share|improve this question
























      up vote
      3
      down vote

      favorite
      1









      up vote
      3
      down vote

      favorite
      1






      1





      I'm setting up a repo by doing the following:



      aptly repo create sample_repo
      aptly repo add sample_repo neuboxdb-0.9.0-amd64.deb
      aptly snapshot create sample_snapshot from repo sample_repo
      aptly publish snapshot sample_snapshot
      aptly serve


      The web server starts on port 8080.



      I then add the following to sources.list on a x86-64 machine:



      deb [arch=amd64] http://[ip address of server:8080/ xenial universe


      Next I run:



      sudo apt-get update


      Which returns:



      W: http://[server ip]:8080/dists/xenial/InRelease: Signature by key EB45DBC87E77FEA9CB66C1D13FB76626D9985912 uses weak digest algorithm (SHA1)


      But when I run:



      sudo apt-get install neuboxdb


      I get:



      E: Unable to locate package neuboxdb


      Looking in /var/lib/apt/lists on the machine I'm installing onto, I see an InRelease file corresponding to the server, but no amd64_Packages file.



      On the repo machine, ~/.aptly/public/dists/xenial/main/binary-amd64 contains an entry for neuboxdb.



      What's not right with this?







      share|improve this question














      I'm setting up a repo by doing the following:



      aptly repo create sample_repo
      aptly repo add sample_repo neuboxdb-0.9.0-amd64.deb
      aptly snapshot create sample_snapshot from repo sample_repo
      aptly publish snapshot sample_snapshot
      aptly serve


      The web server starts on port 8080.



      I then add the following to sources.list on a x86-64 machine:



      deb [arch=amd64] http://[ip address of server:8080/ xenial universe


      Next I run:



      sudo apt-get update


      Which returns:



      W: http://[server ip]:8080/dists/xenial/InRelease: Signature by key EB45DBC87E77FEA9CB66C1D13FB76626D9985912 uses weak digest algorithm (SHA1)


      But when I run:



      sudo apt-get install neuboxdb


      I get:



      E: Unable to locate package neuboxdb


      Looking in /var/lib/apt/lists on the machine I'm installing onto, I see an InRelease file corresponding to the server, but no amd64_Packages file.



      On the repo machine, ~/.aptly/public/dists/xenial/main/binary-amd64 contains an entry for neuboxdb.



      What's not right with this?









      share|improve this question













      share|improve this question




      share|improve this question








      edited May 26 at 6:40









      galoget

      2,1062820




      2,1062820










      asked May 26 at 2:50









      Craig S. Anderson

      1246




      1246




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          Such a nice tool to know about thank you. Well, could you compare these:




          sources.list on on x86-64 machine:



          deb [arch=amd64] http://[ip address of server]:8080/ xenial universe


          ...



          On the repo machine,



          ~/.aptly/public/dists/xenial/main/binary-amd64



          See the component, it is not the same, so your sources.list should have something like:



          deb [arch=amd64] http://[ip address of server]:8080/ xenial main





          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "89"
            ;
            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',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1040455%2faptly-package-in-repo-but-cant-be-installed%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            2
            down vote



            accepted










            Such a nice tool to know about thank you. Well, could you compare these:




            sources.list on on x86-64 machine:



            deb [arch=amd64] http://[ip address of server]:8080/ xenial universe


            ...



            On the repo machine,



            ~/.aptly/public/dists/xenial/main/binary-amd64



            See the component, it is not the same, so your sources.list should have something like:



            deb [arch=amd64] http://[ip address of server]:8080/ xenial main





            share|improve this answer
























              up vote
              2
              down vote



              accepted










              Such a nice tool to know about thank you. Well, could you compare these:




              sources.list on on x86-64 machine:



              deb [arch=amd64] http://[ip address of server]:8080/ xenial universe


              ...



              On the repo machine,



              ~/.aptly/public/dists/xenial/main/binary-amd64



              See the component, it is not the same, so your sources.list should have something like:



              deb [arch=amd64] http://[ip address of server]:8080/ xenial main





              share|improve this answer






















                up vote
                2
                down vote



                accepted







                up vote
                2
                down vote



                accepted






                Such a nice tool to know about thank you. Well, could you compare these:




                sources.list on on x86-64 machine:



                deb [arch=amd64] http://[ip address of server]:8080/ xenial universe


                ...



                On the repo machine,



                ~/.aptly/public/dists/xenial/main/binary-amd64



                See the component, it is not the same, so your sources.list should have something like:



                deb [arch=amd64] http://[ip address of server]:8080/ xenial main





                share|improve this answer












                Such a nice tool to know about thank you. Well, could you compare these:




                sources.list on on x86-64 machine:



                deb [arch=amd64] http://[ip address of server]:8080/ xenial universe


                ...



                On the repo machine,



                ~/.aptly/public/dists/xenial/main/binary-amd64



                See the component, it is not the same, so your sources.list should have something like:



                deb [arch=amd64] http://[ip address of server]:8080/ xenial main






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 26 at 3:26









                user.dz

                33.5k1186165




                33.5k1186165






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1040455%2faptly-package-in-repo-but-cant-be-installed%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491