Re: autopkgtest-build-lxd failing with bionic
On Fri, Feb 16, 2018 at 08:15:35PM +0100, Julian Andres Klode wrote: > > I think the network-online.target is the better thing to key on. > > I think we should just grep the apt output and retry if it fails with > connection error messages. The problem is a general one though. It's not specific to apt. Any time we use automation on a container or VM, we need to wait until it's finished booting. In uvtool this is what "uvt-kvm wait" provides, which currently waits for upstart runlevel 2 or systemd runlevel 5 and then asks cloud-init (since a script might also have asked cloud-init to do things it expects done when the container is "ready"). Of course that's cloud-init specific. The script may need fixing, but Ubuntu should agree upon a general answer to the common question. Even if the answer provides multiple specified points if multiple points in time are appropriate to solve different problems. So, to me, retrying apt is a hacky workaround. Robie signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: autopkgtest-build-lxd failing with bionic
On Fri, Feb 16, 2018 at 11:12:32AM -0800, Steve Langasek wrote: > On Fri, Feb 16, 2018 at 11:52:05AM +, Iain Lane wrote: > > On Thu, Feb 15, 2018 at 09:55:47PM +0100, Martin Pitt wrote: > > > Hello Iain, all, > > > > Iain Lane [2018-02-15 18:48 +]: > > > > There's a patch attached here which fixes the problem for me. I'm not > > > > sure if there's a better way to do this - basically it starts > > > > network-online.target and waits for it to become active, with a timeout. > > > > Review appreciated. > > > > I wouldn't pick on any of these: network-online.target is a sloppily > > > defined > > > shim for SysV init backwards compatibility, and may not ever get started > > > (in > > > fact, that's the goal ☺); and the container might not use networkd, so I > > > wouldn't use s-n-wait-online either. I think querying > > > Interesting. I thought that it was the systemd way to say 'I am online > > now' --- i.e. nm-online or systemd-networkd-wait-online, which is the > > question I wanted to get a positive answer to. I can see that the SysV > > implementation isn't great, but it's not clear to me that it was ill > > defined for this case. > > > > [ -n "$(ip route show to 0/0)" ] > > > This is better though, and works too. Please take a look at the attached > > patch. Thanks! :-) > > Actually no, this is racy, because the route comes up before DNS resolution > is in place. > > It's also not forwards-compatible with ipv6-only deploys. > > I think the network-online.target is the better thing to key on. I think we should just grep the apt output and retry if it fails with connection error messages. This should be fine until I have an improved solution in apt itself, one of (1) "there are no transient errors" (2) one source must have updated (3) all sources must have updated Not sure on details. Could be an option for all three. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: autopkgtest-build-lxd failing with bionic
On Fri, Feb 16, 2018 at 11:52:05AM +, Iain Lane wrote: > On Thu, Feb 15, 2018 at 09:55:47PM +0100, Martin Pitt wrote: > > Hello Iain, all, > > Iain Lane [2018-02-15 18:48 +]: > > > There's a patch attached here which fixes the problem for me. I'm not > > > sure if there's a better way to do this - basically it starts > > > network-online.target and waits for it to become active, with a timeout. > > > Review appreciated. > > I wouldn't pick on any of these: network-online.target is a sloppily defined > > shim for SysV init backwards compatibility, and may not ever get started (in > > fact, that's the goal ☺); and the container might not use networkd, so I > > wouldn't use s-n-wait-online either. I think querying > Interesting. I thought that it was the systemd way to say 'I am online > now' --- i.e. nm-online or systemd-networkd-wait-online, which is the > question I wanted to get a positive answer to. I can see that the SysV > implementation isn't great, but it's not clear to me that it was ill > defined for this case. > > [ -n "$(ip route show to 0/0)" ] > This is better though, and works too. Please take a look at the attached > patch. Thanks! :-) Actually no, this is racy, because the route comes up before DNS resolution is in place. It's also not forwards-compatible with ipv6-only deploys. I think the network-online.target is the better thing to key on. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Regarding a newer version of OpenShot
Esteemed maintainers, I would like to request that OpenShot's new version be included in the Ubuntu Software Repositories. Currently, only version 1.x is available from the repo. But it's been a few years since Ubuntu version 2.x has been released, and it uses it's own powerful library for video editing. Currently, there is a PPA but it is not yet included in the official repo. The benefits of including the software in the repository would be tremendous. I'd like to point out a few of those: 1. You'll be able to contribute bug-fixes back to the main project, which will make the project a lot more stable/better. 2. OpenShot is arguably the most user-friendly Linux video editor. It is far more powerful than imovie and windows movie maker. It is Blender for human beings, so to speak, in terms of video editing. Having it in the repo would help the users get a really friendly video editing app, and would hopefully increase overall user satisfaction, too. 3. Some of the Ubuntu maintainers might love the project and start contributing to it on a regular basis --- which is precisely what this awesome project currently needs. 4. Because the software would be exposed to a lot more users, we might get new enthusiastic community members who might help in the development of the program. That would be another win for Linux Filmmaking. Therefore, in light of the aforementioned benifits, I would like to humbly request the esteemed maintainers to include OpenShot 2.x in the official Ubuntu repositories. Here are the links: Official Website: https://www.openshot.org/ PPA: https://www.openshot.org/ppa GitHub: https://github.com/openshot With Regards, - A well-wisher of the OpenShot project -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: autopkgtest-build-lxd failing with bionic
On Thu, Feb 15, 2018 at 12:00:41PM -0800, Steve Langasek wrote: > It's a bit odd to be "start"ing a target in this manner. Is it even > necessary to start the target, or would it be sufficient to just check > is-active in a loop? Yeah, it is - it needs to be pulled in by something to get started, but in this case it's not so we do the same thing in code. It's like this so you don't end up blocking the boot unnecessarily waiting for the network to be "up" when nothing needs it to be. Doesn't matter any more though for this case. :-) -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Launchpad i386 build: Memory exhausted
Hello everyone, I'm packaging latest MAME 0.194 and it builds fine on my PPA. Unfortunately, link fails for i386 due to virtual machine memory issues: /usr/bin/ld: final link failed: Memory exhausted You can find a full log for build here: https://launchpadlibrarian.net/357194916/buildlog_ubuntu-artful-i386.mame_0.194+dfsg.1-0ubuntu1~ppa2~artful1_BUILDING.txt.gz and also here in case I got struck by the greatest idea and try a new build :) https://pastebin.com/dZLResCK Please note I've already put great care in tweaking linker options to reduce memory consumption, with no luck. I've already faced this issue in backporting, but it never occured with current release. It's worth noting that the default compiler in Artful (gcc 7) is also the recommended compiler by upstream developers, so forcing a different release doesn't look an option either. It would be nice to have a working i386 build on my PPA, but what I care more is uploading Mame 0.194 to Bionic. Does anyone know whether virtual machines for official Ubuntu releases have more resources, specifically more memory? Should I try uploading the tarball and see? What happens if I get the same memory issue, would I be able to downgrade to 0.193? I'm looking forward for any kind advice, thank you in advance! :) Cheers, Cesare -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
