Re: [gentoo-dev] Package stabilization groups

2023-07-16 Thread Arthur Zamarin
On 16/07/2023 21.11, Ulrich Mueller wrote:
>> On Sun, 16 Jul 2023, Arthur Zamarin wrote:
> 
>> - enables an easier syntax as `pkgdev bugs @group1` to file a single bug
>> for all of them. In Gnome's case as an example, we could have "gnome1",
>> "gnome2", "gnome3", "gnome4", etc - groups standing for multiple
>> "layers/stages" of stabilizing, and then you could just file `pkgdev
>> bugs @gnome{1..4}` to file "at one click" the whole gnome stablereqs.
> 
> Can't we do the same that we do for local use flags? Namely, define them
> in metadata.xml, but collect them in one central location?

Do note that this grouping is done at "metadata repo", and not the
normal git repo where development is done. Meaning you need to manually
add the package to the central "index".

> Ulrich

-- 
Arthur Zamarin
arthur...@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)



OpenPGP_signature
Description: OpenPGP digital signature


Re: [gentoo-dev] Package stabilization groups

2023-07-16 Thread Ulrich Mueller
> On Sun, 16 Jul 2023, Arthur Zamarin wrote:

> Let me list some things as advantages to each one (since I see an
> advantage to one as disadvantage to other).

> Advantages of field in metadata.xml:

> - local to package, easier to not miss. Easier to follow for the maintainer.

> - easier to find which group the current package relates to

> Advantages to group files:

> - easier to index (one file listing all children, instead of searching
> across repo who defines it)

> - easier to not repeat group. In the metadata field it might happen to
> repeat, less likely since it is easy to search, but similar group names
> might be created, merging them into one by mistake, or creating very
> similar names and mistaking them. When we have a single file, it is
> easier to see the whole picture and verify things.

> - since this is compressed information (special files instead of spread
> over repo), we could load all of them into app's cache, and make all
> computation easier.

> - enables an easier syntax as `pkgdev bugs @group1` to file a single bug
> for all of them. In Gnome's case as an example, we could have "gnome1",
> "gnome2", "gnome3", "gnome4", etc - groups standing for multiple
> "layers/stages" of stabilizing, and then you could just file `pkgdev
> bugs @gnome{1..4}` to file "at one click" the whole gnome stablereqs.

Can't we do the same that we do for local use flags? Namely, define them
in metadata.xml, but collect them in one central location?

Ulrich


signature.asc
Description: PGP signature


Re: [gentoo-dev] Package stabilization groups

2023-07-16 Thread Arthur Zamarin
On 16/07/2023 17.57, Matt Turner wrote:
> Hello,
> 
> Many of us have started using `pkgdev bugs` to file stabilization
> bugs. It works well (Thanks Arthur!) and I encourage everyone to give
> it a try.

Gladly :) You can semi-blame mgorny for the creation of `pkgdev bugs`,
because I started to file stablereqs for @python packages, and at some
point it was too tiring and repetitive, so I was brought to the drawing
table to think of a solution.

> Where possible, it files one stabilization bug per package. This makes
> arch testers' jobs easier and makes the task easier to automate.
> 
> But sometimes we do want to stabilize packages together. For example
> major versions of x11-wm/mutter and gnome-base/gnome-shell are tied
> together. If a new mutter is stabilized without the new gnome-shell,
> the tree will still be consistent, but emerge -u @world will warn
> users that the mutter upgrade is blocked.
> 
> There was some brief discussion on IRC about how to document these
> groupings, and two main ideas were suggested:
> 
> - add a field to metadata.xml to specify the group by an arbitrary name.
>   E.g. 
>   Each package in the group would specify the same value of name="..."
> 
> - maintain the groups in a separate place (similar to portage @sets).
> 
> Can anyone think of particular advantages or disadvantages to one
> solution versus the other? Any other (better) ideas?

Let me list some things as advantages to each one (since I see an
advantage to one as disadvantage to other).

Advantages of field in metadata.xml:

- local to package, easier to not miss. Easier to follow for the maintainer.

- easier to find which group the current package relates to

Advantages to group files:

- easier to index (one file listing all children, instead of searching
across repo who defines it)

- easier to not repeat group. In the metadata field it might happen to
repeat, less likely since it is easy to search, but similar group names
might be created, merging them into one by mistake, or creating very
similar names and mistaking them. When we have a single file, it is
easier to see the whole picture and verify things.

- since this is compressed information (special files instead of spread
over repo), we could load all of them into app's cache, and make all
computation easier.

- enables an easier syntax as `pkgdev bugs @group1` to file a single bug
for all of them. In Gnome's case as an example, we could have "gnome1",
"gnome2", "gnome3", "gnome4", etc - groups standing for multiple
"layers/stages" of stabilizing, and then you could just file `pkgdev
bugs @gnome{1..4}` to file "at one click" the whole gnome stablereqs.

> Thanks,
> Matt


Now I'll speak from the point of implementer of `pkgdev bugs`. For me I
think both approaches are good, but I would prefer the latter over the
former. Nicer syntax, easy cache of all groups, easier to solve the
"graph problems" in the tool.

-- 
Arthur Zamarin
arthur...@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)



OpenPGP_signature
Description: OpenPGP digital signature


Re: [gentoo-dev] Package stabilization groups

2023-07-16 Thread Matt Turner
On Sun, Jul 16, 2023 at 11:15 AM Fabian Groffen  wrote:
>
> On 16-07-2023 10:57:54 -0400, Matt Turner wrote:
> > Hello,
> >
> > Many of us have started using `pkgdev bugs` to file stabilization
> > bugs. It works well (Thanks Arthur!) and I encourage everyone to give
> > it a try.
> >
> > Where possible, it files one stabilization bug per package. This makes
> > arch testers' jobs easier and makes the task easier to automate.
> >
> > But sometimes we do want to stabilize packages together. For example
> > major versions of x11-wm/mutter and gnome-base/gnome-shell are tied
> > together. If a new mutter is stabilized without the new gnome-shell,
> > the tree will still be consistent, but emerge -u @world will warn
> > users that the mutter upgrade is blocked.
> >
> > There was some brief discussion on IRC about how to document these
> > groupings, and two main ideas were suggested:
> >
> > - add a field to metadata.xml to specify the group by an arbitrary name.
> >   E.g. 
> >   Each package in the group would specify the same value of name="..."
> >
> > - maintain the groups in a separate place (similar to portage @sets).
> >
> > Can anyone think of particular advantages or disadvantages to one
> > solution versus the other? Any other (better) ideas?
>
> I don't know how widespread the problem is, and how much it can be
> generalised, but could you perhaps use a virtual, such that
> stabilisation of the virtual means the deps must be satisfied?

