Re: Call for participation: Git packaging POC 🚀🎉
Hey Brett, I think it would also be nice to have a "password command" option wherein a command would be run every time it needs the token. For instance: token_cmd='pass pkgctltoken' That way there isn't a token hanging around in the environment. that is exactly the idea behind the environment variable, the MR[0] with the manpage entry and prompt regarding the token just wasnt merged yet. You can create an alias for pkgctl like the following in your bash- or zshrc, just note the quoting: $ alias pkgctl='DEVTOOLS_GITLAB_TOKEN="$(command to obtain token)" pkgctl' So the command is evaluated each time when pkgctl is invoked on the shell and the token does not hang around in the environment :) If you want to, you can also have a look at this configuration in my dotfiles[1]. cheers, gromit [0] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/144/diffs#2af9d23df78ef3e268721604c5f8d3fd15a52a13_0_24 [1] https://github.com/christian-heusel/dotfiles/blob/b591506816f8034d67479dfa63431dab4fa156e5/roles/shell-configuration/templates/zshrc.j2#L97 OpenPGP_0x93B11DAA4C197E3D.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Vacation until August
Hey Morten, > I'll be taking a break in July. Have a couple of weeks vacation before > starting > new work in August and need a bit of time to reset. Enjoy the break! Hope you have the chance to refill where needed and can start out fresh in August at your new job! > I'm not going to look at package updates, bugreports, respond to stuff and > misc > other responsebilities I have during this time. However, if I'm blocking > someone > on something please do reach out. I'm still terminally online and reachable :) I can try to have a look at the packaging side of things during that time ... :) It would be great if you could drop me a link to your latest nvchecker config via pm as that would make things easier .. cheers, gromit / chris signature.asc Description: PGP signature
Re: Bugtracker Migration to GitLab
On 23/11/10 12:08AM, Levente Polyak wrote: > ## Rollout Timeline > > If no significant issues arise, we will proceed with the rollout in > approximately 2 weeks. This entails disabling login on Flyspray and > importing all bugs into GitLab. Subsequently, Flyspray will be replaced with > static sites to preserve historical data for some time. Following up on the previous mail we will roll out this change next Saturday (25th November) throughout the day. During the migration we will have to change/deploy various projects aswell as doing the migration itself, so please bear with us and report any inconsistencies only if they still persist the next day. Please have another look at the test setup (as described by the previous mail in this thread) and report any feedback back to us before the migration. This helps us so we can adapt the tooling before the changes go live! Cheers, gromit signature.asc Description: PGP signature
Bug migration post rollout mail [was: Re: Bugtracker Migration to GitLab]
On 23/11/25 04:57PM, Jelle van der Waa wrote: > Hi, > > For all whom it may concern, we are migrating Flyspray issues to Gitlab now > and have disabled bug creation/commenting on Flyspray for reports. > > Bear with us while we break Arch. > > Greetings, > > Gromit & Jelle > Things did go smooth and we migrated all issues from flyspray to GitLab! 🥳 This implies the following changes: - Bugs for packages are now opened on the repo hosting the corresponding packaging sources, "Add a new Bug" on the package page will automatically direct you to the correct package. - A list of all issues can be found [here][0]. To filter for issues assigned to a specific package maintainer, use the filter input box. A link containing the filter can be bookmarked for convenience. - Merge Requests for packaging repos have been enabled - bugs.archlinux.org is readonly and will be replaced by a static clone of the site soon - Navbars on our major webpages have been updated to include a link to GitLab instead of flyspray - the flyspray-migration test group (referenced in previous mails in this thread) has been deleted - Arch Linux Package Maintainers that also want to be assigned to unconfirmed bug of their packages have to react with "🔍" to this [issue][1] If you do not have an account for GitLab already please write us a short mail to accountsupp...@archlinux.org as advised in the banner! Greetings, Jelle, anthraxx & gromit [0]: https://gitlab.archlinux.org/groups/archlinux/packaging/-/issues [1]: https://gitlab.archlinux.org/archlinux/bugbuddy/-/issues/1 signature.asc Description: PGP signature
News Draft: "Bugtracker migration to GitLab completed"
Hello everyone, as we have completed the bugtracker migration it would be good to post a news item about it. Please give feedback if you have any about the draft below! Cheers, klausenbusk & gromit --- # Bugtracker migration to GitLab completed We are happy to announce that the migration of the bugtracker to GitLab is done! 🥳 This means the issue tracker and merge requests on the Gitlab package repos are now enabled. The old bugtracker will subsequently be closed down. For archiving reasons there will be a static copy so that links (for example the randomly picked [Task #56716][0]) are still stable, migrated bugs have a closing comment pointing to the new URL on GitLab. Packaging bugs are now opened on the repo hosting the corresponding packaging sources, the "Add a new Bug" Button on the package page on archlinux.org will automatically direct you to the correct place to open the issue. The workflow afterwards is mostly the same, first our [Bug Wranglers][1] will have a look at the issues and triage them and then they will be handed over to the respective [Package Maintainers][2] to fix. A list of all issues can be found [here][3]. If you do not have an account for GitLab already please write us a mail with your desired username to accountsupp...@archlinux.org as advised in the banner! Thanks to everyone who has helped during the migration! [0]: https://bugs.archlinux.org/task/56716 [1]: https://gitlab.archlinux.org/groups/archlinux/teams/bug-wranglers/-/group_members [2]: https://gitlab.archlinux.org/archlinux/teams/package-maintainer-team [3]: https://gitlab.archlinux.org/groups/archlinux/packaging/-/issues signature.asc Description: PGP signature
Spring cleanup '24
Hello everyone, the amount of birds that are chirping in front of my flat make it clear that spring is coming (at least to Heidelberg). :p Therefore it is time to do our annual spring cleanup and free the repos from any leftovers. Please head to https://archlinux.org/devel/reports/unneeded-orphans/ and adopt packages that you'd like to keep in the repos. The devs among us should maybe also have a look at the (few) [orphans in [core]][0]. This is maybe also a good time to re-evaluate the current package set you maintain and disown anything that you've lost interest in so others can properly maintain it either in the repos or the AUR. Feel free to drop a message here if its anything major. I will start dropping packages on 2024-03-17, so please try to have a look at the lists in the next few days. Cheers, gromit [0]: https://archlinux.org/packages/?sort=&repo=Core&q=&maintainer=orphan signature.asc Description: PGP signature
Re: Spring cleanup '24
On 24/03/02 12:48PM, gromit wrote: > Please head to https://archlinux.org/devel/reports/unneeded-orphans/ and > adopt packages that you'd like to keep in the repos. > > I will start dropping packages on 2024-03-17, so please try to have a > look at the lists in the next few days. Reminder: There is one week left until unneeded orphan packages will be dropped to the AUR. Please have a look at the list again to see if other people orphaned stuff that may be intersting for you. Cheers, gromit signature.asc Description: PGP signature
Re: Spring cleanup '24
On 24/03/11 09:09PM, gromit wrote: > On 24/03/02 12:48PM, gromit wrote: > > I will start dropping packages on 2024-03-17, so please try to have a > > look at the lists in the next few days. > > Reminder: There is one week left until unneeded orphan packages will be > dropped to the AUR. Please have a look at the list again to see if other > people orphaned stuff that may be intersting for you. Hello everyone, I have dropped the unneded orphans as announced earlier. For any interested package maintainers on the AUR (hence the cc to the aur-general list): The packages are now available in the AUR and ready to be adopted, some already have found maintainers :) See the full list below. Cheers, gromit -- ams-lv2 archey3 autocutsel beatslash-lv2 blockdiag cadence deheader deteriorate-lv2 dmg2img eid-mw entityx faudio fluid foxdot fst gambit-c ganv gdlmm gnome-icon-theme-extras gnome-shell-extension-gtile gnubg gnucobol gnupg-pkcs11-scd gob2 gpa gqrx gv hashdeep helm-synth howl htmlhint ibus-m17n ibus-pinyin icecast ir.lv2 junit-system-rules latex2rtf libident liri-calculator liri-cmake-shared liri-files liri-terminal liri-text livewallpaper lockdev lvtk marsyas mdns-scan meterbridge midimsg-lv2 neovim-lsp_signature neovim-nvim-treesitter ninjas2 non-daw non-sequencer notify-sharp-3 osmid pan patchage pc-ble-driver perl-date-simple polyclipping python-apptools python-autodocsumm python-behave python-cx-freeze python-etesync python-git-url-parse python-ipy python-jinja-time python-kaptan python-langdetect python-matrix-nio python-nrfutil python-pc-ble-driver-py python-pdm-pep517 python-piccata python-poyo python-publicsuffix python-pyspinel python-pythonfinder python-schedutils python-tree-format python-webtest-aiohttp python-whichcraft python-yapsy qt5-gsettings razercfg ruby-treetop seqdiag slimit solfege sonic-pi sparkleshare tap-plugins tpacpi-bat ttf-proggy-clean vim-align vim-coverage-highlight vim-editorconfig vim-pastie vocal wake webkit2-sharp weechat-matrix zsh-theme-powerlevel10k signature.asc Description: PGP signature
News draft: Arch Linux Leader Election Results
Hello everyone, a few people have asked for the election results to be published as a News announcement. If you have any feedback regarding the draft below feel free to send it as a response or ping me on IRC. I will post the announcement at the beginning of next week. ^_^ Cheers, gromit === Recently we held our leader election, and the previous Project Leader Levente "anthraxx" Polyák ran again while no other people were nominated for the role. As per [our election rules](https://wiki.archlinux.org/title/DeveloperWiki:Project_Leader#Election) he is re-elected for a new term. The role of of the project lead within Arch Linux is connected to [a few responsibilities](https://wiki.archlinux.org/title/DeveloperWiki:Project_Leader#Roles) regarding decision making (when no consensus can be reached), handling financial matters with SPI and overall project management tasks. **Congratulations to Levente and all the best wishes for another successful term!** === signature.asc Description: PGP signature
Re: AUR Maintenance Saturday 13 July 12:00 UTC
On 24/07/11 12:25PM, Jelle van der Waa wrote: > Hi all, > > We are having some performance issues with the AUR's git repository which > requires some maintenance. [1] > > This means that the AUR will be unavailable for some time starting 12:00 UTC > till it is done (hopefully 2 hours, could be more). > > [1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/599 Hello everyone, the AUR is back up again and we were able to resolve the related issue. signature.asc Description: PGP signature
News draft: Manual intervention for pacman 7.0.0 and local repositories required
Hello everyone, with the move of pacman version 7.0.0 a few changes might require manual intervention from end users, which shall be described in the following news item! If you have feedback to it feel free to reply directly! -- # Manual intervention for pacman 7.0.0 and local repositories required With the release of [version 7.0.0][0] pacman has added support for downloading packages as a separate user with dropped privileges, which we deem a good default for our distribution. For users with local repos however this might imply that the download user does not have access to the files in question, which can be fixed by assigning the files and folder to the "alpm" group. $ chown $USER:alpm -R /path/to/local/repo This is of course only relevant after you have successfully [merged the .pacnew][1] files. Pacman also introduced [a change][2] to improve checksum stability for git repos that utilize .gitattributes files. This might require a one-time checksum change for PKGBUILDs that use git sources. [0]: https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS?ref_type=heads [1]: https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave [2]: https://gitlab.archlinux.org/pacman/pacman/-/commit/9548d6cc765b1a8dcf933e8b1b89d0bcc3e50209 signature.asc Description: PGP signature
Re: Splitting the Arch Linux repo and archive server
On 24/12/27 02:55PM, Kristian Klausen wrote: > Hi all, Hello everyone, > The DevOps team is working on splitting[0] the repo server and the archive > server, which are currently still located on the same box > (gemini.archlinux.org). This reason for splitting it is mainly due to I/O > issues and to ensure separation of concerns. Please see [1] and [2] for a > bit more context. > > We have already ordered the new repo server (AX41-NVMe[3] with an extra 1 TB > NVMe SSD) and switched the rsync endpoint for the mirrors 7 months ago[2], > so now the time has come to move the home of the repos from gemini to the > new repo server. > Christian and I are planning on taking a stab on this in a few hours, during > which the access to the repos will be cut off. We have now successfully finished the maintenance and all services should be reachable again as usual. If you still find things that are amiss please let us know! We still need to fix the archiving setup in the coming days, but the disruptive part of the maintenance work is done. === Information for Packagers === The new repo server has the following host keys, which can also be checked in our [ssh-hostkeys textfile][4]: 256 SHA256:uR8mRzpo828jM6U1jmdBxXvHEiDbuNSwpLur5odBrRA repos.archlinux.org (ECDSA) 256 SHA256:JApvSFU4OvaafW5ebe3ktmlp41WSsOffCkOBvtdNeDU repos.archlinux.org (ED25519) 3072 SHA256:wlSAfyb4o94izuemzbOILFeVPgDZd0Y9n890gq1pyxY repos.archlinux.org (RSA) 256 MD5:55:ee:72:27:c3:9d:f0:c3:89:b4:24:ff:75:dd:60:bf repos.archlinux.org (ECDSA) 256 MD5:90:98:6c:ee:72:b5:a6:dc:bf:ae:12:39:2e:99:b2:c4 repos.archlinux.org (ED25519) 3072 MD5:48:53:1e:51:81:7f:40:fd:ee:7c:dc:06:7c:98:a3:9e repos.archlinux.org (RSA) === Information for Mirror Admins === The rsync deamon is active again and mirroring should continue as usual! Cheers, Kristian and Christian [4]: https://gitlab.archlinux.org/archlinux/infrastructure/-/blob/master/docs/ssh-hostkeys.txt?ref_type=heads signature.asc Description: PGP signature
Re: News draft: glibc 2.41 breaks Discord
On 25/02/02 02:43PM, Frederik Schwan wrote: > Hi everyone, Hello 👋 > as discussed in the Matrix packaging channel, the upcoming glibc move > from testing to stable will break audio connectivity for Discord > clients. Discord has fixed the issue in their canary build and has > communicated an eta for the fix in stable for 2025-02-10. As the glibc > update holds off package moves from testing to stable I would like to > continue releasing the toolchain and give everyone instructions on how > to fix their Discord installation. I'm still not a big fan of us knowingly breaking such a commonly used software, but yeah being stuck for yet another week with the glibc upgrade and kernel in testing because of a proprietary app also sounds bad so let's do it as you proposed. > # Glibc 2.41 corrupting Discord installation > > Glibc and it's friends will move from testing to stable on approx. > 2025-02-03. After installing the update, the Discord client will show > a read warning that the installation is corrupt. > > This issue has been fixed in the Discord canary build. Until the fix > hits the stable Discord release, please use the canary build or login > via browser if you rely on audio connectivity. There have been no > reports that (written) chat connectivity is affected. I think we could also more clearly adivise people to just not upgrade their system until we have also shipped the fixed discord version, as this is the most simple solution to the problem. > Best regards, > Frederik Cheers, gromit
Highlights in the devtools 1.3.0 release
Hello everyone, as we got the feedback on the Arch Linux Summit that not everyone is aware about all the new shiny things in devtools, we wanted to give a small overview about the latest developments. Apart from this effort every release has an easily digestable changelog attached (see [0] as example for 1.3.0), so if you want to stay up to date you can also follow the releases on the Gitlab repo or check the previous release notes for additional gems! # 🚀 Highlights in the 1.3.0 release 🚀 ## ✨ The 'pkgctl issue' subcommands Now all the functionality needed to work with issues is availiable directly on the commandline via pkgctl. A regular packager workflow might look something like this: Check open issues: $ pkgctl issue list --assigned-to-me --group Check details about an issue: $ pkgctl issue view --package linux 97 $ pkgctl issue view --package linux --web 97 $ pkgctl issue view --package linux --comments 97 React to the issue: $ pkgctl issue close --package linux --edit 97 $ pkgctl issue comment --package linux 97 There are way more options and things to do, but feel free to explore on you're own! ➡ Contributed by @anthraxx in [MR!255][1] 🎉 ## 🚧 Fixes to 'offload-build' There was a major refactoring effort for offload-build, which has the very neat consequence that the --inspect argument can now be used in combination with pkgctl build's --offload so that remote builds can be debugged more easily. ➡ Contributed by @lahwaacz in [MR!234][2] 🎉 ## 📦 nvchecker related changes - For packages without an upstream one can now create a special config: $ pkgctl version setup --no-upstream This is thought to be only used with packages that do not have a canonical upstream, like metapackages. If you have trouble setting up nvchecker integration for the more complicated packages feel free to get in touch! - On release there now is a warning when a package repository does not have a '.nvchecker.toml' - We no offer a way to retrieve machine-readable output from pktctl version check: $ pkgctl version check --json * ➡ Contributed by @antiz, @segaja and @anthraxx in [MR!273][3], [MR!275][4] and [MR!286][5] 🎉 --- Apart from the big changes/improvements there are of course a lot of minor bug fixes, documentation improvements and smaller features included. Thanks for everyone that helped to discuss & improve features! 🎉 Cheers, anthraxx & gromit [0]: https://gitlab.archlinux.org/archlinux/devtools/-/releases/v1.3.0 [1]: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/255 [2]: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/234 [3]: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/273 [4]: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/275 [5]: https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/286 signature.asc Description: PGP signature
Re: Standardize on running autoreconf in prepare()
On 25/02/26 09:53PM, Jelle van der Waa wrote: > Hi All, Heyhey, > After all the recent RISC-V news I went ahead and checked out the existing > effort to get Arch Linux supported on RISC-V. Felix maintains an overlay of > PKGBUILDs which require customization to be be able to build on RISC-V. A > lot of these PKGBUILD's patch autotools projects to run `autoreconf -fiv` in > prepare(), this re-generates `configure` to understand RISC-V. > > Since these patches are simple enough and I don't see them harming Arch > Linux, I would argue that we want these patches applied in our packages. > Re-generating configure should not break, and if it does we should not > accept the patch and get a bug filled upstream. > > Re-creating configure and thus not using the provided `configure` could > arguably also be a good thing regarding supply chain security. And this also > should help with other architecture ports. Sounds like a good idea, +1 from me! > As a follow up we can discuss providing our own "/usr/share/config.site" and > then ./configure --prefix=/usr would automatically configure localstatedir, > libexecdir, etc. > > [1] https://github.com/felixonmars/archriscv-packages > [2] > https://github.com/felixonmars/archriscv-packages/blob/master/libafterimage/riscv64.patch Cheers, chris signature.asc Description: PGP signature
Re: Spring cleanup '25
On 25/03/22 11:50AM, Antonio Rojas wrote: > Time to clean up old cruft again. Please head to > https://archlinux.org/devel/reports/unneeded-orphans/ and adopt packages you > want to keep in the repos. For reference, a current list of packages is > attached (but this may vary if packages are adopted/disowned). If you adopt a > package from the list, make sure to check its dependencies and also adopt > them in case they are orphan. > > This is also a good time to check your out-of-date packages and disown the > ones you no longer have interest in/time to maintain, so they can find a > maintainer in the official repos or otherwise in AUR. Keeping packages out of > date and/or with unfixed issues for months/years is not ideal and can be > detrimental to the overall quality of our distro in the long run. I have now also orphaned the packages from farseerfc, see the full list below. Not all of these are unnededed orphans , but it might still make sense to look at all of them since some may need new maintainers to retain a bus factor > 1 :D - alacritty - btrfs-heatmap - dbus-client-gen - fcitx5-mozc - fcitx-mozc - fira-code - flameshot - jlatexmath - kdiskmark - libfilteraudio - libtg_owt - lsw - lzip - otf-ipaexfont - otf-ipafont - otf-ipamjfont - pdfpc - pelican - plantuml - plantuml-ascii-math - powerline - python-btrfs - python-cairocffi - python-dbus-client-gen - python-dbus-signature-pyparsing - python-feedgenerator - python-ghp-import - python-hs-dbus-signature - python-into-dbus - python-justbases - python-justbytes - python-markdown-math - python-mdx-video - python-pdfrw - python-smartypants - python-typogrify - qtox - retext - skk-jisyo - snorenotify - stratis-cli - stratisd - telegram-desktop - toxcore - toxic - ttf-hanazono - ttf-opensans - tuntox - utox - xfsdump Cheers, gromit signature.asc Description: PGP signature
