Re: Cosmic Cuttlefish (to be 18.10) feature freeze
On 08/24/2018 11:59 AM, Andreas Hasenack wrote: > On Fri, Aug 24, 2018 at 1:52 PM Steve Langasek > wrote: >> >> Dear Developers, >> >> As per the release schedule, Cosmic is now in Feature Freeze. >> >> Ideally you will all now be focusing on bug fixing and not on getting >> new features into the release. >> >> As is the custom, packages that have been uploaded to cosmic-roposed prior >> to the feature freeze deadline, but have gotten stuck there, remain >> candidates for fixing between now and release. > > Does this custom apply to NEW packages as well? For example, I had > squid (which replaces squid3) uploaded on monday Aug 20th > (https://launchpad.net/ubuntu/cosmic/+queue?queue_state=0&queue_text=squid), > but it's still in NEW. > > Besides the source package rename, (squid3 -> squid), it is also a new > major version (3.5 -> 4.1). I don't speak for the Release Team, but in my experience as an Ubuntu Developer, Feature Freeze doesn't apply to things already in devel-proposed and NEW packages. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- 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: Proposal: Let's drop i386
Hello, On 05/09/2018 04:29 PM, Walter Lapchynski wrote: >> here are some i386 to amd64 ratios for 18.04: >> Lubuntu cdimage - 0.87 > > And there is my concern. That says the vast majority of Lubuntu's users > are using i386. The question becomes whether or not they have to. There > has been documentation all over the place to download i386 if you don't > know which is the right one and so people may still be running on this. > So maybe the number is skewed. But if it's not, does this mean Lubuntu > becomes irrelevant? You're misreading the statistics. *Less* people use i386, not more. 87 i386 users per 100 amd64 users. Additionally, with Lubuntu modernizing a bit, I would argue that Lubuntu can and will still stay relevant in the future. This is before we dropped LXDE, and it's the LTS. We can judge whether or not Lubuntu is still relevant by seeing how the LXQt transition plays out. Also, to be fair, Lubuntu 18.04 could be considered for sort of a niche audience; people who need to run Linux (specifically, with LXDE and Ubuntu) on older machines. Lubuntu's LXQt transition does modernize things a bit, while still preserving some of those light selling points. I would also not use this as a determining factor, because we have no idea how things will look three years from now. My best guess is that i386 users will drastically diminish. >> The first step would be to all agree on dropping images/installers but >> we should keep the end goal of dropping the port in mind ideally soon >> as well. > > Maybe keeping only the netboot image might make sense? If the port goes away entirely, so will the netboot images. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- 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: Proposal: Let's drop i386
Hello, On 05/09/2018 07:03 PM, Matthias Klose wrote: > I have never seen yours or Olivers name recently fixing i386 and autopkg test > failures. Should be easily to do for you, it's free, and there's no work > involved. I would agree with this point; although I rarely have had to fix i386-only issues, they come up now and then. With our Proposed Migration[1] infrastructure, it is extra work to maintain *any* additional architecture. "Free from Debian" isn't necessarily an excuse either. Often times, issues that we need to fix are Ubuntu-specific. With the Debian Release Team starting to embrace autopkgtesting for testing migration, this improves things, but not completely. By that same logic, where's our RISC V port? What about SPARC64? The answer I have consistently gotten (and agree with, for that matter) is that it takes time, money, and infrastructure to maintain these ports. Certainly, if there is good cause to remove a port from the archive without causing many issues, saving developer time is preferred. [1] https://wiki.ubuntu.com/ProposedMigration -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 signature.asc Description: OpenPGP digital signature -- 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: Updating Python-vtk for Xenial
Hi there, > We are currently using python-vtk6 on the apt repository. We have tried > installing vtk8 via their own documentation but are unable to build it > for Ubuntu. We very much need vtk8 on ubuntu and are unsure as to how to > get vtk8 on the repository. I'll be happy to assist you with this, but I can see two routes here: 1. Backport the package to a PPA and enable the PPA on all of your systems. 2. Use the official Ubuntu Backports repository. Here is the documentation for that: https://wiki.ubuntu.com/UbuntuBackports vtk8 will probably not land in xenial-updates because of our SRU procedure, which you can find here: https://wiki.ubuntu.com/StableReleaseUpdates but we can use the other methods described to get it packaged. > I really look forward to hearing back from you, thanks for your time. If you have any more questions, or if you would like me to directly help you backport it, please feel free to email me or ping me on IRC. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- 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: gimp cage tool - fix in 16.04?
> In other words, it was only committed to master after the gimp-2-8 > branch was made; and there's no evidence that this was cherry-picked > onto the gimp-2-8 branch (from a quick log inspection). It indeed does > not appear that this commit is in 2.8.18, although it should be in 2.9.4 > (an unstable-series release). It might be worth asking upstream whether > it can be fixed in the 2.8 series. Nice catch, thank you. I *thought* that was on master at the time of the git tag, but the web interface tricked me. I learned a new git command today. ;) So in other words, Robert, it's very unlikely that the package I uploaded to that PPA will fix your problem. We'll have to wait for that patch to be backported, and I don't know if there's a clean way to do that as that branch might be far ahead of master. I'll keep the PPA there and I'll keep my eye out for when that gets into master (so it can be applied easily). I'll dig into this more in a bit, and I'll see if I can comment on that bug, citing this email thread. Thanks again, Colin! -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- 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: gimp cage tool - fix in 16.04?
Hello Robert, I'm doing some casual poking around at the moment to see how easy it would be for this patch to be applied. > The cage tool in 2.8.16-1ubuntu1.1 is broken. Details can be found here: > https://bugzilla.gnome.org/show_bug.cgi?id=678085 > > If I am not mistaken 2.8.18 does not fix the issue. At least the > changelog at [1] does not indicate anything about a fix and target > milestone of the bug is 2.10. Do you see any chance that the fix for > this issue will be made available via patch in 16.04? I think otherwise. Look at when this Git tag was set upstream: https://git.gnome.org/browse/gimp/tag/?h=GIMP_2_8_18 tag date2016-07-13 20:27:19 (GMT) This is the date for 2.8.16: tag date2015-11-21 18:04:13 (GMT) Let's look at the timestamps on the two commits that were done to fix this problem: 2016-02-02 11:21:15 (GMT) 2016-02-07 17:50:11 (GMT) So unless there is some magical way to ensure commits don't land in a Git tag (which I highly doubt they would even WANT to do either way), it should be fixed. Since you know this issue better than I do, I've backported Yakkety's GIMP (2.8.18-1) to Xenial and I put it in ppa:tsimonq2/gimp-xenial for you to test. If this solves your issue, then I'll work on getting a debdiff for you to test against the Xenial version. It will most likely take (at least) a half an hour for all the sources to publish, so if you are reading this email right after I send it, please wait. :) After that, the process is fairly simple. Either of us would file a bug in Launchpad, then the Stable Release Update process[1] is followed to get it into Xenial[2]. Thanks for bringing this up! :) [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] This is why I need to know if it exists in Yakkety, so I know if the fix needs to be uploaded to Yakkety first, because that's usually how the procedure goes. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on freenode and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -- 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: Outdated arduino package?
Greetings, On 07/23/2016 10:02 AM, Starbeamrainbowlabs wrote: > I'm emailing to ask about the official arduino package in the Ubuntu > repositories. It's currently at version 1.0.5, yet the latest version on > the arduino website is version 1.6.9. It looks like this package hasn't > been updated since ~May 2013. I've carbon-copied the Debian maintainers, as this isn't a problem with Ubuntu, but there isn't an up-to-date Debian package. > I looked at setting up my own ppa on launchpad and repackaging the > arduino IDE myself, but instructions I found were so horrendously > complicated and mentioned so many things that I hadn't heard of (and I'm > fairly confident in a terminal) I've given up :( > > Is it possible to have the arduino package in the official Ubuntu ppa > for xenial updated please? If not, I'm open to having another go at > packaging it myself, but I currently can't find any tutorials out there > that explain the process adequately. The Debian maintainers should be able to help you if you wish, either way, it's brought to their attention and they should be able to explain why it isn't up-to-date. It needs to be updated in Debian because packages in Debian flow down to the Ubuntu development release, and we can do something about getting in in 16.04 then. The latest version in Debian[1] is 1.0.5 as well, but in experimental, they have 1.5.6.2, so it looks like they have been working on it a bit. Thanks for pointing this out! [1] https://packages.debian.org/search?keywords=arduino&searchon=names&suite=all§ion=all -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- 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: Installation Media and supportability of i386 in 18.04 LTS Re: Ubuntu Desktop on i386
Greetings, Let's also factor in flavors like Lubuntu that aim to use very minimal resources and that have the ability to run with ~ 300 MB of RAM on an i386 machine. While I understand modern applications are removing i386 support, we have a nice application base for Lubuntu for both LXDE and LXQt that provides a minimal but yet functional desktop environment and we have people to maintain these applications. So I'm sort of going with what Mark is saying. Please also factor this in the discussion. -- Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- 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: serious xfwm4 bug fixed last May, but still not in xenial
Is the fix in Debian Stretch or Sid? If not, you should also alert the maintainers there. I understand that because it's an urgent fix, this may not be ideal, but it's something to consider. Simon Quigley tsimo...@ubuntu.com tsimonq2 on Freenode -- 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: about the upgrade
If I remember correctly, the upgrade just updates all packages from the vivid versions to the wily versions with some extra little cleanup(please correct me if I am wrong). If you would like to compare each package in the repository, you can use the following link, replacing vivid with wily when you want to get the package version for wily. http://packages.ubuntu.com/vivid/apport -- Have a nice day, Simon Quigley tsimonq2 Contact for the Ubuntu US Wisconsin LoCo Team Lubuntu Quality Assurance Tester -- 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: Fwd: Using Devel as an Alias in my sources.list for a, "rolling" Ubuntu (Simon Quigley)
Ok, thank you -- Have a nice day, Simon Quigley tsimonq2 Contact for the Ubuntu US Wisconsin LoCo Team Lubuntu Contributor -- 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
Fwd: Using Devel as an Alias in my sources.list for a "rolling" Ubuntu
Good afternoon, I have heard something about replacing the current Ubuntu codename with devel in your sources.list to make a truly rolling Ubuntu, as it would always be on a development release. Could I do this and have a working result? Are there any downfalls? Is this even possible? -- Have a nice day, Simon Quigley tsimonq2 Contact for the Ubuntu US Wisconsin LoCo Team Lubuntu Contributor -- 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
