dpkg: error processing package dradis












0














I just ran apt-get update && apt-get upgrade and this is what I got:



Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up dradis (3.1.0~rc2+git20160609-0kali2) ...
Warning: The home dir /var/lib/dradis you specified already exists.
The system user `dradis' already exists. Exiting.
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize':
undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `new'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:200:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:140:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:185:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:174:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:127:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:8:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/dradis/config/boot.rb:3:in `<top (required)>'
from bin/rake:2:in `require_relative'
from bin/rake:2:in `<main>'
dpkg: error processing package dradis (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
dradis
E: Sub-process /usr/bin/dpkg returned an error code (1)


What should I do?










share|improve this question
























  • Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
    – fkraiem
    Jul 5 '16 at 18:40












  • so what should i do now? any suggestions?
    – viper strike
    Jul 6 '16 at 6:35
















0














I just ran apt-get update && apt-get upgrade and this is what I got:



Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up dradis (3.1.0~rc2+git20160609-0kali2) ...
Warning: The home dir /var/lib/dradis you specified already exists.
The system user `dradis' already exists. Exiting.
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize':
undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `new'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:200:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:140:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:185:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:174:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:127:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:8:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/dradis/config/boot.rb:3:in `<top (required)>'
from bin/rake:2:in `require_relative'
from bin/rake:2:in `<main>'
dpkg: error processing package dradis (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
dradis
E: Sub-process /usr/bin/dpkg returned an error code (1)


What should I do?










share|improve this question
























  • Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
    – fkraiem
    Jul 5 '16 at 18:40












  • so what should i do now? any suggestions?
    – viper strike
    Jul 6 '16 at 6:35














0












0








0







I just ran apt-get update && apt-get upgrade and this is what I got:



Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up dradis (3.1.0~rc2+git20160609-0kali2) ...
Warning: The home dir /var/lib/dradis you specified already exists.
The system user `dradis' already exists. Exiting.
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize':
undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `new'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:200:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:140:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:185:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:174:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:127:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:8:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/dradis/config/boot.rb:3:in `<top (required)>'
from bin/rake:2:in `require_relative'
from bin/rake:2:in `<main>'
dpkg: error processing package dradis (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
dradis
E: Sub-process /usr/bin/dpkg returned an error code (1)


What should I do?










share|improve this question















I just ran apt-get update && apt-get upgrade and this is what I got:



Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up dradis (3.1.0~rc2+git20160609-0kali2) ...
Warning: The home dir /var/lib/dradis you specified already exists.
The system user `dradis' already exists. Exiting.
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize':
undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `new'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:181:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:200:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:140:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:185:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:174:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:127:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:8:in `<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /usr/lib/dradis/config/boot.rb:3:in `<top (required)>'
from bin/rake:2:in `require_relative'
from bin/rake:2:in `<main>'
dpkg: error processing package dradis (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
dradis
E: Sub-process /usr/bin/dpkg returned an error code (1)


What should I do?







apt package-management dpkg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 5 '16 at 18:41









Byte Commander

62.8k26169286




62.8k26169286










asked Jul 5 '16 at 18:34









viper strike

112




112












  • Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
    – fkraiem
    Jul 5 '16 at 18:40












  • so what should i do now? any suggestions?
    – viper strike
    Jul 6 '16 at 6:35


















  • Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
    – fkraiem
    Jul 5 '16 at 18:40












  • so what should i do now? any suggestions?
    – viper strike
    Jul 6 '16 at 6:35
















Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
– fkraiem
Jul 5 '16 at 18:40






Looks like a missing dependency. /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in 'block in initialize': undefined method 'add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)
– fkraiem
Jul 5 '16 at 18:40














so what should i do now? any suggestions?
– viper strike
Jul 6 '16 at 6:35




so what should i do now? any suggestions?
– viper strike
Jul 6 '16 at 6:35










2 Answers
2






active

oldest

votes


















0














deb packages have some hooks defined, where scripts can be executed while the package is installed, uninstalled etc. It seems that in your case one such script fails, so the whole installation fails:



 /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize': 
undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)


So Bundler can't find a method in a library it would like to call. Judging from this issue at Bundler's Github repo, you might be using an outdated version of Bundler. So maybe upgrading Bundler would help. How exactly you need to do that depends on how you installed Ruby including Bundler (package system, RVM, rbenv, ...)






share|improve this answer





















  • i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
    – viper strike
    Jul 6 '16 at 6:34










  • Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
    – Henning Kockerbeck
    Jul 6 '16 at 9:14












  • You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
    – Henning Kockerbeck
    Jul 6 '16 at 9:17










  • Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
    – viper strike
    Jul 6 '16 at 19:15



















0














I had the same issue in Kali. Removing dradis fixed it for me.



apt-get remove dradis





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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f795232%2fdpkg-error-processing-package-dradis%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









    0














    deb packages have some hooks defined, where scripts can be executed while the package is installed, uninstalled etc. It seems that in your case one such script fails, so the whole installation fails:



     /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize': 
    undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)


    So Bundler can't find a method in a library it would like to call. Judging from this issue at Bundler's Github repo, you might be using an outdated version of Bundler. So maybe upgrading Bundler would help. How exactly you need to do that depends on how you installed Ruby including Bundler (package system, RVM, rbenv, ...)






    share|improve this answer





















    • i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
      – viper strike
      Jul 6 '16 at 6:34










    • Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
      – Henning Kockerbeck
      Jul 6 '16 at 9:14












    • You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
      – Henning Kockerbeck
      Jul 6 '16 at 9:17










    • Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
      – viper strike
      Jul 6 '16 at 19:15
















    0














    deb packages have some hooks defined, where scripts can be executed while the package is installed, uninstalled etc. It seems that in your case one such script fails, so the whole installation fails:



     /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize': 
    undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)


    So Bundler can't find a method in a library it would like to call. Judging from this issue at Bundler's Github repo, you might be using an outdated version of Bundler. So maybe upgrading Bundler would help. How exactly you need to do that depends on how you installed Ruby including Bundler (package system, RVM, rbenv, ...)






    share|improve this answer





















    • i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
      – viper strike
      Jul 6 '16 at 6:34










    • Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
      – Henning Kockerbeck
      Jul 6 '16 at 9:14












    • You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
      – Henning Kockerbeck
      Jul 6 '16 at 9:17










    • Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
      – viper strike
      Jul 6 '16 at 19:15














    0












    0








    0






    deb packages have some hooks defined, where scripts can be executed while the package is installed, uninstalled etc. It seems that in your case one such script fails, so the whole installation fails:



     /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize': 
    undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)


    So Bundler can't find a method in a library it would like to call. Judging from this issue at Bundler's Github repo, you might be using an outdated version of Bundler. So maybe upgrading Bundler would help. How exactly you need to do that depends on how you installed Ruby including Bundler (package system, RVM, rbenv, ...)






    share|improve this answer












    deb packages have some hooks defined, where scripts can be executed while the package is installed, uninstalled etc. It seems that in your case one such script fails, so the whole installation fails:



     /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in initialize': 
    undefined method `add_root_vertex' for Molinillo::DependencyGraph::Molinillo::DependencyGraph (NoMethodError)


    So Bundler can't find a method in a library it would like to call. Judging from this issue at Bundler's Github repo, you might be using an outdated version of Bundler. So maybe upgrading Bundler would help. How exactly you need to do that depends on how you installed Ruby including Bundler (package system, RVM, rbenv, ...)







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 5 '16 at 18:53









    Henning Kockerbeck

    3,7351524




    3,7351524












    • i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
      – viper strike
      Jul 6 '16 at 6:34










    • Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
      – Henning Kockerbeck
      Jul 6 '16 at 9:14












    • You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
      – Henning Kockerbeck
      Jul 6 '16 at 9:17










    • Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
      – viper strike
      Jul 6 '16 at 19:15


















    • i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
      – viper strike
      Jul 6 '16 at 6:34










    • Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
      – Henning Kockerbeck
      Jul 6 '16 at 9:14












    • You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
      – Henning Kockerbeck
      Jul 6 '16 at 9:17










    • Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
      – viper strike
      Jul 6 '16 at 19:15
















    i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
    – viper strike
    Jul 6 '16 at 6:34




    i did not install ruby seperately i guess it got installed the last time i did apt-get update && apt-get upgrade... n is there any way to solve this .. coz the last option i have is to reinstall the os
    – viper strike
    Jul 6 '16 at 6:34












    Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
    – Henning Kockerbeck
    Jul 6 '16 at 9:14






    Look which version of ruby you're using at the moment: bundler -v. Look whether it's the most current: gem list -r ^bundler$. The same way, check whether the molinillo is at the most current version: gem list -l molinillo and gem list -r molinillo. Those two are the ones that need to "interact" in your case, but it fails.
    – Henning Kockerbeck
    Jul 6 '16 at 9:14














    You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
    – Henning Kockerbeck
    Jul 6 '16 at 9:17




    You can upgrade a Gem with gem update name-of-the-gem. But be aware that something else might not be compatible with the newer version then, so no guarantees ;)
    – Henning Kockerbeck
    Jul 6 '16 at 9:17












    Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
    – viper strike
    Jul 6 '16 at 19:15




    Thanks for your help.. but i just reinstalled the os n then did an update.. n everything works fine now😁😁.. ...
    – viper strike
    Jul 6 '16 at 19:15













    0














    I had the same issue in Kali. Removing dradis fixed it for me.



    apt-get remove dradis





    share|improve this answer


























      0














      I had the same issue in Kali. Removing dradis fixed it for me.



      apt-get remove dradis





      share|improve this answer
























        0












        0








        0






        I had the same issue in Kali. Removing dradis fixed it for me.



        apt-get remove dradis





        share|improve this answer












        I had the same issue in Kali. Removing dradis fixed it for me.



        apt-get remove dradis






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 5 '16 at 11:54









        kpoustas

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2faskubuntu.com%2fquestions%2f795232%2fdpkg-error-processing-package-dradis%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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

            Eduardo VII do Reino Unido