Bug#873459: RFS: python-singa/1.1.1-1 [ITP]
Hi Moaz,
the package looks good, but I can't build it in a clean chroot:
Run Build Command:"/usr/bin/make" "cmTC_2ee00/fast"
make[1]: Entering directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_2ee00.dir/build.make
CMakeFiles/cmTC_2ee00.dir/build
make[2]: Entering directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_2ee00.dir/CheckSymbolExists.c.o
/usr/lib/ccache/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2-o CMakeFiles/cmTC_2ee00.dir/CheckSymbolExists.c.o -c
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTC_2ee00
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2ee00.dir/link.txt
--verbose=1
/usr/lib/ccache/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic
CMakeFiles/cmTC_2ee00.dir/CheckSymbolExists.c.o -o cmTC_2ee00
CMakeFiles/cmTC_2ee00.dir/CheckSymbolExists.c.o: In function `main':
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_2ee00.dir/build.make:97: recipe for target 'cmTC_2ee00' failed
make[2]: *** [cmTC_2ee00] Error 1
make[2]: Leaving directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_2ee00/fast' failed
make[1]: *** [cmTC_2ee00/fast] Error 2
make[1]: Leaving directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
File
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef pthread_create
return ((int*)(&pthread_create))[argc];
#else
(void)argc;
return 0;
#endif
}
Determining if the function pthread_create exists in the pthreads failed with
the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_c8421/fast"
make[1]: Entering directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_c8421.dir/build.make
CMakeFiles/cmTC_c8421.dir/build
make[2]: Entering directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_c8421.dir/CheckFunctionExists.c.o
/usr/lib/ccache/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o
CMakeFiles/cmTC_c8421.dir/CheckFunctionExists.c.o -c
/usr/share/cmake-3.9/Modules/CheckFunctionExists.c
Linking C executable cmTC_c8421
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_c8421.dir/link.txt
--verbose=1
/usr/lib/ccache/cc -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-z,relro
-rdynamic CMakeFiles/cmTC_c8421.dir/CheckFunctionExists.c.o -o cmTC_c8421
-lpthreads
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
CMakeFiles/cmTC_c8421.dir/build.make:97: recipe for target 'cmTC_c8421' failed
make[2]: *** [cmTC_c8421] Error 1
make[2]: Leaving directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_c8421/fast' failed
make[1]: *** [cmTC_c8421/fast] Error 2
make[1]: Leaving directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake ..
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON returned exit code 1
debian/rules:20: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2017-11-05T09:28:27Z
Finished
+--+
| Cleanup |
+--+
Purging /<>
Not cleaning session: cloned chroot in use
E: Build failure (dpkg-buildpackage died)
DS
--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/
Bug#868245: RFS: python-latexcodec/1.0.5-1
On 13.07.2017 17:56, Ghislain Vaillant wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for the following package: > > * Package name: python-latexcodec > Version : 1.0.5-1 > Upstream Author : Matthias C. M. Troffaes > * URL : https://pypi.python.org/pypi/latexcodec/ > * License : Expat > Section : python In. That's a decent package. Thanks for adopting this. Let me know when Pybtex is ready to follow. Best, DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Re: watch file - remove or only comments?
On 11.10.2016 14:41, Eriberto wrote: > Hi Dominik, > > 2016-10-11 8:53 GMT-03:00 Dominik George : >> >> I wonder what of these two options is the "correct" solution for an >> upstream that is not watch'able (e.g. has no release tarballs, etc.) - >> besides making upstream have release tarballs, that is ;): >> >> a) no watch file >> b) a watch file with only comments >> >> In case a), lintian complains and proposes to place a watch file with a >> comment explaining why it is otherwise empty [0]. >> >> In case b), (at least( the DMD [1] complains about empty uscan output. > > To avoid a false impression that you ignored the watch file by > laziness and to inform an actual status, I created three fake > packages[1]. These packages say if there no upstream site, if there no > release in upstream site or if the upstream site there a package but > doesn't allow track it (using a JavaScript to block it, for example). > > Some people are using my fake packages and you can see the result in > my DDPO[2]. Look at 0.No-Site, 0.No-Release and 0.No-Track. > > Feel free if you want to use this solution. > > [1] https://people.debian.org/~eriberto/#fake-packages > [2] https://qa.debian.org/developer.php?login=eribe...@debian.org > > Regards, > > Eriberto Great thing! DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: scantailor maintainership and alioth
On 27.04.2016 22:41, Jason Crain wrote: > On Wed, Apr 27, 2016 at 06:39:11PM +0800, Paul Wise wrote: >> >> On Wed, Apr 27, 2016 at 4:28 PM, Jason Crain wrote: >> >>> I have a question about Alioth though. The debian package is being >>> maintained at (http://anonscm.debian.org/cgit/collab-maint/scantailor.git). >>> Can I get access to that, or do I need to upload this to github instead >>> and change the Vcs fields in the debian/control file correspondingly? >> >> You can get access, see here: >> >> https://wiki.debian.org/Alioth/Git#Collab_Maint_project >> https://wiki.debian.org/Alioth/PackagingProject >> https://lists.debian.org/debian-devel-announce/2015/02/msg1.html > > Sounds like I'll need a DM or DD to email a signed request before I can > get access. I suppose I'll keep the Vcs fields pointing to Alioth, ask > for an advocate when it's ready, and upload the project to github so > they can review it. Daniel: would you, as the current maintainer, be > willing to advocate Alioth access for me? Hi Jason, yes, I'm going to help you to complete the RFA incl. that. Tell me when you've got the new package ready. Temporarily pushing the repo to Github for reviewing the changes as long as the application for collab-maint is pending is all right. Daniel -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Bug#803895: [pkg-go] Bug#803895: RFS: gox/0.3.0-1 [ITP, pkg-go] -- cross-compilation for Go
On 05.11.2015 22:46, Michael Stapelberg wrote: > Thanks, uploaded. > > FYI, I’ve opened https://github.com/mitchellh/gox/issues/47 with upstream > and it seems like we can fix the test in question for the next release. Yes, all right. Thx for sponsoring! Best, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#803895: [pkg-go] Bug#803895: RFS: gox/0.3.0-1 [ITP, pkg-go] -- cross-compilation for Go
Thanks for picking that up, review points and pointers ...
On 03.11.2015 09:29, Michael Stapelberg wrote:
>> I’ve noticed the resulting package ships /usr/share/gocode/src/… — is that
>> intentional? Does it make sense to ship the library code, i.e. will other
>> programs use gox as a library? On first glance, it looks like a binary
>> only, but you might be more familiar with gox.
No, there's no reason to keep that. Removed it.
> The package builds and works fine, but for some reason the tests don't run
> through.
>
>> The only failing test I can see is:
>
>> === RUN TestGoVersion
>> --- FAIL: TestGoVersion (0.25s)
>> go_test.go:24: bad: "go1.5.1"
>
>> This is the code in question:
>
>> func TestGoVersion(t *testing.T) {
>> v, err := GoVersion()
>> if err != nil {
>> t.Fatalf("err: %s", err)
>> }
>
>> acceptable := []string{"devel", "go1.0", "go1.1", "go1.2"}
>> found := false
>> for _, expected := range acceptable {
>> if strings.HasPrefix(v, expected) {
>> found = true
>> break
>> }
>> }
>
>> if !found {
>> t.Fatalf("bad: %#v", v)
>> }
>> }
>
>> So, the package expects to be compiled with go1.0, go1.1, go1.2, but
>> anything newer is definitely unacceptable…?! Given we have the Go 1
>> stability guarantee (see https://golang.org/doc/go1compat), that test
>> strikes me as not useful.
All right. I've stripped go_test.go via Files-Excluded in deb/copyright from the
upstream release watch gets, and refreshed the tarball within the Git repo.
>> I recommend suggesting upstream to delete the test, and then packaging a
>> new snapshot.
I've seen that upstream has already worked on that:
https://github.com/mitchellh/gox/commit/733261c
Maybe better to switch over to snapshot packaging?
>> We definitely want the other tests to run at package-build time.
Anyway, the tests are running through now.
The changes are in the repo.
Thanks you,
Daniel Stender
--
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/
Bug#803895: RFS: gox/0.3.0-1 [ITP, pkg-go] -- cross-compilation for Go
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: sponsorship-requests Severity: wishlist Control: block 796309 by -1 X-Debbugs-CC: pkg-go-maintain...@lists.alioth.debian.org Hi, I'm looking for a sponsor for my package of Gox, a cross compilation builder for Go: https://github.com/mitchellh/gox I've created an initial package within a new pkg-go repo: https://anonscm.debian.org/cgit/pkg-go/packages/gox.git (new, maybe not yet populated) Buildlog: http://www.danielstender.com/buildlogs/gox_0.3.0-1_amd64-20151102-2329.build Mentors upload: http://mentors.debian.net/package/gox http://mentors.debian.net/debian/pool/main/g/gox/gox_0.3.0-1.dsc The package builds and works fine, but for some reason the tests don't run through. Thank you very much for considering, Daniel Stender - -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWN+mTAAoJEBXgmvTfUYLIfQAP/iA805ir2/rUoytC9pkAi8pj /r1LUxMhqF4kuHVLtGJCxmNviUMkG10IUqVBXYOtVLQmbgYghQGCuSl1LoAePjWr lE5mrsTvPcEtPw0rLE1hPv9JUlJPSHaoKCAzOQOlRpXuATFurHmLl7vQKrjQajMf 9fHszTtZei+8aIhWoQQtq8je4CyTMk3Ju6l8rsoiDRcjn1K0kUrDmrdnI31z8D3v 0XfDYXnPVhalg9TKBsWYAl5ojLoqK9rHT4t+BZ3HFRxY3Za7RAFJguPmkwPOtdQr H9JKzagE/gr5MD+pkyG2w5Swp51V733ujWMkKsZNuawqO3xUmoLUttQ3/HjsuLr6 hkDF2R9YWGv0A7gmHLkAvflDe1P+zAH/tYQ+HRTQXTNueFDDnJT1HTGYC/CVEC7Z voI3u+IIyY03cYx9SJmZqb1SDI6pH1bUB1LpnpmAehWHMrrIoqQFiiWuY6VIpk1s nPrNlqq3j94dgFB6VNzInJ184WDApfrAiFpgysOk5T+m6+4J0PbKfV4ZnuTJ7zsU 8sgwf/HI2x4IHKvl81MUOzeZi6WZWmG7i0D7w6hvmFsZ9mhALlDjHQf7mzsiPr/A gKmEkbTscVf9xI0Wg+O+7l6MxfssF0hhl9uBtK8wvp82l8e0gDgUJCXBWtnLkbDZ /V+J09mJFd+UDS+W8mfY =0ZTO -END PGP SIGNATURE-
Bug#803620: RFS: afl-cov/0.3-1 [ITP] -- code coverage for afl
... "import subprocess32" of course doesn't work but "import subprocess32 as subprocess". Fixed it and refreshed the mentors upload. Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#803620: RFS: afl-cov/0.3-1 [ITP] -- code coverage for afl
Thanks for picking this up! On 01.11.2015 10:06, Gianfranco Costamagna wrote: > quick review: > 1) debian/patches/correct-fsf-address... > well, I usually don't ask to change the address but to forward a patch > upstream instead. > > Doing both is for sure really nice ... in the case some day somebody really writes a letter requesting a copy of the license :-) > 2) you changed to subprocess32, this is nice, but can you please provide a > rationale for it? > > better subprocess handling? why you didn't forward the patch upstream? > I'm asking because such Debian delta usually might introduce downstream > problems :) The patch header is a little sparsely, I've added some info. I don't wanted to add this change to the other things in the pull request stack on Github not to overload it, but I've now posted an issue on this (Forwarded updated). > 3) and now the important part, the reason for the moreinfo tag: > > are you sure about the license? > > I am not :p ... h yes. Little pitfall: "or (at your option) any later version"! :-) Mentors upload is updated, debdiff attached. Best, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/ diff -Nru afl-cov-0.3/debian/copyright afl-cov-0.3/debian/copyright --- afl-cov-0.3/debian/copyright 2015-10-31 22:17:17.0 +0100 +++ afl-cov-0.3/debian/copyright 2015-11-01 11:35:35.0 +0100 @@ -5,21 +5,22 @@ Files: * Copyright: 2015 Michael Rash -License: GPL-2 +License: GPL-2+ Files: debian/* Copyright: 2015 Daniel Stender -License: GPL-2 +License: GPL-2+ -License: GPL-2 - This package is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; version 2 dated June, 1991. +License: GPL-2+ + This program is free software; you can redistribute it and/or + modify it under the terms of the GNU General Public License + as published by the Free Software Foundation; either version 2 + of the License, or (at your option) any later version. . - This package is distributed in the hope that it will be useful, but - WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - General Public License for more details. + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. . On Debian systems, the complete text of the GNU General Public License - version 2 can be found in the /usr/share/common-licenses/GPL-2 file. \ No newline at end of file + version 2 can be found in the /usr/share/common-licenses/GPL-2 file. diff -Nru afl-cov-0.3/debian/patches/use-subprocess32.patch afl-cov-0.3/debian/patches/use-subprocess32.patch --- afl-cov-0.3/debian/patches/use-subprocess32.patch 2015-10-31 22:32:28.0 +0100 +++ afl-cov-0.3/debian/patches/use-subprocess32.patch 2015-11-01 11:20:33.0 +0100 @@ -1,6 +1,8 @@ Description: use subprocess32 instead of subprocess + For thread safety, it's highly recommended to replace the Python 2 + stdlib subprocess module on POSIX systems. Author: Daniel Stender -Forwarded: no +Forwarded: https://github.com/mrash/afl-cov/issues/13/ --- a/afl-cov +++ b/afl-cov
Bug#803620: RFS: afl-cov/0.3-1 [ITP] -- code coverage for afl
Package: sponsorship-requests Severity: wishlist Control: block 796821 by -1 Hello, I'm looking for a sponsor for my new package of afl-cov [1], a little tool which is build around gcov to add code coverage monitoring to the fuzzing (brute force vulnerability detection) of afl (American Fuzzy Lop). I have a buildlog here: http://www.danielstender.com/buildlogs/afl-cov_0.3-1_amd64-20151101-0153.build And a mentors upload prepared: http://mentors.debian.net/package/afl-cov http://mentors.debian.net/debian/pool/main/a/afl-cov/afl-cov_0.3-1.dsc Thank you very much for consideration, Daniel Stender [1] https://github.com/mrash/afl-cov -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#803600: RFS: golang-github-mitchellh-iochan [ITP, pkg-go]
Package: sponsorship-requests Severity: wishlist Control: block 802965 by -1 Hello, I'm looking for a sponsor of my package of golang-github-mitchellh-iochan, a little Go library for turning `io.Reader` into channels [1]. It's a prerequisite for Gox [2]. I've set up a new Git repo for the package in pkg-go: https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-mitchellh-iochan.git git://git.debian.org/git/pkg-go/packages/golang-github-mitchellh-iochan.git Buildlog: http://www.danielstender.com/buildlogs/golang-github-mitchellh-iochan_0.0~git20150529.0.87b45ff-1_amd64-20151031-1837.build Mentors upload: http://mentors.debian.net/package/golang-github-mitchellh-iochan http://mentors.debian.net/debian/pool/main/g/golang-github-mitchellh-iochan/golang-github-mitchellh-iochan_0.0~git20150529.0.87b45ff-1.dsc Thank you very much, Daniel Stender [1] https://github.com/mitchellh/iochan [2] http://bugs.debian.org/796309 ITP: gox -- helper tool for Go cross-compilation -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
On 26.10.2015 10:47, Cornelius Kölbel wrote: > Hi Daniel, > > what do you need me to do? > As the poster of RFS do I need to take action? > > Thanks > Cornelius > > Am Sonntag, den 25.10.2015, 22:00 +0100 schrieb Daniel Stender: >> My idea with this would be, close the RFS for now, then file RFP and >> wishlist-please-update bugs with blocks against the ITP as a todo list. >> >> Needs some afforestation, when everything is available privacyidea goes into >> NEW. Like said, I think I've seen that most of the packages are group >> maintained >> (with Python group in Maintainers field), that's good. >> >> Daniel Yes, I didn't closed it because it's not my bug, that should do the reporter. I've made a "afforestation" before for Prospector, there were ... I think ... more than ten things outdated or not available. I'm going to help with uploads in the groups, and I would really see Privacyidea in Debian at the year's turn (depends on how long the missing packages are going to be in NEW), for Debian 9 there's nothing against it. I'm on it (owner of the ITP bug)! Best, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
My idea with this would be, close the RFS for now, then file RFP and wishlist-please-update bugs with blocks against the ITP as a todo list. Needs some aforestation, when everything is available privacyidea goes into NEW. Like said, I think I've seen that most of the packages are group maintained (with Python group in Maintainers field), that's good. Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
I've gone through the requirements of privacyIDEA (./requirements.txt) yet and there might be a serious problem ... python-qrcode 5.1/5.0.1 python-dateutil 2.4.2/2.2 python-tz 2015.4/2012c snowballstemmer not available python-gunicorn 19.3.0/19.0 python-responses 0.4.0/0.3.0 cookies not available python-flask-script 2.0.5/0.6.7 python-flask-sqlalchemy 2.0/1.0 python-bcrypt 1.1.0/0.4 pycrypto not available python-pytest-cov 1.8.1/1.8.0 pytest-runner not available I'm going to help with updates (most of the packages are Python group maintained) and filing RFP/ITP bugs. Some of them might could be spared, though, but ... Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#801213: RFS: python-privacyidea/2.7-1
On 15.10.2015 11:46, Gianfranco Costamagna wrote: > Control: owner -1 ! > Control: tags -1 moreinfo > > Hi > > please fix the mentors issues and remove tag moreinfo as soon as you have > addressed them. > > e.g. ITP bug is needed, the changelog should target unstable not jessie, you > should contain only an > "initial release, closes: #ITP" or similar > > please try to use pybuild in rules file > > compat level=9 debhelper >=9, > > and so on :) > > cheers, > > G. Hi Gianfranco, I've agreed with Cornelius that I'm going to maintain this for Debian. I'm going to fix everything very soon, come back then. Ciao, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11.10.2015 10:52, Cornelius Kölbel wrote: > Hi Daniel, > > thanks a lot for all the valuable feedback. > > I will dive into it later. > > Do you have any further recommendations on finding a sponser (after > streamlining the package)? > > THanks a lot and kind regards > Cornelius Getting it Lintian clean is a major step. That's a rather complicated package, and somebody might wants to discuss issues beyond that like your architecture of subpackages. The flaws must be out of the way for that. And then, patience ... sponsorship-requests is the right place to seek for a sponsor. Best, Daniel - -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWGi3uAAoJEBXgmvTfUYLIXF4QAJRQbQ3HzZ6As8EhizQMMrLX tATn1Aj5LhB7S2MHuwO6ytkJVkQUbG/3uvIoTqvCCBpEiYzUSp4eTJFsLSa26Wdz H+bwkYlQlwj7/TWTqjBZ2b6wMPMw0J8dnhRur39CaNT25lJ0HLG69RLpkKeLOv9V 2r/D/eEoHuVDySqM1uncOXP+HQCTsMptlqr6BVR7sN1DYgf0L9ltpyQkj2eMyBPF Qg1k15lpBkM5EehS5ri0YnGBqse6qxaUkYrrSuTOeOrTekF3QQjCRbq5CN9caqrc 4NCMcwm6YRVKYDZDWSLuK3ZUfrKh/Djo6gMQNalqWiqv0klDsxbayW8ZGDRJQgdT rVqe4RKb/tKK8BmaFqR3zopJjc3/toACLlRIl5OlAd3B0c1Q1pnwbBRa5zbS0aEp wXjHkkzZVInpsYNBwa2wo44cBWz3nx3JcozT9D4A6SqNY3s333oRwlobmmzoWiHy pirb1QLhDTBHIu1xLqjZmiZ8cyjQhmepxY4pJ2oqOsFXkgMKgmlreJwvdKjY7NHF jCgxLVZo/lMnPnnJU9F/MP4h6tfRlCkF8goSEo2TMGXp36NjIl+OHUl+jEyUfgGV RIVuadM0I4HeX9qdKQMJqKoCxgaiVRXZMUiRWmfOGQPM3LKHa8h6tJpM8GvRxCBo QZmBPl4iP7d+QkHDp33y =8aR4 -END PGP SIGNATURE-
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
bug. And if missing manpages adds to a couple of other issues like that (like sub standard descriptions) the chance of being rejected by the FTP team rises [b]. [a] https://www.debian.org/doc/debian-policy/ch-docs.html#s12.1 [b] https://ftp-master.debian.org/REJECT-FAQ.html (see "Manpages") 14) debian/copyright: this files is the complete license text of the AGPL-3.0, but although this is also being marked as optional in the policy [a], it would be better if it would follow the (machine parse-able) DEP-5 copyright file format [b] instead. [a] https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightformat [b] http://dep.debian.net/deps/dep5/ 15) you have some third-party files in the source package which follow a different license, like privacyidea/static/contrib/js/jquery-1.11.3.js (MIT). All licenses and copyright holders must be listed in debian/copyright (you have to make it DEP-5). Misses are a common reason for new packages to get rejected by the FTP masters [a]. [a] https://ftp-master.debian.org/REJECT-FAQ.html (see "License III"). 16) debian/*.copyright: the individual copyright files for different binaries should be dropped in favour of a DEP-5 debian/copyright, the same for all the binaries. I've rechecked, the policy says: "a copy of the file which will be installed in /usr/share/doc/package/copyright should be in debian/copyright in the source package" [a]. [a] https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile 17) debian/control: the "python-" prefix for the main binary "python-privacyidea" could be dropped, that's mend for packages with public modules used by other packages [a] (there might be different opinions on if you should keep it like it is). But the build-dep on python-all should be replaced with "python", for that package doesn't need to get build against any/all supported Python versions, but only the default one. [a] https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names 18) maybe you would like to build the Sphinx documentation in doc/ into a privacyidea-docs package. As far as I see it doesn't make much sense to run this application offline, but it would be more comfortable to have the documentation that way, instead of only on the web. 19) maintscripts: you have two symlinks in debian/, privacyidea-apache2.postinst and privacyidea-nginx.postinst which are dead (it's "../deploy/debian-ubtuntu/" instead of "../debian-ubuntu/"). They should be replaced by the actual scripts. Policy 6.1: "... they must be proper executeable files" [a] (and not symlinks). The others aren't executable here, either. [a] https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html 20) debian/privacyidea-radius.postinst: there's a Lintian complaint of running the "service" command for a restart-after-upgrade, which isn't wanted for maintainer scripts. 21) the manpage ./usr/share/man/man1/privacyidea-server.1.gz has a Lintian complaint on "manpage-has-errors from-man" [a], and furthermore there is the problem that this manpage is in section "1", which is reserved for binaries resp. executables, but this is a general documentation. That's pre generated out of the Sphinx docs, maybe you would like to put this out in plain text and put it into /usr/share/docs/, if not going for 18), instead (and manpages aren't handled by debian/install, either). [a] https://lintian.debian.org/tags/manpage-has-errors-from-man.html 22) you've got important Lintian complaints on privacy breaches (fetching data from external websites on runtime) in some of the Javascript libraries in privacyidea/static/contrib/js/ (angular.js and ui-bootstrap-tpls-0.13.0.js), this must be patched out. 23) There are some more Lintian complaints on things copied into the binaries, which aren't wanted (image-file-in-usr-lib, extra-license-file), please make your package Lintian clean! 24) there are some more issues on the source tarball (contains .pyc bytecode files, prebuild Javascript objects), and maybe you would like to remove docs/sphinx_rtd_theme.zip from the source package (and use the package python-sphinx-rtd-theme). You might want to use "Files-Excluded:" in debian/copyright [a] to created a reduced Debian tarball via uscan. [a] https://wiki.debian.org/UscanEnhancements I'm sure that privacyIDEA would be a great addition to the Debian archive (I'm going to watch the talk on Datenspuren 2014 [a] after I've sended this), and I would really like to see that package pass the sponsoring-requests stage and that you'll find a sponsor. [a] https://www.youtube.com/watch?v=fvKPQMpvYnw Best, Daniel Stender - -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#801213: RFS: python-privacyidea/2.7-1 [ITP]
I'm going to review this. Please expect the results, soon. Best, Daniel Stender -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Bug#789699: ping :)
On 09.09.2015 08:55, Daniel Stender wrote:
> On 09.09.2015 08:50, Gianfranco Costamagna wrote:
>> Hi, Ping about 789699 (vulture)
>>
>> :)
>> cheers!
>>
>> G.
>
> Yes yes yes :-) I was busy with with other stuff. It's coming up! Soon.
>
> Dan
All right ...
let's do it this way with Vulture: a single new binary, build on Python 3
instead on Python 2
(like the Python policy says it).
The one big thing in the archive with is going to employ is Prospector, which
is currently running
on py2. But, transferring Prospector and its requirements to py3 is one of the
next tasks to do.
Vulture is going to be in NEW for a time, anyway, and is then readily waiting
for Prospector to
come right after.
To build two binaries, vulture{,3} or python{,3}-vulture is no good alternative
to that,
alternatives (maint scripts) are rather complex, needs duplicating the same man
page into two
files with different names, confusing for the end user, and next to
Prospector-being-transferred
nothing really needs the main module in both public paths (and even not at the
same time).
So, here we go with:
committed changes:
http://anonscm.debian.org/viewvc/python-apps/packages/vulture/trunk/
Buildlog:
http://www.danielstender.com/buildlogs/vulture_0.6-1_amd64-20150909-1033.build
fresh Mentors upload:
http://mentors.debian.net/package/vulture
http://mentors.debian.net/debian/pool/main/v/vulture/vulture_0.6-1.dsc
Cheers,
Daniel
--
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
LPI certified Linux admin (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/blog/
Bug#797707: RFS: python-subprocess32/3.2.6-1
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for a sponsor for my package of python-subprocess32 [1]. It's needed resp. recommended e.g. by ocrodjvu >= 0.9.1, but missing in Debian so far. I've injected the package into a DPMT repo: http://anonscm.debian.org/cgit/python-modules/packages/python-subprocess32.git Buildlog: http://www.danielstender.com/buildlogs/python-subprocess32_3.2.6-1_amd64-20150901-2104.build Mentors upload: http://mentors.debian.net/package/python-subprocess32 http://mentors.debian.net/debian/pool/main/p/python-subprocess32/python-subprocess32_3.2.6-1.dsc Thanks for consideration, Daniel Stender [1] https://bugs.debian.org/797583 ITP: python-subprocess32 -- Py2 backport of Py3 stdlib subprocess module -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux Admin (LPI000329859) http://www.danielstender.com/blog/
Bug#789699: vulture review
On Wed, 26 Aug 2015 22:18:02 +0200 Daniel Stender
wrote:
> On Tue, 25 Aug 2015 19:32:16 +0200 Daniel Stender
> wrote:
> For the name of binaries, I would prefer "vulture{,3}" over
> "python{,3}-vulture" like Pylint does
> it, but it appears Pybuild expects this ... does it?
... but in the end I'm also all right with "python{,3}-vulture". I'll have it
ready in the next days.
Dan
--
http://www.danielstender.com/entwicklerblog
GnuPG key: 4096R/DF5182C8
Bug#789699: vulture review
On Tue, 25 Aug 2015 19:32:16 +0200 Daniel Stender
wrote:
> On 25.08.2015 19:17, Gianfranco Costamagna wrote:
> ... yeah, this would be an option, Py3 as default is coming up, anyway.
>
> This is going to be an enhancement for Prospector, which is on Py2, but I
> think it runs Vulture
> as an app, an not imports anything from it.
>
> I'll take a look and come back!
I've rechecked now ... actually Prospector imports vulture.py to work with it.
A Py3 package
on the side would be reasonable to have it available when Prospector gets
transfered to Py3
some day in the future. There are also other reasons to prepare it, but to
build/run Vulture
solely on Py3 is a non option because of that.
A Py3 package on the side ... the binaries-have-conflict could be handled like
Jakub suggested
for python-afl.
For the name of binaries, I would prefer "vulture{,3}" over
"python{,3}-vulture" like Pylint does
it, but it appears Pybuild expects this ... does it?
Daniel
--
http://www.danielstender.com/blog/
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#789699: vulture review
On 25.08.2015 19:17, Gianfranco Costamagna wrote: > Control: owner -1 ! > > Hi Daniel, I would appreciate if you could provide the python3 package, or > both. > > What do you think? according to setup.py the package is python3 ready, so > maybe > running pybuild --with python3, or providing two packages might be good. > > what do you think? ... yeah, this would be an option, Py3 as default is coming up, anyway. This is going to be an enhancement for Prospector, which is on Py2, but I think it runs Vulture as an app, an not imports anything from it. I'll take a look and come back! Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#796894: RFS: afl/1.86b-1 -- fuzzy tester for binary formats [ITA]
Package: sponsorship-requests Severity: normal Hi, I'm looking for an uploader for my new package of American Fuzzy Lop (afl), which is on ITA [1]. The package is Git-ized here: http://anonscm.debian.org/cgit/collab-maint/afl.git Build log: http://www.danielstender.com/buildlogs/afl_1.86b-1_amd64-20150825-1547.build Mentors upload: http://mentors.debian.net/debian/pool/main/a/afl/afl_1.86b-1.dsc Due to problems with clang-3.5 on arm64 [2] I've disabled the build for this arch temporarily, as Jakub suggested to do. Gianfranco has found out that the package builds again fine with >= clang-3.7. When this is in I want to prepare a -2 for experimental patched for llvm-toolchain-3.7 for those really need this on arm64. [1] https://bugs.debian.org/786806 ITA: afl -- instrumentation-driven fuzzer for binary formats [2] https://bugs.debian.org/796343 clang-3.5: [arm64] segfault in 'Greedy Register Allocator' -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#792447: Fwd: Re: Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP]
Forwarded Message Subject: Re: Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP] Date: Fri, 21 Aug 2015 14:25:34 +0200 From: Daniel Stender To: Gianfranco Costamagna On 21.08.2015 14:19, Gianfranco Costamagna wrote: > Control: tags -1 moreinfo > > Hi Daniel, > > I do not remember how we left this one, anyway: > > now with the llvm stuff being fixed/rebuilt, I asked for a give back of > afl, and it is actually building almost everywhere > (just arm64 needs investigation, and s390x/kfreebsd-amd64 needs an > llvm-toolchain-3.6 rebuild, > ongoing right now) > > How do you feel about updating afl, checking if everything is good and then > followup with python-afl? > > cheers, > > Gianfranco Hi Gianfranco, ... yes I was thinking about asking you if you would like to make a wrap out of both. AFL build again fine after the latest lvm-toolchain-3.5 update, so that are only the manpages are missing. I'm going to fix the AFL ITA over the weekend and come back then! Thanks! Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP]
On 10.08.2015 11:04, Gianfranco Costamagna wrote: > I did a look, and the packaging looks really good (and the upstream > maintainer too :) ). > > However prior to sponsor I would like to see afl working, otherwise it would > be not installable > on sid. > > (I'll try to work on llvm side in the next few days) > > Little (I guess not trivial to fix) nitpick: you might avoid pthread link > dpkg-shlibdeps: warning: package could avoid a useless dependency if > debian/python-afl/usr/lib/python2.7/dist-packages/afl.x86_64-linux-gnu.so was > not linked against libpthread.so.0 (it uses none of the library's symbols) > dpkg-shlibdeps: warning: package could avoid a useless dependency if > debian/python3-afl/usr/lib/python3/dist-packages/afl.cpython-34m-x86_64-linux-gnu.so > was not linked against libpthread.so.0 (it uses none of the library's > symbols) > > But I really do not think this is trivial to solve (more a cython problem > than a python-afl one IIRC) > > cheers, > Gianfranco Very much welcome! :-) Deal, when you've successfully fuzzed with it we go on with the sponsoring, I'll get into that link issue in the meanwhile. Best, Daniel -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55c870b3.2040...@danielstender.com
Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP]
I've rewritten deb/control and deb/rules to build with two packages, for Py2 and Py3. Fresh mentors upload is available. New buildlog: http://www.danielstender.com/buildlogs/python-afl_0.2.1-1_amd64-20150809-2223.build Thanks, DS -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55c7b98e.2050...@danielstender.com
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
... "convenient way to test build source packages against resp. on hurd-i386 or kfreebsd-amd64" ... on a Linux kernel machine. On 19.07.2015 17:52, Daniel Stender wrote: > Hi, > > I'm looking for a convenient way to test build source packages against resp. > on hurd-i386 or kfreebsd-amd64 instead of setting up simple "end user" Qemu > boxes and build within them. Sbuild and qemu-debootstrap somehow? > > Another question related to that, do FTBFS on these architectures block > transitions? > > Thanks in advance, > Daniel Stender -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55abca5f.4040...@danielstender.com
Build on hurd-i386 and kfreebsd-amd64 ... at home
Hi, I'm looking for a convenient way to test build source packages against resp. on hurd-i386 or kfreebsd-amd64 instead of setting up simple "end user" Qemu boxes and build within them. Sbuild and qemu-debootstrap somehow? Another question related to that, do FTBFS on these architectures block transitions? Thanks in advance, Daniel Stender -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55abc7b0.3070...@danielstender.com
Bug#792447: RFS: python-afl/0.2.1-1 -- American Fuzzy Lop fuzzy testing for Python code [ITP]
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for a sponsor of my package of python-afl [1]. The package source is stashed in a PAPT repo: http://anonscm.debian.org/viewvc/python-apps/packages/python-afl/trunk/ I've uploaded the package to mentors: http://mentors.debian.net/package/python-afl http://mentors.debian.net/debian/pool/main/p/python-afl/python-afl_0.2.1-1.dsc Build log: http://www.danielstender.com/buildlogs/python-afl_0.2.1-1_amd64-20150714-2243.build Thank you very much for considering, Daniel Stender [1] https://bugs.debian.org/792317 ITP: python-afl -- American fuzzy lop for Python -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55a57866.8050...@danielstender.com
Sbuild doesn't pick experimental over unstable
Hi, for the upcoming transition of Libvigraimpex I want to test build some packages against the version in experimental (1.10.0) locally in a Sbuild chroot. The problem is, I can add experimental as extra repository (--extra-repository), but the dependency solver won't pick over the package in Sid and always pulls 1.9.0 [1]. Is this the way it's mend to work? Is there a way to cheat this? Thanks Daniel Stender [1] http://paste.debian.net/280950/ -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/559f7503.4070...@danielstender.com
Bug#789497: RFS: python-requirements-detector/0.4-1 [ITP]
Hi Raphael, thank you very much! On 26.06.2015 21:20, Raphael Hertzog wrote: > Hello Daniel, > > On Sun, 21 Jun 2015, Daniel Stender wrote: >> I'm looking for an uploader resp. sponsor for my package of >> (python-)requirements-detector [1]. > > I took a look at your package. It's mostly good but you should not ship > /usr/bin/detect-requirements in both packages. > > Python 2 and Python 3 libraries must be co-installable. Since users of > a command line interface don't care if it's run with Python 2 or Python > 3 I suggest that you keep it in python3-requirements-detector and drop it > from python-requirements-detector. > > In some cases, it might make sense to put such scripts in a third package > but here I don't believe it's worth it. > > Please fix this (don't forget to adjust the package descriptions) and I'll > upload your package. Yes, that's better. Fixed that. http://anonscm.debian.org/cgit/python-modules/packages/python-requirements-detector.git/commit/?id=88b98a7b6f239189860bbd105d37eccc37c74374 > I also noted that the git repository that you created does not contain any > tag. Please push the upstream/* tags at least. All right. Tags are pushed. Mentors package updated. > Thanks for your work! My pleasure. Best, Daniel -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558e48e8.8060...@danielstender.com
Bug#789680: RFS: pep8-naming/0.3.1-1 [ITP]
On 24.06.2015 18:56, Daniel Stender wrote:
> On 24.06.2015 18:31, Andrey Rahmatullin wrote:
>> It's not working:
>
>> Traceback (most recent call last):
>> File "/usr/bin/flake8", line 9, in
>> load_entry_point('flake8==2.2.2', 'console_scripts', 'flake8')()
>> File "/usr/lib/python2.7/dist-packages/flake8/main.py", line 24, in main
>> flake8_style = get_style_guide(parse_argv=True,
>> config_file=DEFAULT_CONFIG)
>> File "/usr/lib/python2.7/dist-packages/flake8/engine.py", line 93, in
>> get_style_guide
>> options_hook(options)
>> File "/usr/lib/python2.7/dist-packages/pep8ext_naming.py", line 80, in
>> parse_options
>> cls.ignore_names = options.ignore_names.split(' ')
>> AttributeError: 'list' object has no attribute 'split'
>
> Yep, confirmed. Breaks.
>
> 0.3.2: Fix bug trying to call split on a list
>
> Coming up! Thanks!
>
> Dan
Updated.
DS
--
http://qa.debian.org/developer.php?login=debian%40danielstender.com
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/558bc670.1000...@danielstender.com
Bug#789680: RFS: pep8-naming/0.3.1-1 [ITP]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24.06.2015 18:31, Andrey Rahmatullin wrote:
> It's not working:
>
> Traceback (most recent call last):
> File "/usr/bin/flake8", line 9, in
> load_entry_point('flake8==2.2.2', 'console_scripts', 'flake8')()
> File "/usr/lib/python2.7/dist-packages/flake8/main.py", line 24, in main
> flake8_style = get_style_guide(parse_argv=True,
> config_file=DEFAULT_CONFIG)
> File "/usr/lib/python2.7/dist-packages/flake8/engine.py", line 93, in
> get_style_guide
> options_hook(options)
> File "/usr/lib/python2.7/dist-packages/pep8ext_naming.py", line 80, in
> parse_options
> cls.ignore_names = options.ignore_names.split(' ')
> AttributeError: 'list' object has no attribute 'split'
Yep, confirmed. Breaks.
0.3.2: Fix bug trying to call split on a list
Coming up! Thanks!
Dan
- --
http://qa.debian.org/developer.php?login=debian%40danielstender.com
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJViuEjAAoJEBXgmvTfUYLIhRMP/3DV3KxabMKhpB239TPO56DQ
TJarWHS3q8EYLCt1w6AbKtLKsKNrvDwkW9PXVMnGqzqjVKQqycijcVZg8yMhI6uI
yqPbWavQwfFtgOqceo8wApL7Zg5s/7r43WN9Sz4ugqMP4rmOieaxDmNUSVB1/SbL
yk6/sokvDjlj4sG2QOXhXysDEhfieVcDKUYBr7pHjovGXszb1jCz1S4a6GjkQBJi
4mvCRMwGH0Xit2sFVS5L0TopzP20tASwNw94wGDVB0iVpZb7KFbM+Qvlau4nfSc0
/EKQjFuVhDoBWHGkOFPKp3sH0lL0+3IEEre+7pC6uDgvbgXUfsgvlF6sOytrl1KA
DvUm5QLiqlJDbla7JZP/Etq62EqUyV66MF4LwI4yoeBQ2Oftx9Ycd6DWYNLEgjAu
SapKZiDyE+nbYj4P0tH1uWHLT4PczwIy4dOegQj5oHycWIIp/ryTVbd58oLQ8/cr
qk0I8Q1q3peUR7/2ShVFC7foVuQhovkTrTK3OaTkn9JeqZ1v3/kha7qM6D3O6zJS
pyAwwUtoAeOurHkc7S0te8AHKJfHeBboG1DtCxBu9lL7WqK0/Ejwc6Z3a+d6uVSj
Yp0JwgiT/2FInRh7CUw6YwB48xiOAqQOBDpLpFRH1FyfCurSqBz6aPZ6akwQQkbs
mqorR7ZeqasZN/WC+DCM
=eXdf
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/558ae123.3010...@danielstender.com
Bug#789712: RFS: pylint-celery/0.3-1 [ITP]
Hi Dmitry, thanks for checking this over! Yes, all right I've installed an override for dh_auto_test. However the test suite doesn't seem to be complete and breaks on some missing things. I've contacted upstream if it's supposed to run somehow. GPL short name changed. I've wondered myself but I found that all Pylint (the main modules and the recently added pylint-django and pylint-plugins-utils) happens with publically available libraries and therefore I think is really expected being in /dist-packages/. There are things in the borderland of library and app ... :-) Daniel On 24.06.2015 02:16, Dmitry Smirnov wrote: > Hi Daniel, > > On Tue, 23 Jun 2015 20:20:34 Daniel Stender wrote: >> I'm seeking for an uploader resp. sponsor of my package of pylint-celery > > I'm not sure if I'll be able to sponsor your package but I had a quick look > and spotted a problem in packaging: it is incorrect to override > DEB_BUILD_OPTIONS from "debian/rules". DEB_BUILD_OPTIONS should be available > to whoever builds your package to override default behaviour (for example > disable tests, etc.). > Correct way to disable tests is by using "override_dh_auto_test" where > you can invoke "-dh_auto_test" (that's right, with "minus" character) to run > tests but continue on their failures. If some tests are meaningful it might > be > useful to run them in order to capture tests output in build logs. > > Also I believe the correct name of the license is "GPL-2" instead of > "GPL-2.0". > > Finally I have some doubts whether this tiny plugin is worth exposing system- > wide -- if it is only used by Pylint then perhaps it could be installed > privately? Isn't that what Python team policy says? > -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558a5d36.2000...@danielstender.com
Bug#789712: RFS: pylint-celery/0.3-1 [ITP]
Package: sponsorship-requests Severity: wishlist Hello, I'm seeking for an uploader resp. sponsor of my package of pylint-celery [1]. It's a requirement for Prospector [2]. I've pushed the package to a new Git repo of the DPMT: http://anonscm.debian.org/cgit/python-modules/packages/pylint-celery.git Buildlog: http://www.danielstender.com/buildlogs/pylint-celery_0.3-1_amd64-20150623-2004.build Mentors upload: http://mentors.debian.net/package/pylint-celery http://mentors.debian.net/debian/pool/main/p/pylint-celery/pylint-celery_0.3-1.dsc Thanks, DS [1] https://bugs.debian.org/788235 ITP: pylint-celery -- Pylint plugin for analysing code using Celery [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5589a372.5010...@danielstender.com
Bug#789699: RFS: vulture/0.6-1 [ITP,PAPT]
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for an uploader resp. sponsor for my new package of vulture [1]. It's a recommendation for Prospector [2]. The package is injected into the PAPT repo: http://anonscm.debian.org/viewvc/python-apps/packages/vulture/trunk/ Buildlog: http://www.danielstender.com/buildlogs/vulture_0.6-1_amd64-20150623-1623.build Mentors upload: http://mentors.debian.net/package/vulture http://mentors.debian.net/debian/pool/main/v/vulture/vulture_0.6-1.dsc Some applications (like Prospector) expect the module vulture.py to be available publically. Thanks, DS [1] https://bugs.debian.org/788222 ITP: vulture -- scanner for unused Python code [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55896e68.2070...@danielstender.com
Bug#789680: RFS: pep8-naming/0.3.1-1 [ITP]
Package: sponsorship-requests Severity: wishlist Hello, I'm looking for a sponsor resp. uploaded of my new package of pep8-naming [1]. It's another prerequisite for Prospector [2]. I've injected the package to a new Git repo of the DPMT: http://anonscm.debian.org/cgit/python-modules/packages/pep8-naming.git Buildlog: http://www.danielstender.com/buildlogs/pep8-naming_0.3.1-1_amd64-20150623-1200.build Mentors upload: http://mentors.debian.net/package/pep8-naming http://mentors.debian.net/debian/pool/main/p/pep8-naming/pep8-naming_0.3.1-1.dsc Thanks, DS [1] https://bugs.debian.org/788234 ITP: pep8-naming -- check pep8 naming conventions in Python code (flake8 plugin) [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55893219.3020...@danielstender.com
Bug#789617: RFS: dodgy/0.1.7-1 [ITP,PAPT]
Automatically I've set up DEP-8 tests, but dodgy might really doesn't need that ... DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5589056e.1060...@danielstender.com
Bug#789617: RFS: dodgy/0.1.7-1 [ITP,PAPT]
Package: sponsorship-requests Severity: wishlist Hi, I'm looking to an uploaded resp. sponsor for my new package of dodgy [1]. That's yet another prerequisite for Prospector [2]. I've injected the package to a new SVN repo of the PAPT: http://anonscm.debian.org/viewvc/python-apps/packages/dodgy/trunk/ Buildlog: http://www.danielstender.com/buildlogs/dodgy_0.1.7-1_amd64-20150622-1948.build Mentors source package: http://mentors.debian.net/package/dodgy http://mentors.debian.net/debian/pool/main/d/dodgy/dodgy_0.1.7-1.dsc The same as pep257 [3]: it's an app with its modules needed public by some other things like Prospector. Thanks, DS [1] https://pypi.python.org/pypi/dodgy/0.1.7 [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool [3] https://bugs.debian.org/789595 RFS: pep257/0.5.0-1 -- static Python code analysis tool [ITP] -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55884d40.6030...@danielstender.com
Bug#789595: RFS: pep257/0.5.0-1 -- static Python code analysis tool [ITP]
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for an uploader resp. sponsor for my new package of pep257 [1]. That's another prerequisite for Prospector [2]. I've injected the package to a new SVN repo of the PAPT: http://anonscm.debian.org/viewvc/python-apps/packages/pep257/trunk/ The buildlog is here: http://www.danielstender.com/buildlogs/pep257_0.5.0-1_amd64-20150622-1350.build Mentors upload: http://mentors.debian.net/package/pep257 http://mentors.debian.net/debian/pool/main/p/pep257/pep257_0.5.0-1.dsc Before that gets complained, pep257 is basically an app, however some other things like e.g. Prospector expect pep257.py to be available publically. Thanks, DS [1] https://pypi.python.org/pypi/pep257 [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/558800ad.8050...@danielstender.com
Bug#789520: RFS: python-setoptconf/0.2.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Hello, I'm looking for an uploaded resp. sponsor for my package of (python-)setoptconf [1]. It's another prerequisite for Prospector [2]. The package is pushed to a new Git repo of the DPMT: http://anonscm.debian.org/cgit/python-modules/packages/python-setoptconf.git The buildlog is here: http://www.danielstender.com/buildlogs/python-setoptconf_0.2.0-1_amd64-20150621-2013.build A mentors upload is here: http://mentors.debian.net/package/python-setoptconf http://mentors.debian.net/debian/pool/main/p/python-setoptconf/python-setoptconf_0.2.0-1.dsc It builds all right, but I would be grateful for a suggestion how to get the tests running also for Py3 (the package builds with use_2to3). Thanks, Daniel Stender [1] https://bugs.debian.org/788212 ITP: python-setoptconf -- retrieve program settings from various sources [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55870267.9020...@danielstender.com
Bug#789497: RFS: python-requirements-detector/0.4-1 [ITP]
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for an uploader resp. sponsor for my package of (python-)requirements-detector [1]. It's a prerequisite for Prospector [2]. The package is already pushed to a new Git repo of the DPMT: http://anonscm.debian.org/cgit/python-modules/packages/python-requirements-detector.git The buildlog is here: http://www.danielstender.com/buildlogs/python-requirements-detector_0.4-1_amd64-20150621-1611.build Mentors upload is available here: http://mentors.debian.net/package/python-requirements-detector http://mentors.debian.net/debian/pool/main/p/python-requirements-detector/python-requirements-detector_0.4-1.dsc Thanks, Daniel Stender [1] https://bugs.debian.org/788208 ITP: python-requirements-detector -- find and list requirements of a Python project [2] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5586cb52.5060...@danielstender.com
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
The state of the package is: I'm not sure if it's o.k. for it to get accepted into the archive when a DFSG compliant change of the license is declared for the project but the actual file headers state something different. For that I've added a patch which disables the style check over by default for the +dfsg package w/o the RELAX NG schemes which would do it until the files get updated. With that the citeproc just does not warn for faulty custom styles, which is great to have but could be dispensed for a while [1]. I would like to discuss this option with the sponsor, maybe it's possible to push it non +dfsg already which a Comment link to the declaration of the new licensing. Anyway, I've uploaded the latest package to mentors [2]. DS [1] The other citeproc in Debian, the Haskell pandoc-citeproc does not feature the schemes at all: https://packages.debian.org/stretch/all/libghc-pandoc-citeproc-data/filelist [2] http://mentors.debian.net/debian/pool/main/c/citeproc-py/citeproc-py_0.3.0+dfsg-1.dsc -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5583d683.2090...@danielstender.com
Bug#775532: license of the CSL scheme files
Great! Thank you very much. Best, Daniel On 18.06.2015 16:37, Rintze Zelle wrote: > http://citationstyles.org/developers/ now says "Note. All versions of > the CSL schema have recently been relicensed under the more > permissible MIT license, and the GitHub repository will soon be > updated to reflect this change.". > > I'll add the MIT license to the repository and change the "rights" > blurb in the schema itself, but it might be a while before I get to > that. > > Rintze -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5582d8f4.7070...@danielstender.com
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
I've checked some deeper and found that at least schema/csl.rng is needed by the build in scheme validator in citeproc/frontend.py. In the SVN repo there are some waste experiments towards a +dfsg package - I'll complete everything when the new licenses are declared. DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5581cde1.8050...@danielstender.com
Bug#775532: license of the CSL scheme files
Thank you very much for the reply. Yes I think a link to something like this on the project's page would do it until then, great! I'll check for it and put in the copyright register in the package, then. Greetings, Daniel On 14.06.2015 17:26, Rintze Zelle wrote: > Hi Daniel, > > Bruce D'Arcus and I think that the MIT license might be the best > option for relicensing the CSL schema. I just proposed the change on > our mailing list > (http://xbiblio-devel.2463403.n2.nabble.com/MIT-license-as-default-for-CSL-software-tp7579193p7579395.html), > but I don't expect any objections. We certainly always wish to be > FOSS-compatible and nonrestrictive. > > If nobody objects to the MIT license, it might still be a while before > I get to updating all the schema files with the new license, so maybe > I'll just make a note to that effect on http://citationstyles.org/. > You can also rely on this email for permission to package the schema > under MIT-license terms. > > Best, > > Rintze -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d9eb5.7010...@danielstender.com
Bug#775532: license of the CSL scheme files
Hi Rintze, (we've been in contact last year on my TUGBOAT article on CSL) I'm packaging Brecht Machiel's citepyroc-py for Debian and we have an issue over the license of the CSL scheme files (schema/*) which are shipped with this: for the locales and the style files it's clearly stated (headers, sources) that they're CC-BY-SA-3.0, but the only thing we could find stated for the scheme files is "Permission to freely use, copy and distribute", which doesn't comply to the free software guidelines of Debian. Is it's really mend that the scheme files are distributed under more restrict conditions than the other elements of CSL? If that's not the case, could this be declared somewhere? Greetings, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d4728.6050...@danielstender.com
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
Sorry I was busy. Thank you for reviewing the package! I think the RELAX NG scheme files for CSL style files aren't necessary for the citeproc to run anyway, nor really necessary to have them in the package. I'll get into that again today. DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557d3b46.4040...@danielstender.com
Bug#780793: RFS: hovercraft/2.0~b1+dfsg-1 [ITP] --- impress.js presentations by reStructuredText
I've injected Hovercraft to the group's SVN repo [1] now. It'll take part in the upcoming svn-git migration procedure then and will find itself in the proper git repo automatically. DS [1] svn+ssh://lo...@svn.debian.org/svn/python-apps/packages/hovercraft -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/555713de.60...@danielstender.com
Bug#784749: RFS: gamera/3.4.2-1 -- document analysis framework
Package: sponsorship-requests Severity: normal Hello, I'm searching for a sponsor/uploader for a new package of Gamera. The changelog is: gamera (3.4.2-1) unstable; urgency=medium * New upstream release. * Added constant-seed-for-docs.diff to make build reproducible by using constant seed for generation of example/documentation images (Closes: #775228). * Added docs-no-modified-timestamp.diff (Closes: #784680). * deb/control: + added dh-python to build-deps. + updated Vcs fields (moved to git). * deb/copyright: updated. * deb/patches: + fix-typos.diff: corrected path error. + dropped avoid_mktemp.diff, gendoc-version-parsing.diff, suppress- wxdebug-assertion-messages.diff, wxpython3.0-transition.diff (applied upstream). + added gendoc-no-sflogo.diff (dropped sflogo removal from deb/rules). * Added deb/gbp.conf. -- Daniel Stender Fri, 08 May 2015 14:16:58 +0200 In the main it's the new upstream release (which incorporated several patches towards the wxpython 3.0 transition) plus two new patches for reproducible building. Buildlog: http://www.danielstender.com/buildlogs/gamera_3.4.2-1_amd64-20150508-1418.build The repo has moved to Git: http://anonscm.debian.org/cgit/python-modules/packages/gamera.git git://anonscm.debian.org/python-modules/packages/gamera.git Mentors upload: http://mentors.debian.net/debian/pool/main/g/gamera/gamera_3.4.2-1.dsc http://mentors.debian.net/package/gamera I'm DM, thus alternatively/additionally upload rights could be granted. Thanks for consideration, DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cb15c.2040...@danielstender.com
Bug#783676: RFS: gummi/0.6.5-4 -- GTK+ based LaTeX editor with live preview
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: debian-scie...@lists.debian.org I'm looking for a uploader/sponsor of this new package of Gummi. gummi (0.6.5-4) unstable; urgency=low * Use synctex parser provided by libsynctex-dev (Closes: #753827): + added use-system-synctex.patch (thanks to Sebastian Ramacher). + added libsyntex-dev to b-ds. * deb/changelog: fixed typos. * deb/control: + Updated Maintainer and Uploaders (package moved to Debian Science). + bumped standards to 3.9.6 (no changes needed). + updated Vcs-Git and -Browser (Debian Science), and Homepage (project moved to Github). * deb/copyright: updated. * deb/rules: removed override for dh_installchangelogs (obsolete). * deb/watch: updated (moved to Github). * added deb/gbp.conf, deb/source/local-options. * wrap-and-sort -a -s. -- Daniel Stender Wed, 29 Apr 2015 07:14:01 +0200 Buildlog: http://www.danielstender.com/buildlogs/gummi_0.6.5-4_amd64-20150429-0715.build Mentors upload: http://mentors.debian.net/debian/pool/main/g/gummi/gummi_0.6.5-4.dsc The package repo moved to Debian Science [1]. I'm DM, thus alternatively/additionally uploading rights for this package could be granted. I'm going to file a SoB entry, too. Thank for consideration, Daniel Stender [1] http://anonscm.debian.org/cgit/debian-science/packages/gummi.git -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55406c96.1060...@danielstender.com
Bug#776571: RFS: svg.path/2.0~b1-1 -- [ITP] Python modules providing SVG objects
Maybe it could be discussed if python-svg.path would be a better name even for the source package. Could be put into Git before the initial upload with that repo name. DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55375802.9060...@danielstender.com
Re: packaging with cmake
On 14.04.2015 20:47, Jerome BENOIT wrote: > Hello List, > > II am on my way to package normaliz [1] which can be built either > with ready to use Makefile or with cmake. Since the cmake setup is the > one advised by the upstream team (while on the other hand the furnished > Makefile may need refreshment), I will first give a try to the cmake > machinery. > > So I am looking for a well debiannized software that builts with cmake: > any idea ? > > thanks in advance, > Jerome > > > [1] bugs.debian.org/776019 e.g. Scantailor Greetings, DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/552d6aa1.7070...@danielstender.com
Bug#780793: RFS: hovercraft/2.0~b1+dfsg-1 [ITP] --- impress.js presentations by reStructuredText
Package: sponsorship-requests Severity: wishlist Hello mentors, I am looking for a sponsor for my package of "hovercraft" [1]. The software is written in Python and generates beautiful impress.js based presentations which could be displayed in a browser [2], from reST sources. I've git-ized the source at collab maint [3] for now, but would like to put it under the umbrella of the PAPT - the repo could be transfered to git.debian.org/git/python-applications when it becomes available with ease (Vcs- fields kept blank). The dfsg- packaging is to take out a Python logo image which is shipped in the orig for the examples and the tests [4]. I've patched the examples but disabled the tests for now. They need python3-manuel, which is not yet available [5], anyway. I'm going to ask upstream if the image could be replaced for the next release, then. The status of the binary deps not-yet-in-unstable is, python3-watchdog is currently in NEW, python3-svg.path is also RFS [6]. The package has been uploaded to Mentors: http://mentors.debian.net/package/hovercraft http://mentors.debian.net/debian/pool/main/h/hovercraft/hovercraft_2.0~b1+dfsg-1.dsc Buildlog: http://www.danielstender.com/buildlogs/hovercraft_2.0~b1+dfsg-1_amd64-20150319-1332.build Thank you for considering a sponsorship, Daniel Stender [1] https://github.com/regebro/hovercraft [2] http://bartaz.github.io/impress.js/ [3] http://anonscm.debian.org/cgit/collab-maint/hovercraft.git [4] https://lists.debian.org/debian-legal/2015/03/msg3.html [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776885 [6] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776571 -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/550adf72.2060...@danielstender.com
Python logo license
Hi folks, I've got the official Python logo image [1] here in a package. 1) what would be the proper license for that file in deb/copyright? 2) what's the best place in Debian to ask copyright/licensing related questions like this in the future, the developer's list? Thanks in advance, Daniel Stender [1] https://www.python.org/static/community_logos/python-logo-master-v3-TM.png -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54f1e0c4.2030...@danielstender.com
Re: Qemubuilder for arm64?
Thanks guys for the pointer to qemu-debootstrap. I've experimented some on that and came out the wrapper works pretty well also with Sbuild, as easy as: # sbuild-createchroot --arch=arm64 --debootstrap=qemu-debootstrap --make-sbuild-tarball=/var/lib/sbuild/sid-arm64.tar.gz sid `mktemp -d` http://http.debian.net/debian BTW that also seems to work with arch armhf against Raspbian ... Greetings, Daniel Stender On 20.11.2014 00:14, Wookey wrote: > +++ Daniel Stender [2014-11-19 21:41 +0100]: >> Hi, >> >> I'm trying to get Qemubuilder run for arm64 package building, but fails >> so far. I've got a proper kernel and initrd, but breaks with: >> "Your architecture arm64 does not seem to be supported". Maybe that's >> exactly how it is, is it? > > I am not familiar with qemubuilder. What does it do? > > I can tell you that qemu works fine for arm64 and has for a while. > > qemu-debootstrap will make you a qemu-ready chroot you can build in. > >> Does anybody has got Qemubuilder run for arm64, or have any pointers >> to other cross-package-building solutions other than building in >> a Qemu box itself? > > amd64->arm64 cross-toolchains for Jessie and unstable exist: > https://wiki.debian.org/CrossToolchains has details. > > This stuff is still quite new and I'm moving things around at the > moment. Note that the unstable cross-toolchains are uninstallable for > a couple of days after each new gcc upload until new ones are rebuilt > to match. Updated packages should be uploaded tomorrow. > > Wookey -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54e0ddc3.3010...@danielstender.com
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
I've put the package into the DPMT team repo (SVN for now): svn://anonscm.debian.org/python-modules/packages/citeproc-py/trunk/ http://anonscm.debian.org/viewvc/python-modules/packages/citeproc-py/trunk/ A fresh package with the Svn fields and some minor changes is uploaded to Mentors. Buildlog: http://www.danielstender.com/buildlogs/citeproc-py_0.3.0-1_amd64-20150204-1529.build Thanks, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d22d3b.8030...@danielstender.com
Bug#775595: RFS: pyuca/1.0-1 [ITP] -- Python Unicode sorting library
... looking for my package of ... of course DS -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d0d1d0.5010...@danielstender.com
Bug#776885: RFS: manuel/1.8.0-1 [ITP] -- Python library for documented tests
Package: sponsorship-requests Severity: wishlist Hi, I'm looking for a sponsor for my package of Manuel 1.8.0 [1]. It builds those binary packages: python-manuel - Python library for testable documents and documented tests python3-manuel - Python3 library for testable documents and documented tests Mentors upload: http://mentors.debian.net/package/manuel http://mentors.debian.net/debian/pool/main/m/manuel/manuel_1.8.0-1.dsc Buildlog: http://www.danielstender.com/buildlogs/manuel_1.8.0-1_amd64-20150202-2204.build I've made everything ready for a injection into the DPMT repository (SVN fields and Uploaders present). Thank you very much, Daniel Stender [1] https://pypi.python.org/pypi/manuel/ -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54cfea7e.3020...@danielstender.com
Bug#776571: RFS: svg.path/2.0~b1-1 -- [ITP] Python modules providing SVG objects
Package: sponsorship-requests Severity: wishlist Hello, I am looking for a sponsor for my package of svg.path: * Package name: svg.path Version : 2.0b1 Upstream Author : Lennart Regebro * URL : https://github.com/regebro/svg.path * License : CC0-1.0 Programming Lang: Python Description : Python library providing SVG path objects and parser It builds those binary packages: python-svg.path - SVG path objects and parser for Python python3-svg.path - SVG path objects and parser for Python3 Description: SVG path objects and parser for Python In SVG (Scalable Vector Graphics), paths are used to draw simple or compounded shape outlines. svg.path is a collection of objects that implement the path commands in SVG (Line, Arc, QuadraticBezier, CubicBezier), and a parser for SVG path definitions. Buildlog: http://www.danielstender.com/buildlogs/svg.path_2.0~b1-1_amd64-20150129-1319.build For a member of this group, I've already put it under the care of the DPMT: http://anonscm.debian.org/viewvc/python-modules/packages/svg.path/trunk/ And uploaded it to Mentors: http://mentors.debian.net/package/svg.path dget -x http://mentors.debian.net/debian/pool/main/s/svg.path/svg.path_2.0~b1-1.dsc Thank you very much for considering, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ca2cb9.6020...@danielstender.com
Bug#775595: RFS: pyuca/1.0-1 [ITP] - Python Unicode sorting library
Package: sponsorship-requests Severity: wishlist Hello, I am looking for my package of Pyuca, which I've uploaded onto Mentors [1]. That's a useful Python3 implementation of the Unicode Collation Algorithm, for further infos on this please see the ITP [2]. I'm a member of the DPMT, so would be good under that umbrella (incl. Git-izing). Thank you very much for considering, Daniel Stender [1] https://mentors.debian.net/package/pyuca [2] ITP: https://bugs.debian.org/768968 -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54bac385.3010...@danielstender.com
Bug#775532: RFS: citeproc-py/0.3.0-1 [ITP] -- Python library for CSL based bibliography processing
Package: sponsorship-requests Severity: wishlist I am looking for a sponsor of my package of citeproc-py, which is a Python library for typesetting formatted bibliographies out of (so far) BibTeX and JSON databases, according to CSL (Citation Style Language) styles [1]. The initial package is stashed on Mentors [2]. I'm joining the DPMT, would be a good idea to put it under that umbrella (incl. Git-izing). Thank you very much for considering, Daniel Stender [1] ITP: https://bugs.debian.org/769159 [2] http://mentors.debian.net/package/citeproc-py -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b9861e.6030...@danielstender.com
Bug#772130: RFS: gamera/3.4.1+svn1423-3 [RC] -- document analysis framework
3.4.1+svn1423-3 contains also changes of some patch headers toggled forwarded, which the release team confirmed it's o.k. with the freeze policy [1]. Daniel Stender [1] http://bugs.debian.org/769394 (unblock: gamera/3.4.1+svn1423-2) -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54819aa0.6050...@danielstender.com
Bug#772130: RFS: gamera/3.4.1+svn1423-3 [RC] -- document analysis framework
Package: sponsorship-requests Severity: important Hello, I'm looking for a uploader of my latest package of Gamera, on AUTORM for 2014-12-22. It fixes the RC serious bugs 766740 and 770646 (FTBFS on arm64). I've pretested on a local Qemu setup and it appears to build fine on that architecture, but that's a package for experimental to test it again before uploading into Sid. Buildlog: http://www.danielstender.com/buildlogs/gamera_3.4.1+svn1423-3_amd64.build Mentors upload: http://mentors.debian.net/debian/pool/main/g/gamera/gamera_3.4.1+svn1423-3.dsc Debdiff attached. Thank you very much for consideration. Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 diff -Nru gamera-3.4.1+svn1423/debian/changelog gamera-3.4.1+svn1423/debian/changelog --- gamera-3.4.1+svn1423/debian/changelog 2014-11-12 10:01:41.0 +0100 +++ gamera-3.4.1+svn1423/debian/changelog 2014-11-20 13:54:54.0 +0100 @@ -1,3 +1,10 @@ +gamera (3.4.1+svn1423-3) experimental; urgency=medium + + * Build dbg on arm64 with different optimization (Closes: #766740). + * Some patches toggled forwarded. + + -- Daniel Stender Thu, 20 Nov 2014 13:54:10 +0100 + gamera (3.4.1+svn1423-2) unstable; urgency=medium * Added gendoc-version-parsing.diff (Closes: #767158). diff -Nru gamera-3.4.1+svn1423/debian/patches/avoid_mktemp.diff gamera-3.4.1+svn1423/debian/patches/avoid_mktemp.diff --- gamera-3.4.1+svn1423/debian/patches/avoid_mktemp.diff 2014-07-09 01:49:56.0 +0200 +++ gamera-3.4.1+svn1423/debian/patches/avoid_mktemp.diff 2014-11-13 11:10:26.0 +0100 @@ -1,6 +1,6 @@ Description: Fixed security hole because of usage of tmpfile.mktemp() -Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737324 -Forwarded: no +Bug: http://bugs.debian.org/737324 +Forwarded: yes Author: Daniel Stender Last-Update: 2014-07-09 --- a/gamera/io.py diff -Nru gamera-3.4.1+svn1423/debian/patches/gendoc-use-wxversion.diff gamera-3.4.1+svn1423/debian/patches/gendoc-use-wxversion.diff --- gamera-3.4.1+svn1423/debian/patches/gendoc-use-wxversion.diff 2014-08-06 13:25:21.0 +0200 +++ gamera-3.4.1+svn1423/debian/patches/gendoc-use-wxversion.diff 2014-11-13 11:10:26.0 +0100 @@ -2,7 +2,7 @@ Make the documentation generator prefer wxPython 2.8 over other versions. This patch is intended to alleviate Debian bug #451104. Author: Jakub Wilk -Forwarded: not-needed +Forwarded: yes Reviewed-by: Daniel Stender Last-Update: 2014-08-06 diff -Nru gamera-3.4.1+svn1423/debian/patches/gendoc-version-parsing.diff gamera-3.4.1+svn1423/debian/patches/gendoc-version-parsing.diff --- gamera-3.4.1+svn1423/debian/patches/gendoc-version-parsing.diff 2014-11-12 10:01:19.0 +0100 +++ gamera-3.4.1+svn1423/debian/patches/gendoc-version-parsing.diff 2014-11-13 11:10:26.0 +0100 @@ -4,7 +4,7 @@ but fulfills what's needed here Author: Daniel Stender Bug: http://bugs.debian.org/767158 -Forwarded: no +Forwarded: yes Last-Update: 2014-10-29 --- a/gamera/gendoc.py diff -Nru gamera-3.4.1+svn1423/debian/patches/suppress-wxdebug-assertion-messages.diff gamera-3.4.1+svn1423/debian/patches/suppress-wxdebug-assertion-messages.diff --- gamera-3.4.1+svn1423/debian/patches/suppress-wxdebug-assertion-messages.diff 2014-09-05 15:30:41.0 +0200 +++ gamera-3.4.1+svn1423/debian/patches/suppress-wxdebug-assertion-messages.diff 2014-11-13 11:10:26.0 +0100 @@ -3,7 +3,7 @@ on exit Author: Daniel Stender Bug: http://bugs.debian.org/758578 -Forwarded: no-needed +Forwarded: yes Last-Update: 2014-08-26 --- a/gamera/gui/gui.py diff -Nru gamera-3.4.1+svn1423/debian/patches/wxpython3.0-transition.diff gamera-3.4.1+svn1423/debian/patches/wxpython3.0-transition.diff --- gamera-3.4.1+svn1423/debian/patches/wxpython3.0-transition.diff 2014-08-26 10:04:33.0 +0200 +++ gamera-3.4.1+svn1423/debian/patches/wxpython3.0-transition.diff 2014-11-13 11:10:26.0 +0100 @@ -3,7 +3,7 @@ cf. http://bugs.debian.org/758578, so completely disabled here Bug: http://bugs.debian.org/757208 Author: Daniel Stender -Forwarded: no +Forwarded: yes Last-Update: 2014-08-26 --- a/gamera/gui/gamera_display.py diff -Nru gamera-3.4.1+svn1423/debian/rules gamera-3.4.1+svn1423/debian/rules --- gamera-3.4.1+svn1423/debian/rules 2014-10-08 13:05:18.0 +0200 +++ gamera-3.4.1+svn1423/debian/rules 2014-11-20 13:26:59.0 +0100 @@ -8,10 +8,16 @@ export PYTHONHASHSEED=random export CFLAGS = $(shell dpkg-buildflags --get CFLAGS) -export CFLAGS_noopt = $(patsubst -O2,-Og,$(CFLAGS)) export CPPFLAGS = $(shell dpkg-buildflags --get CPPFLAGS) export LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS) +DEB_BUILD_ARCH := $(shell dpkg-architecture -qDEB_BUILD_ARCH) +ifeq ($(DEB_BUILD_ARCH),arm64) +export CFLAGS_noopt = $(patsubst -O2,-O0,$(CFLAGS)) +else +export CFLAGS_noopt = $(patsubst -O2,-
Qemubuilder for arm64?
Hi, I'm trying to get Qemubuilder run for arm64 package building, but fails so far. I've got a proper kernel and initrd, but breaks with: "Your architecture arm64 does not seem to be supported". Maybe that's exactly how it is, is it? Does anybody has got Qemubuilder run for arm64, or have any pointers to other cross-package-building solutions other than building in a Qemu box itself? Thanks in advance, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/546d008a.5030...@danielstender.com
Re: Versioning for cherry picked after-freeze RC fixing packages
Thanks! Greetings, Daniel Stender On 07.11.2014 00:12, Jakub Wilk wrote: > * Daniel Stender , 2014-11-06, 21:27: >> But further following the idea of an separate package, what about >> "-3+jessie1"? Is that a case for which this scheme is mend? > > The + scheme is obsolete. If anything, it should be > "-3+deb8u1". > > Documentation: last paragraph of Developer's Reference §5.11.2. (This > section is about NMUs, but the advice regarding forking version applies > to the non-NMU case as well.) -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545c0ebb.4070...@danielstender.com
Re: Versioning for cherry picked after-freeze RC fixing packages
Commit history and changelog "doesn't match" didn't mean they are connected, but maybe that's rubbish anyway ... But yes, simply unstaging the commits and reconstructing the repo for that -4/-5 would be a way, thank you very much for the suggestion. But further following the idea of an separate package, what about "-3+jessie1"? Is that a case for which this scheme is mend? Greetings, Daniel Stender On 06.11.2014 20:59, Tobias Frost wrote: > Why not just revert your commits (by applying undoing commits) and then > apply the fixes neccessary to do the RC-4? > > After a upload, you can reapply them. The SVN log is not really linked > to the debian/changelog. > > A NMU-style version would be wrong, IMHO. > > -- > tobi -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545bd9a7.4020...@danielstender.com
Versioning for cherry picked after-freeze RC fixing packages
Hi, I'm searching a procedure for the following case: 1) against one my packages (it's Deap), currently a "-3" in Testing, a RC critical bug has been filed 2) the fix for that bug is already available together with other further developments as "-4" in the SVN repo, I am collecting improvements for a future package there, 3) but only RC critical bug fixes are accepted into Testing now, so I thought about creating a package "-4" which only contains the bug fix, and push the other changes into "-5" in the changelog, that's easy, 4) but then, I cannot tag the "-4" anywhere because the SVN commit history doesn't match the changelog, 5) I was thinking about creating a minor version number "-3.1" for the RC bug fix, but that's preserved for NMU (Lintian complaint), which it isn't Any experiences how to proceed? It's going to be sponsored anyway, asking the sponsor or the release team to just upload a NMU "-3.1"? Greetings, Daniel Stender -- http://qa.debian.org/developer.php?login=debian%40danielstender.com GPG key: 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545ba2f6.1060...@danielstender.com
Bug#755410: RFS: python-xmp-toolkit/2.0.1-1 [ITA] -- Python library for XMP
On 29.08.2014 15:52, Eriberto wrote: Further, I would like to package the latest git rev. as 2.0.1~git000-1, do you agree? Yes! But I think that the correct is 2.0.1~git20140309.984fb5. To see more examples: $ dpkg -l | grep -i git. Alright. I've checked out the latest revision which was pushed on the same day, it just completed CHANGELOG and AUTHORS: https://github.com/python-xmp-toolkit/python-xmp-toolkit/commit/5437b0ac5f756762ceba30bf97486d049727cd0b There appears an additional author email address, which I've also added to deb/changelog: http://lists.alioth.debian.org/pipermail/python-modules-commits/2014-August/029616.html The updated build is: http://www.danielstender.com/buildlogs/python-xmp-toolkit_2.0.1~git20140309.5437b0a-1_amd64.build Pushed also to mentors: http://mentors.debian.net/debian/pool/main/p/python-xmp-toolkit/python-xmp-toolkit_2.0.1~git20140309.5437b0a-1.dsc Greetings, Daniel -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54008ebd.8020...@danielstender.com
Bug#755410: RFS: python-xmp-toolkit/2.0.1-1 [ITA] -- Python library for XMP
Eriberto,
thank you very much for reviewing my package.
On 28.08.2014 21:49, Eriberto Mota wrote:
1. d/copyright says that upstream copyright years are 2008-2009.
However, the upstream changelog has newer dates. Please, update the
years.
The changelog spans up to 2.0.0 of 2013.
I've rechecked the repo and found that our tarball 2.0.1 is actually a
beta (Git releases: "2.0.1 release preparation"). AAMOF the repo
contains an updated changelog with infos on release 2.0.1 (spanning to
2014).
So, I've updated deb/copyright to the actual year of the code, 2014.
Further, I would like to package the latest git rev. as
2.0.1~git000-1, do you agree?
I've also updated an Upstream-Contact email address according to AUTHOR.
2. Remove the useless file d/source/options.
Yes, that's obselete. Removed it.
3. A problem: after the build of the binary python-libxmp-doc, the new
files usr/share/doc/python-libxmp-doc/html/_static/{basic,default}.css
have this header:
* Sphinx stylesheet -- default theme.
*
* :copyright: Copyright 2007-2014 by the Sphinx team, see AUTHORS.
* :license: BSD, see LICENSE for details.
It is an inedit situation for me, but the license must be placed at
d/copyright. So, I suggest put it in d/copyright and add a field
'comment'[1] to explain about this.
[1] http://dep.debian.net/deps/dep5/#fields
I've added that to deb/copyright. License details I've taken from
LICENSE of the python-sphinx source package.
4. Note that your package has new binaries (.deb) and will be NEW.
Yes, alright.
Thanks for your work. Your packaging is very good.
Thanks for encouraging, nice!
For the fresh build, please cf.
http://lists.alioth.debian.org/pipermail/python-modules-commits/2014-August/029615.html
http://svn.debian.org/viewsvn/python-modules/packages/python-xmp-toolkit/trunk/
http://www.danielstender.com/buildlogs/python-xmp-toolkit_2.0.1-1_amd64.build
http://mentors.debian.net/debian/pool/main/p/python-xmp-toolkit/python-xmp-toolkit_2.0.1-1.dsc
Greetings,
Daniel Stender
--
http://www.danielstender.com/blog/
PGP key: 2048R/E41BD2D0
C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/540078e0.9020...@danielstender.com
Bug#757675: RFS: python-djvulibre/0.3.9-2 -- Python support for the DjVu image container format
Hi Vincent, much thanks for the review. On 10.08.2014 14:54, Vincent Bernat wrote: Not much to say. Are you sure that upstream-signing-key.pgp is at the right location? The manual page for uscan still says debian/upstream/signing-key.pgp. When I try, I get: Newest version on remote site is 0.3.9, local version is 0.3.9 => Forcing download as requested -- Downloading updated package python-djvulibre-0.3.9.tar.gz -- Downloading OpenPGP signature for package as python-djvulibre-0.3.9.tar.gz.pgp -- Verifying OpenPGP signature python-djvulibre-0.3.9.tar.gz.pgp for python-djvulibre-0.3.9.tar.gz gpgv: Signature made lun. 19 mars 2012 21:02:31 CET using RSA key ID 015475F5 gpgv: [don't know]: invalid packet (ctb=2d) gpgv: keydb_search failed: invalid packet gpgv: Can't check signature: public key not found uscan warning: OpenPGP signature did not verify. Yes, that doesn't work: it's not the developer's public key. Corrected. -- Downloading OpenPGP signature for package as python-djvulibre-0.3.9.tar.gz.pgp -- Verifying OpenPGP signature python-djvulibre-0.3.9.tar.gz.pgp for python-djvulibre-0.3.9.tar.gz gpgv: Signature made Mo 19 Mär 2012 21:02:31 CET using RSA key ID 015475F5 gpgv: Good signature from "Jakub Wilk " gpgv: aka "Jakub Wilk " gpgv: aka "Jakub Wilk " gpgv: aka "[invalid image]" -- Successfully downloaded updated package python-djvulibre-0.3.9.tar.gz -- Successfully renamed /tmp/python-djvulibre-0.3.9.tar.gz to /tmp/python-djvulibre_0.3.9.orig.tar.gz. -- Scan finished Also, you may want to remove debian/patches when it is empty. Removed. Greetings, Daniel -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e77d3a.20...@danielstender.com
Bug#757675: RFS: python-djvulibre/0.3.9-2 -- Python support for the DjVu image container format
Package: sponsorship-requests Severity: normal Hello, I'm looking for a sponsor for my new package of python-djvulibre, which now also builds Python3 packages. It appears to be Lintian clean. For changes, please cf. http://lists.alioth.debian.org/pipermail/python-modules-commits/2014-August/029360.html http://lists.alioth.debian.org/pipermail/python-modules-commits/2014-August/029361.html (changelog update) The Debian patch is community maintained: http://anonscm.debian.org/viewvc/python-modules/packages/python-djvulibre/trunk/ Mentors upload: http://mentors.debian.net/package/python-djvulibre Buildlog: http://www.danielstender.com/buildlogs/python-djvulibre_0.3.9-2_amd64.build Changelog: * deb/control: + Updated maintainer email address. + Removed unneccesary b-ds and updated for Python3 packages. + Added Python3 package descriptions (Closes: #604037). + Bumped standards to 3.9.5 (no further changes needed). + Use canonical URIs for Vcs-* fields [Jakub Wilk]. * deb/copyright: + Changed Source URI to code repo. + Updated Format-Specification, copyright spans and email addresses. * deb/rules: + added DEB_BUILD_OPTIONS export line. + build with pybuild, reduced. + added doc/credits.txt to dh_installdocs for all packages. + build documentation with dh_sphinxdoc. * Dropped .install-s (unneeded), .examples (moved to doc package), -doc.links, updated -doc.doc-base. * deb/compat: bumped Debhelper level to 9. * deb/watch: added pgpsigurlmangle (also added deb/upstream-signing-key.pgp). * Added \.egg.info to source/options. * Wrapped-and-sorted -a. Thank you very much for considering, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e75092.3050...@danielstender.com
Bug#755718: Fwd: Re: Bug#755718: RFS: nltk/3.0.0b1-1 [ITP] -- Python Natural Language Toolkit
Original Message Subject: Re: Bug#755718: RFS: nltk/3.0.0b1-1 [ITP] -- Python Natural Language Toolkit Date: Sat, 26 Jul 2014 17:31:40 +0200 From: Daniel Stender To: Andreas Tille Hi Andreas, thank you for your offer. That's interesting and I think Nltk would fit perfectly into DebianScience/Linguistics. I'll take care of the SoB requirements then (e.g. transferring to DebianScience VCS), and come back. Greetings, Daniel On 26.07.2014 08:28, Andreas Tille wrote: Hi, On Sat, Jul 26, 2014 at 01:29:04AM +0200, Daniel Stender wrote: The package now builds with the apis while just the examples have been left out - they need the corpus data any, which isn't shipped with the upstream tarball, so this might be a non issue at last. I might consider sponsering the package if you confirm that the package fits into the Debian Science task linguistics[1]. In this case I'd recommend you follow the adwise given at the Sponsering of Blends Wiki page[2]. Kind regards Andreas. [1] http://blends.debian.org/science/tasks/linguistics [2] https://wiki.debian.org/DebianPureBlends/SoB -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d3cafb.5000...@danielstender.com
Bug#755718: RFS: nltk/3.0.0b1-1 [ITP] -- Python Natural Language Toolkit
The package now builds with the apis while just the examples have been left out - they need the corpus data any, which isn't shipped with the upstream tarball, so this might be a non issue at last. Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d2e840.4060...@danielstender.com
Re: Python package documentation with Sphinx: encoding related build failure
I'm afraid the problem lies somewhat deeper, ~$ export LC_ALL=C.UTF-8 ~$ locale | grep LC_ALL LC_ALL=C.UTF-8 ~$ python Python 2.7.8 (default, Jul 4 2014, 13:08:34) [GCC 4.9.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.getdefaultencoding() 'ascii' >>> Cf. http://blog.webforefront.com/archives/2011/02/python_ascii_co.html Greetings, Daniel On 24.07.2014 22:45, Daniel Stender wrote: Thanks guys for the hints. Yes indeed, I've checked the Sid within Cowbuilder and the environment is set to "C". But here, several attempts to change the build LC_LANG failed so far being effective for the Sphinx build, and that error remains. I'll come back when I've got deeper into that issue. Greetings, Daniel -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d2e173.10...@danielstender.com
Bug#755718: RFS: nltk/3.0.0b1-1 [ITP] -- Python Natural Language Toolkit
There is an open issue with the documentation: https://lists.debian.org/debian-mentors/2014/07/msg00349.html Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d19c63.3090...@danielstender.com
Re: Python package documentation with Sphinx: encoding related build failure
Thanks guys for the hints. Yes indeed, I've checked the Sid within Cowbuilder and the environment is set to "C". But here, several attempts to change the build LC_LANG failed so far being effective for the Sphinx build, and that error remains. I'll come back when I've got deeper into that issue. Greetings, Daniel On 24.07.2014 18:06, Etienne Millon wrote: * Barry Warsaw [140724 17:41]: I don't remember the details, but I think there are some build environments where the locale is not set correct (or not set?), which can cause Python's default encodings to kick in and make incorrect assumptions (albeit based on limited available information). I think I've seen this with sbuilds occasionally. The fix is usually to be explicit about the encoding or make sure the locale is set to UTF-8. It'll also work differently depending on whether you're using Python 2 or 3. Sorry I'm a little fuzzy on the details - it's been a while. Hopefully that gives enough of a clue to keep digging in the right place. I had the problem with a build environment which resets LC_ALL to C or unsets it (can't remember if it's at the pbuilder or pybuild level). To print a (unicode) string, python3 needs to know how to encode the string and uses locale for that. In my case the following worked: override_dh_auto_test: LC_ALL=C.UTF-8 dh_auto_test -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d1707a.90...@danielstender.com
Python package documentation with Sphinx: encoding related build failure
Hi, I'm working on packaging a Python package with a Sphinx based documentation, Nltk 3.0.0b1, and there are encoding related build errors. building [html]: targets for 28 source files that are out of date updating environment: 28 added, 0 changed, 0 removed reading sources... [ 3%] api/nltk reading sources... [ 7%] api/nltk.align reading sources... [ 10%] api/nltk.app reading sources... [ 14%] api/nltk.ccg reading sources... [ 17%] api/nltk.chat reading sources... [ 21%] api/nltk.chunk reading sources... [ 25%] api/nltk.classify reading sources... [ 28%] api/nltk.cluster reading sources... [ 32%] api/nltk.corpus reading sources... [ 35%] api/nltk.corpus.reader reading sources... [ 39%] api/nltk.draw reading sources... [ 42%] api/nltk.examples Encoding error: 'ascii' codec can't decode byte 0xf3 in position 386: ordinal not in range(128) The full traceback has been saved in /tmp/sphinx-err-zJoCwN.log, if you want to report the issue to the developers. *** Introductory Examples for the NLTK Book *** Loading ptext1, ... and psent1, ... Type the name of the text or sentence to view it. Type: 'texts()' or 'sents()' to list the materials. Makefile:21: recipe for target 'web' failed Strangely, this only occurs when trying to build against Sid (via Cowbuilder), building with debuild withing Testing works fine. The package is: http://mentors.debian.net/debian/pool/main/n/nltk/nltk_3.0.0b1-1.dsc (switched to build "$(MAKE) without_api" in deb/rules so far to prevent FBFS, "$(MAKE) web" reproduces this error. BTW, the package is RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755718 Thanks in advance for any hint, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53d0c3f3.7070...@danielstender.com
Bug#754202: Gamera/3.4.1-1
Here, everything's ready to push the updated dependency immediately after wxpython3.0 hits Sid, also for a 3.4.1-2. Greetings, Daniel On 23.07.2014 03:53, Dmitry Smirnov wrote: On Tue, 15 Jul 2014 19:21:35 Jakub Wilk wrote: As the bug says, there is no wxPython 3.0 in Debian yet... True, but the following bug was just filed: transition: wxpython3.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755757 -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53cf7d77.8050...@danielstender.com
Bug#755718: RFS: nltk/3.0.0b1-1 [ITP] -- Python Natural Language Toolkit
Package: sponsorship-requests Severity: wishlist Hi, I'm searching for an sponsor of my initial package of Nltk 3.0: http://www.nltk.org/ This is a major library for Natural language processing, but although the WNPP-Bug really is from 2004, it haven't made it into Debian so far: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=279422 The source package builds also a binary package for Python 3, and appears to be Lintian (-F) clean. I'm not sure about the Copyright info "License: eGenix.com Public License" deriving out of the Ubuntu package (still 2.0) on which there remains a complaint by cme check dpkg-copyright. Anyway, the debian patch is stored here: http://anonscm.debian.org/viewvc/python-modules/packages/nltk/ Mentors upload: http://mentors.debian.net/package/nltk http://mentors.debian.net/debian/pool/main/n/nltk/nltk_3.0.0b1-1.dsc Buildlog (build with Cowbuilder against Sid): http://www.danielstender.com/buildlogs/nltk_3.0.0b1-1_amd64.build Thank you very much for considering, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53cea910.3010...@danielstender.com
Bug#755410: RFS: python-xmp-toolkit/2.0.1-1 [ITA] -- Python library for XMP
Package: sponsorship-requests Severity: normal Hi, I'm looking for a sponsor of my package of the Python-xmp-toolkit: https://packages.qa.debian.org/p/python-xmp-toolkit.html The Debian patch is community maintained: http://anonscm.debian.org/viewvc/python-modules/packages/python-xmp-toolkit/trunk/ Plus, I've uploaded the my package to mentors: http://mentors.debian.net/package/python-xmp-toolkit http://mentors.debian.net/debian/pool/main/p/python-xmp-toolkit/python-xmp-toolkit_2.0.1-1.dsc My buildlog: http://www.danielstender.com/buildlogs/python-xmp-toolkit_2.0.1-1_amd64.build Changelog: * New upstream release: updated hardcode-library-name.diff, removed fix-deprecated-unittest-methods.diff (applied upstream). * Changed to build with setuptools: + Removed patches/no-setuptools.diff, added b-ds on python(3)-setuptools. * deb/control: + Change of maintainer (Closes: #708545). + Bumped debhelper level to 9 (also in debian/compat). + B-ds: dropped python-support, added python3-all, python(3)-mock, python(3)-tz (needed by test suite), and dh-python. + Bumped standards to 3.9.5 (no changes needed). + Changed Homepage URL (Google Code became obsolete). + Added X-Python(3)-Versions. + Added description for Python3 bindings package. * deb/copyright: + Updated Format URI [Jakub Wilk]. + Straightened, removed trailing commas, updated. * deb/rules: + Added DH_VERBOSE, DEB_BUILD_OPTIONS and PYBUILD_NAME export lines. + Reduced to build with dh sequencer. * deb/watch: changed from Google Code (obsolete) to Pypi. * Upstream ships with Sphinx documentation: + Removed deb/get-orig.source.sh (not needed anymore to create dfsg). + deb/control: added b-d for python-sphinx. + deb/rules: overrides for building docs and removal of docs/_build. + deb/rules: generation of symbolic links for jquery.js and underscore.js. + Added deb/python(3)-libxmp.docs and deb/python(3)-libxmp.doc-base. * deb/source: added extend-diff-ignore for \.egg-info. * Wrapped and sorted. Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53cbc2e2.5010...@danielstender.com
Bug#755254: RFS: pybtex/0.18-1 -- BibTeX-compatible bibliography processor (update)
Package: sponsorship-requests Severity: normal Hello, I'm looking for an sponsor of my new package of Pybtex. For changes, please cf. http://anonscm.debian.org/viewvc/python-apps/packages/pybtex/trunk/ or checkout: svn://anonscm.debian.org/python-apps/packages/pybtex/trunk/ Mentors upload: http://mentors.debian.net/package/pybtex package: http://mentors.debian.net/debian/pool/main/p/pybtex/pybtex_0.18-1.dsc Buildlog: http://www.danielstender.com/buildlogs/pybtex_0.18-1_amd64.build Changelog: * New upstream release. * deb/changelog: fixed typo (fixes lintian complaint on experimental-to-unstable-w/o-comment). * deb/control: + Updated maintainer email address. + Bumped standards to 3.9.5 (no changes needed). + Use canonical URIs for Vcs-* fields [Jakub Wilk]. + Added python-pkg-resources to Depends (Closes: #684699). + Removed Conflicts (obsolete). * deb/copyright: changed Format line for DEP-5, updated. * deb/rules: + Added export lines for DH_VERBOSE and DEB_BUILD_OPTIONS. + Removed build targets in favour of simplified dh sequencer call. * Changed to build with dh_python2: + deb/control: removed b-d on python-support, bumped version of python-all to 2.6.6-3~. + deb/rules: rearragned, added python2 to dh sequencer. * Upstream now ships with changelog: + deb/clean: removed doc/changelog. + deb/control: removed b-p on elinks. + deb/rules: dropped override for dh_installchangelogs. * Removed lintian-overrides (obsolete). Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ca2e45.4090...@danielstender.com
Bug#754202: Gamera/3.4.1-1
On 14.07.2014 08:21, Dmitry Smirnov wrote: All right, Although debian/copyright is almost comprehensive it still misses some organisations, notably "2007 INRIA" (AKA Dolphin?), "2006 LIFL" (AKA OPAC?). Worth to clarify. Besides copyright file feels not very human-readable and therefore it is hard to review. I understand the effort that will be necessary but I still hope that eventually (when convenient) the following improvements can be made: * Sorting (please alphabetise copyright holders) * Padding with spaces (to make lists appears more like tables i.e. add spaces between copyright year and name if necessary to make all names begin from the same column). This will increase readability. * Ideally it will be nice to have contact emails listed as well. Many of them can be harvested from source files. * I prefer to be more precise regarding years of copyright so I would remove trailing commas after copyright years. When year of copyright written like "2007," it may create wrong impression that person is still actively contributing which is not true on many occasions. I believe it is better to write "2007-2011" and never use ambiguous trailing commas. I've improved the copyright file throughout, sorted, padded, removed trailing commas, enriched. I've noticed that package is not using dh_python2. I do not have enough experience with Python to say whether it is a good or bad thing. I also think that package could use more debhelper functionality. This is not a problem but I'd prefer someone (other than me) who have more Python experience to review and upload. Hopefully someone from Python team could help? In addition to the exchange of python_support with dh_python2 I've now changed also "XS-Python-Version" to "X-Python-Version" in deb/control. Gamera_gui exposes its modules globally which may be unnecessary. I understand that according to Python policy it is desirable to install application's modules privately. In that sense "python-gamera" obviously should be exposed in global name space but "gamera-gui" may be better to hide its modules. I've build with the gamera-gui modules in /usr/share/gamera-gui/ but there a deeper module import problems. I don't know if that could be solved w/o getting dirty, but I'll keep to that issue. `cme check dpkg-control` (from "libconfig-model-dpkg-perl") reported unnecessary versioned dependencies. This is the opportunity to clean "debian/control". Yes, right. I've checked against cme check dpkg-control and removed the needless b-ds. Finally my biggest concern is new dependency on wxwidgets2.8. There is on-going transition to wxwidgets3.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748169 So if I understand situation properly your package will be blocking this transition (if uploaded as is) and therefore it will be affected by yet-to-be- filed "serious" bug. IMHO it will be ideal to migrate to wxwidgets3.0 before upload. If wxpython3.0 becomes available when this bug is still open changes on that could be pushed quickly. Otherwise I'm going to prepare another package immediately after it is available. Greetings, Daniel -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c908d2.5030...@danielstender.com
Bug#754202: Gamera/3.4.1-1
Thanks Dmitry for the close review and the valuable hints for further improvements. I'll get through it, luckily there is still some time until the package really gets AUTORM. Greetings, Daniel On 14.07.2014 08:21, Dmitry Smirnov wrote: Hi Daniel, I'm not sure if I have enough time to familiarise myself with the package to sponsor it but I had a quick look so here is my feedback and improvement ideas: Although debian/copyright is almost comprehensive it still misses some organisations, notably "2007 INRIA" (AKA Dolphin?), "2006 LIFL" (AKA OPAC?). Worth to clarify. Besides copyright file feels not very human-readable and therefore it is hard to review. I understand the effort that will be necessary but I still hope that eventually (when convenient) the following improvements can be made: * Sorting (please alphabetise copyright holders) * Padding with spaces (to make lists appears more like tables i.e. add spaces between copyright year and name if necessary to make all names begin from the same column). This will increase readability. * Ideally it will be nice to have contact emails listed as well. Many of them can be harvested from source files. * I prefer to be more precise regarding years of copyright so I would remove trailing commas after copyright years. When year of copyright written like "2007," it may create wrong impression that person is still actively contributing which is not true on many occasions. I believe it is better to write "2007-2011" and never use ambiguous trailing commas. I've noticed that package is not using dh_python2. I do not have enough experience with Python to say whether it is a good or bad thing. I also think that package could use more debhelper functionality. This is not a problem but I'd prefer someone (other than me) who have more Python experience to review and upload. Hopefully someone from Python team could help? Gamera_gui exposes its modules globally which may be unnecessary. I understand that according to Python policy it is desirable to install application's modules privately. In that sense "python-gamera" obviously should be exposed in global name space but "gamera-gui" may be better to hide its modules. `cme check dpkg-control` (from "libconfig-model-dpkg-perl") reported unnecessary versioned dependencies. This is the opportunity to clean "debian/control". Finally my biggest concern is new dependency on wxwidgets2.8. There is on-going transition to wxwidgets3.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748169 So if I understand situation properly your package will be blocking this transition (if uploaded as is) and therefore it will be affected by yet-to-be- filed "serious" bug. IMHO it will be ideal to migrate to wxwidgets3.0 before upload. -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53c37c9b.1020...@danielstender.com
Bug#754202: RFS: gamera/3.4.1-1 [RC, ITA] -- document analysis framework
In the meanwhile, I've added another patch to fix #737324 (CVE-2014-1937). Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53bc87c9.5070...@danielstender.com
Bug#754202: RFS: gamera/3.4.1-1 [RC, ITA] -- document analysis framework
Package: sponsorship-requests Severity: important Hello, I'm seeking for a sponsor for my package of Gamera: https://packages.qa.debian.org/g/gamera.html The Debian patch is community maintained: http://anonscm.debian.org/viewvc/python-modules/packages/gamera/trunk/ svn://svn.debian.org/python-modules/packages/gamera/trunk I've putted the package up onto Mentors: http://mentors.debian.net/package/gamera http://mentors.debian.net/debian/pool/main/g/gamera/gamera_3.4.1-1.dsc Build log: http://www.danielstender.com/buildlogs/gamera_3.4.1-1_amd64.build The package includes a new upstream release, closes a couple of bugs, and prohibits the imminent AUTORM of itself and several dependencies in a couple of days because of the spurious libtiff4-dev b-p of the orphaned predecessor (cf. #736004). Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53bc1ef8.8030...@danielstender.com
Bug#754043: RFS: dictdlib/2.0.4.2-1 [ITA] -- python-dictdlib - Python library for dictd dictionaries
Package: sponsorship-requests
Severity: normal
Hello,
I'm looking for a sponsor of my package of python-dictdlib
https://packages.qa.debian.org/d/dictdlib.html
The package appears to be Lintian clean. I've uploaded it to mentors:
http://mentors.debian.net/package/dictdlib
http://mentors.debian.net/debian/pool/main/d/dictdlib/dictdlib_2.0.4.2-1.dsc
Buildlog:
http://www.danielstender.com/buildlogs/dictdlib_2.0.4.2-1_amd64.build
Changelog:
* New upstream tarball w/o debian/*.
* deb/control:
+ Changed Section from interpreters to python.
+ Change of maintainer.
+ Bumped Debhelper level to 8 (also im deb/compat).
+ Changed b-p of python-all-dev to python-all.
+ Bumped Standards to 3.9.5.
+ Added Homepage.
+ Added ${misc:Depends} to Depends.
* deb/copyright: Updated and changed throughout.
* deb/rules:
+ Added build-arch and -indep build targets.
+ Added removal of egg-info (version backlog in setup.py).
+ Package changelog now handled by dh_installchangelogs (deleted
from deb/docs).
+ Removed unnecessary comments and dh helpers.
* Added watch file, doc-base, sources/format.
* Removed deb/examples (not included).
On the ITA w/o RFA bug: I've been in contact with John Goerzen on this.
Greetings,
Daniel Stender
--
http://www.danielstender.com/blog/
PGP key: 2048R/E41BD2D0
C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53b9d1a0.3060...@danielstender.com
Bug#753824: RFS: greekocr4gamera/1.0.1-5 [ITA] -- (DPMT) python-gamera.toolkits.greekocr - toolkit for building OCR systems for polytonal Greek
Package: sponsorship-requests Severity: normal Hi people, I'm looking for a sponsor of my new package of the OCR toolkit for Classical Greek for Gamera. It appears to be Lintian clean. For the my changes, please cf. http://anonscm.debian.org/viewvc/python-modules/packages/greekocr4gamera/trunk/ Mentors upload of the package: http://mentors.debian.net/package/greekocr4gamera Buildlog: http://www.danielstender.com/buildlogs/greekocr4gamera_1.0.1-5_amd64.build greekocr4gamera (1.0.1-5) UNRELEASED; urgency=low * deb/control: + New maintainer (Closes: #644570). + Bumped version of b-p on python-all to 2.6.6-3~. + Dropped b-d on python-support. + Bumped standards to 3.9.5 (no changes needed). + Use canonical URIs for Vcs-* fields [Jakub Wilk]. + Added X-Python-Version. + Rearranged, wrapped and sorted. * deb/copyright: + Added email address for Upstream-Contact. + Added myself to Copyright owners of deb/*. * deb/rules: + Added export line for DH_VERBOSE. + Reduced to build with dh sequencer. * Removal of generated manpage(s) moved to deb/clean. This package is closely related to ocr4gamera (python-gamera.toolkits.ocr), which is also on RFS, please cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753731 An update Gamera itself is coming up quickly. Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b80524.6080...@danielstender.com
Bug#753731: RFS: ocr4gamera/1.1.0-1 -- (DPMT) python-gamera.toolkits.ocr - toolkit for building OCR systems
Package: sponsorship-requests Severity: normal Hi, I'm looking for a sponsor of my new package of the OCR toolkit for Gamera. It appears to be Lintian clean. For changes, please cf. http://anonscm.debian.org/viewvc/python-modules/packages/ocr4gamera/trunk/ Mentors upload: http://mentors.debian.net/package/ocr4gamera Buildlog: http://www.danielstender.com/buildlogs/ocr4gamera_1.1.0-1_amd64.build Changelog: ocr4gamera (1.1.0-1) UNRELEASED; urgency=low * New upstream release. + Removed doc-fix-hyperlink-target.diff, doc-plugin-import.diff, and no-wx-import.diff. * deb/control: + New maintainer (Closes: #629179). + Dropped b-d on python-support. + Added versioning to b-d on python-all-dev. + Bumped standards to 3.9.5 (no changes needed). + Use canonical URIs for Vcs-* fields [Jakub Wilk]. + Changed XS-Python-Version to X-Python-Version, bumped to 2.5. + Rearranged, wrapped and sorted. * deb/copyright: + Specified Upstream-Contact according to README. + Added new maintainer. + Improved Copyright lines. * deb/rules: + Added export for DH_VERBOSE. + Reduced to build with dh sequencer. * Removal of generated manpage(s) moved to deb/clean. An update of the Gamera package is coming up, next. Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53b6bb2f.2020...@danielstender.com
Bug#752729: RFS: djvusmooth/0.2.14-2 -- (Python-apps) graphical editor for DjVu
Plus, the changelog entry for this package: djvusmooth (0.2.14-2) UNRELEASED; urgency=low * deb/control: + bumped standards to 3.9.5 (no changes needed). + changed maintainer email address. * deb/copyright: + changed maintainer email address. + expanded copyrights to 2014. * deb/watch: added pgpsigurlmangle (also added deb/upstream-signing-key.pgp). -- Daniel Stender Thu, 26 Jun 2014 00:19:40 +0200 Greetings, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ad3b12.5040...@danielstender.com
Bug#752729: RFS: djvusmooth/0.2.14-2 -- (Python-apps) graphical editor for DjVu
Package: sponsorship-requests Severity: normal Hi people, I'm looking for an uploader for my new package of Djvusmooth. There are only minor changes and it appears to be Lintian clean. Mentors upload: http://mentors.debian.net/package/djvusmooth http://mentors.debian.net/debian/pool/main/d/djvusmooth/djvusmooth_0.2.14-2.dsc Svn: http://anonscm.debian.org/viewvc/python-apps/packages/djvusmooth/trunk/ svn://anonscm.debian.org/python-apps/packages/djvusmooth/trunk/ Build log: http://www.danielstender.com/buildlogs/djvusmooth_0.2.14-2_amd64.build Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53ab4f37.4080...@danielstender.com
Bug#752027: RFS: ocrodjvu/0.7.18-1 -- (Python-apps) tool to perform OCR on DjVu documents
Package: sponsorship-requests Severity: normal Hi, I am seeking for an uploader for my new package of the useful Ocrodjvu. It appears to be Lintian clean. For that, please cf: http://anonscm.debian.org/viewvc/python-apps/packages/ocrodjvu/trunk/ svn://anonscm.debian.org/python-apps/packages/ocrodjvu/trunk/ Mentors upload: http://mentors.debian.net/package/ocrodjvu http://mentors.debian.net/debian/pool/main/o/ocrodjvu/ocrodjvu_0.7.18-1.dsc Buildlog: http://www.danielstender.com/buildlogs/ocrodjvu_0.7.18-1_amd64.build Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53a1fa5e.7020...@danielstender.com
Bug#751742: RFS: didjvu/0.2.8-1 -- (Python-apps) DjVu encoder with foreground/background separation
Package: sponsorship-requests Severity: normal Hello, I'm seeking for an uploader resp. reviewer for my update of Didjvu. It appears to be Lintian clean. Please cf: http://anonscm.debian.org/viewvc/python-apps/packages/didjvu/trunk/ svn://anonscm.debian.org/python-apps/packages/didjvu/trunk/ Mentors upload: http://mentors.debian.net/debian/pool/main/d/didjvu/didjvu_0.2.8-1.dsc Build log: http://www.danielstender.com/buildlogs/didjvu_0.2.8-1_amd64.build Thank you very much, Daniel Stender -- http://www.danielstender.com/blog/ PGP key: 2048R/E41BD2D0 C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539eb63d.8030...@danielstender.com
Bug#715142: RFS: ocrodjvu/0.7.16-1 -- tool to perform OCR on DjVu documents
Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for my new package of Ocrodjvu (http://packages.qa.debian.org/o/ocrodjvu.html). The Debian patch is kept within the Python Applications Team, please cf. http://anonscm.debian.org/viewvc/python-apps/packages/ocrodjvu/trunk/ The changelog entry for this package is: ocrodjvu (0.7.16-1) UNRELEASED; urgency=low [ Daniel Stender ] * New upstream release (closes: #671764, LP: #1108387). * Bumped dephelper to 9 (deb/control and deb/compat). * debian/changelog: extended copyrights to 2013. * debian/control: + bumped standards to 3.9.4 (no changes needed). + added html5lib to Recommmends (closes: #672489). + changed X-Python-Version to 2.6. + dropped unnecessary version from python-djvu dep. [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. * Use "python-all (>= 2.7.3-5)" (that is, python-all that have only 2.7 as supported version) as an alternative to python-argparse in Build-Depends (closes: #707806). Thanks to Luca Falavigna for the bug report. -- Daniel Stender Sat, 06 Jul 2013 09:02:20 +02007 I've uploaded my build log here: http://www.danielstender.com/buildlogs/ocrodjvu_0.7.16-1_amd64.build The package is uploaded to mentors: http://mentors.debian.net/package/ocrodjvu http://mentors.debian.net/debian/pool/main/o/ocrodjvu/ocrodjvu_0.7.16-1.dsc Thanks in advance for any pointer & greetings, Daniel Stender -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51d7c7f4.3080...@danielstender.com
Bug#714947: RFS: djvusmooth/0.2.14-1 -- graphical editor for DjVu
Thanks for further close checking! > Sorry but I have to ask you to correct corresponding changelog entry: > > + removed unnecessary deps (python-all, djvulibre-bin, python-djvu). > > Clearly it says that you dropped three packages from depends while you > merely removed obsolete versioning... Could you re-phrase it please? > That's my only concern -- otherwise I'm ready to upload. Yes, that's misleading, I've improved that. > Also latest changes not yet committed to repository, right? I've committed right now and also I've updated the package at Mentors. Greetings, Daniel -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51d6e795.2070...@danielstender.com
Bug#714947: RFS: djvusmooth/0.2.14-1 -- graphical editor for DjVu
Much thanks again for reviewing and pointers! 1) > `cme check dpkg-control` report the following unnecessary versioned > dependencies: > > * python-all (>= 2.6.6-3~) >Debian has squeeze -> 2.6.6-3+squeeze7; wheezy -> 2.7.3-4; jessie -> > 2.7.5-2; sid -> 2.7.5-2; > * djvulibre-bin (>= 3.5.20-5~) >Debian has squeeze -> 3.5.23-3; wheezy -> 3.5.25.3-1; jessie -> > 3.5.25.3-3; sid -> 3.5.25.4-1; > * python-djvu (>= 0.1.15) >Debian has squeeze -> 0.1.18-2; wheezy -> 0.3.9-1; jessie -> 0.3.9-1; sid > -> 0.3.9-1; sid -> 0.3.9-1+b1; > > This time let's remove them before upload please. Removed the unecessary deps. Great pointer to cme! 2) >> * Bumped Debhelper level to 8 (deb/control and compat). > > Why only to level 8? Current recommended level is 9 and even if you're > backporting to squeeze-backports debhelper 9 is there. > Any particular reason to stay on compat=8? > > I know Arch:all packages benefit little from upgrade from dh-8 to dh-9 > but personally I would upgrade for the sake of staying > up-to-date. IMHO there are less caveats if you maintain all/most of > your packages in same DH compatibility level... Yes, allright. When packaging this, I wasn't sure about if generally at least level 8 would be worth to keep, bumped that. 3) > Another improvement idea might be to use upstream .desktop file from > "extra/". There are few differences from .desktop file in "debian/" > and perhaps they could be merged with patch. Usually it is better to > use upstream files when possible as it help to track changes and share > our improvements as well as reduce duplication. I've removed my own .desktop and added a patch. > Please advise if you want to address any of the above issues before > upload. Thanks. I've updated the package at Mentors. Greetings, Daniel -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51d6a7d0.10...@danielstender.com
Bug#714947: RFS: djvusmooth/0.2.14-1 -- graphical editor for DjVu
Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for my new package of Djvusmooth (http://packages.qa.debian.org/d/djvusmooth.html). The Debian patch is kept within the Python Application Team, please cf. http://anonscm.debian.org/viewvc/python-apps/packages/djvusmooth/trunk The changelog entry for this package is: djvusmooth (0.2.14-1) unstable; urgency=low [ Daniel Stender ] * New upstream release. * Bumped Debhelper level to 8 (deb/control and compat). * deb/control: + bumped standards to 3.9.4 (no changes needed). + bumped X-Python-Version to 2.6 (according to Depends). * deb/copyright: + extended copyrights to 2013. * deb/docs: + added doc/credits.txt. * Locales are now shipped with the upstream tarball: + deb/rules: removed execution of update-i18n script and dh_auto_clean overrides. + deb/control: removed b-d on gettext. + removed deb/source/options. [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. -- Daniel Stender Thu, 27 Jun 2013 16:43:01 +0200 I've uploaded my build log here: http://www.danielstender.com/buildlogs/djvusmooth_0.2.14-1_amd64.build While the package is stashed at Mentors: https://mentors.debian.net/package/djvusmooth http://mentors.debian.net/debian/pool/main/d/djvusmooth/djvusmooth_0.2.14-1.dsc Thanks in advance for any pointers! Greetings, Daniel Stender -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51d58fe4.2080...@danielstender.com
Bug#714144: RFS: didjvu/0.2.7-1 -- DjVu encoder (python-apps)
Package: sponsorship-requests Severity: normal Dear mentors, I'm looking for a sponsor for my new package of didjvu (http://packages.qa.debian.org/d/didjvu.html), http://pypi.python.org/packages/source/d/didjvu/didjvu-0.2.7.tar.gz The Debian patch is kept within the Python Application Team, please cf. the latest commit: http://anonscm.debian.org/viewvc/python-apps/packages/didjvu/trunk/ Changelog: didjvu (0.2.7-1) UNRELEASED; urgency=low [ Daniel Stender ] * New upstream release (Closes: #683581). * Bumped debhelper level to 9 (deb/control and deb/compat). * Added deb/docs to include doc/credits.txt. * deb/control: + bumped standards to 3.9.4 (no changes needed). + added pyexiv2 to Suggests and b-p. + changed Python dependencies (cf. #707807). * deb/copyright: expanded copyrights to 2013. * deb/rules: + removed override for dh_installchangelogs (not needed). + added execution of tests. [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. -- Daniel Stender Mon, 03 Jun 2013 17:47:57 +0200 Please cf. my build log, here: http://www.danielstender.com/uploads/didjvu_0.2.7-1_amd64.build I've stashed the package at mentors, please cf.: http://mentors.debian.net/package/didjvu http://mentors.debian.net/debian/pool/main/d/didjvu/didjvu_0.2.7-1.dsc Thanks in advance for any pointers! Daniel Stender -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51cab06f.9060...@danielstender.com
Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
On 19.06.2013 22:42, Dmitry Smirnov wrote: > Hi Daniel, > > Thanks for your recent corrections. Just few more left to do and I'll > upload for you. Thanks for additional pointers and the close review - the package is going to be much better than it's Ubuntu precursor. *** control *** > * When I mentioned "unnecessary versioned dependencies" I meant that >versioning is unnecessary and safe to drop. There is no point >writing "cmake (>= 2.8.2+dfsg.1-0+squeeze1)" when just "cmake" is >enough because cmake in oldstable is above minimum requirement. >Same applies to "libqt4-dev". > > * Short package description should start with lowercase letter. Fixed. *** copyright *** 1) > * Upstream uses two emails in source files: > > Joseph Artsimovich > Joseph Artsimovich > >The latter statement appears to be older (it is often accompanied >by years 2007-2008 and one would hardly use this horrible russian >email service while having account at gmail). > >I would at least mention first statement (i.e. contact email) in >Upstream-Contact or even include both statement to copyright >paragraph as it would be speculative to decide which statement is >more important/valid. I've been in contact with Joseph over a couple of weeks ago. I've just changed that throughout, also in the manpages. 2) > * The following copyright holders are not listed in debian/copyright: > > Vadim Kuznetsov ()DikBSD > 2011 Petr Kovar I've added individual paragraphs for these files. 3) > * "Based on code from the GIMP project" is not a copyright statement >so perhaps it's better to move it to Comment section. Then it would >become obvious that word "Copyright" is used twice in the >paragraph. Yes, I've moved the "based on" info of this files to Comments. 4) > * At least one file in "packaging/osx" is under BOOST license. Also >file "ScanTailor.icns" is a (sourceless?) binary file... I've added a licence paragraph for packaging/osx/user-config.jam 5) > * "License: PD" perhaps is better written as > "License: public-domain". >For files in Public-Domain copyright is not applicable so it is >better to write "Copyright: not-applicable" but mention origin of >files (i.e. Tango project and URL) in Comment field. Changed that. 6) > * One of the man pages is written by "Artem Popov " >but that's not how his name is written in debian/copyright. It is >always safer to use original statement as written by author without >unnecessary translation of person's name to native characters even >if it is done correctly. Yes, all right, changed that. *** misc *** 1) > * Generated man page is not removed on clean. Added debian/clean for that purpose. 2) > Probably you don't need this reminder but when convenient please > forward patch and man pages to upstream. Yes, all right, I'm going to do that. Everything has been pushed to the Git repo. Greetings, Daniel -- http://www.danielstender.com/blog/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c86e2b.90...@danielstender.com
