Tristan Miller wrote:
> Greetings.
>
> On 02/04/2021 04.07, Malcolm wrote:
>> Ask for it to be rebuilt with the new version 2.53.7
>
>
> I'm one of the maintainers of the SeaMonkey package for openSUSE.
> Unfortunately, in SeaMonkey 2.53.6 the build system changed in a way
> that broke the scripts used by many packagers (not just for openSUSE but
> other distributions as well).  I spent a long time trying to get things
> to work again back in January but was unsuccessful; I also reached out
> to the other package maintainer but received no response.
>
> In February I was contacted by the SeaMonkey packager for Fedora, who
> seems to have figured out how to get his own RPMs to build again, and
> shared some advice and a new Makefile.  Unfortunately, due to real life
> commitments I haven't yet been able to look into these yet.  I expect
> I'll be able to do this starting in mid-April.
>
> In the meantime, if anyone else wants to give things a shot, you can
> discuss your results at the bug I've raised for this issue [1] or you
> can just download and run the official binaries [2] which is the
> workaround I'm using.  In any case, you might want to CC yourself on
> that bug as that way you'll be notified when it's fixed.
>
> Regards,
> Tristan
>
> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181525
>
> [2] https://www.seamonkey-project.org/
>

I see that bug 1181525 was marked as "Resolved Fixed" on April 16, but
neither 2.53.6 nor the later levels have made it to the Leap-Update
repository yet. The current level on Leap-Mozilla-Test is 2.53.7.1, it
has been available there since April 20.

Greetings.

On 27/04/2021 10.50, Andrew wrote:
>> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181525
>>
>
> I see that bug 1181525 was marked as "Resolved Fixed" on April 16, but
> neither 2.53.6 nor the later levels have made it to the Leap-Update
> repository yet.  The current level on Leap-Mozilla-Test is 2.53.7.1, it
> has been available there since April 20.

The bug in question was just about building Leap packages for SeaMonkey
2.53.6, not about actually submitting them to the official Leap
repository. (There is a separate bug for each package submission to
Leap.) I never bothered submitting the packages because I built 2.53.6,
2.53.7, and 2.53.7.1 in rapid succession (over the course of two or
three days) and figured that users would care only about the latest version.

Is it important for you (or anyone else) to get 2.53.6 and 2.53.7
packages in the official Leap update repository? If so, I can try
retroactively submitting them, though to be honest I'm not sure if OBS
will even let me submit anything other than the current revision of a
devel project package, let alone if the update repository maintainers
would actually accept such a submission. I might need to ask about this
first.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Greetings.

On 30/04/2021 18.36, Tristan Miller wrote:
> On 27/04/2021 10.50, Andrew wrote:
>>> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181525
>>>
>>
>> I see that bug 1181525 was marked as "Resolved Fixed" on April 16, but
>> neither 2.53.6 nor the later levels have made it to the Leap-Update
>> repository yet.  The current level on Leap-Mozilla-Test is 2.53.7.1,
>> it has been available there since April 20.
>
> The bug in question was just about building Leap packages for SeaMonkey
> 2.53.6, not about actually submitting them to the official Leap
> repository.  (There is a separate bug for each package submission to
> Leap.)  I never bothered submitting the packages because I built 2.53.6,
> 2.53.7, and 2.53.7.1 in rapid succession (over the course of two or
> three days) and figured that users would care only about the latest
> version.
>
> Is it important for you (or anyone else) to get 2.53.6 and 2.53.7
> packages in the official Leap update repository?  If so, I can try
> retroactively submitting them, though to be honest I'm not sure if OBS
> will even let me submit anything other than the current revision of a
> devel project package, let alone if the update repository maintainers
> would actually accept such a submission.  I might need to ask about this
> first.

Oh, it occurs to me now that you're saying that even the 2.53.7.1
packages are missing from the Leap update repository. If so, I suspect
that's because my submission of the package [1] [2] was accepted only
today, though I see now that for some reason the SeaMonkey project that
got created in the update repository [3] is failing to build. I'll take
a look into it.

Regards,
Tristan

[1] https://build.opensuse.org/request/show/888961

[2] https://bugzilla.opensuse.org/show_bug.cgi?id=1185349