Heh, I guess we could do that if we had no other options.



Re: [gentoo-dev] Package stabilization groups

2023-07-16 Thread Fabian Groffen
On 16-07-2023 10:57:54 -0400, Matt Turner wrote:
> Hello,
> 
> Many of us have started using `pkgdev bugs` to file stabilization
> bugs. It works well (Thanks Arthur!) and I encourage everyone to give
> it a try.
> 
> Where possible, it files one stabilization bug per package. This makes
> arch testers' jobs easier and makes the task easier to automate.
> 
> But sometimes we do want to stabilize packages together. For example
> major versions of x11-wm/mutter and gnome-base/gnome-shell are tied
> together. If a new mutter is stabilized without the new gnome-shell,
> the tree will still be consistent, but emerge -u @world will warn
> users that the mutter upgrade is blocked.
> 
> There was some brief discussion on IRC about how to document these
> groupings, and two main ideas were suggested:
> 
> - add a field to metadata.xml to specify the group by an arbitrary name.
>   E.g. 
>   Each package in the group would specify the same value of name="..."
> 
> - maintain the groups in a separate place (similar to portage @sets).
> 
> Can anyone think of particular advantages or disadvantages to one
> solution versus the other? Any other (better) ideas?

I don't know how widespread the problem is, and how much it can be
generalised, but could you perhaps use a virtual, such that
stabilisation of the virtual means the deps must be satisfied?

Thanks,
Fabian

-- 
Fabian Groffen
Gentoo on a different level


signature.asc
Description: PGP signature


[gentoo-dev] Package stabilization groups

2023-07-16 Thread Matt Turner
Hello,

Many of us have started using `pkgdev bugs` to file stabilization
bugs. It works well (Thanks Arthur!) and I encourage everyone to give
it a try.

Where possible, it files one stabilization bug per package. This makes
arch testers' jobs easier and makes the task easier to automate.

But sometimes we do want to stabilize packages together. For example
major versions of x11-wm/mutter and gnome-base/gnome-shell are tied
together. If a new mutter is stabilized without the new gnome-shell,
the tree will still be consistent, but emerge -u @world will warn
users that the mutter upgrade is blocked.

There was some brief discussion on IRC about how to document these
groupings, and two main ideas were suggested:

- add a field to metadata.xml to specify the group by an arbitrary name.
  E.g. 
  Each package in the group would specify the same value of name="..."

- maintain the groups in a separate place (similar to portage @sets).

Can anyone think of particular advantages or disadvantages to one
solution versus the other? Any other (better) ideas?

Thanks,
Matt



Re: [gentoo-dev] [PATCH 1/7] eclass/nuget.eclass: introduce new eclass

2023-07-16 Thread Maciej Barć

Offtopic: That calls for a YAS snippet ;D

W dniu 16.07.2023 o 15:40, Ulrich Mueller pisze:

On Sun, 16 Jul 2023, Maciej Barć wrote:



+case "${EAPI}" in
+   7 | 8 )
+   :
+   ;;
+   * )
+   die "${ECLASS}: EAPI ${EAPI} unsupported."
+   ;;
+esac


The QA team has invested quite some work to unify that case block
between different eclasses. So, please stay with the standard style:

case ${EAPI} in
7|8) ;;
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
esac


--
Have a great day!

~ Maciej XGQT Barć

x...@gentoo.org
Gentoo Linux developer
(dotnet, emacs, math, ml, nim, scheme, sci)
https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C



Re: [gentoo-dev] [PATCH 1/7] eclass/nuget.eclass: introduce new eclass

2023-07-16 Thread Ulrich Mueller
> On Sun, 16 Jul 2023, Maciej Barć wrote:

> +case "${EAPI}" in
> + 7 | 8 )
> + :
> + ;;
> + * )
> + die "${ECLASS}: EAPI ${EAPI} unsupported."
> + ;;
> +esac

The QA team has invested quite some work to unify that case block
between different eclasses. So, please stay with the standard style:

case ${EAPI} in
7|8) ;;
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
esac


signature.asc
Description: PGP signature


Re: [gentoo-dev] [PATCH 6/7] dev-dotnet/dotnet-sdk-bin: update packaging mechanism

2023-07-16 Thread Maciej Barć

+RESTRICT+=" splitdebug "
+


Why? Add a comment.



Added by previous maint.


+PDEPEND="
+   ~dev-dotnet/dotnet-runtime-nugets-${RUNTIME_SLOT}
+   ~dev-dotnet/dotnet-runtime-nugets-3.1.32
+"
+


What's this about?


Wanted to comment right away, but needed to wait for mialing list to 
digest my patches.


Ok, so essentially when building .NET packages dotnet-sdk will 
**always** pull in a set of predefined nugets that need to be in the 
${NUGET_PACKAGES} dir. If they are not there, then the build fails.


Because otherwise we would have to have a very ugly if-else in the 
eclass we pull them regardless if user will build dev-dotnet packages.


The elcass later copies those nugets from /opt/dotnet-nugest to 
NUGEt_PACKAGES dir.


This set is different for each dotnet-sdk version and has to be checked 
while packaging new dotnet-sdk versions by restoring a package without 
other dependencies for each supported .NET version: that is: 3.1, 6.0 
and 7.0.


W dniu 16.07.2023 o 14:58, Sam James pisze:


Maciej Barć  writes:


Bug: https://bugs.gentoo.org/900597
Bug: https://github.com/gentoo/gentoo/pull/29309
Signed-off-by: Maciej Barć 
---
  dev-dotnet/dotnet-sdk-bin/Manifest| 36 ++
  .../dotnet-sdk-bin-6.0.402-r3.ebuild  | 65 ++
  .../dotnet-sdk-bin-6.0.404-r1.ebuild  | 65 ++
  .../dotnet-sdk-bin-7.0.200-r1.ebuild  | 66 +++
  .../dotnet-sdk-bin-7.0.203.ebuild | 66 +++
  dev-dotnet/dotnet-sdk-bin/metadata.xml|  6 +-
  6 files changed, 287 insertions(+), 17 deletions(-)
  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.404-r1.ebuild
  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.200-r1.ebuild
  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.203.ebuild

