September 2023 - Aur-general - lists.archlinux.org

Help with AUR
by Xavier Baez 04 Sep '23

04 Sep '23

Hello I would like the community to help and decide on what to do. I am the maintainer of motivewave There is a person that went and created a duplicate motivewave-latest-bin and went and publicly said I am incompetent and insinuated I was stupid. Even today, labor day, when I want to spend time with my 3 kids, I have to be on the computer basically doing code review. During the last 12 days, the package has 1) always compiled and built Now, I was recommended to make some changes source=("${pkgname}-${pkgver}.deb:: https://downloads.motivewave.com/builds/${build_id}/motivewave${pkgver}_amd… ") then: makepkg --printsrcinfo > .SRCINFO But that would break my package. I found a solution with a custom variable, but 1) The other package is not being deleted: motivewave-latest-bin 2) My package is being basically spammed. 3) I am call the spammer I would like the community to let me know if someone recommends you to add code, and the code doesn't work, then why is there a pushover from Xiota to orphan the package. I have also received threads to have my account suspended/deleted but I wake up today at 3:00 AM my phone is beeping again because the person that copied the package, Xiota, cannot stop. -- Regards Xavier

3 2

[PATCH][tu-bylaws] bylaw amendments: switch to gitlab merge requests
by Christian Heusel 04 Sep '23

04 Sep '23

Most of our worflows have moved from mailing lists and patches to merge requests on gitlab. Until now amending the TU Bylaws formally requires sending patches via mail which this amendment intends to replace with merge requests on the gitlab repository. Signed-off-by: Christian Heusel <christian(a)heusel.eu> --- tu-bylaws.adoc | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/tu-bylaws.adoc b/tu-bylaws.adoc index 376d909..70a8a27 100644 --- a/tu-bylaws.adoc +++ b/tu-bylaws.adoc @@ -170,21 +170,10 @@ These bylaws may be amended at any time. A TU must motion for an amendment by sending an announcement to https://mailman.archlinux.org/mailman/listinfo/aur-general[aur-general]. -The message must either contain, or have attached, a Git-formatted patch -against this document which accomplishes the suggested change. The patch should -be based on the master branch of the official -https://gitlab.archlinux.org/archlinux/tu-bylaws.git/[tu-bylaws repository] and should -be sent "inline" (i.e. using `git send-email`) so that other TUs can easily -comment on specific parts. The strings `[PATCH]` and `[tu-bylaws]` should be -included in the subject. `git send-email --annotate` can be used to edit a -patch before sending it to the mailing list. - -Sending multiple patches is generally discouraged and should only be done if no -more than one of the patches are subject for debate (the remaining patches -might be formatting changes or minor wording changes). If multiple patches are -sent as part of one proposal, a cover letter describing the changes must be -included. The `--cover-letter` option of `git send-email` can be used to -achieve this. +The message must contain a link to a merge reqest in the official +https://gitlab.archlinux.org/archlinux/tu-bylaws[tu-bylaws repository] and the +merge request description should contain a meaningful description and +motivation for the change. SVP is commenced at the time of the motion, with a discussion period of 5 days, a quorum of 75%, and a voting period of 7 days. -- 2.42.0

4 12

application as package maintainer - fabiscafe
by Fabian Bornschein 02 Sep '23

02 Sep '23

