You are not logged in.
Hello developer,
when we get firefox 83.0-2?
archlinux amd64
https://www.archlinux.de/packages/extra/x86_64/firefox
The archlinux amd64 allways much faster.
Many package in archlinux32 are old.
Greets
arch322yes
Last edited by arch322yes (2020-12-12 19:33:21)
Offline
The archlinux amd64 allways much faster.
Yes, to an extent that's to be expected. Stable builds on arch64 eventually find their way into arch32 testing (although I'm not sure how the staging repos fit into this timeline to be fair), and theoretically at least are tested there before being promoted to stable.
I don't think that entirely explains the delays in firefox however, which hasn't even turned up in testing yet. There are some changelogs in the release notes that might be worth having for us 32-bit users, but only really if you let the javascript engine run rampant IIRC.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
arch322yes wrote:The archlinux amd64 allways much faster.
Yes, to an extent that's to be expected. Stable builds on arch64 eventually find their way into arch32 testing (although I'm not sure how the staging repos fit into this timeline to be fair), and theoretically at least are tested there before being promoted to stable.
arch32 is behind arch by design: we only (attempt to) build what already is in archlinux's core/extra/community (e.g. "stable") repositories. Then it traverses staging and testing to stable.
Additionally, we're sabotaged from many sources:
- arch PKGBUILDs, that won't even work on x86_64: because the source was exchanged upstream, because there is some not-shown boostrap necessary, because the PKGBUILD simply does not match the package by human error, etc.
- arch PKGBUILDs, that won't work on 32-bit: because they are written for x86_64 only, because the software is written for x86_64 only, because the software has severe bugs on i686, because they depend on stuff (which is not important for the core functionality), that isn't available on arch32 (for one of the former reasons), etc.
- bugs in our build system (a.k.a. my mistakes)
Offline
Stable builds on arch64 eventually find their way into arch32 testing (although I'm not sure how the staging repos fit into this timeline to be fair), and theoretically at least are tested there before being promoted to stable.
Moving from staging to testing goes totally automatic (when all dependencies are available and no packages in testing will get broken because some dependency in testing would be deleted/updated).
Moving from testing to stable goes automatic, too (by the same criteria as above), but requires the package to either be actively tested (and marked as "good") or sitting around for some time (I think, 7 days) without issues being reported.
in my experience, "staging -> testing" goes almost immediately (except for big rebuilds of python or so), while "testing -> stable" strongly depends on all kind of strange factors ...
Offline
Am I as a user and kind of a tester, permitted to mark things as good? If so, how would I go about this?
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
sure, you are!
The process is a little convoluted (but can be fully automated, if you like)
Offline
Oof, yes that is a little convoluted. I will bump it up my list of things to look at doing however.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
I'm open to suggestions on how to improve the process (or add a different report way which is more convenient for you)
Offline
Yes, it's the setting up of msmtp that's the scariest thing to me. My normal mail client these days is claws-mail, and from reading it's man page it looks possible to make it bring up a pre-filled in window (although it doesn't say how you specify it should be gpg encrypted).
Edit: Also, while it's been able to check the signature on incoming mails for me, it seem signing stuff is still a little broken (or probably misconfigured, but that still counts as broken in one sense at least). It doesn't seem to be able to find any of my keys.
Might be simpler just to go thought the steps and set up msmtp. Although it would be nice for a couple of people I mail regularly if I could encrypt my mails properly.
Last edited by levi (2020-12-13 00:07:47)
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline