Re: Versioned dependencies and maintainer scripts
On Mon, Jun 25, 2018 at 11:10:51AM -0600, Daniele Nicolodi wrote: >... > On 6/25/18 1:04 AM, Simon McVittie wrote: >... > > For the postinst, you can rely on the updated init-system-helpers being > > at least unpacked (which should be enough, because i-s-h is Essential, > > so it's required to provide its core functionality while merely unpacked > > and not yet configured). > > > > The difference for Pre-Depends is that it would give you the ability to > > assume that i-s-h has been configured (fully installed) before your > > postinst runs. I don't think you need that here. > > > > In the postrm, you can't normally rely on having your package's > > dependencies still installed, but init-system-helpers is Essential so > > it should still be there, and we don't officially support downgrades so > > i-s-h should still be at least the required version. > > Only tangentially related: does that mean that we can drop the checks > for the presence of deb-systemd-helper in the postrm maintainer scripts > injected by dh_installsystemd (for example [1]) and simplify them a bit? >... "purge" might happen decades (sic) after "remove" with no dependencies installed and packages that are essential today no longer being essential. > Cheers, > Dan >... cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Re: Mass filing on Python 3.7 async module import?
On 08/07/18 00:17, Paul R. Tagliamonte wrote: > Hey DPMT (BCC'ing -devel, let's keep conversaion on DPMT), > > I see that Python 3.7 now raises a syntax error when you try to import > a module that is named `async`. > > ``` > $ python3.6 > Python 3.6.6 (default, Jun 27 2018, 14:44:17) > [GCC 8.1.0] on linux > Type "help", "copyright", "credits" or "license" for more information. import foo.async > Traceback (most recent call last): > File "", line 1, in > ModuleNotFoundError: No module named 'foo' > ``` > > With Python 3.7: > > ``` > $ python3.7 > Python 3.7.0 (default, Jun 27 2018, 14:40:03) > [GCC 8.1.0] on linux > Type "help", "copyright", "credits" or "license" for more information. import foo.async > File "", line 1 > import foo.async >^ > SyntaxError: invalid syntax > ``` > > Quickly checking codesearch, there are a bunch of packages that have > import lines that look like they'd fail. > > Anyone mind if I do a MBF on libraries that are providing anything > named `async.py`? List of affected packages: openscap-daemon: /usr/lib/python3/dist-packages/openscap_daemon/async.py pylint3: /usr/lib/python3/dist-packages/pylint/checkers/async.py python3-astroquery: /usr/lib/python3/dist-packages/astroquery/vo_conesearch/async.py python3-celery: /usr/lib/python3/dist-packages/celery/backends/async.py python3-dropbox: /usr/lib/python3/dist-packages/dropbox/async.py python3-exabgp: /usr/lib/python3/dist-packages/exabgp/reactor/async.py python3-gunicorn: /usr/lib/python3/dist-packages/gunicorn/workers/async.py python3-ldap: /usr/lib/python3/dist-packages/ldap/async.py python3-mapproxy: /usr/lib/python3/dist-packages/mapproxy/util/async.py python3-opengl: /usr/lib/python3/dist-packages/OpenGL/GL/SGIX/async.py python3-opengl: /usr/lib/python3/dist-packages/OpenGL/raw/GL/SGIX/async.py python3-pexpect: /usr/lib/python3/dist-packages/pexpect/async.py python3-pylama: /usr/lib/python3/dist-packages/pylama/async.py python3-pymodbus: /usr/lib/python3/dist-packages/pymodbus/client/async.py python3-pymodbus: /usr/lib/python3/dist-packages/pymodbus/server/async.py python3-raven: /usr/lib/python3/dist-packages/raven/contrib/async.py python3-rpyc: /usr/lib/python3/dist-packages/rpyc/core/async.py python3-tenacity: /usr/lib/python3/dist-packages/tenacity/async.py salt-common: /usr/lib/python3/dist-packages/salt/utils/async.py visidata: /usr/lib/python3/dist-packages/visidata/async.py and the dd-list: Andriy Senkovych salt (U) Anja Boskovic visidata Bas Couwenberg mapproxy (U) Benjamin Drung salt (U) Brian May celery (U) Carl Suster rpyc (U) ChangZhuo Chen (陳昌倬) pylama (U) Chris Lamb gunicorn Debian Astro Team astroquery Debian GIS Project mapproxy Debian Python Modules Team celery pexpect pylama pymodbus pyopengl python-dropbox python-ldap python-raven (U) python-tenacity rpyc Debian Salt Team salt Debian Security Tools openscap-daemon Franklin G Mendoza salt (U) Joe Healy salt (U) Maximiliano Curia pymodbus (U) Michael Fladischer celery (U) python-dropbox (U) Ondřej Kobližek python-tenacity (U) Ondřej Nový python-tenacity (U) salt (U) Philippe Thierry openscap-daemon (U) Python Applications Packaging Team pylint (U) Sandro Tosi pylint Thomas Goirand python-tenacity (U) Tobias Hansen pexpect (U) Torsten Marek pyopengl (U) Vincent Bernat exabgp python-raven Vincent Prat astroquery (U) W. Martin Borgert pymodbus (U) Willem van den Akker python-ldap (U) Wolodja Wentland salt (U) Cheers, Emilio
SALSA migration of XML/SGML packages (sgml-data for me)
Hi, I am wondering what is happening with XML/SGML packages. I am doing SALSA migration and I realized I need to RFA or Orphan some of my packages. Specifically: sgml-data debiandoc-sgml debiandoc-sgml-doc debiandoc-sgml-pt-br All debiandoc-sgml* packages can be almost safely set to Orphan path. (Maybe not for buster but after buster. Debian Policy doesn't use this any more. I will take care them if needed.) But sgml-data has too many packages depending on it and it is best to hand this package to a right person. This sgml-data is SGML package so it is most appropriate to be taken care by people who were on Debian XML/SGML Group . I think this is unreachable email address by now. Listing this as maintainer address may be RC bug. That is why I am writing to debian-devel@lists.debian.org while CCing recent uploaders of these packages to be sure. Many important packages list this email address. https://qa.debian.org/developer.php?email=debian-xml-sgml-pkgs%40lists.alioth.debian.org libxml2 libxslt docbook-utils ... Some of them still list old alioth VCS URL. Does anyone working on moving these repo to SALSA and uploading properly updated packages with reachable group address? FYI: I created SALSA repo for sgml-data https://salsa.debian.org/debian/sgml-data Osamu PS: - DATA $ build-rdeps debiandoc-sgml Reverse Build-depends in main: -- backup-manager cli-common dbconfig-common debian-faq debian-history debian-installer debiandoc-sgml-doc debiandoc-sgml-doc-pt-br dh-kpatches doc-debian-fr focalinux gap java-policy junior-doc libnss-pgsql menu sgml-base-doc tcltk-defaults userv Found a total of 19 reverse build-depend(s) for debiandoc-sgml. $ build-rdeps sgml-data Reverse Build-depends in main: -- a2ps aafigure abcm2ps aboot accountsservice ace aconnectgui adcli aes2501-wy aisleriot akonadi-calendar akonadi-calendar-tools akonadi-import-wizard akonadiconsole akregator alex alsa-utils alsamixergui altermime altos amarok ... (over 1000 packages)
Re: SALSA migration of XML/SGML packages (sgml-data for me)
[dropping individual email addresses] Osamu Aoki 于2018年7月8日周日 下午10:21写道： > > Hi, > > I am wondering what is happening with XML/SGML packages. > > I am doing SALSA migration and I realized I need to RFA or Orphan some > of my packages. Specifically: > > sgml-data > debiandoc-sgml > debiandoc-sgml-doc > debiandoc-sgml-pt-br > > All debiandoc-sgml* packages can be almost safely set to Orphan path. > (Maybe not for buster but after buster. Debian Policy doesn't use this > any more. I will take care them if needed.) > > But sgml-data has too many packages depending on it and it is best to > hand this package to a right person. > > This sgml-data is SGML package so it is most appropriate to be taken > care by people who were on Debian XML/SGML Group > . I think this is > unreachable email address by now. Listing this as maintainer address > may be RC bug. That is why I am writing to > debian-devel@lists.debian.org while CCing recent uploaders of these > packages to be sure. Many important packages list this email address. I remember that the whole Debian XML/SGML Group is already dead with the last member retiring several years ago. I can't find the retirement email now but that did happen before. I believe those infrastracture really needs some caring. -- Regards, Boyuan Yang
Re: SALSA migration of XML/SGML packages (sgml-data for me)
On Sun, Jul 08, 2018 at 11:20:57PM +0900, Osamu Aoki wrote: > I am wondering what is happening with XML/SGML packages. The group is now on salsa at: https://salsa.debian.org/xml-sgml-team and not all packages are abandoned, thought several are. > This sgml-data is SGML package so it is most appropriate to be taken > care by people who were on Debian XML/SGML Group > . I think this is > unreachable email address by now. You think wrong, as that mail address has been migrated on the temporary server on alioth-lists.debian.net, together with all the others (although I believe most of them should have been archived away, and move to use a team+foo@tracker.d.o address). > Does anyone working on moving these repo to SALSA and uploading properly > updated packages with reachable group address? If you checked DDPO as you said, and noticed that *some* are on alioth, you must also have noticed that the others are already on salsa… https://salsa.debian.org/groups/xml-sgml-team/-/group_members I added you to the team now. > FYI: I created SALSA repo for sgml-data > https://salsa.debian.org/debian/sgml-data I'd consider asking the salsa admin to move it under the team namespace, unless you think it would be best under /debian/, of course. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Re: SALSA migration of XML/SGML packages (sgml-data for me)
On Sun, Jul 08, 2018 at 11:20:57PM +0900, Osamu Aoki wrote: > Hi, > > I am wondering what is happening with XML/SGML packages. > > I am doing SALSA migration and I realized I need to RFA or Orphan some > of my packages. Specifically: > > sgml-data > debiandoc-sgml > debiandoc-sgml-doc > debiandoc-sgml-pt-br > > All debiandoc-sgml* packages can be almost safely set to Orphan path. > (Maybe not for buster but after buster. Debian Policy doesn't use this > any more. I will take care them if needed.) > > But sgml-data has too many packages depending on it and it is best to > hand this package to a right person. RFA sounds appropriate for that, and you can also state in the RFA bug that anyone intending to adopt it should contact you first. This being SGML the most likely result would be noone adopting it, and you could then retitle the WNPP bugs to O later. How many packages do actually use sgml-data? translate-docformat depends on it, but I'd assume/hope most actual users no longer use SGML. docbook-xml (sic) depends on sgml-data and sgml-base. All this gives sgml-base impressive popcon numbers, but the actual usage is likely pretty limited. I'm sure we have users who still need tooling for SGML, but all this is now more a fringe area of the archive. > This sgml-data is SGML package so it is most appropriate to be taken > care by people who were on Debian XML/SGML Group > . I think this is > unreachable email address by now. Listing this as maintainer address > may be RC bug. That is why I am writing to > debian-devel@lists.debian.org while CCing recent uploaders of these > packages to be sure. >... Someone took care of that, the list was migrated and is still reachable: https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-xml-sgml-pkgs cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#903345: ITP: python-seqcluster -- analysis of small RNA in NGS data
Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: python-seqcluster * URL : https://github.com/lpantano/seqcluster * License : MIT Programming Lang: Python Description : analysis of small RNA in NGS data About to appear at https://salsa.debian.org/med-team/python-seqcluster
Bug#903371: ITP: ocaml-qcheck -- QuickCheck inspired property-based testing for OCaml
Package: wnpp Severity: wishlist Owner: Andy Li -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: ocaml-qcheck Version : 0.8 Upstream Author : Simon Cruanes Rudi Grinberg Jacques-Pascal Deplaix Jan Midtgaard * URL : https://github.com/c-cube/qcheck * License : BSD Programming Lang: OCaml Description : QuickCheck inspired property-based testing for OCaml This module allows to check invariants (properties of some types) over randomly generated instances of the type. It provides combinators for generating instances and printing them. This is one of the dependencies of the next version of Haxe (4.0.0). -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJbQtJ5AAoJENYPsCrEEWxpQp4H/RzEQbLn54kzqCmwbpZLWcI1 U/ygzXbw8BXKtmisOm209gEnCVi265cuidbxRt9WPT8bxlNJb270/KUU0r4W0+Xd sa90yYBVwRM/esWcrklTSkQBUCp0oVGMv5vVkEuw95i3OKJtS+ENuAox6Mj49l7X EcdiQZ2vkrXBfq2NHVLT4wwLmnXhcau2xFJyAfMiL/Jqw3jhemu9oYJwc+pnrE83 LryrYt5s1c75hYySH2ZJiPrUmSotpeu2/1Ol3Tq0LElTEnMUwMMYe+09jTdqe82t Rm1llmd0bWm6XElApArThzWnXsFcSBcTcy4cjLuIsqBcx7H79C4z8gsn1QgF2T0= =n5Qp -END PGP SIGNATURE-
Research survey: Impact of Microsoft Acquisition of GitHub
Dear Debian developers, I am Natnaree Asavaseri and currently undertaking a research internship at Nara Institute of Science and Technology, Japan. Note that we are not biased to either GitHub or Microsoft, and this is purely from an empirical research perspective. As a part of my research in the field of Software Engineering (SE), my professors and I are analyzing the impact of Microsoft's acquisition of GitHub. The main purpose of my survey is understanding how developers perceive the Microsoft's acquisition of GitHub, especially from contributors to Linux distributions and BSD families. If the survey is successful, we will publish our findings at SE academic venues (journals or conference). So please consider voicing your opinion by allowing us up to 5 minutes to complete my short survey. https://goo.gl/forms/lbIL5qsinDRQyTaK2 We would like to remind you that participation in this survey is completely voluntary and your identity is hidden for anonymity. Thank you for your time in advance. Best regards, Natnaree (cc Shade, Raula, Hideaki) Nara Institute of Science and Technology, Japan
