Instructions on rolling back to 3.2b1?

A Former User

@oozeBot said in Instructions on rolling back to 3.2b1?:

I wasn't thinking clearly as I just realized I could clone one of my other machine's sd cards to get me back to 3.2b1..

you'd have to run M997 to flash the duet if you haven't already.

oozeBot

@bearer yes- got that part right..! Thanks!

gloomyandy

Do anyone come up with a way of installing/rolling back to 3.2b1 on the SBC? It would be very useful to be able to do this to check for changes between beta1/beta2.

jay_s_uk

This is also an issue for LPC/STM users who have accidentally upgraded or want to move over to the from 3.1.1.
We currently haven't released beta 2 builds as the changes are still being merged in.
I've tried to roll back using a number of version numbers but have been unable to do so.
Is this one for @chrishamm to look at?

chrishamm

To downgrade to 3.2-b1 you must install RRF 3.2-b1 first, because the protocol version has been increased and older DSF versions cannot communicate with it. To do that, download the corresponding firmware binary from GitHub, upload it on the System page, and install it.

Then open a terminal on the SBC (e.g. via SSH) and run the following command with the right software version (3.2.0-beta1 is what you want instead of 3.1.1):

apt-get install duetsoftwareframework=3.1.1 duetcontrolserver=3.1.1 duetsd=1.0.6 duettools=3.1.1 duetwebserver=3.1.0 duetwebcontrol=3.1.1 reprapfirmware=3.1.1-1 duetruntime=3.1.1

Please note that the RRF package has an extra suffix after the software version (-1, may vary).

jay_s_uk

@chrishamm said in Instructions on rolling back to 3.2b1?:

3.2.0-beta1

that still doesn't work. I can roll back to 3.1.1 but I can't roll forwards to 3.2.0-beta1.
This is what I am trying to run

sudo apt-get install duetsoftwareframework=3.2.0-beta1+1 duetcontrolserver=3.2.0-beta1+1 duetsd=1.0.7 duettools=3.2.0-beta1+1 duetwebserver=3.2.0-beta1 duetwebcontrol=3.2.0-beta1+2 reprapfirmware=3.2.0-beta1+1-1 duetruntime=3.2.0-beta1+1

And I still get and unmet dependency for duetwebserver. See the output below

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 duetwebserver : Depends: duetcontrolserver (>= 3.2.0-beta2) but 3.2.0-beta1+1 is to be installed
                 Depends: duetruntime (>= 3.2.0-beta2) but 3.2.0-beta1+1 is to be installed
E: Unable to correct problems, you have held broken packages.

How can a beta1 release be dependent on beta2?

chrishamm

@jay_s_uk Hmm right, I must have overwritten the old DWS package accidentally which caused this error. I just rebuilt b1 and b2 and updated the packages on the server. Try to run sudo apt-get update once again and then downgrade the packages using your command line. If it still doesn't work, remove the downloaded deb files from /var/cache/apt/archives and try again.

jay_s_uk

@chrishamm that works now, thank you

A Former User

Phew, I thought I was going bonkers .. probably are, but at least not with apt:)

oozeBot

@chrishamm Thank you for the assist! I'm glad to see it wasn't my ignorance with Linux causing the issue..!