diff --git a/dev-dotnet/dotnet-sdk-bin/Manifest 
b/dev-dotnet/dotnet-sdk-bin/Manifest
index 0db1365533..34d9d16893 100644
--- a/dev-dotnet/dotnet-sdk-bin/Manifest
+++ b/dev-dotnet/dotnet-sdk-bin/Manifest
@@ -1,12 +1,24 @@
-DIST dotnet-sdk-6.0.404-linux-arm.tar.gz 181563995 BLAKE2B 
ff359d26264f0298d6210a2b7ae8cd0f1b577bf9937aaff09805f361e54349bdab5338182b674c81c8cb330c90f7a17a601ccce899e63f2e837a90bfd02c3726
 SHA512 
1b9b5e0c45f90a4c752bf6990e5dda4110403a62392dc78abf9145c69b1d329b2630945a88cb4d7756322b188b7f4a9334bfc376067edff5dcfabfd85098d7d8
-DIST dotnet-sdk-6.0.404-linux-arm64.tar.gz 180324700 BLAKE2B 
33780337294f427da0b8d44d8a3819c4276c0b01ffefe5a846cc5524039a5af203a231fe5893c63dce5b1557cd1288c4cb3e1d93505320a49eeccd4fd22cefe7
 SHA512 
7c58595aa57b655ff5a268ae4fc680ff3fb15a84dcc0ce84ae7eb25ba27bf66f0c5273c985f15034583f5b05437a5354db68c4064953030dc4caebb11339ac76
-DIST dotnet-sdk-6.0.404-linux-musl-arm.tar.gz 182613890 BLAKE2B 
f0475535f703a80c23a881ef578eeac87923586b27bcc7ed018b75aa88dccc84dcbd9e20543b1e502e0e800b947afd8e6bbc3a44b4101ad786674d0ad2fb196a
 SHA512 
d7818ea567db81832cfeed5057c42255d2f19750a741a2cbc57e2d7134267a27e9937f86846b30f393c6f0ad2dbf0f4c73a902ed78b0de56138f077f62f34686
-DIST dotnet-sdk-6.0.404-linux-musl-arm64.tar.gz 180323728 BLAKE2B 
ff32a89653f265df2fda39dc0bb2ff6853e6fced029fb1a16096436a7876ad061e55a1d45fd29f395e4d6585f67cde2e5d95b0c0c2bbaec2b073cfd2785c87e5
 SHA512 
999220f7247881d44c7f5a429b25c04d31044a1b91af5ede3f899df142af2d9f056a4ac6058c9e56f14b014a479f3a7455bd499f42f8e0f9b4fcacfeabc023b5
-DIST dotnet-sdk-6.0.404-linux-musl-x64.tar.gz 185037621 BLAKE2B 
0ff97d56c4d061cb5f227c745afb34cf462c286f4c0347224885360cec861dfd59f90a6ef85571c49aa79b12d558111b07a29ac48451739f721e5b13d45f94c1
 SHA512 
5313d8cbb41e27f462a141914f852e3d3e729886ce063be82778e1444df2d44dadcd2829f60ae97ae300d19798fab9d3b3932a7d9b9d00e948a80ccebbf5e106
-DIST dotnet-sdk-6.0.404-linux-x64.tar.gz 185546757 BLAKE2B 
ce8447f82b93880c6491e06fd35d556b880f59403fd7c6161d228271de6bffc6c74810e5ec5d834e35a715b9bc6173cb028aeb443bd28717a2d8838b543eec9f
 SHA512 
7a0f4b308d3fe98df9b426b0f8f8fb7bd7247244af3570e867a3969349c62c7ea4c6da81a1a2280788e300784167a2933db523f461985aef0681e0cf14bf8f0d
-DIST dotnet-sdk-7.0.200-linux-arm.tar.gz 192996891 BLAKE2B 
43c271a53d2eeebfbbeb7702e0c7a203960b57246f4b1f557d78391abdf10d0cca87c7ee364a37151f8e9e91df53e427df077a7cc25e1ccce5ac5d37fc73bc3a
 SHA512 
7b1072c8080a0f38946d207945417dbeea4cbb688c2ea2dba1cb31330da15652da0823d8571c063a08830fe2157dbacb635eb2a8c7f20033cd1b8a35a9cfde36
-DIST dotnet-sdk-7.0.200-linux-arm64.tar.gz 193106712 BLAKE2B 
5db6eab8bf56a85a15e6107bd4bca0dd4669d9eb2b3db287b8aa7621e38e07ce213c8e2446add010623b78b7092c0658d17bf4c90a059440778519e5aa117a9e
 SHA512 
2990b7d2b23adb2b2621786ba774450e8cf73bf872173ab57026d7658599accdb5a4cefb5292945e264408f833503210621ed787c8d77eb467d3b204da8073a8
-DIST dotnet-sdk-7.0.200-linux-musl-arm.tar.gz 192955116 BLAKE2B 
5b5549e158ebc7059b123d601566efddaacd04aa6ee531699b3c70327b2f2005ed11cbb7dea7b9a8a9c5f792fcc7461ea34b0a33a81828b4085327f21

Re: [gentoo-dev] [PATCH 6/7] dev-dotnet/dotnet-sdk-bin: update packaging mechanism

2023-07-16 Thread Sam James

Maciej Barć  writes:

