Rebuild on Ubuntu instead of Debian

[JuiP]

Few errors after trying to rebuild on ubuntu. ( Since Ubuntu is derived from Debian, most of things should work fine)

P: Restoring bootstrap stage from cache...
[2020-02-02 01:11:14] lb_bootstrap_copy 
[2020-02-02 01:11:14] lb_bootstrap_cdebootstrap 
[2020-02-02 01:11:14] lb_bootstrap_debootstrap 
P: Begin bootstrapping system...
[2020-02-02 01:11:14] lb_testroot 
P: If the following stage fails, the most likely cause of the problem is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)... 
W: Cannot check Release signature; keyring file not available /usr/share/keyrings/debian-archive-keyring.gpg
I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file http://archive.ubuntu.com/ubuntu/dists/buster/Release
P: Begin unmounting filesystems...
P: Saving caches...
chroot: failed to run command ‘/usr/bin/env’: No such file or directory
normal successful completion

I tried fixing the mirror configuration and caching proxy by ensuring that these packages were up-to-date: qemu-user-static, binfmt-support,qemu-kvm qemu-utils,ubuntu-keyring and changed to the country specific mirror files. Nothing really made a difference.

Later I found the index of ubuntu archives from where the release file was supposed to be fetched: http://in.archive.ubuntu.com/ubuntu/dists/bionic/ Since it had bionic instead of buster I fixed the source code auto->config file-> and changed the distribution to bionic. Now I didn't get the same error as before however I ended up with a new set of errors-

Reading package lists...
Building dependency tree...
Reading state information...
Package gir1.2-telepathyglib-0.12 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package intltool is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package python-gi-cairo is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package metacity is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package lightdm
E: Unable to locate package python3-empy
E: Unable to locate package icon-naming-utils
E: Unable to locate package gnome-common
E: Package 'intltool' has no installation candidate
E: Package 'python-gi-cairo' has no installation candidate
E: Unable to locate package python-pygame
E: Unable to locate package python3-decorator
E: Package 'gir1.2-telepathyglib-0.12' has no installation candidate
E: Unable to locate package python3-xapian
E: Unable to locate package python3-pygame
E: Unable to locate package gir1.2-abi-3.0
E: Couldn't find any package by glob 'gir1.2-abi-3.0'
E: Couldn't find any package by regex 'gir1.2-abi-3.0'
E: Package 'metacity' has no installation candidate
E: Unable to locate package telepathy-mission-control-5
E: Unable to locate package telepathy-salut
E: Unable to locate package telepathy-gabble
E: Unable to locate package gstreamer1.0-espeak
E: Couldn't find any package by glob 'gstreamer1.0-espeak'
E: Couldn't find any package by regex 'gstreamer1.0-espeak'
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
normal successful completion

Should I go ahead with fixing all these errors too, just to rebuild the sugar-live-build on ubuntu?

[quozl]

Thanks. I knew about these problems, and have no plans to fix them. Sugar Live Build is written and tested against Debian. Ubuntu have made their own incompatible changes, the least of which is the name of the distribution.

You're welcome to make a fork that works on Ubuntu, and let me see it, and I may take parts of it, but at this stage I don't need Sugar Live Build to run on Ubuntu at all; I use a Debian schroot as isolation.

For building Ubuntu based Sugar distributions, I use an OLPC OS specific builder that remasters the distribution media by adding packages from an archive.

If you just wanted to use Sugar Live Build, you don't need to rebuild it. Just download the ISO.

[JuiP]

Alright, Thanks for help. :) I had already got the Sugar Live Build running on the virtual machine, I was just trying to test sugar-live-build compatibility with ubuntu, when I came across this issue. I now understand that ubuntu mode support is not a priority at the moment.

Nevertheless, I would like to mention the changes I tried making to work around the issue, just in case someone else would also like to continue making changes.

1. --mode ubuntu added in the auto folder config file.
2. sudo gedit /etc/apt/sources.list

   deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse

3. Added in the auto folder config file --apt-ftp-proxy packages http://in.archive.ubuntu.com/ubuntu/dists/bionic/main/debian-installer/binary-amd64/ | gzip > Packages.gz

I have not investigated further but so far the error is not resolved. It might be live-build which is not copying the files properly, it might be apt-ftparchive which is not generating the Packages file correctly or it might be apt-get not finding the package.

[quozl]

Thanks. If you do get it working in Ubuntu, please offer to support it for others. It is beyond my own needs.

Looking at the errors you reported, the most recent were missing packages, and those packages are not missing when a properly configured Ubuntu 18.04 Bionic system is tested. The package names can be independently verified by visiting a URL of packages.ubuntu.com/N, e.g. https://packages.ubuntu.com/metacity. So there's something wrong with either the archive, transparent proxy servers, or your configuration of debootstrap.

[JuiP]

Yes, I already verified the package names. Out of all the things you mentioned I just seemed to have overlooked checking the configuration of debootstrap. I will surely offer to support it for other Ubuntu users if it all I get it working.