From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id wAMDIEIt028427 for ; Thu, 22 Nov 2018 08:18:14 -0500 Received: by smtp.corp.redhat.com (Postfix) id 6377B604CD; Thu, 22 Nov 2018 13:18:14 +0000 (UTC) Received: from mx1.redhat.com (ext-mx14.extmail.prod.ext.phx2.redhat.com [10.5.110.43]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5715A605AF for ; Thu, 22 Nov 2018 13:18:11 +0000 (UTC) Received: from mail-oi1-f181.google.com (mail-oi1-f181.google.com [209.85.167.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id BD0D73097071 for ; Thu, 22 Nov 2018 13:18:10 +0000 (UTC) Received: by mail-oi1-f181.google.com with SMTP id a77so7438584oii.5 for ; Thu, 22 Nov 2018 05:18:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=XztuQMMhQQjfZkXmbaYA7DM0iinx5EIkrfXgL182dWg=; b=SLPnK2acS4FzXnhMPPZCyTyP/PM2HE6/SQ5+2+L+JDO7KIfkQ8IGC+mPjU2Zoxmoay DGB4mxLKb77a8YVLbtfLPADIog2POlDqbEmkOa22yyrxTbo8LPs7ZDqLlQSLthAKTwks JWd0DCRxRXHmk2NFauck+eiU4VDfVzZuBoxIG5qBJoUeneLgvJpxkJ0pa0F6PyNf0uZZ gNaoY3Em2yOqZ2hZJeNA3rDTeOQkYc7HlwmJWD4yMaomWwHMcOZMQstUw2de4Q+7fmG8 7unp6pv9Ej79TUZUnlImYGwAtMegEbavbrMiT0fkw3euw+GUNnkngIVooRPWY2i4zOfP yZwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=XztuQMMhQQjfZkXmbaYA7DM0iinx5EIkrfXgL182dWg=; b=ERgFgshZhKxNIIeLxN5wh8dfYCPJCpGEdG8UNQJHKKUXr6th2P246Sfo9o3up/I+px m+7/Xf1uvV2K2eOPsgEP0BBGuz1617O9AcZlmYUdU3PIpYhpGDMhOdQRa63C8fT4HSJY UxYYajcQEpnuA/ILLLU0gZUOwyWxyrShZLNNelBiusgcLz7eaaLoBtOFwV/WZCm/NbwJ wsQ90XvRlRlg5GanoBeK9CThl5YwaaQVEudtTRMBmZ44moRkXC/qfnsbH+ANzOZqebYe Z8qWZIVaOGAgUMrFSmTRePBdCMbwGmMF4AbqXaAqsNEoQFSDfitP7nvUKAYV8BjOwUei QjsA== X-Gm-Message-State: AGRZ1gKpi8bvLy/JVBIrgA4RfeYEHoOAPhepLZ7UyPIX9tlOWBPZP09B oJieWX7Bbe2imppTVvmlniegpkHAYH4j5Fptm9pHN+r/ X-Google-Smtp-Source: AJdET5elGP7t5VsCkonazkq20Pvlnu65qitw9pRlxeWacsMkJcGq7EmcZLeFc4zsLy0tfECpRz2WVwmCWqbLx8Om7us= X-Received: by 2002:aca:3506:: with SMTP id c6-v6mr5783912oia.308.1542892689764; Thu, 22 Nov 2018 05:18:09 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a9d:541a:0:0:0:0:0 with HTTP; Thu, 22 Nov 2018 05:18:09 -0800 (PST) In-Reply-To: References: Date: Thu, 22 Nov 2018 13:18:09 +0000 Message-ID: Subject: Re: apt-get error with espeakup To: blinux-list@redhat.com Content-Type: text/plain; charset="UTF-8" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Thu, 22 Nov 2018 13:18:10 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.43]); Thu, 22 Nov 2018 13:18:10 +0000 (UTC) for IP:'209.85.167.181' DOMAIN:'mail-oi1-f181.google.com' HELO:'mail-oi1-f181.google.com' FROM:'mewtamer@gmail.com' RCPT:'' X-RedHat-Spam-Score: -0.11 (DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_PASS) 209.85.167.181 mail-oi1-f181.google.com 209.85.167.181 mail-oi1-f181.google.com X-Scanned-By: MIMEDefang 2.84 on 10.5.110.43 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-loop: blinux-list@redhat.com From: Linux for blind general discussion X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: blinux-list@redhat.com List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2018 13:18:14 -0000 For what it's worth, installation and removal scripts are stored in /var/lib/dpkg/info, are named after the package they belong to and have the following extensions: .preinst: pre installation. .postinst: post installation. .prerm: pre removal. .postrm: post removal. and the .list files in those directories list all the files on the system that belong to that page. removing a script that failed will cause dpkg to ignore it the next time you attempt the package operation that ran the script, but I'm not sure this is advisable if you plan to try compiling the package your trying to remove from source. Also, removing a package's entry from /var/lib/dpkg/status will render it invisible to apt/dpkg/most apt frontends, but again, not sure if advisable, and errors in the status file will make apt/dpkg refuse to do anything until its fixed. Messing with this stuff is quite hackerish, and even if it solves the immediate problem, there's no guarantee it won't cause bigger problems down the line. -- Sincerely, Jeffery Wright Bachelor of Computer Science President Emeritus, Nu Nu Chapter, Phi Theta Kappa.