Bug#987187: libcurl3-gnutls from debian backports breaks git http operations
hi, we still have the issue in deb10, i had to revert today to 7.64.0-4+deb10u6 for git operation to work again. Do you think there will be a patch anytime in bpo ? :) have a nice day. -- cordialement, Ghislain ADNET. AQUEOS.
Bug#1023389: RM: simpleitk -- ROM; Has RC bugs but no active maintainer
Le jeu. 3 nov. 2022, 11:33, Andreas Tille a écrit : > Package: ftp.debian.org > Severity: normal > X-Debbugs-Cc: debian-...@lists.debian.org, Ghislain Antony Vaillant < > ghisv...@gmail.com> > > Hi, > > it seems we have to face reality: Due to RC bugs this package has not > migrated to testing for 1373 days and the only current uploader of the > package inside the Debian Med team does not respond to any ping. We > simply have no capacity to care for this package. > > So please remove the package from Debian. > > Kind regards and thanks for your work as ftpmaster > > Andreas. > I second Andreas' assessment. This package should be removed given my lack of time to maintain it anymore. Best regards, Ghis >
Bug#951805: Help with glbinding
If you need sponsorship and access to the repo, feel free to request them to the Debian Science mailing list. Cheers, Ghis Le dim., oct. 2 2022 at 22:04:07 +0200, Andrea Pappacoda a écrit : Il giorno dom 2 ott 2022 alle 20:54:01 +02:00:00, Ghislain Vaillant mailto:ghisv...@gmail.com>> ha scritto: Feel free to assist with maintenance of any of my packages under the Debian science team umbrella. You don't need to ask for permission Thanks for the fast reply, Ghislain! I'll start working on this in a few days. Would you be able to sponsor my first upload and/or grant me DM rights to the package? If you prefer, I can publish my changes in a Salsa fork so that you can take a look at them before trusting me too much :) -- OpenPGP key: 66DE F152 8299 0C21 99EF A801 A8A1 28A8 AB1C EE49
Bug#951805: Help with glbinding
Hi Andrea, Feel free to assist with maintenance of any of my packages under the Debian science team umbrella. You don't need to ask for permission Ghis Le dim. 2 oct. 2022, 18:22, Andrea Pappacoda a écrit : > Hi Ghislain, glbinding hasn't been updated in four years. Would you > like some help with the package? I've used glbinding in the past, and > I'd be happy to help with maintenance under the Science team. > > -- > OpenPGP key: 66DE F152 8299 0C21 99EF A801 A8A1 28A8 AB1C EE49 > > >
Bug#1020518: [debian-mysql] Bug#1020518: Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf
Le 22/09/2022 à 18:37, Robie Basak a écrit : On Thu, Sep 22, 2022 at 05:28:27PM +0100, Robie Basak wrote: Again, note that I'm still speculating here because I don't follow the exact sequence of events which is causing the third party packaging to trip up here. If there's something we're doing wrong then we should fix it, but nothing I've read so far suggests that. Oh, hold on. Is the issue that you've *deleted* /etc/mysql/mariadb.cnf? If so, then yes, /usr/share/mysql-common/configure-symlinks could reasonably not call update-alternatives --install to maintain that "sysadmin choice". It should probably print a warning in this case. Sorry if i am not clear enough. in fact /etc/mysql/mariadb.cnf does not exist as there is a mysql server and not a mariadb one. I have a perconna mysql server running and i want to install mytop that require a perl lib that require libmariad3b, that then, want to replace /etc/mysql/my.cnf with a link to /etc/mysql/mariadb.cnf, but /etc/mysql/mariadb.cnf does not exist while /etc/mysql/my.cnf exist from the percona packages. hope that clarify ? sorry not native english speaker too so... -- cordialement, Ghislain ADNET. AQUEOS.
Bug#1020518: [debian-mysql] Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf
Le 22/09/2022 à 18:12, Robie Basak a écrit : On Thu, Sep 22, 2022 at 05:10:05PM +0200, nobody wrote: * What outcome did you expect instead? installing a client library should not require anything on the server side and should not modify server configuration of mariadb or other mysql flavors (imho ;p) Both MySQL/MariaDB client libraries and MySQL/MariaDB daemons expect and use /etc/mysql/my.cnf, and many common packages supplied by Debian link to a MySQL/MariaDB library. So Debian ends up needing to ship a working /etc/mysql/my.cnf essentially by default. It doesn't matter which side of the fork is in use - it's necessary either way. Maybe upstream could separate the two out, but they don't. thanks for your quick answer So perhaps we could see it another way : in this particular case i think that a client library, if it find an existing /etc/mysql/my.cnf, should not do anything as it is there adn so everything it need is okay. There is no need for a client library to change this part if it is here if it only need one to exist. Perhaps just adding a check if [[ ! -e /etc/mysql/my.cnf ]]; then do touch server configuration in /etc/mysql/my.cnf fi -- cordialement, Ghislain ADNET.
Bug#995829: ITP: itk5 -- extensive suite of software tools for image analysis
Package: wnpp Severity: wishlist Owner: Ghislain Vaillant X-Debbugs-Cc: debian-de...@lists.debian.org, debian-...@lists.debian.org * Package name: itk5 Version : 5.2.1 Upstream Author : NumFOCUS * URL : https://itk.org * License : Apache-2.0 Programming Lang: C++, Python Description : extensive suite of software tools for image analysis This package is a core dependency for a large array of medical packages. This package will be maintained by the Debian Med Packaging Team.
Bug#976622: ITP: python3-oscrypto -- cryptography library for Python
Use python-oscrypto (as in Python the language) or just oscrypto for the source package name. Use python3-oscrypto for the name of the binary package installing the module for Python 3. Le dim. 6 déc. 2020 à 01:18, Joseph Nahmias a écrit : > Package: wnpp > Severity: wishlist > > * Package name: python3-oscrypto > Version : 1.2.1 > Upstream Author : Will Bond > * URL : https://github.com/wbond/oscrypto > * License : MIT > Programming Lang: Python > Description : cryptography library for Python > > TLS (SSL) sockets, key generation, encryption, decryption, signing, > verification and KDFs using the OS crypto libraries. Does not require a > compiler, and relies on the OS for patching. Works on Windows, OS X and > Linux/BSD. > > I plan to maintain this under the Debian Python Team. > > Used by a number of cross-platform projects including for verifying > LineageOS > builds. > >
Bug#949622: proftpd on buster
hi, I think this is an important package to get updated in stable, or via the volatile updates repo. The one that is in stable now only works on very few clients. Hopefully the release managers agree. yes, this is not a security fix but a package that cannot be used at all is not very usefull. So i think this should be pushed in the repo for users to be able to stay in debian. Thansk for all the works of all of you ! regards, Ghislain.
Bug#949622: SSH authentication fails for many clients due to receiving of SSH_MSG_IGNORE packet
hi, As tests has been done successfully for package, and patch from proftpd for 1.3.6 and 1.3.5 have been given by upstream i wanted to know if this has been pushed to production ? :) because on my test 80% of mac/windows client seems are unable to connect to proftpd rigth now on debian 8,9 (not tested 10). regards, Ghislain.
Bug#949622: patch for 1.3.5
Hi, Tj was kind enough to make a patch for the 1.3.5 unsupported branch ! = This is for: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949622 See attached patch, generated against the 1.3.5 branch of ProFTPD in GitHub. Hope this helps, TJ proftpd-1.3.5-sftp-kbdint-packets-bug4385.patch Description: Binary data
Bug#949622: proftpd-basic: SSH authentication fails for many clients due to receiving of SSH_MSG_IGNORE packet
hi, the problem still exist for debian 9 and debian 8, is it possible to backport the patch for those versions ? regards, Ghislain.
Bug#940680: Provide backports for Buster
On Mon, 30 Sep 2019 19:42:39 +0200 Ghislain Vaillant < ghisv...@gmail.com> wrote: > On Mon, 23 Sep 2019 10:44:08 +0100 Simon McVittie > wrote: > > On Thu, 19 Sep 2019 at 00:17:00 +0200, ghisv...@gmail.com wrote: > > > Since the release of freedesktop runtime version 19.08, flatpak > attempts > > > to install org.freedesktop.Platform.openh264 but fails with the > > > following warning message: > > > > > > Warning: org.freedesktop.Platform.openh264 needs a later flatpak > version > > > > This will be addressed by flatpak 1.2.5 in the next buster > > point release (see #940818). It should become available soon via > > buster-proposed-updates, if you want to test it early. > > I'd be happy to. I have enabled buster-pu and await said update. The update landed today on my machine. The issue with upgrading org.freedesktop.Platform.openh264 is indeed resolved. Cheers, Ghis
Bug#940680: Provide backports for Buster
On Mon, 23 Sep 2019 10:44:08 +0100 Simon McVittie wrote: > On Thu, 19 Sep 2019 at 00:17:00 +0200, ghisv...@gmail.com wrote: > > Since the release of freedesktop runtime version 19.08, flatpak attempts > > to install org.freedesktop.Platform.openh264 but fails with the > > following warning message: > > > > Warning: org.freedesktop.Platform.openh264 needs a later flatpak version > > This will be addressed by flatpak 1.2.5 in the next buster > point release (see #940818). It should become available soon via > buster-proposed-updates, if you want to test it early. I'd be happy to. I have enabled buster-pu and await said update. > > Would you consider providing backports of newer releases of flatpak to > > Buster to bypass future issues with new runtimes? > > I'll probably do a backport eventually, but ideally using backports > shouldn't be necessary in order to use Flathub, so fixing stable is a > higher priority for me right now than maintaining backports. Agreed. As a flatpak maintainer myself, I have not felt the need to upgrade to a newer release even for development purposes. Cheers, Ghis
Bug#926719: Info received (Bug#926719: SFTP ProFTPD terminating (signal 11) after Update to 1.3.5e-0+deb8u1)
hi, We are still using the old package not protected from the vulnerability, any idea when sftp on jessie will work again ? Is there anything i can do to help it ? regards, Ghislain.
Bug#926935: arpack: FTBFS (does not honor parallel=n in DEB_BUILD_OPTIONS)
Le mer. 24 avr. 2019 à 17:02, Santiago Vila a écrit : > On Wed, Apr 24, 2019 at 04:47:16PM +0200, Sylvestre Ledru wrote: > > Le 24/04/2019 à 16:45, Santiago Vila a écrit : > > > On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote: > > > > Anyone objecting on applying Santiago's patch to src:arpack to fix > the > > > > occasionnal FTBFS on single-core builders? > > > > > > > > If not, then I am happy to prepare a release. > > > > > > Thanks a lot. > > > > > > One minor clarification: The failure happens always on single-cpu > systems, > > > not just occassionally. > > > > > Don't hesitate to forward that upstream if you find a fix > > https://github.com/opencollab/arpack-ng > > A general fix (i.e. one that upstream accept) would probably involve > using "nproc" command inside the Makefiles, but then we would have to > override that anyway to avoid using so many simultaneous jobs if the > user explicitly ask for less jobs via DEB_BUILD_OPTIONS. > > The safe/conservative thing to do would be to use 1 job for the test suite. > > I can put an issue in github if you confirm there is not one yet. > > Thanks. > I did not find one, but glanced very quickly through the issue tracker. >
Bug#926719: SFTP ProFTPD terminating (signal 11) after Update to 1.3.5e-0+deb8u1
Could you send me your sftp configuration snippet for proftpd and tell me more about your setup? How can you connect via command-line sftp but not via filezilla? i use the unmodified package with this sftp configuration SFTPEngine on AllowOverwrite on RequireValidShell off # Configure the server to listen on the normal SSH2 port, port 22 Port 2221 SFTPHostKey /etc/ssh/ssh_host_rsa_key SFTPHostKey /etc/ssh/ssh_host_dsa_key SFTPAuthorizedUserKeys file:~/.sftp/authorized_keys SFTPCompression delayed MaxLoginAttempts 6 DefaultRoot ~ Umask 0026 0027 as i said numerous customer reported issues connecting in sftp following the upgrade. We had to rollback and everything worked again. Client used where :filezilla and dreamweaver, both up to date. my command line client ( command SFTP) on ubuntu 18.04 was able to connect but not fillezilla. After rollback to previous version both client worked. The new version On debian 9 it works, but on debian 8 it fails. Ghis.
Bug#926719: dreamweaver sftp also
dreamweaver sftp client (v19.1) is also not working since the upgrade. regards, ghislain.
Bug#926719: same problem here with filezilla but not with sftp command line
] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): in dir_check_full(): path = '/', fullpath = '/usr/local/.admin/home/admin/'. 2019-04-10 10:02:59,870 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): in dir_check_full(): setting umask to 0027 (was 0022) 2019-04-10 10:02:59,870 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): USER admin: Login successful 2019-04-10 10:02:59,871 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): ProFTPD terminating (signal 11) 2019-04-10 10:02:59,871 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): ProFTPD terminating (signal 11) 2019-04-10 10:02:59,871 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): mod_sftp/0.9.9: scrubbing 2 passphrases from memory 2019-04-10 10:02:59,871 .x.com proftpd[23496] 0.0.0.0 (211.ip-51-68-231.eu[51.68.231.211]): SSH2 session closed. ssh session is openned but closed asap by the server. Reported by several people here, using filezilla. It was working yesterday fine. However the sftp command line works: sftp -vv -P 2221 ... Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. debug1: Authentication succeeded (keyboard-interactive). Authenticated to xxx ([xx.xx.164.232]:2221). debug2: fd 5 setting O_NONBLOCK debug1: channel 0: new [client-session] debug2: channel 0: send open debug1: Entering interactive session. debug1: pledge: network debug2: channel_input_open_confirmation: channel 0: callback start debug2: fd 3 setting TCP_NODELAY debug2: client_session2_setup: id 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug1: Sending env LC_NUMERIC = C debug2: channel 0: request env confirm 0 debug1: Sending subsystem: sftp debug2: channel 0: request subsystem confirm 1 debug2: channel_input_open_confirmation: channel 0: callback done debug2: channel 0: open confirm rwindow 4294967295 rmax 32768 debug2: channel_input_status_confirm: type 99 id 0 debug2: subsystem request accepted on channel 0 debug2: Remote version: 3 debug2: Unrecognised server extension "versions" debug2: Server supports extension "fs...@openssh.com" revision 1 debug2: Server supports extension "posix-ren...@openssh.com" revision 1 debug2: Server supports extension "stat...@openssh.com" revision 2 debug2: Server supports extension "fstat...@openssh.com" revision 2 Connected to x. sftp> ls Maildir RPM-GPG-KEY-virtualmin RPM-GPG-KEY-webmin sftp> best regards, Ghislain.
Bug#921460: dead upstream - keep out of testing
Le mar. 5 févr. 2019 à 20:21, Rebecca N. Palmer a écrit : > Package: clsparse > Severity: serious > X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com > (plus an identical one for freefem3d) > > This package is dead upstream, and it has been suggested [0] that > because of this, it should not be fixed for buster. > > I don't know enough about it to have an opinion on this: I am opening > this bug as a "don't waste your time fixing it" notice. > > If this remains the consensus, please consider removing it from unstable > as well. > > [0] https://lists.debian.org/debian-science/2019/02/msg00015.html Agreed. It should be removed. Ghislain > >
Bug#916859: closed by Andrey Rahmatullin (Re: Bug#916859: RFS: PDF Studio Viewer/2018 [ITP] -- pdf viewer)
Le jeu. 20 déc. 2018 à 12:33, Sven Hoexter a écrit : > On Wed, Dec 19, 2018 at 05:12:39PM -0500, Studio Support wrote: > > Hello Andrey, > > > > Regarding the solution on Bug#916859 about our package "pdfstudioviewer" > > > > It's free in the real sense of the term, meaning that users don't pay > for it. But it is not open source. Our end-user license is displayed to > users upon running our application the first time. > > > > We don't care if our application is listed under the Free or the > Commercial products. > > > > We have a Debian installer so I hope you can use that. > > Hi, > I, and propably many more Debian developers, appreciate that you try to > engange > with the Debian project, but really we're focused on open source software. > You might > want to read https://www.debian.org/social_contract.html > > So yes it's true that we have this sad part called "non-free" on our > mirrors but formally > it's not really part of the distribution, and still everything shipped in > non-free requires > to have a source package as well. > https://wiki.debian.org/Packaging/SourcePackage > > In the end I can only encourage you to open source your software, > otherwise you've to move > on and distribute it via your own self hosted repository. > > Sven > Another solution would be to distribute your software via Flatpak or Snap which most distributions, including Debian, support very well. Ghis >
Bug#887747: ITP: gnome-shell-extension-easyscreencast -- video recording extension for the GNOME shell
Le lun. 1 oct. 2018 à 05:42, Samuel Henrique a écrit : > Hello everyone, > > I see that the last email here is from January 21th, so I decided to > myself package gnome-shell-extension-easyscreencast, > You did well. > > It is almost ready at salsa[0], it just need a final review of d/copyright > to check if there were new copyright holders added on the new release. I > did not committed under gnome's team organization, but I can do so if asked > (I didn't because I don't know if this is what the team wants). > If you want the package to be under team maintenance, you should. > > Please let me know if you've made any progress on your package, if you > want to do any changes on top of mine or if you want to co-maintain it. > > If there's no opinions against, I will do the upload soon. > Please go ahead. Thank you for taking care of it. > > Thanks, > > [0]https://salsa.debian.org/debian/gnome-shell-extension-easyscreencast > > -- > Samuel Henrique >
Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]
Le sam. 8 sept. 2018 à 15:05, Mo Zhou a écrit : > control: owner -1 ! > > Hi Ghislain, > > I can sponsor this now. Should wait for you to update the package > to the latest upstream verison, or check and upload it from git > repo as is? > > I think the packaging repo is this one: > https://salsa.debian.org/python-team/modules/python-jsonrpc I'll have a look soon. > > BTW, why don't you submit a DD application at nm.d.o? > Lack of time, mostly. Congrats for yours btw. Ghis >
Bug#904478: Enable support for JPEG 2000
Package: src:pillow Severity: wishlist Dear maintainer, According to the upstream documentation [1], Pillow should have read support for JPEG 2000 via OpenJPEG v2. This format is used quite heavily in medical software (via the DICOM format), so it would be really nice to provide a JPEG2000 enabled version of Pillow for this community. [1] https://pillow.readthedocs.io/en/5.2.x/handbook/image-file-formats.html#jpeg-2000 ``` To enable JPEG 2000 support, you need to build and install the OpenJPEG library, version 2.0.0 or higher, before building the Python Imaging Library. ``` I suppose it should be as straightforward as adding `libopenjp2-7-dev` in Build-depends, and verifying that `setup.py` detects it properly? Best regards, Ghis -- System Information: Debian Release: 9.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#903136: RFP: spyder-kernels -- Jupyter kernels for the Spyder console
Package: wnpp Severity: wishlist * Package name: spyder-kernels Version : 1.0.1 Upstream Author : Spyder Development Team * URL : https://github.com/spyder-ide/spyder-kernels * License : Expat Programming Lang: Python Description : Jupyter kernels for the Spyder console Long-Description: Package that provides the kernels used by Spyder on its IPython console. . Spyder is the Scientific Python Development Environment. Spyder-kernels is a required dependency for spyder>=3.3. I would suggest to co-maintain this package wit the Debian Science Team wherein spyder and its plugins are currently located.
Bug#902553: New version does not build
I am away right now and can't investigate before two weeks. Looks Cython related from a first look. Ghis Le ven. 29 juin 2018 à 11:17, Andreas Tille a écrit : > Hi Ghislain, > > since one of the Debian Med packages seems to be affected I tried to > upgrade h5py (see Git repository). Unfortunately it does not build: > > ... > running build_ext > Traceback (most recent call last): > File "setup.py", line 168, in > cmdclass = CMDCLASS, > File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line > 129, in setup > return distutils.core.setup(**attrs) > File "/usr/lib/python2.7/distutils/core.py", line 151, in setup > dist.run_commands() > File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands > self.run_command(cmd) > File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command > cmd_obj.run() > File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run > self.run_command(cmd_name) > File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command > self.distribution.run_command(command) > File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command > cmd_obj.run() > File "/build/h5py-2.8.0/setup_build.py", line 156, in run > from Cython.Build import cythonize > File "/usr/lib/python2.7/dist-packages/Cython/Build/__init__.py", line > 1, in > from .Dependencies import cythonize > File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", > line 36, in > from ..Compiler.Main import Context, CompilationOptions, > default_options > File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Main.py", line > 30, in > from .Symtab import ModuleScope > File "/usr/lib/python2.7/dist-packages/Cython/Compiler/Symtab.py", line > 19, in > from . import PyrexTypes > File "/usr/lib/python2.7/dist-packages/Cython/Compiler/PyrexTypes.py", > line 17, in > from .Code import UtilityCode, LazyUtilityCode, TempitaUtilityCode > File "Cython/Compiler/Code.py", line 38, in init Cython.Compiler.Code > ImportError: /usr/lib/python2.7/dist-packages/Cython/ > StringIOTree.x86_64-linux-gnu.so: undefined symbol: Py_InitModule4_64 > E: pybuild pybuild:336: build: plugin distutils failed with: exit code=1: > /usr/bin/python-dbg setup.py build > dh_auto_build: pybuild --build -i python{version}-dbg -p 2.7 returned exit > code 13 > make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25 > make[1]: Leaving directory '/build/h5py-2.8.0' > make: *** [debian/rules:10: build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > > Can you please have a look? > > Kind regards > > Andreas. > > -- > http://fam-tille.de >
Bug#897603: New upstream release
Package: thefuck Version: 3.11-2 Severity: wishlist Dear maintainer, Please consider upgrading src:thefuck to the latest upstream version (3.26 at the time of writing). You might also want to take this opportunity to switch the dependencies to Python 3, thereby dropping the need for pathlib2. On a side note, it might be good to transition the package from collab-maint to the new salsa hosting service. Since the application is written in Python, you might be interested to join the Python Application Team to facilitate potential co-maintenance. Thank you for your work on src:thefuck. Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thefuck depends on: ii python2.7.15~rc1-1 ii python-colorama 0.3.7-1 ii python-decorator 4.1.2-1 ii python-pathlib2 2.3.2-1 ii python-psutil 5.4.2-1 ii python-six1.11.0-2 ii python2.7 2.7.15~rc1-1 thefuck recommends no packages. thefuck suggests no packages. -- no debconf information
Bug#894811: New upstream release
Package: src:python-pbr Severity: wishlist Dear maintainer, Please consider upgrading the packaging to the latest version (4.0.1 at this time). Cheers, Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#894810: New upstream release
Package: src:python-doc8 Severity: wishlist Dear maintainers, Please consider upgrading the packaging to the latest version (0.8 at this time). Cheers, Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]
Hi Gianfranco, could you upload this please? Cheers, Ghis Le jeu. 15 févr. 2018 à 15:59, Ghislain Vaillant <ghisv...@gmail.com> a écrit : > Le jeudi 15 février 2018 à 15:51 +, Lumin a écrit : > > Hi, > > > > On 15 February 2018 at 13:52, Ghislain Vaillant <ghisv...@gmail.com> > > wrote: > > > > > > 1. please fix the following copyright issue: > > > I will update d/copyright accordingly. > > > > 2. This package failed to build when python2 version of sphinx > > > > exists: > > > > > > I don't care to be honest. > > > > > > It builds fine on a clean chroot with the Python 3 version of > > > Sphinx: > > > > OK. Let's omit the failure in an unclean build environment. > > > > @Gianfranco: Would you mind sponsoring this package after > > Ghislain uploaded updated package to mentors? > > I've checked several lists [1][2][3] and the package LGTM, > > expect for the license issue mentioned above. > > > > ✔ control and rules in good shape > > ✔ debomatic build and tests successful > > > > [1] devref section 7.5.1 Sponsoring packages > > [2] https://wiki.debian.org/SponsorChecklist > > [3] https://wiki.debian.org/LucaFalavigna/NEWChecklist > > I have just pushed the change requested by Lumin in the packaging > repository, retagged and submitted an updated tarball to mentors. > > Also, hi Gianfranco, been a while... > > ...yes I know my DD application :-) > > Ghis >
Bug#893729: sympy FTBFS: python3-distutils is now a separate package
Another option could be to patch the build system to use setuptools instead of distutils as recommended by the PyPA? Le mer. 21 mars 2018 à 20:45, Rebecca N. Palmera écrit : > Source: sympy > Severity: serious > Control: tags -1 patch > X-Debbugs-Cc: debian-pyt...@lists.debian.org > > python3-distutils has been moved out of python3.6 (as of 3.6.5~rc1-2), > so if you need it, please build-depend on it. (Or python3-setuptools, > given that this looks like it might prefer that.) > > (Has anyone checked whether there are more of these?) > > dpkg-buildpackage: info: source package sympy > dpkg-buildpackage: info: source version 1.1.1-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Yaroslav Halchenko > > dpkg-buildpackage: info: host architecture amd64 > dpkg-source --before-build sympy-1.1.1 > fakeroot debian/rules clean > dh clean --with python2,python3 --buildsystem=pybuild > debian/rules override_dh_auto_clean > make[1]: Entering directory > '/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1' > dh_auto_clean > I: pybuild base:217: python2.7 setup.py clean > /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown > distribution option: 'install_requires' >warnings.warn(msg) > running clean > I: pybuild base:217: python3.6 setup.py clean > Traceback (most recent call last): >File "setup.py", line 46, in > from setuptools import setup, Command > ModuleNotFoundError: No module named 'setuptools' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): >File "setup.py", line 49, in > from distutils.core import setup, Command > ModuleNotFoundError: No module named 'distutils' > E: pybuild pybuild:330: clean: plugin distutils failed with: exit > code=1: python3.6 setup.py clean > dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit > code 13 > make[1]: *** [debian/rules:29: override_dh_auto_clean] Error 25 > make[1]: Leaving directory > '/home/rnpalmer/Debian/builds/stackbuild/sympy-1.1.1' > make: *** [debian/rules:10: clean] Error 2 > dpkg-buildpackage: error: fakeroot debian/rules clean subprocess > returned exit status 2 > >
Bug#892758: ITP: python-bsdf -- Python implementation of the Binary Structured Data Format
Package: wnpp Severity: wishlist Owner: Ghislain Vaillant <ghisv...@gmail.com> * Package name: python-bsdf Version : 2.1.1 Upstream Author : Almar Klein * URL : http://bsdf.io/ * License : BSD Programming Lang: Python Description : Python implementation of the Binary Structured Data Format Long-Description: The Binary Structured Data Format (BSDF) is an open specification for serializing (scientific) data, for the purpose of storage and (inter process) communication. . It's designed to be a simple format, making it easy to implement in many programming languages. However, the format allows implementations to support powerful mechanics such as lazy loading of binary data, and streamed reading/writing. . BSDF is a binary format; by giving up on human readability, BSDF can be simple, compact and fast. See the full specification, or how it compares to other formats. This library is a new dependency for src:python-imageio. It will be maintained by the Debian Science Team.
Bug#888935: node-xterm FTBFS: error TS2339: Property 'parentElement' does not exist on type 'never'
> Source: node-xterm > Version: 2.7.0+ds1-1 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/no > de-xterm.html > > ... >debian/rules override_dh_auto_build > make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1' > tsc --project . > src/utils/Mouse.ts(30,80): error TS2339: Property 'parentElement' > does not exist on type 'never'. > debian/rules:19: recipe for target 'override_dh_auto_build' failed > make[1]: *** [override_dh_auto_build] Error 2 No idea how to fix this. The package used to build fine. Without further context, I am clueless about what to do about it. Please help, Ghis
Bug#891613: steam: Steam update suddenly depends on full nvidia graphic support regardless of equipment
On Tue, 27 Feb 2018 11:34:06 +0300 Boris Pekwrote: > Hi, > > (I am not a maintainer of this package.) > > > My system uses AMD graphics and while X installs a variety of other drivers, it > > is not that demanding of storage. Steam only adds nvidia support, but with the > > new edition it *requires* nvidia support whether needed or not. > > It is not true. nvidia packages are only in recommendations of package steam. > > > apt install steam > > [...] > > Try something like this: > sudo apt install -V steam --no-install-recommends > > Best wishes, > Boris IMO, they should be demoted to Suggests instead of Recommends. Steam on Windows does not come bundled with Nvidia drivers, nor does it explictly recommends to use Nvidia-powered hardware. I don't see how their inclusion in Recommends is justified by the definition in the Debian packaging policy. Besides, having the Nvidia libs listed in Recommends is inconvenient for users with only AMD or Intel graphics, which is my case personally. Being involved in Debian packaging, I do know about the presence of the --no-install-recommends option, but most Debian or Ubuntu users don't. Please reconsider. Best regards, Ghis
Bug#890200: PyQt5 package should provide an egg-info
On Mon, 12 Feb 2018 23:35:14 -0500 Scott Kittermanwrote: > On Sunday, February 11, 2018 09:19:59 PM VA wrote: > > Package: python-pyqt5 > > Version: 5.9.2+dfsg-1 > > > > Many Debian python packages include an egg-info folder, but python- pyqt5 > > does not. > > The PyQt5 upstream does not use standard Python tools for building the > package. As shipped by upstream, a source build of PyQt5: > > python3 configure.py > make > sudo make install > > does not install any egg information. Only the upstream wheels provide > anything. They provide a PyQt5-5.10.dist-info directory which appears to > perform a similar function. > > This is probably not feasible in Debian as we split PyQt5 into a number of > sub-packages to minimize the dependencies that get pulled in for various > applications. I'm not sure how to manage the egg-info for such a case. > > Scott K The problem is that anything that explicitly depends on pyqt5 (as in 'pyqt5' being listed in install_requires) yields a DistributionNotFound error. I am having this very issue with the recent release of spyder. A solution is to remove the explicit dependency in order to trick the setuptools metadata, but it is pretty ugly. Is there really no other way? Ghis
Bug#891618: DistributionNotFound: The 'pyqt5' distribution was not found
Package: spyder3 Version: 3.2.6+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, The latest update of src:spyder now explicitly requires pyqt5. Despite being pulled transitively by python{,3}-qtpy, detection by pkg_resources is failing. Launching spyder3 yields a DistributionNotFound error with the following traceback: Traceback (most recent call last): File "/usr/bin/spyder3", line 6, in from pkg_resources import load_entry_point File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3147, in @_call_aside File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3131, in _call_aside f(*args, **kwargs) File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3160, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 666, in _build_master ws.require(__requires__) File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 984, in require needed = self.resolve(parse_requirements(requirements)) File "/home/ghislain/.local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 870, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pyqt5' distribution was not found and is required by spyder -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spyder3 depends on: ii python3 3.6.4-1 ii python3-spyder 3.2.6+dfsg1-1 ii python3.6 3.6.4-4 spyder3 recommends no packages. spyder3 suggests no packages. Versions of packages python3-spyder depends on: ii libjs-jquery 3.2.1-1 ii libjs-mathjax2.7.2+dfsg-1 ii pylint3 1.8.1-1 ii python3 3.6.4-1 ii python3-chardet 3.0.4-1 ii python3-cloudpickle 0.5.2-2 ii python3-jedi 0.11.1-1 ii python3-nbconvert5.3.1-1 ii python3-numpydoc 0.7.0-1 ii python3-pickleshare 0.7.4-2 ii python3-psutil 5.4.2-1 ii python3-pycodestyle 2.3.1-2 ii python3-pyflakes 1.6.0-1 ii python3-pygments 2.2.0+dfsg-1 ii python3-qtawesome0.4.4+ds1-1 ii python3-qtconsole4.3.1-1 ii python3-qtpy 1.3.1-1 ii python3-rope 0.10.5-2 ii python3-sphinx 1.6.7-1 ii python3-zmq 16.0.2-2+b1 ii spyder-common3.2.6+dfsg1-1 Versions of packages python3-spyder suggests: ii cython3 0.26.1-0.4 pn python3-matplotlib pn python3-numpy pn python3-pandas ii python3-pil 4.3.0-2 pn python3-scipy pn python3-sympy pn spyder-doc Versions of packages python3-pyqt5 depends on: ii libc62.26-6 ii libgcc1 1:8-20180218-1 ii libpython3.6 3.6.4-4 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-12 ii libqt5dbus5 5.9.2+dfsg-12 ii libqt5designer5 5.9.2-6 ii libqt5gui5 5.9.2+dfsg-12 ii libqt5help5 5.9.2-6 ii libqt5network5 5.9.2+dfsg-12 ii libqt5printsupport5 5.9.2+dfsg-12 ii libqt5test5 5.9.2+dfsg-12 ii libqt5widgets5 5.9.2+dfsg-12 ii libqt5xml5 5.9.2+dfsg-12 ii libstdc++6 8-20180218-1 ii python3 3.6.4-1 ii python3-sip [sip-py3api-12.3]4.19.7+dfsg-1 Versions of packages python3-pyqt5 suggests: pn python3-pyqt5-dbg -- no debconf information
Bug#891617: DistributionNotFound: The 'pyopengl' distribution was not found
Package: spyder Version: 3.2.6+dfsg1-1 Severity: grave Justification: renders package unusable The latest update of src:spyder now requires pyopengl, which is currently missing from Depends. Launching spyder yields a DistributionNotFound error with the following traceback: Traceback (most recent call last): File "/usr/bin/spyder", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3147, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3131, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3160, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 666, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 984, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 870, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pyopengl' distribution was not found and is required by spyder -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spyder depends on: ii python 2.7.14-4 ii python-spyder 3.2.6+dfsg1-1 ii python2.7 2.7.14-6 spyder recommends no packages. spyder suggests no packages. Versions of packages python-spyder depends on: ii libjs-jquery3.2.1-1 ii libjs-mathjax 2.7.2+dfsg-1 ii pylint 1.8.1-1 ii python 2.7.14-4 ii python-chardet 3.0.4-1 ii python-cloudpickle 0.5.2-2 ii python-jedi 0.11.1-1 ii python-nbconvert5.3.1-1 ii python-numpydoc 0.7.0-1 ii python-pickleshare 0.7.4-2 ii python-psutil 5.4.2-1 ii python-pycodestyle 2.3.1-2 ii python-pyflakes 1.6.0-1 ii python-pygments 2.2.0+dfsg-1 ii python-qtawesome0.4.4+ds1-1 ii python-qtconsole4.3.1-1 ii python-qtpy 1.3.1-1 ii python-rope 0.10.5-2 ii python-sphinx 1.6.7-1 ii python-zmq 16.0.2-2+b1 ii spyder-common 3.2.6+dfsg1-1 Versions of packages python-spyder suggests: pn cython pn python-matplotlib ii python-numpy 1:1.13.3-2 pn python-pandas ii python-pil 4.3.0-2 pn python-scipy pn python-sympy pn spyder-doc Versions of packages python-pyqt5 depends on: ii libc62.26-6 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-12 ii libqt5dbus5 5.9.2+dfsg-12 ii libqt5designer5 5.9.2-6 ii libqt5gui5 5.9.2+dfsg-12 ii libqt5help5 5.9.2-6 ii libqt5network5 5.9.2+dfsg-12 ii libqt5printsupport5 5.9.2+dfsg-12 ii libqt5test5 5.9.2+dfsg-12 ii libqt5widgets5 5.9.2+dfsg-12 ii libqt5xml5 5.9.2+dfsg-12 ii libstdc++6 8-20180218-1 ii python 2.7.14-4 ii python-sip [sip-api-12.3]4.19.7+dfsg-1 Versions of packages python-pyqt5 suggests: pn python-pyqt5-dbg -- no debconf information
Bug#891132: RFS: python-meshio/1.11.7-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-meshio" * Package name: python-meshio Version : 1.11.7-1 Upstream Author : Nico Schlömer * URL : https://github.com/nschloe/meshio * License : Expat Section : python It builds those binary packages: meshio-tools - command-line tools for meshio python3-meshio - library for reading and writing mesh data (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-meshio Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-meshio/python-meshio_1.11.7-1.dsc Changes since the last upload: * New upstream version 1.11.7 * Refresh the patch queue * Update the copyright years * Remove obsolete dependency on lxml * Drop the get-orig-source target * Point the VCS URIs to salsa.debian.org * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 Regards, Ghislain Vaillant
Bug#891131: RFS: pytest-qt/2.3.1-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pytest-qt" * Package name: pytest-qt Version : 2.3.1-1 Upstream Author : Bruno Oliveira * URL : https://github.com/pytest-dev/pytest-qt * License : Expat Section : python It builds those binary packages: python-pytestqt-doc - documentation for pytest-qt python3-pytestqt - pytest plugin for Qt application testing (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pytest-qt Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pytest-qt/pytest-qt_2.3.1-1.dsc Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org [ Ghislain Antony Vaillant ] * New upstream version 2.3.1 * Refresh the patch queue * Update the copyright years * Normalize the package descriptions * Drop the get-orig-source target * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Set PYTEST_QT_API before running the tests * Increase verbosity of autopkgtests Regards, Ghislain Vaillant
Bug#891130: RFS: python-mechanicalsoup/0.10.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-mechanicalsoup" * Package name: python-mechanicalsoup Version : 0.10.0-1 Upstream Author : Mirth Hickford <mirth.hickf...@gmail.com> * URL : https://github.com/hickford/MechanicalSoup * License : Expat Section : python It builds those binary packages: python-mechanicalsoup - library for automating interaction with websites (Python 2) python3-mechanicalsoup - library for automating interaction with websites (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-mechanicalsoup Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-mechanicalsoup/python-mechanicalsoup_0.10.0-1.dsc Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org [ Ghislain Antony Vaillant ] * New upstream version 0.10.0 (Closes: #883366) * Refresh the patch queue * Update the copyright years * Drop the get-orig-source target * Normalize the package descriptions * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Explicitly disable testing at build time. Reason: Tests require network access * Add pytest-mock to the autopkgtest Depends Regards, Ghislain Vaillant
Bug#891117: RFS: python-schema/0.6.7-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-schema" * Package name: python-schema Version : 0.6.7-1 Upstream Author : Vladimir Keleshev <vladi...@keleshev.com> * URL : https://github.com/keleshev/schema * License : Expat Section : python It builds those binary packages: pypy-schema - simple data validation library (PyPy) python-schema - simple data validation library (Python 2) python3-schema - simple data validation library (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-schema Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-schema/python-schema_0.6.7-1.dsc Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org [ Ghislain Antony Vaillant ] * Update the gbp configuration * New upstream version 0.6.7 * Fixup whitespacing in rules file * Support the nocheck build profile * Filter egg-info with extend-diff-ignore * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Update the copyright years Regards, Ghislain Vaillant
Bug#891116: RFS: python-sparse/0.2.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-sparse" * Package name: python-sparse Version : 0.2.0-1 Upstream Author : Matthew Rocklin <mrock...@gmail.com> * URL : https://github.com/mrocklin/sparse * License : BSD Section : python It builds those binary packages: python3-sparse - multidimensional sparse arrays for Python To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-sparse Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-sparse/p ython-sparse_0.2.0-1.dsc Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org [ Ghislain Antony Vaillant ] * New upstream version 0.2.0 * Drop superfluous nocheck guards * Fixup whitespacing in rules file * Add versioned dependency to scipy * Add new install dependency on six * Add new test dependency on packaging * Move extend-diff-ignore to d/s/options * Add patch disabling the upstream pytest config - New patch: No-pytest-config.patch * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Update the copyright years Regards, Ghislain Vaillant
Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]
Le jeudi 15 février 2018 à 15:51 +, Lumin a écrit : > Hi, > > On 15 February 2018 at 13:52, Ghislain Vaillant <ghisv...@gmail.com> > wrote: > > > > 1. please fix the following copyright issue: > > I will update d/copyright accordingly. > > > 2. This package failed to build when python2 version of sphinx > > > exists: > > > > I don't care to be honest. > > > > It builds fine on a clean chroot with the Python 3 version of > > Sphinx: > > OK. Let's omit the failure in an unclean build environment. > > @Gianfranco: Would you mind sponsoring this package after > Ghislain uploaded updated package to mentors? > I've checked several lists [1][2][3] and the package LGTM, > expect for the license issue mentioned above. > > ✔ control and rules in good shape > ✔ debomatic build and tests successful > > [1] devref section 7.5.1 Sponsoring packages > [2] https://wiki.debian.org/SponsorChecklist > [3] https://wiki.debian.org/LucaFalavigna/NEWChecklist I have just pushed the change requested by Lumin in the packaging repository, retagged and submitted an updated tarball to mentors. Also, hi Gianfranco, been a while... ...yes I know my DD application :-) Ghis
Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]
2018-02-15 8:33 GMT+00:00 Lumin <cdlumin...@gmail.com>: > control: merge -1 880442 > control: owner -1 ! > control: tag -1 +moreinfo > > Hi Ghislain, > > Some comments on this package: > > 1. please fix the following copyright issue: >(reproduce with $ licensecheck -r .) > > ./jsonrpc/six.py: MIT/X11 (BSD like) >Copyright (c) 2010-2013 Benjamin Peterson > > There is six.py. What's the relationship between it and python3-six? > My preliminary guess is that upstream just copied that file to their > project. Correct. Don't think it is worth repacking though. I will update d/copyright accordingly. > 2. This package failed to build when python2 version of sphinx exists: > > make[2]: Entering directory > '/home/lumin/packages/sponsor/python-jsonrpc-1.10.8/docs' > sphinx-build -b html -d _build/doctrees source _build/html > Running Sphinx v1.6.7 > making output directory... > > Configuration error: > There is a programable error in your configuration file: > > Traceback (most recent call last): > File "/usr/lib/python2.7/dist-packages/sphinx/config.py", line 157, > in __init__ > execfile_(filename, config) > File "/usr/lib/python2.7/dist-packages/sphinx/util/pycompat.py", > line 150, in execfile_ > exec_(code, _globals) > File "/usr/lib/python2.7/dist-packages/six.py", line 709, in exec_ > exec("""exec _code_ in _globs_, _locs_""") > File "", line 1, in > File "conf.py", line 109, in > import sphinx_rtd_theme > ImportError: No module named sphinx_rtd_theme > > make[2]: *** [Makefile:45: html] Error 1 > make[2]: Leaving directory > '/home/lumin/packages/sponsor/python-jsonrpc-1.10.8/docs' > make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 > make[1]: Leaving directory > '/home/lumin/packages/sponsor/python-jsonrpc-1.10.8' > make: *** [debian/rules:9: build] Error 2 > dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 > debuild: fatal error at line 1152: > dpkg-buildpackage -rfakeroot -us -uc -ui -i failed I don't care to be honest. It builds fine on a clean chroot with the Python 3 version of Sphinx: http://debomatic-amd64.debian.net/distribution#unstable/python-jsonrpc/1.10.8-1/buildlog That's all that matters. Ghis
Bug#890364: pybind11-dev: Request migration to unstable
Hi Shane, thanks for reaching out, On Wed, 14 Feb 2018 00:48:14 + Shane Loretzwrote: > Would the maintainer be willing to migrate 2.2.1 from experimental to unstable? I'm a user of a distribution based on debian unstable. I have been using pybind11 from pip previously. The package in experimental appears to be working flawlessly for my usecase and has some nice new features not in the version currently in unstable. There are a few rdpends I have got to test first to guarantee a smooth upgrade. But yes, I intend to migrate the new version to unstable soon. Cheers, Ghis
Bug#890379: RFS: python-jsonrpc/1.10.8-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-jsonrpc" * Package name: python-jsonrpc Version : 1.10.8-1 Upstream Author : Kirill Pavlov <k...@p99.io> * URL : https://github.com/pavlov99/json-rpc * License : Expat Section : python It builds those binary packages: python-jsonrpc-doc - documentation for json-rpc python3-jsonrpc - Python implementation of JSON-RPC 1.0 and 2.0 (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-jsonrpc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-jsonrpc/python-jsonrpc_1.10.8-1.dsc Packaging repository: https://salsa.debian.org/python-team/modules/python-jsonrpc Debomatic build: http://debomatic-amd64.debian.net/distribution#unstable/python-jsonrpc/1.10.8-1 Changes since the last upload: * Initial release. (Closes: #879050) Regards, Ghislain Vaillant
Bug#890306: RFS: sphinxcontrib-doxylink/1.5-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sphinxcontrib-doxylink" * Package name: sphinxcontrib-doxylink Version : 1.5-1 Upstream Author : Matt Williams * URL : https://github.com/sphinx-contrib/doxylink * License : BSD Section : python It builds those binary packages: python3-sphinxcontrib.doxylink - Sphinx extension for linking to Doxygen documentation (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sphinxcontrib-doxylink Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sphinxcontrib-doxylink/sphinxcontrib-doxylink_1.5-1.dsc Packaging repository: https://salsa.debian.org/python-team/modules/sphinxcontrib-doxylink Debomatic build: http://debomatic-amd64.debian.net/distribution#unstable/sphinxcontrib-doxylink/1.5-1 Changes since the last upload: [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org [ Ghislain Antony Vaillant ] * d/gbp.conf: Sign all tags * d/gbp.conf: Drop pq section * Source future releases from GitHub * New upstream version 1.5 * Drop the patch queue, fixed upstream * Drop the packaging for Python 2, dropped upstream * Add new build dependency on doxygen and pytest * Add pybuild setup for running the tests * Run autopkgtests for all supported Python versions * Point the Homepage URI to the GitHub repository * Update the copyright years * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Normalize the package descriptions Regards, Ghislain Vaillant
Bug#889891: python-csvkit: Executable for csvgrep.py, csvcut.py etc. are needed
Control: tags -1 wontfix On Thu, 08 Feb 2018 14:13:53 +0300 Aleksey Cheusovwrote: > Hello. Could you please provide executables for .py files under > /usr/lib/python2.7/dist-packages/csvkit/utilities directory? > That is, csvgrep (without .py or .pyc extension), csvcut, csvsort etc. > It would be nice to see these executable under bin directory. python3-csvkit already provides said scripts under /usr/bin. > Also, please specify python2 in shebang explicitely instead of '/usr/bin/env python'. > A reason for this is that default python may change to, for example, python v.3. No need for that. Again, if you need these scripts, please install the python3-csvkit package.
Bug#890225: RFS: flake8-polyfill/1.0.2-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "flake8-polyfill" * Package name: flake8-polyfill Version : 1.0.2-1 Upstream Author : Ian Cordasco <graffatcolmin...@gmail.com> * URL : https://gitlab.com/pycqa/flake8-polyfill * License : MIT Section : python It builds those binary packages: python3-flake8-polyfill - polyfill package for Flake8 plugins To access further information about this package, please visit the following URL: https://mentors.debian.net/package/flake8-polyfill Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/flake8-polyfill/flake8-polyfill_1.0.2-1.dsc Packaging repository: https://salsa.debian.org/python-team/modules/flake8-polyfill Debomatic: http://debomatic-amd64.debian.net/distribution#unstable/flake8-polyfill/1.0.2-1 Changes since the last upload: * New upstream version 1.0.2 * Update copyright years * Drop superfluous nocheck guards * Fixup whitespacing in rules file * Point VCS URIs to salsa.debian.org * Bump the debhelper version to 11 * Bump the standards version to 4.1.3 * Add missing Enhances relationship Regards, Ghislain Vaillant
Bug#880402: Blocked by #888458
Control: block -1 by 888458
Bug#888458: python-networkx: packages out of date, haven't been updated for 18 months
CC'd Sandro explictly in case he is not subscribed to the bugs. Several packages now require an update for networkx. Please confirm whether you are still actively involved with its packaging, or whether assistance is required and in what form. Thanks, Ghis On Thu, 25 Jan 2018 14:25:49 -0800 Jameson Graef Rollinswrote: > Package: python-networkx > Version: 1.11-2 > Severity: normal > > The python-networkx packages were last updated in August 2016, which > was 18 months ago. There has been a major upstream releases since > then (current stable upstream is 2.1). The missing major release > update is causing compatibility problems with other platforms. > > Has this package been orphaned? Please advise. > > Thanks for the help. > > jamie. > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages python-networkx depends on: > ii python2.7.14-4 > ii python-decorator 4.1.2-1 > > Versions of packages python-networkx recommends: > ii python-matplotlib 2.0.0+dfsg1-2+b1 > ii python-numpy 1:1.13.3-2 > ii python-pkg-resources 38.2.4-2 > ii python-pydot 1.2.3-1 > ii python-pygraphviz 1.4~rc1-1+b1 > ii python-scipy 0.19.1-2 > ii python-yaml 3.12-1+b1 > > Versions of packages python-networkx suggests: > ii python-networkx-doc 1.11-2 > > -- no debconf information > >
Bug#890048: src:pydocstyle: New upstream release
Package: src:pydocstyle Severity: wishlist Dear Maintainer, Please consider updating the packaging for src:pydocstyle to the latest upstream release (2.1.1 at present). The latest upstream release for flake8-docstrings requires python3-pydocstyle >= 2.1. Cheers, Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#887933: src:nose2: Provide a binary package for PyPy
Can you build a pypy-nose2 package for pypy, in addition to the current binary packages for Python 2 (python-nose2) and Python 3 (python3-nose2). Thanks, Ghis 2018-02-05 16:05 GMT+00:00 Pierre-Elliott Bécue <be...@crans.org>: > Dear Ghislain, > > I might be unaware of something, but I'm not able to understand what you are > currently asking. > > Could you please give me some hints? :) > > Cheers, > > -- > Pierre-Elliott Bécue > GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
Bug#889554: RFP: gnome-shell-extension-backslide -- wallpaper slideshow extension for GNOME Shell
Package: wnpp Severity: wishlist * Package name: gnome-shell-extension-backslide Version : 1.4.4 Upstream Author : Lukas Knuth * URL : https://extensions.gnome.org/extension/543/backslide/ * License : GPL-3+ Programming Lang: Javascript Description : wallpaper slideshow extension for GNOME Shell Long-Description: A simple Gnome-Shell Extension for setting up an automatic background-image (wallpaper) slideshow.
Bug#889284: src:sphinx-gallery: Missing install dependencies
Package: src:sphinx-gallery Severity: normal Dear Maintainer, Upstream did not explicitly list the required install dependencies for sphinx-gallery (see comment in setup.py). According to the upstream README the following relationships should be added: Depends: python{,3}-matplotlib, python{,3}-pil, python{,3}-sphinx, Suggests: python{,3}-mayavi, python{,3}-seaborn Cheers, Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#888482: RFP: python-numcodecs -- buffer compression and transformation codecs for Python
Package: wnpp Severity: wishlist * Package name: python-numcodecs Version : 0.5.2 Upstream Author : Alistair Miles* URL : https://github.com/alimanfoo/numcodecs * License : Expat Programming Lang: Python Description : buffer compression and transformation codecs for Python Long-Description: Numcodecs is a Python package providing buffer compression and transformation codecs for use in data storage and communication applications. These include: . - Compression codecs, e.g., Zlib, BZ2, LZMA and Blosc. - Pre-compression filters, e.g., Delta, Quantize, FixedScaleOffset, PackBits, Categorize. - Integrity checks, e.g., CRC32, Adler32. . All codecs implement the same API, allowing codecs to be organized into pipelines in a variety of ways. This package is a dependency for src:python-zarr also under RFP.
Bug#888481: RFP: python-zarr -- chunked, compressed, N-dimensional arrays for Python
Package: wnpp Severity: wishlist * Package name: python-zarr Version : 2.1.4 Upstream Author : Alistair Miles* URL : https://github.com/zarr-developers/zarr * License : Expat Programming Lang: Python Description : chunked, compressed, N-dimensional arrays for Python Long-Description: Zarr is a Python package providing an implementation of chunked, compressed, N-dimensional arrays. Some highlights: . - Create N-dimensional arrays with any NumPy dtype. - Chunk arrays along any dimension. - Compress chunks using the fast Blosc meta-compressor or alternatively using zlib, BZ2 or LZMA. - Store arrays in memory, on disk, inside a Zip file, on S3, ... - Read an array concurrently from multiple threads or processes. - Write to an array concurrently from multiple threads or processes. - Organize arrays into hierarchies via groups. - Use filters to preprocess data and improve compression. This package is a new supported backend for src:python-xarray. It should probably be team-maintained within the Debian Science Team alongside src:python-xarray.
Bug#888075: Switch to ITA
Control: owner -1 ! Control: retitle -1 ITA: csvkit I intend to adopt csvkit and transfer its maintenance to the Debian Science Team together with the agate stack it depends on. Cheers, Ghis
Bug#874498: protobuf: Please package latest upstream version
On Fri, 17 Nov 2017 15:47:57 -0500 Sandro Tosiwrote: > adding explicitly all the protobug uploaders + the latest 2 DDs who > uploaded the package > > > Please package the latest version from upstream (3.4.0 at this time). > > > > Severity important because currect protoc produces broken JavaScript > > code for gogo.proto. > > Is there any chance we could get a newer version of protobuf uploaded > to sid? we're currently running a rather old version for a project > moving relatively fast as protobuf. 3.5.0 was released few days ago > and it would be extremely helpful if we can get it available for > debian unstable Just to complement what Sandro said, the latest release of grpcio (used by Tensorflow) requires protobuf >= 3.5.
Bug#787519: git-buildpackage: Read config from XDG_CONFIG_HOME/debian/gbp.conf
On Sat, 16 Dec 2017 08:36:03 +0100 Guido =?iso-8859-1?Q?G=FCnther?= wrote: > > Another issue is that once we do this writing config files (which will will > need to happen too) has to decide what to do if both ~/.gbp.conf and > ~/.git-buildpackage/gbp.conf are there. With the current order we'd need > to still favour ~/.gbp.conf so IMHO the XDG_CONFIG_HOME version needs > to have higher priority than ~/.gbp.conf. I second that $XDG_CONFIG_HOME/git-buildpackage/gbp.conf should be given priority over $HOME/.gbp.conf, which should facilitate the transition whilst keeping old configurations working. Ghis
Bug#887933: src:nose2: Provide a binary package for PyPy
Package: src:nose2 Severity: wishlist Dear Maintainer, Please consider providing a binary package for PyPy to facilitate testing of other PyPy packages which test suite depends on nose2. One such package is src:python-jsonrpc, which I am currently working on. Cheers, Ghis -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3
cc'd to Pirate Praveen who reported a similar issue for a version on experimental? Do you have an idea what's going on? Why is Adrian's log different to yours? On Thu, 18 Jan 2018 09:23:11 +0200 Adrian Bunkwrote: > Source: libjs-fetch > Version: 2.0.3-1 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/li bjs-fetch.html > > ... >debian/rules override_dh_auto_test > make[1]: Entering directory '/build/1st/libjs-fetch-2.0.3' > xvfb-run -a -s "-screen 0 640x480x16" ./script/test > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime- pbuilder1' > Error loading resource http://localhost:3901/node_modules/mocha/mocha .css (203). Details: Error transferring http://localhost:3901/node_modu les/mocha/mocha.css - server replied: Not Found > Error loading resource http://localhost:3901/node_modules/url-search- params/build/url-search-params.js (203). Details: Error transferring ht tp://localhost:3901/node_modules/url-search-params/build/url-search- params.js - server replied: Not Found > Error loading resource http://localhost:3901/node_modules/mocha/mocha .js (203). Details: Error transferring http://localhost:3901/node_modul es/mocha/mocha.js - server replied: Not Found > ReferenceError: Can't find variable: Mocha > ReferenceError: Can't find variable: suite > TypeError: mocha.run is not a function. (In 'mocha.run()', 'mocha.run' is undefined) > Likely due to external resource loading and timing, your tests require calling `window.initMochaPhantomJS()` before calling any mocha setup functions. See https://github.com/nathanboktae/mocha-phantomjs-co re/issues/12 > TypeError: Attempting to change the setter of an unconfigurable property. > TypeError: Attempting to change the setter of an unconfigurable property. > QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime- pbuilder1' > Error loading resource http://localhost:3901/node_modules/mocha/mocha .css (203). Details: Error transferring http://localhost:3901/node_modu les/mocha/mocha.css - server replied: Not Found > Error loading resource http://localhost:3901/node_modules/url-search- params/build/url-search-params.js (203). Details: Error transferring ht tp://localhost:3901/node_modules/url-search-params/build/url-search- params.js - server replied: Not Found > Error loading resource http://localhost:3901/node_modules/mocha/mocha .js (203). Details: Error transferring http://localhost:3901/node_modul es/mocha/mocha.js - server replied: Not Found > ReferenceError: Can't find variable: Mocha > Likely due to external resource loading and timing, your tests require calling `window.initMochaPhantomJS()` before calling any mocha setup functions. See https://github.com/nathanboktae/mocha-phantomjs-co re/issues/12 > TypeError: Attempting to change the setter of an unconfigurable property. > TypeError: Attempting to change the setter of an unconfigurable property. > debian/rules:28: recipe for target 'override_dh_auto_test' failed > make[1]: *** [override_dh_auto_test] Error 1 > >
Bug#887747: RFP: gnome-shell-extension-easyscreencast -- video recording extension for the GNOME shell
Control: owner -1 ! Control: retitle -1 ITP: gnome-shell-extension-easyscreencast -- video recording extension for the GNOME shell I have successfully built a local version of the package using the initial work done by the Kali team [1]. I intend to base the initial packaging on that and improve it to the Debian packaging standards. I'd like it to be maintained under the umbrella of the Debian GNOME team (cc'd). Anyone from the team, could you please accept my request to join the group on salsa, so I can push and start a formal review. [1] http://git.kali.org/gitweb/?p=packages/gnome-shell-extension-easyscreencast.git;a=summary Cheers, Ghis On Fri, 19 Jan 2018 16:10:47 + Ghislain Vaillant <ghisv...@gmail.co m> wrote: > Package: wnpp > Severity: wishlist > > * Package name: gnome-shell-extension-easyscreencast > Version : 0.10 > Upstream Author : Tobias Schönberg > * URL : https://github.com/EasyScreenCast/EasyScreenCast > * License : GPL-3 > Programming Lang: JavaScript > Description : video recording extension for the GNOME shell > > Long-Description: > This extension simplifies the use of the video recording function > integrated in gnome shell, allows quickly to change the various > settings of the desktop recording.
Bug#887747: RFP: gnome-shell-extension-easyscreencast -- video recording extension for the GNOME shell
Package: wnpp Severity: wishlist * Package name: gnome-shell-extension-easyscreencast Version : 0.10 Upstream Author : Tobias Schönberg * URL : https://github.com/EasyScreenCast/EasyScreenCast * License : GPL-3 Programming Lang: JavaScript Description : video recording extension for the GNOME shell Long-Description: This extension simplifies the use of the video recording function integrated in gnome shell, allows quickly to change the various settings of the desktop recording.
Bug#881205: Assistance for maintaining src:backintime
Dear Jonathan, I was suprised to discover that backintime had been removed from testing despite RC bug #881205 being fixed upstream [1]. For testing/unstable an update of the package to version 1.1.24 should do the trick, whilst stretch/wheezy will require a backport of this particular commit. I was wondering whether you need any help with the maintenance of the package, which I'd be happy to offer. It might also be useful to move the package to team-maintenance long term, under collab-maint or one of the Python packaging teams. [1] https://github.com/bit-team/backintime/commit/cef81d0da93ff60125260 7df3db1a48f7f6f01 Cheers, Ghis
Bug#863168: ismrmrd FTBFS on armhf
Le 17/12/17 à 15:40, Adrian Bunk a écrit : On Sun, Dec 17, 2017 at 02:33:03PM +, Ghislain Vaillant wrote: ISMRMRD uses a non-portable instruction (#pragma pack) which modifies the memory alignment of its data structures. It seems neither armhf nor sparc64 supports it, hence the failure of the test suite for both architectures. #pragma pack is supported everywhere, and this pragma is the cause of the FTBFS. Ack. I am not sure what the best course of action is. Either leaving things as is assuming a future rebuild with a newer compiler could improve it, disabling the tests or even dropping the packages for the failing architectures. Opinions welcome. With #pragma pack you are forcing the compiler to do the wrong thing, the only thing a newer compiler could possibly improve would be to error on such code. Ack. Unaligned floating point access on armhf is expected to fail, and that's exactly what happens here: unknown location(0): fatal error: in "AcquisitionsTest/test_acquisition_header": memory access violation at address: 0xbecd3b6a: invalid address alignment Running the test in gdb confirms that this is floating point code. sparc is generally unhappy with unaligned access: unknown location(0): fatal error: in "AcquisitionsTest/test_acquisition_header": memory access violation at address: 0x7feffb7c936: invalid address alignment Note that even on architectures where unaligned access is permitted it can be slower than aligned access. So, what would be the right course of action moving forward? Removing the package for both armhf and sparc64? Ghis
Bug#863168: ismrmrd FTBFS on armhf
ISMRMRD uses a non-portable instruction (#pragma pack) which modifies the memory alignment of its data structures. It seems neither armhf nor sparc64 supports it, hence the failure of the test suite for both architectures. I am not sure what the best course of action is. Either leaving things as is assuming a future rebuild with a newer compiler could improve it, disabling the tests or even dropping the packages for the failing architectures. Opinions welcome. Ghis
Bug#884154: Forwarded upstream
Control: forwarded -1 https://github.com/github/fetch/issues/594
Bug#884154: [Pkg-javascript-devel] Bug#884154: FTBFS with chai 4.1.2 in experimental
Le 16/12/17 à 17:31, Pirate Praveen a écrit : On ശനി 16 ഡിസംബര് 2017 10:44 വൈകു, Ghislain Vaillant wrote: I don't know anything about chai. Besides, since you are its maintainer, I would expect the investigation to be done by yourself rather than myself. No, that is not how a transition is supposed to work. Do you expect maintainer of nodejs package to fix all issues of all packages using nodejs by themselves when updating nodejs versions? You are deliberately taking an extreme case to fulfill your narrative. I would not fit nodejs and chai in the same basket. I did not even get heads up with webmock transition in ruby team. It was right away FTBFS and autoremoval from testing for packages failing to build with webmock 3. And? I can try and help, but as maintainer of libjs-fetch, it is your responsibility to fix issues of your package when dependencies change. We are talking about a *test* dependencies which now makes the build fail after a major version bump. It makes sense to expect more information from the corresponding maintainer. Should we expect every single maintainer affected by an FTBFS to go read the release notes of chai in order to figure what broke between version 3 and 4. I am very skeptical about this. I meant context about why the package now FTBFS. I understand this is a transition and I don't think uploading to unstable is wise before FTBFS issues such as this one are fixed. Is there an urgency in having chai 4.x in testing/unstable? Indeed, that is why it is uploaded first to experimental and giving heads up to packages affected by this transition. We can definitely wait for a reasonable time before uploading to unstable. Which is appreciated. 1. chai itself is FTBFS with nodejs 6 That's unfortunate indeed. 2. we generally want to ship the latest versions But not systematically. 3. Some packages are already starting to require newer versions of chai, for example node-yargs (whose tests are disabled currently). It makes sense to disable them if they specifically require chai >= 4. You could ask upstream to move to chai 4 and take their help. Or you could also disable tests. Disabling the tests would be a serious downgrade considering testing is currently working, unlike node-yargs. I am seriously uncomfortable with this proposal. I can ask upstream, though chai is officially pinned at version 2.x there.
Bug#884154: [Pkg-javascript-devel] Bug#884154: FTBFS with chai 4.1.2 in experimental
Le 16/12/17 à 17:07, Pirate Praveen a écrit : On ശനി 16 ഡിസംബര് 2017 08:41 വൈകു, Ghislain Vaillant wrote: Why is this happening with chai 4.x and not 3.5? That is what we need to find out. Possibly some deprecated methods are removed from new version. I don't know anything about chai. Besides, since you are its maintainer, I would expect the investigation to be done by yourself rather than myself. Sorry, but I am gonna need more context to fix this. We are trying to update chai from 3.5 to 4.x but noticed this package fails with chai 4.x. Once we upload chai 4.x to unstable, it will cause FTBFS (and severity will be changed to serious) and we wanted to give a heads up before that. This is the normal procedure of a transition. I meant context about why the package now FTBFS. I understand this is a transition and I don't think uploading to unstable is wise before FTBFS issues such as this one are fixed. Is there an urgency in having chai 4.x in testing/unstable?
Bug#884154: FTBFS with chai 4.1.2 in experimental
Why is this happening with chai 4.x and not 3.5? Sorry, but I am gonna need more context to fix this. Ghis On Tue, 12 Dec 2017 14:00:12 +0530 Pirate Praveenwrote: package: libjs-fetch version: 2.0.3-1 severity: important I'd like to upload chai 4.1.2 to unstable soon, please fix these failures. xvfb-run -a -s "-screen 0 640x480x16" ./script/test QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pravi' Error loading resource http://localhost:3901/node_modules/url-search-params/build/url-search-params.js (203). Details: Error transferring http://localhost:3901/node_modules/url-search-params/build/url-search-params.js - server replied: Not Found ․ArrayBuffer is deprecated in XMLHttpRequest.send(). Use ArrayBufferView instead. ․ 94 passing (578ms) 11 pending 21 failing 1) polyfill Headers returns null on no header found: isNull@http://localhost:3901/node_modules/chai/chai.js:4757:58 http://localhost:3901/test/test.js:208:18 callFn@http://localhost:3901/node_modules/mocha/mocha.js:4613:25 run@http://localhost:3901/node_modules/mocha/mocha.js:4 06:13 runTest@http://localhost:3901/node_modules/mocha/mocha.js:5002:13 http://localhost:3901/node_modules/mocha/mocha.js:5080:19 next@http://localhost:3901/node_modules/mocha/mocha.js:4927:16 http://localhost:3901/node_modules/mocha/mocha.js:4937:11 next@http://localhost:3901/node_modules/mocha/mocha.js:4875:25 http://localhost:3901/node_modules/mocha/mocha.js:4904:9 timeslice@http://localhost:3901/node_modules/mocha/mocha.js:6042:27 2) polyfill Headers deletes headers: isNull@http://localhost:3901/node_modules/chai/chai.js:4757:58 http://localhost:3901/test/test.js:221:18 callFn@http://localhost:3901/node_modules/mocha/mocha.js:4613:25 run@http://localhost:3901/node_modules/mocha/mocha.js:4 06:13 runTest@http://localhost:3901/node_modules/mocha/mocha.js:5002:13 http://localhost:3901/node_modules/mocha/mocha.js:5080:19 next@http://localhost:3901/node_modules/mocha/mocha.js:4927:16 http://localhost:3901/node_modules/mocha/mocha.js:4937:11 next@http://localhost:3901/node_modules/mocha/mocha.js:4875:25 http://localhost:3901/node_modules/mocha/mocha.js:4904:9 timeslice@http://localhost:3901/node_modules/mocha/mocha.js:6042:27 3) polyfill Headers throws TypeError on invalid character in field name: throws@http://localhost:3901/node_modules/chai/chai.js:6320:16 http://localhost:3901/test/test.js:237:18 callFn@http://localhost:3901/node_modules/mocha/mocha.js:4613:25 run@http://localhost:3901/node_modules/mocha/mocha.js:4606:13 runTest@http://localhost:3901/n de_modules/mocha/mocha.js:5002:13 http://localhost:3901/node_modules/mocha/mocha.js:5080:19 next@http://localhost:3901/node_modules/mocha/mocha.js:4927:16
Bug#883366: python-mechanicalsoup: new upstream version 0.9.0
Dear Paul, On Sun, 03 Dec 2017 12:13:27 +0800 Paul Wisewrote: Source: python-mechanicalsoup Severity: wishlist Please package the new upstream version 0.9.0 of MechanicalSoup: https://github.com/MechanicalSoup/MechanicalSoup/releases I'd be happy to update the packaging of MechanicalSoup to the latest upstream release. However, version 0.8.0 has been under RFS for more than a month, and has yet to be answered [1]. This is not an isolated case unfortunately, and my personal motivation is suffering as a result. Please also adjust the Homepage to point at the new github org. Sure. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878175 Cheers, Ghis
Bug#883784: src:cloudpickle: Binary package for Python 2
Package: src:cloudpickle Severity: normal Dear Maintainer, The next release of spyder will require a dependency on cloudpickle [1]. Since spyder is packaged for both Python 2 and 3, could you please consider providing a binary package for Python 2? [1] https://github.com/spyder-ide/spyder/pull/5341 Thanks, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful'), (100, 'artful-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-17-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#883782: src:cloudpickle: New upstream release
Package: src:cloudpickle Severity: wishlist Dear Maintainer, Please consider upgrading the packaging to the latest version (0.5.2 at the time of writing). Thanks, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful'), (100, 'artful-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-17-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#882303: RFS: sphinxcontrib-bibtex/0.3.6-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: sphinxcontrib-bibtex Version : 0.3.6-2 Upstream Author : Matthias C. M. Troffaes * URL : https://github.com/mcmtroffaes/sphinxcontrib-bibtex * License : BSD Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/sphinxcontrib-bibtex.git Changes since last upload: * Enable testing during build * Ignore tests requiring Tinkerer * Add missing B-D on sphinx-common * Bump the standards version to 4.1.1 Regards, Ghis
Bug#882302: RFS: python-meshio/1.9.3-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-meshio Version : 1.9.3-1 Upstream Author : Nico Schlömer * URL : https://github.com/nschloe/meshio * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-meshio.git Changes since last upload: * New upstream version 1.9.3 * Refresh the patch queue * Add new dependency on netCDF4 * Add support for nocheck builds Regards, Ghis
Bug#877316: Forwarded upstream
Control: forwarded -1 https://github.com/clMathLibraries/clBLAS/issues/321
Bug#881837: Updating the h5py Uploaders list
Control: tags -1 + fixed pending On Wed, 15 Nov 2017 18:16:51 +0100 Tobias Frostwrote: Source: h5py Version: 2.6.0-2 2.7.1-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Soeren Sonnenburg wishes no longer to be uploader of h5py. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. Done. Soeren Sonnenburg has been removed from the Uploaders list of this package. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) I already took over maintenance a while back. Thanks for your work within the MIA team. Regards, Ghis
Bug#879196: patch attached
On Tue, 14 Nov 2017 22:35:47 + "Ana C. Custura"wrote: Hi Ghis, Thank you for the patches. I have merged this one (I thought the way you rewrote the rules file was very elegant), and the ones you sent separately with regards to enabling tests. Thanks, did you push your latest changes to the Alioth repository? FYI, #881765 should also be fixed. @anbe, once yapf 0.19.0-1 is cleared from new, you might want to use this version for the backports if that's possible. Cheers, Ghis
Bug#880958: yapf3 explicitly depends on python3.5
What about the patches fixing the other two bugs affecting yapf? Please consider checking the BTS. Ghis Le 14 nov. 2017 22:25, "Ana C. Custura" <a...@netstat.org.uk> a écrit : Hi Ghis, Thank you for the reply. There is a package on mentors that addresses both this bug (88958) and the split (879196) bug you raised. I am waiting for my mentor to review it before uploading. Ana On Tue, Nov 14, 2017, at 08:59 AM, Ghislain Vaillant wrote: > Thank you Matthias for raising this issue. CC'ing the maintainer in case > she's not subscribed. > > On Mon, 6 Nov 2017 11:52:00 +0100 Matthias Klose <d...@debian.org> wrote: > > Package: yapf3 > > Version: 0.17.0-1 > > Severity: serious > > Tags: sid buster > > > > yapf3 explicitly depends on python3.5. One mistake certainly is the b-d on > > python3-all, which is wrong for an application-only package. > > The application is not compliant with the Python packaging guidelines. > The public modules should be split from the application package. See > #879196 for a discussion about it. > > I have proposed a patch offline but it has yet to be applied. Fixing > #879196 will transitively fix the issue you just reported. > > > And if this package is application-only, why ship both Python2 and Python3 vesions? > > It is nether application-only, nor Python 3 specific. > > Cheers, > Ghis
Bug#879196: patch attached
Here is a patch implementing the proposed split. >From 37a9eaf8b03aebd4eb6839280aee68cbd48d68b4 Mon Sep 17 00:00:00 2001 From: Ghislain Antony Vaillant <ghisv...@gmail.com> Date: Tue, 14 Nov 2017 09:24:42 + Subject: [PATCH] Ship the modules in separate binary packages Gbp-Dch: Short Thanks: Matthias Klose for reporting Closes: #879196, #880958 --- debian/control | 50 +++--- debian/rules | 18 +- 2 files changed, 48 insertions(+), 20 deletions(-) diff --git a/debian/control b/debian/control index 21120f5..facb68c 100644 --- a/debian/control +++ b/debian/control @@ -1,5 +1,5 @@ Source: yapf -Section: python +Section: utils Priority: optional Maintainer: Ana Custura <a...@netstat.org.uk> Build-Depends: debhelper (>=9),dh-python,python-all,python-setuptools,python3-all,python3-setuptools @@ -12,20 +12,56 @@ Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/yapf.git Package: yapf Architecture: all -Depends: ${python:Depends}, ${misc:Depends} +Depends: ${misc:Depends}, + ${python:Depends}, + python-yapf Description: Python code formatter for different styles (Python 2) Yapf is a tool that reformats code to the best formatting that conforms to the style guide. It is not only concerned with lint errors, but also with the styilistic appearance of Python code. The idea is also similar to the 'gofmt' - tool for the Go programming language. This package installs the tool for Python - 2. + tool for the Go programming language. + . + This package provides the command-line interface for Python 2. + +Package: python-yapf +Architecture: all +Section: python +Depends: ${misc:Depends}, + ${python:Depends} +Breaks: yapf (<< 0.17.0-2) +Replaces: yapf (<< 0.17.0-2) +Description: public modules for yapf (Python 2) + Yapf is a tool that reformats code to the best formatting that conforms to the + style guide. It is not only concerned with lint errors, but also with the + styilistic appearance of Python code. The idea is also similar to the 'gofmt' + tool for the Go programming language. + . + This package provides the modules for Python 2. Package: yapf3 Architecture: all -Depends: ${python3:Depends}, ${misc:Depends} +Depends: ${misc:Depends}, + ${python3:Depends}, + python3-yapf Description: Python code formatter for different styles (Python 3) Yapf is a tool that reformats code to the best formatting that conforms to the style guide. It is not only concerned with lint errors, but also with the styilistic appearance of Python code. The idea is also similar to the 'gofmt' - tool for the Go programming language. This package installs the tool for Python - 3. + tool for the Go programming language. + . + This package provides the command-line interface for Python 3. + +Package: python3-yapf +Architecture: all +Section: python +Depends: ${misc:Depends}, + ${python3:Depends} +Breaks: yapf3 (<< 0.17.0-2) +Replaces: yapf3 (<< 0.17.0-2) +Description: public modules for yapf (Python 3) + Yapf is a tool that reformats code to the best formatting that conforms to the + style guide. It is not only concerned with lint errors, but also with the + styilistic appearance of Python code. The idea is also similar to the 'gofmt' + tool for the Go programming language. + . + This package provides the modules for Python 3. diff --git a/debian/rules b/debian/rules index 420e98a..675be8c 100755 --- a/debian/rules +++ b/debian/rules @@ -5,22 +5,14 @@ PYVERS=$(shell pyversions -sv) PY3VERS=$(shell py3versions -sv) export PYBUILD_NAME=yapf +export PYBUILD_DESTDIR_python2=debian/python-${PYBUILD_NAME} +export PYBUILD_DESTDIR_python3=debian/python3-${PYBUILD_NAME} %: dh $@ --with python2,python3 --buildsystem=pybuild override_dh_auto_install: dh_auto_install - - set -e && for pyvers in $(PYVERS); do \ -python$$pyvers setup.py install --install-layout=deb \ ---root $(CURDIR)/debian/yapf; \ -done - - set -e && for pyvers in $(PY3VERS); do \ -python$$pyvers setup.py install --install-layout=deb \ ---root $(CURDIR)/debian/yapf3; \ -done - - mv $(CURDIR)/debian/yapf3/usr/bin/yapf $(CURDIR)/debian/yapf3/usr/bin/yapf3 - + dh_movefiles --package=yapf --sourcedir=$(PYBUILD_DESTDIR_python2) usr/bin + dh_movefiles --package=yapf3 --sourcedir=$(PYBUILD_DESTDIR_python3) usr/bin + (cd $(CURDIR)/debian/yapf3 && mv ./usr/bin/yapf ./usr/bin/yapf3) -- 2.14.1
Bug#877701: patch attached
Here is a patch removing the confusing section from the manpage. >From cf7d5826bb9a17c68403f81ba9c9b346497c9c70 Mon Sep 17 00:00:00 2001 From: Ghislain Antony Vaillant <ghisv...@gmail.com> Date: Tue, 14 Nov 2017 09:17:09 + Subject: [PATCH] Remove confusing SEE ALSO section in manpages Gbp-Dch: Short Thanks: Matthias Urlichs for reporting Closes: #877701 --- debian/yapf.1 | 2 -- debian/yapf3.1 | 2 -- 2 files changed, 4 deletions(-) diff --git a/debian/yapf.1 b/debian/yapf.1 index dccfae6..66c774d 100644 --- a/debian/yapf.1 +++ b/debian/yapf.1 @@ -48,5 +48,3 @@ don't search for local style definition (.style.yapf) .IP [\-\-style STYLE] [\-\-style\-help] [\-\-no\-local\-style] [files [files ...]] -.SH "SEE ALSO" -More detailed information can be found in the html files in /usr/local/share/doc/yapf diff --git a/debian/yapf3.1 b/debian/yapf3.1 index 68f9dd7..e68dc72 100644 --- a/debian/yapf3.1 +++ b/debian/yapf3.1 @@ -48,5 +48,3 @@ don't search for local style definition (.style.yapf3) .IP [\-\-style STYLE] [\-\-style\-help] [\-\-no\-local\-style] [files [files ...]] -.SH "SEE ALSO" -More detailed information can be found in the html files in /usr/local/share/doc/yapf3 -- 2.14.1
Bug#880958: yapf3 explicitly depends on python3.5
Thank you Matthias for raising this issue. CC'ing the maintainer in case she's not subscribed. On Mon, 6 Nov 2017 11:52:00 +0100 Matthias Klosewrote: Package: yapf3 Version: 0.17.0-1 Severity: serious Tags: sid buster yapf3 explicitly depends on python3.5. One mistake certainly is the b-d on python3-all, which is wrong for an application-only package. The application is not compliant with the Python packaging guidelines. The public modules should be split from the application package. See #879196 for a discussion about it. I have proposed a patch offline but it has yet to be applied. Fixing #879196 will transitively fix the issue you just reported. And if this package is application-only, why ship both Python2 and Python3 vesions? It is nether application-only, nor Python 3 specific. Cheers, Ghis
Bug#881604: src:mypy: New upstream release
Package: src:mypy Severity: wishlist Control: block -1 by 881602 The update of mypy to the latest upstream version (0.550) requires a newer version of psutil (>=5.4, <5.5). A request for updating src:python-psutil has already been filed. Regards, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#881602: src:python-psutil: New upstream release
Package: src:python-psutil Severity: wishlist Dear Maintainer, The latest version of mypy (0.550) now depends on a newer version of psutil (>=5.4, <5.5). Please consider updating the packaging with a suitable version. The latest version of psutil is 5.4.1 at this time. Regards, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#881199: RFS: python-coloredlogs/7.3-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: coloredlogs Version : 7.3-1 Upstream Author : Peter Odding* URL : https://coloredlogs.readthedocs.io * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/cgit/python-modules/packages/python-coloredlogs.git Changes since the last upload: * New upstream version 7.3 * Bump the standards version to 4.1.1 * Add recommended get-orig-source target Best regards, Ghis
Bug#881054: libarrayfire-opencl3: "INTERNAL KERNEL BUILD ERROR" from af::matmulTN
Hi Ralf, Based on the content of your report, you are suggesting that the latest version (3.5.1 at this very time) would solve the issue you are experiencing, am I correct? Cheers, Ghis
Bug#880729: RFS: python-parameterized/0.6.1-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-parameterized Version : 0.6.1-2 Upstream Author : David Wolever * URL : https://github.com/wolever/parameterized * License : BSD Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/cgit/python-modules/packages/python-parameterized.git Changes since the last upload: * Fix debci failures due to a buggy test - New patch Remove-unicode-docstring-test.patch * Fixup the Vcs-Browser URI * Remove superfluous nocheck guards * Add recommended get-orig-source target * Bump the standards version to 4.1.1 Best regards, Ghis
Bug#880678: src:bottleneck: Transfer package maintenance to the DPMT
Package: src:bottleneck Severity: wishlist Hi Pietro, Could you acknowledge your agreement to this request, which we discussed offline some time ago. This way I can make it official by closing this bug in the next entry of the change log. Thanks, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#880679: src:bottleneck: Relicense debianization to compatible terms with upstream
Package: src:bottleneck Severity: wishlist Hi Pietro, Could you acknowledge your agreement to this request, which we discussed offline some time ago. This way I can make it official by closing this bug in the next entry of the change log. Thanks, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#880577: RFS: shark/3.1.4+ds1-1 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for the following package: * Package name: shark Version : 3.1.4+ds1-1 Upstream Author : Christian Igel* URL : http://image.diku.dk/shark/ * License : LGPL-3 Section : science Please check out the package by visiting the following URL: https://anonscm.debian.org/cgit/debian-science/packages/shark.git Changes since the last upload: * New upstream version 3.1.4+ds1 (Closes: #853658) * Add missing Built-Using metadata for the docs * Add support for the nodoc build profile * Build the docs with Python 3 * Bump the standards version to 4.1.1 Regards, Ghis
Bug#880443: RFS: spyder-reports/0.1.1-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for the following package: * Package name: spyder-reports Version : 0.1.1-1 Upstream Author : Spyder Project Contributors * URL : https://github.com/spyder-ide/spyder-reports * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/cgit/debian-science/packages/spyder-reports.git Changes since the last upload: * Initial release. (Closes: #872534) Regards, Ghis
Bug#880442: RFS: python-jsonrpc/1.10.3-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for the following package: * Package name: python-jsonrpc Version : 1.10.3-1 Upstream Author : Kirill Pavlov* URL : https://github.com/pavlov99/json-rpc * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/cgit/python-modules/packages/python-jsonrpc.git Changes since the last upload: * Initial release. (Closes: #879050) Regards, Ghis
Bug#880412: RFS: python-h5netcdf/0.5.0-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-h5netcdf Version : 0.5.0-1 Upstream Author : Stephan Hoyer* URL : https://github.com/shoyer/h5netcdf * License : BSD Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-h5netcdf.git Changes since the last upload: * New upstream version 0.5.0 * Add recommended get-orig-source target Regards, Ghis
Bug#880408: RFS: python-pymeasure/0.5-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-pymeasure Version : 0.5-1 Upstream Author : PyMeasure Developers * URL : https://github.com/ralph-group/pymeasure * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-pymeasure.git Changes since last upload: * New upstream version 0.5 * Refresh the patch queue * Bump the standards version to 4.1.1 * Add recommended get-orig-source target Regards, Ghis
Bug#880406: RFS: python-bayespy/0.5.12-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-bayespy Version : 0.5.12-1 Upstream Author : Jaakko Luttinen* URL : https://www.bayespy.org * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-bayespy.git Changes since the last upload: * New upstream version 0.5.12 * Bump the standards version to 4.1.1 * Add recommended get-orig-source target Regards, Ghis
Bug#880405: RFS: python-meshio/1.8.17-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-meshio Version : 1.8.17-1 Upstream Author : Nico Schlömer * URL : https://github.com/nschloe/meshio * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-meshio.git Changes since last upload: * New upstream version 1.8.17 * Bump the standards version to 4.1.1 Regards, Ghis
Bug#880402: src:python-prov: New upstream release (version 1.5.1)
Package: src:python-prov Severity: wishlist Control: block -1 by 868857 New versions of python-prov requires pydot with a minimum version of 1.2.0 for testing. A wishlist bug to update src:pydot has already been filed. -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#879611: src:backintime: Switch graphical backend to PyQt5
Package: src:backintime Severity: wishlist Dear Maintainer, PyQt4 is planned for removal for the Buster release cycle [1]. It would be wise to consider switching the backend of backintime from PyQt4 to PyQt5 whenever possible. It might not be possible for the 1.1.x series, but it will definitely be possible in 1.2.x according to the README in the master branch [2]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875109 [2] https://github.com/bit-team/backintime/blob/master/README.md Best regards, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#879609: src:backintime: New upstream release
Package: src:backintime Severity: wishlist Dear Maintainer, A new release of backintime is available (1.1.20). Since the current version (1.1.12), a number of bug fixes have been backported from the 1.2.x branch, including CVE-2017-7572. Also, perhaps this new release would be a good opportunity to switch the graphical backend from Qt4 to Qt5. PyQt4 is planned for removal for the Buster release cycle [1]. I'll file a different bug for that. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875109 Best regards, Ghis -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500, 'artful-updates'), (500, 'artful') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-16-generic (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)