Hey everyone! My name is Fabian Bornschein, I'm an IT-service-technician from germany and I would like to join the group of package maintainers. Let's start with the lengthy and less exciting parts of my Linux journey. My first Arch installation took place around 2010. I believe it was due to the fact that the other Linux distribution wasn't functioning properly on my new laptop. A few months later, I switched to Kubuntu and stuck with it for several years. During that time, I was heavily involved in designing various components for KDE Plasma such as themes, icons, and more. Thanks to this work and some contributions[0], I was invited to become a founding member of the KDE Visual Design Group[1]. Unfortunately, I didn't contribute much during my time there before eventually moving on. So, around 2015/16-ish, I found my way back to Arch, just to jump ship yet again over to (oh no!) Manjaro. After some time, lots of talks and small contributions, I ended up as the go-to person for maintaining the Radeon+AMDGPU[2]/FGLRX[3] setup scripts. Later on, I took charge of all those setup scripts for open-source drivers through "mhwd". Another project that kept me busy was my re-do of Manjaro's Steam client[4]. In late 2017 or early 2018, I left Manjaro and returned to Arch. However, to this day, I'm still the creator and owner of the Manjaro (Community) Telegram group[5] :P Now that I'm back on Arch, I do help people on various platforms, such as Fedi/Mastodon, Matrix, and Telegram. You can find me using my 'fabiscafe' alias. In the last 2-3 years, I've been working on another project: FCGU. It's an Arch Linux repo for GNOME pre-releases[6]. I started it because testing GNOME pre-releases on Arch was tough, and the AUR wasn't suitable for something as big as GNOME. What began as a personal venture grew when others wanted to test it too. I reached out to find some people who wanted to provide mirrors, and now it's a thing! :) The PKGBUILDs are nowadays on Arch gitlab[7]. In my rare spare time, I try to relax, spend time with family, or simply be with friends. I enjoy Anime/Manga and, of course, a good cup of coffee \o/. So, what do I want to do for Arch? Essentially, it's pretty much the same as what I'm currently doing for FCGU. Jan Alexander Steffens (heftig) asked me (twice already, sorry about that) if I'm willing to help with GNOME in Arch and if I'd like to incorporate the FCGU work into gnome-unstable. I believe it would benefit everyone if Arch could provide official unstable releases of GNOME in a repository. On the flip side, this might also speed up the availability of new stable releases on Arch - and thus, potentially reduce user spam on Reddit. :D So, in a nutshell, I want to: - Offer GNOME unstable releases (beta, rc) in gnome-unstable - Assist in transitioning them to Arch once they become stable versions My sponsors are Jan Alexander Steffens (heftig) and Torsten Keßler (tpkessler). Many thanks to both of you! Now I hope the Manjaro stuff doesn't exclude me directly and thanks for reading all of this. :) Fabian Bornschein - fabiscafe [0] https://jgrulich.cz/2014/02/27/plasma-nm-is-finally-out/ [1] https://wheeldesign.blogspot.com/2014/01/the-visual-design-group-short-intr… [2] https://github.com/manjaro/mhwd-db/commit/2bc57fddcc081ded1d3d701b83f6e7029… [3] https://github.com/manjaro/packages-extra/commit/b867bd3c26f4f3672889d1deac… [4] https://github.com/manjaro/packages-community/pull/252 [5] https://t.me/Manjaro [6] https://codeberg.org/fabiscafe/fcgu [7] https://gitlab.archlinux.org/fabiscafe [aur] https://aur.archlinux.org/account/fabiscafe

5 8

Re: Waterfox G
by Aaron Liu 01 Sep '23

01 Sep '23

Oops, I've sent this to the arch-general mailing list instead! I meant to send this to aur-general, sorry. I guess forwarding it should be fine. On 9/1/23 15:15, Aaron Liu wrote: > Currently, there are 2 packages for the latest Waterfox "current": > waterfox-g-bin and waterfox-current-bin . > > My guess is as follows: This arose from Waterfox changing their > versions from "current" to "G", short for "generation". hawkeye116477, > the maintainer for the former package and former maintainer for the > latter package, decided to create a new package, waterfox-g-bin, for > later releases and keep waterfox-current-bin frozen at the last > release with "current". However, MarsSeed orphaned > waterfox-current-bin through [PRQ#42365] in June and Leo Izen claimed > it and updated it to the latest Waterfox G. > > The current situation is that Waterfox refers to "Waterfox G" as > simply "Waterfox" and both bin packages have the wrong name. What > should be done? > > Also, is it necessary to have both gtk3 and gtk2 as > dependencies? Looking at the PKGBUILDs the only difference between the > packages is waterfox-g-bin disables automatic updates + update > notifications and has the extra profile manager desktop action while > waterfox-current-bin has none of these and has the extra dependency > "nss" (is this necessary?) > > P.S.: I've Bcc'd everybody I've named in this email. I'm new to the > AUR, so tell me if that's not the right thing to do. >

1 0