strange pkg upgrade problems
I tried to do a pkg upgrade on one of my FreeBSD 8.4-STABLE boxes and ran into some strange problems. # pkg upgrade Updating myrepo repository catalogue... myrepo repository is up-to-date. All repositories are up-to-date. Checking for upgrades (365 candidates): 100% Processing candidates (365 candidates): 100% Checking integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 72 packages will be affected (of 0 checked): Installed packages to be REMOVED: giflib-nox11-4.2.3_4 New packages to be INSTALLED: giflib: 5.0.6 libedit: 3.1.20141030_2 Installed packages to be UPGRADED: xorg-libraries: 7.7_1 -> 7.7_2 xorg-apps: 7.7_1 -> 7.7_2 webp: 0.4.2_2 -> 0.4.2_3 vigra: 1.10.0_4 -> 1.10.0_5 vala: 0.26.1 -> 0.26.2 unzip: 6.0_2 -> 6.0_3 unrar: 5.10,5 -> 5.21,5 uhttpmock: 0.3.1_1 -> 0.3.3 transcode: 1.1.7_20 -> 1.1.7_21 tracker: 1.2.5_1 -> 1.2.5_2 thunderbird: 31.3.0_1 -> 31.4.0 tevent: 0.9.21 -> 0.9.22 tdb: 1.2.13,1 -> 1.3.4,1 talloc: 2.1.0 -> 2.1.1 sqlite3: 3.8.7.4 -> 3.8.8 scilab: 5.5.0_1 -> 5.5.0_2 py34-setuptools34: 5.5.1 -> 5.5.1_1 py27-setuptools27: 5.5.1 -> 5.5.1_1 py27-pygments: 1.6_2 -> 2.0.1 py27-lxml: 3.4.0 -> 3.4.1 py27-cryptography: 0.5.4 -> 0.7.2 pciids: 20150105 -> 20150117 p5-Net-SSLeay: 1.66_1 -> 1.67 p5-HTTP-Message: 6.06_3 -> 6.06_4 p5-Filter: 1.53 -> 1.54 p5-Crypt-Eksblowfish: 0.009_1 -> 0.009_2 p5-CGI-FormBuilder: 3.0800_1 -> 3.0900 p5-Archive-Zip: 1.42 -> 1.43 octave: 3.8.1_6 -> 3.8.1_7 mplayer: 1.1.r20141223 -> 1.1.r20141223_1 mencoder: 1.1.r20141223 -> 1.1.r20141223_2 matio: 1.5.2_3 -> 1.5.2_4 lua52: 5.2.3_3 -> 5.2.3_4 libxul: 31.3.0_1 -> 31.4.0 libxklavier: 5.2.1_1,1 -> 5.3,1 libxine: 1.2.6_2 -> 1.2.6_3 librsvg2: 2.40.6 -> 2.40.6_1 libnice-gst1: 0.1.7_1 -> 0.1.8 libnice-gst010: 0.1.7_1 -> 0.1.8 libnice: 0.1.7_1 -> 0.1.8 libgweather: 3.14.2 -> 3.14.3 libgsf: 1.14.30 -> 1.14.30_1 libamrwb: 11.0.0.0_1 -> 11.0.0.0_2 libamrnb: 11.0.0.0,2 -> 11.0.0.0_1,2 libXft: 2.3.1_2 -> 2.3.2 hdf5: 1.8.13_1 -> 1.8.14 guile2: 2.0.11_2 -> 2.0.11_3 gtkspell3: 3.0.4_2 -> 3.0.6 gtkhtml4: 4.8.4 -> 4.8.5 gnome-power-manager: 3.12.2 -> 3.14.1 gnome-documents: 3.14.1 -> 3.14.2 gnome-dictionary: 3.14.0 -> 3.14.2 gnome-color-manager: 3.14.1 -> 3.14.2 gfbgraph: 0.2.2_1 -> 0.2.2_2 geoclue: 2.1.9 -> 2.1.10 folks: 0.10.0 -> 0.10.1 firefox: 34.0.5_1,1 -> 35.0,1 farstream: 0.2.4 -> 0.2.6 evolution-data-server: 3.12.9 -> 3.12.10 evolution: 3.12.9 -> 3.12.10_1 dvdauthor: 0.7.1_8 -> 0.7.1_9 dbus: 1.8.12 -> 1.8.12_1 cuse4bsd-kmod: 0.1.35 -> 0.1.36 cracklib: 2.9.2 -> 2.9.2_1 cmake-modules: 3.1.0 -> 3.1.0_1 bash: 4.3.30_1 -> 4.3.33 baobab: 3.14.0 -> 3.14.1 aisleriot: 3.14.1 -> 3.14.2 ImageMagick: 6.9.0.2,1 -> 6.9.0.4,1 The process will require 4 MB more space. Proceed with this action? [y/N]: y [1/72] Upgrading pciids from 20150105 to 20150117... pkg: unlinkat(usr/local/share/licenses/pciids-20150105/BSD3CLAUSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/pciids-20150105/GPLv2): No such file or directory pkg: unlinkat(usr/local/share/licenses/pciids-20150105/GPLv3): No such file or directory pkg: unlinkat(usr/local/share/licenses/pciids-20150105/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/pciids-20150105/catalog.mk): No such file or directory [1/72] Extracting pciids-20150117: 100% [2/72] Upgrading libXft from 2.3.1_2 to 2.3.2... pkg: unlinkat(usr/local/lib/libXft.so.2.3.1): No such file or directory [2/72] Extracting libXft-2.3.2: 100% [3/72] Upgrading dbus from 1.8.12 to 1.8.12_1... ==> You should manually remove the "messagebus" user. ===> Creating users and/or groups. Using existing group 'messagebus'. Using existing user 'messagebus'. [3/72] Extracting dbus-1.8.12_1: 100% [4/72] Upgrading talloc from 2.1.0 to 2.1.1... pkg: unlinkat(usr/local/share/licenses/talloc-2.1.0/LGPL3): No such file or directory pkg: unlinkat(usr/local/share/licenses/talloc-2.1.0/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/talloc-2.1.0/catalog.mk): No such file or directory [4/72] Extracting talloc-2.1.1: 100% [5/72] Upgrading py27-setuptools27 from 5.5.1 to 5.5.1_1... pkg: unlinkat(usr/local/share/licenses/py27-setuptools27-5.5.1/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/py27-setuptools27-5.5.1/PSFL): No such file or directory pkg: unlinkat(usr/local/share/licenses/py27-setuptools27-5.5.1/catalog.mk): No such file or directo
Re: strange pkg upgrade problems
On 23/01/2015 07:59, Don Lewis wrote: > The EPERM errors seem to be kind of random. If I go and look at the > "from" file for the rename() using "ls -lo", I see all sorts of random > flags, like opaque, archive, uunlnk, etc. I booted single user and ran > fsck, which came back totally clean. Then I used chflags -R to clear > all the flags, did pkg upgrade again, and ran into the exact same > problems. If I rerun pkg upgrade, it may fail on the same port again, > ir it might pick another. I can go in an manually clear the flags, nuke > the temporary file that pkg created and upgrade the failed package. I > never had that fail. But running pkg upgrade without specifying a > package will then fail elsewhere. This has been fixed in pkg(8) GitHub, and the fix will appear in the next release (1.4.7) due out within a few days. https://github.com/freebsd/pkg/commit/93d1647d0b986e4c6ad317c4e96886784477dcfe Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ textproc/tralics| 2.15.1 | 2.15.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: strange pkg upgrade problems
On Fri, Jan 23, 2015 at 08:16:46AM +, Matthew Seaman wrote: > On 23/01/2015 07:59, Don Lewis wrote: > > The EPERM errors seem to be kind of random. If I go and look at the > > "from" file for the rename() using "ls -lo", I see all sorts of random > > flags, like opaque, archive, uunlnk, etc. I booted single user and ran > > fsck, which came back totally clean. Then I used chflags -R to clear > > all the flags, did pkg upgrade again, and ran into the exact same > > problems. If I rerun pkg upgrade, it may fail on the same port again, > > ir it might pick another. I can go in an manually clear the flags, nuke > > the temporary file that pkg created and upgrade the failed package. I > > never had that fail. But running pkg upgrade without specifying a > > package will then fail elsewhere. > > This has been fixed in pkg(8) GitHub, and the fix will appear in the > next release (1.4.7) due out within a few days. > > https://github.com/freebsd/pkg/commit/93d1647d0b986e4c6ad317c4e96886784477dcfe No, I don't think it has been fixed. The bug is here: https://github.com/freebsd/pkg/issues/1151 Looks like it still needs a bit more work. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x6C226B37FDF38D55 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking at new port deskutils/currtime
Hi freebsd-ports Mailing List, I have a new FreeBSD port deskutils/currtime, which is a command-line operated real time clock. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196781 Keep in mind that right now, deskutils/currtime is just a command-line based clock without any additional frills, although I do plan to add more features to currtime in the future as I am the author of currtime. Thanks, Neel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Au revoir de notre bulletin d'information
Goodbye from our Newsletter, sorry to see you go. You have been unsubscribed from our newsletters. This is the last email you will receive from us. Our newsletter system, phpList, will refuse to send you any further messages, without manual intervention by our administrator. If there is an error in this information, you can re-subscribe: please go to http://www.ma-mutuelle.tk/obseque/?p=subscribe and follow the steps. Thank you ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
