- Arch-dev-public - lists.archlinux.org

[arch-dev-public] Switching the bugtracker to Bugzilla
by Jelle van der Waa 20 Nov '17

20 Nov '17

It's time to switch our to something which is maintained and can be extended to our wishes. Flyspray isn't actively maintained, has had several security issues [1] [2]. It seems to be time to move on, and Bugzilla is one of the more active and maintained bugtrackers out there. Used by several big projects such as Gnome, LLVM and Mozilla. One of the benefits of moving would be the possibility of default assignees per 'component'. # Migration There are several options for migrating the bug history to Bugzilla and a few options are under debate. (input welcome) * No migration at all * Migrate open bugs * Migrate open bugs and auto-closing them * Migrate all bugs * Migrate all bugs and auto-closing them In either case, I believe it would be nice to "archive" the current bugtracker and make it read only. # User migration User migration should be possible as well, except migrating the password, a mass password reset would be wise. Since I'm not sure what kind of old hashing method / salt flyspray uses. # Migration Projects Bugzilla has a concept of products with components, so for all our packages we can create a component counterpart. It should be possible to auto-assign bugs with the pkgname <-> maintainer information from archweb. Possible products would be. # Products * Arch packages (core/extra or split this up) * Community packages (community) * Pacman * AURWeb * Keyring * Archweb (new) * Arch VM / Docker images (new) * Release engineering Input would be welcome, on what we should migrate from flyspray and what products we should define. [1] https://github.com/Flyspray/flyspray/releases/tag/v1.0-rc6 [2] https://github.com/Flyspray/flyspray/releases/tag/v1.0-rc4 -- Jelle van der Waa

11 14

[arch-dev-public] Resigning as TU
by Evangelos Foutras 17 Nov '17

17 Nov '17

For a long time I have been inactive in TU matters (i.e.: handling AUR requests, looking into TU applicants, and overseeing community contributions in general). Due to this, I feel it's proper to let go of my TU title. No heartfelt goodbyes, since my involvement in Arch remains unchanged. (On a related note, where did the last 9 years go?!)

1 0

[arch-dev-public] [draft] The end of i686 support
by Bartłomiej Piotrowski 06 Nov '17

06 Nov '17

Following 9 months of [deprecation period][1], support for the i686 architecture effectively ends today. By the end of November, i686 packages will be removed from our mirrors and later from the packages archive. For users unable to upgrade their hardware to x86_64, an alternative is a community maintained fork named [Arch Linux 32][2]. See their website for details on migrating existing installations. [1]: https://www.archlinux.org/news/phasing-out-i686-support/ [2]: https://archlinux32.org/

6 8

[arch-dev-public] aurweb 4.6.0 release preparations
by Lukas Fleischer 03 Nov '17

03 Nov '17

Hi, Since the AUR ToS documents are still being reviewed and I do not expect any major progress within the next couple of weeks, I would like to release 4.6.0 before the documents are polished (against my original plans to synchronize the aurweb release with the ToS release). Apart from proper ToS support, the current development version includes some nice features such as Markdown support in comments as well as some bug fixes. There is one change, namely commit d9883ee (mkpkglists: Generate a list of user names, 2017-08-01), which might be a bit controversial as-is. It extends the public interface to provide a list of user names (just the account names, no real name). Some members of our team expressed their concerns with making such a change without informing all registered users. Therefore, I would like to send an automated email to all registered AUR accounts, informing them on the change and giving them the chance to opt-out of the feature by deleting their accounts (all accounts with any kind of activity already reveal their user names, so people potentially concerned about making their user name publicly visible do not need their accounts anyway). Here is a draft: Dear AUR user, The next aurweb release, which will be released on 2017-12-03, includes a public interface to obtain a list of account names of all registered users. This means that, starting on 2017-12-03, your user name (only the account name you specified when registering, not your real name) will be visible to the general public. If you do not agree to this change, please delete your account by logging into the AUR web interface, going to your account details page and clicking the account deletion link before 2017-12-03. Thanks for using the AUR! The AUR Development Team If have any objections/improvements, please let me know. Regards, Lukas

3 4

[arch-dev-public] Orphan mono packages
by Antonio Rojas 24 Oct '17

24 Oct '17

After Daniel's resignation, mono related packages became orphan. anthraxx and grazzolini adopted nuget and mono itself, but the following packages still don't have a maintainer: monodevelop xsd mod_mono mono-basic boo mono-debugger mono-upnp gtk-sharp-beans gettext-mono and others I may have missed. mono stuff breaks frequently (in fact most of these packages don't build currently) so they need a dedicated maintainer. Please adopt them if you're interested (or reply here so they're moved to community if you're a TU), otherwise I'll drop them in a few days.

2 2

[arch-dev-public] Away 31.10 - 5.11
by Bartłomiej Piotrowski 22 Oct '17

22 Oct '17

Hi all, as I'll be traveling in the beginning of November, you will have to bear building for i686 one week more. I'll prepare news draft before I'm gone and changes to devtools are ready, so it won't take long after my return. Bartłomiej

1 0

[arch-dev-public] Stepping back as Arch Linux developer
by Daniel Isenmann 17 Oct '17

17 Oct '17

Hi there, that wasn't an easy decision, but after months of inactivity and only sporadic checks of the mailing lists and emails, I have decided to step back. My interests moved and my free time is limited and Arch Linux deserves more time than I can actually offer. It was a fantastic and excited journey over all these years. It was great to be part of this community. I have met interesting people along the way, had interesting discussions and learned a lot. I wish Arch Linux and each of you all the best. Nevertheless I will be around as a user. Keep Arch Linux rolling.... Cheers Daniel

5 4

[arch-dev-public] systemd, kernel keyring and pam_keyinit
by Christian Hesse 06 Oct '17

06 Oct '17

Hello everybody, systemd v233 introduced code that makes use of the kernel keyring, initializing a private keyring for every service and adding a protected key named "invocation_id". This caused some trouble and we reverted it since then. Things will change with systemd v235, which adds a new option "KeyringMode=" for units. The values are "inherit", "private" and "shared". The commit [0] message and changes give the details. Now cryptsetup units are generated with "KeyringMode=shared", which unbreaks this use case. Other services that use the kernel keyring and want to share secrets with other services have to add this as well. However login sessions where user context is changed can not be handled by systemd. Looks like we have to update our PAM configurations and add a line for every service where session is expected to use the kernel keyring: session optional pam_keyinit.so force revoke This is required for eCryptfs to function properly. Any comments on this? Any concerns? I would like to keep the upstream keyring behavior with release version 235. Would be nice to have this sorted before. [0] https://github.com/systemd/systemd/commit/b1edf4456eabc5951d76b96bc7df2db3f… -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}

1 2

[arch-dev-public] closure-linter, closure-compiler
by Ike Devolder 28 Sep '17

28 Sep '17

I just disowned closure-linter and closure-compiler. I no longer use these and have no more interest to just bump versions for the sake of bumping the version without proper testing. If someone is interested feel free to adopt. When no-one adopts within a few weeks I'll move it to AUR. -- Ike

1 0

[arch-dev-public] removed mariadb 10.1.27 from [testing]
by Christian Hesse 26 Sep '17

26 Sep '17

Hello everybody, after the release of 10.1.27 upstream was made aware of a regression, so the release has been pulled from the downloads system. The fix will be in 10.1.28. I removed mariadb 10.1.27 packages from [testing]. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}

1 0