Your message dated Sat, 17 Aug 2019 16:21:51 +0000 with message-id <e1hz1sh-000aoz...@fasolo.debian.org> and subject line Bug#907636: fixed in opam 2.0.5-1 has caused the Debian Bug report #907636, regarding opam: "opam init" calls gringo that requires 3GB of memory to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: opam Version: 2.0.0-1 Severity: normal Dear Maintainer, I ran "opam init" on my little machine that has only 2GB of RAM and had to kill it after gringo had gobbled all the available memory. I just tried on a bigger computer to see that it peaks at 3 or 4GB, making it unusable on small machines. I wondered why, and how to mitigate this: maybe gringo is not the best default choice for the chain of dependencies (opam -> aspcud -> gringo) in opam's case? Is it a bug in opam 2 (I had not noticed a problem with the previous version), giving a terrible problem to solve to aspcud? Best regards, Samuel -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 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 opam depends on: ii aspcud 1:1.9.4-1 ii build-essential 12.5 ii curl 7.61.0-1 ii libbz2-1.0 1.0.6-9 ii libc6 2.27-5 ii opam-docs 2.0.0-1 ii opam-installer 2.0.0-1 ii packup 0.6-3 ii unzip 6.0-21 ii wget 1.19.5-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages opam recommends: ii darcs 2.14.0-1 ii git 1:2.19.0~rc1-1 ii m4 1.4.18-1 ii mercurial 4.7-1 ii ocaml 4.05.0-10+b1 ii rsync 3.1.2-2.2 opam suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Source: opam Source-Version: 2.0.5-1 We believe that the bug you reported is fixed in the latest version of opam, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 907...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Braud-Santoni <ni...@debian.org> (supplier of updated opam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 17 Aug 2019 17:37:02 +0200 Source: opam Architecture: source Version: 2.0.5-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org> Changed-By: Nicolas Braud-Santoni <ni...@debian.org> Closes: 907636 908203 Changes: opam (2.0.5-1) unstable; urgency=medium . * New upstream version 2.0.5 + Forward-compatibility improvements (OCaml 4.08, Dune 1.7 and later, ...) + Numerous bugfixes + Patch typos + Fixup opam's version number in debian/rules Upstream's tarball has the wrong version number set. . * Build OPAM with its internal solver; add dependency on ocaml-mccs. * Remove dependency on external CUDF solvers. (Closes: #908203, #907636) * Add basic autopkgtest (opam init && opam install some packages) This is sufficient to catch #907636 . * opam: Replace {pre,post}* scripts with a declarative maintscript * Switch to debhelper 12, remove the old-style debian/compat. This is because dh's compatibility level 12 hard-errors on maintscript issues. dh 12 is available in stretch-backports, buster, and later. . * debian/control: Remove unnecessary dependencies * Update authorship information (dates, email, ...) * Declare compliance with policy 4.4.0 * Override spurious Lintian warnings Checksums-Sha1: b8c5c65910aec1d9c949fbcb9a3ea367c34b50e8 2509 opam_2.0.5-1.dsc f442c6d927791bc22b6f9fa709062383658240b4 619527 opam_2.0.5.orig.tar.gz 544af909b1851068a2874d93dcb5d66fef9ac447 8352 opam_2.0.5-1.debian.tar.xz 36f215899f22898257baeb46ff835c876886c520 12079 opam_2.0.5-1_amd64.buildinfo Checksums-Sha256: 191e6762aafdf2ae43cb182c319cde4f4d6cf132bcd579529d100f9eda8e1466 2509 opam_2.0.5-1.dsc 9432111732bea1610e284e8ad04489d1a2a9fab81437f5b23bdffdb08afacb82 619527 opam_2.0.5.orig.tar.gz 10b564288a22d8dcf9bf0605ecf274692ca73e0cbab827047b26688b993cb6d5 8352 opam_2.0.5-1.debian.tar.xz f8d997ccf52b2559c0e716cbaa8acd916988938e4b64f731b3d71507288f2cd0 12079 opam_2.0.5-1_amd64.buildinfo Files: 10a03430abb3792bcca3344101d5fde2 2509 ocaml optional opam_2.0.5-1.dsc f86e4330020b6a0e724344ebb04fd73a 619527 ocaml optional opam_2.0.5.orig.tar.gz 31646f9ae253648f293f723a6794e6a2 8352 ocaml optional opam_2.0.5-1.debian.tar.xz 840804fef7e5bc79098ede44df4cd3a2 12079 ocaml optional opam_2.0.5-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAl1YIG8ACgkQ5vmO4pLV 7MsFjA/+KecBPRwEYIkOkfKCTgsFxhOqe7Z8wYr2/1YfR5ldAV1F/zE4VoxGh3mz C1c5T75qgExpz+CaieoOH5GrVP54STUJLtZjShMHKXAwPhtqvVKn6DC8G80vsTJA IaMI18bTlIYD+1INtXo8IexpOsvthSjh/3AIBKSsdCn7VlJQCNXUDjqOAgDH9WYR XcauSwbQQEApF0MTddkRuNKBa7q4q6U0Pi7Utek/kR9sq56565o5m3FE6NLRXszq cu2ViuADkSSJyvqHIej9/jC46K8yZ9n2/VjX58K+HwUkaoPKXw12MFfhAfjRbXds AlJS+Q9TBSVWlW3WJhp4Q3/FHoefIvifGsw5bJLQUPrsLBOC7OneOWR00d+ga7tY VZNtOwVkgWYs9Niy1qad0Ge/SKFNRbeV/S4lDBjA6qPNqsozHasHfDXF18+4h7SY ooJjpxS5J01r6NCmJn/sRHqMIDTgiCtPxybl/C+mD9pzR8iF5mMaLNMzuW08joNE Pi6hcUoBsDG1Hr9Fs7RojTF0bDvXLqKQgC7HzyUW4/faugR6EU6nBo3ihB06ux/Y V3iumeX1NdXNGyQl9c7s0uGg9ziAX2Qj+stkVakASrFsiWS70Bc58ojg9U6Ct/fn s8vQWl+HLQwk40O10MyLis7R7d2RGB+fBAg6jySBrUo9G/1Vjmw= =SD5R -----END PGP SIGNATURE-----
--- End Message ---
