Re: on current, pkg install openssl kills pkg
Hi, Reference: > From: Bernard Spil > Date: Sun, 28 Oct 2018 02:08:08 +0100 Bernard Spil wrote: > On 2018-10-17 0:26, Julian H. Stacey wrote: > > Hi po...@freebsd.org > > cc br...@freebsd.org maintaine= of ports/security/openssl > > > > On current, 12.0-ALPHA9, this kills pkg: > > pkg install openssl > > > > uname -r# 12.0-ALPHA9 > > cd /usr/src > > cat .ctm_status # src-cur 13733 > > cat .svn_revision # 339303 > > > > pkg install openssl > > Updating FreeBSD repository catalogue... > > FreeBSD repository is up to date. > > All repositories are up to date. > > The following 1 package(s) will be affected (of 0 checked): > > New packages to be INSTALLED: > > openssl: 1.0.2p_1,1 > > Number of packages to be installed: 1 > > The process will require 12 MiB more space. > > 3 MiB to be downloaded. > > [1/1] Fetching openssl-1.0.2p_1,1.txz: 100%3 MiB 626.9kB/s > > 00:05 > > Checking integrity... done (0 conflicting) > > [1/1] Installing openssl-1.0.2p_1,1... > > [1/1] Extracting openssl-1.0.2p_1,1: 100% > > Message from openssl-1.0.2p_1,1: > > Edit /usr/local/openssl/openssl.cnf to fit your needs. > > > > pkg install openvpn > > ld-elf.so.1: /usr/local/lib/libcrypto.so.9: version > > OPENSSL_1_1_0 required bysr/local/lib/libpkg.so.4 not defined > > > > That ld-elf message was rather too opaque for me. > > I fumbled with various libs to no good effect, copying from another > > host, > > & reinstalling from current ports/ports-mgmt/pkg etc, > > Nothing fixed it till I used another AMD+NFS mounted current host: > > > > /host/lapr/usr/local/sbin/pkg delete openssl > > > > Comments please ? Meaning ? How to prevent / fix it ? > > > > its just that one package, I'm rebuilding & up to here OK: > > pkg info -a | wc -l # 1062 > > using > > foreach i ( `fetch -o - > > http://berklix.com/~jhs/src/bsd/fixes/freebsd/packages/to_pkg_install` > > ) > > echo DOING $i > > pkg install -y $i > > done > > > > Ive removed openssl from my list of package to install, nothing else > > wants it so far. > > It used to be in my ports/security/Makefile.inc to support > > cd /usr/ports/x11-servers/xorg-server;make > > But I'll just leave it to automatic depend from now on. > > > > Cheers, > > Julian > > Hi Julian, > > Bit late to the party, but you're most likely hit by the update of > crypto/openssl to 1.1.1 in base. There's another change the past days > where the libraries have been renamed to libcrypto.so.111 and > libssl.so.111 which might hit you too. > > Cheers, Bernard. Yes thanks Bernard, Lots of threads on src ports pkgs seem to be hit by these 2 disturbances. I've stabilised my laptop on an older current that works, & won't update that for a while, another current tower is on bleeding edge current. Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich. Brexit referendum stole 3,700,000 Brits votes abroad, inc. 700,000 in EU. Campaign lies, criminal funding, economy & pound down. Time for an honest ref. http://exitbrexit.ukhttps://www.peoples-vote.uk/petition https://eci.ec.europa.eu/002/public/#/initiative ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Silent failure of 'pkg upgrade'
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: ... 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-qt47-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 ... [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.10.6_1,1: 0%^M[17/47] Extracting gimp-app-2.10.6_1,1: 1%^M[17/47] Extracting 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 gimp-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/align-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 -- David H. Wolfskill da...@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. signature.asc Description: PGP signature
Re: head -r339076 amd64 -> armv7 port cross build attempt with native tools involved: hangs between a cc (wait) and its child ld (uwait)
[I have a work around for the specific activity to avoid
the hang.]
On 2018-Oct-27, at 6:00 PM, Mark Millard wrote:
> [The bigger test still hung up.]
>
> On 2018-Oct-27, at 5:30 PM, Mark Millard wrote:
>
>> [Just the __packed removal patch was sufficient to no longer
>> have the hang problem that I originally reported for the
>> print/texinfo build in poudriere.]
>>
>> On 2018-Oct-27, at 4:33 PM, Mark Millard wrote:
>>
>>> [Some of this discussion occurred off list. The point here
>>> is not specific to the hang that I originally reported.]
>>>
>>> On 2018-Oct-27, at 3:03 PM, Mark Millard wrote:
>>
>> Mikaël Urankar is being quoted below:
>>
> . . .
>
>> There are bugs in qemu that can cause such deadlock, you can try these
>> 2 patches:
>> https://github.com/MikaelUrankar/qemu-bsd-user/commit/9424a5ffde4de2768ab6baa45fdbe0dbb56a7371
>> https://github.com/MikaelUrankar/qemu-bsd-user/commit/d6f65a7f07d280b6906d499d8e465d4d2026c52b
>>
>> Back to me:
>>
> I'll try those later. Thanks. (I need to get back to sleep.)
>
> It was interesting that attach/detach to the ld process
> caused it to progress. The rest of the build completed
> just fine. But that one spot consistently hung up before
> trying gdb to look at the back trace.
>
Looking at the qemu code related to the 2nd patch: the
structure of the field copies (via __get_user) seems
very sensitive to the ABI rules for the target and
how things align and such, given that the structure
description and code are host code. __packed vs. not
is possibly not sufficient control to always make things
match right across all the potential combinations of
host and target from what I can see.
Lack of __packed may prove sufficient for my specific
context (amd64 host and armv7 target) but it seems
non-obvious what to do in general.
There would also seem to be big endian vs. little endian
issues on the individual __get_user styles of copies
when the host and target do not match for a multi-byte
numeric encoding.
>>>
>>> Well, I get the following for:
>>>
>>> #include "/usr/include/sys/event.h" // kevent
>>> #include // offsetof
>>> #include // printf
>>>
>>> int
>>> main()
>>> {
>>> printf("%lu\n", (unsigned long) sizeof(struct kevent));
>>> printf("ident %lu\n", (unsigned long) offsetof(struct kevent, ident));
>>> printf("filter %lu\n", (unsigned long) offsetof(struct kevent,
>>> filter));
>>> printf("flags %lu\n", (unsigned long) offsetof(struct kevent, flags));
>>> printf("fflags %lu\n", (unsigned long) offsetof(struct kevent,
>>> fflags));
>>> printf("data %lu\n", (unsigned long) offsetof(struct kevent, data));
>>> printf("udata %lu\n", (unsigned long) offsetof(struct kevent, udata));
>>> printf("ext %lu\n", (unsigned long) offsetof(struct kevent, ext));
>>> return 0;
>>> }
>>>
>>> (This code avoided warnings for type mismatches with the
>>> printf strings and such.)
>>>
>>> amd64 native [host of qemu use] (comments hand added):
>>>
>>> # ./a.out
>>> 64
>>> ident 0
>>> filter 8 // NOTE!
>>> flags 10 // NOTE!
>>> fflags 12 // NOTE!
>>> data 16
>>> udata 24
>>> ext 32
>>>
>>> (The above is not particularly important but I
>>> include it for completeness.)
>>>
>>> armv7 native [target in qemu use] (comments hand added):
>>>
>>> # ./a.out
>>> 64 // NOTE vs. below!
>>> ident 0
>>> filter 4 // NOTE vs. above!
>>> flags 6 // NOTE vs. above!
>>> fflags 8 // NOTE vs. above!
>>> data 16 // NOTE vs. below!
>>> udata 24 // NOTE vs. below!
>>> ext 32 // NOTE vs. below!
>>>
>>> /usr/include/sys/event.h lacks __packed in both cases.
>>>
>>> With __packed in qemu-arm-static's source code
>>> for target_freebsd_kevent I confirm that via
>>> gdb for the qemu-arm-static:
>>>
>>> p/d sizeof(struct target_freebsd_kevent)
>>> p/d &((struct target_freebsd_kevent *)0)->ident
>>> p/d &((struct target_freebsd_kevent *)0)->filter
>>> p/d &((struct target_freebsd_kevent *)0)->flags
>>> p/d &((struct target_freebsd_kevent *)0)->fflags
>>> p/d &((struct target_freebsd_kevent *)0)->data
>>> p/d &((struct target_freebsd_kevent *)0)->udata
>>> p/d &((struct target_freebsd_kevent *)0)->ext
>>>
>>> reports as the 2nd patch's problem-report
>>> material reports (56,0,4,6,8,12,20,24): not
>>> even the right size.
>>>
>>> I also confirm that removing __packed in qemu's
>>> code and rebuilding and then checking with gdb
>>> reported a match to the above armv7 native report
>>> (64,0,4,6,8,16,24,32).
>>>
>>> I have not verified __packed used vs. not for any
>>> other combination of host and target platforms.
>>
>> Removing the 2 examples of __packed, including the
>> 1 for target_freebsd_kevent, as in Mikaël Urankar's
>> 2nd listed patch, was sufficient to avoid the hang
>> that I originally reported. (Technically FreeBSD 11
>> is not involved and so one of the __p
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 +-+ devel/py-marshmallow| 3.0.0b7 | 3.0.0b9 +-+ net-mgmt/mk-livestatus | 1.2.8p20| 1.2.8p22 +-+ 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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
