Closing due to the latest release of flake8 and D4232.

I went ahead and built spyder and installed it and @sunnyflunk is correct. Updating pylint to 2.0 or above would mean that spyder will not work correctly. As far as I can see there could be three solutions to this. The first being to separate the pylint package into python2/3 versions keeping the python 2 version at 1.9 which IIRC will have python 2 support until 2020. The second solution would be to leave pylint at version 1.9 and see what the spyder developers do about the depreciation of python 2 support for pylint. The last would be to remove spyder but this seems a little extreme.

Sorted rundeps

I missed that you accepted this before I updated it to 2.0.1. Sorry it's only a minor change which fixes a crash.

Update pylint to 2.0.1

I dropped Python 2 support because pylint itself no longer supports Python 2. Here is an issue which was closed on the 9th of May saying that pylint 2.0 will be dropping support for Python 2. This is the same for python-astroid.

Ah okay that's good to hear. In that case the testing was successful. I was able to login to Battle.Net.

I will point out that although I am able to login to Battle.Net using this wine version I do get a 'program error' popup. Battle.Net seems to run perfectly fine anyway though. I have tried it with Wine 3.12 and 3.13 and I get the same error.

Updated Atom to 1.28.1. Thanks alecbcs for letting me know.

Update Atom to 1.27.2

In terms of building Atom 1.27.1 afaik I'm not doing anything in particular. I'm building with Solbuild (1.4.2) using the unstable-x86_64 image. I've included a screenshot showing the Atom version I have installed.

Updated diff info. I accidentally closed arc.

Removed the depends on D2885.

This package should not be upgraded until the next version of 'flake8'. The new dependencies are required otherwise a 'DistributionNotFound' error will be thrown leaving flake8 unusable.

Updated license

Forgot to update license in pspec_x86_64.xml

Updated license

Okay. I will go through my current open patches and update them where necessary.

After looking back at this differential I believe I misunderstood when to use 'Depends'. Updating 'pylint' does not *require* updating 'python-astroid' however as it states of the GitHub page the later the version of 'python-astroid' the better. I'll leave the 'Depends' in the differential for now unless instructed otherwise.

I didn't know you could do that^^. I will do from now on. Updated change log available here.

No need to have a separate package

Package has now been updated to a later version

Thanks for the link to the packaging practices. I have given them a good read over; the yauto.py script does indeed make the job a lot easier. I see no reason that they can't be shipped with eopkg it defiantly doesn't need to be a separate project.

After re-reading the inclusion policy. I see the mistake I've made here; I should have created a package request to see it would be accepted into the repository. I will stick to updating packages for now. Thanks again.

Oh no it's just a package that I've needed in the past and it was trivial to package up. I thought package requests were just if you didn't know how to package for yourself; I can submit a request if that's the correct route to take. I will read of over the package inclusion policy again.

Replaced libjpeg-turbo-devel with pkgconfig(libturbojpeg)

Fixed error with 'python-pillow-devel' package.
The headers directory was moved from 'libImaging' -> 'src/libImaging'.

Changed to new 'programming.ruby' component

Changed to new 'programming.ruby' component

Changed to new 'programming.ruby' component

Okay that sounds good ill try build the packages again whenever you are ready. Thanks for the quick reply!

Scratch that It seems to be temperamental. I've just tried rebuilding 'ruby-multi-json' and get the same error now?

I've just tested building this package with '%gem_install' which builds the 'ruby-multi-gem' package successfully. However not the other two packages. I've added a screenshot which shows the error I'm getting with 'ruby-neovim' and 'ruby-msgpack' but not 'ruby-multi-json'

Hi Josh, Sorry first time doing this; what is it that you want in terms of test plan? I'm also guessing you want the change log in the 'arc diff' message?