On Mon, Mar 7, 2016 at 2:59 PM, Bruno Friedmann wrote:

On lundi, 7 mars 2016 13.46:42 h CET Todd Rme wrote:

...

Several packages in devel:languages:python3 are not building due to incompatibilities with the current version of their dependencies. These packages are apparently abandoned upstream, having no upstream activity in at least a year. With the release of upcoming switch to python 3.5, these will likely stop working entirely.

You mean you will create a Staging repo and test 3.5 build and fix there, or for the sake of the community, you just want to go the hardway and destroy dlp3 ?

The 3.5 builds have been tested for dlp3 using the bleeding_edge_python_Factory for months. A lot of people, myself included, have been working very hard testing and making sure all the packages work. openSUSE is currently testing other packages and found one other problem. I submitted a fix for that a few minutes ago. However, there are a few packages that don't work for any build target on any version of openSUSE or SLES with any version of python. These are the ones I am talking removing. They most likely will refuse to install with a new version of the python3 package, because any binary for them that still exists was built against the old version of the python3 package.

Now a question arise, we (community) have to bother still about python2 and python3 equivalence ? So if a fix is made in python3 package, how to backport this one to the python dlp repo?

Manually, currently. But that is a completely different issue.

Did we still have to manually work on 2 specs 2 sources in 2 differents repositories, or there's a plan to merge everything back and use only two spec but one source?

If Fedora is able to build all its python package with only one spec why we are not able?

There has been talk about that, but currently it isn't set up. But again, that is a completely different issue.

...

I would like to remove them from the repo one week from today (next Monday). So if you need these packages, please either copy them to your home repo or patch them to get them working properly.

Hard to do when they already have been removed no?

I restored them a while ago. I already emailed you about that.

...

The packages:

python3-PyAVM - no release or upstream activity in one year python3-South - no release or upstream activity in more than a year, upstream website is gone

Those two were building and working perfectly on a TW. I use them everyday ...

No, they weren't. Look at the build results. They have been like that for months: https://build.opensuse.org/package/show/devel:languages:python3/python3-PyAV... https://build.opensuse.org/package/show/devel:languages:python3/python3-Sout...

...

python3-pyramid_handlers - no release or upstream activity in 3 years python3-pyramid_zcml - no release or upstream activity in one year

You want to do this next week, but you already remove them. Some code still work as expected, perhaps that's how some others define mature?

They do not build. Again: https://build.opensuse.org/package/show/devel:languages:python3/python3-pyra... https://build.opensuse.org/package/show/devel:languages:python3/python3-pyra...

Please reinstance those package and bring me as bugowner and maintainer as I've asked those status during first submit.

I already did that before I sent my previous email.

It would be also cool to warn people on -packaging list next time ;-) At least to drive interested people to the right thread.

I figured if someone really cared about the packages they would have done something in the 6 months or more that the packages have been failing. Apparently that was a faulty assumption.

Okay we can't for the moment use the wiki to create a page, and build a constructive discussion about the plan, communicate about it in advance, and get feedback.

I'm certain your plan seems perfect from your point of view, but reality is not.

What do you propose we do instead? As I said, leaving non-building packages in there slows down the entire project. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

python3-SoOn Mon, Mar 7, 2016 at 3:43 PM, Bruno Friedmann wrote:

On lundi, 7 mars 2016 15.22:15 h CET Todd Rme wrote:

...

On Mon, Mar 7, 2016 at 2:59 PM, Bruno Friedmann wrote:

...

On lundi, 7 mars 2016 13.46:42 h CET Todd Rme wrote:

...

Several packages in devel:languages:python3 are not building due to incompatibilities with the current version of their dependencies. These packages are apparently abandoned upstream, having no upstream activity in at least a year. With the release of upcoming switch to python 3.5, these will likely stop working entirely.

You mean you will create a Staging repo and test 3.5 build and fix there, or for the sake of the community, you just want to go the hardway and destroy dlp3 ?

