Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updating 3.0.1 to 3.0.2 fails. Ketchup 3.à.2 on 3.0.2 fails #1

Closed
EricV opened this issue Aug 16, 2011 · 3 comments
Closed

updating 3.0.1 to 3.0.2 fails. Ketchup 3.à.2 on 3.0.2 fails #1

EricV opened this issue Aug 16, 2011 · 3 comments

Comments

@EricV
Copy link

EricV commented Aug 16, 2011

Title says all. I tried the debian version then retried with git (linux3 branch).

@psomas
Copy link
Owner

psomas commented Aug 16, 2011

I pushed a change to fix an issue with get_ver() function and 3.x kernels (which could cause some problems), but kernel.org has some mirroring problems right now too, and it's likely that it's due to that (for example, without the --no-gpg flag, ketchup will try to find the .bz2.sign signature, which is not yet available for 3.0.2 at kernel.org and will fail -- although we should probably fix that too). Is this the error you're getting?

Btw, kernel.org keep changing the URLs (for the -rc releases for example), and it's likely that 3.0-rcs will work, while 3.1-rcs won't, or vice versa.

@EricV
Copy link
Author

EricV commented Aug 16, 2011

On 16/08/2011 21:54, psomas wrote:

I pushed a change to fix an issue with get_ver() function and 3.x kernels (which could cause some problems), but kernel.org has some mirroring problems right now too, and it's likely that it's due to that (for example, without the --no-gpg flag, ketchup will try to find the .bz2.sign signature, which is not yet available for 3.0.2 at kernel.org and will fail -- although we should probably fix that too). Is this the error you're getting?

Btw, kernel.org keep changing the URLs (for the -rc releases for example), and it's likely that 3.0-rcs will work, while 3.1-rcs won't, or vice versa.

I correctly update from 2.6.39.3 to 3.0.1 yesterday. Today I tried to
upgrade to 3.0.2 from 3.0.1 and it tries to apply 3.0.2 without first
removing 3.0.1.

I did it manually and then tried to do what should be a nop operation
3.0.2 to 3.0.2 and it tries to apply 3.0.2 anyway.

-- eric

@EricV
Copy link
Author

EricV commented Aug 16, 2011

Tested your last hour fix and yes it fixes the problem.

@EricV EricV closed this as completed Aug 16, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants