rollback to lower firefly_svn fails

[goana]

hi together,

I have running an unslung NSLU2 (V2.3R63-uNSLUng-6.8-beta) with firefly svn-1696.
Now I want roll back to svn-1498-1 for testing some things but I do not have any success.

I have done things as follows:
– Downloading the file mt-daapd_svn-1498-1_armeb.ipk and have put the file into the folder \slugADMIN 2tmp
– telnet into my slug as root
– cd /tmp
– ipkg install -force-overwrite mt-daapd_svn-1498-1-1_armeb.ipk

But what I see is “package mt-daapd (svn-1696-1) installed in root is up to date. Nothing to be done”!

What’s wrong with my procedure?

I am happy about any help.

goana

[rpedde]

@goana wrote:

hi together,

I have running an unslung NSLU2 (V2.3R63-uNSLUng-6.8-beta) with firefly svn-1696.
Now I want roll back to svn-1498-1 for testing some things but I do not have any success.

I have done things as follows:
– Downloading the file mt-daapd_svn-1498-1_armeb.ipk and have put the file into the folder \slugADMIN 2tmp
– telnet into my slug as root
– cd /tmp
– ipkg install -force-overwrite mt-daapd_svn-1498-1-1_armeb.ipk

But what I see is “package mt-daapd (svn-1696-1) installed in root is up to date. Nothing to be done”!

What’s wrong with my procedure?

I am happy about any help.

goana

It’s a dumbness in ipkg. The latest version broke the ability to downgrade. To make it do so, you can move your repos out of the way, then do the ipkg install:

# mv /etc/ipkg /etc/ipkg.old

# ipkg update

# ipkg install /path/to/ipkg

# mv /etc/ipkg.old /etc/ipkg

# ipkg update

Kind of lame, but there you go.

Remember that database structure upgrades from old version to new version, but doesn’t gracefully downgrade, so you’ll likely need ot delete your songs*.db

— Ron

[goana]

hi ron,

thanks for your fast reply.

I have done things as follows:

# mv /etc/ipkg /etc/ipkg.old
# ipkg update
# cd /tmp (path to ipkg)
# ipkg install -force-overwrite mt-daapd_svn-1498-1_armeb.ipk

after that the slug “says”: Package mt-daapd (svn-1696-1) installed in root is up to date. Nothing do be done.

# mv /etc/ipkg.old /etc/ipkg
# ipkg update

What’s wrong? Any idea?

I have also tried the “wget” command:
cd /tmp
wget http://nightlies.mt-daapd.org/dl.php?FILE=mt-daapd_svn-1498-1_armeb.ipk
ipkg install -force-overwrite mt-daapd_svn-1498-1_armeb.ipk

But it is the same as mentioned above, the slug says “Package mt-daapd (svn-1696-1) installed in root is up to date. Nothing do be done”.

I am lucky about any help

goana

[rpedde]

@goana wrote:

after that the slug “says”: Package mt-daapd (svn-1696-1) installed in root is up to date. Nothing do be done.

Oh, sorry… do an “ipkg remove mt-daapd” before it, so it has no current installed version to compare to.

So:

– mv
– update
– remove
– install
– mv
– update

— Ron

[goana]

hi ron,

thanks a lot for your help. now the downgrade to svn-1498 has worked :-)).

One question, now (svn-1498) the database type is sqlite but I can also chose sqlite3. What is the difference between both database types and which one should I use?

regards and thanks for that great firefly software

goana

[rpedde]

@goana wrote:

hi ron,

thanks a lot for your help. now the downgrade to svn-1498 has worked :-)).

One question, now (svn-1498) the database type is sqlite but I can also chose sqlite3. What is the difference between both database types and which one should I use?

regards and thanks for that great firefly software

goana

No real difference, but sqlite3 is generally faster, so I’d go with that.

— Ron

[Author]

Posts