Bug#807797:
On Sun, Mar 27, 2016 at 7:33 AM, Brian May wrote: > "László Böszörményi (GCS)" writes: >> On Sat, Mar 26, 2016 at 3:42 AM, Brian May wrote: >> As I couldn't find example for DEP-8 tests, waiting for the answer to >> your mail ATM. > > My latest version works. Confirmed. > It does have the weird issue that the egg-info files are > executable. Which gives lintian warnings. However I think that package > should work fine regardless. I've the latest Lintian, 2.5.42.1 version. It doesn't show any messages. I'm aware of DEP-5 on MIT versions vs Expat and took that change as well. Even if it may confuse users, MIT is advertised everywhere as the license of apscheduler. Thanks for your help, Laszlo/GCS
Bug#807797: apscheduler: Please package python3 package
"László Böszörményi (GCS)" writes: > On Sat, Mar 26, 2016 at 3:42 AM, Brian May wrote: >> Have been told the best solution might be to set up DEP-8 style tests. > I've found the same like you it seems. If I override the test target > and make it pass, after installing the package make the re-enabled > build tests success. > As I couldn't find example for DEP-8 tests, waiting for the answer to > your mail ATM. My latest version works. It does have the weird issue that the egg-info files are executable. Which gives lintian warnings. However I think that package should work fine regardless. -- Brian May
Bug#807797: apscheduler: Please package python3 package
On Sat, Mar 26, 2016 at 3:42 AM, Brian May wrote: > Have been told the best solution might be to set up DEP-8 style tests. I've found the same like you it seems. If I override the test target and make it pass, after installing the package make the re-enabled build tests success. As I couldn't find example for DEP-8 tests, waiting for the answer to your mail ATM. Thanks, Laszlo/GCS
Bug#807797: apscheduler: Please package python3 package
Brian May writes: > Have been told the best solution might be to set up DEP-8 style tests. See the following thread for more details: https://lists.debian.org/msgid-search/20160325181936.72584...@subdivisions.wooz.org -- Brian May
Bug#807797: apscheduler: Please package python3 package
"László Böszörményi (GCS)" writes: >> https://bitbucket.org/agronholm/apscheduler/issues/114/lookuperror-no-trigger-by-the-name-date > OK, upstream says it's the missing tox.ini , can test it in the afternoon. No, a bit more involved then then. tox isn't really useful for doing tests during package builds. tox wants to set up different test environments and test everything, but we only want to test the environment that we building the package for. Have been told the best solution might be to set up DEP-8 style tests. -- Brian May
Bug#807797: apscheduler: Please package python3 package
On Fri, Mar 25, 2016 at 4:37 AM, Brian May wrote: > Brian May writes: > >> LookupError: No trigger by the name "date" was found I was investigating this issue. Found an other possible reason. > I reported this upstream: > > https://bitbucket.org/agronholm/apscheduler/issues/114/lookuperror-no-trigger-by-the-name-date OK, upstream says it's the missing tox.ini , can test it in the afternoon. Thanks, Laszlo/GCS
Bug#807797: apscheduler: Please package python3 package
Brian May writes: > LookupError: No trigger by the name "date" was found I reported this upstream: https://bitbucket.org/agronholm/apscheduler/issues/114/lookuperror-no-trigger-by-the-name-date -- Brian May
Bug#807797: apscheduler: Please package python3 package
Brian May writes: > Just so you know I have a mostly working updated package at: > > Vcs-Git: git://anonscm.debian.org/python-modules/packages/apscheduler.git > Vcs-Browser: > https://anonscm.debian.org/cgit/python-modules/packages/apscheduler.git Looks like won't build due to a number of test failures. LookupError: No trigger by the name "date" was found So this may require a bit more work before it is usable. -- Brian May
Bug#807797: apscheduler: Please package python3 package
Brian May writes: > I found this depends on tzlocal which is not in Debian (I still need to > add the build depends). So I filled ITP #819126 and have a working > package for tzlocal: > > Vcs-Git: git://anonscm.debian.org/python-modules/packages/tzlocal.git > Vcs-Browser: > https://anonscm.debian.org/cgit/python-modules/packages/tzlocal.git Was just told this package is already in Debian. So ignore this part :-) -- Brian May
Bug#807797: apscheduler: Please package python3 package
"László Böszörményi (GCS)" writes: >> I am going to assume that you are not interested in maintaining this >> package anymore. > Sorry, it's fallen between the cracks. December was busy and > holidays, then I'd other priority. But I still want to maintain and > keep it fresh in the archive. Ok, good. Just so you know I have a mostly working updated package at: Vcs-Git: git://anonscm.debian.org/python-modules/packages/apscheduler.git Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/apscheduler.git I found this depends on tzlocal which is not in Debian (I still need to add the build depends). So I filled ITP #819126 and have a working package for tzlocal: Vcs-Git: git://anonscm.debian.org/python-modules/packages/tzlocal.git Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/tzlocal.git -- Brian May
Bug#807797: apscheduler: Please package python3 package
On Thu, Mar 24, 2016 at 12:10 AM, Brian May wrote: > On Sun, Dec 13, 2015 at 04:11:35PM +1100, Brian May wrote: >> Can you please package the Python 3 package? It looks like upstream >> supports Python 3. Yes, that was the plan. >> In addition I notice the Debian version is very old, version 3.0.5 is >> current upstream. >> >> If you want me to: I can change fix the package up and upload as part of >> the Debian Python Modules Team, so you don't have to worry. I can do it probably tomorrow. > No response since December. > > I am going to assume that you are not interested in maintaining this > package anymore. Sorry, it's fallen between the cracks. December was busy and holidays, then I'd other priority. But I still want to maintain and keep it fresh in the archive. Thanks for the heads-up, Laszlo/GCS
Bug#807797: apscheduler: Please package python3 package
On Sun, Dec 13, 2015 at 04:11:35PM +1100, Brian May wrote: > Can you please package the Python 3 package? It looks like upstream > supports Python 3. > > In addition I notice the Debian version is very old, version 3.0.5 is > current upstream. > > If you want me to: I can change fix the package up and upload as part of > the Debian Python Modules Team, so you don't have to worry. No response since December. I am going to assume that you are not interested in maintaining this package anymore. As discussed I will update the package, put it into git, and change the maintainer to the Debian Python Module Team. After I upload the new version it will get stuck in the NEW queue for a while, so there is still time to disagree if you want. Regards -- Brian May
Bug#807797: apscheduler: Please package python3 package
Source: apscheduler Version: 2.1.2-2 Severity: normal Hello, Can you please package the Python 3 package? It looks like upstream supports Python 3. In addition I notice the Debian version is very old, version 3.0.5 is current upstream. If you want me to: I can change fix the package up and upload as part of the Debian Python Modules Team, so you don't have to worry. Regards. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