[3]
https://build.opensuse.org/package/show/openSUSE:Maintenance:16186/seamonkey.openSUSE_Leap_15.2_Update

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Tristan Miller wrote:
> Greetings.
>
> On 30/04/2021 18.36, Tristan Miller wrote:
>> On 27/04/2021 10.50, Andrew wrote:
>>>> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181525
>>>>
>>>
>>> I see that bug 1181525 was marked as "Resolved Fixed" on April 16,
>>> but neither 2.53.6 nor the later levels have made it to the
>>> Leap-Update repository yet.  The current level on Leap-Mozilla-Test
>>> is 2.53.7.1, it has been available there since April 20.
>>
>> The bug in question was just about building Leap packages for
>> SeaMonkey 2.53.6, not about actually submitting them to the official
>> Leap repository.  (There is a separate bug for each package submission
>> to Leap.)  I never bothered submitting the packages because I built
>> 2.53.6, 2.53.7, and 2.53.7.1 in rapid succession (over the course of
>> two or three days) and figured that users would care only about the
>> latest version.
>>
>> Is it important for you (or anyone else) to get 2.53.6 and 2.53.7
>> packages in the official Leap update repository?  If so, I can try
>> retroactively submitting them, though to be honest I'm not sure if OBS
>> will even let me submit anything other than the current revision of a
>> devel project package, let alone if the update repository maintainers
>> would actually accept such a submission.  I might need to ask about
>> this first.
>
>
> Oh, it occurs to me now that you're saying that even the 2.53.7.1
> packages are missing from the Leap update repository.  If so, I suspect
> that's because my submission of the package [1] [2] was accepted only
> today, though I see now that for some reason the SeaMonkey project that
> got created in the update repository [3] is failing to build.  I'll take
> a look into it.
>
> Regards,
> Tristan
>
> [1] https://build.opensuse.org/request/show/888961
>
> [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1185349
>
> [3]
> https://build.opensuse.org/package/show/openSUSE:Maintenance:16186/seamonkey.openSUSE_Leap_15.2_Update
>
>

You are correct in that reassessment, I was wondering when a new level
was going to make it to the Update repository.
"Failing to build"? That *is* a surprise.

According to [3] Seamonkey requires rust >= 1.47 in order to build (but
not to execute, my Yast/Software Management search for "rust" did not
show any installed packages).
Tumbleweed uses rust 1.51
Leap 15.2 uses rust 1.43.1

Thank you.
I have a test machine running Leap and I suppose I could download your
Seamonkey 2.53.7.1 from there (the Mozilla Test repository) and see if
it works. If not, grabbing the Tumbleweed version would be worth a
test, I'll have to check the Seamonkey dependencies before doing that.

Greetings.

On 30/04/2021 20.43, Andrew wrote:
> According to [3] Seamonkey requires rust >= 1.47 in order to build (but
> not to execute, my Yast/Software Management search for "rust" did not
> show any installed packages).
> Tumbleweed uses rust 1.51
> Leap 15.2 uses rust 1.43.1

Yes, it seems that the build environments in the two projects differ.
I'm loath to lower the rust version dependency in the spec file because
upstream says that 1.47 or higher is required.

> I have a test machine running Leap and I suppose I could download your
> Seamonkey 2.53.7.1 from there (the Mozilla Test repository) and see if
> it works.

That's what I'm doing on my Leap machines. (Either that, or just using
the build I produce locally.) The Tumbleweed SeaMonkey won't work on
Leap; zypper (or YaST2) will complain about missing glibc dependencies
when you try to install it.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Greetings.

On 30/04/2021 21.05, Tristan Miller wrote:
>> According to [3] Seamonkey requires rust >= 1.47 in order to build
>> (but not to execute, my Yast/Software Management search for "rust" did
>> not show any installed packages).
>> Tumbleweed uses rust 1.51
>> Leap 15.2 uses rust 1.43.1
>
> Yes, it seems that the build environments in the two projects differ.
> I'm loath to lower the rust version dependency in the spec file because
> upstream says that 1.47 or higher is required.

I got in touch with the person at SUSE who accepted the submission and
he says he'll see if he can bootstrap a newer version of Rust for Leap
15.2 next week. After that I presume that the SeaMonkey 2.53.7.1
package will automatically get built and appear in the Leap 15.2 Update
repository.

In the meantime, Leap 15.2 users can use the SeaMonkey RPMs from the
Mozilla repository at
<http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.2/>.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-