Date: Sun, 28 Oct 2018 12:44:18 -0700 From: David Wolfskill <david@catwhisker.org> To: freebsd-ports@freebsd.org Subject: Silent failure of 'pkg upgrade' Message-ID: <20181028194418.GB1242@albert.catwhisker.org>
next in thread | raw e-mail | index | archive | help
--i0/AhcQY5QxfSsSZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Since July, 2015, I have been updating my "production" machines here at
home on a weekly basis; for the ports/packages phase of this, I have
been using poudriere (on a dedicated "build machine") to build packages
for the production machines.
Overall, this approach has been working quite well.
Thus, I was rather surprised to find after this morning's update that
the packages had actually not been updated at all.
Reviewing the typescript, I see that sailent parts of it read:
=2E..
Checking integrity... done (0 conflicting)
The following 47 package(s) will be affected (of 0 checked):
Installed packages to be REMOVED:
webkit-gtk2-2.4.11_17
webkit2-gtk3-2.20.5
gvfs-1.30.4
gnome-online-accounts-3.28.0
libgdata-0.17.9
Installed packages to be UPGRADED:
tmux: 2.7 -> 2.8
tesseract: 3.05.02_2 -> 3.05.02_3
sqlite3: 3.25.1 -> 3.25.1_1
spidermonkey52: 52.8.0_1 -> 52.8.0_2
qtchooser: 39 -> 66
qt5-core: 5.11.2 -> 5.11.2_1
python36: 3.6.6_1 -> 3.6.7
py27-openssl: 17.5.0_1 -> 18.0.0
py27-libxml2: 2.9.7 -> 2.9.7_1
py27-gimp: 2.8.22_1 -> 2.10.6_1
portmaster: 3.19_15 -> 3.19_18
pkgconf: 1.5.3,1 -> 1.5.4,1
pciids: 20180921 -> 20181027
nss: 3.39 -> 3.40
netpbm: 10.83.02 -> 10.84.02
net-snmp: 5.7.3_18 -> 5.7.3_19
neon: 0.30.2_3 -> 0.30.2_4
mesa-dri: 18.1.9 -> 18.1.9_1
llvm60: 6.0.1_2 -> 6.0.1_3
linux-c6: 6.9_1 -> 6.10_1
libdvdcss: 1.4.1 -> 1.4.2
icu: 62.1_2,1 -> 63.1,1
help2man: 1.47.7 -> 1.47.8
harfbuzz-icu: 2.0.0 -> 2.0.2_1
harfbuzz: 2.0.0 -> 2.0.2
gtk-doc: 1.28 -> 1.29
gpgme: 1.11.1 -> 1.12.0
glib: 2.56.1_1,1 -> 2.56.1_2,1
gimp-app: 2.8.22_1,1 -> 2.10.6_1,1
gimp: 2.8.22,2 -> 2.10.6,2
freeglut: 3.0.0_1 -> 3.0.0_2
firefox: 62.0.3,1 -> 63.0_3,1
ffmpeg: 4.0.2_5,1 -> 4.0.2_7,1
dovecot: 2.3.3 -> 2.3.3_2
ca_root_nss: 3.39 -> 3.40
boost-libs: 1.68.0_1 -> 1.68.0_2
bind911: 9.11.4P2 -> 9.11.5
apr: 1.6.3.1.6.1_1 -> 1.6.5.1.6.1
apache24: 2.4.35 -> 2.4.37
Installed packages to be REINSTALLED:
nut-2.7.4_8 (options changed)
linux-c6-qt47-webkit-4.7.2_4 (direct dependency changed: linux-c6-q=
t47-x11)
gimp-gutenprint-5.2.14 (needed shared library changed)
Number of packages to be removed: 5
Number of packages to be upgraded: 39
Number of packages to be reinstalled: 3
The operation will free 121 MiB.
Proceed with this action? [y/N]: y
=2E..
[17/47] Upgrading gimp-app from 2.8.22_1,1 to 2.10.6_1,1...
[17/47] Extracting gimp-app-2.10.6_1,1: 0%^M[17/47] Extracting gimp-app-2=
=2E10.6_1,1: 0%^M[17/47] Extracting gimp-app-2.10.6_1,1: 1%^M[17/47] Ex=
tracting gimp-app-2.10.6_1,1: 2%^M[17/47] Extracting gimp-app-2.10.6_1,1:=
3%^M[17/47] Extracting gimp-app-2.10.6_1,1: 4%^M[17/47] Extracting gim=
p-app-2.10.6_1,1: 5%^M[17/47] Extracting gimp-app-2.10.6_1,1: 6%
pkg: Fail to create temporary file: /usr/local/libexec/gimp/2.2/plug-ins/al=
ign-layers/.align-layers.pD2NdeK0jYaA:Not a directory
^M[17/47] Extracting gimp-app-2.10.6_1,1: 100%
Command exit status: 0
Script done on Sun Oct 28 05:34:25 2018
[For those who may be curious: I circumvented the problem -- once I
discovered its existence -- by deleting the graphics/gimp* packages,
re-issuing "pkg upgrade", then installing graphics/gimp.]
I'm a little(!) concerned, though, that pkg would encounter an issue
that caused it to completely fail to perform what it had been doing, and
then exit with a status of 0.
Am I missing something that others would find obvious, here? (I thought
a reality check might be in order before filing a bug report.)
Thanks. Replies directed to the list: I'm subscribed.
Peace,
david
--=20
David H. Wolfskill david@catwhisker.org
Women (and decent men): vote against supporters of Trump's misogyny!
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--i0/AhcQY5QxfSsSZ
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlvWEZJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND
QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ
7heajggA0PbF90lmN28UdcNS1EU90Jyq3UKnc71iae87tXp4nLGZf4SecIqlANb2
BFIrE2m6S73zfz4vFvGZfsLe7VYubK57DrtGqxNTGTDPhrR/M7ITfAM/SXGAo8yf
9nb9/6nZu12AXdbNTQOVFa9x0wwNhs/NqwjzKG8Ow9yEo30/8D9MHHlZ/ihrc7T8
tc+3WJ8wo/tM9/33JKNwe0fcrAeVRJgFz09DDJk45T1y+mhkkya8KZlDvG+TDMX9
L3PBW6lHuNvfZTNzCquOvynZULW3RHQm0pUGq1WHymk/6gYVpYTTDCCRZdZ5gtY5
DYjN2LBX4mNBRX37vFke4zzzTDnr2w==
=HWud
-----END PGP SIGNATURE-----
--i0/AhcQY5QxfSsSZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181028194418.GB1242>