> Bug: https://bugs.gentoo.org/900597
> Bug: https://github.com/gentoo/gentoo/pull/29309
> Signed-off-by: Maciej Barć 
> ---
>  dev-dotnet/dotnet-sdk-bin/Manifest| 36 ++
>  .../dotnet-sdk-bin-6.0.402-r3.ebuild  | 65 ++
>  .../dotnet-sdk-bin-6.0.404-r1.ebuild  | 65 ++
>  .../dotnet-sdk-bin-7.0.200-r1.ebuild  | 66 +++
>  .../dotnet-sdk-bin-7.0.203.ebuild | 66 +++
>  dev-dotnet/dotnet-sdk-bin/metadata.xml|  6 +-
>  6 files changed, 287 insertions(+), 17 deletions(-)
>  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
>  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.404-r1.ebuild
>  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.200-r1.ebuild
>  create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.203.ebuild
>
> diff --git a/dev-dotnet/dotnet-sdk-bin/Manifest 
> b/dev-dotnet/dotnet-sdk-bin/Manifest
> index 0db1365533..34d9d16893 100644
> --- a/dev-dotnet/dotnet-sdk-bin/Manifest
> +++ b/dev-dotnet/dotnet-sdk-bin/Manifest
> @@ -1,12 +1,24 @@
> -DIST dotnet-sdk-6.0.404-linux-arm.tar.gz 181563995 BLAKE2B 
> ff359d26264f0298d6210a2b7ae8cd0f1b577bf9937aaff09805f361e54349bdab5338182b674c81c8cb330c90f7a17a601ccce899e63f2e837a90bfd02c3726
>  SHA512 
> 1b9b5e0c45f90a4c752bf6990e5dda4110403a62392dc78abf9145c69b1d329b2630945a88cb4d7756322b188b7f4a9334bfc376067edff5dcfabfd85098d7d8
> -DIST dotnet-sdk-6.0.404-linux-arm64.tar.gz 180324700 BLAKE2B 
> 33780337294f427da0b8d44d8a3819c4276c0b01ffefe5a846cc5524039a5af203a231fe5893c63dce5b1557cd1288c4cb3e1d93505320a49eeccd4fd22cefe7
>  SHA512 
> 7c58595aa57b655ff5a268ae4fc680ff3fb15a84dcc0ce84ae7eb25ba27bf66f0c5273c985f15034583f5b05437a5354db68c4064953030dc4caebb11339ac76
> -DIST dotnet-sdk-6.0.404-linux-musl-arm.tar.gz 182613890 BLAKE2B 
> f0475535f703a80c23a881ef578eeac87923586b27bcc7ed018b75aa88dccc84dcbd9e20543b1e502e0e800b947afd8e6bbc3a44b4101ad786674d0ad2fb196a
>  SHA512 
> d7818ea567db81832cfeed5057c42255d2f19750a741a2cbc57e2d7134267a27e9937f86846b30f393c6f0ad2dbf0f4c73a902ed78b0de56138f077f62f34686
> -DIST dotnet-sdk-6.0.404-linux-musl-arm64.tar.gz 180323728 BLAKE2B 
> ff32a89653f265df2fda39dc0bb2ff6853e6fced029fb1a16096436a7876ad061e55a1d45fd29f395e4d6585f67cde2e5d95b0c0c2bbaec2b073cfd2785c87e5
>  SHA512 
> 999220f7247881d44c7f5a429b25c04d31044a1b91af5ede3f899df142af2d9f056a4ac6058c9e56f14b014a479f3a7455bd499f42f8e0f9b4fcacfeabc023b5
> -DIST dotnet-sdk-6.0.404-linux-musl-x64.tar.gz 185037621 BLAKE2B 
> 0ff97d56c4d061cb5f227c745afb34cf462c286f4c0347224885360cec861dfd59f90a6ef85571c49aa79b12d558111b07a29ac48451739f721e5b13d45f94c1
>  SHA512 
> 5313d8cbb41e27f462a141914f852e3d3e729886ce063be82778e1444df2d44dadcd2829f60ae97ae300d19798fab9d3b3932a7d9b9d00e948a80ccebbf5e106
> -DIST dotnet-sdk-6.0.404-linux-x64.tar.gz 185546757 BLAKE2B 
> ce8447f82b93880c6491e06fd35d556b880f59403fd7c6161d228271de6bffc6c74810e5ec5d834e35a715b9bc6173cb028aeb443bd28717a2d8838b543eec9f
>  SHA512 
> 7a0f4b308d3fe98df9b426b0f8f8fb7bd7247244af3570e867a3969349c62c7ea4c6da81a1a2280788e300784167a2933db523f461985aef0681e0cf14bf8f0d
> -DIST dotnet-sdk-7.0.200-linux-arm.tar.gz 192996891 BLAKE2B 
> 43c271a53d2eeebfbbeb7702e0c7a203960b57246f4b1f557d78391abdf10d0cca87c7ee364a37151f8e9e91df53e427df077a7cc25e1ccce5ac5d37fc73bc3a
>  SHA512 
> 7b1072c8080a0f38946d207945417dbeea4cbb688c2ea2dba1cb31330da15652da0823d8571c063a08830fe2157dbacb635eb2a8c7f20033cd1b8a35a9cfde36
> -DIST dotnet-sdk-7.0.200-linux-arm64.tar.gz 193106712 BLAKE2B 
> 5db6eab8bf56a85a15e6107bd4bca0dd4669d9eb2b3db287b8aa7621e38e07ce213c8e2446add010623b78b7092c0658d17bf4c90a059440778519e5aa117a9e
>  SHA512 
> 2990b7d2b23adb2b2621786ba774450e8cf73bf872173ab57026d7658599accdb5a4cefb5292945e264408f833503210621ed787c8d77eb467d3b204da8073a8
> -DIST dotnet-sdk-7.0.200-linux-musl-arm.tar.gz 192955116 BLAKE2B 
> 5b5549e158ebc7059b123d601566efddaacd04aa6ee531699b3c70327b2f2005ed11cbb7dea7b9a8a9c5f792fcc7461ea34b0a33a81828b4085327f219224d19
>  SHA512 
> 1e4f9160cb93ca9704015e787491bf78c5850c2a0aa7f5794b35f607f6f342903c9d8aa182593133d6609d5b9aded9bed769855213e0464311f357a65df0a640
> -DIST dotnet-sdk-7.0.200-linux-musl-arm64.tar.gz 192893152 BLAKE2B 
> ea793eebc9d414f5f8dd0c4a1b2c0330bf762db8fb1626aaa97d84b8fffe2a6b8d85f8cf735467dd49d6f588cd17254dad7ced926410f7e26488da08e0bb593a
>  SHA512 
> 63c568b1e0014e2039def200fde47d932e5366ba794fcd89f0efbcfd845e8b8b1c0ede6406a518f366356f5b566df2d0a1b53e6fdc9b58a26a59bdaa89e0ce32
> -DIST dotnet-sdk-7.0.200-linux-musl-x64.tar.gz 197209986 BLAKE2B 
> 4219149ed4f682ecb3d2c00cb2ed24f5352153ca0a5063bf07e7d42ddce95a5d3b4924e257bc166e1a1ca779dd9fb1d8e52d7a17a37ae73a596f3b5f4ed98c5b
>  SHA512 
> e907c96e7f1c7a3497f8726176b1fad9e93050b7b5f30900a634d253c4c5c822c8d729b22b36fa00d5bb2be0834f6c683d47db8c22077fbb191e38ae67e12119
> -DIST dotnet-sdk-7.0.200-linux-x64.tar.gz 197802070 BLAKE2B 
> 100af2f1e3fda195542f383a

[gentoo-dev] [PATCH 7/7] dev-dotnet/dotnet-sdk-bin: drop old

