Bug#898688: RFS: deepin-image-viewer/1.2.19-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "deepin-image-viewer" * Package name: deepin-image-viewer Version : 1.2.20-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/deepin-image-viewer * License : GPL-3+ Section : graphics It builds those binary packages: deepin-image-viewer - Image Viewer for Deepin Desktop Environment To access further information about this package, please visit the following URL: https://mentors.debian.net/package/deepin-image-viewer Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/deepin-image-viewer/deepin-image-viewer_1.2.20-1.dsc More information about hello can be obtained from https://salsa.debian.org/pkg-deepin-team/deepin-image-viewer Changes since the last upload: * New upstream release. * d/control: change maintainer field back to pkg-deepin-de...@lists.alioth.debian.org -- Yanhao Mo signature.asc Description: PGP signature
Bug#895812: RFS: json-editor.js/0.7.28+ds-1 [ITP]
Hi Paolo, Thanks for taking the time to review my package. Just to let you know, I am working on the things you mentioned, but have hit a roadblock when it comes to actually joining the js-team. > 3. If you wish to maintain this package within this team, I'd suggest that > you join the team ! >Just drop a mail to the mailing list committing to follow the team > policies, and indicate your salsa alias. >One of the js-team group owners can then add you to the group on salsa. So, I actually sent an email to pkg-javascript-de...@lists.alioth.debian.org some time ago, asking to join the team, but my email got stuck in moderation and as far as I am aware never actually made it to the list. Is there something you can do or recommend I do about this?
Bug#895812: RFS: json-editor.js/0.7.28+ds-1 [ITP]
Dear reviewers, I have uploaded a new version of json-editor.js, which addresses many of Paolo's concerns. It can be downloaded from https://mentors.debian.net/package/json-editor.js, and the git repository is available at https://salsa.debian.org/joelcross-guest/json-editor.js. - Joel Cross
Re: Salsa repository request (gpp)
On Mon, May 14, 2018 at 10:16:42PM -0400, Sergio Durigan Junior wrote: > Hey Fabian, > > Can you add yourself on d/copyright, under the entry for the "debian/*" > files? After all, you deserve the credit as well ;-). > > Other than that, it's ready for upload. Let me know when you make the > change, and I'll upload it. I have added myself in debian/copyright and reuploaded the package to Mentors: https://mentors.debian.net/package/gpp Thanks for sponsoring the upload! Best regards, Fabian
Re: Salsa repository request (gpp)
On Tuesday, May 15 2018, Fabian Wolff wrote: > On Mon, May 14, 2018 at 10:16:42PM -0400, Sergio Durigan Junior wrote: >> Hey Fabian, >> >> Can you add yourself on d/copyright, under the entry for the "debian/*" >> files? After all, you deserve the credit as well ;-). >> >> Other than that, it's ready for upload. Let me know when you make the >> change, and I'll upload it. > > I have added myself in debian/copyright and reuploaded the package to > Mentors: > > https://mentors.debian.net/package/gpp > > Thanks for sponsoring the upload! Thank you. I've uploaded it now. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Bug#895940: RFS: python-dataclasses/0.5-1 [ITP]
On Monday, May 14 2018, Joel Cross wrote: > On Mon, 30 Apr 2018, at 6:21 PM, Joel Cross wrote: >> > Ah! Found it. It's listed in the "setup.py" file. Hmm... I wonder if >> > that's a problem, because no other file contains any kind of copyright >> > notice, and there's no LICENSE file. I'd definitely file a bug against >> > upstream asking them to clarify this, but I honestly don't know if >> > ftp-master will accept the package as is. Maybe there's some >> > precedence, but I'm short on time right now and can't really dive into >> > the archives to find something. Perhaps someone more knowledgeable can >> > chime in? >> >> Hi Sergio, >> >> As an update to this, I filed a bug report upstream. The author >> originally planned to license as Apache2 but neglected to add the >> license to the repo (I guess 'MIT' was some default somewhere): see >> discussion at https://github.com/ericvsmith/dataclasses/issues/123 >> >> Anyway, the author has now added the license, but has not yet released a >> new version, as no code has actually changed. I was wondering if you >> could help me with regards to packaging based on a specific upstream Git >> commit rather than a release version, and how that works with the git- >> buildpackage flow (if it's even allowed/recommended). >> > Hi again, > > Did you get the chance to think about the above? I will happily > repackage from the git master, but I'm not sure what to do about > version numbers and stuff (and online informaition about this is hard > to find!). Please can you help? Hey Joel, Sorry about the delay, this one fell through the cracks. So, to be honest, I'm not 100% sure how to proceed in this case. I mean, I probably would talk to upstream again and ask them to cut a release after fixing the licensing issue, because IMHO it's an important fix and justifies a new release. But I understand they may not agree. Packaging from git master would probably involve importing upstream's master branch as another branch on your package's repository, and then generating a tarball from there. Or maybe you could follow: https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html (specifically the "Upstream tarballs and separate upstream history" section). But again, the very first thing I would do is to ask for upstream to cut a (minor?) release containing the license fix. This should be really easy for them to do, and it will really simplify things for you. Please keep me posted and let me know if you need more help. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
Package: sponsorship-requests Severity: normal Dear Maintainer, I'm on my way to become the maintainer of a couple of packages for the management of botanic collections, namely bauble and ghini.desktop. both of them rely upon fibra, and fibra wasn't yet in Debian. so I need fibra in two different packages, and it is also small enough so that it's being a learning example for me of what difficulties to expect when I'll face the larger packages. Fibra itself is a mature product, it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17), after that the upstream developer did not think of renaming the stable version to 1.0.0. It offers collaborative concurrency, and has been helpful in bauble, avoiding us trouble with threading and real concurrency. friendly regards, Mario Frasca -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote: [...] > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17) [...] The dates made me strongly suspect, but skimming the upstream source confirms, this is very much not a Py3K-ready library. Are you becoming de facto upstream for this and planning to update it to support Python 3.x in preparation for 2.7 reaching end of life? -- Jeremy Stanley
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I did not notice the template Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "fibra" * Package name: fibra Version : 0.0.17-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : python It builds those binary packages: python-fibra - Advanced cooperative concurrency using Python generators. python-fibra-doc - Advanced cooperative concurrency using Python generators. python3-fibra - Advanced cooperative concurrency using Python generators. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fibra Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fibra/fibra_0.0.17-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: this is my first upload. Regards, Mario Frasca
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
On 2018-05-15 14:20:15 -0500 (-0500), Mario Frasca wrote: [...] > it was developed between 2008-11 (0.0.6) and 2009-8 (0.0.17) > [...] The dates made me strongly suspect, but skimming the upstream source confirms, this is very much not a Py3K-ready library. Are you becoming de facto upstream for this and planning to update it to support Python 3.x in preparation for 2.7 reaching end of life? -- Jeremy Stanley
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
I don't see any inconvenience with this what you suggest. I can import the library (with, if necessary, its history) into a new github project. I already patched upstream so it can be loaded in python3.
Bug#898773: RFS: python-fibra/0.0.17-1 [ITP 898736]
> planning to update it to > support Python 3.x in preparation for 2.7 reaching end of life? btw, since my two adopted children `bauble` and `ghini` both depend on `fibra`, and python is reaching end of life for them too, I'm afraid I will port `fibra` to python3 anyway, that it is accepted into Debian or not. I'm already reconstructing its history, and will publish it in github as soon as I'm done. M
Bug#898430: marked as done (RFS: gnustep-base/1.25.1-3 [RC])
Your message dated Tue, 15 May 2018 22:21:56 + with message-id and subject line closing RFS: gnustep-base/1.25.1-3 [RC] has caused the Debian Bug report #898430, regarding RFS: gnustep-base/1.25.1-3 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 898430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "gnustep-base". * Package name: gnustep-base Version : 1.25.1-3 Upstream Author : Richard Frith-Macdonald , Adam Fedor and many others * URL : http://gnustep.org * License : LGPL-2.1+ (library), GPL-3+ (tools) Section : gnustep It builds these binary packages: gnustep-base-common - GNUstep Base library - common files gnustep-base-doc - Documentation for the GNUstep Base Library gnustep-base-runtime - GNUstep Base library - daemons and tools libgnustep-base-dev - GNUstep Base header files and development libraries libgnustep-base1.25 - GNUstep Base library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gnustep-base Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gnustep-base/gnustep-base_1.25.1-3.dsc Git repository: https://salsa.debian.org/gnustep-team/gnustep-base Changes since the last upload: * debian/patches/icu-60.patch: Fix FTBFS on big-endian architectures (really closes: #888908). * debian/templates/control.m4 (Standards-Version): Bump to 4.1.4; no changes required. * debian/control: Regenerate. --- End Message --- --- Begin Message --- Package gnustep-base version 1.25.1-3 is in unstable now. https://packages.qa.debian.org/gnustep-base--- End Message ---
RFS: pygithub/1.40a3-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pygithub" * Package name: pygithub Version : 1.40a3-1 Upstream Author : Author : Adam Dangoor Vincent Jacques < vinc...@vincent-jacques.net> Jeremy Phelps < jphe...@linuxfoundation.org> * URL : https://pypi.python.org/pypi/PyGithub * License : LGPL-3+ Section : python It builds those binary packages: python-github - Access to full Github API v3 from Python2 python3-github - Access the full Github API v3 from Python3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pygithub or https://salsa.debian.org/python-team/modules/pygithub Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc or git clone g...@salsa.debian.org:python-team/modules/pygithub.git More information about pygithub can be obtained from http://pygithub.readthedocs.io/ Changes since the last upload: * New upstream release * Update Standards-Version from 4.1.3 to 4.1.4 version * Add Uploaders field from debian/control to intent to adopt the package (Closes: #851187) Regards, Emmanuel Arias -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Bug#895812: RFS: json-editor.js/0.7.28+ds-1 [ITP]
I'm currently out of the country for a couple weeks and have no access to a computer or my key. At a cursory glance, I see no issues. When I return, if not uploaded, I'll plan to do so. Thanks for your efforts! On Wed, May 16, 2018, 00:42 Joel Cross wrote: > Dear reviewers, > > I have uploaded a new version of json-editor.js, which addresses many of > Paolo's concerns. It can be downloaded from > https://mentors.debian.net/package/json-editor.js, and the git repository > is available at https://salsa.debian.org/joelcross-guest/json-editor.js. > > - > Joel Cross >
Bug#898688: closing 898688
close 898688 thanks Uploaded with new version. Thanks! -- Regards, Boyuan Yang
