Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote: > Then if you don't mind I'd still keep my NMU as it is and let it enter > unstable. The only thing is that you'd find yourself to integrate it > into your own tree. no worries. will merge it. thanks felix
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 07:36:57PM +0100, Felix Salfelder wrote: > On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote: > > Then if you don't mind I'd still keep my NMU as it is and let it enter > > unstable. The only thing is that you'd find yourself to integrate it > > into your own tree. > > no worries. will merge it. ACK, so I rescheduled the NMU to go in now. Thank you! /me looks forward for his other NMU for libkolabxml to also go in… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 05:03:27PM +0100, Felix Salfelder wrote: > On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote: > > If it's only about sponsoring I'm happy to help, but I don't really want > > to play with symbols at this time… > > my preferred solution will be to accept the dpkg-shlibdeps warnings, as > described in the manual. it will be more tricky to silence them. I also usually just ignore those myself… > > With this and onther package being the only last blockers for the > > removal of python3.6 I'm somewhat pressured to continue, unless you can > > give me a shorter ETA. Also, I'm happy to rework my work. > > I essetially agree with your changes. the ETA is subject to > review & sponsoring. Then if you don't mind I'd still keep my NMU as it is and let it enter unstable. The only thing is that you'd find yourself to integrate it into your own tree. > > * you are build-depending on python3-dev, instead of python3-all-dev, > > is that wanted? As I went for the letter in my NMU. > > looks reasonable. i simply did not know about it. python3-all-dev depends on all the supported python3 versions, which means that until 2 months ago it would have pulled in both 3.6 and 3.7. Instead, python3-dev only pulls in the default version. > > Also, while working on gnucap-python, I had the feeling that those > > out2.7 and out3.6 directories were pre-built stuff that shouldn't be in > > out* contains the expected output for testing, which varies across > python versions. it actually shouldn't, and it does not between 3.7 and > 3.6. perhaps out2 and out3 will be sufficient. work in progress, > possibly ready in 0.0.3. Oh, then my change that is removing them is not right. mhh well, since the tests are disabled anyway I'll leave it there, but indeed it requires some changes. Sorry I didn't understand what that thing was. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote: > If it's only about sponsoring I'm happy to help, but I don't really want > to play with symbols at this time… my preferred solution will be to accept the dpkg-shlibdeps warnings, as described in the manual. it will be more tricky to silence them. > With this and onther package being the only last blockers for the > removal of python3.6 I'm somewhat pressured to continue, unless you can > give me a shorter ETA. Also, I'm happy to rework my work. I essetially agree with your changes. the ETA is subject to review & sponsoring. > On that note, looking at the git repository I see that: > * you didn't do anything to d/rules, that still mention 3.6 and 3.7 I used a symlink to make tests work across python versions. currently the tests are not active, due to numerical noise. I had planned to clean up d/rules after reworking the tests upstream, when re-enabling the tests. > * you are build-depending on python3-dev, instead of python3-all-dev, > is that wanted? As I went for the letter in my NMU. looks reasonable. i simply did not know about it. > Also, while working on gnucap-python, I had the feeling that those > out2.7 and out3.6 directories were pre-built stuff that shouldn't be in out* contains the expected output for testing, which varies across python versions. it actually shouldn't, and it does not between 3.7 and 3.6. perhaps out2 and out3 will be sufficient. work in progress, possibly ready in 0.0.3. thanks felix
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
Hi, On Sun, Jan 20, 2019 at 03:44:55PM +0100, Felix Salfelder wrote: > thanks for your commitment. I have prepared 0.0.2-2 in the > pkg-electronics team repo, looking for a sponsor. we are now discussing > issues with toolchains [2], ETA unknown. I see that the discussion there has moved on to something about C++ symbols I'm not so concerned about myself. If it's only about sponsoring I'm happy to help, but I don't really want to play with symbols at this time… > Please proceed as you wish. With this and onther package being the only last blockers for the removal of python3.6 I'm somewhat pressured to continue, unless you can give me a shorter ETA. Also, I'm happy to rework my work. On that note, looking at the git repository I see that: * you didn't do anything to d/rules, that still mention 3.6 and 3.7 * you are build-depending on python3-dev, instead of python3-all-dev, is that wanted? As I went for the letter in my NMU. Please have a look at my diff and see if that's good in your opinion. Also, while working on gnucap-python, I had the feeling that those out2.7 and out3.6 directories were pre-built stuff that shouldn't be in the source distribution. If that's really the case, I suggest you ask upstream to get rid of them for the next version. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#919255: [Pkg-electronics-devel] Bug#918533: gnucap-python: diff for NMU version 0.0.2-1.1
On Sun, Jan 20, 2019 at 01:55:18PM +0100, Mattia Rizzolo wrote: > I've prepared an NMU for gnucap-python (versioned as 0.0.2-1.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Dear Mattia. thanks for your commitment. I have prepared 0.0.2-2 in the pkg-electronics team repo, looking for a sponsor. we are now discussing issues with toolchains [2], ETA unknown. Please proceed as you wish. regards felix [1] https://salsa.debian.org/electronics-team/Gnucap/gnucap-python.git [2] https://alioth-lists.debian.net/pipermail/pkg-electronics-devel/2019-January/thread.html#5887