The 3.5 builds have been tested for dlp3 using the bleeding_edge_python_Factory for months. A lot of people, myself included, have been working very hard testing and making sure all the packages work. openSUSE is currently testing other packages and found one other problem. I submitted a fix for that a few minutes ago.

However, there are a few packages that don't work for any build target on any version of openSUSE or SLES with any version of python. These are the ones I am talking removing. They most likely will refuse to install with a new version of the python3 package, because any binary for them that still exists was built against the old version of the python3 package.

...

Now a question arise, we (community) have to bother still about python2 and python3 equivalence ? So if a fix is made in python3 package, how to backport this one to the python dlp repo?

Manually, currently. But that is a completely different issue.

...

Did we still have to manually work on 2 specs 2 sources in 2 differents repositories, or there's a plan to merge everything back and use only two spec but one source?

If Fedora is able to build all its python package with only one spec why we are not able?

There has been talk about that, but currently it isn't set up. But again, that is a completely different issue.

...

...

I would like to remove them from the repo one week from today (next Monday). So if you need these packages, please either copy them to your home repo or patch them to get them working properly.

Hard to do when they already have been removed no?

I restored them a while ago. I already emailed you about that.

...

...

The packages:

python3-PyAVM - no release or upstream activity in one year python3-South - no release or upstream activity in more than a year, upstream website is gone

Those two were building and working perfectly on a TW. I use them everyday ...

No, they weren't. Look at the build results. They have been like that for months: https://build.opensuse.org/package/show/devel:languages:python3/python3-PyAV... https://build.opensuse.org/package/show/devel:languages:python3/python3-Sout...

...

...

python3-pyramid_handlers - no release or upstream activity in 3 years python3-pyramid_zcml - no release or upstream activity in one year

You want to do this next week, but you already remove them. Some code still work as expected, perhaps that's how some others define mature?

They do not build. Again: https://build.opensuse.org/package/show/devel:languages:python3/python3-pyra... https://build.opensuse.org/package/show/devel:languages:python3/python3-pyra...

...

Please reinstance those package and bring me as bugowner and maintainer as I've asked those status during first submit.

I already did that before I sent my previous email. Cool

...

It would be also cool to warn people on -packaging list next time ;-) At least to drive interested people to the right thread.

I figured if someone really cared about the packages they would have done something in the 6 months or more that the packages have been failing. Apparently that was a faulty assumption.

My bad too, as I was pretty sure to be maintainer, then hermes will have bogus me with failing state ... Seems I should have check it more carefully. I will do my shopping list next week-end and ask maintainer role for all of those I need.

...

...

Okay we can't for the moment use the wiki to create a page, and build a constructive discussion about the plan, communicate about it in advance, and get feedback.

I'm certain your plan seems perfect from your point of view, but reality is not.

What do you propose we do instead? As I said, leaving non-building packages in there slows down the entire project.

I'm also not in favor of, but even if it's still work, it is quite easy to ping the last maintainer in the changelog to ask him if he care or not.

That's what I'm doing normally in my process when I need a fix or upgrade of one package. ;-)

both of package are already starting build, was just a question of bogus test and upstream has an opened issue for that (January this year).

expect an sr soon ;-)

Bruno has gotten python3-pyramid_zcml and python3-pyramid_handlers working, and I have gotten python3-PyAVM working. However, python3-South is still failing. It appears that this package has been rendered unnecessary by Django 1.7, and thus has been abandoned upstream. It will not ever be made to work with modern versions of Django. If anyone still needs it, please get it into your home repository now. On the web interface you can branch it, then above the file list click "(show unmerged sources) ", then delete the "_link" file. Links will be broken when the package is deleted in devel:languages:python3. openSUSE:Factory has switched to python 3.5.1, so as soon as it lands in Tumbleweed this package will become uninstallable (although it is already non-functional with the version of django it is published alongside). I said I wanted to remove it yesterday, but with the transition to python 3.5.1 underway I will wait until 3.5.1 is published in Tumbleweed. This could happen at any time, so please do not wait. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org