Re: dcm2niix -- I have an intent to take over (still under Debian Med team), objections?
On Tue, Dec 04, 2018 at 06:39:15AM +0100, Ghislain Vaillant wrote: > > I would be happy to move it to salsa. I just pointed to it as the one > > we currently use > > > > I guess I would then move it to dcm2niix-epoch1 smth like that (on salsa > > i.e.) so previous versions could be found from the original > > dcm2niix repo (to which I would also add a commit obliterating > > everything and stating to look into that -epoch1 repo) > > > > Please use the original packaging work on salsa and keep the history intact. > > I don't see what would prevent you from rebasing the work done on > Neurodebian on top of mine. Epoch bumps don't justify history rewrites or > new repositories, imo. I agree with Ghislain. Feel free to simply rebase your packaging but please keep the same repository name. We have the policy that the package resides in a repository with the same name as the source package (and some of our tools are relying on this) and I do not see any reason to diverge from it. There is also no point in keeping an unused repository of the old packaging around. Kind regards Andreas. -- http://fam-tille.de
Re: dcm2niix -- I have an intent to take over (still under Debian Med team), objections?
Le lun. 3 déc. 2018 à 22:39, Yaroslav Halchenko a écrit : > > On Mon, 03 Dec 2018, Andreas Tille wrote: > > > Hi Yaroslav, > > > On Mon, Dec 03, 2018 at 03:36:19PM -0500, Yaroslav Halchenko wrote: > > > > Chris asked me to take over maintenance in Debian as well, and Ghislain > > > blessed me as well. > > > Fine for me. > > > > To minimize amount of work for myself, I would like > > > to continue with NeuroDebian packaging, just polishing it up (copyright > > > file and may be some cleanup). How NeuroDebian packaging is > > > different (dropping historical perspective) ATM it is at > > > http://github.com/neurodebian/dcm2niix > > > Please do not do this. The development platform for Debian packages is > > salsa.debian.org and *lots* of QA tools are relying to find the > packaging > > code here. I do not mind about the team but I mind a lot about the host > > any Blends package can be found. > > I would be happy to move it to salsa. I just pointed to it as the one > we currently use > > I guess I would then move it to dcm2niix-epoch1 smth like that (on salsa > i.e.) so previous versions could be found from the original > dcm2niix repo (to which I would also add a commit obliterating > everything and stating to look into that -epoch1 repo) > Please use the original packaging work on salsa and keep the history intact. I don't see what would prevent you from rebasing the work done on Neurodebian on top of mine. Epoch bumps don't justify history rewrites or new repositories, imo. Unless I misunderstood your intent. It's not 100% clear to me. > > > > - main difference is our git repo sitting on top of the upstream so we > > > also can produce an .orig. tarball with dcm_qa submodule which > > > provides data for testing of correct operation. That increases the > > > tarball size but IMHO it is worth it! > > > I do not mind about the tarball size. > > I also didn't but current one (280MB) made me think... not sure yet what > thoughts it would give ;) > > > > ... removed all agreeed upon ... > > > > Please let me know what you think > > > All those packaging details sound sensible but please, pretty > > please stick to salsa.d.o. > > sure > > > Thank you for your work on this package > > 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 > >
Re: dcm2niix -- I have an intent to take over (still under Debian Med team), objections?
On Mon, 03 Dec 2018, Andreas Tille wrote: > Hi Yaroslav, > On Mon, Dec 03, 2018 at 03:36:19PM -0500, Yaroslav Halchenko wrote: > > Chris asked me to take over maintenance in Debian as well, and Ghislain > > blessed me as well. > Fine for me. > > To minimize amount of work for myself, I would like > > to continue with NeuroDebian packaging, just polishing it up (copyright > > file and may be some cleanup). How NeuroDebian packaging is > > different (dropping historical perspective) ATM it is at > > http://github.com/neurodebian/dcm2niix > Please do not do this. The development platform for Debian packages is > salsa.debian.org and *lots* of QA tools are relying to find the packaging > code here. I do not mind about the team but I mind a lot about the host > any Blends package can be found. I would be happy to move it to salsa. I just pointed to it as the one we currently use I guess I would then move it to dcm2niix-epoch1 smth like that (on salsa i.e.) so previous versions could be found from the original dcm2niix repo (to which I would also add a commit obliterating everything and stating to look into that -epoch1 repo) > > - main difference is our git repo sitting on top of the upstream so we > > also can produce an .orig. tarball with dcm_qa submodule which > > provides data for testing of correct operation. That increases the > > tarball size but IMHO it is worth it! > I do not mind about the tarball size. I also didn't but current one (280MB) made me think... not sure yet what thoughts it would give ;) > > ... removed all agreeed upon ... > > Please let me know what you think > All those packaging details sound sensible but please, pretty > please stick to salsa.d.o. sure > Thank you for your work on this package 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
Re: dcm2niix -- I have an intent to take over (still under Debian Med team), objections?
Hi Yaroslav, On Mon, Dec 03, 2018 at 03:36:19PM -0500, Yaroslav Halchenko wrote: > > Chris asked me to take over maintenance in Debian as well, and Ghislain > blessed me as well. Fine for me. > To minimize amount of work for myself, I would like > to continue with NeuroDebian packaging, just polishing it up (copyright > file and may be some cleanup). How NeuroDebian packaging is > different (dropping historical perspective) ATM it is at > http://github.com/neurodebian/dcm2niix Please do not do this. The development platform for Debian packages is salsa.debian.org and *lots* of QA tools are relying to find the packaging code here. I do not mind about the team but I mind a lot about the host any Blends package can be found. > - main difference is our git repo sitting on top of the upstream so we > also can produce an .orig. tarball with dcm_qa submodule which > provides data for testing of correct operation. That increases the > tarball size but IMHO it is worth it! I do not mind about the tarball size. > - we run (build-time only ATM) tests using that dcm_qa/ data. That > already allowed to iron out differences in behavior between i386 and > amd64. > > I expect though that testing for all the other platforms would open a > huge can of worms. But I think it would be beneficial in the long > run to name them all ;) I bet Chris (the upstream) would be > "thrilled" to help nailing them down > > any objections on relying on gbp to produce orig source tarballs? > > - in a rush toward "let's converge packaging" I have added needed then > epoch 1: to the versioning.It would need to "propagate" into > Debian. I hope that is ok We all know epochs are ugly but sometimes needed. > - we still use debhelper 9 for maximal ease of backportability. > > any objections? No. > - we do carry a few patches > https://github.com/neurodebian/dcm2niix/tree/debian/debian/patches > including patches for the packaging backports on elderly jessie (and > equally old ubuntus) > > https://github.com/neurodebian/dcm2niix/blob/debian/debian/patches/jessie-dsc-patch > probably some symlinks for really old /EOLed ubuntus could be removed, > will do now > > But any objections against carrying backport patches? No. > Please let me know what you think All those packaging details sound sensible but please, pretty please stick to salsa.d.o. Thank you for your work on this package Andreas. -- http://fam-tille.de
dcm2niix -- I have an intent to take over (still under Debian Med team), objections?
Dear Team Comrades, Upon blessing from Ghislain Antony Vaillant (previous team maintainer) and Chris Rorden (upstream, CCed) I would like to take over the maintenance of dcm2niix. And I would like to do it largely by taking the dcm2niix packaging setup we have in NeuroDebian. bits of history - we have initially packaged dcm2niix long ago (Sep 2015) but forgot to file an ITP because there were a number of outstanding license issues to be resolved before considering for "Debian proper". - Rightfully so, without seeing an ITP, Ghislain provided separate packaging in Dec 2016. - I don't remember at which stage licensing issues got resolved ;) and that is when I realized that there is already a package in Debian. so we started to talk with Ghislain in Jan 2017 about possibly merging the effort, but never converged. Chris asked me to take over maintenance in Debian as well, and Ghislain blessed me as well. To minimize amount of work for myself, I would like to continue with NeuroDebian packaging, just polishing it up (copyright file and may be some cleanup). How NeuroDebian packaging is different (dropping historical perspective) ATM it is at http://github.com/neurodebian/dcm2niix - main difference is our git repo sitting on top of the upstream so we also can produce an .orig. tarball with dcm_qa submodule which provides data for testing of correct operation. That increases the tarball size but IMHO it is worth it! - we run (build-time only ATM) tests using that dcm_qa/ data. That already allowed to iron out differences in behavior between i386 and amd64. I expect though that testing for all the other platforms would open a huge can of worms. But I think it would be beneficial in the long run to name them all ;) I bet Chris (the upstream) would be "thrilled" to help nailing them down any objections on relying on gbp to produce orig source tarballs? - in a rush toward "let's converge packaging" I have added needed then epoch 1: to the versioning.It would need to "propagate" into Debian. I hope that is ok - we still use debhelper 9 for maximal ease of backportability. any objections? - we do carry a few patches https://github.com/neurodebian/dcm2niix/tree/debian/debian/patches including patches for the packaging backports on elderly jessie (and equally old ubuntus) https://github.com/neurodebian/dcm2niix/blob/debian/debian/patches/jessie-dsc-patch probably some symlinks for really old /EOLed ubuntus could be removed, will do now But any objections against carrying backport patches? Please let me know what you think -- 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#914928: marked as done (ITP: python-typing-extensions -- Backported and Experimental Type Hints for Python)
Your message dated Mon, 03 Dec 2018 13:01:52 + with message-id and subject line Bug#914928: fixed in python-typing-extensions 3.6.6-1 has caused the Debian Bug report #914928, regarding ITP: python-typing-extensions -- Backported and Experimental Type Hints for Python to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 914928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Debian Med team * Package name: python-typing-extensions Version : 3.6.6 Upstream Author : Guido van Rossum, Jukka Lehtosalo, Lukasz Langa, Michael Lee * URL : https://github.com/python/typing/blob/master/typing_extensions/README.rst * License : PSF Programming Lang: Python Description : Backported and Experimental Type Hints for Python The typing module was added to the standard library in Python 3.5 on a provisional basis and will no longer be provisional in Python 3.7. However, this means users of Python 3.5 - 3.6 who are unable to upgrade will not be able to take advantage of new types added to the typing module, such as typing.Text or typing.Coroutine. . The typing_extensions module contains both backports of these changes as well as experimental types that will eventually be added to the typing module, such as Protocol. . Users of other Python versions should continue to install and use the typing module from PyPi instead of using this one unless specifically writing code that must be compatible with multiple Python versions or requires experimental types. A dependency of the latest release of python-schema-salad. This package will be team-maintained by Debian Med --- End Message --- --- Begin Message --- Source: python-typing-extensions Source-Version: 3.6.6-1 We believe that the bug you reported is fixed in the latest version of python-typing-extensions, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated python-typing-extensions package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 28 Nov 2018 11:16:19 -0800 Source: python-typing-extensions Binary: python3-typing-extensions Architecture: source all Version: 3.6.6-1 Distribution: unstable Urgency: medium Maintainer: Michael R. Crusoe Changed-By: Michael R. Crusoe Description: python3-typing-extensions - Backported and Experimental Type Hints for Python Closes: 914928 Changes: python-typing-extensions (3.6.6-1) unstable; urgency=medium . * New package (Closes: #914928) Checksums-Sha1: cc80133e32c6ff4ca2fd9ebdf436d49a4edf69e9 2119 python-typing-extensions_3.6.6-1.dsc 95c1ad71a67783dc2d1f58e44300a619c788c99d 32610 python-typing-extensions_3.6.6.orig.tar.gz c760ab1d2b28f49fa33160311213ce9345af6b42 2616 python-typing-extensions_3.6.6-1.debian.tar.xz a7c5401dfddf7ca3c8ecb379ce60b1d788e04c39 6236 python-typing-extensions_3.6.6-1_amd64.buildinfo cd37d590d1ff71c8983515e98bee4ede695bedf1 14104 python3-typing-extensions_3.6.6-1_all.deb Checksums-Sha256: 020a669e6711f65d56f558332fe0e259d9905adede03a19e8ddff4c3bff99042 2119 python-typing-extensions_3.6.6-1.dsc 51e7b7f3dcabf9ad22eed61490f3b8d23d9922af400fe6656cb08e66656b701f 32610 python-typing-extensions_3.6.6.orig.tar.gz 96528835f7006ba1948b21ede79fda41133e9324c76299febfc7ab9d3eacb7ca 2616 python-typing-extensions_3.6.6-1.debian.tar.xz 6366f0cc050ce1e51e9d54759c36159af2898222fa3ff9fee7c4cee88e2bb4ba 6236 python-typing-extensions_3.6.6-1_amd64.buildinfo 5c4ed54500b519f27d0b73f363f9ff16bd8e378d0603d84750bb020a8ea581f7 14104 python3-typing-extensions_3.6.6-1_all.deb Files: ee13e4fbf8817d8d6bb8098348cf6921 2119 python optional python-typing-extensions_3.6.6-1.dsc 9509b7ff9cbd479d195e61b04d70cd3a 32610 python optional python-typing-extensions_3.6.6.orig.tar.gz e4ba11d65347e9d512f9cd76f325339f 2616 python optional python-typing-extensions_3.6.6-1.debian.tar.xz 5694b5264183d9aef1f31805cb33fb63 6236 python optional
