Re: [arch-dev-public] Tracking different CPU architectures with pkgstats
Hi, I saw your post; I just did not want to go off-topic right away. :-) At least as long as I am the only contributor I hesitate to give up on how the infrastructure is set up. It seems to be much more complex to do this on "official" servers. I like being able to switch things around outside of just deploying some scripts. E.g. I do automatic deployments, updates, change Web server or database configurations etc.. Greetings, Pierre On Mon, Mar 15, 2021 at 10:42 PM Sven-Hendrik Haase via arch-dev-public wrote: > > On Sun, 14 Mar 2021 at 15:17, Levente Polyak via arch-dev-public > wrote: > > > > On 3/14/21 3:07 PM, Pierre Schmitz via arch-dev-public wrote: > > > I just updated the server to also accept x86_64 feature levels, ARM > > > and even i686. There is a new version of pkgstats (>= 3.1.0; currently > > > in [testing]) which is able to detect feature levels. ARM support is > > > pretty early, but x86_64 should be fine (using Intel's cpuid library). > > > > > > If you like to check what gets detected on your system run: > > > $ pkgstats submit --dump-json | head > > > system.architecture is your CPU and os.architecture should be the same > > > as "uname -m" > > > > > > Let me know if this does work for you and especially if it does not. > > > Using Qemu for testing is quite limited and I lack old, new and AMD > > > CPUs. > > > > > > An API and UI to analyze these data will follow in the future. (I > > > guess we need to wait a few weeks to see some valid results) > > > > Hi Pierre, > > > > that sounds wonderful, thanks for the work, this will be nice data points :) > > > > Did you see my previous mail? It would be amazing if you can consider > > growing this side-project into something official in terms of being > > available on http://pkgstats.archlinux.org/ > > > > I think this is really a great idea and project that we should advocate > > in the official hosting namespace :) > > > > cheers and thanks, > > Levente > > > > I second this and we've tried to touch on this in the past. I think > "officializing" pkgstats would be neat. > > Cheers, > Sven
Re: [arch-dev-public] Tracking different CPU architectures with pkgstats
On 3/16/21 6:00 PM, Pierre Schmitz via arch-dev-public wrote: > Hi, I saw your post; I just did not want to go off-topic right away. > :-) At least as long as I am the only contributor I hesitate to give > up on how the infrastructure is set up. It seems to be much more > complex to do this on "official" servers. I like being able to switch > things around outside of just deploying some scripts. E.g. I do > automatic deployments, updates, change Web server or database > configurations etc.. > Hey Pierre :) Hm I kind of get the way you feel... but i really really believe it would be very beneficial if we make this an official project. I don't think there needs to be a strong relation between contributor and hosting, we also host foreign software we don't even write ourselves. Otherwise every main dev of one of our projects would just host their stuff on their private servers as well :D I don't think you need to have any fear about the complexity or losing control, it is actually pretty straight forward and the devops team is more then open to implement every single bit of the devops ansible infra setup. So there won't be any workload on you :) There are multiple ways, for the security tracker (which I'm also more or less basically the only main dev :P) it is as easy as just bumping the commit hash [0]. I kind of understand your "concern", if you aim more for a fluent deployment, we have also prototyped GitLab CI pipeline deployment for the AUR in a convenient and secure way. This can give more deployment control without the need to always touch ansible. I'm a hundred percent convinced there is a good way to make all parties happy and still be able to promote your side project into an awesome official bit of Arch Linux as it truly deserves it. sincerely, Levente PS: we have a bottom reply post policy on our mailinglist :D :D :D [0] https://gitlab.archlinux.org/archlinux/infrastructure/-/commit/61869fdd16fe59feec413ba6815bb2a719a3d26f OpenPGP_signature Description: OpenPGP digital signature
[arch-dev-public] Arch Linux partners with Nitrokey to equip its staff with USB keys
We are happy to announce that Arch Linux has partnered with Nitrokey [0] to equip its staff with free Nitrokey devices. We will use the Nitrokey devices to store cryptographic keys for signing of git commits, emails and software packages, GnuPG keys, and SSH accounts. Thanks to the Nitrokey’s discount and the Arch Linux funds, each Arch Linux staff is eligible to receive one free Nitrokey Pro 2 or hopefully soon the new Nitrokey 3. To receive their Nitrokey, eligible staff will need to register with their @archlinux.org email address at the dedicated order form. Further instructions about this process will be sent to our staff. A Nitrokey Guide will be made available on the Arch Linux Wiki with FAQ & instructions for integrating Nitrokeys into our workflow. Nitrokey Pro 2 provides strong reliable hardware encryption. It has open source firmware, is open hardware and can help you to: sign Git commits; decrypt emails and files; secure server access; and protect accounts against identity theft via two-factor authentication (one-time passwords). Furthermore, the new Nitrokey 3 will support additional features like FIDO. Nitrokey is a German IT security company committed to open source hardware and software. Nitrokey develops and produces USB keys for data encryption, email encryption (PGP/GPG, S/MIME), and secure account logins (SSH, two-factor authentication via OTP and FIDO). Besides their hardware products they offer services, consulting and help you with concept, development and certification of your specific security solutions. Nitrokey is proud to support Arch Linux in further securing its infrastructure and contributing to a secure open source Linux ecosystem. [0] https://www.nitrokey.com/ OpenPGP_signature Description: OpenPGP digital signature
