-
Notifications
You must be signed in to change notification settings - Fork 14
Linux .deb format #194
Comments
what? |
I think the installer is saying the md5 sums don't match up |
Can you provide the error message/info message? On Tuesday, November 27, 2012, misson20000 wrote:
Cheers, |
I did. I'll reformat it so that the info message is more noticable |
Oh, sorry, I had been replying via email and you had updated the post after I received the original email. Regardless, it looks like something got messed up in the generation of the .deb file. Not sure how that might have happened. If you give me a minute, i will tell the buildbot to re-generate the .deb |
Can you please try this file? I just had the buildbot re-compile the toolchain and re-generate that .deb |
Still doesn't work. Exactly the same error as before. The installation of a package which violates the quality standards isn't allowed. This could cause serious problems on your computer. Please contact the person or organisation who provided this package file and include the details beneath. Details: |
Still getting the same error, although the path is in /tmp now, not surprising to me, though. I extracted the previous debs out of the tar.gz file and this one is the direct deb. Same error, though |
I just tried gdebi and gdebi doesn't have a problem with the debs |
Well, actually all of them work, but give me warnings |
we'll check it out @Mause ;) |
@misson20000 would you be willing to try building the toolchain .deb's on your machine to try to fix this? I am unsure of where to go from here, or what the exact problem might be. @hach-que may have some idea however. |
I can't assist much as I don't use a Debian-based system. |
@misson20000 did you have any luck building on your own machine? |
Ubuntu Software Center gives me this warning when I install dcpu-toolchain. To me, it looks like md5 sums aren't matching up
Lintian check results for /home/misson20000/.cache/.fr-rCtlf0/toolchain.deb:
E: dcputoolchain: control-file-has-bad-permissions md5sums 0600 != 0644
The text was updated successfully, but these errors were encountered: