On Fri, Aug 26, 2022 at 11:30:09PM -0700, Steve M wrote:

My apologies for making another "my package won't show up" thread, but that is
my problem and I can't figure it out. My package "swiftlang" takes about 3 hours
to build and uses about 23GiB of disk space, so that may play a role.

Mentors doesn't build binary packages, no.

My first upload on Tuesday afternoon resulted in a REJECT e-mail due to an error
in the d/copyright file.

Oh, does mentors do REJECTs now?

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors.

Note that there is already a package called "swift" in the archive.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmMJvc0tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh sF8QAI0MRw66JjCvvzCIc+7eFyx81NK52d4BKi+ZJ0tkj2cQsTcxPclALnhFEbec lAki29vHzSGz+qaOu61pvVBlp7MTBya4tROqN7skJITLNeoV42ll3WxLVrbyI8MS kLUE/dzDo1s8L6skNnKHE+zMtbPAFtLc7bu4ihUGH73elu1WD9wJmqdjYA+UXAjF HO4CXQp6CyRdrAJLfkjQTjtxHxl1r7w5eGXlB96hxFhcWJL/1hVhuK3iZvhVtZIR ddd8C1vn9IPNhRAQHcwQPPptP9tG71lUeVLE/tXv5EQis3rcuuPI6SfggmWUDTYV SPigh4A/qgxTyTRv1iR1MfngOkdtlra9eM0wCN82c3bE1wUmwfdB/dNhgyCvFv37 yzG54EdiBX6Kyh5Y2P6WdWh1QuSYfYPGhwmHy+RL1JhH3KI6+0tTRbi0mgnsn7Zx GmjvVcepAhVIF6WjJGBBTXJml79v020Qnwq1HwRoZnM3XqbXY0lEAV/aCPtK/aaU wat/USk00BXmevny98wc/yLkpL37l26VzYXZIKZkvsDq6sbUf4F3RJ1L56oiDOtg OZgV0kLAgLqQfwBjYIqQfrwwK7GUCMFW63ZQSsc/qqHhRao54nMfEJVBtTKIt0yt JQKtUtjnjPQwWsWTkk7yhU0Dr8pj8nFa7v0sMCENt7ZvlTyn
=Mf7L
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Mentors,

My apologies for making another "my package won't show up" thread, but that is my problem and I can't figure it out. My package "swiftlang" takes about 3 hours
to build and uses about 23GiB of disk space, so that may play a role.

My first upload on Tuesday afternoon resulted in a REJECT e-mail due to an error
in the d/copyright file. I fixed that and uploaded again on Tuesday evening. We are now about 72 hours later and no acknowledgment has been received. I tried again 14 hours ago and it has been the same, no REJECT or ACCEPT e-mail and it doesn't show up in the list of mentor packages. Yesterday I had two ACCEPTed uploads for a different package so I am fairly certain I've got everything set up correctly on my end. Can someone try to find out why it is not completing?

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors. Successfully uploaded swift_5.6.2.orig.tar.gz to mentors.debian.net for mentors.
Successfully uploaded swift_5.6.2-1.debian.tar.xz to mentors.debian.net for mentors.
Successfully uploaded swift_5.6.2-1_amd64.buildinfo to mentors.debian.net for mentors.
Successfully uploaded swiftlang-dbgsym_5.6.2-1_amd64.deb to mentors.debian.net for mentors.
Successfully uploaded swiftlang_5.6.2-1_amd64.deb to mentors.debian.net for mentors.
Successfully uploaded swift_5.6.2-1_amd64.changes to mentors.debian.net for mentors.


Thanks
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Aug 27, 2022 at 12:23:51AM -0700, Steve M wrote:

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors.

Note that there is already a package called "swift" in the archive.

This made me go look at the REJECTED e-mail again and I noticed it says "Unfortunately your package "swift" was rejected". That's not right. My package
is "swiftlang"

No, your source package is named "swift".

something correctly there. I am aware of the existing package "swift" and my package is marked as being a conflict with it due to both packages having binaries named "swift".

This is wrong as well, see https://www.debian.org/doc/debian-policy/ch-files.html#binaries

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmMJx6UtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh ULwP/3CjYLY0KxPiX/l4yLpbZrfPtoH6KN6gqT8++WhF5TstOlujPhk8N68q1D6e Rg8AMB3EyKflRd5zCxWHzn/XC7s7r2KJsnwRPN+nswINps6eLaH4VTi2TOIBfdBE p96LHde9IqpXRzsSIwUYjT241mDx0DkyEWCIEZvLArlmQ392uPTVVEN0Gm9aJAgo QJFLUyKiZvxqVJEJyyxDmHQXC6ai5OIHXBIt8F497aVQ5K+C8+HymvNXhb6hyqP7 0ZRY1ohpf+xMgLTCxlkbfCsQHoQPkafQlL24QreoYOghBecztz2s6vnaN8OwDAh4 vmTuwr4pYn3kO/R3sC9PHtaTcwfE52Kn1uudr4fCjFrF2Jb1xR0hufiMYQblo//0 EkzhMlvtmjh7kIjICV4rn7N4zQgqx9feTM9RFYViCZZ00BBOf/UuA9jK5aVxirpr UJMF+Qw3cJzQGZRSmbS01esbqD3rzkU7i3fFhgWJTae4LA2hJnSoJ/qGr2fkvxSF uA7OvbJWZz4SO2YZCFNjQtL2Bo9ITBwYAAndZQI767D/kq0Nv2J/HN0zANo7nqXp 581TUwkz3w8uoe2SZNi4hRKaWJwkrmzPWrtv035Lp3U2A2DD8G2DT4iwtNjD+8b2 e6QK9TySCssbiya9pb02ExSyPAvW44M0hBofpiFRFaUzfR1m
=pp/D
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 2022-08-27 at 12:28 +0500, Andrey Rahmatullin wrote:

On Sat, Aug 27, 2022 at 12:23:51AM -0700, Steve M wrote:

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors.

Note that there is already a package called "swift" in the archive.

This made me go look at the REJECTED e-mail again and I noticed it says "Unfortunately your package "swift" was rejected". That's not right. My package
is "swiftlang"

No, your source package is named "swift".

So then maybe I did it all correctly to have my package named "swiftlang" and my
upstream named "swift"? It took me a while to get the build tools to be happy so
I thought I must have.

something correctly there. I am aware of the existing package "swift" and my
package is marked as being a conflict with it due to both packages having binaries named "swift".

This is wrong as well, see https://www.debian.org/doc/debian-policy/ch-files.html#binaries

I had to read that policy a few times, but now I see that I am not allowed to use the "conflicts" mechanism is this situation. My "swift" binary is actually just a symbolic link to "swift-frontend", but it is the main mechanism by which the compiler and REPL is called. Also, "swiftc" is also a symbolic link to that
same "swift-frontend" so it might be possible to simply drop "swift" and depend on "swiftc" which would then only be an issue for people trying to follow documentation that tells then to run the "swift" command. Should I now reach out
to debian-devel to ask about it?

Also, what is the ITP bug number for this package?

The ITP bug # is 788327 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788327

Thanks
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

Am 27.08.22 um 18:34 schrieb Steve M:

Note that there is already a package called "swift" in the archive.

[..]

So then maybe I did it all correctly to have my package named "swiftlang" and my
upstream named "swift"? It took me a while to get the build tools to be happy so
I thought I must have.

The buildtools might be happy, but Debian's archive software won't. The
names of source (and binary packages) must be unique. And as there is
already a source package named "swift" you'll have to change the name of
yours.


Best regards,
Alexander

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Aug 27, 2022 at 09:34:57AM -0700, Steve M wrote:

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors.

Note that there is already a package called "swift" in the archive.

This made me go look at the REJECTED e-mail again and I noticed it says "Unfortunately your package "swift" was rejected". That's not right. My package
is "swiftlang"

No, your source package is named "swift".

So then maybe I did it all correctly to have my package named "swiftlang" and my
upstream named "swift"? It took me a while to get the build tools to be happy so
I thought I must have.

You didn't, as, like as I said and the quote line proves, your source
package name is "swift".

something correctly there. I am aware of the existing package "swift" and my
package is marked as being a conflict with it due to both packages having binaries named "swift".

This is wrong as well, see https://www.debian.org/doc/debian-policy/ch-files.html#binaries

I had to read that policy a few times, but now I see that I am not allowed to use the "conflicts" mechanism is this situation. My "swift" binary is actually
just a symbolic link to "swift-frontend", but it is the main mechanism by which
the compiler and REPL is called. Also, "swiftc" is also a symbolic link to that
same "swift-frontend" so it might be possible to simply drop "swift" and depend
on "swiftc" which would then only be an issue for people trying to follow documentation that tells then to run the "swift" command. Should I now reach out
to debian-devel to ask about it?

You can try that, yes, but generally it should be an upstream decision.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmMKhXgtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh KCsP/11hIiIjSyhtGjQ1yTG3i2wIfxMERdoCSeqL8y87hejuqkmWoub/E8bAqI+Z RO2HWQEDjw7K4q94+Clo2liUaEOrn+VXombFlT4x1cEecs/2pVSNc1W8ouS8vGkf m3rWFnkVfPEHkNjoP8qqmKKTgsfPGtV9/moDaO/1LBUfNSy6zgg1ze6/R+kogSxD mC7mxOUNim2IVLr/ymO6HobwOd2OG66sAvUsk6tHVhBS6GOzcKdIIjhDG1IkeLmY 94dwzihvuJZOf/h3q9mmLUrRc94X7zhUfcgkv36kZjm7L2iIq5yYj8u4utFyaR8w wERJ/nuZWhhPcz0H827qz/VjJQv4/cChquIkH1G8+YfAmz+MgD20RO8kZObgfKJF U8mRUL2ARDgXrmHofXOTi3x/FXR+txyUrfQgDim3nvTerZYPeRj3kvPuIPrLTaKu FfLs9v3QtAwNybZtb6IAqJcTF25tOvcgYiVjxmaRNubTskJ8Thsa9G9ZxigNxaU5 a0CNfx2XswxS/5d44lvJPcx2jID+x/Gr1pDKS/b/LMg1FqamOpNXBMjFeiSMj0XF /khoLuWizScB9DExCI1WYH8+bgStjlbTGFJJVFpA3DERhBfaOudNWp9Zbmdvv0IZ tvaFONoPDshzSl1vGgsmcp14ItnuP3Bjo0pR7qYdVO5wykVg
=BmmP
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 2022-08-28 at 01:58 +0500, Andrey Rahmatullin wrote:

On Sat, Aug 27, 2022 at 09:34:57AM -0700, Steve M wrote:

Successfully uploaded swift_5.6.2-1.dsc to mentors.debian.net for mentors.

Note that there is already a package called "swift" in the archive.

This made me go look at the REJECTED e-mail again and I noticed it says "Unfortunately your package "swift" was rejected". That's not right. My package
is "swiftlang"

No, your source package is named "swift".

So then maybe I did it all correctly to have my package named "swiftlang" and my
upstream named "swift"? It took me a while to get the build tools to be happy so
I thought I must have.

You didn't, as, like as I said and the quote line proves, your source
package name is "swift".

I renamed the upstream to "swiftlang" and uploaded to Mentors again, but still nothing 22 hours later. If anyone can help me figure out why that would be appreciated, if not then I'll just have to get along without it.

something correctly there. I am aware of the existing package "swift" and my
package is marked as being a conflict with it due to both packages having
binaries named "swift".

This is wrong as well, see https://www.debian.org/doc/debian-policy/ch-files.html#binaries

I had to read that policy a few times, but now I see that I am not allowed to
use the "conflicts" mechanism is this situation. My "swift" binary is actually
just a symbolic link to "swift-frontend", but it is the main mechanism by which
the compiler and REPL is called. Also, "swiftc" is also a symbolic link to that
same "swift-frontend" so it might be possible to simply drop "swift" and depend
on "swiftc" which would then only be an issue for people trying to follow documentation that tells then to run the "swift" command. Should I now reach
out
to debian-devel to ask about it?

You can try that, yes, but generally it should be an upstream decision.

I'm certain that upstream won't rename their "swift" binary/link, but I have asked about using "switfc" instead to see if there is any problem not having "swift" available. Sylvestre Ledru has kindly agreed to sponsor this package so I will work with him on how to best address this naming conflict issue and any other policy issues that I need to clean up.

Thank you for your help.
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

On Fri, Aug 26, 2022 at 11:30:09PM -0700, Steve M wrote:

My apologies for making another "my package won't show up" thread, but that is
my problem and I can't figure it out. My package "swiftlang" takes about 3 hours
to build and uses about 23GiB of disk space, so that may play a role.

My first upload on Tuesday afternoon resulted in a REJECT e-mail due to an error
in the d/copyright file. I fixed that and uploaded again on Tuesday evening. We
are now about 72 hours later and no acknowledgment has been received. I tried again 14 hours ago and it has been the same, no REJECT or ACCEPT e-mail and it
doesn't show up in the list of mentor packages.

mentors processes uploads every few minutes, so waiting more than 1
hour almost certanly means something went wrong.

Anyway, I don't want to compute what "afternoon" and "evening" is for
you, but this is from mentors' logs:

Aug 23 23:05:33 wv-debian-mentors1 celery[1121]: [2022-08-23 23:05:33,095: INFO/Beat] Scheduler: Sending due task importer (debexpo.importer.tasks.importer)
Aug 23 23:05:33 wv-debian-mentors1 celery[524]: [2022-08-23 23:05:33,098: INFO/MainProcess] Received task: debexpo.importer.tasks.importer[f0d330ec-73c2-423a-a537-d85eca4ef8bb]
Aug 23 23:05:35 wv-debian-mentors1 celery[1120]: [2022-08-23 23:05:35,989: INFO/ForkPoolWorker-3] POST https://bugs.debian.org/cgi-bin/soap.cgi
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to import swift: Source package is invalid
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to parse debian/copyright: Files paragraph missing License field
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: [2022-08-23 23:06:00,703: ERROR/ForkPoolWorker-3] Failed to import swift: Source package is invalid
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to parse debian/copyright: Files paragraph missing License field
Aug 23 23:06:04 wv-debian-mentors1 celery[1120]: [2022-08-23 23:06:04,021: INFO/ForkPoolWorker-3] Task debexpo.importer.tasks.importer[f0d330ec-73c2-423a-a537-d85eca4ef8bb] succeeded in 30.92165717900206>


This is likely the reject you had.


Then, I see another upload on Aug 24 04:30:25 of "swift" and another one
on Aug 26 15:30:16. This is followed by a "swiftlang" upload on Aug 28 00:31:15.

Quite interestingly, all these 3 uploads caused the service to be killed
by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmMMbHIACgkQCBa54Yx2 K63CDg/+Mb93p5eBudMfia0DtBlKab/7mL5Ac8ehi4m8lH4XB3iSoF7k72DBwDpx OTlin3L1W9wpi1rjPlLhZTnxHGDNcQqr82QmBRmuiW/CnH5PBVKaavlAe/j4NFme LMEeFcFs2Keox9q+hoRmXBaZ5UGLVppuNNTQ92CtkT4uIj5rOAK09yIpLZs1GcGD mJZZcpVJ/CcSFxgaEc8VSr8ZLrGT6fETiEbA/YVSzIKeExSrBMvBDHyWMkG+OIbi Gn5O+c1hoHjKsIPMIqLQORJZI9pnV0dKjXJ81XPfASSbH1TqpFttFT589Jcye3lC HC4BHz8mXfAsJT5rnNPdVAl6hK8YKaDHAyE3ybef9dt9beeoN8vVOYpXzef1VSkt ga0g1Itdptn1XLWRjG49PiE0b1RLd/EW6r9HmYRFQo1/Z4Xd7Jyi1BBncADymh3K hUbiRx9xhXqKKpYDu0TkrwAmkrv9k2Csvw0D1x0L4LqjCW+7mMUYMX4Jtj4N+dqu cc93//nPxip6E0mhbGc9q7AubJLZk3Hck8ZH7RdfwWK3oL/T7RC

On Mon, 2022-08-29 at 09:36 +0200, Mattia Rizzolo wrote:

Hi!

On Fri, Aug 26, 2022 at 11:30:09PM -0700, Steve M wrote:

My apologies for making another "my package won't show up" thread, but that is
my problem and I can't figure it out. My package "swiftlang" takes about 3 hours
to build and uses about 23GiB of disk space, so that may play a role.

My first upload on Tuesday afternoon resulted in a REJECT e-mail due to an error
in the d/copyright file. I fixed that and uploaded again on Tuesday evening.
We
are now about 72 hours later and no acknowledgment has been received. I tried
again 14 hours ago and it has been the same, no REJECT or ACCEPT e-mail and it
doesn't show up in the list of mentor packages.

mentors processes uploads every few minutes, so waiting more than 1
hour almost certanly means something went wrong.

Anyway, I don't want to compute what "afternoon" and "evening" is for
you, but this is from mentors' logs:

Aug 23 23:05:33 wv-debian-mentors1 celery[1121]: [2022-08-23 23:05:33,095: INFO/Beat] Scheduler: Sending due task importer (debexpo.importer.tasks.importer)
Aug 23 23:05:33 wv-debian-mentors1 celery[524]: [2022-08-23 23:05:33,098: INFO/MainProcess] Received task: debexpo.importer.tasks.importer[f0d330ec- 73c2-423a-a537-d85eca4ef8bb]
Aug 23 23:05:35 wv-debian-mentors1 celery[1120]: [2022-08-23 23:05:35,989: INFO/ForkPoolWorker-3] POST https://bugs.debian.org/cgi-bin/soap.cgi
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to import swift: Source package is invalid
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to parse debian/copyright: Files paragraph missing License field
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: [2022-08-23 23:06:00,703: ERROR/ForkPoolWorker-3] Failed to import swift: Source package is invalid
Aug 23 23:06:00 wv-debian-mentors1 celery[1120]: Failed to parse debian/copyright: Files paragraph missing License field
Aug 23 23:06:04 wv-debian-mentors1 celery[1120]: [2022-08-23 23:06:04,021: INFO/ForkPoolWorker-3] Task debexpo.importer.tasks.importer[f0d330ec-73c2- 423a-a537-d85eca4ef8bb] succeeded in 30.92165717900206>

This is likely the reject you had.

Then, I see another upload on Aug 24 04:30:25 of "swift" and another one
on Aug 26 15:30:16.  This is followed by a "swiftlang" upload on Aug 28 00:31:15.

Quite interestingly, all these 3 uploads caused the service to be killed
by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

Thank you for looking into this. Please let me know if there is anything you need me to do to help with the debug.

Regards
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Aug 29, 2022 at 08:31:44PM -0700, Steve M wrote:

Quite interestingly, all these 3 uploads caused the service to be killed
by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

Thank you for looking into this. Please let me know if there is anything you need me to do to help with the debug.

