Howdy,
I've been dealing with this for a while. When I do my updates, it
either omits seamonkey because the rust version installed is to new or downgrades rust. I keyworded rust to see if emerge could sort it out
itself but Seamonkey then complains about the newer version of rust.
I've read some stories about rust and such but this is annoying. Is
there not a way to make both packages happy? For once, I'd like to be
able to update and get a clean outcome. Heck, at this point, I'm a bit confused. I've went around in circles so much, I feel like a
professional drunk. :/
Thoughts?
On Mon, 10 Jan 2022 at 08:50, Dale <rdalek1967@gmail.com> wrote:
Howdy,I would try to remove this dependency in an overlay. I noticed the
I've been dealing with this for a while. When I do my updates, it
either omits seamonkey because the rust version installed is to new or
downgrades rust. I keyworded rust to see if emerge could sort it out
itself but Seamonkey then complains about the newer version of rust.
I've read some stories about rust and such but this is annoying. Is
there not a way to make both packages happy? For once, I'd like to be
able to update and get a clean outcome. Heck, at this point, I'm a bit
confused. I've went around in circles so much, I feel like a
professional drunk. :/
Thoughts?
release notes for seamonkey 2.53.10.2 mentions fixing something about rust-1.57, and no mention of rust in any of the versions between the
latest in portage and that one, so I question if there is actually a dependency on an older rust here.
Regards,
Arve
On Mon, 10 Jan 2022 at 11:33, Dale <rdalek1967@gmail.com> wrote:
I read in a bug report that this is fixed in a overlay. Makes me wonder why this has been going on for a month or so without a 'in tree' fix.
I'd rather not add a overlay but if it is the only fix, may have too.
An alternative to adding the whole overlay (and the poly-c overlay is
quite big) is to just copy the ebuild you want to your local overlay.
It looks like poly is involved in the maintenance of this package
normally, so I'm not sure why this is not in the main repo yet, if
there is something weird being worked on.
The biggest change if you copy it locally, is that you get the latest released version of seamonkey, and the rust dependency in the ebuild
has been updated to:
=virtual/rust-1.34.0
That seems to indicate that the current requirement of <1.53 was never correct?
Either way, worth a try if you ask me, you're on a newer version, the
rust conflict with firefox will not come up again, and hopefully
eventually, the main gentoo repo will get even newer versions so
you'll get automatically updated without having added a full extra
overlay.
I read in a bug report that this is fixed in a overlay. Makes me wonder
why this has been going on for a month or so without a 'in tree' fix.
I'd rather not add a overlay but if it is the only fix, may have too.
=virtual/rust-1.34.0
On Mon, 10 Jan 2022 at 12:28, Arve Barsnes <arve.barsnes@gmail.com> wrote:
On Mon, 10 Jan 2022 at 11:33, Dale <rdalek1967@gmail.com> wrote:Also, the ebuild to copy:
I read in a bug report that this is fixed in a overlay. Makes me wonder >>> why this has been going on for a month or so without a 'in tree' fix.An alternative to adding the whole overlay (and the poly-c overlay is
I'd rather not add a overlay but if it is the only fix, may have too.
quite big) is to just copy the ebuild you want to your local overlay.
It looks like poly is involved in the maintenance of this package
normally, so I'm not sure why this is not in the main repo yet, if
there is something weird being worked on.
The biggest change if you copy it locally, is that you get the latest
released version of seamonkey, and the rust dependency in the ebuild
has been updated to:
=virtual/rust-1.34.0That seems to indicate that the current requirement of <1.53 was never correct?
Either way, worth a try if you ask me, you're on a newer version, the
rust conflict with firefox will not come up again, and hopefully
eventually, the main gentoo repo will get even newer versions so
you'll get automatically updated without having added a full extra
overlay.
https://www.gentoofan.org/gentoo/poly-c_overlay/www-client/seamonkey/seamonkey-2.53.10.2-r2.ebuild
Cheers,
Arve
rsync: getaddrinfo: rsync.gentoofan.org 873: Temporary failure in name resolution
On Wed, 12 Jan 2022 at 02:14, Dale <rdalek1967@gmail.com> wrote:
rsync: getaddrinfo: rsync.gentoofan.org 873: Temporary failure in nameI noticed somewhere on the page it said that the layman method of
resolution
adding the overlay was deprecated, maybe he has removed rsync
capability for it.
Regards,
Arve
Well, first a patch failed to . . . patch. I commented it out and
rebuilt the manifest and gave that a try. Then it failed with this:
Arve Barsnes wrote:
On Wed, 12 Jan 2022 at 02:14, Dale <rdalek1967@gmail.com> wrote:
rsync: getaddrinfo: rsync.gentoofan.org 873: Temporary failure in nameI noticed somewhere on the page it said that the layman method of
resolution
adding the overlay was deprecated, maybe he has removed rsync
capability for it.
Regards,
Arve
Well, that would make sense. Guess I'll steal the ebuild you linked to
and put it in my overlay. I was hoping for a overlay that would update itself but maybe not.
Thanks.
Dale
:-) :-)
* Skipping make test/check due to ebuild restriction.Source compiled.
sed: can't read /var/tmp/notmpfs/portage/www-client/seamonkey-2.53.10.2-r2/files/all-gentoo-1.js:Test phase [disabled because of RESTRICT=test]: www-client/seamonkey-2.53.10.2-r2
Install www-client/seamonkey-2.53.10.2-r2 into /var/tmp/notmpfs/portage/www-client/seamonkey-2.53.10.2-r2/image
I tried to set up dovecut once but failed. I guess I better get back on that since I use Seamonkey to do my email with. I don't like
Thunderbird and sadly may not like much of the other email methods either.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 293 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 234:03:17 |
| Calls: | 6,624 |
| Files: | 12,172 |
| Messages: | 5,319,637 |