So here is latest on on new packages and sponsorship.
seb128 wrote
“It seems “moved to universe” means “added to Ubuntu” there, you should get those in the sponsoring queue as described on UbuntuDevelopment/NewPackages - Ubuntu Wiki”
Khurshid is working on that. We cannot do anything till we set up seeds, then subscribe to sponsorship, then , perhaps we will get an ISO build in the on the servers.
I always wonder, how come what’s unstable to Debian become stable to Ubuntu? Ubuntu is using Debian’s unstable packages, while Debian never releases any official distro made out of those unstable packages. True, you can install unstable directly from netinstall.
The only difference between Sid (unstable) based distros and Ubuntu is that Ubuntu repackages somewhat differently than Debian, and these packages are not interchangeable. The other Sid based distro developers always give a warning that those distros might break because of the instability, while Ubuntu doesn’t. So, the question, how come what’s unstable to Debian become stable to Ubuntu? What guarantee can Ubuntu give on Debian unstable packages that they are (only) stable, if you use them in Ubuntu?
Go inside of the folder and run ./update in terminal.
It will start downloading source from main, restricted and universe and after completion it will automatically modify debian/changelog. It could take a while.
Don’t push back using git push. This is just for testing. Post terminal outputs to https://pastebin.ubuntu.com/.
ventrical@ventrical-Precision-WorkStation-T3400:~$ dir
Desktop Public
Documents Templates
Downloads ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1
examples.desktop ubuntu-unity-meta_1.407+201711160715~ubuntu18.04.1.dsc
Music ubuntu-unity-meta_1.407+201711160715~ubuntu18.04.1.tar.xz
Pictures Videos
ventrical@ventrical-Precision-WorkStation-T3400:~$ ./update
bash: ./update: No such file or directory
ventrical@ventrical-Precision-WorkStation-T3400:~$
so this is second set of files it asks to install along with /devscripts so we should instruct that these extra files will be downloaded when we execute the script in the command line.
ventrical@ventrical-Precision-WorkStation-T3400:~/ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1$ ./update
./update: 13: exec: germinate-update-metapackage: not found
ventrical@ventrical-Precision-WorkStation-T3400:~/ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1$
So after many updates there is one small error ‘could not open structure’.
! Could not open STRUCTURE from checkout of (any of):
! bzr+ssh://bazaar.launchpad.net/~unity7maintainers/ubuntu-seeds/ubuntu-unity.bionic
ventrical@ventrical-Precision-WorkStation-T3400:~/ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1$
I went to my working desktop(xenial) that already had debootstrap installed and I did an update and now it is stuck in a loop and I can’t get rid of this package. I rebooted, logon, log off etc// This was a machine with working bzr+ssh.
ventrical@ventrical-MS-7798:~/ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1$ ./update
[info] Initialising ubuntu-unity-* package lists update...
/usr/bin/germinate-update-metapackage: Installed debootstrap is older than in the previous version! (1.0.78+nmu1ubuntu1.5 < 1.0.81ubuntu3)
ventrical@ventrical-MS-7798:~/ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1$
I tried synaptic but it keeps coming up with the above message when I do-
I figured it out. I assumed ubuntu-unity-meta-1.407+201711160715~ubuntu18.04.1 was the new version, but it isn’t as automatic build was disabled. I have initiated new builds. Try with new version and make sure you have bzr configured on your machine.