Hey everyone,
As unstable has been a lot stabler than testing these last few days, I decided to migrate it to testing. An image will be generated later today, but I strongly encourage you to switch your feeds to testing, or flash the new testing image when it'll be out, as we're probably going to break unstable in the next few days.
For those of you as lazy as me, if you're using one of the latest unstable, the following should do the trick: sed -e 's/unstable/testing/g' /etc/opkg/*
Please don't do that until you see a new image, else I won't account for the result :-)
As unstable has been a lot stabler than testing these last few days, I decided to migrate it to testing. An image will be generated later today, but I strongly encourage you to switch your feeds to testing, or flash the new testing image when it'll be out, as we're probably going to break unstable in the next few days.
For those of you as lazy as me, if you're using one of the latest unstable, the following should do the trick: sed -e 's/unstable/testing/g' /etc/opkg/*
Please don't do that until you see a new image, else I won't account for the result :-)
for i in /etc/opkg/*; do cp $i $i.BAC; sed -e 's/unstable/testing/g' $i.BAC > $i; done
I haven't found a place to throw a comment in general so I will do it here. It would be great if it was announced why testing in a period was testing-bad and also why unstable suddenly has a time-stamp saying 25. April as it earlier today had a time-stamp saying 4. May.
It doesn't work for me