From ipmplant at gmail.com Mon Jun 1 14:52:14 2020 From: ipmplant at gmail.com (=?euc-kr?B?ZGVubnloYW4=?=) Date: Mon, 01 Jun 2020 22:52:14 +0900 Subject: [Pkg-zsh-devel] =?euc-kr?q?_=28AD=29_OSANG_HEALTHCARE_=2E=2C_ltd_?= =?euc-kr?q?COVID-19_diagnostic_kit!?= Message-ID: <202006012252149917@send106.postman.co.kr> An HTML attachment was scrubbed... URL: From contato at kasat.com.br Mon Jun 1 23:51:15 2020 From: contato at kasat.com.br (Douglas McGregor) Date: Mon, 01 Jun 2020 15:51:15 -0700 Subject: [Pkg-zsh-devel] Is this email still active? Message-ID: I have been trying to reach you, is this email still active? I have something important to discuss with you. Please get back to me as soon as you can. A. Douglas McGregor From vincent at vinc17.net Wed Jun 3 16:21:31 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 17:21:31 +0200 Subject: [Pkg-zsh-devel] Bug#962133: zsh-common: missing package in "dpkg -s" completion Message-ID: <20200603152131.GA3497045@zira.vinc17.org> Package: zsh-common Version: 5.8-4 Severity: normal The package libplacebo7 is installed, but "dpkg -s" completion does not propose it: zira:~> dpkg -s libplacebo7 Package: libplacebo7 Status: purge ok installed Priority: optional Section: libs Installed-Size: 2332 Maintainer: Debian Multimedia Maintainers Architecture: amd64 Multi-Arch: same Source: libplacebo Version: 1.7.0-2 [...] zira:~> dpkg -s libpl[TAB] Completing package libplack-perl libplexus-interpolation-java libplexus-archiver-java libplexus-io-java libplexus-cipher-java libplexus-sec-dispatcher-java libplexus-classworlds-java libplexus-utils2-java libplexus-component-annotations-java libplot2c2:amd64 According to "dpkg -s [TAB]", it seems to be the only missing package. I don't know what is particular with it, except that it is marked to be purged. But it is not purged yet, so that there is no reason to take that into account. -- Package-specific info: Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-======================================================= ii curl 7.68.0-1 amd64 command line tool for transferring data with URL syntax ii pass 1.7.3-2 all lightweight directory-based password manager ii pulseaudio 13.0-5 amd64 PulseAudio sound server ii qpdf 10.0.1-2 amd64 tools for transforming and inspecting PDF files ii systemd 245.5-3 amd64 system and service manager ii udev 245.5-3 amd64 /dev/ and hotplug management daemon ii vlc-bin 3.0.10-1 amd64 binaries from VLC ii youtube-dl 2020.05.08-1 all downloader of videos from YouTube and other sites The following files were modified: /etc/systemd/system.conf /etc/systemd/logind.conf /etc/systemd/journald.conf dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled zsh-common depends on no packages. Versions of packages zsh-common recommends: ii zsh 5.8-4 Versions of packages zsh-common suggests: ii zsh-doc 5.8-4 -- no debconf information -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Wed Jun 3 16:32:13 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 17:32:13 +0200 Subject: [Pkg-zsh-devel] Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603152131.GA3497045@zira.vinc17.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603153213.GM367472@zira.vinc17.org> Actually there's another one: zira:~> dpkg -l | grep '^rc' rc openntpd 1:6.0p1-1 amd64 OpenBSD NTP daemon zira:~> dpkg -s openntpd Package: openntpd Status: deinstall ok config-files Priority: optional Section: net [...] but "dpkg -s openn[TAB]" does not give any completion. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From abe at debian.org Wed Jun 3 16:34:44 2020 From: abe at debian.org (Axel Beckert) Date: Wed, 3 Jun 2020 17:34:44 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603152131.GA3497045@zira.vinc17.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603153440.xd35ahadjnx7dujd@sym.noone.org> Hi, Vincent Lefevre wrote: > The package libplacebo7 is installed, but "dpkg -s" completion does > not propose it: [...] > According to "dpkg -s [TAB]", it seems to be the only missing package. > I don't know what is particular with it, except that it is marked to > be purged. "marked to be purged" in which application? Aptitude? > But it is not purged yet, so that there is no reason to > take that into account. I wonder if this could also be related to the fact that libplacebo7 is currently no more in Debian Unstable, just in Debian Testing: → apt-cache policy libplacebo7 libplacebo7: Installed: (none) Candidate: 1.7.0-2 Version table: 1.7.0-2 600 600 https://debian.ethz.ch/debian testing/main amd64 Packages Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From vincent at vinc17.net Wed Jun 3 16:45:00 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 17:45:00 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603153440.xd35ahadjnx7dujd@sym.noone.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603153440.xd35ahadjnx7dujd@sym.noone.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603154500.GN367472@zira.vinc17.org> On 2020-06-03 17:34:44 +0200, Axel Beckert wrote: > Vincent Lefevre wrote: > > The package libplacebo7 is installed, but "dpkg -s" completion does > > not propose it: > [...] > > According to "dpkg -s [TAB]", it seems to be the only missing package. > > I don't know what is particular with it, except that it is marked to > > be purged. > > "marked to be purged" in which application? Aptitude? Yes, aptitude: before completing the upgrade (at the apt-listchanges step), I wanted to have a look at the package description. But this is not local to aptitude: aptitude just tells dpkg that the package needs to be purged. I think that this is equivalent to what "dpkg --set-selections" does. > > But it is not purged yet, so that there is no reason to > > take that into account. > > I wonder if this could also be related to the fact that libplacebo7 is > currently no more in Debian Unstable, just in Debian Testing: > > → apt-cache policy libplacebo7 > libplacebo7: > Installed: (none) > Candidate: 1.7.0-2 > Version table: > 1.7.0-2 600 > 600 https://debian.ethz.ch/debian testing/main amd64 Packages No, on another machine on which I haven't started the upgrade, the completion is fine. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From abe at debian.org Wed Jun 3 16:45:11 2020 From: abe at debian.org (Axel Beckert) Date: Wed, 3 Jun 2020 17:45:11 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603153213.GM367472@zira.vinc17.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> <20200603153213.GM367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> Control: severity -1 wishlist Control: tag -1 + upstream Hi Vincent, Vincent Lefevre wrote: > Actually there's another one: > > zira:~> dpkg -l | grep '^rc' > rc openntpd 1:6.0p1-1 amd64 OpenBSD NTP daemon All packages shown as "rc" by dpkg on my system seem _not_ to be installed but are usually removed, but not purged. Example: → dpkg -l snapper [...] rc snapper 0.8.1-1 amd64 Linux filesystem snapshot management tool → aptitude show snapper Package: snapper Version: 0.8.9-1+b1 State: not installed (configuration files remain) [...] → dpkg -s sn completing package snetz sniffglue snooze snowdrop sntop >From the design of the current implementation (only show installed packages for "dpkg -s" completion) it is correct that "dpkg -s" doesn't complete these packages. But it seems a valid point that especially the "dpkg -s" completion also completes packages where only configuration files remain. So from my point of view, this is a valid feature request for upstream. Marking it as such. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From owner at bugs.debian.org Wed Jun 3 16:48:06 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jun 2020 15:48:06 +0000 Subject: [Pkg-zsh-devel] Processed: Re: Bug#962133: zsh-common: missing package in "dpkg -s" completion References: <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: Processing control commands: > severity -1 wishlist Bug #962133 [zsh-common] zsh-common: missing package in "dpkg -s" completion Severity set to 'wishlist' from 'normal' > tag -1 + upstream Bug #962133 [zsh-common] zsh-common: missing package in "dpkg -s" completion Added tag(s) upstream. -- 962133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962133 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From vincent at vinc17.net Wed Jun 3 17:02:39 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 18:02:39 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> <20200603153213.GM367472@zira.vinc17.org> <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603160239.GO367472@zira.vinc17.org> On 2020-06-03 17:45:11 +0200, Axel Beckert wrote: > Vincent Lefevre wrote: > > Actually there's another one: > > > > zira:~> dpkg -l | grep '^rc' > > rc openntpd 1:6.0p1-1 amd64 OpenBSD NTP daemon > > All packages shown as "rc" by dpkg on my system seem _not_ to be > installed but are usually removed, but not purged. Example: They are not installed, but are valid candidates for "dpkg -s" arguments. > From the design of the current implementation (only show installed > packages for "dpkg -s" completion) Currently this is: installed and not marked to be uninstalled (or to be purged). > it is correct that "dpkg -s" doesn't complete these packages. This is not correct. "dpkg -s" should complete to any valid argument, i.e. for which package information is available (thus this excludes purged packages). This is a real bug. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Wed Jun 3 17:15:27 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 18:15:27 +0200 Subject: [Pkg-zsh-devel] Bug#962135: zsh-common: "dpkg -l" completion should not proposed purged packages Message-ID: <20200603161527.GA3504924@zira.vinc17.org> Package: zsh-common Version: 5.8-4 Severity: normal Tags: upstream "dpkg -l" proposes all packages known by apt-cache: zira:~> dpkg -l [TAB] zsh: do you wish to see all 95490 possibilities (95491 lines)? For instance, in the completion list: zira:~> dpkg -l abcde dpkg-query: no packages found matching abcde Only packages with available information should be proposed, like "dpkg -s" (whose completion is currently buggy, see bug 962133). -- Package-specific info: Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-======================================================= ii curl 7.68.0-1 amd64 command line tool for transferring data with URL syntax ii pass 1.7.3-2 all lightweight directory-based password manager ii pulseaudio 13.0-5 amd64 PulseAudio sound server ii qpdf 10.0.1-2 amd64 tools for transforming and inspecting PDF files ii systemd 245.5-3 amd64 system and service manager ii udev 245.5-3 amd64 /dev/ and hotplug management daemon ii vlc-bin 3.0.10-1+b1 amd64 binaries from VLC ii youtube-dl 2020.05.08-1 all downloader of videos from YouTube and other sites The following files were modified: /etc/systemd/journald.conf /etc/systemd/logind.conf /etc/systemd/system.conf dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled zsh-common depends on no packages. Versions of packages zsh-common recommends: ii zsh 5.8-4 Versions of packages zsh-common suggests: ii zsh-doc 5.8-4 -- no debconf information -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Wed Jun 3 17:38:03 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 18:38:03 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603160239.GO367472@zira.vinc17.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> <20200603153213.GM367472@zira.vinc17.org> <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> <20200603160239.GO367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603163803.GA3502917@zira.vinc17.org> The issue is that /usr/share/zsh/functions/Completion/Debian/_deb_packages just considers packages in states install and hold: _deb_packages_update_installed () { if ( [[ ${+_deb_packages_cache_installed} -eq 0 ]] || _cache_invalid DEBS_installed ) && ! _retrieve_cache DEBS_installed; then _deb_packages_cache_installed=() dpkg --get-selections | while read package state ; do [[ $state = (install|hold) ]] && _deb_packages_cache_installed+=$package done _store_cache DEBS_installed _deb_packages_cache_installed fi cachevar=_deb_packages_cache_installed } Instead, any state should be valid for "dpkg -s" completion. It seems that this is what _deb_packages_update_xinstalled does: xinstalled () { if ( [[ ${+_deb_packages_cache_xinstalled} -eq 0 ]] || _cache_invalid DEBS_xinstalled ) && ! _retrieve_cache DEBS_xinstalled; then _deb_packages_cache_xinstalled=() dpkg --get-selections | while read package state ; do _deb_packages_cache_xinstalled+=$package done _store_cache DEBS_xinstalled _deb_packages_cache_xinstalled fi cachevar=_deb_packages_cache_xinstalled } So the fix should be easy: in /usr/share/zsh/functions/Completion/Debian/_dpkg remove|status|listfiles) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s "$_dpkg_options[@]" \ '*:package:_deb_packages installed' ;; purge) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s "$_dpkg_options[@]" \ '*:package:_deb_packages xinstalled' ;; move "status" and "listfiles" to "purge" (which uses xinstalled). Still, "remove" and "purge" would remain inconsistent, which is another bug... -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Wed Jun 3 17:51:02 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 18:51:02 +0200 Subject: [Pkg-zsh-devel] Bug#962135: zsh-common: "dpkg -l" completion should not proposed purged packages In-Reply-To: <20200603161527.GA3504924@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200603165102.GP367472@zira.vinc17.org> Control: retitle -1 zsh-common: "dpkg -l" completion should not propose purged packages On 2020-06-03 18:15:27 +0200, Vincent Lefevre wrote: > "dpkg -l" proposes all packages known by apt-cache: > > zira:~> dpkg -l [TAB] > zsh: do you wish to see all 95490 possibilities (95491 lines)? > > For instance, in the completion list: > > zira:~> dpkg -l abcde > dpkg-query: no packages found matching abcde > > Only packages with available information should be proposed, like > "dpkg -s" (whose completion is currently buggy, see bug 962133). Like for bug 962133, the fix should be easy: change avail (which is used for "apt-cache show") to xinstalled. I'm going to do some tests. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From owner at bugs.debian.org Wed Jun 3 17:54:03 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jun 2020 16:54:03 +0000 Subject: [Pkg-zsh-devel] Processed: Re: zsh-common: "dpkg -l" completion should not proposed purged packages References: <20200603165102.GP367472@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: Processing control commands: > retitle -1 zsh-common: "dpkg -l" completion should not propose purged packages Bug #962135 [zsh-common] zsh-common: "dpkg -l" completion should not proposed purged packages Changed Bug title to 'zsh-common: "dpkg -l" completion should not propose purged packages' from 'zsh-common: "dpkg -l" completion should not proposed purged packages'. -- 962135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962135 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From vincent at vinc17.net Wed Jun 3 18:55:50 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 19:55:50 +0200 Subject: [Pkg-zsh-devel] Bug#962133: patch for bugs 962133 and 962135 References: <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603175550.GQ367472@zira.vinc17.org> Control: tags 962133 patch Control: tags 962135 patch I've attached a patch for Debian bugs 962133 ("dpkg -s" completion) and 962135 ("dpkg -l" completion), which also fixes "dpkg --remove" and "dpkg --purge" completions. I've added a note about that: # Note: Packages may be marked as "deinstall" or "purge", i.e. selected # for deinstallation or to be purged (see dpkg(1) man page); this means # that the operation has not been completed yet. In the meantime, such # packages may still be installed (if marked as purge, one is not sure, # though, as the package could have been uninstalled but not purged yet), # so that purge and remove operations remain valid. Basically, the fix consists of the _dpkg change. My patch also removes "deinstalled" from _deb_packages as it does not seem to be used (and should be useless). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -------------- next part -------------- diff -aurd compl-debian-deb/_deb_packages compl-debian-fix/_deb_packages --- compl-debian-deb/_deb_packages 2020-03-22 15:12:25.000000000 +0000 +++ compl-debian-fix/_deb_packages 2020-06-03 17:09:43.704256786 +0000 @@ -1,6 +1,6 @@ #autoload -# Usage: _deb_packages expl... (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) +# Usage: _deb_packages expl... (installed|xinstalled|held|uninstalled|avail|available|source) _deb_packages_update_avail () { if ( [[ ${+_deb_packages_cache_avail} -eq 0 ]] || @@ -41,19 +41,6 @@ cachevar=_deb_packages_cache_held } -_deb_packages_update_deinstalled () { - if ( [[ ${+_deb_packages_cache_deinstalled} -eq 0 ]] || - _cache_invalid DEBS_deinstalled ) && ! _retrieve_cache DEBS_deinstalled; - then - _deb_packages_cache_deinstalled=() - dpkg --get-selections | while read package state ; do - [[ $state = deinstall ]] && _deb_packages_cache_deinstalled+=$package - done - _store_cache DEBS_deinstalled _deb_packages_cache_deinstalled - fi - cachevar=_deb_packages_cache_deinstalled -} - _deb_packages_update_xinstalled () { if ( [[ ${+_deb_packages_cache_xinstalled} -eq 0 ]] || _cache_invalid DEBS_xinstalled ) && ! _retrieve_cache DEBS_xinstalled; @@ -103,14 +90,14 @@ zstyle ":completion:*:*:$service:*" cache-policy _debs_caching_policy fi - [[ "$command" = (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) ]] || { + [[ "$command" = (installed|xinstalled|held|uninstalled|avail|available|source) ]] || { _message "unknown command: $command" return } zstyle -s ":completion:${curcontext}:" packageset pkgset - [[ "$pkgset" = (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) ]] || { + [[ "$pkgset" = (installed|xinstalled|held|uninstalled|avail|available|source) ]] || { pkgset="$command" } diff -aurd compl-debian-deb/_dpkg compl-debian-fix/_dpkg --- compl-debian-deb/_dpkg 2020-03-22 15:12:25.000000000 +0000 +++ compl-debian-fix/_dpkg 2020-06-03 17:24:33.866990607 +0000 @@ -149,21 +149,17 @@ - nonrecur \ '*: :_deb_files' ;; - remove|status|listfiles) - _call_function ret _dpkg_$state && return ret - _arguments -C -A "-*" -s "$_dpkg_options[@]" \ - '*:package:_deb_packages installed' - ;; - purge) +# Note: Packages may be marked as "deinstall" or "purge", i.e. selected +# for deinstallation or to be purged (see dpkg(1) man page); this means +# that the operation has not been completed yet. In the meantime, such +# packages may still be installed (if marked as purge, one is not sure, +# though, as the package could have been uninstalled but not purged yet), +# so that purge and remove operations remain valid. + list|listfiles|purge|remove|status) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s "$_dpkg_options[@]" \ '*:package:_deb_packages xinstalled' ;; - list) - _call_function ret _dpkg_$state && return ret - _arguments -C -A "-*" -s "$_dpkg_options[@]" \ - '*:packages:_deb_packages avail' - ;; compare_versions) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s \ From owner at bugs.debian.org Wed Jun 3 18:57:04 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jun 2020 17:57:04 +0000 Subject: [Pkg-zsh-devel] Processed: patch for bugs 962133 and 962135 References: <20200603175550.GQ367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: Processing control commands: > tags 962133 patch Bug #962133 [zsh-common] zsh-common: missing package in "dpkg -s" completion Added tag(s) patch. > tags 962135 patch Bug #962135 [zsh-common] zsh-common: "dpkg -l" completion should not propose purged packages Added tag(s) patch. -- 962133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962133 962135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962135 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From vincent at vinc17.net Wed Jun 3 18:55:50 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 19:55:50 +0200 Subject: [Pkg-zsh-devel] Bug#962135: patch for bugs 962133 and 962135 References: <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200603175550.GQ367472@zira.vinc17.org> Control: tags 962133 patch Control: tags 962135 patch I've attached a patch for Debian bugs 962133 ("dpkg -s" completion) and 962135 ("dpkg -l" completion), which also fixes "dpkg --remove" and "dpkg --purge" completions. I've added a note about that: # Note: Packages may be marked as "deinstall" or "purge", i.e. selected # for deinstallation or to be purged (see dpkg(1) man page); this means # that the operation has not been completed yet. In the meantime, such # packages may still be installed (if marked as purge, one is not sure, # though, as the package could have been uninstalled but not purged yet), # so that purge and remove operations remain valid. Basically, the fix consists of the _dpkg change. My patch also removes "deinstalled" from _deb_packages as it does not seem to be used (and should be useless). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -------------- next part -------------- diff -aurd compl-debian-deb/_deb_packages compl-debian-fix/_deb_packages --- compl-debian-deb/_deb_packages 2020-03-22 15:12:25.000000000 +0000 +++ compl-debian-fix/_deb_packages 2020-06-03 17:09:43.704256786 +0000 @@ -1,6 +1,6 @@ #autoload -# Usage: _deb_packages expl... (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) +# Usage: _deb_packages expl... (installed|xinstalled|held|uninstalled|avail|available|source) _deb_packages_update_avail () { if ( [[ ${+_deb_packages_cache_avail} -eq 0 ]] || @@ -41,19 +41,6 @@ cachevar=_deb_packages_cache_held } -_deb_packages_update_deinstalled () { - if ( [[ ${+_deb_packages_cache_deinstalled} -eq 0 ]] || - _cache_invalid DEBS_deinstalled ) && ! _retrieve_cache DEBS_deinstalled; - then - _deb_packages_cache_deinstalled=() - dpkg --get-selections | while read package state ; do - [[ $state = deinstall ]] && _deb_packages_cache_deinstalled+=$package - done - _store_cache DEBS_deinstalled _deb_packages_cache_deinstalled - fi - cachevar=_deb_packages_cache_deinstalled -} - _deb_packages_update_xinstalled () { if ( [[ ${+_deb_packages_cache_xinstalled} -eq 0 ]] || _cache_invalid DEBS_xinstalled ) && ! _retrieve_cache DEBS_xinstalled; @@ -103,14 +90,14 @@ zstyle ":completion:*:*:$service:*" cache-policy _debs_caching_policy fi - [[ "$command" = (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) ]] || { + [[ "$command" = (installed|xinstalled|held|uninstalled|avail|available|source) ]] || { _message "unknown command: $command" return } zstyle -s ":completion:${curcontext}:" packageset pkgset - [[ "$pkgset" = (installed|deinstalled|xinstalled|held|uninstalled|avail|available|source) ]] || { + [[ "$pkgset" = (installed|xinstalled|held|uninstalled|avail|available|source) ]] || { pkgset="$command" } diff -aurd compl-debian-deb/_dpkg compl-debian-fix/_dpkg --- compl-debian-deb/_dpkg 2020-03-22 15:12:25.000000000 +0000 +++ compl-debian-fix/_dpkg 2020-06-03 17:24:33.866990607 +0000 @@ -149,21 +149,17 @@ - nonrecur \ '*: :_deb_files' ;; - remove|status|listfiles) - _call_function ret _dpkg_$state && return ret - _arguments -C -A "-*" -s "$_dpkg_options[@]" \ - '*:package:_deb_packages installed' - ;; - purge) +# Note: Packages may be marked as "deinstall" or "purge", i.e. selected +# for deinstallation or to be purged (see dpkg(1) man page); this means +# that the operation has not been completed yet. In the meantime, such +# packages may still be installed (if marked as purge, one is not sure, +# though, as the package could have been uninstalled but not purged yet), +# so that purge and remove operations remain valid. + list|listfiles|purge|remove|status) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s "$_dpkg_options[@]" \ '*:package:_deb_packages xinstalled' ;; - list) - _call_function ret _dpkg_$state && return ret - _arguments -C -A "-*" -s "$_dpkg_options[@]" \ - '*:packages:_deb_packages avail' - ;; compare_versions) _call_function ret _dpkg_$state && return ret _arguments -C -A "-*" -s \ From owner at bugs.debian.org Wed Jun 3 18:57:06 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jun 2020 17:57:06 +0000 Subject: [Pkg-zsh-devel] Processed: patch for bugs 962133 and 962135 References: <20200603175550.GQ367472@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: Processing control commands: > tags 962133 patch Bug #962133 [zsh-common] zsh-common: missing package in "dpkg -s" completion Ignoring request to alter tags of bug #962133 to the same tags previously set > tags 962135 patch Bug #962135 [zsh-common] zsh-common: "dpkg -l" completion should not propose purged packages Ignoring request to alter tags of bug #962135 to the same tags previously set -- 962133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962133 962135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962135 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From abe at debian.org Wed Jun 3 19:28:11 2020 From: abe at debian.org (Axel Beckert) Date: Wed, 3 Jun 2020 20:28:11 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603175550.GQ367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603182810.rwxid7dhvugiogfd@sym.noone.org> Hi Vincent, Vincent Lefevre wrote: > I've attached a patch for Debian bugs 962133 ("dpkg -s" completion) > and 962135 ("dpkg -l" completion), which also fixes "dpkg --remove" > and "dpkg --purge" completions. Thanks for the patch! Daniel: Would you review it for upstream inclusion? > I've added a note about that: > > # Note: Packages may be marked as "deinstall" or "purge", i.e. selected > # for deinstallation or to be purged (see dpkg(1) man page); this means > # that the operation has not been completed yet. In the meantime, such > # packages may still be installed (if marked as purge, one is not sure, > # though, as the package could have been uninstalled but not purged yet), > # so that purge and remove operations remain valid. *sigh* IMHO this is highly misleading. The difference between dpkg "states" (i.e. the current state) and "selection states" (i.e. the wanted state) only matters if you use dselect, which nearly nobody does nowadays. So please do _not_ refer to "selection states" in such places since "selected for deinstallation" always sounds as if deinstallation is imminent while it in 99.9% of all cases already has happened, possibly even years ago. > My patch also removes "deinstalled" from _deb_packages as it does not > seem to be used (and should be useless). Not sure if this is wanted. That code might have been made "complete" on purpose for 3rd-party (or future internal) usage. I'd not remove it. Nevertheless good to know that it doesn't seem to get used in zsh internally currently. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From abe at debian.org Wed Jun 3 19:28:11 2020 From: abe at debian.org (Axel Beckert) Date: Wed, 3 Jun 2020 20:28:11 +0200 Subject: [Pkg-zsh-devel] Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603175550.GQ367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200603182810.rwxid7dhvugiogfd@sym.noone.org> Hi Vincent, Vincent Lefevre wrote: > I've attached a patch for Debian bugs 962133 ("dpkg -s" completion) > and 962135 ("dpkg -l" completion), which also fixes "dpkg --remove" > and "dpkg --purge" completions. Thanks for the patch! Daniel: Would you review it for upstream inclusion? > I've added a note about that: > > # Note: Packages may be marked as "deinstall" or "purge", i.e. selected > # for deinstallation or to be purged (see dpkg(1) man page); this means > # that the operation has not been completed yet. In the meantime, such > # packages may still be installed (if marked as purge, one is not sure, > # though, as the package could have been uninstalled but not purged yet), > # so that purge and remove operations remain valid. *sigh* IMHO this is highly misleading. The difference between dpkg "states" (i.e. the current state) and "selection states" (i.e. the wanted state) only matters if you use dselect, which nearly nobody does nowadays. So please do _not_ refer to "selection states" in such places since "selected for deinstallation" always sounds as if deinstallation is imminent while it in 99.9% of all cases already has happened, possibly even years ago. > My patch also removes "deinstalled" from _deb_packages as it does not > seem to be used (and should be useless). Not sure if this is wanted. That code might have been made "complete" on purpose for 3rd-party (or future internal) usage. I'd not remove it. Nevertheless good to know that it doesn't seem to get used in zsh internally currently. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From vincent at vinc17.net Wed Jun 3 20:14:12 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 21:14:12 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603182810.rwxid7dhvugiogfd@sym.noone.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200603191412.GR367472@zira.vinc17.org> Hi Axel, On 2020-06-03 20:28:11 +0200, Axel Beckert wrote: > Daniel: Would you review it for upstream inclusion? > > > I've added a note about that: > > > > # Note: Packages may be marked as "deinstall" or "purge", i.e. selected > > # for deinstallation or to be purged (see dpkg(1) man page); this means > > # that the operation has not been completed yet. In the meantime, such > > # packages may still be installed (if marked as purge, one is not sure, > > # though, as the package could have been uninstalled but not purged yet), > > # so that purge and remove operations remain valid. > > *sigh* IMHO this is highly misleading. > > The difference between dpkg "states" (i.e. the current state) and > "selection states" (i.e. the wanted state) only matters if you use > dselect, which nearly nobody does nowadays. > > So please do _not_ refer to "selection states" in such places since > "selected for deinstallation" always sounds as if deinstallation is > imminent while it in 99.9% of all cases already has happened, possibly > even years ago. Well, the dpkg(1) man page says "selection states" and "selected for deinstallation": Package selection states install The package is selected for installation. hold A package marked to be on hold is not handled by dpkg, unless forced to do that with option --force-hold. deinstall The package is selected for deinstallation (i.e. we want to remove all files, except configuration files). purge The package is selected to be purged (i.e. we want to remove everything from system directories, even configuration files). unknown The package selection is unknown. A package that is also in a not-installed state, and with an ok flag will be forgotten in the next database store. Do you mean that this man page should be modified? > > My patch also removes "deinstalled" from _deb_packages as it does not > > seem to be used (and should be useless). > > Not sure if this is wanted. That code might have been made "complete" > on purpose for 3rd-party (or future internal) usage. I'd not remove it. Perhaps, but why aren't there equivalent functions for the "install" and "purge" states, then? Note that this is not documented, so I thought that this was just internal, and 3rd party code should have its own functions. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Wed Jun 3 20:14:12 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Wed, 3 Jun 2020 21:14:12 +0200 Subject: [Pkg-zsh-devel] Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603182810.rwxid7dhvugiogfd@sym.noone.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200603191412.GR367472@zira.vinc17.org> Hi Axel, On 2020-06-03 20:28:11 +0200, Axel Beckert wrote: > Daniel: Would you review it for upstream inclusion? > > > I've added a note about that: > > > > # Note: Packages may be marked as "deinstall" or "purge", i.e. selected > > # for deinstallation or to be purged (see dpkg(1) man page); this means > > # that the operation has not been completed yet. In the meantime, such > > # packages may still be installed (if marked as purge, one is not sure, > > # though, as the package could have been uninstalled but not purged yet), > > # so that purge and remove operations remain valid. > > *sigh* IMHO this is highly misleading. > > The difference between dpkg "states" (i.e. the current state) and > "selection states" (i.e. the wanted state) only matters if you use > dselect, which nearly nobody does nowadays. > > So please do _not_ refer to "selection states" in such places since > "selected for deinstallation" always sounds as if deinstallation is > imminent while it in 99.9% of all cases already has happened, possibly > even years ago. Well, the dpkg(1) man page says "selection states" and "selected for deinstallation": Package selection states install The package is selected for installation. hold A package marked to be on hold is not handled by dpkg, unless forced to do that with option --force-hold. deinstall The package is selected for deinstallation (i.e. we want to remove all files, except configuration files). purge The package is selected to be purged (i.e. we want to remove everything from system directories, even configuration files). unknown The package selection is unknown. A package that is also in a not-installed state, and with an ok flag will be forgotten in the next database store. Do you mean that this man page should be modified? > > My patch also removes "deinstalled" from _deb_packages as it does not > > seem to be used (and should be useless). > > Not sure if this is wanted. That code might have been made "complete" > on purpose for 3rd-party (or future internal) usage. I'd not remove it. Perhaps, but why aren't there equivalent functions for the "install" and "purge" states, then? Note that this is not documented, so I thought that this was just internal, and 3rd party code should have its own functions. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From d.s at daniel.shahaf.name Thu Jun 4 04:32:49 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Thu, 4 Jun 2020 03:32:49 +0000 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603191412.GR367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200604033249.7d68ec61@tarpaulin.shahaf.local2> Vincent Lefevre wrote on Wed, 03 Jun 2020 21:14 +0200: > On 2020-06-03 20:28:11 +0200, Axel Beckert wrote: > > Daniel: Would you review it for upstream inclusion? Sure. > Note that this is not documented, so I thought that this was just > internal, and 3rd party code should have its own functions. As far as completion functions go, I'd err on the side of considering the comment at the top of _deb_packages to be API documentation, notwithstanding that it's only a top-of-file comment and not in the manual. Furthermore, I'd rather not remove code just because it's currently unused in zsh.git. The completion system — especially the Type/* functions — is an API, not a blackbox. Does the function proposed for removal answer a useful question? Might third party tools (or even people's zshrc files) be using or in the future use that function? The function has already been written (and debugged, etc); how likely is it that if we remove it, someone will have to reinvent the wheel? So, I agree with Axel about the _deb_packages part of the patch. As to the _dpkg part of the patch, first of all, it's incomplete: it removes the "listfiles" case but not the code that sets that value. Once the latter is removed too, the function will then display a single asterisk to the user instead of an actual description. And with _that_ fixed, there'll still be the issue that, where possible, it's better to generate completions than to just tell the user what type of thing they're supposed to type in. Incorrect or incomplete code should, if possible, be corrected rather than axed. So I consider the _dpkg part of the patch a helpful debugging aid, but I'm afraid I don't think it's ready to be merged as-is. I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of semantics, but in general, completion should (1) offer everything that the command would accept, (2) not offer things the command won't accept. That's in descending order of priority: it's usually better to offer too much than too little. HTH. Let me know if you have further questions ☺ Cheers, Daniel (no pun intended) From d.s at daniel.shahaf.name Thu Jun 4 04:32:49 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Thu, 4 Jun 2020 03:32:49 +0000 Subject: [Pkg-zsh-devel] Bug#962135: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200603191412.GR367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200604033249.7d68ec61@tarpaulin.shahaf.local2> Vincent Lefevre wrote on Wed, 03 Jun 2020 21:14 +0200: > On 2020-06-03 20:28:11 +0200, Axel Beckert wrote: > > Daniel: Would you review it for upstream inclusion? Sure. > Note that this is not documented, so I thought that this was just > internal, and 3rd party code should have its own functions. As far as completion functions go, I'd err on the side of considering the comment at the top of _deb_packages to be API documentation, notwithstanding that it's only a top-of-file comment and not in the manual. Furthermore, I'd rather not remove code just because it's currently unused in zsh.git. The completion system — especially the Type/* functions — is an API, not a blackbox. Does the function proposed for removal answer a useful question? Might third party tools (or even people's zshrc files) be using or in the future use that function? The function has already been written (and debugged, etc); how likely is it that if we remove it, someone will have to reinvent the wheel? So, I agree with Axel about the _deb_packages part of the patch. As to the _dpkg part of the patch, first of all, it's incomplete: it removes the "listfiles" case but not the code that sets that value. Once the latter is removed too, the function will then display a single asterisk to the user instead of an actual description. And with _that_ fixed, there'll still be the issue that, where possible, it's better to generate completions than to just tell the user what type of thing they're supposed to type in. Incorrect or incomplete code should, if possible, be corrected rather than axed. So I consider the _dpkg part of the patch a helpful debugging aid, but I'm afraid I don't think it's ready to be merged as-is. I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of semantics, but in general, completion should (1) offer everything that the command would accept, (2) not offer things the command won't accept. That's in descending order of priority: it's usually better to offer too much than too little. HTH. Let me know if you have further questions ☺ Cheers, Daniel (no pun intended) From d.s at daniel.shahaf.name Thu Jun 4 04:47:19 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Thu, 4 Jun 2020 03:47:19 +0000 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962133: Bug#962133: zsh-common: missing package in "dpkg -s" completion In-Reply-To: <20200603160239.GO367472@zira.vinc17.org> References: <20200603152131.GA3497045@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> <20200603153213.GM367472@zira.vinc17.org> <20200603154505.qm7y47sxhrgdjz4r@sym.noone.org> <20200603152131.GA3497045@zira.vinc17.org> <20200603160239.GO367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200604034719.022cb869@tarpaulin.shahaf.local2> Vincent Lefevre wrote on Wed, 03 Jun 2020 18:02 +0200: > On 2020-06-03 17:45:11 +0200, Axel Beckert wrote: > > Vincent Lefevre wrote: > > > Actually there's another one: > > > > > > zira:~> dpkg -l | grep '^rc' > > > rc openntpd 1:6.0p1-1 amd64 OpenBSD NTP daemon > > > > All packages shown as "rc" by dpkg on my system seem _not_ to be > > installed but are usually removed, but not purged. Example: > > They are not installed, but are valid candidates for "dpkg -s" > arguments. > > > From the design of the current implementation (only show installed > > packages for "dpkg -s" completion) > > Currently this is: installed and not marked to be uninstalled > (or to be purged). > > > it is correct that "dpkg -s" doesn't complete these packages. > > This is not correct. Axel did not say that _dpkg's behaviour was correct. Axel only said that _dpkg was behaving as designed. Furthermore, in the snipped context Axel agreed that it would be good to have _dpkg modified to behave as per your proposal. > "dpkg -s" should complete to any valid > argument, i.e. for which package information is available > (thus this excludes purged packages). This is a real bug. From vincent at vinc17.net Thu Jun 4 09:03:26 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Thu, 4 Jun 2020 10:03:26 +0200 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200604033249.7d68ec61@tarpaulin.shahaf.local2> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200604033249.7d68ec61@tarpaulin.shahaf.local2> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200604080326.GS367472@zira.vinc17.org> On 2020-06-04 03:32:49 +0000, Daniel Shahaf wrote: > Furthermore, I'd rather not remove code just because it's currently > unused in zsh.git. The completion system — especially the Type/* > functions — is an API, not a blackbox. Does the function proposed for > removal answer a useful question? Might third party tools (or even > people's zshrc files) be using or in the future use that function? The > function has already been written (and debugged, etc); how likely is it > that if we remove it, someone will have to reinvent the wheel? An issue is that deinstall can mean 2 things: 1. A package that has been uninstalled but not purged. 2. A package that is still installed but is selected for deinstallation. and that is not currently documented in _deb_packages_update_deinstalled. I fear that a tool that uses it is likely to be buggy. FYI, a case for (1) on one of my machines: zira:~> dpkg --get-selections | grep deinstall openntpd deinstall (and "dpkg -L openntpd" only lists files under /etc and directories under /var) and for (2) on another machine (where I selected some packages for upgrade in aptitude, then quit aptitude): cventin:~> dpkg --get-selections | grep deinstall libplacebo7:amd64 deinstall (and "dpkg -L libplacebo7:amd64" lists all files). > So, I agree with Axel about the _deb_packages part of the patch. > > As to the _dpkg part of the patch, first of all, it's incomplete: > it removes the "listfiles" case but not the code that sets that value. It does not remove "listfiles", but moves it to use "xinstalled" instead of "installed" (perhaps I forgot to say I fixed that too). This listfiles command still makes sense for any package listed by "dpkg --get-selections", even if it has already been uninstalled (see above on openntpd). > Once the latter is removed too, the function will then display a single > asterisk to the user instead of an actual description. And with _that_ > fixed, there'll still be the issue that, where possible, it's better to > generate completions than to just tell the user what type of thing they're > supposed to type in. Incorrect or incomplete code should, if possible, > be corrected rather than axed. I don't understand what you mean. > I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of > semantics, but in general, completion should (1) offer everything that > the command would accept, (2) not offer things the command won't accept. This is what my patch corrects for the remove, status, listfiles and list commands. > That's in descending order of priority: it's usually better to offer too > much than too little. Yes, remove, status and listfiles offered too little (only packages in the install or hold state). On the opposite, list offered too much (all packages known to apt), but for a package that is not listed by "dpkg --get-selections", i.e. for which no information is available for dpkg, I don't see how this can be useful: "dpkg --list foo", where foo is neither installed, nor uninstalled (but not purged), just returns an error. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From vincent at vinc17.net Thu Jun 4 09:03:26 2020 From: vincent at vinc17.net (Vincent Lefevre) Date: Thu, 4 Jun 2020 10:03:26 +0200 Subject: [Pkg-zsh-devel] Bug#962135: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200604033249.7d68ec61@tarpaulin.shahaf.local2> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200604033249.7d68ec61@tarpaulin.shahaf.local2> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200604080326.GS367472@zira.vinc17.org> On 2020-06-04 03:32:49 +0000, Daniel Shahaf wrote: > Furthermore, I'd rather not remove code just because it's currently > unused in zsh.git. The completion system — especially the Type/* > functions — is an API, not a blackbox. Does the function proposed for > removal answer a useful question? Might third party tools (or even > people's zshrc files) be using or in the future use that function? The > function has already been written (and debugged, etc); how likely is it > that if we remove it, someone will have to reinvent the wheel? An issue is that deinstall can mean 2 things: 1. A package that has been uninstalled but not purged. 2. A package that is still installed but is selected for deinstallation. and that is not currently documented in _deb_packages_update_deinstalled. I fear that a tool that uses it is likely to be buggy. FYI, a case for (1) on one of my machines: zira:~> dpkg --get-selections | grep deinstall openntpd deinstall (and "dpkg -L openntpd" only lists files under /etc and directories under /var) and for (2) on another machine (where I selected some packages for upgrade in aptitude, then quit aptitude): cventin:~> dpkg --get-selections | grep deinstall libplacebo7:amd64 deinstall (and "dpkg -L libplacebo7:amd64" lists all files). > So, I agree with Axel about the _deb_packages part of the patch. > > As to the _dpkg part of the patch, first of all, it's incomplete: > it removes the "listfiles" case but not the code that sets that value. It does not remove "listfiles", but moves it to use "xinstalled" instead of "installed" (perhaps I forgot to say I fixed that too). This listfiles command still makes sense for any package listed by "dpkg --get-selections", even if it has already been uninstalled (see above on openntpd). > Once the latter is removed too, the function will then display a single > asterisk to the user instead of an actual description. And with _that_ > fixed, there'll still be the issue that, where possible, it's better to > generate completions than to just tell the user what type of thing they're > supposed to type in. Incorrect or incomplete code should, if possible, > be corrected rather than axed. I don't understand what you mean. > I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of > semantics, but in general, completion should (1) offer everything that > the command would accept, (2) not offer things the command won't accept. This is what my patch corrects for the remove, status, listfiles and list commands. > That's in descending order of priority: it's usually better to offer too > much than too little. Yes, remove, status and listfiles offered too little (only packages in the install or hold state). On the opposite, list offered too much (all packages known to apt), but for a package that is not listed by "dpkg --get-selections", i.e. for which no information is available for dpkg, I don't see how this can be useful: "dpkg --list foo", where foo is neither installed, nor uninstalled (but not purged), just returns an error. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From d.s at daniel.shahaf.name Fri Jun 5 04:45:53 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Fri, 5 Jun 2020 03:45:53 +0000 Subject: [Pkg-zsh-devel] Bug#962135: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200604080326.GS367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200604033249.7d68ec61@tarpaulin.shahaf.local2> <20200604080326.GS367472@zira.vinc17.org> <20200603161527.GA3504924@zira.vinc17.org> Message-ID: <20200605034553.04742886@tarpaulin.shahaf.local2> Vincent Lefevre wrote on Thu, 04 Jun 2020 10:03 +0200: > On 2020-06-04 03:32:49 +0000, Daniel Shahaf wrote: > > Furthermore, I'd rather not remove code just because it's currently > > unused in zsh.git. The completion system — especially the Type/* > > functions — is an API, not a blackbox. Does the function proposed for > > removal answer a useful question? Might third party tools (or even > > people's zshrc files) be using or in the future use that function? The > > function has already been written (and debugged, etc); how likely is it > > that if we remove it, someone will have to reinvent the wheel? > > An issue is that deinstall can mean 2 things: > 1. A package that has been uninstalled but not purged. > 2. A package that is still installed but is selected for > deinstallation. > > and that is not currently documented in _deb_packages_update_deinstalled. > I fear that a tool that uses it is likely to be buggy. Even so, I don't see how that's a reason to remove the function. It's quite common for maintainers of completion functions to have to be well acquainted with uncommon functionalities of the tool they work on, and "All packages that have been selected to be deinstalled" sounds (to this not-familiar-with-dpkg(8)-internals reader) like a fair question to ask. It might not be the _right_ question to ask in every case, but that's a separate problem. Note that alongside «_deb_packages deinstalled» there is also «_deb_packages uninstalled». It seems to me that some documentation is in order, to explain the differences between those two functions and the related pitfalls. While we're there, it would be nice to also explain what xinstalled does (people shouldn't have to read the implementation of _deb_packages to figure out the answer to that). > > So, I agree with Axel about the _deb_packages part of the patch. > > > > As to the _dpkg part of the patch, first of all, it's incomplete: > > it removes the "listfiles" case but not the code that sets that value. > > It does not remove "listfiles", but moves it to use "xinstalled" > instead of "installed" (perhaps I forgot to say I fixed that > too). My apologies. I misread the diff. > This listfiles command still makes sense for any package > listed by "dpkg --get-selections", even if it has already been > uninstalled (see above on openntpd). So you're saying that «dpkg -L» should complete xinstalled rather than deinstalled. I don't know dpkg well enough to have an opinion one way or the other. What I will say is that if «dpkg -L foo» works, then «dpkg -L » should offer «foo». > > Once the latter is removed too, the function will then display a single > > asterisk to the user instead of an actual description. And with _that_ > > fixed, there'll still be the issue that, where possible, it's better to > > generate completions than to just tell the user what type of thing they're > > supposed to type in. Incorrect or incomplete code should, if possible, > > be corrected rather than axed. > > I don't understand what you mean. > I don't understand what part you didn't understand, but in any case, just ignore that paragraph; it was a consequent misunderstanding of my misreading of the diff. > > I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of > > semantics, but in general, completion should (1) offer everything that > > the command would accept, (2) not offer things the command won't accept. > > This is what my patch corrects for the remove, status, listfiles and > list commands. That's great. > > That's in descending order of priority: it's usually better to offer too > > much than too little. > > Yes, remove, status and listfiles offered too little (only packages > in the install or hold state). On the opposite, list offered too much > (all packages known to apt), but for a package that is not listed by > "dpkg --get-selections", i.e. for which no information is available > for dpkg, I don't see how this can be useful: "dpkg --list foo", > where foo is neither installed, nor uninstalled (but not purged), > just returns an error. Yes, if «dpkg -L foo» returns an error then «foo» shouldn't be completed. > Axel, do you have any concerns about the _dpkg part of the patch? Cheers, Daniel From d.s at daniel.shahaf.name Fri Jun 5 04:45:53 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Fri, 5 Jun 2020 03:45:53 +0000 Subject: [Pkg-zsh-devel] Bug#962133: Bug#962135: Bug#962135: patch for bugs 962133 and 962135 In-Reply-To: <20200604080326.GS367472@zira.vinc17.org> References: <20200603161527.GA3504924@zira.vinc17.org> <20200603175550.GQ367472@zira.vinc17.org> <20200603182810.rwxid7dhvugiogfd@sym.noone.org> <20200603161527.GA3504924@zira.vinc17.org> <20200603191412.GR367472@zira.vinc17.org> <20200604033249.7d68ec61@tarpaulin.shahaf.local2> <20200604080326.GS367472@zira.vinc17.org> <20200603152131.GA3497045@zira.vinc17.org> Message-ID: <20200605034553.04742886@tarpaulin.shahaf.local2> Vincent Lefevre wrote on Thu, 04 Jun 2020 10:03 +0200: > On 2020-06-04 03:32:49 +0000, Daniel Shahaf wrote: > > Furthermore, I'd rather not remove code just because it's currently > > unused in zsh.git. The completion system — especially the Type/* > > functions — is an API, not a blackbox. Does the function proposed for > > removal answer a useful question? Might third party tools (or even > > people's zshrc files) be using or in the future use that function? The > > function has already been written (and debugged, etc); how likely is it > > that if we remove it, someone will have to reinvent the wheel? > > An issue is that deinstall can mean 2 things: > 1. A package that has been uninstalled but not purged. > 2. A package that is still installed but is selected for > deinstallation. > > and that is not currently documented in _deb_packages_update_deinstalled. > I fear that a tool that uses it is likely to be buggy. Even so, I don't see how that's a reason to remove the function. It's quite common for maintainers of completion functions to have to be well acquainted with uncommon functionalities of the tool they work on, and "All packages that have been selected to be deinstalled" sounds (to this not-familiar-with-dpkg(8)-internals reader) like a fair question to ask. It might not be the _right_ question to ask in every case, but that's a separate problem. Note that alongside «_deb_packages deinstalled» there is also «_deb_packages uninstalled». It seems to me that some documentation is in order, to explain the differences between those two functions and the related pitfalls. While we're there, it would be nice to also explain what xinstalled does (people shouldn't have to read the implementation of _deb_packages to figure out the answer to that). > > So, I agree with Axel about the _deb_packages part of the patch. > > > > As to the _dpkg part of the patch, first of all, it's incomplete: > > it removes the "listfiles" case but not the code that sets that value. > > It does not remove "listfiles", but moves it to use "xinstalled" > instead of "installed" (perhaps I forgot to say I fixed that > too). My apologies. I misread the diff. > This listfiles command still makes sense for any package > listed by "dpkg --get-selections", even if it has already been > uninstalled (see above on openntpd). So you're saying that «dpkg -L» should complete xinstalled rather than deinstalled. I don't know dpkg well enough to have an opinion one way or the other. What I will say is that if «dpkg -L foo» works, then «dpkg -L » should offer «foo». > > Once the latter is removed too, the function will then display a single > > asterisk to the user instead of an actual description. And with _that_ > > fixed, there'll still be the issue that, where possible, it's better to > > generate completions than to just tell the user what type of thing they're > > supposed to type in. Incorrect or incomplete code should, if possible, > > be corrected rather than axed. > > I don't understand what you mean. > I don't understand what part you didn't understand, but in any case, just ignore that paragraph; it was a consequent misunderstanding of my misreading of the diff. > > I'm not overly familiar with the aptitude/apt/dpkg/dselect hierarchy of > > semantics, but in general, completion should (1) offer everything that > > the command would accept, (2) not offer things the command won't accept. > > This is what my patch corrects for the remove, status, listfiles and > list commands. That's great. > > That's in descending order of priority: it's usually better to offer too > > much than too little. > > Yes, remove, status and listfiles offered too little (only packages > in the install or hold state). On the opposite, list offered too much > (all packages known to apt), but for a package that is not listed by > "dpkg --get-selections", i.e. for which no information is available > for dpkg, I don't see how this can be useful: "dpkg --list foo", > where foo is neither installed, nor uninstalled (but not purged), > just returns an error. Yes, if «dpkg -L foo» returns an error then «foo» shouldn't be completed. > Axel, do you have any concerns about the _dpkg part of the patch? Cheers, Daniel From d.s at daniel.shahaf.name Tue Jun 9 09:12:01 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Tue, 9 Jun 2020 08:12:01 +0000 Subject: [Pkg-zsh-devel] Bug#960298: Bug#960298: Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream In-Reply-To: <20200511160702.67b66884@tarpaulin.shahaf.local2> References: <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> <20200511160702.67b66884@tarpaulin.shahaf.local2> <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> Message-ID: <20200609081201.01e5c94e@tarpaulin.shahaf.local2> Daniel Shahaf wrote on Mon, 11 May 2020 16:07 +0000: > Daniel Shahaf wrote on Mon, 11 May 2020 15:58 +0000: > > On the heels of #953389, which added _dscverify, shall we backport the > > newly-added _debsnap completion as well? > > > > It was posted in 45724, revised and committed in 45731, and has had an > > unposted followup afterwards. > > Current version: > > https://github.com/zsh-users/zsh/blob/494f6bcb3ca00626ac66348c572a9a69d8b0af37/Completion/Debian/Command/_debsnap Ping? Would it help if I uploaded this to mentors.d.n? Cheers, Daniel From owner at bugs.debian.org Wed Jun 10 16:45:05 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 10 Jun 2020 15:45:05 +0000 Subject: [Pkg-zsh-devel] Bug#568333: marked as done (zsh: bad %? value for prompt expansion) References: <20200610154317.GA5218@tarpaulin.shahaf.local2> <20100204000305.GA21886@xvii.vinc17.org> Message-ID: Your message dated Wed, 10 Jun 2020 15:43:17 +0000 with message-id <20200610154317.GA5218 at tarpaulin.shahaf.local2> and subject line Re: zsh: bad %? value for prompt expansion has caused the Debian Bug report #568333, regarding zsh: bad %? value for prompt expansion 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 owner at bugs.debian.org immediately.) -- 568333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568333 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Vincent Lefevre Subject: zsh: bad %? value for prompt expansion Date: Thu, 4 Feb 2010 01:03:05 +0100 Size: 3465 URL: -------------- next part -------------- An embedded message was scrubbed... From: Daniel Shahaf Subject: Re: zsh: bad %? value for prompt expansion Date: Wed, 10 Jun 2020 15:43:17 +0000 Size: 5480 URL: From d.s at daniel.shahaf.name Wed Jun 10 17:00:45 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Wed, 10 Jun 2020 16:00:45 +0000 Subject: [Pkg-zsh-devel] Bug#658198: Autocompletion: 'ls --n' first returns 'ls --n-g'. In-Reply-To: <20120131180857.c722c41f164a4d0c540fc252@gis.net> References: <20120131180857.c722c41f164a4d0c540fc252@gis.net> <20120131180857.c722c41f164a4d0c540fc252@gis.net> Message-ID: <20200610160045.GA5539@tarpaulin.shahaf.local2> A. Costa wrote on Tue, Jan 31, 2012 at 18:08:57 -0500: > Package: zsh > Version: 4.3.15-1 > Severity: minor > > Dear Maintainer, > > If I do: > > ls --n > > ...the first autocompletion from 'zsh' is: > > ls --n-g > > Of course 'ls' has no '--n-g' option. > No, but it does have --no-group and --numeric-uid-gid. It is ambiguous which one was meant, so zsh completes the unambiguous parts and asks you to type in the rest: that's why you get «--n-g» with the cursor as shown. At that point can type «o» to complete the former option and either «u» or «-» to complete the latter. This is due to matchspecs, as described under the path-completion style but with hyphens rather than slashes. (The gory details are in the manual under "Completion matching control".) If anything, the bug here is that «--n-g» doesn't offer --numeric-uid-gid, even though that option's existence was the reason --no-group wasn't offered immediately. However, I can't reproduce this one when I set the «menu» style. > A second returns: > > ls --no-group > > ...which is a valid 'ls' option. --no-group is a valid option today. > I looked in '/usr/share/zsh/functions/Completion/Unix/_ls' for > clues, but didn't notice anything obviously wrong. But I'm not > a 'zsh' expert. _ls is fine. The matchspecs are handled elsewhere. (They're fetched from a C struct by the «comparguments -M» call in _arguments.) > Hope this helps... It does. Thanks for the report. Daniel (Better late than never…) > > > PS: This is a spin-off bug from Bug#463507. From MREYES at senasa.gob.pe Tue Jun 16 13:26:51 2020 From: MREYES at senasa.gob.pe (MARCO ANTONIO REYES MORA) Date: Tue, 16 Jun 2020 12:26:51 +0000 Subject: [Pkg-zsh-devel] : RE: Dringende Nachricht Message-ID: <40a08e2c783d44819fab9ed59437cdc8@senasa.gob.pe> Schönen Tag Ich hoffe du hast einen schönen Tag. Richard Gordon ist mein Name, ich bin ein professioneller Bitcoin Miner und arbeite bei Discovery Bitcoin Mining https://www.discoverybtcmining.com Ist Ihnen bewusst, dass Sie mit Bitcoin täglich zwischen $5,000 USD und $85,000 USD verdienen können? Es ist legal, garantiert und hat kein Risiko. Kontaktieren Sie mich per E-Mail unten oder klicken Sie auf Antwort auf diese Nachricht, wenn Sie interessiert sind, und ich werde Ihnen umfassende Details zur Funktionsweise senden. Ich erwarte deine Antwort. Kontakt E-Mail: customer at discoverybitcmining.com Freundliche Grüße Richard Gordon -------------- next part -------------- An HTML attachment was scrubbed... URL: From jannyhamy at gmail.com Thu Jun 18 09:06:45 2020 From: jannyhamy at gmail.com (janny hamy) Date: Thu, 18 Jun 2020 01:06:45 -0700 Subject: [Pkg-zsh-devel] =?utf-8?q?=28no_subject=29?= Message-ID: Hello, I am Susanne Klatten from Germany (born April 28, 1962), I am an advertising agency in Frankfurt. I have given 25 percent of my personal fortune to charity and, based on the current situation Covid -19 Virus, provide you with € 500,000.00. Your email was selected via our (E.B.S.) email voting system. The Incorporated Network International teams arrange and collect all email addresses of people who are active online, among the billions that are sent to all emails worldwide. You can also view my link and learn more about me. https://en.wikipedia.org/wiki/Susanne_Klatten Contact me quickly to get directories. Signature. Hallo, ich bin Susanne Klatten aus Deutschland (geb. 28. April 1962), ich bin eine Werbeagentur in Frankfurt. Ich habe 25 Prozent meines persönlichen Vermögens für wohltätige Zwecke gespendet und Ihnen auf der Grundlage der aktuellen Situation des Covid-19-Virus 500.000,00 € zur Verfügung gestellt. Ihre E-Mail wurde über unser E-Mail-Abstimmungssystem (E.B.S.) ausgewählt. Die Teams von Incorporated Network International arrangieren und sammeln alle E-Mail-Adressen von Personen, die online aktiv sind, unter den Milliarden, die an alle E-Mails weltweit gesendet werden. Sie können auch meinen Link anzeigen und mehr über mich erfahren. https://en.wikipedia.org/wiki/Susanne_Klatten Kontaktieren Sie mich schnell, um Verzeichnisse zu erhalten. Unterschrift. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lucas at debian.org Sun Jun 21 21:15:00 2020 From: lucas at debian.org (Lucas Nussbaum) Date: Sun, 21 Jun 2020 22:15:00 +0200 Subject: [Pkg-zsh-devel] Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found Message-ID: <20200621201500.GA30963@xanadu.blop.info> Source: zsh Version: 5.8-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj/Doc' > /bin/sh ../../mkinstalldirs /<>/debian/zsh-common/usr/share/man/man1 > mkdir -m 755 -p -- /<>/debian/zsh-common/usr/share/man/man1 > for file in zsh.1 zshbuiltins.1 zshcalsys.1 zshcompctl.1 zshcompwid.1 zshcompsys.1 zshcontrib.1 zshexpn.1 zshmisc.1 zshmodules.1 zshoptions.1 zshparam.1 zshroadmap.1 zshtcpsys.1 zshzftpsys.1 zshzle.1 zshall.1; do \ > test -s $file || exit 1; \ > /usr/bin/install -c -m 644 $file /<>/debian/zsh-common/usr/share/man/man1/`echo $file | sed 's|zsh|zsh|'` || exit 1; \ > done > make[3]: Leaving directory '/<>/obj/Doc' > make[2]: Leaving directory '/<>/obj' > perl /<>/Util/helpfiles obj/Doc/zshbuiltins.1 debian/zsh-common/usr/share/zsh/help > helpfiles: attempting man obj/Doc/zshbuiltins.1 >debian/zsh-common/usr/share/zsh/help/man.tmp > man: can't execute col: No such file or directory > man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }' > helpfiles: attempting nroff -man obj/Doc/zshbuiltins.1 >debian/zsh-common/usr/share/zsh/help/man.tmp > helpfiles: attempting col -bx debian/zsh-common/usr/share/zsh/help/col.tmp > sh: 1: col: not found > helpfiles: attempting colcrt - debian/zsh-common/usr/share/zsh/help/man.tmp >debian/zsh-common/usr/share/zsh/help/col.tmp > sh: 1: colcrt: not found > helpfiles: col -bx and colcrt - both failed > make[1]: *** [debian/rules:97: override_dh_auto_install-indep] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/zsh_5.8-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. From abe at debian.org Sun Jun 21 22:18:58 2020 From: abe at debian.org (Axel Beckert) Date: Sun, 21 Jun 2020 23:18:58 +0200 Subject: [Pkg-zsh-devel] Bug#963420: Bug#963420: zsh: FTBFS: sh: 1: colcrt: not found In-Reply-To: <20200621201500.GA30963@xanadu.blop.info> References: <20200621201500.GA30963@xanadu.blop.info> <20200621201500.GA30963@xanadu.blop.info> Message-ID: <20200621211857.uoszip3bsrij2lof@sym.noone.org> Hi Lucas, Lucas Nussbaum wrote: > > helpfiles: attempting col -bx debian/zsh-common/usr/share/zsh/help/col.tmp > > sh: 1: col: not found > > helpfiles: attempting colcrt - debian/zsh-common/usr/share/zsh/help/man.tmp >debian/zsh-common/usr/share/zsh/help/col.tmp > > sh: 1: colcrt: not found > > helpfiles: col -bx and colcrt - both failed > > make[1]: *** [debian/rules:97: override_dh_auto_install-indep] Error 1 Thanks for that bug report! This is very likely caused by moving around some binaries between bsdmainutils and util-linux: bsdmainutils (12.1.1) unstable; urgency=medium The "calendar" program, formerly provided in this package, now appears in the separate package "calendar". The tools The tools col, colrm, column, hexdump, and ul are now provided as "bsdextrautils" from the util-linux sources. -- Michael Meskes Wed, 27 May 2020 17:05:02 +0200 And from the changelog of bsdmainutils (12.1.1): * Follow BSD and remove colcrt, it is only useful on very old terminals anyway. >From the message "col -bx and colcrt - both failed" and the fact that col was testet before colcrt, I assume that it suffices to add a build-dependency on bsdextrautils and as alternative a b-d on bsdmainutils << 12.1.1~ to make sure at least col is installed. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From owner at bugs.debian.org Sun Jun 21 22:33:02 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 21 Jun 2020 21:33:02 +0000 Subject: [Pkg-zsh-devel] Processed: tagging 963420 References: <1592775043-2548-bts-abe@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > tags 963420 + confirmed Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Sun Jun 21 22:39:43 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 21 Jun 2020 21:39:43 +0000 Subject: [Pkg-zsh-devel] Processed: Merge duplicates References: <20200621213734.GA6100@localhost> Message-ID: Processing commands for control at bugs.debian.org: > reassign 963327 bsdmainutils 12.1.1 Bug #963327 [src:libstorj] libstorj: FTBFS: configure: error: hexdump is required for tests Bug reassigned from package 'src:libstorj' to 'bsdmainutils'. No longer marked as found in versions libstorj/1.0.3-1. Ignoring request to alter fixed versions of bug #963327 to the same values previously set Bug #963327 [bsdmainutils] libstorj: FTBFS: configure: error: hexdump is required for tests Marked as found in versions bsdmainutils/12.1.1. > reassign 963349 bsdmainutils 12.1.1 Bug #963349 [src:libdap] libdap: FTBFS: /bin/bash: col: command not found Bug reassigned from package 'src:libdap' to 'bsdmainutils'. No longer marked as found in versions libdap/3.20.6-2. Ignoring request to alter fixed versions of bug #963349 to the same values previously set Bug #963349 [bsdmainutils] libdap: FTBFS: /bin/bash: col: command not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963350 bsdmainutils 12.1.1 Bug #963350 [src:slashem] slashem: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:slashem' to 'bsdmainutils'. No longer marked as found in versions slashem/0.0.7E7F3-9. Ignoring request to alter fixed versions of bug #963350 to the same values previously set Bug #963350 [bsdmainutils] slashem: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963353 bsdmainutils 12.1.1 Bug #963353 [src:mcl] mcl: FTBFS: /bin/bash: col: command not found Bug reassigned from package 'src:mcl' to 'bsdmainutils'. No longer marked as found in versions mcl/1:14-137+ds-6. Ignoring request to alter fixed versions of bug #963353 to the same values previously set Bug #963353 [bsdmainutils] mcl: FTBFS: /bin/bash: col: command not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963355 bsdmainutils 12.1.1 Bug #963355 [src:ocp] ocp: FTBFS: /bin/sh: 1: hexdump: not found Bug reassigned from package 'src:ocp' to 'bsdmainutils'. No longer marked as found in versions ocp/1:0.2.2+ds-1. Ignoring request to alter fixed versions of bug #963355 to the same values previously set Bug #963355 [bsdmainutils] ocp: FTBFS: /bin/sh: 1: hexdump: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963359 bsdmainutils 12.1.1 Bug #963359 [src:glhack] glhack: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:glhack' to 'bsdmainutils'. No longer marked as found in versions glhack/1.2-4. Ignoring request to alter fixed versions of bug #963359 to the same values previously set Bug #963359 [bsdmainutils] glhack: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963361 bsdmainutils 12.1.1 Bug #963361 [src:hub] hub: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:hub' to 'bsdmainutils'. No longer marked as found in versions hub/2.7.0~ds1-1. Ignoring request to alter fixed versions of bug #963361 to the same values previously set Bug #963361 [bsdmainutils] hub: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963365 bsdmainutils 12.1.1 Bug #963365 [src:sendmail] sendmail: FTBFS: /bin/sh: 1: ul: not found Bug reassigned from package 'src:sendmail' to 'bsdmainutils'. No longer marked as found in versions sendmail/8.15.2-19. Ignoring request to alter fixed versions of bug #963365 to the same values previously set Bug #963365 [bsdmainutils] sendmail: FTBFS: /bin/sh: 1: ul: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963372 bsdmainutils 12.1.1 Bug #963372 [src:console-setup] console-setup: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:console-setup' to 'bsdmainutils'. No longer marked as found in versions console-setup/1.195. Ignoring request to alter fixed versions of bug #963372 to the same values previously set Bug #963372 [bsdmainutils] console-setup: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963375 bsdmainutils 12.1.1 Bug #963375 [src:conky] conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory Bug reassigned from package 'src:conky' to 'bsdmainutils'. No longer marked as found in versions conky/1.10.8-1.1. Ignoring request to alter fixed versions of bug #963375 to the same values previously set Bug #963375 [bsdmainutils] conky: FTBFS: /usr/bin/man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963376 bsdmainutils 12.1.1 Bug #963376 [src:apcupsd] apcupsd: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:apcupsd' to 'bsdmainutils'. No longer marked as found in versions apcupsd/3.14.14-3. Ignoring request to alter fixed versions of bug #963376 to the same values previously set Bug #963376 [bsdmainutils] apcupsd: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963377 bsdmainutils 12.1.1 Bug #963377 [src:xterm] xterm: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:xterm' to 'bsdmainutils'. No longer marked as found in versions xterm/356-1. Ignoring request to alter fixed versions of bug #963377 to the same values previously set Bug #963377 [bsdmainutils] xterm: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963378 bsdmainutils 12.1.1 Bug #963378 [src:xcolorsel] xcolorsel: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:xcolorsel' to 'bsdmainutils'. No longer marked as found in versions xcolorsel/1.1a-22. Ignoring request to alter fixed versions of bug #963378 to the same values previously set Bug #963378 [bsdmainutils] xcolorsel: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963383 bsdmainutils 12.1.1 Bug #963383 [src:calc] calc: FTBFS: /bin/sh: 5: col: not found Bug reassigned from package 'src:calc' to 'bsdmainutils'. No longer marked as found in versions calc/2.12.7.2-4. Ignoring request to alter fixed versions of bug #963383 to the same values previously set Bug #963383 [bsdmainutils] calc: FTBFS: /bin/sh: 5: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963395 bsdmainutils 12.1.1 Bug #963395 [src:man-db] man-db: FTBFS: dh_auto_test: error: cd debian/build && make -j4 check VERBOSE=1 returned exit code 2 Bug reassigned from package 'src:man-db' to 'bsdmainutils'. No longer marked as found in versions man-db/2.9.2-1. Ignoring request to alter fixed versions of bug #963395 to the same values previously set Bug #963395 [bsdmainutils] man-db: FTBFS: dh_auto_test: error: cd debian/build && make -j4 check VERBOSE=1 returned exit code 2 Marked as found in versions bsdmainutils/12.1.1. > reassign 963403 bsdmainutils 12.1.1 Bug #963403 [src:mp3info] mp3info: FTBFS: /bin/sh: 1: col: not found Bug reassigned from package 'src:mp3info' to 'bsdmainutils'. No longer marked as found in versions mp3info/0.8.5a-2. Ignoring request to alter fixed versions of bug #963403 to the same values previously set Bug #963403 [bsdmainutils] mp3info: FTBFS: /bin/sh: 1: col: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963413 bsdmainutils 12.1.1 Bug #963413 [src:vmem] vmem: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:vmem' to 'bsdmainutils'. No longer marked as found in versions vmem/1.8-1. Ignoring request to alter fixed versions of bug #963413 to the same values previously set Bug #963413 [bsdmainutils] vmem: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963414 bsdmainutils 12.1.1 Bug #963414 [src:latex2rtf] latex2rtf: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:latex2rtf' to 'bsdmainutils'. No longer marked as found in versions latex2rtf/2.3.16-1. Ignoring request to alter fixed versions of bug #963414 to the same values previously set Bug #963414 [bsdmainutils] latex2rtf: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963420 bsdmainutils 12.1.1 Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Bug reassigned from package 'src:zsh' to 'bsdmainutils'. No longer marked as found in versions zsh/5.8-4. Ignoring request to alter fixed versions of bug #963420 to the same values previously set Bug #963420 [bsdmainutils] zsh: FTBFS: sh: 1: colcrt: not found Marked as found in versions bsdmainutils/12.1.1. > reassign 963427 bsdmainutils 12.1.1 Bug #963427 [src:ding] ding: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:ding' to 'bsdmainutils'. No longer marked as found in versions ding/1.8.1-8. Ignoring request to alter fixed versions of bug #963427 to the same values previously set Bug #963427 [bsdmainutils] ding: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963442 bsdmainutils 12.1.1 Bug #963442 [src:pbuilder] pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2 Bug reassigned from package 'src:pbuilder' to 'bsdmainutils'. No longer marked as found in versions pbuilder/0.230.4. Ignoring request to alter fixed versions of bug #963442 to the same values previously set Bug #963442 [bsdmainutils] pbuilder: FTBFS: dh_auto_test: error: make -j4 check returned exit code 2 Marked as found in versions bsdmainutils/12.1.1. > reassign 963448 bsdmainutils 12.1.1 Bug #963448 [src:wiki2beamer] wiki2beamer: FTBFS: man: can't execute col: No such file or directory Bug reassigned from package 'src:wiki2beamer' to 'bsdmainutils'. No longer marked as found in versions wiki2beamer/0.10.0-1. Ignoring request to alter fixed versions of bug #963448 to the same values previously set Bug #963448 [bsdmainutils] wiki2beamer: FTBFS: man: can't execute col: No such file or directory Marked as found in versions bsdmainutils/12.1.1. > reassign 963451 bsdmainutils 12.1.1 Bug #963451 {Done: Samuel Thibault } [src:loadlin] loadlin: FTBFS: /bin/sh: 1: hexdump: not found Bug reassigned from package 'src:loadlin' to 'bsdmainutils'. No longer marked as found in versions loadlin/1.6f-7. No longer marked as fixed in versions loadlin/1.6f-8. Bug #963451 {Done: Samuel Thibault } [bsdmainutils] loadlin: FTBFS: /bin/sh: 1: hexdump: not found Marked as found in versions bsdmainutils/12.1.1. > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 Bug #963327 [bsdmainutils] libstorj: FTBFS: configure: error: hexdump is required for tests Changed Bug title to 'bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1' from 'libstorj: FTBFS: configure: error: hexdump is required for tests'. > affects 963327 src:apcupsd src:calc src:conky src:console-setup src:ding src:glhack src:hub src:latex2rtf src:libdap src:libstorj src:loadlin src:man-db src:mcl src:mp3info src:ocp src:pbuilder src:sendmail src:slashem src:vmem src:wiki2beamer src:xcolorsel src:xterm src:zsh Bug #963327 [bsdmainutils] bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 Added indication that 963327 affects src:apcupsd, src:calc, src:conky, src:console-setup, src:ding, src:glhack, src:hub, src:latex2rtf, src:libdap, src:libstorj, src:loadlin, src:man-db, src:mcl, src:mp3info, src:ocp, src:pbuilder, src:sendmail, src:slashem, src:vmem, src:wiki2beamer, src:xcolorsel, src:xterm, and src:zsh > thanks Stopping processing here. Please contact me if you need assistance. -- 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 963427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963427 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From abe at debian.org Sun Jun 21 23:05:00 2020 From: abe at debian.org (Axel Beckert) Date: Mon, 22 Jun 2020 00:05:00 +0200 Subject: [Pkg-zsh-devel] Processed: Merge duplicates In-Reply-To: References: <20200621213734.GA6100@localhost> Message-ID: <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> Control: unmerge 963420 Control: reassign 963420 src:zsh Control: retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found Control: found 963420 5.8-4 Control: affects 963420 = Dear Adrian, Debian Bug Tracking System wrote: > > reassign 963420 bsdmainutils 12.1.1 > Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found > Bug reassigned from package 'src:zsh' to 'bsdmainutils'. > No longer marked as found in versions zsh/5.8-4. [...] > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 I disagree that this would help in the case of the zsh FTBFS in #963420. And as you might have guessed from my reply to the bug report, I'm already in the process of fixing it. Hence removing it from that mass-bug-merging again. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From owner at bugs.debian.org Sun Jun 21 23:06:29 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 21 Jun 2020 22:06:29 +0000 Subject: [Pkg-zsh-devel] Processed: Re: Processed: Merge duplicates References: <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> <20200621201500.GA30963@xanadu.blop.info> Message-ID: Processing control commands: > unmerge 963420 Bug #963420 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963349 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963353 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963414 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils Disconnected #963420 from all other report(s). > reassign 963420 src:zsh Bug #963420 [bsdmainutils] bsdmainutils must depend on bsdextrautils Bug reassigned from package 'bsdmainutils' to 'src:zsh'. No longer marked as found in versions bsdmainutils/12.1.1. Ignoring request to alter fixed versions of bug #963420 to the same values previously set > retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found Bug #963420 [src:zsh] bsdmainutils must depend on bsdextrautils Changed Bug title to 'zsh: FTBFS: sh: 1: colcrt: not found' from 'bsdmainutils must depend on bsdextrautils'. > found 963420 5.8-4 Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Marked as found in versions zsh/5.8-4. > affects 963420 = Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Removed indication that 963420 affects src:ding, src:man-db, src:sendmail, src:xterm, src:pbuilder, src:mcl, src:mp3info, src:zsh, src:conky, src:libstorj, src:xcolorsel, src:wiki2beamer, src:console-setup, src:loadlin, src:hub, src:vmem, src:libdap, src:calc, src:latex2rtf, src:slashem, src:glhack, src:ocp, and src:apcupsd -- 963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327 963349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963349 963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350 963353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963353 963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355 963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359 963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361 963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365 963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372 963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375 963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376 963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377 963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378 963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383 963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395 963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403 963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413 963414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963414 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442 963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448 963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From bunk at debian.org Sun Jun 21 23:10:30 2020 From: bunk at debian.org (Adrian Bunk) Date: Mon, 22 Jun 2020 01:10:30 +0300 Subject: [Pkg-zsh-devel] Processed: Merge duplicates In-Reply-To: <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> References: <20200621213734.GA6100@localhost> <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> Message-ID: <20200621221030.GF6921@localhost> On Mon, Jun 22, 2020 at 12:05:00AM +0200, Axel Beckert wrote: > Control: unmerge 963420 > Control: reassign 963420 src:zsh > Control: retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found > Control: found 963420 5.8-4 > Control: affects 963420 = > > Dear Adrian, > > Debian Bug Tracking System wrote: > > > reassign 963420 bsdmainutils 12.1.1 > > Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found > > Bug reassigned from package 'src:zsh' to 'bsdmainutils'. > > No longer marked as found in versions zsh/5.8-4. > [...] > > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 > > I disagree that this would help in the case of the zsh FTBFS in > #963420. >... I already updated the title of the mass-merged bug to "bsdmainutils must depend on bsdextrautils". This is anyway mandatory for not breaking upgrades from buster. > Regards, Axel cu Adrian From abe at debian.org Sun Jun 21 23:13:44 2020 From: abe at debian.org (Axel Beckert) Date: Mon, 22 Jun 2020 00:13:44 +0200 Subject: [Pkg-zsh-devel] Processed: Merge duplicates In-Reply-To: <20200621221030.GF6921@localhost> References: <20200621213734.GA6100@localhost> <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> <20200621221030.GF6921@localhost> Message-ID: <20200621221343.nxhstbetask7vfbh@sym.noone.org> Hi Adrian, Adrian Bunk wrote: > > > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 > > > > I disagree that this would help in the case of the zsh FTBFS in > > #963420. > >... > > I already updated the title of the mass-merged bug to > "bsdmainutils must depend on bsdextrautils". Ah, sorry, missed that. > This is anyway mandatory for not breaking upgrades from buster. If you don't mind I'll nevertheless fix that directly in zsh as it will likely come back again as transition after bullseye. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From bunk at debian.org Sun Jun 21 23:10:30 2020 From: bunk at debian.org (Adrian Bunk) Date: Mon, 22 Jun 2020 01:10:30 +0300 Subject: [Pkg-zsh-devel] Bug#963420: Processed: Merge duplicates In-Reply-To: <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> References: <20200621213734.GA6100@localhost> <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> <20200621201500.GA30963@xanadu.blop.info> Message-ID: <20200621221030.GF6921@localhost> On Mon, Jun 22, 2020 at 12:05:00AM +0200, Axel Beckert wrote: > Control: unmerge 963420 > Control: reassign 963420 src:zsh > Control: retitle 963420 zsh: FTBFS: sh: 1: colcrt: not found > Control: found 963420 5.8-4 > Control: affects 963420 = > > Dear Adrian, > > Debian Bug Tracking System wrote: > > > reassign 963420 bsdmainutils 12.1.1 > > Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found > > Bug reassigned from package 'src:zsh' to 'bsdmainutils'. > > No longer marked as found in versions zsh/5.8-4. > [...] > > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 > > I disagree that this would help in the case of the zsh FTBFS in > #963420. >... I already updated the title of the mass-merged bug to "bsdmainutils must depend on bsdextrautils". This is anyway mandatory for not breaking upgrades from buster. > Regards, Axel cu Adrian From abe at debian.org Sun Jun 21 23:13:44 2020 From: abe at debian.org (Axel Beckert) Date: Mon, 22 Jun 2020 00:13:44 +0200 Subject: [Pkg-zsh-devel] Bug#963420: Processed: Merge duplicates In-Reply-To: <20200621221030.GF6921@localhost> References: <20200621213734.GA6100@localhost> <20200621220459.oya7zfnvxtvz3btg@sym.noone.org> <20200621221030.GF6921@localhost> <20200621201500.GA30963@xanadu.blop.info> Message-ID: <20200621221343.nxhstbetask7vfbh@sym.noone.org> Hi Adrian, Adrian Bunk wrote: > > > > retitle 963327 bsdmainutils needs Breaks on util-linux versions without the tools removed in 12.1.1 > > > > I disagree that this would help in the case of the zsh FTBFS in > > #963420. > >... > > I already updated the title of the mass-merged bug to > "bsdmainutils must depend on bsdextrautils". Ah, sorry, missed that. > This is anyway mandatory for not breaking upgrades from buster. If you don't mind I'll nevertheless fix that directly in zsh as it will likely come back again as transition after bullseye. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From abe at debian.org Mon Jun 22 03:24:20 2020 From: abe at debian.org (Axel Beckert) Date: Mon, 22 Jun 2020 04:24:20 +0200 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa Message-ID: <20200622022419.g7mlu33we2imnceq@sym.noone.org> Hi, today I added a debian/salsa-ci.yml file to our zsh git repo to be able to use the generci Gitlab CI pipeline the Debian Salsa CI Team maintains[1]. (I currently see this as an addition to Grml's Jenkins at https://jenkins.grml.org/view/Debian/, but we might decide to only continue to use one of them in the future.) reprotest[2] builds the package under different environment (languages, timezones, etc.) and checks if the resulting packages are identical. Currently two tests fails[3] during the package build as follows: 6583 Running test: unreadable directories can be globbed (users/24619, users/24626) 6584 Test ../../Test/D02glob.ztst failed: test was expected to fail, but passed. 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) 6586 ../../Test/D02glob.ztst: test failed. and 7563 ../../Test/P01privileged.ztst: starting. 7564 Selecting unprivileged UID:EUID pair automatically 7565 Selecting unprivileged GID:EGID pair automatically 7566 Using unprivileged UID 1, EUID 2, GID 1, EGID 2 7567 Running test: PRIVILEGED automatically enabled when RUID != EUID 7568 --- /tmp/zsh.ztst.14839/ztst.err 2020-06-21 13:45:57.442336033 -1200 7569 +++ /tmp/zsh.ztst.14839/ztst.terr 2020-06-21 13:45:57.454336024 -1200 7570 @@ -0,0 +1 @@ 7571 +ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. 7572 Test ../../Test/P01privileged.ztst failed: error output differs from expected as shown above for: 7573 re_zsh $ruid $ruid -1 -1 'echo $UID/$EUID $options[privileged]' 7574 re_zsh $euid $euid -1 -1 'echo $UID/$EUID $options[privileged]' 7575 re_zsh $ruid $euid -1 -1 'echo $UID/$EUID $options[privileged]' 7576 Was testing: PRIVILEGED automatically enabled when RUID != EUID 7577 ../../Test/P01privileged.ztst: test failed. Both seem to be permissions/privileges related, so I wonder what your gut feeling says: * Are these issues with how the Salsa CI works? * Are these issues that Zsh's test suite doesn't properly to detect if an environment allows specific tests to be made. * Are these real bugs in Zsh? My gut feeling currently thinks that the first issue is likely related to how Salsa CI works. And for the second issue my gut feeling says this is either due to how Salsa CI works or that Zsh should have detected this situation and not run that test. Haven't digged much deeper yet, though. [1] https://salsa.debian.org/salsa-ci-team/pipeline/ [2] https://packages.debian.org/unstable/reprotest [3] https://salsa.debian.org/debian/zsh/-/jobs/818139 Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From owner at bugs.debian.org Mon Jun 22 05:21:03 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 22 Jun 2020 04:21:03 +0000 Subject: [Pkg-zsh-devel] Processed: tagging 963420 References: <1592799504-1805-bts-abe@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > # https://salsa.debian.org/debian/zsh/-/commit/d4dedd992a9fcfce3c34a8155425d5d2a5821d77 > tags 963420 + pending Bug #963420 [src:zsh] zsh: FTBFS: sh: 1: colcrt: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From d.s at daniel.shahaf.name Tue Jun 23 13:18:30 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Tue, 23 Jun 2020 12:18:30 +0000 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa In-Reply-To: <20200622022419.g7mlu33we2imnceq@sym.noone.org> References: <20200622022419.g7mlu33we2imnceq@sym.noone.org> Message-ID: <20200623121830.75f75a45@tarpaulin.shahaf.local2> Axel Beckert wrote on Mon, 22 Jun 2020 04:24 +0200: > * Are these issues with how the Salsa CI works? > * Are these issues that Zsh's test suite doesn't properly to detect if > an environment allows specific tests to be made. > * Are these real bugs in Zsh? > 6583 Running test: unreadable directories can be globbed (users/24619, users/24626) > 6584 Test ../../Test/D02glob.ztst failed: test was expected to fail, but passed. > 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) > 6586 ../../Test/D02glob.ztst: test failed. > > My gut feeling currently thinks that the first issue is likely related > to how Salsa CI works. This test checks unreadable/unexecutable directories are included in glob expansions. It doesn't try to read the contents of those directories. Which is to say, this isn't the run-of-the-mill scenario where a test creates a mode-000 directory, expects to fail to read it, and XPASSes when run with superuser privileges on some systems. Rather, this test point tests a bug in zsh that only manifests when privilege restrictions _are_ in effect. The test passes only on Salsa and fails as expected everywhere else (that's what the output says, though it's not immediately clear), it is plausible that the reason for the difference has to do with how Salsa runs the tests. The bug which the test tests for was fixed upstream in workers/45291. > 7563 ../../Test/P01privileged.ztst: starting. > 7564 Selecting unprivileged UID:EUID pair automatically > 7565 Selecting unprivileged GID:EGID pair automatically > 7566 Using unprivileged UID 1, EUID 2, GID 1, EGID 2 > 7567 Running test: PRIVILEGED automatically enabled when RUID != EUID > 7568 --- /tmp/zsh.ztst.14839/ztst.err 2020-06-21 13:45:57.442336033 -1200 > 7569 +++ /tmp/zsh.ztst.14839/ztst.terr 2020-06-21 13:45:57.454336024 -1200 > 7570 @@ -0,0 +1 @@ > 7571 +ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. > 7572 Test ../../Test/P01privileged.ztst failed: error output differs from expected as shown above for: > 7573 re_zsh $ruid $ruid -1 -1 'echo $UID/$EUID $options[privileged]' > 7574 re_zsh $euid $euid -1 -1 'echo $UID/$EUID $options[privileged]' > 7575 re_zsh $ruid $euid -1 -1 'echo $UID/$EUID $options[privileged]' > 7576 Was testing: PRIVILEGED automatically enabled when RUID != EUID > 7577 ../../Test/P01privileged.ztst: test failed. > > And for the second issue my gut feeling says this is either due to how > Salsa CI works or that Zsh should have detected this situation and not > run that test. The test fails because the test harness was invoked with an invalid LD_PRELOAD value. zsh's build system did not set up the libeatmydata.so preloading, so I don't see why it should have skipped the test. Questions: - What set up eatmydata? - Why did the test fail with that error? - Why did other *.ztst files _not_ fail? Cheers, Daniel From d.s at daniel.shahaf.name Tue Jun 23 13:36:50 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Tue, 23 Jun 2020 12:36:50 +0000 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa In-Reply-To: <20200623121830.75f75a45@tarpaulin.shahaf.local2> References: <20200622022419.g7mlu33we2imnceq@sym.noone.org> <20200623121830.75f75a45@tarpaulin.shahaf.local2> Message-ID: <20200623123650.5b41c553@tarpaulin.shahaf.local2> Daniel Shahaf wrote on Tue, 23 Jun 2020 12:18 +0000: > Axel Beckert wrote on Mon, 22 Jun 2020 04:24 +0200: > > 6583 Running test: unreadable directories can be globbed (users/24619, users/24626) > > 6584 Test ../../Test/D02glob.ztst failed: test was expected to fail, but passed. > > 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) > > 6586 ../../Test/D02glob.ztst: test failed. > > (that's what the output says, though it's not immediately clear), Patch sent upstream: workers/46102. Cheers, Daniel From d.s at daniel.shahaf.name Tue Jun 23 14:22:00 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Tue, 23 Jun 2020 13:22:00 +0000 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa In-Reply-To: <20200623121830.75f75a45@tarpaulin.shahaf.local2> References: <20200622022419.g7mlu33we2imnceq@sym.noone.org> <20200623121830.75f75a45@tarpaulin.shahaf.local2> Message-ID: <5c9d5128-f1ab-4e61-b607-98c8eaae6f27@www.fastmail.com> Daniel Shahaf wrote on Tue, 23 Jun 2020 12:18 +00:00: > Axel Beckert wrote on Mon, 22 Jun 2020 04:24 +0200: > > 7563 ../../Test/P01privileged.ztst: starting. > > 7564 Selecting unprivileged UID:EUID pair automatically > > 7565 Selecting unprivileged GID:EGID pair automatically > > 7566 Using unprivileged UID 1, EUID 2, GID 1, EGID 2 > > 7567 Running test: PRIVILEGED automatically enabled when RUID != EUID > > 7568 --- /tmp/zsh.ztst.14839/ztst.err 2020-06-21 13:45:57.442336033 -1200 > > 7569 +++ /tmp/zsh.ztst.14839/ztst.terr 2020-06-21 13:45:57.454336024 -1200 > > 7570 @@ -0,0 +1 @@ > > 7571 +ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. > > 7572 Test ../../Test/P01privileged.ztst failed: error output differs from expected as shown above for: > > 7573 re_zsh $ruid $ruid -1 -1 'echo $UID/$EUID $options[privileged]' > > 7574 re_zsh $euid $euid -1 -1 'echo $UID/$EUID $options[privileged]' > > 7575 re_zsh $ruid $euid -1 -1 'echo $UID/$EUID $options[privileged]' > > 7576 Was testing: PRIVILEGED automatically enabled when RUID != EUID > > 7577 ../../Test/P01privileged.ztst: test failed. > > > > And for the second issue my gut feeling says this is either due to how > > Salsa CI works or that Zsh should have detected this situation and not > > run that test. > > The test fails because the test harness was invoked with an invalid > LD_PRELOAD value. zsh's build system did not set up the libeatmydata.so > preloading, so I don't see why it should have skipped the test. > > Questions: > > - What set up eatmydata? > > - Why did the test fail with that error? > > - Why did other *.ztst files _not_ fail? I guess libeatmydata.so failed to be opened because the uid/gid had been changed. That'd answer the third question. However, for the second question, why did libeatmydata.so fail to be opened? Normally eatmydata would be installed root:wheel 0555, in which case it'd be usable even after changing the uid and gid. Cheers, Daniel From danielsh at apache.org Tue Jun 23 16:21:33 2020 From: danielsh at apache.org (Daniel Shahaf) Date: Tue, 23 Jun 2020 15:21:33 +0000 Subject: [Pkg-zsh-devel] Bug#960298: Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream In-Reply-To: <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> References: <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> Message-ID: <20200623152133.52041e25@tarpaulin.shahaf.local2> Control: tags -1 pending Daniel Shahaf wrote on Mon, 11 May 2020 15:58 +0000: > It was posted in 45724, revised and committed in 45731, and has had an > unposted followup afterwards. I looked again and I can't find an unposted followup, so at Axel's suggestion I pushed a backport of 45731 to the packaging repository. Cheers, Daniel From owner at bugs.debian.org Tue Jun 23 16:24:04 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 23 Jun 2020 15:24:04 +0000 Subject: [Pkg-zsh-devel] Processed: Re: Bug#960298: zsh-common: Please consider backporting new debsnap completion from upstream References: <20200623152133.52041e25@tarpaulin.shahaf.local2> <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> Message-ID: Processing control commands: > tags -1 pending Bug #960298 [zsh-common] zsh-common: Please consider backporting new debsnap completion from upstream Added tag(s) pending. -- 960298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960298 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From abe at debian.org Tue Jun 23 16:25:33 2020 From: abe at debian.org (Axel Beckert) Date: Tue, 23 Jun 2020 17:25:33 +0200 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa In-Reply-To: <20200623123650.5b41c553@tarpaulin.shahaf.local2> <20200623121830.75f75a45@tarpaulin.shahaf.local2> Message-ID: <20200623152533.7tjgo5ujs2y4jqg7@sym.noone.org> Hi Daniel, thanks a lot for looking into this. Daniel Shahaf wrote: > > 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) > > 6586 ../../Test/D02glob.ztst: test failed. > > > > My gut feeling currently thinks that the first issue is likely related > > to how Salsa CI works. > > This test checks unreadable/unexecutable directories are included in > glob expansions. It doesn't try to read the contents of those directories. > > Which is to say, this isn't the run-of-the-mill scenario where a test > creates a mode-000 directory, expects to fail to read it, and XPASSes > when run with superuser privileges on some systems. Rather, this test > point tests a bug in zsh that only manifests when privilege restrictions > _are_ in effect. Ok. Yay, I found a bug! ;-) > The test passes only on Salsa and fails as expected everywhere else > (that's what the output says, though it's not immediately clear), Yes, I was aware of this. I don't care if the test needs a "not" in front or not. :-) > it is plausible that the reason for the difference has to do with > how Salsa runs the tests. Ack. > The bug which the test tests for was fixed upstream in workers/45291. This seems to have been short before the 5.8 release and is hence included, right? > > 7576 Was testing: PRIVILEGED automatically enabled when RUID != EUID > > 7577 ../../Test/P01privileged.ztst: test failed. > > > > And for the second issue my gut feeling says this is either due to how > > Salsa CI works or that Zsh should have detected this situation and not > > run that test. > > The test fails because the test harness was invoked with an invalid > LD_PRELOAD value. zsh's build system did not set up the libeatmydata.so > preloading, so I don't see why it should have skipped the test. > > Questions: > > - What set up eatmydata? Likely the container in which the test was run, i.e. either Salsa's CI itself or the pipeline defined by the Salsa CI Team. > - Why did the test fail with that error? Good question. > - Why did other *.ztst files _not_ fail? Even better question! Daniel Shahaf wrote: > > > 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) > > > 6586 ../../Test/D02glob.ztst: test failed. > > > > (that's what the output says, though it's not immediately clear), > > Patch sent upstream: workers/46102. Hmmm, I don't get that patch. But maybe because understanding the output was not my issue. :-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE From d.s at daniel.shahaf.name Tue Jun 23 16:40:30 2020 From: d.s at daniel.shahaf.name (Daniel Shahaf) Date: Tue, 23 Jun 2020 15:40:30 +0000 Subject: [Pkg-zsh-devel] zsh test suite failures under reprotest on Salsa In-Reply-To: <20200623152533.7tjgo5ujs2y4jqg7@sym.noone.org> References: <20200623121830.75f75a45@tarpaulin.shahaf.local2> <20200623152533.7tjgo5ujs2y4jqg7@sym.noone.org> Message-ID: <20200623154030.21b1ed91@tarpaulin.shahaf.local2> Axel Beckert wrote on Tue, 23 Jun 2020 17:25 +0200: > Daniel Shahaf wrote: > > The bug which the test tests for was fixed upstream in workers/45291. > > This seems to have been short before the 5.8 release and is hence > included, right? That change is not included in the 5.8 release because it was pushed to a different branch than 5.8 was tagged from. (The use of branches before the 5.8 release is described in workers/45441, though a bit briefly.) It will, however, be included in 5.9. > > > 7576 Was testing: PRIVILEGED automatically enabled when RUID != EUID > > > 7577 ../../Test/P01privileged.ztst: test failed. > > > > > > And for the second issue my gut feeling says this is either due to how > > > Salsa CI works or that Zsh should have detected this situation and not > > > run that test. > > > > The test fails because the test harness was invoked with an invalid > > LD_PRELOAD value. zsh's build system did not set up the libeatmydata.so > > preloading, so I don't see why it should have skipped the test. > > > > Questions: > > > > - What set up eatmydata? > > Likely the container in which the test was run, i.e. either Salsa's CI > itself or the pipeline defined by the Salsa CI Team. > *nod* > > - Why did the test fail with that error? > > Good question. > > > - Why did other *.ztst files _not_ fail? > > Even better question! > I wonder if perhaps eatmydata was installed in the user-that-runs-the-build's home directory. > Daniel Shahaf wrote: > > > > 6585 Was testing: unreadable directories can be globbed (users/24619, users/24626) > > > > 6586 ../../Test/D02glob.ztst: test failed. > > > > > > (that's what the output says, though it's not immediately clear), > > > > Patch sent upstream: workers/46102. > > Hmmm, I don't get that patch. But maybe because understanding the > output was not my issue. :-) The point of that patch is to make line 6586 say "Test XPassed" rather than "Test failed", because the latter normally connotes that the test had been expected to pass. Cheers, Daniel From owner at bugs.debian.org Tue Jun 23 18:15:05 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 23 Jun 2020 17:15:05 +0000 Subject: [Pkg-zsh-devel] Processed: Bug#960298 marked as pending in zsh References: <5ef2377df0d5e_3f03fb11e05a424957b9@godard.mail> <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> Message-ID: Processing control commands: > tag -1 pending Bug #960298 [zsh-common] zsh-common: Please consider backporting new debsnap completion from upstream Ignoring request to alter tags of bug #960298 to the same tags previously set -- 960298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960298 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From sirjakes11 at gmail.com Tue Jun 30 00:10:49 2020 From: sirjakes11 at gmail.com (sir jakes) Date: Mon, 29 Jun 2020 16:10:49 -0700 Subject: [Pkg-zsh-devel] =?utf-8?q?=28no_subject=29?= Message-ID: -- *Vom Schreibtisch von: Visa® Inc.900 Metro Center Blvd.Foster City, CA 94404-2172.* Lieber glücklicher Gewinner! Herzliche Glückwünsche! Wir möchten Sie demütig darüber informieren, dass Sie unter den 10.000.000 glücklichen Kunden ausgewählt wurden, die die Summe der Covid-19-Virus-Lotterie 2020 in Höhe von 2.969.775 (zwei Millionen, neunhundertneunundsechzigtausend und siebenhundertfünfundsiebzig Euro) gewonnen haben für dich. Diese nationale Lotterie- / Lotto-Aktion wurde von Visa USA Incorporated organisiert und gesponsert, um die neuen Vorteile der Visa® Card für Reisende und Geschäftsinhaber einzuführen. Die Gewinner der internationalen Lotterie von Visa United States Incorporated Network wurden über das EBS-E-Mail-Abstimmungssystem (EBS) ausgewählt. Die Teams von Visa United States Incorporated Network International organisieren und sammeln alle E-Mail-Adressen von Personen, die online aktiv sind. Unter den Milliarden, die alle globalen E-Mail-Netzwerke abonniert haben, wählen wir nur neun (10.000.000) Kandidaten pro Jahr als Gewinner aus . Diese nationale Lotterie sollte Familien und Gemeinden bei der aktuellen globalen Krise des Covid-19-Virus helfen und auch dazu beitragen, die Armut in der globalen Welt aufgrund des Corona-Virus zu verringern. Sie wurden ausgewählt und haben den Preis erhalten. Bleiben Sie in Verbindung. Von der Förderung der finanziellen Eingliederung bis hin zur Unterstützung in Krisenzeiten setzen wir unsere Produkte, unser Know-how und unsere Philanthropie ein, um positive Veränderungen herbeizuführen. Dieses Angebot steht Ihnen nur in dieser Saison zur Verfügung und Sie werden automatisch bezahlt. Dieser Lotteriepreis muss spätestens (5) Werktage nach dem Datum der Bekanntgabe nach dem Ziehungsdatum, an dem der Preis gewonnen wurde, geltend gemacht werden. Alle Preisabrechnungen müssen eingelöst werden, Gewinner müssen in der staatlichen Gerichtsbarkeit oder im Abrechnungszentrum ausgezahlt werden und alle Preise, die nicht innerhalb der Frist von (5) beansprucht werden, verfallen. Wenden Sie sich an Ihren Schadenverwalter / -agenten und befolgen Sie dessen Richtlinien. Ansprechpartner: -------- Frau Glenda Hartwell (Verwaltungsbeamte) E-Mail-Adresse: --------- visalortteryinc at gmail.com Gebührenfreie Nummer: ------------ + 1 (57) 528-2722 Bitte wenden Sie sich innerhalb der 24-Stunden-Arbeitszeit per E-Mail / Telefon an Ihren Schadenregulierer und an Ihre Co-Branded Visa®-Karte. Senden Sie die folgenden Informationen an die oben angegebene E-Mail-Adresse, um die Zahlung Ihres Gewinnpreises mit dem Bestellten zu erleichtern und zu verarbeiten zahlende Bank. Ticket Nr.: 51 79 4 58 1 0 Gewinnnummer: 1 39 48 11 67 18 26 Referenznummer: MMV-SF71271-00-18VINC Registrierungsnummer: MMLV-W73-3L2019 Geschäftsführer: Alfred F Kelly Jr. *MACHT FÜR SIE. Fühlen Sie sich wie zu Hause und machen Sie die Visa Corporation zu Ihrem © Copyright 1996-2020. Visa Lotterie Alle Rechte vorbehalten.BLEIB SICHER!!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From ftpmaster at ftp-master.debian.org Tue Jun 30 17:13:36 2020 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Tue, 30 Jun 2020 16:13:36 +0000 Subject: [Pkg-zsh-devel] Processing of zsh_5.8-5_source.changes Message-ID: zsh_5.8-5_source.changes uploaded successfully to localhost along with the files: zsh_5.8-5.dsc zsh_5.8-5.debian.tar.xz zsh_5.8-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Tue Jun 30 17:19:40 2020 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Tue, 30 Jun 2020 16:19:40 +0000 Subject: [Pkg-zsh-devel] zsh_5.8-5_source.changes ACCEPTED into unstable Message-ID: Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 30 Jun 2020 17:42:41 +0200 Source: zsh Architecture: source Version: 5.8-5 Distribution: unstable Urgency: medium Maintainer: Debian Zsh Maintainers Changed-By: Axel Beckert Closes: 960298 963420 Changes: zsh (5.8-5) unstable; urgency=medium . [ Axel Beckert ] * [75eb3334] Retroactively mention #928194 in 5.8-1 changelog entry. * [d4dedd99] Adapt to "col" having been moved from bsdmainutils to bsdextrautils. (Closes: #963420) * [71a1b8a4] Try to fix cross-installability of run-testsuite autopkgtest check. * [dc40a872] Add a minimal debian/salsa-ci.yml file. * [27586e0e] Bump debhelper compatibility level to 13. * [c2242d6d] Cherry-pick 754658af from upstream to fix "git stash drop" tab-completion. * [eda6cb4d] Update lintian overrides wrt. renamed lintian tags. . [ Daniel Shahaf ] * [49dbae2c] Retroactively close #740587 in 5.2-test-1-1. * [e8d6bb61] Cherry-pick d128bc0b from upstream: 45731: _debsnap: New completion function (Closes: #960298) Checksums-Sha1: f22585436490d1bcd974ecc5723cfd6d288368d7 2801 zsh_5.8-5.dsc 34c06fcc6ec8ac83b664067c7fdd7fb3dbb05066 88812 zsh_5.8-5.debian.tar.xz 9d62efad32b7aee9f0cd350c5ee6d57b48cfb25f 8906 zsh_5.8-5_source.buildinfo Checksums-Sha256: 5419a72f36c549d66f973a287f6855cb07dc919c9c489ecd6746228d9c855917 2801 zsh_5.8-5.dsc 057ab99dad213010019a0488a7824f9c9bbe59a1769b7ed7ec4d3563e8525859 88812 zsh_5.8-5.debian.tar.xz f552d7d8dbf7e6852aaf1e7cc4a01f8176f52360c2829f60782cd693f8f0e85d 8906 zsh_5.8-5_source.buildinfo Files: e0630b470b48f0a772e7ab8f0b8313b9 2801 shells optional zsh_5.8-5.dsc 564b0fb57f19acf24fd1b7692fcdb083 88812 shells optional zsh_5.8-5.debian.tar.xz d8389a5528d0c3afd1bb45a4b6e470da 8906 shells optional zsh_5.8-5_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAl77YBIACgkQa+Zjx1o1 yXXpjRAAnih5w8ihWR750RAfZ1Hn7O2BCYeZZtPG3HqQYeWZCwGErO63wggxqZsx coRZ367+1VHPWWQoRW3gPA27IU2IptXJm3SSgkB6i41c1neUxceal2gwB5/jbeR2 KkBaKVHuK2VC1ZnThWuoRn2BXvaKdXu1rt05w3PBZONtIoAWgG6yL8px+m8HIMZ4 m6qStVRmWjUW9DYLqZwIyYDAhEh8PEvssn/7MsBaIDS4ZkUkljvaZdbH2+kzJMZ1 frR+aoxcVULL8/6LBkAX8G/0+pAO5XQeSXBzUs1IY89yKOuA+8RQbDPGwYXsn2kE bhD7/wK0gjxyExMRw+UookCsuY/Dl2DNO1CkY5XZ2Zk6beAUThuv0o20AEe5dMUJ odEQilEE730rBQnITw4DlcKuRQSDAduTIwWHEdAiQm4j8LbSLcIxfp4cG35ANXgr GlAwSCkm9P7J4Kfl+wqUf3DlDjZWr2l6YazFBAqjeCEc30c0aJfrb3qzNYN/Otcj p5q+dVt+mZRAgVscgssNSB3jXZn5GkabjeK9cYDDzNAPRsOyOqQOPeIwXZrFvQlX vfxECpfOXInBi8msiWN/RzhmvFf1LWe9+6OqixWZuz0GpemRQdTQiPPhUTn6BZXN kI3ZjKf1Kw/BYUlKKsw98xyvP9VZl9TjQLIgO5niPV+0r7BKu7o= =vyaE -----END PGP SIGNATURE----- Thank you for your contribution to Debian. From owner at bugs.debian.org Tue Jun 30 17:21:06 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 30 Jun 2020 16:21:06 +0000 Subject: [Pkg-zsh-devel] Bug#960298: marked as done (zsh-common: Please consider backporting new debsnap completion from upstream) References: <158921273272.17333.3774902273842372804.reportbug@tarpaulin.shahaf.local2> Message-ID: Your message dated Tue, 30 Jun 2020 16:19:40 +0000 with message-id and subject line Bug#960298: fixed in zsh 5.8-5 has caused the Debian Bug report #960298, regarding zsh-common: Please consider backporting new debsnap completion from upstream 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 owner at bugs.debian.org immediately.) -- 960298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960298 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Daniel Shahaf Subject: zsh-common: Please consider backporting new debsnap completion from upstream Date: Mon, 11 May 2020 15:58:52 +0000 Size: 4095 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#960298: fixed in zsh 5.8-5 Date: Tue, 30 Jun 2020 16:19:40 +0000 Size: 5753 URL: From owner at bugs.debian.org Tue Jun 30 17:21:08 2020 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 30 Jun 2020 16:21:08 +0000 Subject: [Pkg-zsh-devel] Bug#963420: marked as done (zsh: FTBFS: sh: 1: colcrt: not found) References: <20200621201500.GA30963@xanadu.blop.info> Message-ID: Your message dated Tue, 30 Jun 2020 16:19:40 +0000 with message-id and subject line Bug#963420: fixed in zsh 5.8-5 has caused the Debian Bug report #963420, regarding zsh: FTBFS: sh: 1: colcrt: not found 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 owner at bugs.debian.org immediately.) -- 963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Lucas Nussbaum Subject: zsh: FTBFS: sh: 1: colcrt: not found Date: Sun, 21 Jun 2020 22:15:00 +0200 Size: 3967 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#963420: fixed in zsh 5.8-5 Date: Tue, 30 Jun 2020 16:19:40 +0000 Size: 5778 URL: