Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
FWIW -- about to upload, cosmetics now On Mon, 25 Jun 2018, Graham Inggs wrote: > On 25 June 2018 at 18:21, Yaroslav Halchenko wrote: > > I am loosely involved and highly interested ;-) If someone could help > > maintaining it, I would appreciate. > > meanwhile since there were no other activity regarding this issue, I > > will look into updating it for 0.14.0 > In case you didn't receive Lumin's earlier reply: > On 25 June 2018 at 13:45, Lumin wrote: > > I'm working on this. It would take days for me to finish it > > due to my final terms... But I think it doesn't matter because > > we still have a month until AUTORM. > > https://salsa.debian.org/lumin-guest/skimage/commits/master -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
On Mon, 25 Jun 2018, Graham Inggs wrote: > On 25 June 2018 at 18:21, Yaroslav Halchenko wrote: > > I am loosely involved and highly interested ;-) If someone could help > > maintaining it, I would appreciate. > > meanwhile since there were no other activity regarding this issue, I > > will look into updating it for 0.14.0 > In case you didn't receive Lumin's earlier reply: > On 25 June 2018 at 13:45, Lumin wrote: > > I'm working on this. It would take days for me to finish it > > due to my final terms... But I think it doesn't matter because > > we still have a month until AUTORM. > > https://salsa.debian.org/lumin-guest/skimage/commits/master oops -- missed it somehow... (travel... still digging through emails), hopefully we didn't duplicate much of effort. I'm building a sample package ATM, here is the changelog summary of what I've done: skimage (0.14.0-1) unstable; urgency=medium * Fresh upstream release - should resolve FTBFS due to incompatibility with NumPy 1.14 (Closes #901377) * d/patches - refreshed patches skipping on some archs. Use testing.skipif instead of explicit import of skipif into the namespace - remove_deprecated_box-forced.patch - removed since was CPed from upstream -- Yaroslav Halchenko Mon, 25 Jun 2018 12:26:51 -0400 -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
On 25 June 2018 at 18:21, Yaroslav Halchenko wrote: > I am loosely involved and highly interested ;-) If someone could help > maintaining it, I would appreciate. > > meanwhile since there were no other activity regarding this issue, I > will look into updating it for 0.14.0 In case you didn't receive Lumin's earlier reply: On 25 June 2018 at 13:45, Lumin wrote: > I'm working on this. It would take days for me to finish it > due to my final terms... But I think it doesn't matter because > we still have a month until AUTORM. > > https://salsa.debian.org/lumin-guest/skimage/commits/master
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
On Sat, 23 Jun 2018, Graham Inggs wrote: > Hi Stefan, Yaroslav > On 22 June 2018 at 21:15, Stefan van der Walt wrote: > > That sounds like a good solution to me. That said, scikit-image in > > Debian is now maintained by the science team, so it would be good to > > hear from a member of that team. > Lumin is a member of Debian Science Team. :) > According to Science Team's policy [1], > "The Maintainer field should be "Debian Science Maintainers > ". > You should also add yourself to the Uploaders field. Doing so shows > your involvement and interest in the package. Developers listed in > Uploaders will take care of maintenance, bug reports and other QA > work, helped by the Debian Science team." > You are listed as one of Uploaders for skimage. If you, for whatever > reason, are no longer involved or interested in the skimage package, > then we need to update the Uploaders field to reflect reality. Should > your name be removed from Uploaders with the next upload? > Yaroslav, are you still involved or interested in skimage? Sorry for the delay. I am loosely involved and highly interested ;-) If someone could help maintaining it, I would appreciate. meanwhile since there were no other activity regarding this issue, I will look into updating it for 0.14.0 Cheers -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
Hi Stefan, Yaroslav On 22 June 2018 at 21:15, Stefan van der Walt wrote: > That sounds like a good solution to me. That said, scikit-image in > Debian is now maintained by the science team, so it would be good to > hear from a member of that team. Lumin is a member of Debian Science Team. :) According to Science Team's policy [1], "The Maintainer field should be "Debian Science Maintainers ". You should also add yourself to the Uploaders field. Doing so shows your involvement and interest in the package. Developers listed in Uploaders will take care of maintenance, bug reports and other QA work, helped by the Debian Science team." You are listed as one of Uploaders for skimage. If you, for whatever reason, are no longer involved or interested in the skimage package, then we need to update the Uploaders field to reflect reality. Should your name be removed from Uploaders with the next upload? Yaroslav, are you still involved or interested in skimage? Regards Graham [1] https://science-team.pages.debian.net/policy/#idm66
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
On Fri, 22 Jun 2018 08:57:47 +, Lumin wrote: > Briefly speaking, we plan to team-upload skimage (= 0.14.0) to resolve > this RC bug if the original maintainers allows us to do so. We'll try > to fix this after one week if the original maintainers didn't take > action. That sounds like a good solution to me. That said, scikit-image in Debian is now maintained by the science team, so it would be good to hear from a member of that team. signature.asc Description: PGP signature
Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)
Dear skimage maintainer, Briefly speaking, we plan to team-upload skimage (= 0.14.0) to resolve this RC bug if the original maintainers allows us to do so. We'll try to fix this after one week if the original maintainers didn't take action. skimage failed to build from source since numpy (>= 1.14) was uploaded to Debian unstable, and the cause of the trouble is exactly numpy api changes. In upstream repo, there are several commits that adapts the source to the api changes but they don't apply to Debian's source without change. So I think the most efficient way is to import 0.14.0 . Please tell us if we can fix this RC by importing skimage (= 0.14.0). Thanks. signature.asc Description: PGP signature