2023-07-16 Thread Maciej Barć
Bug: https://bugs.gentoo.org/900597
Bug: https://github.com/gentoo/gentoo/pull/29309
Signed-off-by: Maciej Barć 
---
 dev-dotnet/dotnet-sdk-bin/Manifest|  8 +--
 .../dotnet-sdk-bin-6.0.402-r3.ebuild  | 65 --
 .../dotnet-sdk-bin-6.0.404.ebuild | 67 ---
 .../dotnet-sdk-bin-7.0.200.ebuild | 67 ---
 4 files changed, 1 insertion(+), 206 deletions(-)
 delete mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
 delete mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.404.ebuild
 delete mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.200.ebuild

diff --git a/dev-dotnet/dotnet-sdk-bin/Manifest 
b/dev-dotnet/dotnet-sdk-bin/Manifest
index 34d9d16893..8469c78ba4 100644
--- a/dev-dotnet/dotnet-sdk-bin/Manifest
+++ b/dev-dotnet/dotnet-sdk-bin/Manifest
@@ -1,15 +1,9 @@
-DIST dotnet-sdk-6.0.402-linux-arm.tar.gz 181622588 BLAKE2B 
1010a7cd9f598e0487af127f9e1dac86681479cd6d95e39eb5f1fbf555fd3923be7e2a56bf0bc878259c17e7eb66b711da9587fcfc8ac3ab5f5b17abff1c6da7
-DIST dotnet-sdk-6.0.402-linux-arm64.tar.gz 179368834 BLAKE2B 
102b1f2ce6d3162ad423b1e24c7f4730b2846aee5d6eb19a2fbbc52271f18cda1d98121c39fd9e2dd375c2837ab5a6714f8acc81245ab720f13c5b4c6e4e9dc3
-DIST dotnet-sdk-6.0.402-linux-musl-arm.tar.gz 181678689 BLAKE2B 
66d059106c0daab97497585935f85febcc1099474dc8f72e25e7ec2ad91b0f118a4978a0875508d11f1d5b47b75ce29e0a6782fa84c4ab654f8f6a4c31b2
-DIST dotnet-sdk-6.0.402-linux-musl-arm64.tar.gz 179488323 BLAKE2B 
459bfc25c250e36ed351eb76037aac29f999ae111889662079d13555707e2006c719ec88516ffed013e6d88fc836d41148b81d194afaa3049ae2696b8c606d63
-DIST dotnet-sdk-6.0.402-linux-musl-x64.tar.gz 185028850 BLAKE2B 
92f24b251d8d36d7cf154c44ff5096b069cd4df1fd3a1a3aea9d4aedb8934ab81ae2c33ae891cd892d942ecceb0ed677ee4c8eb242ad43a7c7f9a4ac2303a79a
-DIST dotnet-sdk-6.0.402-linux-x64.tar.gz 185619780 BLAKE2B 
1880ec1f94bd8c79db550fae5c0bd684e7e96e5ee99d5bf41c20a0d9678facb6aaca0065d246015feaa265b0e99d95afaff4f1468fabd04594a9834224afc118
 DIST dotnet-sdk-6.0.404-linux-arm.tar.gz 181563995 BLAKE2B 
ff359d26264f0298d6210a2b7ae8cd0f1b577bf9937aaff09805f361e54349bdab5338182b674c81c8cb330c90f7a17a601ccce899e63f2e837a90bfd02c3726
 DIST dotnet-sdk-6.0.404-linux-arm64.tar.gz 180324700 BLAKE2B 
33780337294f427da0b8d44d8a3819c4276c0b01ffefe5a846cc5524039a5af203a231fe5893c63dce5b1557cd1288c4cb3e1d93505320a49eeccd4fd22cefe7
 DIST dotnet-sdk-6.0.404-linux-musl-arm.tar.gz 182613890 BLAKE2B 
f0475535f703a80c23a881ef578eeac87923586b27bcc7ed018b75aa88dccc84dcbd9e20543b1e502e0e800b947afd8e6bbc3a44b4101ad786674d0ad2fb196a
 DIST dotnet-sdk-6.0.404-linux-musl-arm64.tar.gz 180323728 BLAKE2B 
ff32a89653f265df2fda39dc0bb2ff6853e6fced029fb1a16096436a7876ad061e55a1d45fd29f395e4d6585f67cde2e5d95b0c0c2bbaec2b073cfd2785c87e5
 DIST dotnet-sdk-6.0.404-linux-musl-x64.tar.gz 185037621 BLAKE2B 
0ff97d56c4d061cb5f227c745afb34cf462c286f4c0347224885360cec861dfd59f90a6ef85571c49aa79b12d558111b07a29ac48451739f721e5b13d45f94c1
-DIST dotnet-sdk-6.0.404-linux-x64.tar.gz 185546757 BLAKE2B 
ce8447f82b93880c6491e06fd35d556b880f59403fd7c6161d228271de6bffc6c74810e5ec5d834e35a715b9bc6173cb028aeb443bd28717a2d8838b543eec9f
+DIST dotnet-sdk-6.0.404-linux-x64.tar.gz 185546757 BLAKE2B 
ce8447f82b93880c6491e06fd35d556b880f59403fd7c6161d228271de6bffc6c74810e5ec5d834e35a715b9bc6173cb028aeb443bd28717a2d8838b543eec9f
 SHA512 
7a0f4b308d3fe98df9b426b0f8f8fb7bd7247244af3570e867a3969349c62c7ea4c6da81a1a2280788e300784167a2933db523f461985aef0681e0cf14bf8f0d
 DIST dotnet-sdk-7.0.200-linux-arm.tar.gz 192996891 BLAKE2B 
43c271a53d2eeebfbbeb7702e0c7a203960b57246f4b1f557d78391abdf10d0cca87c7ee364a37151f8e9e91df53e427df077a7cc25e1ccce5ac5d37fc73bc3a
 DIST dotnet-sdk-7.0.200-linux-arm64.tar.gz 193106712 BLAKE2B 
5db6eab8bf56a85a15e6107bd4bca0dd4669d9eb2b3db287b8aa7621e38e07ce213c8e2446add010623b78b7092c0658d17bf4c90a059440778519e5aa117a9e
 DIST dotnet-sdk-7.0.200-linux-musl-arm.tar.gz 192955116 BLAKE2B 
