[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#929836: marked as done (apt: export/exportall commands apparently useless if not parsable)

Your message dated Tue, 9 Jul 2019 09:27:21 +0200
with message-id <20190709092547.GA27000@debian.org>
and subject line Re: Bug#929836: apt: export/exportall commands apparently useless if not parsable
has caused the Debian Bug report #929836,
regarding apt: export/exportall commands apparently useless if not parsable
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@bugs.debian.org
immediately.)


-- 
929836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929836
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.8.2
Severity: minor

Dear Maintainer,

I have a script that runs "apt-key exportall" for backup-reasons. The
command diverts output to a file, and now outputs the following warning:

   Warning: apt-key output should not be parsed (stdout is not a terminal)

That begs the question what export/exportall are meant for - their output
is clearly NOT human-readable but computer-parsable. If the output
is not meant to be parsed (presumably by computer program), and not
human-readable, do they have a purpose at all?

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt depends on:
ii  adduser                 3.118
ii  debian-archive-keyring  2019.1
ii  gpgv                    2.2.12-1
ii  libapt-pkg5.0           1.8.2
ii  libc6                   2.28-10
ii  libgcc1                 1:8.3.0-6
ii  libgnutls30             3.6.7-3
ii  libseccomp2             2.3.3-4
ii  libstdc++6              8.3.0-6

Versions of packages apt recommends:
ii  ca-certificates  20190110

Versions of packages apt suggests:
pn  apt-doc         <none>
ii  aptitude        0.8.11-7
ii  dpkg-dev        1.19.6
ii  gnupg           2.2.12-1
ii  gnupg2          2.2.12-1
ii  powermgmt-base  1.34
ii  synaptic        0.84.6

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Jun 01, 2019 at 03:35:32PM +0200, Marc Lehmann wrote:
> Package: apt
> Version: 1.8.2
> Severity: minor
> 
> Dear Maintainer,
> 
> I have a script that runs "apt-key exportall" for backup-reasons. The
> command diverts output to a file, and now outputs the following warning:
> 
>    Warning: apt-key output should not be parsed (stdout is not a terminal)
> 
> That begs the question what export/exportall are meant for - their output
> is clearly NOT human-readable but computer-parsable. If the output
> is not meant to be parsed (presumably by computer program), and not
> human-readable, do they have a purpose at all?

apt-key is a legacy tool, just don't use it. It might not even work,
as it requires gpg for these things but does not depend on it. 

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--- End Message ---
Reply to: