Cabal unexpected behaviour when upgrading












1














ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library
ramiro@omfg-hello:~$ sudo cabal install cabal-install --force-reinstalls
[sudo] password for ramiro:
Resolving dependencies...
Configuring cabal-install-2.4.0.0...
Building cabal-install-2.4.0.0...
Installed cabal-install-2.4.0.0
ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library


Indeed i wasn't expecting something like this. I'm stunned.



Edit:



Fixed with @duplode comment



Further edit:



Anybody knows why i'm still getting this?



ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-test all
cabal: unrecognised command: new-test (try --help)


At least i get the correct cabal version now



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal --v
cabal-install version 2.4.0.0
compiled using version 2.4.0.1 of the Cabal library


EditN :



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal new-build
/home/ramiro/.cabal/packages/hackage.haskell.org: openBinaryTempFileWithDefaultPermissions: permission denied (Permission denied)
ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-build
[sudo] password for ramiro:
Up to date
ramiro@omfg-hello:~/Haskell/happstack-server$


Non-sudo vs sudo.










share|improve this question




















  • 1




    (1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
    – duplode
    Nov 12 '18 at 3:18










  • @duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
    – user3927886
    Nov 12 '18 at 4:11










  • Note that, in your edit, you are still running cabal with sudo.
    – duplode
    Nov 12 '18 at 4:28










  • Won't work without sudo atm
    – user3927886
    Nov 12 '18 at 5:38










  • "Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
    – duplode
    Nov 12 '18 at 5:42
















1














ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library
ramiro@omfg-hello:~$ sudo cabal install cabal-install --force-reinstalls
[sudo] password for ramiro:
Resolving dependencies...
Configuring cabal-install-2.4.0.0...
Building cabal-install-2.4.0.0...
Installed cabal-install-2.4.0.0
ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library


Indeed i wasn't expecting something like this. I'm stunned.



Edit:



Fixed with @duplode comment



Further edit:



Anybody knows why i'm still getting this?



ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-test all
cabal: unrecognised command: new-test (try --help)


At least i get the correct cabal version now



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal --v
cabal-install version 2.4.0.0
compiled using version 2.4.0.1 of the Cabal library


EditN :



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal new-build
/home/ramiro/.cabal/packages/hackage.haskell.org: openBinaryTempFileWithDefaultPermissions: permission denied (Permission denied)
ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-build
[sudo] password for ramiro:
Up to date
ramiro@omfg-hello:~/Haskell/happstack-server$


Non-sudo vs sudo.










share|improve this question




















  • 1




    (1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
    – duplode
    Nov 12 '18 at 3:18










  • @duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
    – user3927886
    Nov 12 '18 at 4:11










  • Note that, in your edit, you are still running cabal with sudo.
    – duplode
    Nov 12 '18 at 4:28










  • Won't work without sudo atm
    – user3927886
    Nov 12 '18 at 5:38










  • "Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
    – duplode
    Nov 12 '18 at 5:42














1












1








1







ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library
ramiro@omfg-hello:~$ sudo cabal install cabal-install --force-reinstalls
[sudo] password for ramiro:
Resolving dependencies...
Configuring cabal-install-2.4.0.0...
Building cabal-install-2.4.0.0...
Installed cabal-install-2.4.0.0
ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library


Indeed i wasn't expecting something like this. I'm stunned.



Edit:



Fixed with @duplode comment



Further edit:



Anybody knows why i'm still getting this?



ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-test all
cabal: unrecognised command: new-test (try --help)


At least i get the correct cabal version now



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal --v
cabal-install version 2.4.0.0
compiled using version 2.4.0.1 of the Cabal library


EditN :



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal new-build
/home/ramiro/.cabal/packages/hackage.haskell.org: openBinaryTempFileWithDefaultPermissions: permission denied (Permission denied)
ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-build
[sudo] password for ramiro:
Up to date
ramiro@omfg-hello:~/Haskell/happstack-server$


Non-sudo vs sudo.










share|improve this question















ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library
ramiro@omfg-hello:~$ sudo cabal install cabal-install --force-reinstalls
[sudo] password for ramiro:
Resolving dependencies...
Configuring cabal-install-2.4.0.0...
Building cabal-install-2.4.0.0...
Installed cabal-install-2.4.0.0
ramiro@omfg-hello:~$ cabal --version
cabal-install version 1.24.0.2
compiled using version 1.24.2.0 of the Cabal library


Indeed i wasn't expecting something like this. I'm stunned.



Edit:



Fixed with @duplode comment



Further edit:



Anybody knows why i'm still getting this?



ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-test all
cabal: unrecognised command: new-test (try --help)


At least i get the correct cabal version now



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal --v
cabal-install version 2.4.0.0
compiled using version 2.4.0.1 of the Cabal library


EditN :



ramiro@omfg-hello:~/Haskell/happstack-server$ cabal new-build
/home/ramiro/.cabal/packages/hackage.haskell.org: openBinaryTempFileWithDefaultPermissions: permission denied (Permission denied)
ramiro@omfg-hello:~/Haskell/happstack-server$ sudo cabal new-build
[sudo] password for ramiro:
Up to date
ramiro@omfg-hello:~/Haskell/happstack-server$


Non-sudo vs sudo.







haskell cabal






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 12 '18 at 5:48

























asked Nov 12 '18 at 2:52









user3927886

15910




15910








  • 1




    (1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
    – duplode
    Nov 12 '18 at 3:18










  • @duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
    – user3927886
    Nov 12 '18 at 4:11










  • Note that, in your edit, you are still running cabal with sudo.
    – duplode
    Nov 12 '18 at 4:28










  • Won't work without sudo atm
    – user3927886
    Nov 12 '18 at 5:38










  • "Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
    – duplode
    Nov 12 '18 at 5:42














  • 1




    (1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
    – duplode
    Nov 12 '18 at 3:18










  • @duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
    – user3927886
    Nov 12 '18 at 4:11










  • Note that, in your edit, you are still running cabal with sudo.
    – duplode
    Nov 12 '18 at 4:28










  • Won't work without sudo atm
    – user3927886
    Nov 12 '18 at 5:38










  • "Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
    – duplode
    Nov 12 '18 at 5:42








1




1




(1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
– duplode
Nov 12 '18 at 3:18




(1) Do not use sudo to run cabal. With typical workflows, cabal-install is meant to be ran from your regular user account. (2) Make sure $HOME/.cabal/bin, the default location for executables installed with cabal-install, appears in your PATH before the system-wide location of your preexisting cabal-install. (3) Remember you can check where the executable actually is with which cabal.
– duplode
Nov 12 '18 at 3:18












@duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
– user3927886
Nov 12 '18 at 4:11




@duplode Your suggestions worked, thanks! but do you know how to solve my updated problem? the whole point of upgrading cabal was to run the command new-test
– user3927886
Nov 12 '18 at 4:11












Note that, in your edit, you are still running cabal with sudo.
– duplode
Nov 12 '18 at 4:28




Note that, in your edit, you are still running cabal with sudo.
– duplode
Nov 12 '18 at 4:28












Won't work without sudo atm
– user3927886
Nov 12 '18 at 5:38




Won't work without sudo atm
– user3927886
Nov 12 '18 at 5:38












"Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
– duplode
Nov 12 '18 at 5:42




"Won't work without sudo atm" -- Exactly how does it fail? If cabal --v and which cabal show you are indeed using the 2.4.0.0 version installed in your home directory, cabal new-test should, in principle, also work.
– duplode
Nov 12 '18 at 5:42












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53255399%2fcabal-unexpected-behaviour-when-upgrading%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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%2fstackoverflow.com%2fquestions%2f53255399%2fcabal-unexpected-behaviour-when-upgrading%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

Full-time equivalent

Bicuculline

さくらももこ