info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
no more Seamonkey in tumbleweed?
2 views
Skip to first unread message
bad sector
Apr 1, 2021, 9:48:50 PM4/1/21
to
I need it for the composer, it was installed but
vanished when I ran a 'zypper dup'
It's been and *will remain* my only word processor
Malcolm
Apr 1, 2021, 10:07:14 PM4/1/21
to
Ask for it to be rebuilt with the new version 2.53.7 which has
just been released after an almost 18 month hiatus ......
https://www.seamonkey-project.org/
https://build.opensuse.org/package/show/mozilla/seamonkey
--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20210330 | GNOME Shell 3.38.3 | 5.11.6-1-default
Intel DQ77MK | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/AMD/Nvidia
up 1 day 10:32, 2 users, load average: 1.55, 1.87, 1.57
Andrew
Apr 2, 2021, 4:59:26 AM4/2/21
to
Malcolm wrote:
> On Thu, 1 Apr 2021 21:48:06 -0400
> bad sector <forgetski@postit_INVALID_.gov> wrote:
>
>>
>> I need it for the composer, it was installed but
>> vanished when I ran a 'zypper dup'
>>
>> It's been and *will remain* my only word processor
>>
>>
> Hi
> Ask for it to be rebuilt with the new version 2.53.7 which has
> just been released after an almost 18 month hiatus ......
>
> https://www.seamonkey-project.org/
> https://build.opensuse.org/package/show/mozilla/seamonkey
>
What do you mean by "almost 18 month hiatus"? The "current" level of
> On Thu, 1 Apr 2021 21:48:06 -0400
> bad sector <forgetski@postit_INVALID_.gov> wrote:
>
>>
>> I need it for the composer, it was installed but
>> vanished when I ran a 'zypper dup'
>>
>> It's been and *will remain* my only word processor
>>
>>
> Hi
> Ask for it to be rebuilt with the new version 2.53.7 which has
> just been released after an almost 18 month hiatus ......
>
> https://www.seamonkey-project.org/
> https://build.opensuse.org/package/show/mozilla/seamonkey
>
Seamonkey on OpenSuse is 2.53.5.1 and it was unleashed on Leap users
around 23 November, four days after it was first announced.
Carlos E.R.
Apr 2, 2021, 6:36:09 AM4/2/21
to
https://software.opensuse.org/package/seamonkey
--
Cheers, Carlos.
Andrew
Apr 3, 2021, 3:18:53 PM4/3/21
to
2.53.x packages for Tumbleweed at one point because he had problems with
an early one and asked for help in a Seamonkey Support group.
You may remember that I was complaining about the ancient (2.49.4) level
of Seamonkey when Leap 15.2 came out, he was the one who fixed it.
I'll see what I can provoke.
Carlos E.R.
Apr 3, 2021, 4:44:09 PM4/3/21
to
but I have no idea how to find out why.
--
Cheers, Carlos.
Tristan Miller
Apr 4, 2021, 11:25:59 AM4/4/21
to
Greetings.
I'm one of the maintainers of the SeaMonkey package for openSUSE. I did
an upgrade of my Tumbleweed machines today and also noticed that the
packages have vanished. It seems that the Tumbleweed builds on OBS [1]
are now broken, but I probably won't have time to look into why until
Friday. In the meantime, you could always download and run the official
binary [2] which is what I'm doing.
Regards,
Tristan
[1] https://build.opensuse.org/package/show/mozilla/seamonkey
[2] https://www.seamonkey-project.org/
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
an upgrade of my Tumbleweed machines today and also noticed that the
packages have vanished. It seems that the Tumbleweed builds on OBS [1]
are now broken, but I probably won't have time to look into why until
Friday. In the meantime, you could always download and run the official
binary [2] which is what I'm doing.
Regards,
Tristan
[1] https://build.opensuse.org/package/show/mozilla/seamonkey
[2] https://www.seamonkey-project.org/
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Apr 4, 2021, 11:28:19 AM4/4/21
to
Greetings.
On 02/04/2021 04.07, Malcolm wrote:
> Ask for it to be rebuilt with the new version 2.53.7
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
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
Andrew
Apr 4, 2021, 12:07:46 PM4/4/21
to
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/
>
Tristan,
> 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/
>
The Seamonkey News-Group you used to ask for advice just over a year ago
is in the process of closing. It is still available and one of the very
last posts there explains what has replaced it.
(Subject "support-seamonkey list / newsgroup" from just after midnight
this morning)
In addition an interested party founded alt.comp.software.seamonkey (and
.firefox, .thunderbird) which are also available via aioe.
The developer who helped back then is one of those who uses it.
Hope that helps, and thanks for caring!
Carlos E.R.
Apr 4, 2021, 3:24:06 PM4/4/21
to
On 04/04/2021 17.28, 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/
Thank you for this information :-)
> 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 guessed there was some problem.
Could you share it as well on sup...@lists.opensuse.org?
<https://lists.opensuse.org/archives/list/sup...@lists.opensuse.org/message/6SL3Z6XB7DNFBS5QXJJDTRWLI57RTWEQ/
If you are not subscribed, I can forward your email there, if that's ok
with you.
--
Cheers, Carlos.
Tristan Miller
Apr 5, 2021, 8:12:25 AM4/5/21
to
Greetings.
On 04/04/2021 21.22, Carlos E.R. wrote:
> Thank you for this information :-)
> I guessed there was some problem.
>
> Could you share it as well on sup...@lists.opensuse.org?
I'll be glad to if you (or someone else) can tell me what newsgroup on
Gmane that mailing list corresponds to.
Regards,
Tristan
On 04/04/2021 21.22, Carlos E.R. wrote:
> Thank you for this information :-)
> I guessed there was some problem.
>
> Could you share it as well on sup...@lists.opensuse.org?
Gmane that mailing list corresponds to.
Regards,
Tristan
Malcolm
Apr 5, 2021, 8:24:08 AM4/5/21
to
On Mon, 5 Apr 2021 14:12:22 +0200
Tristan Miller <psych...@nothingisreal.com> wrote:
>
>
> I'll be glad to if you (or someone else) can tell me what newsgroup
> on Gmane that mailing list corresponds to.
>
> Regards,
> Tristan
>
Hi Tristan
Tristan Miller <psych...@nothingisreal.com> wrote:
>
>
> I'll be glad to if you (or someone else) can tell me what newsgroup
> on Gmane that mailing list corresponds to.
>
> Regards,
> Tristan
>
It's: gmane.linux.suse.opensuse.support
--
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20210330 | GNOME Shell 3.38.3 | 5.11.6-1-default
Intel DQ77MK | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/AMD/Nvidia
Tristan Miller
Apr 13, 2021, 5:31:05 AM4/13/21
to
Dear all,
On 04/04/2021 17.25, Tristan Miller wrote:
> I'm one of the maintainers of the SeaMonkey package for openSUSE. I did
> an upgrade of my Tumbleweed machines today and also noticed that the
> packages have vanished. It seems that the Tumbleweed builds on OBS [1]
> are now broken, but I probably won't have time to look into why until
> Friday.
SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
(except for i586 builds, which weren't working anyway). I'll look at
updating the packages to the current SeaMonkey 2.53.7 later this week,
though this may take a while due to my having to figure out the new
build system and/or adapt the new Makefile from Fedora.
Regards,
Tristan
On 04/04/2021 17.25, Tristan Miller wrote:
> I'm one of the maintainers of the SeaMonkey package for openSUSE. I did
> an upgrade of my Tumbleweed machines today and also noticed that the
> packages have vanished. It seems that the Tumbleweed builds on OBS [1]
> are now broken, but I probably won't have time to look into why until
> Friday.
(except for i586 builds, which weren't working anyway). I'll look at
updating the packages to the current SeaMonkey 2.53.7 later this week,
though this may take a while due to my having to figure out the new
build system and/or adapt the new Makefile from Fedora.
Regards,
Tristan
Tristan Miller
Apr 16, 2021, 4:28:59 AM4/16/21
to
Dear all,
On 13/04/2021 11.31, Tristan Miller wrote:
> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
> (except for i586 builds, which weren't working anyway). I'll look at
> updating the packages to the current SeaMonkey 2.53.7 later this week,
> though this may take a while due to my having to figure out the new
> build system and/or adapt the new Makefile from Fedora.
SeaMonkey 2.53.6 packages are now available for openSUSE 15.x and
openSUSE Tumbleweed (including both i586 and x86_64). The only issue
seems to be that debugsource builds are not longer working, though I'm
looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
RPMs out next week.
On 13/04/2021 11.31, Tristan Miller wrote:
> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
> (except for i586 builds, which weren't working anyway). I'll look at
> updating the packages to the current SeaMonkey 2.53.7 later this week,
> though this may take a while due to my having to figure out the new
> build system and/or adapt the new Makefile from Fedora.
openSUSE Tumbleweed (including both i586 and x86_64). The only issue
seems to be that debugsource builds are not longer working, though I'm
looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
RPMs out next week.
Andrew
Apr 16, 2021, 12:08:41 PM4/16/21
to
Tristan Miller wrote:
> Dear all,
>
> On 13/04/2021 11.31, Tristan Miller wrote:
>> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
>> (except for i586 builds, which weren't working anyway). I'll look at
>> updating the packages to the current SeaMonkey 2.53.7 later this week,
>> though this may take a while due to my having to figure out the new
>> build system and/or adapt the new Makefile from Fedora.
>
>
> SeaMonkey 2.53.6 packages are now available for openSUSE 15.x and
> openSUSE Tumbleweed (including both i586 and x86_64). The only issue
> seems to be that debugsource builds are not longer working, though I'm
> looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
> RPMs out next week.
>
> Regards,
> Tristan
>
Thank you very verry muchly!
> Dear all,
>
> On 13/04/2021 11.31, Tristan Miller wrote:
>> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
>> (except for i586 builds, which weren't working anyway). I'll look at
>> updating the packages to the current SeaMonkey 2.53.7 later this week,
>> though this may take a while due to my having to figure out the new
>> build system and/or adapt the new Makefile from Fedora.
>
>
> SeaMonkey 2.53.6 packages are now available for openSUSE 15.x and
> openSUSE Tumbleweed (including both i586 and x86_64). The only issue
> seems to be that debugsource builds are not longer working, though I'm
> looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
> RPMs out next week.
>
> Regards,
> Tristan
>
Andrew
Apr 27, 2021, 4:50:49 AM4/27/21
to
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
> 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/
>
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.
Tristan Miller
Apr 30, 2021, 12:36:56 PM4/30/21
to
Greetings.
On 27/04/2021 10.50, Andrew wrote:
>> [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1181525
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
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
>
> 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.
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
Apr 30, 2021, 12:45:27 PM4/30/21
to
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
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.
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
Andrew
Apr 30, 2021, 2:43:49 PM4/30/21
to
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.
Andrew
Apr 30, 2021, 3:04:20 PM4/30/21
to
Tristan Miller wrote:
> Dear all,
>
> On 13/04/2021 11.31, Tristan Miller wrote:
>> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
>> (except for i586 builds, which weren't working anyway). I'll look at
>> updating the packages to the current SeaMonkey 2.53.7 later this week,
>> though this may take a while due to my having to figure out the new
>> build system and/or adapt the new Makefile from Fedora.
>
>
> SeaMonkey 2.53.6 packages are now available for openSUSE 15.x and
> openSUSE Tumbleweed (including both i586 and x86_64). The only issue
> seems to be that debugsource builds are not longer working, though I'm
> looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
> RPMs out next week.
>
> Regards,
> Tristan
>
The version in the Leap 15.2 Mozilla Test repository works just fine.
> Dear all,
>
> On 13/04/2021 11.31, Tristan Miller wrote:
>> SeaMonkey 2.53.5.1 packages are now building again for Tumbleweed
>> (except for i586 builds, which weren't working anyway). I'll look at
>> updating the packages to the current SeaMonkey 2.53.7 later this week,
>> though this may take a while due to my having to figure out the new
>> build system and/or adapt the new Makefile from Fedora.
>
>
> SeaMonkey 2.53.6 packages are now available for openSUSE 15.x and
> openSUSE Tumbleweed (including both i586 and x86_64). The only issue
> seems to be that debugsource builds are not longer working, though I'm
> looking into solving this. I will work on getting 2.53.7 and 2.53.7.1
> RPMs out next week.
>
> Regards,
> Tristan
>
This is my "test machine" but the only difference between it and the
normal one - in this context - is that I retrieve Firefox and Seamonkey
from that repository.
Tristan Miller
Apr 30, 2021, 3:05:39 PM4/30/21
to
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
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
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.
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
May 5, 2021, 9:51:36 AM5/5/21
to
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/>.
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.
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/>.
bad sector
Aug 26, 2021, 11:07:16 AM8/26/21
to
On 4/4/21 11:25 AM, Tristan Miller wrote:
> Greetings.
>
>
> On 02/04/2021 03.48, bad sector wrote:
>> I need it for the composer, it was installed but
>>
>> vanished when I ran a 'zypper dup'
>>
>> It's been and *will remain* my only word processor
>
> I'm one of the maintainers of the SeaMonkey package for openSUSE. I
> did an upgrade of my Tumbleweed machines today and also noticed that
> the packages have vanished. It seems that the Tumbleweed builds on
> OBS [1] are now broken, but I probably won't have time to look into
> why until Friday. In the meantime, you could always download and run
> the official binary [2] which is what I'm doing.
>
> Regards, Tristan
🪂
> Greetings.
>
>
> On 02/04/2021 03.48, bad sector wrote:
>> I need it for the composer, it was installed but
>>
>> vanished when I ran a 'zypper dup'
>>
>> It's been and *will remain* my only word processor
>
> I'm one of the maintainers of the SeaMonkey package for openSUSE. I
> did an upgrade of my Tumbleweed machines today and also noticed that
> the packages have vanished. It seems that the Tumbleweed builds on
> OBS [1] are now broken, but I probably won't have time to look into
> why until Friday. In the meantime, you could always download and run
> the official binary [2] which is what I'm doing.
>
> Regards, Tristan
Thank you VERY MUCH, it's now in the TW repo
But it still wasn't in the Leap-15.3 repo so I grabbed the package here
https://www.seamonkey-project.org/releases/seamonkey-2.53.9.en-US.linux-x86_64.tar.bz2
unpacked it into /usr/local and linked the binary to my plasma panel like so:
/usr/local/seamonkey/seamonkey -edit
it's a fire-axe approach but it gives me all that I need from it!
I'll ask the bartender to say a mass for your soul :-)
Andrew
Aug 27, 2021, 10:04:36 AM8/27/21
to
repository
http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/
nowadays - but https://en.opensuse.org/Rust indicates that it is
possible to install newer versions of Rust, which means Seamonkey 2.53.x
levels can now be built. This was a prerequisite to getting Seamonkey
back into the standard repositories.
The levels of Rust currently provided are 1.43, 1.53 and 1.54. (looking
at YaST -> Software Management).
The Mozilla repository I use has one big disadvantage, an updated
Seamonkey is provided every few days.
bad sector
Aug 27, 2021, 6:58:56 PM8/27/21
to
says:
"There is no official package available for openSUSE Leap 15.3"
To me this suggests that there may be issues with using
other versions. Leap, 15.3 today, is my go-to system. If I
wanna risk non-starting apps, system lockups or boot
failures I can always try Tumbleweed. This is my perhaps
mistaken but learned take on it.
Andrew
Aug 28, 2021, 8:47:15 AM8/28/21
to
supply the level of Rust necessary to generate 2.53.x levels of
Seamonkey (Rust is a requirement for generating SM, not executing it).
This deficiency has been recognised and fixed - newer versions of Rust
can now be installed under 15.3. As an aside, I'm told that newer
versions of Rust may possibly break some obscure older functionality -
this is the reason Rust was unchanged from - I think - OpenSUSE 15.1.
Since the Mozilla Test repository has to be able to generate Firefox,
Seamonkey, Thunderbird and possibly some other sins, and they (a guess)
all need the newer version of Rust, that server has a compatible level.
That is why that server is the obvious place to go as long as OpenSUSE
main does not supply Seamonkey. It is also where you can get the
current - rather than the ESR - version of Firefox if you feel that way
inclined. Not sure about Thunderbird, the Mozilla Test repository
offers 78.13.0 and 91.0.2 (the "normal" version is 78.12.0) but I don't
have a clue how Zypper chooses which one to take.
bad sector
Aug 28, 2021, 6:06:54 PM8/28/21
to
standard repo, I also added the mozilla one. For my money the
Mozilla and Gnome as well as the nVidia and Packman repos
should both have been left int the community-repos list of Yast.
https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/
Andrew
Aug 29, 2021, 4:11:02 PM8/29/21
to
"They" is Tristan Miller, he's the maintainer nowadays.
Thank you Tristan!
0 new messages