5b5549e158ebc7059b123d601566efddaacd04aa6ee531699b3c70327b2f2005ed11cbb7dea7b9a8a9c5f792fcc7461ea34b0a33a81828b4085327f219224d19
diff --git a/dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild 
b/dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
deleted file mode 100644
index f2f49466ae..00
--- a/dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
+++ /dev/null
@@ -1,65 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI=8
-
-DESCRIPTION=".NET is a free, cross-platform, open-source developer platform"
-HOMEPAGE="https://dotnet.microsoft.com/";
-SRC_URI="
-amd64? (
-   elibc_glibc? ( 
https://dotnetcli.azureedge.net/dotnet/Sdk/${PV}/dotnet-sdk-${PV}-linux-x64.tar.gz
 )
-   elibc_musl? ( 
https://dotnetcli.azureedge.net/dotnet/Sdk/${PV}/dotnet-sdk-${PV}-linux-musl-x64.tar.gz
 )
-)
-arm? (
-   elibc_glibc? ( 
https://dotnetcli.azureedge.net/dotnet/Sdk/${PV}/dotnet-sdk-${PV}-linux-arm.tar.g

[gentoo-dev] [PATCH 6/7] dev-dotnet/dotnet-sdk-bin: update packaging mechanism

2023-07-16 Thread Maciej Barć
Bug: https://bugs.gentoo.org/900597
Bug: https://github.com/gentoo/gentoo/pull/29309
Signed-off-by: Maciej Barć 
---
 dev-dotnet/dotnet-sdk-bin/Manifest| 36 ++
 .../dotnet-sdk-bin-6.0.402-r3.ebuild  | 65 ++
 .../dotnet-sdk-bin-6.0.404-r1.ebuild  | 65 ++
 .../dotnet-sdk-bin-7.0.200-r1.ebuild  | 66 +++
 .../dotnet-sdk-bin-7.0.203.ebuild | 66 +++
 dev-dotnet/dotnet-sdk-bin/metadata.xml|  6 +-
 6 files changed, 287 insertions(+), 17 deletions(-)
 create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.402-r3.ebuild
 create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-6.0.404-r1.ebuild
 create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.200-r1.ebuild
 create mode 100644 dev-dotnet/dotnet-sdk-bin/dotnet-sdk-bin-7.0.203.ebuild

diff --git a/dev-dotnet/dotnet-sdk-bin/Manifest 
b/dev-dotnet/dotnet-sdk-bin/Manifest
index 0db1365533..34d9d16893 100644
--- a/dev-dotnet/dotnet-sdk-bin/Manifest
+++ b/dev-dotnet/dotnet-sdk-bin/Manifest
@@ -1,12 +1,24 @@
-DIST dotnet-sdk-6.0.404-linux-arm.tar.gz 181563995 BLAKE2B 
ff359d26264f0298d6210a2b7ae8cd0f1b577bf9937aaff09805f361e54349bdab5338182b674c81c8cb330c90f7a17a601ccce899e63f2e837a90bfd02c3726
 SHA512 
1b9b5e0c45f90a4c752bf6990e5dda4110403a62392dc78abf9145c69b1d329b2630945a88cb4d7756322b188b7f4a9334bfc376067edff5dcfabfd85098d7d8
-DIST dotnet-sdk-6.0.404-linux-arm64.tar.gz 180324700 BLAKE2B 
33780337294f427da0b8d44d8a3819c4276c0b01ffefe5a846cc5524039a5af203a231fe5893c63dce5b1557cd1288c4cb3e1d93505320a49eeccd4fd22cefe7
 SHA512 
7c58595aa57b655ff5a268ae4fc680ff3fb15a84dcc0ce84ae7eb25ba27bf66f0c5273c985f15034583f5b05437a5354db68c4064953030dc4caebb11339ac76
-DIST dotnet-sdk-6.0.404-linux-musl-arm.tar.gz 182613890 BLAKE2B 
f0475535f703a80c23a881ef578eeac87923586b27bcc7ed018b75aa88dccc84dcbd9e20543b1e502e0e800b947afd8e6bbc3a44b4101ad786674d0ad2fb196a
 SHA512 
d7818ea567db81832cfeed5057c42255d2f19750a741a2cbc57e2d7134267a27e9937f86846b30f393c6f0ad2dbf0f4c73a902ed78b0de56138f077f62f34686
-DIST dotnet-sdk-6.0.404-linux-musl-arm64.tar.gz 180323728 BLAKE2B 
ff32a89653f265df2fda39dc0bb2ff6853e6fced029fb1a16096436a7876ad061e55a1d45fd29f395e4d6585f67cde2e5d95b0c0c2bbaec2b073cfd2785c87e5
 SHA512 
999220f7247881d44c7f5a429b25c04d31044a1b91af5ede3f899df142af2d9f056a4ac6058c9e56f14b014a479f3a7455bd499f42f8e0f9b4fcacfeabc023b5
-DIST dotnet-sdk-6.0.404-linux-musl-x64.tar.gz 185037621 BLAKE2B 
0ff97d56c4d061cb5f227c745afb34cf462c286f4c0347224885360cec861dfd59f90a6ef85571c49aa79b12d558111b07a29ac48451739f721e5b13d45f94c1
 SHA512 
5313d8cbb41e27f462a141914f852e3d3e729886ce063be82778e1444df2d44dadcd2829f60ae97ae300d19798fab9d3b3932a7d9b9d00e948a80ccebbf5e106
-DIST dotnet-sdk-6.0.404-linux-x64.tar.gz 185546757 BLAKE2B 
ce8447f82b93880c6491e06fd35d556b880f59403fd7c6161d228271de6bffc6c74810e5ec5d834e35a715b9bc6173cb028aeb443bd28717a2d8838b543eec9f
 SHA512 
7a0f4b308d3fe98df9b426b0f8f8fb7bd7247244af3570e867a3969349c62c7ea4c6da81a1a2280788e300784167a2933db523f461985aef0681e0cf14bf8f0d
-DIST dotnet-sdk-7.0.200-linux-arm.tar.gz 192996891 BLAKE2B 
43c271a53d2eeebfbbeb7702e0c7a203960b57246f4b1f557d78391abdf10d0cca87c7ee364a37151f8e9e91df53e427df077a7cc25e1ccce5ac5d37fc73bc3a
 SHA512 
7b1072c8080a0f38946d207945417dbeea4cbb688c2ea2dba1cb31330da15652da0823d8571c063a08830fe2157dbacb635eb2a8c7f20033cd1b8a35a9cfde36
-DIST dotnet-sdk-7.0.200-linux-arm64.tar.gz 193106712 BLAKE2B 
5db6eab8bf56a85a15e6107bd4bca0dd4669d9eb2b3db287b8aa7621e38e07ce213c8e2446add010623b78b7092c0658d17bf4c90a059440778519e5aa117a9e
 SHA512 
2990b7d2b23adb2b2621786ba774450e8cf73bf872173ab57026d7658599accdb5a4cefb5292945e264408f833503210621ed787c8d77eb467d3b204da8073a8
-DIST dotnet-sdk-7.0.200-linux-musl-arm.tar.gz 192955116 BLAKE2B 
5b5549e158ebc7059b123d601566efddaacd04aa6ee531699b3c70327b2f2005ed11cbb7dea7b9a8a9c5f792fcc7461ea34b0a33a81828b4085327f219224d19
 SHA512 
1e4f9160cb93ca9704015e787491bf78c5850c2a0aa7f5794b35f607f6f342903c9d8aa182593133d6609d5b9aded9bed769855213e0464311f357a65df0a640
-DIST dotnet-sdk-7.0.200-linux-musl-arm64.tar.gz 192893152 BLAKE2B 
ea793eebc9d414f5f8dd0c4a1b2c0330bf762db8fb1626aaa97d84b8fffe2a6b8d85f8cf735467dd49d6f588cd17254dad7ced926410f7e26488da08e0bb593a
 SHA512 
63c568b1e0014e2039def200fde47d932e5366ba794fcd89f0efbcfd845e8b8b1c0ede6406a518f366356f5b566df2d0a1b53e6fdc9b58a26a59bdaa89e0ce32
-DIST dotnet-sdk-7.0.200-linux-musl-x64.tar.gz 197209986 BLAKE2B 
4219149ed4f682ecb3d2c00cb2ed24f5352153ca0a5063bf07e7d42ddce95a5d3b4924e257bc166e1a1ca779dd9fb1d8e52d7a17a37ae73a596f3b5f4ed98c5b
 SHA512 
e907c96e7f1c7a3497f8726176b1fad9e93050b7b5f30900a634d253c4c5c822c8d729b22b36fa00d5bb2be0834f6c683d47db8c22077fbb191e38ae67e12119
-DIST dotnet-sdk-7.0.200-linux-x64.tar.gz 197802070 BLAKE2B 
100af2f1e3fda195542f383a449473b1e52a7c5c1ff40b3ee666305a883885e1440996be7e588d8ccad44702917cf8d5e87900a59d80b8a43f9ba76a8e602927
 SHA512 
bb88cc5099bcb090608f5e02e7fcdc4f6a8211488137

[gentoo-dev] [PATCH 5/7] app-eselect/eselect-dotnet: new package

2023-07-16 Thread Maciej Barć
Bug: https://bugs.gentoo.org/900597
Bug: https://github.com/gentoo/gentoo/pull/29309
Signed-off-by: Maciej Barć 
---
 app-eselect/eselect-dotnet/Manifest   |  1 +
 .../eselect-dotnet-0.1.0.ebuild   | 25 +++
 app-eselect/eselect-dotnet/metadata.xml   |  9 +++
 3 files changed, 35 insertions(+)
 create mode 100644 app-eselect/eselect-dotnet/Manifest
 create mode 100644 app-eselect/eselect-dotnet/eselect-dotnet-0.1.0.ebuild
 create mode 100644 app-eselect/eselect-dotnet/metadata.xml

diff --git a/app-eselect/eselect-dotnet/Manifest 
b/app-eselect/eselect-dotnet/Manifest
new file mode 100644
index 00..9cf36cadf1
--- /dev/null
+++ b/app-eselect/eselect-dotnet/Manifest
@@ -0,0 +1 @@
+DIST eselect-dotnet-0.1.0.tar.bz2 7788 BLAKE2B 
141e5a2fc765454682de60a6a337d6634766b4dd76f218606e2f4eb18960fdcf8940b954deda2fb6b0903f72b161513936c1d767210883316c32200704188945
 SHA512 
879281019d1e4a8a5ee3d3e6b6de3446ba573d253a5b3b0c59aa9faffcd6eb4382066e1752e18cb4e48c3e14340a278b2189c2674b1baa258ceb3980d13a
diff --git a/app-eselect/eselect-dotnet/eselect-dotnet-0.1.0.ebuild 
b/app-eselect/eselect-dotnet/eselect-dotnet-0.1.0.ebuild
new file mode 100644
index 00..3923b1a5a3
--- /dev/null
+++ b/app-eselect/eselect-dotnet/eselect-dotnet-0.1.0.ebuild
@@ -0,0 +1,25 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DESCRIPTION="Eselect module for management of multiple dotnet versions"
+HOMEPAGE="https://gitlab.gentoo.org/dotnet/eselect-dotnet/";
+
+if [[ ${PV} == ** ]] ; then
+   inherit git-r3
+   EGIT_REPO_URI="https://gitlab.gentoo.org/dotnet/${PN}.git";
+else
+   
SRC_URI="https://gitlab.gentoo.org/dotnet/${PN}/-/archive/${PV}/${P}.tar.bz2";
+   KEYWORDS="~amd64 ~arm ~arm64"
+fi
+
+LICENSE="GPL-2+"
+SLOT="0"
+
+RDEPEND="app-admin/eselect"
+
+src_install() {
+   insinto /usr/share/eselect/modules
+   doins dotnet.eselect
+}
diff --git a/app-eselect/eselect-dotnet/metadata.xml 
b/app-eselect/eselect-dotnet/metadata.xml
new file mode 100644
index 00..08bae967b8
--- /dev/null
+++ b/app-eselect/eselect-dotnet/metadata.xml
@@ -0,0 +1,9 @@
+
+https://www.gentoo.org/dtd/metadata.dtd";>
+
+
+  
+dot...@gentoo.org
+Gentoo Dotnet Project
+  
+
-- 
2.41.0




[gentoo-dev] [PATCH 4/7] dev-dotnet/dotnet-runtime-nugets: new package

2023-07-16 Thread Maciej Barć
Bug: https://bugs.gentoo.org/900597
Bug: https://github.com/gentoo/gentoo/pull/29309
Signed-off-by: Maciej Barć 
---
 dev-dotnet/dotnet-runtime-nugets/Manifest | 117 ++
 .../dotnet-runtime-nugets-3.1.32.ebuild   |  45 +++
 .../dotnet-runtime-nugets-6.0.12.ebuild   |  48 +++
 .../dotnet-runtime-nugets-6.0.14.ebuild   |  48 +++
 .../dotnet-runtime-nugets-6.0.16.ebuild   |  48 +++
 .../dotnet-runtime-nugets-7.0.3.ebuild|  48 +++
 .../dotnet-runtime-nugets-7.0.5.ebuild|  48 +++
 dev-dotnet/dotnet-runtime-nugets/metadata.xml |   9 ++
 8 files changed, 411 insertions(+)
 create mode 100644 dev-dotnet/dotnet-runtime-nugets/Manifest
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-3.1.32.ebuild
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-6.0.12.ebuild
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-6.0.14.ebuild
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-6.0.16.ebuild
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-7.0.3.ebuild
 create mode 100644 
dev-dotnet/dotnet-runtime-nugets/dotnet-runtime-nugets-7.0.5.ebuild
 create mode 100644 dev-dotnet/dotnet-runtime-nugets/metadata.xml

diff --git a/dev-dotnet/dotnet-runtime-nugets/Manifest 
b/dev-dotnet/dotnet-runtime-nugets/Manifest
new file mode 100644
index 00..8b2278ec5b
--- /dev/null
+++ b/dev-dotnet/dotnet-runtime-nugets/Manifest
@@ -0,0 +1,117 @@
+DIST microsoft.aspnetcore.app.ref.3.1.10.nupkg 2535203 BLAKE2B 
de332022234864a337f7430966fa98dad3cde28f3a5bc049365636855b51054e4a3d452474a61c4df647c9f6eb33db80c155d442c5df41770d93e25b2dabe852
+DIST microsoft.aspnetcore.app.ref.6.0.12.nupkg 3341830 BLAKE2B 
460b1f8a5bb4a49b494f8582c8f06792b48d1e5f24d990456c4510189881cb995d9cf0de0f4a464105a3dce0a59e9efd7c6a73aaad95d83518cbd595df8b7014
+DIST microsoft.aspnetcore.app.ref.6.0.14.nupkg 3340852 BLAKE2B 
8481d2ec13e937c24335fbb7480941fd2679d3dfa2f5f2245bce48c9be04050c5dde9f2ec9e54625f1306d68223a5b953ae6d779335990cba244217ec0a44659
+DIST microsoft.aspnetcore.app.ref.6.0.16.nupkg 3341587 BLAKE2B 
4a3588d50412a0659b9776482e494055a5b476dfd8748c8455777e068e6f86a58349c069f8f3288c088dd52b7d1f219fce520f40d5ee952eb3249bef3be89c46
 SHA512 
7b994bf1cf10a2b9c24f333046adbd78a14a5a969d1c235cb23ac93af51d1fe6a01304b61983b00bea9eb4c772bf6c9439f95d40d1db0f09c10d141bbe068cf2
+DIST microsoft.aspnetcore.app.ref.7.0.3.nupkg 3557271 BLAKE2B 
aec4693047178e484c75775975e5eb7501a8f72c6adbab90206c7fb357f5e28fe1ed1955db323180e8067302851c21b722b05d4edc1a81a14ed8124f5b712d1b
+DIST microsoft.aspnetcore.app.ref.7.0.5.nupkg 306 BLAKE2B 
6cc7ea23b65e6416f8394af50fca31803c760a4ecef080c64fc2fb0d938161a45707497d66147b2ce4398ca3b0e1796d33e84b852d4e5c1b8db3218b04932218
 SHA512 
1f7952a5ea05cd8c68b215a8025c11ee97639e4f523943b7d32256390184ab9cac81598965da76ec5a3fc1af1c3077b440b7f198bf483badb409312d00cd0e80
+DIST microsoft.aspnetcore.app.runtime.linux-arm.3.1.32.nupkg 9422779 BLAKE2B 
1fc5426e790842ad03ee9dadd62447c59cbb6cc462acfda2d3688e75c68581f478a69a2f5b3b2648b17e8a637f89f7fc45b0ef09423d8a3ae8bc8dfa4870b5ce
+DIST microsoft.aspnetcore.app.runtime.linux-arm.6.0.12.nupkg 10095058 BLAKE2B 
abd9ac8ed867b2e2e827e8c80dd0d8303262daf9076e80892caac268cc54656982a0b3ad67877e8a7c845ec3f6638f3122a25340609d5a34580de03be23c0f9c
+DIST microsoft.aspnetcore.app.runtime.linux-arm.6.0.14.nupkg 10095297 BLAKE2B 
4af3698eeda253c2eb5e90aae464ef496c8ccffcae201b2f8dc3e9695cb4ee2cd00a270f6e48871c8378ebb4182b7ca25eda957df036611194e572453b898690
+DIST microsoft.aspnetcore.app.runtime.linux-arm.6.0.16.nupkg 10095817 BLAKE2B 
939b1f0008af535aede118ee5e4559e3fcafdc39c392f41f80ed0200420495137d3d6049fd305c1baed4c605c1ead4a7adb9a629f4c242b8dd3363517c9bb23b
 SHA512 
40dfef2423b5a8cd8ec6ba97bc2e6e6e121664809499540f9f77b4766f49655990056b546d8ff1027dcec84007a4c8144cf7a50de0722be65d61aeec09fe1bb5
+DIST microsoft.aspnetcore.app.runtime.linux-arm.7.0.3.nupkg 10803489 BLAKE2B 
2f5c1cccd718ad00d851ae7482402fd059145ac963ba611a884e757219bade0184c37db6badf5d3aa9a76df75b9d194568203d9105e673e08a0db22d9d2f62b7
 SHA512 
af20c42549dcf7f25a2046aa6ef071d0231c554e0b5c5a357207fc708384d46a1d57e6f2e054a4eddeb2f04fe64d7ef3c9974fc50878d6e3ae018b0f735cd141
+DIST microsoft.aspnetcore.app.runtime.linux-arm.7.0.5.nupkg 10806144 BLAKE2B 
c2305cde423b51359ca4ecaec6925ff4afd378b992d775ee89598543da4ae530d5ce533e22cddebded18509653e886b97d33269e8d2bb79ad81ba2e79f895212
 SHA512 
2ba63d7eea0758fc109f947e687e6265089c4c7a6f3dc44cee269139cd5171e027125afacf5bc9d21c63292b9419d776b513149547efeb6acbb6c31f37ededc3
+DIST microsoft.aspnetcore.app.runtime.linux-arm64.3.1.32.nupkg 8938556 BLAKE2B 
16dca004bfe9741ab542e3ac1155a587750ebf6d128ac981e60f190ce2375891dd50fb5c186f50aadd9b67690477e5de41215661fc2d8b215f1bb4664de11770
+DIST microsoft.aspnetcore.app.runtime.linux-arm64.6.0.12.nupkg 9864158 BLAKE2B 
1000452879b7efdd7d47927f61122c42873a3c320652a592e754b8cfdbd13