From mirageos-devel-bounces@lists.xenproject.org Wed Jul 08 16:18:59 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Jul 2026 16:18:59 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1357197.1611693 (Exim 4.92) (envelope-from ) id 1whUyz-0005uz-DB; Wed, 08 Jul 2026 16:18:45 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1357197.1611693; Wed, 08 Jul 2026 16:18:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1whUyz-0005us-9h; Wed, 08 Jul 2026 16:18:45 +0000 Received: by outflank-mailman (input) for mailman id 1357197; Wed, 08 Jul 2026 16:18:43 +0000 Received: from mx.expurgate.net ([194.145.224.10]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1whUyx-0005um-EH for mirageos-devel@lists.xenproject.org; Wed, 08 Jul 2026 16:18:43 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1whUyw-000c63-3z for mirageos-devel@lists.xenproject.org; Wed, 08 Jul 2026 18:18:42 +0200 Received: from [10.42.69.2] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a4e7854-e002-0a2a0a5209dd-0a2a4502b45c-26 for ; Wed, 08 Jul 2026 18:18:42 +0200 Received: from [209.85.221.51] (helo=mail-wr1-f51.google.com) by tlsNG-720697.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.1) (envelope-from ) id 6a4e7861-5a27-0a2a45020019-d155dd33c5fd-3 for ; Wed, 08 Jul 2026 18:18:41 +0200 Received: by mail-wr1-f51.google.com with SMTP id ffacd0b85a97d-47640541585so526653f8f.1 for ; Wed, 08 Jul 2026 09:18:41 -0700 (PDT) Received: from [192.168.2.43] ([31.32.33.168]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-47a9e4d7801sm44296967f8f.16.2026.07.08.09.18.40 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Jul 2026 09:18:40 -0700 (PDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=20251104 header.d=tarides-com.20251104.gappssmtp.com header.i="@tarides-com.20251104.gappssmtp.com" header.h="Subject:From:To:Content-Language:User-Agent:MIME-Version:Date:Message-ID:Content-Type" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tarides-com.20251104.gappssmtp.com; s=20251104; t=1783527521; x=1784132321; darn=lists.xenproject.org; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:content-type:from:to:cc:subject:date:message-id:reply-to :content-type; bh=vQeK+IJZ2gpM0Sya4JjnOvRyRhFsBtDuaHJLozoZSF8=; b=PfGk09dXVAV/qa2STZVrTDOcLKPqzTXbgMnl94gsO8rnzZ50ywvBjrDj3VywTbMhTX ribboiNmgK8yo/aXWUXAVz9P8JumfOOISOt7F8l2rjzTWadMV7RS4jvPB8vcrrpgPVYv zaGRP1tZ45iUxCjLcpWQO1cvHbzZdUKAuSAAGGN9zJFMdPp7ezbyg9KPnDJ5szB+ILHG 0gMV5mvDcZanmaNQ0gOPWe8MLvNEIw3O7beQfDw3UUmKaM0bXfY5sKXaCBTcGm3V9b91 trUXZ8fHN5bnm+qdM2xouhZHIsKLeYKIEJ5+HAtGtpTbzyZLN+OJmuRmy5mqPU/JGmCR 3L3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783527521; x=1784132321; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:content-type:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=vQeK+IJZ2gpM0Sya4JjnOvRyRhFsBtDuaHJLozoZSF8=; b=P+BL95IauUHiB7TkrnMmNmJWc+N1MBEfzWIpGrRde3E4qQmV1yCoDFZ1xAfCH04rVa 2597UO9mb7jW/kMMypFDvz/ElVRavcmITQcSQG5WyxoGx4UjXeyzzep2y0ya2nRoH2s1 ZlsWjdo8+lgXJ8DfpuIMZrf0Ap+a8IQNF7pB3giWHEcWfZccGEqnxgqtc8luRv6hwJr4 XnDgamPjCyX2reThlhqve8fheAXsi3i9iJmwzO5mdGinujd0BcXCK+bbGcrsTJkN5Zzq tsrfLihI1tgalU7lZJlT5iLjRGhxz4vh340UCkLxSmWvPLbnLUhcOruOrKhBOBNrQc86 /zPw== X-Gm-Message-State: AOJu0YzgAq+5qAx/Q4YLKyBCBtDrCFMAPDqvMunHPj4wb3ixX8h4NuiY QmHllnkuc59/vIMDVczYfn1iACaBweqaQZ3DDuViqjLcaJyLyNAnNVLLI/6wlh2uT+kBP+PJ1PN 3w0ztsts= X-Gm-Gg: AfdE7cnP15ipvIEAQrPrFyv1Mb85HWo1Am1JbjcfFyrnY1KaA6APNX2sS6T05mbHw6I jzjwhuN4FNcutdSBdKgYJWC8vzR/hI5DbgUreiRkz0S2zJe2PrS8wjqRDY04Flp2kmkI35GG+RK C0G640/QUqmCicRIfKx+ntsSKv7OKmq9e7cSzCwy0zNE3N8e7nMZsLKEZqBr/CGaSXSjzxaIAfw JONY0H0drvF5tGyTpG/YZNN7aBw6BHdeJqCP7wSbljDbArSTLSROnDiHxpcFxJ5WM74TkvPtKsh 8F3FolLL867Ypumkq/CJVWvtaEPLBeigpyMe+//3SkUkbZiUrswQ3frP+nxarezbePtdS1CzyVv V02noHXZQR9d6TGqg95HZw9WTxTe78hxcatAwC5lP8TtKw1vKXAy/QZ7chtL3N+uvZrUrsXprEI OpC52y3lCI88vgveW0aLK7aIt+G+D1WJyi8JTpnkyhmvRULe3eBGY3rrFV X-Received: by 2002:a05:6000:4613:b0:47d:ecaa:3f60 with SMTP id ffacd0b85a97d-47df077b2dbmr3459368f8f.46.1783527521115; Wed, 08 Jul 2026 09:18:41 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------rpL3DcIFZa0l1Bw7sp3C8wBu" Message-ID: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> Date: Wed, 8 Jul 2026 18:18:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: mirageos-devel@lists.xenproject.org From: Virgile Robles Subject: Merge of opam-overlays and mirage-opam-overlays X-purgate-ID: tlsNG-720697/1783527522-4CB077C5-D9481952/0/0 X-purgate-type: clean X-purgate-size: 4089 This is a multi-part message in MIME format. --------------rpL3DcIFZa0l1Bw7sp3C8wBu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear all, Today our build infrastructure based on opam-monorepo is relying on all unikernel dependencies building with dune. To that end, we have two opam overlay repositories containing ports of packages that do not use dune upstream: * opam-overlays : historically decoupled from Mirage, containing almost all ports guaranteed to build with dune but not necessarily cross-compilable * mirage-opam-overlays : for ports that need further or different adaptations to be cross-compilable, since we need it for Mirage. The second one actually only contains the zarith package, for which we have two different ports. Following some discussions we had some time ago observing there is some seemingly unnecessary complexity in having two separate repositories for one single package, and that opam-monorepo is (to my knowledge) only used by Mirage, I have merged mirage-opam-overlays into opam-overlays and propose that going forward only opam-overlays be used (and requires that all ports are cross-compilable). mirage-opam-overlays is now empty and redirecting to opam-overlays, so no unikernels should be affected, but I'm ready to revert if this change broke someone's workflow (Mirage-related or not), so please let me know if this is the case or if you have a use for the non-mirage zarith port! After some time in the absence of issues I'll submit a PR to mirage/mirage to produce Makefiles without mirage-opam-overlays. Have a great day, Virgile --------------rpL3DcIFZa0l1Bw7sp3C8wBu Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Dear all,

Today our build infrastructure based on opam-monorepo is relying on all unikernel dependencies building with dune. To that end, we have two opam overlay repositories containing ports of packages that do not use dune upstream:

  • opam-overlays: historically decoupled from Mirage, containing almost all ports guaranteed to build with dune but not necessarily cross-compilable
  • mirage-opam-overlays: for ports that need further or different adaptations to be cross-compilable, since we need it for Mirage.

The second one actually only contains the zarith package, for which we have two different ports.

Following some discussions we had some time ago observing there is some seemingly unnecessary complexity in having two separate repositories for one single package, and that opam-monorepo is (to my knowledge) only used by Mirage, I have merged mirage-opam-overlays into opam-overlays and propose that going forward only opam-overlays be used (and requires that all ports are cross-compilable).

mirage-opam-overlays is now empty and redirecting to opam-overlays, so no unikernels should be affected, but I'm ready to revert if this change broke someone's workflow (Mirage-related or not), so please let me know if this is the case or if you have a use for the non-mirage zarith port!

After some time in the absence of issues I'll submit a PR to mirage/mirage to produce Makefiles without mirage-opam-overlays.

Have a great day,

Virgile

--------------rpL3DcIFZa0l1Bw7sp3C8wBu-- From mirageos-devel-bounces@lists.xenproject.org Sat Jul 11 17:58:32 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 11 Jul 2026 17:58:32 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1360524.1613348 (Exim 4.92) (envelope-from ) id 1wibxy-0005pM-87; Sat, 11 Jul 2026 17:58:18 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1360524.1613348; Sat, 11 Jul 2026 17:58:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wibxy-0005pF-4f; Sat, 11 Jul 2026 17:58:18 +0000 Received: by outflank-mailman (input) for mailman id 1360524; Sat, 11 Jul 2026 17:58:16 +0000 Received: from mx.expurgate.net ([194.145.224.10]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wibxw-0005p9-3y for mirageos-devel@lists.xenproject.org; Sat, 11 Jul 2026 17:58:16 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wibxv-00AIzJ-A5 for mirageos-devel@lists.xenproject.org; Sat, 11 Jul 2026 19:58:15 +0200 Received: from [10.42.69.2] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a5283ba-5cb7-0a2a0a5109dd-0a2a4502be54-42 for ; Sat, 11 Jul 2026 19:58:15 +0200 Received: from [91.218.175.177] (helo=out-177.mta0.migadu.com) by tlsNG-720697.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.2) (envelope-from ) id 6a528436-64c6-0a2a45020019-5bdaafb16d6d-3 for ; Sat, 11 Jul 2026 19:58:14 +0200 X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=key1 header.d=exn.st header.i="@exn.st" header.h="From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=exn.st; s=key1; t=1783792694; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/C//UtPngkrNxnc+wjAAceRJ3EsXlPBE1zcatr9ASyk=; b=MYVkWtvZMekA5oIda02/b0rPw0CmBTDexfo8uRa8vH4ab3B7F96thORNuXN2eGRzht3kPJ Gl+h+ukU7MSwTpzHm5AbjB+NmC3YTD/XmfChqQ+mnFFImjuiBWBc8VFJ5gB+uriz7vAJD/ gbCfk+IMQOWWx8k6SY4ErJir04NDJPJiDikjXiYTXr4FpBt8dcG5Q9y7s57NCEE7x/b+ED 2FAQuCUoGVsh5FhgAf4Nqmx5asUnp502a/5Ou5ujwO6Uyw3AaxsexMZMHPvBHBuVP4x6sz TK4lReSIhl/ziggt1mm+KUQkALR7OGRCCMbaf/l3SW9D8sHrDsjMWMRH/rOx7w== Date: Sat, 11 Jul 2026 18:58:07 +0100 MIME-Version: 1.0 Subject: Re: Merge of opam-overlays and mirage-opam-overlays To: mirageos-devel@lists.xenproject.org References: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> Content-Language: en-GB, fr, de-DE X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kate In-Reply-To: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT X-purgate-ID: tlsNG-720697/1783792695-3E546A87-16B23DA1/0/0 X-purgate-type: clean X-purgate-size: 2125 Hi, Locally, the first time i called opam update, this repository failed with some uncaught exception and even after non-failed subsequent updates the resulting repository wasn't the one it's supposed to be redirected to, thus leaving us with the empty repository. Could you confirm the redirection worked for you locally when you tested this? Cheers, Kate On 7/8/26 17:18, Virgile Robles wrote: > Dear all, > > Today our build infrastructure based on opam-monorepo is relying on all > unikernel dependencies building with dune. To that end, we have two opam > overlay repositories containing ports of packages that do not use dune > upstream: > > * opam-overlays : > historically decoupled from Mirage, containing almost all ports > guaranteed to build with dune but not necessarily cross-compilable > * mirage-opam-overlays overlays>: for ports that need further or different adaptations to > be cross-compilable, since we need it for Mirage. > > The second one actually only contains the zarith package, for which we > have two different ports. > > Following some discussions we had some time ago observing there is some > seemingly unnecessary complexity in having two separate repositories for > one single package, and that opam-monorepo is (to my knowledge) only > used by Mirage, I have merged mirage-opam-overlays into opam-overlays > and propose that going forward only opam-overlays be used (and requires > that all ports are cross-compilable). > > mirage-opam-overlays is now empty and redirecting to opam-overlays, so > no unikernels should be affected, but I'm ready to revert if this change > broke someone's workflow (Mirage-related or not), so please let me know > if this is the case or if you have a use for the non-mirage zarith port! > > After some time in the absence of issues I'll submit a PR to mirage/ > mirage to produce Makefiles without mirage-opam-overlays. > > Have a great day, > > Virgile > From mirageos-devel-bounces@lists.xenproject.org Mon Jul 13 12:29:25 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Jul 2026 12:29:25 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1361644.1613802 (Exim 4.92) (envelope-from ) id 1wjFmc-0002Dl-44; Mon, 13 Jul 2026 12:29:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1361644.1613802; Mon, 13 Jul 2026 12:29:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjFmc-0002De-0i; Mon, 13 Jul 2026 12:29:14 +0000 Received: by outflank-mailman (input) for mailman id 1361644; Mon, 13 Jul 2026 12:29:12 +0000 Received: from mx.expurgate.net ([194.145.224.20]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjFma-0002DY-30 for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 12:29:12 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wjFmZ-007MwL-AK for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 14:29:11 +0200 Received: from [10.42.69.4] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a54da04-e002-0a2a0a5209dd-0a2a4504b234-32 for ; Mon, 13 Jul 2026 14:29:11 +0200 Received: from [209.85.128.49] (helo=mail-wm1-f49.google.com) by tlsNG-ebf023.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.2) (envelope-from ) id 6a54da16-b1e5-0a2a45040019-d1558031f1f7-3 for ; Mon, 13 Jul 2026 14:29:11 +0200 Received: by mail-wm1-f49.google.com with SMTP id 5b1f17b1804b1-493ba701891so28952665e9.3 for ; Mon, 13 Jul 2026 05:29:11 -0700 (PDT) Received: from ?IPV6:2a01:e0a:813:8090:bcf4:88b6:4894:1927? ([2a01:e0a:813:8090:bcf4:88b6:4894:1927]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-493eb6df417sm385604265e9.8.2026.07.13.05.29.09 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Jul 2026 05:29:09 -0700 (PDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=20251104 header.d=tarides-com.20251104.gappssmtp.com header.i="@tarides-com.20251104.gappssmtp.com" header.h="Content-Transfer-Encoding:Content-Type:In-Reply-To:From:Content-Language:References:To:Subject:User-Agent:MIME-Version:Date:Message-ID" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tarides-com.20251104.gappssmtp.com; s=20251104; t=1783945750; x=1784550550; darn=lists.xenproject.org; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to:content-type; bh=wsFroaRDuatEBc3dIA87KiocWnT9yOtB3Lceqs7b2vQ=; b=iJvzbffrRqXcLkG9lTiUsGbZOMgeogRSdROvU04Ss0xo3W6pCOpdDPLOhqsV0yZiSq /L0mPhSZ0rMSTW/NcpwqvpbTqy6LDUYUUq5a8J/hCYz6E6KcGOFW+9AF1fOKjhcA396L 4ndnDc1M4V2ie7KKPmZ53mTcrBXML2LZEhSO5nM6RvB0tzpNDtPrQHQi2+5WNd9Mvarb 7EqYl8x1VVPhg1kEt/l+tZvrvrLaa9KMAp4duz26/wMQeWWuH1vqt7i0nKioPl9tvjHZ lMfDcfdq3ZOx8V1Cur/oSJNr/lvNQghedAQ8gZr9ggbvVP1wESNeQAJJKGTWzckzNB7G 68kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783945750; x=1784550550; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=wsFroaRDuatEBc3dIA87KiocWnT9yOtB3Lceqs7b2vQ=; b=J3taiVStyTWIXsmAstN0AOQWsv+ezOYwFv1qh+EbnRB81yVOWzWGJhROkuY2oD9Fx+ TLPRUowHL1p5Yxka+yrfs5GBOePoE+fadYWw43GKVwTu27ZXE+lLXsWqKRpHz4e88nwq xGKKguovgYHl/88L+0CpScX1S+KslZfnpk0QwNBrZFEMPsMQQa30+r/E1n+ho7TSXmco sB2QDto1Jjl4o1PuA6d5Fvypc3lxi6ODDfqIBXeex7/KmIkZUgzjECeJxYjmJpYme+2r WN6vMjdYJ3U+N/Mb/+cmQ9+YOg9uJ6yf7OyiWGcoP2r+/kqmHVtxdis6GHbqSu+WJje8 5r/Q== X-Gm-Message-State: AOJu0Yz1CRMBSm/a6WJvQrr3Ou5H6VOWJq3DMRU9hwWui855oWnkZE7Q gfQ/mKRlcTRoJA+2bJWf/NYEannupBrc8WgKSZXs0XDAQ0IOpNPhgnq4+piJErOFNe8pIcLeCA9 bkYxoiho= X-Gm-Gg: AfdE7ckkiZY4Marx+0lX1N+/JVBBLSK1Lb+S3pNeMvGdZbequil7qBGWQZJAs/bd8dC CA96Fvg9eXcOsnv3qdN9XU+W7Qbe8Sjk9+RKLA70J9rLz3GlysuiWzT53ihsB+JM9OoWe5JrbXX g6jj/knVUmonHu9i7gcnIEOShhaTXw0XajoVLZFPPDiTj4q7kXPXb26S+qVZl2iVQ62QZO5G8Gx 0SnXQn5jNzJiLpzrwSQJtVAczY0X2VlP630cE3V5YLRkgrtyfMDPwCmEitTYx/i7itM/jeSz6td NTSlqB6CWxfDr+rXrdk6JbCCuc2/dSABCYXdjL4Ub6RVqZmcUmLCJW3jb+nrR6fHJc+3wfKX0w/ 254ihcb/p/qphErqwzDroeGeL5NmtXEMXlIjnk1G4GOL+nFDgE+ExXRI8BtKcm4hj1szZdkyy7U sV3G1+iFSAJf6g+J87qw9o+ekmL9ZZhUGvV+1CjdpHkjKLMsLOtvd9FsPfSxYlg6MBVePKZvee/ EIRjxOgHhePxoYBv/+ma4lXrRu0 X-Received: by 2002:a05:600c:474f:b0:493:c845:bc20 with SMTP id 5b1f17b1804b1-493f87d8aafmr93955765e9.4.1783945750322; Mon, 13 Jul 2026 05:29:10 -0700 (PDT) Message-ID: Date: Mon, 13 Jul 2026 14:29:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Merge of opam-overlays and mirage-opam-overlays To: mirageos-devel@lists.xenproject.org References: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> Content-Language: en-US From: Virgile Robles In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-purgate-ID: tlsNG-ebf023/1783945751-7D85EFE7-DE5990DD/0/0 X-purgate-type: clean X-purgate-size: 2893 Hi Kate, Thanks for the report. Locally I never encountered any exceptions, however I realize that my tests never checked that the redirection worked (I tested having only opam-overlays or opam-overlays+mirage-opam-overlays), since I expected any user of mirage-opam-overlays to have opam-overlays added as well. And indeed opam doesn't seem to follow the redirect and I couldn't find a way to make it work. For now I've re-added the packages to mirage-opam-overlays, which is the safer option (they are still in opam-overlays, and mirage-opam-overlays is still deprecated). Does that solve the issue you were seeing? Cheers, Virgile Le 11/07/2026 à 19:58, Kate a écrit : > Hi, > > Locally, the first time i called opam update, this repository failed > with some uncaught exception and even after non-failed subsequent > updates the resulting repository wasn't the one it's supposed to be > redirected to, thus leaving us with the empty repository. > > Could you confirm the redirection worked for you locally when you tested > this? > > > Cheers, > Kate > > On 7/8/26 17:18, Virgile Robles wrote: >> Dear all, >> >> Today our build infrastructure based on opam-monorepo is relying on >> all unikernel dependencies building with dune. To that end, we have >> two opam overlay repositories containing ports of packages that do not >> use dune upstream: >> >>   * opam-overlays : >>     historically decoupled from Mirage, containing almost all ports >>     guaranteed to build with dune but not necessarily cross-compilable >>   * mirage-opam-overlays >     overlays>: for ports that need further or different adaptations to >>     be cross-compilable, since we need it for Mirage. >> >> The second one actually only contains the zarith package, for which we >> have two different ports. >> >> Following some discussions we had some time ago observing there is >> some seemingly unnecessary complexity in having two separate >> repositories for one single package, and that opam-monorepo is (to my >> knowledge) only used by Mirage, I have merged mirage-opam-overlays >> into opam-overlays and propose that going forward only opam-overlays >> be used (and requires that all ports are cross-compilable). >> >> mirage-opam-overlays is now empty and redirecting to opam-overlays, so >> no unikernels should be affected, but I'm ready to revert if this >> change broke someone's workflow (Mirage-related or not), so please let >> me know if this is the case or if you have a use for the non-mirage >> zarith port! >> >> After some time in the absence of issues I'll submit a PR to mirage/ >> mirage to produce Makefiles without mirage-opam-overlays. >> >> Have a great day, >> >> Virgile >> > > From mirageos-devel-bounces@lists.xenproject.org Mon Jul 13 13:17:28 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Jul 2026 13:17:28 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1361666.1613816 (Exim 4.92) (envelope-from ) id 1wjGXC-000051-JD; Mon, 13 Jul 2026 13:17:22 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1361666.1613816; Mon, 13 Jul 2026 13:17:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjGXC-00004u-Fm; Mon, 13 Jul 2026 13:17:22 +0000 Received: by outflank-mailman (input) for mailman id 1361666; Mon, 13 Jul 2026 13:17:20 +0000 Received: from mx.expurgate.net ([195.190.135.10]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjGXA-0008WU-AU for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 13:17:20 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wjGX9-0078ea-Ft for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 15:17:19 +0200 Received: from [10.42.69.5] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a54e555-bab6-0a2a0a5309dd-0a2a4505e60a-26 for ; Mon, 13 Jul 2026 15:17:19 +0200 Received: from [128.232.132.147] (helo=smtp-1.srv.uis.cam.ac.uk) by tlsNG-c201ff.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.2) (envelope-from ) id 6a54e55e-4f1d-0a2a45050019-80e884939114-3 for ; Mon, 13 Jul 2026 15:17:18 +0200 Received: from svr-postfix-0.cl.cam.ac.uk ([128.232.119.3]:43405) by smtp-1.srv.uis.cam.ac.uk with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.99.4) (envelope-from ) id 1wjGX8-0000000FPuE-2zzV for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 14:17:18 +0100 Received: from fauth-a1-smtp.messagingengine.com (fauth-a1-smtp.messagingengine.com [103.168.172.200]) (Authenticated sender: avsm2+fm) by svr-postfix-0.cl.cam.ac.uk (Postfix) with ESMTPSA id 2FB7B40821 for ; Mon, 13 Jul 2026 13:17:15 +0000 (UTC) Received: from phl-compute-04.internal (phl-compute-04.internal [10.202.2.44]) by mailfauth.phl.internal (Postfix) with ESMTP id 69E3DF40072; Mon, 13 Jul 2026 09:17:14 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-04.internal (MEProxy); Mon, 13 Jul 2026 09:17:14 -0400 Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 Jul 2026 09:17:13 -0400 (EDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=20250721.smtp header.d=cam.ac.uk header.i="@cam.ac.uk" header.h="References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cam.ac.uk; s=20250721.smtp; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version: Content-Type:Message-Id:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=lYMhPgFUk55UVctD4AjdQWBGk1nulzQ1+vP1hKhy7Rc=; b=kAHVOUKbx4y3qLvICvC5ogJJlw Qv8cUIw8BUi3SgR4173SxmG0Ta6BbkA0W/YM5RL7HQ3m3AVpA/RTXrDIWH4QsJokzNEgktqITUbbQ lONV/zlEd0CjmCB6mx0pxugmp6SaJ+bxi2HAhCRhl9J5KfRDklASsWNlGyQqO5mDvJAJHc/VvYl8G Chsw/hBtKmwbA2iyAdynH2VMDq94jMZPhOg6y2DovcIZrXp7Wtihh4eIDy/OdPcIr7wm06CLaTZHe reeY62k8FMYvMJJplyIp4Rm/Gb4N1wcaa59gV2zBGk8oVTq5DnXKjDGl62PrlFWHZBcU6F4yfyo0k 93klUkwA==; X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: https://help.uis.cam.ac.uk/email-scanner-virus X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTGTWAFbTKcChTppEoTH/sk1HVv1Ci4Ms7dlb1HDGm+UFTf8Ez9lQQM5i9o+VndfTR /FyPFFM67qZTr6l64kZ3ZJPTeR3gdL+uxqSaygvlRND4C4CjMjYZvACUQSoeDwTWSWuD6C s9E7qVKmUVMoZ+pgyc4yZTVB86pJXeoyDy2UfSl53dmzDz8coIrRrsbYTDPCyRR07DY4Dt /3ezKLhoFN5ulcLxGs6mNIlKdlS96fyI91Is3+WHn40zZbiQAijPv95VBSwGgzAeGFxiWH aq6/CO1JabaaqQvC7DjHtyRZuzuPI9c3Tt8QNxzr5da6x0aDIvfmAhc57yetuLz1cDE4a2 6Ef22WkaA0eHUk/PMZW1v8n1bxAXW0nsqRIiri2tZS7k9GjPFHgJh5WG+WeLtIOFT6s3x8 CKHqXaFjxmMQjpwvcFuiqpw/JefzB+UIXAKHICNg93Bl1xBx3NXs5NyUVRf3a6pFgvvmlU y5Zc2N6VCfB042JAfPhjkzJpQf0UbWZpYy8C+Y0C2V/c7aC4RnGuLhPjlfED3pk1RuyDUz ++D5PZAFt/T/rnA2SmMNF8rdbfs09o6POs561r1ob1jtl9z22iYESNTfVs4tCmS4EUFKkV yH3YFr3auGWYssLKtHOwgrSA/9TVcbJzFR9b8Pp/673Z4LLRdzZl9kdSXa2w X-ME-Proxy: Feedback-ID: i9ebc46d9:Fastmail From: Anil Madhavapeddy Message-Id: <04D998D3-B6DD-4883-B049-637753053117@cl.cam.ac.uk> Content-Type: multipart/alternative; boundary="Apple-Mail=_8816B11A-5D9A-4A92-9706-BA86B2F46B18" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\)) Subject: Re: Merge of opam-overlays and mirage-opam-overlays Date: Mon, 13 Jul 2026 14:17:02 +0100 In-Reply-To: Cc: mirageos-devel@lists.xenproject.org To: Virgile Robles References: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> X-Mailer: Apple Mail (2.3864.600.51.1.1) X-purgate-ID: tlsNG-c201ff/1783948639-DB34312E-60557754/0/0 X-purgate-type: clean X-purgate-size: 8898 --Apple-Mail=_8816B11A-5D9A-4A92-9706-BA86B2F46B18 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Thanks for doing this Virgile! Is the redirect actually necessary, as = keeping the mirage overlay empty should be fine I think? I'm also curious (as an aside) what the differences between the = mirage/dune Zarith and the opam-overlay dunified Zarith packages is. If it's just = the cross-compilation glue, it's worth retiring the dunified Zarith as the = Mirage one should be strictly better. best, Anil -- Anil Madhavapeddy, Professor of Planetary Computing = (https://anil.recoil.org) Computer Laboratory, University of Cambridge (https://cst.cam.ac.uk) > On 13 Jul 2026, at 13:29, Virgile Robles wrote: >=20 > Hi Kate, >=20 > Thanks for the report. Locally I never encountered any exceptions, > however I realize that my tests never checked that the redirection > worked (I tested having only opam-overlays or > opam-overlays+mirage-opam-overlays), since I expected any user of > mirage-opam-overlays to have opam-overlays added as well. >=20 > And indeed opam doesn't seem to follow the redirect and I couldn't = find > a way to make it work. >=20 > For now I've re-added the packages to mirage-opam-overlays, which is = the > safer option (they are still in opam-overlays, and = mirage-opam-overlays > is still deprecated). >=20 > Does that solve the issue you were seeing? >=20 > Cheers, > Virgile >=20 > Le 11/07/2026 =C3=A0 19:58, Kate a =C3=A9crit : >> Hi, >>=20 >> Locally, the first time i called opam update, this repository failed >> with some uncaught exception and even after non-failed subsequent >> updates the resulting repository wasn't the one it's supposed to be >> redirected to, thus leaving us with the empty repository. >>=20 >> Could you confirm the redirection worked for you locally when you = tested >> this? >>=20 >>=20 >> Cheers, >> Kate >>=20 >> On 7/8/26 17:18, Virgile Robles wrote: >>> Dear all, >>>=20 >>> Today our build infrastructure based on opam-monorepo is relying on >>> all unikernel dependencies building with dune. To that end, we have >>> two opam overlay repositories containing ports of packages that do = not >>> use dune upstream: >>>=20 >>> * opam-overlays : >>> historically decoupled from Mirage, containing almost all ports >>> guaranteed to build with dune but not necessarily = cross-compilable >>> * mirage-opam-overlays = >> overlays>: for ports that need further or different adaptations = to >>> be cross-compilable, since we need it for Mirage. >>>=20 >>> The second one actually only contains the zarith package, for which = we >>> have two different ports. >>>=20 >>> Following some discussions we had some time ago observing there is >>> some seemingly unnecessary complexity in having two separate >>> repositories for one single package, and that opam-monorepo is (to = my >>> knowledge) only used by Mirage, I have merged mirage-opam-overlays >>> into opam-overlays and propose that going forward only opam-overlays >>> be used (and requires that all ports are cross-compilable). >>>=20 >>> mirage-opam-overlays is now empty and redirecting to opam-overlays, = so >>> no unikernels should be affected, but I'm ready to revert if this >>> change broke someone's workflow (Mirage-related or not), so please = let >>> me know if this is the case or if you have a use for the non-mirage >>> zarith port! >>>=20 >>> After some time in the absence of issues I'll submit a PR to mirage/ >>> mirage to produce Makefiles without mirage-opam-overlays. >>>=20 >>> Have a great day, >>>=20 >>> Virgile >>>=20 >>=20 >>=20 >=20 >=20 --Apple-Mail=_8816B11A-5D9A-4A92-9706-BA86B2F46B18 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Thanks for doing this Virgile! Is the = redirect actually necessary, as keeping
the mirage overlay empty = should be fine I think?

I'm also curious (as an = aside) what the differences between the mirage/dune
Zarith and = the opam-overlay dunified Zarith packages is. If it's just = the
cross-compilation glue, it's worth retiring the dunified = Zarith as the Mirage
one should be strictly = better.

best,
Anil

=
--
Anil Madhavapeddy, Professor = of Planetary Computing (https://anil.recoil.org)
Computer = Laboratory, University of Cambridge = (https://cst.cam.ac.uk)

On 13 Jul 2026, at 13:29, = Virgile Robles <virgile@tarides.com> wrote:

Hi Kate,

Thanks for = the report. Locally I never encountered any exceptions,
however I = realize that my tests never checked that the redirection
worked (I = tested having only opam-overlays = or
opam-overlays+mirage-opam-overlays), since I expected any user = of
mirage-opam-overlays to have opam-overlays added as = well.

And indeed opam doesn't seem to follow the redirect and I = couldn't find
a way to make it work.

For now I've re-added the = packages to mirage-opam-overlays, which is the
safer option (they are = still in opam-overlays, and mirage-opam-overlays
is still = deprecated).

Does that solve the issue you were = seeing?

Cheers,
Virgile

Le 11/07/2026 =C3=A0 19:58, = Kate a =C3=A9crit :
Hi,

Locally, = the first time i called opam update, this repository failed
with some = uncaught exception and even after non-failed subsequent
updates the = resulting repository wasn't the one it's supposed to be
redirected = to, thus leaving us with the empty repository.

Could you confirm = the redirection worked for you locally when you = tested
this?


Cheers,
Kate

On 7/8/26 17:18, = Virgile Robles wrote:
Dear = all,

Today our build infrastructure based on opam-monorepo is = relying on
all unikernel dependencies building with dune. To that = end, we have
two opam overlay repositories containing ports of = packages that do not
use dune upstream:

  * opam-overlays = <https://github.com/dune-universe/opam-overlays>:
  &nb= sp; historically decoupled from Mirage, containing almost all = ports
    guaranteed to build with dune but not = necessarily cross-compilable
  * mirage-opam-overlays = <https://github.com/dune-universe/mirage-opam-
    = overlays>: for ports that need further or different adaptations = to
    be cross-compilable, since we need it for = Mirage.

The second one actually only contains the zarith package, = for which we
have two different ports.

Following some = discussions we had some time ago observing there is
some seemingly = unnecessary complexity in having two separate
repositories for one = single package, and that opam-monorepo is (to my
knowledge) only used = by Mirage, I have merged mirage-opam-overlays
into opam-overlays and = propose that going forward only opam-overlays
be used (and requires = that all ports are cross-compilable).

mirage-opam-overlays is now = empty and redirecting to opam-overlays, so
no unikernels should be = affected, but I'm ready to revert if this
change broke someone's = workflow (Mirage-related or not), so please let
me know if this is = the case or if you have a use for the non-mirage
zarith = port!

After some time in the absence of issues I'll submit a PR = to mirage/
mirage to produce Makefiles without = mirage-opam-overlays.

Have a great = day,

Virgile






= --Apple-Mail=_8816B11A-5D9A-4A92-9706-BA86B2F46B18-- From mirageos-devel-bounces@lists.xenproject.org Mon Jul 13 22:53:50 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 13 Jul 2026 22:53:50 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1362000.1613991 (Exim 4.92) (envelope-from ) id 1wjPWu-0005b1-KA; Mon, 13 Jul 2026 22:53:40 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1362000.1613991; Mon, 13 Jul 2026 22:53:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjPWu-0005au-Ha; Mon, 13 Jul 2026 22:53:40 +0000 Received: by outflank-mailman (input) for mailman id 1362000; Mon, 13 Jul 2026 22:53:39 +0000 Received: from mx.expurgate.net ([194.145.224.20]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjPWt-0005aj-1t for mirageos-devel@lists.xenproject.org; Mon, 13 Jul 2026 22:53:39 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wjPWs-00FDIp-F1 for mirageos-devel@lists.xenproject.org; Tue, 14 Jul 2026 00:53:38 +0200 Received: from [10.42.69.8] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a556c36-bab6-0a2a0a5309dd-0a2a4508989e-28 for ; Tue, 14 Jul 2026 00:53:38 +0200 Received: from [95.215.58.177] (helo=out-177.mta1.migadu.com) by tlsNG-c1860d.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.2) (envelope-from ) id 6a556c71-ee29-0a2a45080019-5fd73ab19d27-3 for ; Tue, 14 Jul 2026 00:53:37 +0200 X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=key1 header.d=exn.st header.i="@exn.st" header.h="From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=exn.st; s=key1; t=1783983217; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RYa2cqKVYJzXY8+yyfShByJX1gTv+68/f94uhWmS0jU=; b=CZR71b02eW0QZ215BmJQyd7HqP4gQsHi4N/nQYYQ0FpQSJ6Rqmq1DsW8k2ysBot8uwCIe/ lTEh92SVkWdOJUSd9yde3j2Koq07GBIDDiiwlOJglxENEtETT9qkQkcwXnmpQjFv1jryFN PBxUjvxPHBjiAM+ZLdlD2yON7DKiewuOLuXB7qGafbkqVZvhi0ippB8kVP0uhE29hcUTwi s/vY+jq7ubE1L+5HfoLzDrkC0VBTt4Atp/n/lJNeha1oB9u5u+Y0lnIE4TDygyRObfIDla 0IiMxIjji/v0CWS6ZFbqIYA5FnRH2GgSSXJIZKHc0hXy4ZDNaRBJn5MsiYCS0w== Date: Mon, 13 Jul 2026 23:53:30 +0100 MIME-Version: 1.0 Subject: Re: Merge of opam-overlays and mirage-opam-overlays To: mirageos-devel@lists.xenproject.org References: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> Content-Language: en-GB, fr, de-DE X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kate In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT X-purgate-ID: tlsNG-c1860d/1783983218-7B22501C-C20D1FC4/0/0 X-purgate-type: clean X-purgate-size: 3278 Thanks, Would you be able to open a ticket on our bugtracker for the redirect issue? https://github.com/ocaml/opam/issues For the uncaught exception i'm gonna blame it on my setup because i can't reproduce it. Cheers, Kate On 7/13/26 13:29, Virgile Robles wrote: > Hi Kate, > > Thanks for the report. Locally I never encountered any exceptions, > however I realize that my tests never checked that the redirection > worked (I tested having only opam-overlays or > opam-overlays+mirage-opam-overlays), since I expected any user of > mirage-opam-overlays to have opam-overlays added as well. > > And indeed opam doesn't seem to follow the redirect and I couldn't find > a way to make it work. > > For now I've re-added the packages to mirage-opam-overlays, which is the > safer option (they are still in opam-overlays, and mirage-opam-overlays > is still deprecated). > > Does that solve the issue you were seeing? > > Cheers, > Virgile > > Le 11/07/2026 à 19:58, Kate a écrit : >> Hi, >> >> Locally, the first time i called opam update, this repository failed >> with some uncaught exception and even after non-failed subsequent >> updates the resulting repository wasn't the one it's supposed to be >> redirected to, thus leaving us with the empty repository. >> >> Could you confirm the redirection worked for you locally when you tested >> this? >> >> >> Cheers, >> Kate >> >> On 7/8/26 17:18, Virgile Robles wrote: >>> Dear all, >>> >>> Today our build infrastructure based on opam-monorepo is relying on >>> all unikernel dependencies building with dune. To that end, we have >>> two opam overlay repositories containing ports of packages that do not >>> use dune upstream: >>> >>>   * opam-overlays : >>>     historically decoupled from Mirage, containing almost all ports >>>     guaranteed to build with dune but not necessarily cross-compilable >>>   * mirage-opam-overlays >>     overlays>: for ports that need further or different adaptations to >>>     be cross-compilable, since we need it for Mirage. >>> >>> The second one actually only contains the zarith package, for which we >>> have two different ports. >>> >>> Following some discussions we had some time ago observing there is >>> some seemingly unnecessary complexity in having two separate >>> repositories for one single package, and that opam-monorepo is (to my >>> knowledge) only used by Mirage, I have merged mirage-opam-overlays >>> into opam-overlays and propose that going forward only opam-overlays >>> be used (and requires that all ports are cross-compilable). >>> >>> mirage-opam-overlays is now empty and redirecting to opam-overlays, so >>> no unikernels should be affected, but I'm ready to revert if this >>> change broke someone's workflow (Mirage-related or not), so please let >>> me know if this is the case or if you have a use for the non-mirage >>> zarith port! >>> >>> After some time in the absence of issues I'll submit a PR to mirage/ >>> mirage to produce Makefiles without mirage-opam-overlays. >>> >>> Have a great day, >>> >>> Virgile >>> >> >> > > From mirageos-devel-bounces@lists.xenproject.org Tue Jul 14 12:48:26 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jul 2026 12:48:26 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1362374.1614197 (Exim 4.92) (envelope-from ) id 1wjcYa-0003KO-S9; Tue, 14 Jul 2026 12:48:16 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1362374.1614197; Tue, 14 Jul 2026 12:48:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjcYa-0003KH-Ok; Tue, 14 Jul 2026 12:48:16 +0000 Received: by outflank-mailman (input) for mailman id 1362374; Tue, 14 Jul 2026 12:48:14 +0000 Received: from mx.expurgate.net ([194.145.224.20]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wjcYY-0003KB-JG for mirageos-devel@lists.xenproject.org; Tue, 14 Jul 2026 12:48:14 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wjcYX-00Afw8-SS for mirageos-devel@lists.xenproject.org; Tue, 14 Jul 2026 14:48:14 +0200 Received: from [10.42.69.8] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a56300a-e002-0a2a0a5209dd-0a2a45088e80-36 for ; Tue, 14 Jul 2026 14:48:13 +0200 Received: from [209.85.128.50] (helo=mail-wm1-f50.google.com) by tlsNG-c1860d.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.1) (envelope-from ) id 6a56300d-f659-0a2a45080019-d1558032f02f-3 for ; Tue, 14 Jul 2026 14:48:13 +0200 Received: by mail-wm1-f50.google.com with SMTP id 5b1f17b1804b1-493b77b150aso6495195e9.2 for ; Tue, 14 Jul 2026 05:48:13 -0700 (PDT) Received: from ?IPV6:2a01:e0a:813:8090:bcf4:88b6:4894:1927? ([2a01:e0a:813:8090:bcf4:88b6:4894:1927]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-49508724786sm75639545e9.3.2026.07.14.05.48.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 14 Jul 2026 05:48:12 -0700 (PDT) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=20251104 header.d=tarides-com.20251104.gappssmtp.com header.i="@tarides-com.20251104.gappssmtp.com" header.h="Content-Transfer-Encoding:Content-Type:In-Reply-To:From:Content-Language:References:Cc:To:Subject:User-Agent:MIME-Version:Date:Message-ID" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tarides-com.20251104.gappssmtp.com; s=20251104; t=1784033293; x=1784638093; darn=lists.xenproject.org; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to :content-type; bh=KfPfbXsjiwlt9KOXX8tueJjGq7FZHYWdJmWJk2fhgqU=; b=Ha8MIHriiJIcAYF5rMfhrvz+Yp2/5vpEnKo48U8VUxghGoU0ndWxrFeny8fp83btc5 w5QOMoycKFLBmdfVyLWNqa0XTJY0UdDbIpuWrv54bS8lEkDSx8N2QVJMg0E8iWyfKAWM PFlyV/NUoiwRHhXTUrvIGnRIfNwXvLvkNOO32CGcJIYEVxpriaQVt3+xOFW7ogeLlZSs 1+AW4kx4KxuiC06VZj4LxsbkQn2caKyqTwJqQFyv42JY+biN2z+C2AEYbFyOI2OI56AQ tMMrD6T62YdpQIfNjEwNWxETLbawwgsvm+ZVqA46fVVmZgG5ATngdPECbI4xOJGwCUJ/ rulA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784033293; x=1784638093; h=content-transfer-encoding:content-type:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=KfPfbXsjiwlt9KOXX8tueJjGq7FZHYWdJmWJk2fhgqU=; b=S8Te+hn3V7O2mwbc4PESU5VbplIOqfL091NJD2UX+Ru8DyAgZyvcOgR5InKHDHnunY 4/1kSZI4X8sNn174ztrmPtlCke7XaJtCrn3YgGMOyGzmrYGgxWKh0jyY4Ldn+0cg9t+d VoLo94L5+EsUUatoO44Xyfau9Z6xGwYm1hLeWqWrcV6W6P+MrREeWzMgsjv4k5L398Q3 poxi9n+dfbfNxgExA4JYI4iBk1GHeNJwU4EvB6K1cxzTiAj7ppfTOx/Nv8+S/LG6ci5g lOwrLht8ew7/boy1B0pHKNak34Jy3LeFMY/8+nxWty1i3FVrdTDl3WQKpgb5SGw713fZ FDEw== X-Gm-Message-State: AOJu0Yw6yeoxOvRz0eB3xZO14SX3RmV+/qrxkTEY+I9mr8wpG5/e6IKa ZzUZsw0BX4OfMFMxVN5YDNaXMJJobtQ9Ny8wTEenmsTrGly5ak/mjtTVUfpmWPD8voc1ZpLPtDT X4qYLhpg= X-Gm-Gg: AfdE7clXgIlaiYhetdSd0RUQxkZFO8LjeZHT5zFQD4AHkJPEiVy9orENirhf96zKftl 4hpnFdjT27k8HsOY5AY52HTQai84AkdVBWm2CIjk17CG8IaXHn/lViuvZrEJRayDYjjPQZcG6iT vHFi83vgeADyRZ5EPiSWe+IroMXklS6wxs9icBaPY2cUXCLBptYxRrFzjEndMSQ+4gznWVtslt4 hMIW2lNwy8icy/krKTZCxnlefxBs6bMMDj+ZpS0Wp4wcVoa6Q2UO0rxd7S4ay+W4hln+v3b5Sgv 905JnMtR9fP89BHV46iHCcSI78PNZuAqchwEQzWTNLTcEzCSiTntTieyol12wVytrPOuUTk14mh X4131fAeZCECLOWHOf8xfIUVA2fQh7U7eEeJo/7KyP+hcvORcOIZj2FB9wTI/HF3TuyOMt6WZqs B4EfuJrIOdFNWd67BXkLfnRGzAj0kNO0JLioZKY9P1pNb2sGRCfuVdfY6c/pz57ReTW+a813bdn 3BrY9A5mcXJ18UmMA== X-Received: by 2002:a05:600c:80c5:b0:493:a570:df7d with SMTP id 5b1f17b1804b1-493f881d20fmr94259925e9.20.1784033293112; Tue, 14 Jul 2026 05:48:13 -0700 (PDT) Message-ID: <424fe1fe-da64-48ff-b686-8ebf8a3dc09f@tarides.com> Date: Tue, 14 Jul 2026 14:48:12 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Merge of opam-overlays and mirage-opam-overlays To: Anil Madhavapeddy Cc: mirageos-devel@lists.xenproject.org References: <0bac0d33-bd66-4440-a19c-f029718bd267@tarides.com> <04D998D3-B6DD-4883-B049-637753053117@cl.cam.ac.uk> Content-Language: en-US From: Virgile Robles In-Reply-To: <04D998D3-B6DD-4883-B049-637753053117@cl.cam.ac.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-purgate-ID: tlsNG-c1860d/1784033293-D6B4187B-72548B5D/0/0 X-purgate-type: clean X-purgate-size: 4025 Hi Anil, > Is the redirect actually necessary, as keeping > the mirage overlay empty should be fine I think? It's not strictly necessary, but it would have been a good use case of redirects. > I'm also curious (as an aside) what the differences between the mirage/dune > Zarith and the opam-overlay dunified Zarith packages is. If it's just the > cross-compilation glue, it's worth retiring the dunified Zarith as the > Mirage one should be strictly better. They are very similar, but indeed the mirage port (done and maintained by Dinosaure and Hannes) seems strictly better and cleaner at discovering its environment both for cross-compilation or not. Best, Virgile > best, > Anil > > /-- > Anil Madhavapeddy, Professor of Planetary Computing (https:// > anil.recoil.org) > Computer Laboratory, University of Cambridge (https://cst.cam.ac.uk)/ > >> On 13 Jul 2026, at 13:29, Virgile Robles wrote: >> >> Hi Kate, >> >> Thanks for the report. Locally I never encountered any exceptions, >> however I realize that my tests never checked that the redirection >> worked (I tested having only opam-overlays or >> opam-overlays+mirage-opam-overlays), since I expected any user of >> mirage-opam-overlays to have opam-overlays added as well. >> >> And indeed opam doesn't seem to follow the redirect and I couldn't find >> a way to make it work. >> >> For now I've re-added the packages to mirage-opam-overlays, which is the >> safer option (they are still in opam-overlays, and mirage-opam-overlays >> is still deprecated). >> >> Does that solve the issue you were seeing? >> >> Cheers, >> Virgile >> >> Le 11/07/2026 à 19:58, Kate a écrit : >>> Hi, >>> >>> Locally, the first time i called opam update, this repository failed >>> with some uncaught exception and even after non-failed subsequent >>> updates the resulting repository wasn't the one it's supposed to be >>> redirected to, thus leaving us with the empty repository. >>> >>> Could you confirm the redirection worked for you locally when you tested >>> this? >>> >>> >>> Cheers, >>> Kate >>> >>> On 7/8/26 17:18, Virgile Robles wrote: >>>> Dear all, >>>> >>>> Today our build infrastructure based on opam-monorepo is relying on >>>> all unikernel dependencies building with dune. To that end, we have >>>> two opam overlay repositories containing ports of packages that do not >>>> use dune upstream: >>>> >>>>   * opam-overlays : >>>>     historically decoupled from Mirage, containing almost all ports >>>>     guaranteed to build with dune but not necessarily cross-compilable >>>>   * mirage-opam-overlays >>>     overlays>: for ports that need further or different adaptations to >>>>     be cross-compilable, since we need it for Mirage. >>>> >>>> The second one actually only contains the zarith package, for which we >>>> have two different ports. >>>> >>>> Following some discussions we had some time ago observing there is >>>> some seemingly unnecessary complexity in having two separate >>>> repositories for one single package, and that opam-monorepo is (to my >>>> knowledge) only used by Mirage, I have merged mirage-opam-overlays >>>> into opam-overlays and propose that going forward only opam-overlays >>>> be used (and requires that all ports are cross-compilable). >>>> >>>> mirage-opam-overlays is now empty and redirecting to opam-overlays, so >>>> no unikernels should be affected, but I'm ready to revert if this >>>> change broke someone's workflow (Mirage-related or not), so please let >>>> me know if this is the case or if you have a use for the non-mirage >>>> zarith port! >>>> >>>> After some time in the absence of issues I'll submit a PR to mirage/ >>>> mirage to produce Makefiles without mirage-opam-overlays. >>>> >>>> Have a great day, >>>> >>>> Virgile >>>> >>> >>> >> >> > From mirageos-devel-bounces@lists.xenproject.org Fri Jul 31 19:39:04 2026 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 31 Jul 2026 19:39:04 +0000 Received: from list by lists.xenproject.org with outflank-mailman.1379581.1624060 (Exim 4.92) (envelope-from ) id 1wpt4I-0000xH-9B; Fri, 31 Jul 2026 19:38:54 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1379581.1624060; Fri, 31 Jul 2026 19:38:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wpt4I-0000xA-67; Fri, 31 Jul 2026 19:38:54 +0000 Received: by outflank-mailman (input) for mailman id 1379581; Fri, 31 Jul 2026 19:38:53 +0000 Received: from mx.expurgate.net ([195.190.135.10]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1wpt4H-0000x4-He for mirageos-devel@lists.xenproject.org; Fri, 31 Jul 2026 19:38:53 +0000 Received: from mx.expurgate.net (helo=localhost) by mx.expurgate.net with esmtp id 1wpt4G-004BPH-MD for mirageos-devel@lists.xenproject.org; Fri, 31 Jul 2026 21:38:52 +0200 Received: from [10.42.69.2] (helo=localhost) by localhost with ESMTP (eXpurgate MTA 0.9.1) (envelope-from ) id 6a6cf971-bab6-0a2a0a5309dd-0a2a45029104-46 for ; Fri, 31 Jul 2026 21:38:52 +0200 Received: from [185.205.69.213] (helo=mail.w13.tutanota.de) by tlsNG-720697.mxtls.expurgate.net with ESMTPS (eXpurgate 4.57.1) (envelope-from ) id 6a6cf9cc-6ca4-0a2a45020019-b9cd45d59572-3 for ; Fri, 31 Jul 2026 21:38:52 +0200 Received: from tutadb.w10.tutanota.de (w10.api.tuta.com [IPv6:fd:ac::d:10]) by mail.w13.tutanota.de (Postfix) with ESMTP id 2758516772F9A for ; Fri, 31 Jul 2026 21:38:52 +0200 (CEST) X-BeenThere: mirageos-devel@lists.xenproject.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mirageos-devel-bounces@lists.xenproject.org Precedence: list Sender: "MirageOS-devel" Authentication-Results: eu.smtp.expurgate.cloud; dkim=pass header.s=s1 header.d=tuta.io header.i="@tuta.io" header.h="From:To:Subject:Content-Type:Content-Transfer-Encoding:Cc:Date:MIME-Version:Message-ID" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1785526732; s=s1; d=tuta.io; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender; bh=KfeYm9kWCUKR4gLmWBcRqJfFpWyRRwMAp031WqNW/bY=; b=kUyvQipHifGnuTfSvwY33L00AoZVhq+JR73QSW/lLpTV82lK0LAjdejmhYMgarzs UmaB6AxZCZDbtbwmwIfx6jY8Sk3bXfXl3BbEJwHpXtufVgFPBPYxkxriYX7CrywvLNX kV1YzaXZg8E4Ixocexb/Bn8f+W+w6Py/2grpNTslFZ58qq22o+iBY3mThWdZrtOfV7V 75xJ0daBsmPOyU6/ESJFG/Zf3Y6ODG4oyrWc2zIIcgPopZNPnPVbmUIplP2k2h8m5Kc Rmgaa/pzU0lhsElHXsnrlDXvZEvIJuS9+FXNUPssuQrRGJ4eSbMaJL8yIiPuGH+PflU XEyeJ6uQYg== Date: Fri, 31 Jul 2026 21:38:52 +0200 (CEST) From: pierre.alain@tuta.io To: Mirageos Devel Cc: Pierre Alain Message-ID: Subject: Mirage-net-xen and Generic Segmentation Offload, and question about genAI and code MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Feedback-ID: 01eaf8ab5c4fb66a25616152514a399f598322e6638868ba822dedd227211ef3e68edf4699e2849fa51d28ca2bbb961117ec852d94c0b4e715ebab57f6709efd92:TurnOnPrivacy!:tutamail X-purgate-ID: tlsNG-720697/1785526732-F0CA22AC-C4A6105F/0/0 X-purgate-type: clean X-purgate-size: 2411 Dear All, I've started some time ago (maybe years?) to add Generic Segmentation Offlo= ad to mirage-net-xen to improve bandwidth for qubes-mirage-firewall, becaus= e I observed that it introduced a large restriction compared to a Linux ker= nel firewall [1]. That was very long, and now I'm happy to announce that I have some PRs [2-5= ] that enable GSO with qubes-mirage-firewall. The 'good' thing is that I've= got the following results on Qubes using iperf3 for 10 second runs between= two VMs with a firewall in between (run only once, and 10s, so I won't com= mit to exact figures, just take the overall picture): - GSO disabled with qubes-mirage-firewall: 0.531 Gbit/s (current head is at= 0.350 Gbit/s) vs. Linux: 1.92 Gbit/s, ratio 3.62 - GSO enabled with qubes-mirage-firewall: 3.16 Gbit/s vs. Linux-fw: 6.16 Gb= it/s, ratio 1.95 So now we're only roughly half the performance of Linux \o/ Although there is still a lot of work to do to improve the bandwidth, it's = not on the GSO path any more. The 'bad' thing, leading to this email, is that across the branches for mir= age-xen, mirage-net-xen, mirage-nat and qubes-mirage-firewall, some (a lot = of) findings and code were produced using Claude Opus 5 as a 'rubber duck'.= I tried to be explicit in the commits about the help I got from it, from f= indings to co-authorship, and I want to convey that, even if I've done a lo= t of work before, I would not have been able to finish so quickly without t= hat tool. It really helped me a lot for tracking issues in pcaps, comparing= packets byte by byte, finding references in the Xen or Linux sources, etc. So my question about this work is whether the way I disclosed it in the com= mits the right granularity? Especially, when Claude Opus is credited with c= o-authorship (e.g. the mirage-xen PR [3]), it means the code was written by= the tool and reviewed by me,=C2=A0I cannot guarantee that the same code do= es not exist in another repository, possibly under a more restrictive licen= ce. Best, Pierre [1]:=C2=A0https://github.com/mirage/qubes-mirage-firewall/issues/130#issuec= omment-1571959103 [2]:=C2=A0https://github.com/mirage/mirage-net-xen/pull/117 [3]:=C2=A0https://github.com/mirage/mirage-xen/pull/56 [4]:=C2=A0https://github.com/mirage/mirage-nat/pull/54 [5]:=C2=A0https://github.com/mirage/mirage-nat/pull/53 -- P.