I could probably recommend you subscribe to that salsa issue above, so
that you are notify of updates, and subsequently try again once it's
fixed (which probably won't take too long, no promises however).

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmMOKW8ACgkQCBa54Yx2 K60ZiRAAteYWeW1LU7VwJyApEYt+fnebxOUc0yLU4+xMjCi9F2Nr7N4nVQ1vDZRm fHJCQG+W+gwlXbZYuvRBiJVrlwAsb1bC5PxAhlQ2FzkPXUc3Lr7K83b1cN1nlzfn tE3YfsUY5WcglulV6mUtBzQ5aDkxoDM4LTrVQ/4HDMCUx3U9KTRhBkUng0UbzUxf C0t/TFkxWiX8v5iuN6ORrHbjBLmM4WDfEU4QH/SyeGRXFaIuzFLqXCIG0qVSG0qJ ZJ6CIOqdAZVE0j4l0EkOuSAmPJ4CD9cTbXp2TDDx4sql8LL37qkhSfDJsGFo4FQx 42Amdd/HcE1fS9uxSTFx69OgqfnWrewgGADV94AeyrXpeo8GfjSPaU5ppJ3nFcD2 8n7AetV5xYBSlTBmN9CbsVl63LNp1IZ/ZD2S5ADajaOs595yp2P61XD55vdGYoX3 iUM81EwFCAgoTTqoPDMOq3USpTMrvgB0LDEmczs/PKfwDJ4cicmcEC9bkXAiDee8 tuvv9zbs6r0wEXbfyYpQrGRRLSuJ0Qk1JEf4AIzfLT/nZGPnZLa

Hi Steve,

On 2022/08/30 05:14 PM, Mattia Rizzolo wrote:

On Mon, Aug 29, 2022 at 08:31:44PM -0700, Steve M wrote:

Quite interestingly, all these 3 uploads caused the service to be killed by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

We've deployed a fix to mentors.debian.net. Could you try to re-upload
your package?

Best,

--
Baptiste Beauplat - lyknode

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQt4kiVMTxdp/CJ4U4XSUsQeV3XMwUCYw+eiQAKCRAXSUsQeV3X M+RWAP92YKaVRLadoeycWV3MVb+/8X9YzJBiSoaZdRyl4n43PgD/W1krhfNivZqc 6RXc1wEtB/cnBq6fSi9ykBNhMbiL1wo=
=EpKL
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2022-08-31 at 19:46 +0200, Baptiste Beauplat wrote:

Hi Steve,

On 2022/08/30 05:14 PM, Mattia Rizzolo wrote:

On Mon, Aug 29, 2022 at 08:31:44PM -0700, Steve M wrote:

Quite interestingly, all these 3 uploads caused the service to be killed
by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

We've deployed a fix to mentors.debian.net. Could you try to re-upload
your package?

Best,

Baptiste,

I have re-uploaded swiftlang to mentors several minutes ago. Lintian takes about
an hour to run so it is too soon for me to know if it has worked or not.

Thanks
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2022-08-31 at 14:09 -0700, Steve M wrote:

On Wed, 2022-08-31 at 19:46 +0200, Baptiste Beauplat wrote:

Hi Steve,

On 2022/08/30 05:14 PM, Mattia Rizzolo wrote:

On Mon, Aug 29, 2022 at 08:31:44PM -0700, Steve M wrote:

Quite interestingly, all these 3 uploads caused the service to be killed
by the OOM killer.... https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/143

So I guess that's why you are not seeing any answer from mentors.

We've deployed a fix to mentors.debian.net. Could you try to re-upload
your package?

Best,

Baptiste,

I have re-uploaded swiftlang to mentors several minutes ago. Lintian takes about
an hour to run so it is too soon for me to know if it has worked or not.

Thanks
-Steve

My package "swiftlang" has been accepted on mentors now. It is missing lintian results: "lintian failed to run: None", but that is ok.

Thanks for the help.
-Steve

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, Aug 31, 2022 at 02:53:26PM -0700, Steve M wrote:

My package "swiftlang" has been accepted on mentors now. It is missing lintian
results: "lintian failed to run: None", but that is ok.

This is great!

however that "None" shows a different bug! :P

https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/146

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmMQyNwACgkQCBa54Yx2 K60Xuw//f61HY2idw+93SLKWPjADtiPjOVyZSnbpK9l0RNsrkHeAIdbQMAgURXZV Kn8ddXtHio00c48chgYOlSqIC1JdJbzZ0sx3N3Qw2aVbcbuWOJlP6/UyGhkDiKAZ TD3STJDWZNzl1jDxtbg2eWWUDLA5j3rK/S8s5i8anlNXdNZ98+ztKWlgrUWRXCf5 aPvO8p4b4juEs66+mSF4koOIX+diYXdwbc/CfqZVTcSzsXDdlj4nHWQQWISxaJXG gw0elC8tRloE/6KpsO9XaUJorPY/77WqkXfAERHE4y/UeifDdgPB4euhDJmLvgcw MuxOWAeyWdSnO0DM2eViOZasrkfX1Q8qROJ4HPnM0tZr6oN9z6d1tLoLA+5BVV23 bXnfb6+40u57H01HXxjYGVO6BRQqR/9T7wzOqMGNKwjd9oN9IbSGuFmlHME1oU97 usQTBzbIU51vb5fOPpTzlRVbdDTeU64aRfmAwzw5s+WRlicMJo/7R/vdRqj/nldY k3+qeuUJuwLyDu99VdGcAjeZa26YpPU3lJQE9TTHnCXEw7AQSNZ