Scratchbox repositories
m (→Warning) |
m (→Warning) |
||
Line 60: | Line 60: | ||
$ fakeroot dpkg -i /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso8_i386.deb | $ fakeroot dpkg -i /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso8_i386.deb | ||
- | So it finally shuts up. | + | So it finally shuts up and you have involuntarily updated to Diablo. ;-) |
= Diablo = | = Diablo = |
Revision as of 19:40, 10 August 2008
Contents |
Why?
Since distributions seem to use different formats for the "/etc/apt/source.list" file, we decided to create this page for the benefit of people that don't want to reinstall scratchbox every few weeks... ;)
How?
In the Scratchbox, do:
$ vi "/etc/apt/sources.list" <put new entries> $ apt-get update $ apt-get dist-upgrade
Chinook
deb http://repository.maemo.org/ chinook free non-free deb-src http://repository.maemo.org/ chinook free
Warning
Note that for at least one user, the current chinook repository doesn't work anymore:
(Reading database ... 12047 files and directories currently installed.) Preparing to replace passwd 1:4.0.3-31sarge5.osso7 (using .../passwd_1%3a4.0.3-31sarge5.osso7_i386.deb) ... Unpacking replacement passwd ... dpkg: error processing /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso7_i386.deb (--unpack): trying to overwrite `/usr/sbin/add-shell', which is also in package debianutils Errors were encountered while processing: /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso7_i386.deb E: Sub-process /scratchbox/devkits/debian-sarge/bin/dpkg returned an error code (1)
When that happens, you can't dist-upgrade either. So do this BEFORE editing "/etc/apt/sources.list" (or reedit it for "Chinook"):
$ apt-get install passwd $ dpkg -i --force-all /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso7_i386.deb $ apt-get install --reinstall debianutils $ dpkg -i --force-all /var/cache/apt/archives/debianutils<tab
Or if that doesn't work either, you can, AS A LAST RESORT, try editing "/etc/apt/sources.list" for "Diablo", and then:
$ apt-get install passwd
This will update "passwd" to Diablo's "passwd". If you expect anything to work after that, HAHAHA. Did I tell you this advice comes with no warranty? No really, if you are lucky (about as lucky as not getting run over when crossing the street on foot while traffic is high), it could work.
Don't forget to dist-update as soon as possible afterwards so that the remainder of the system is updated too (and hopefully doesn't choke on the already-updated "passwd"):
$ apt-get dist-upgrade
In any case, should this happen after you updated the distribution one way or another:
Preparing to replace passwd 1:4.0.3-31sarge5.osso7 (using .../passwd_1%3a4.0.3-31sarge5.osso8_i386.deb) ... Unpacking replacement passwd ... dpkg: error processing /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso8_i386.deb (--unpack): trying to overwrite `/usr/sbin/remove-shell', which is also in package debianutils
Then do this:
$ fakeroot dpkg -i /var/cache/apt/archives/passwd_1%3a4.0.3-31sarge5.osso8_i386.deb
So it finally shuts up and you have involuntarily updated to Diablo. ;-)
Diablo
deb http://repository.maemo.org/ diablo/sdk free non-free deb-src http://repository.maemo.org/ diablo/sdk free deb http://repository.maemo.org/ diablo/tools free non-free deb-src http://repository.maemo.org/ diablo/tools free