From nobody Fri May 10 09:18:57 2024 X-Original-To: xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VbNc605dZz5J1C6 for ; Fri, 10 May 2024 09:19:02 +0000 (UTC) (envelope-from roger.pau@cloud.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VbNc55Grpz4DG2 for ; Fri, 10 May 2024 09:19:01 +0000 (UTC) (envelope-from roger.pau@cloud.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x829.google.com with SMTP id d75a77b69052e-43dfc9b9519so3274321cf.1 for ; Fri, 10 May 2024 02:19:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrix.com; s=google; t=1715332740; x=1715937540; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=bqpFmg8zkURnALhEXF6Zb+lo1WvCG7f8ZXbWr2HaJ1E=; b=gAT5ZRbttAsH8bzQZncEBc0Q5v38PwgQNdK3JNaVlK3FmNtfCnDbI2tJp8DwPgpYdf 7ZxLJxRkFZcBdusX8Xnv1q3KrwP/Qv61fbOJxmqIUqDmHA/N1MjbZmWNFPIgerYcxmTB wE3LN+vgLIX7Uw3/ND29YBicDlxJq8oQE4/Cs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715332740; x=1715937540; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=bqpFmg8zkURnALhEXF6Zb+lo1WvCG7f8ZXbWr2HaJ1E=; b=Um9b915NHUuokyEQuvPB05ZK4hun7aZn9noYSlg8QUGz0s+fx3WTc0H1s1gFBSNmzw xEiBrNngZhq9e1LE3+t6xk73m9kqZk2d5sfO5XvTjRKBbcPqGxyvHjABCiXUdIbxW/1o Iqxm9/O0xO7MvITR9/Flwb+xbx9ZnY2fMd1etECSvIQF8spI3Yec3fMnnO/FBce8VAnD 4itoaSeqApz2ldDehP6oVnfQhrvSh/94+17cXmlpuMjwp35r34Gx9OthKvCNK531Uk5N vIu94c1okn95i61RE1kJ9FanpKt2fQs5KAX4UlT2x0mt6o3gKHB8gaxFR465h6sMZGw9 dVmQ== X-Gm-Message-State: AOJu0YxW5EtHyarYLF5Z5TNhUxLQemzGXbuIJx7BxtiLcXRqjV9mU973 5JgfDXZNsKMLqz3KsgBB92xrfY/1XC24LJTqzHEX1H+m3vg5bwPekzBpsljnlyVW7afag52zDV8 Y X-Google-Smtp-Source: AGHT+IH/3q4VxD/1lTEhwNKoOBgiJBcyxxQBnrh3QX0Pnhbn5HQdH+w4buoY8VnDD98MYden4eTJ/Q== X-Received: by 2002:ac8:598a:0:b0:43a:f8d3:b556 with SMTP id d75a77b69052e-43dfdb8abddmr17930461cf.68.1715332740274; Fri, 10 May 2024 02:19:00 -0700 (PDT) Received: from localhost ([213.195.114.223]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-43df569ba65sm19018941cf.70.2024.05.10.02.18.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 May 2024 02:18:59 -0700 (PDT) Date: Fri, 10 May 2024 11:18:57 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Brian Buhrow Cc: xen@freebsd.org Subject: Re: Xen-4.16.0 + FreeBSD-13.1 dom0 fails on large ADM64 system Message-ID: References: <202405100843.44A8hL5Z004502@nfbcal.org> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-xen@freebsd.org Sender: owner-freebsd-xen@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <202405100843.44A8hL5Z004502@nfbcal.org> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VbNc55Grpz4DG2 On Fri, May 10, 2024 at 01:43:21AM -0700, Brian Buhrow wrote: > On May 10, 10:14am, Roger Pau =?utf-8?B?TW9ubsOp?= wrote: > } Subject: Re: Xen-4.16.0 + FreeBSD-13.1 dom0 fails on large ADM64 system > } On Sun, May 05, 2024 at 12:52:39AM -0700, Brian Buhrow wrote: > } > hello Roger. After some further investigation, I found a solution. The first is a link > } > to a bug report which demonstrates the problem. Then, I include the diff I made to the ports > } I'm afraid with this applied I get: > } > } ====> Checking for pkg-plist issues (check-plist) > } ===> Parsing plist > } ===> Checking for items in STAGEDIR missing from pkg-plist > } Error: Orphaned: %%PYTHON_SITELIBDIR%%/pygrub-0.7-py%%PYTHON_VER%%.egg-info > } Error: Orphaned: %%PYTHON_SITELIBDIR%%/xen-3.0-py%%PYTHON_VER%%.egg-info > } ===> Checking for items in pkg-plist which are not in STAGEDIR > } Error: Missing: %%PYTHON_SITELIBDIR%%/pygrub-0.7-py%%PYTHON_VER%%.egg-info/PKG-INFO > } Error: Missing: %%PYTHON_SITELIBDIR%%/pygrub-0.7-py%%PYTHON_VER%%.egg-info/SOURCES.txt > } Error: Missing: %%PYTHON_SITELIBDIR%%/pygrub-0.7-py%%PYTHON_VER%%.egg-info/dependency_links.txt > } Error: Missing: %%PYTHON_SITELIBDIR%%/pygrub-0.7-py%%PYTHON_VER%%.egg-info/top_level.txt > } Error: Missing: %%PYTHON_SITELIBDIR%%/xen-3.0-py%%PYTHON_VER%%.egg-info/PKG-INFO > } Error: Missing: %%PYTHON_SITELIBDIR%%/xen-3.0-py%%PYTHON_VER%%.egg-info/SOURCES.txt > } Error: Missing: %%PYTHON_SITELIBDIR%%/xen-3.0-py%%PYTHON_VER%%.egg-info/dependency_links.txt > } Error: Missing: %%PYTHON_SITELIBDIR%%/xen-3.0-py%%PYTHON_VER%%.egg-info/top_level.txt > } ===> Error: Plist issues found. > } *** Error code 1 > } > } I've got not idea what's wrong here. > } > } Roger. > > That's interesting. I think you said you're runing under FreeBSD-15, while I'm running > FreeBSD-13.1. You'vve already confirmed that the egg-info names point to files, rather than > directories, but with the ports tree snapped to the latest version on 13.1, when I build python > packages, the egg-info names point to directories with the files indicated in the patch inside them. > That's regardless of whether I build python3.8 or python3.9. > I wonder why your copy of the ports tree is building the egg-info names as files? I use poudriere with a pristine 15 jail and copy of the ports tree, so everything is build from scratch based on the last snapshot of the ports tree I have locally. > Are you > updating your entire ports tree, or just the packages you work on? I update everything since that's how poudriere works. > I wouldn't think the > difference in the packaging would have to do with the different versions of FreeBSD, especially > since under older versions of the ports tree, the egg-info names are built as files as well, > while running on FreeBSD-13.1. I'm testing with a 13.2 jail now, let's see if that's different. Are you using a specific snapshot of the ports tree? > With the patch I sent you, I can make package and make install successfully with the xen-tools > port on 13.1, using the latest version of the ports tree. FWIW, the xen-tools package as-is seems to also build fine in the pkg builders for 13.2 and 13.3, so I'm really unsure of what's wrong with your specific setup. Regards, Roger.