Nautilus6 Package Repository FAQ

Questions:


Answers:

  Q: What will I find on the package repository? (↑)
  A: We have packaged the MIPv6 related softwares that have no binary packages yet or that had to be modified to support mobility. This includes, among others:
  • Linux kernel with MIPv6 extensions enabled
  • mipv6-daemon-umip, the MIPv6 daemon
  • mipv6tester, a tool to report the down time of your connectivity when changing IPv6 network
  • racoon and racoon2, key management systems for IPsec patched for IPv6 mobility support
  • scapy6, a packet forger with Mobile IPv6 capabilities
  • sonar, a mobility statistics retrieving tool

  Q: Which distributions are supported? (↑)
  A: Today, only the Debian (sid) and Ubuntu (gutsy) Linux distributions are supported. We would like to support more distributions, let us know on our support mailing list if you can help in this task.

  Q: How to use the Nautilus6 Package repository? (↑)
  A: For Debian users, add to your /etc/apt/sources.list file:
 deb http://software.nautilus6.org/packages/debian unstable/
 deb-src http://software.nautilus6.org/packages/debian unstable/

For Ubuntu users, add to your /etc/apt/sources.list file:

 deb http://software.nautilus6.org/packages/ubuntu gutsy/
 deb-src http://software.nautilus6.org/packages/ubuntu gutsy/

Then you can:

 # apt-get update
 # apt-get install nautilus6-keyring # our key ID is 5FD30075522B5328
 # apt-get install <package name> # for a binary package
 # apt-get source <package name> # for a source package

After you first run apt-get update, you will have a warning about unverified signatures. Install the nautilus6-keyring package so apt can check that nautilus6.org is the server it claims to be.

  Q: I get an error about signatures that couldn't be verified (↑)
  A: In case you have the following error:

W: GPG error: http://software.nautilus6.org unstable/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5FD30075522B5328
W: You may want to run apt-get update to correct these problems

All you need to do is install the nautilus6 keyring:

 # apt-get install nautilus6-keyring # our key ID is 5FD30075522B5328

This will give the possibility to apt to check the origin of our packages.

  Q: Where to report a bug? (↑)
  A: If you encounter a bug with one of the packages provided here or with the package repository itself, you should first explain your problem on the Nautilus6 support mailing list. There we can discuss the issue and determine where to report it efficiently, either to the respective author of the software or to the packagers. Additionally, have a look to our issue tracker.

  Q: What does "Depends: libc6 (>= 2.5) but 2.3.6.ds1-13 is to be installed" mean ? (↑)
  A: Indeed, Debian Etch comes with libc6 version 2.3. The easiest way to install a newer libc6 without upgrading the whole system to Lenny is to add the testing sources to your /etc/apt/source.list (but still keep the stable one) and perform the following commands as superuser:
 # apt-get update
 # apt-get install libc6 -t testing

Then you should be able to install any of the package or our repository.

 Nautilus6
 WIDE
Powered by PmWiki