Mailing lists matching lists.archlinux.org
arch-commits lists.archlinux.orgarch-dev-public lists.archlinux.org
arch-mirrors lists.archlinux.org
aur-general lists.archlinux.org
aur-requests lists.archlinux.org
...
Re: [arch-general] update error(?)
Okay . . . Thank you for the input. May I just state that I can (and do) use all of the information resources aforementioned. Oh, if you only knew the may hours I have spent reading, reading, reading. Yes, I have learned much from reading. But reading is not always the most efficient or even the most effective learning modality. Often, just asking questions is the best way to promote knowledge transfer. Having said that, in the interest of avoiding the potential of adverse sentiment, perhaps further discussion on this point might better be taken "off-list"? Now regarding mailing lists, I believe this is the collection of official Arch (publically available) mailing lists: *List* *Description* *arch-announce* <https://lists.archlinux.org/listinfo/arch-announce> Arch Linux Announcements *arch-commits* <https://lists.archlinux.org/listinfo/arch-commits> Arch Linux packaging commits *arch-dev-public* <https://lists.archlinux.org/listinfo/arch-dev-public> Public mailing list for Arch Linux development *arch-events* <https://lists.archlinux.org/listinfo/arch-events> Arch Linux Events *arch-general* <https://lists.archlinux.org/listinfo/arch-general> General Discussion about Arch Linux *arch-mirrors* <https://lists.archlinux.org/listinfo/arch-mirrors> Arch Linux Mirroring Discussion and Announcements *arch-multilib* <https://lists.archlinux.org/listinfo/arch-multilib> Arch Linux Multilib (32bit libs on 64bit OSes) *arch-ports* <https://lists.archlinux.org/listinfo/arch-ports> Discussion regarding the porting of Arch Linux to non-i686 architectures *arch-projects* <https://lists.archlinux.org/listinfo/arch-projects> Arch Linux projects development discussion *arch-releng* <https://lists.archlinux.org/listinfo/arch-releng> Arch Linux Release Engineering *arch-security* <https://lists.archlinux.org/listinfo/arch-security> Discussion about security issues in Arch Linux and its packages *arch-women* <https://lists.archlinux.org/listinfo/arch-women> Mailing list for the Arch Women project *aur-dev* <https://lists.archlinux.org/listinfo/aur-dev> Arch User Repository (AUR) Development *aur-general* <https://lists.archlinux.org/listinfo/aur-general> Discussion about the Arch User Repository (AUR) *aur-requests* <https://lists.archlinux.org/listinfo/aur-requests> Public mailing list for AUR package deletion/merge/orphan requests *pacman-dev* <https://lists.archlinux.org/listinfo/pacman-dev> Discussion list for pacman development -- After carefully reviewing it, I have not yet found a list more suitable to my limited capabilities, such as: arch-newb...@archlinux.org or arch-for-the-cognitively-challen...@archlinux.org So, for now, all I can do is: - keep looking - keep reading - keep asking Cheers! On Mon, Apr 20, 2015 at 3:43 PM, Aaron Caffrey wrote: > Hello Francis, > > In archlinux you have to rely on the wiki, man pages and info documents > more often than you do in the mail list, as a lot the wiki pages there are > written by people that have dedicated a lot of their free time to write > the provided information correctly and well explained, also they make sure > that most of the pages are up to date. > > A quick 5-10 minutes web research would nail almost all of your future > quirks. And if you can't, feel free to submit a new message to the > mail list as there are always nerds around that would help you out. > > Best regards, > Aaron Caffrey >
[aur-requests] [PRQ#27743] Deletion Request for repoos
FabioLolix [1] filed a deletion request for repoos [2]: This is a 'group package' there are 5 different unrelated programs, while this could be solved by making 5 different pkgbuilds, these programs are made by Wayne Wesley also known as TheCynicalLiger, The- Repo-Club, TheCynicalTeam and have a habit stealing and license washing other people's code * https://github.com/dylanaraps/neofetch/issues/1811 * https://lists.archlinux.org/pipermail/aur- requests/2021-July/056462.html * https://lists.archlinux.org/pipermail/aur- requests/2021-July/055898.html * https://lists.archlinux.org/pipermail/aur- requests/2021-July/055899.html * https://lists.archlinux.org/pipermail/aur- requests/2021-July/056462.html * https://lists.archlinux.org/pipermail/aur- requests/2021-July/055952.html * https://lists.archlinux.org/pipermail/aur- requests/2021-July/056425.html [1] https://aur.archlinux.org/account/FabioLolix/ [2] https://aur.archlinux.org/pkgbase/repoos/
[arch-general] https://lists.archlinux.org/
Hi, mails to mail...@lists.archlinux.org [1] are rejected. I try to get in contact with the owner of one list, but don't get a reply. Regards, Ralf [1] "If you are having trouble using the lists, please contact mail...@lists.archlinux.org." - https://lists.archlinux.org/
[PRQ#45680] Deletion Request for tlauncher-org
FabioLolix [1] filed a deletion request for tlauncher-org [2]: Already deleted once for safety concerns, see [PRQ#39110] https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/ID2UXSU7MOH7N36YAW5T2KQUPYJ4RAH3/ https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/PG5UEOSXVHONLBPI4ZEPM3W62L2DLKOX/ [1] https://aur.archlinux.org/account/FabioLolix/ [2] https://aur.archlinux.org/pkgbase/tlauncher-org/
[PRQ#64212] Deletion Request for josm-stable
Freso [1] filed a deletion request for josm-stable [2]: josm-stable is (still) [extra]/josm See also: PRQ#40147 [1] PRQ#60082 [2] [1] https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/YDWQFANBTUXXUA2RGE5V5DAFYSAXLNUU/ [2] https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/OWACFKEUQIZTS64B2EXWYDBCPOKGM7N6/ [1] https://aur.archlinux.org/account/Freso/ [2] https://aur.archlinux.org/pkgbase/josm-stable/
Re: About user MarsSeed's script-like mass requests
Hi there I won't enter into all the discussion details but an explicit accusation needs be cleared: However there is a lot to be said with the response time of legitimate requests, it does seem like MarsSeed has priority, I have seen their requests be handle very quickly, while others wait for months and get caught in the backlog. This is a 100% false argument: there are so many requests to process, most of them made by MarsSeed, so it's obvious most of the responses are relative to MarsSeed requests. Also what happened the day before this discussion started, seemed to demonstrate the exact opposite: [1] [2] [3] [4] [5] [6] [7] I repeat, this could seem we give priority to 7Ji (which is the OP of this whole discussion), but I confirm this is simply a matter of luck and package maintainership (see below). Also some of MarsSeed's requests are being rejected after evaluation if the reasons are not enough to accept. Archives are public for anyone. Requests made by the package maintainers (as the previous 7 indicated before) are processed quicker as the package's maintainer should know better the state of the package he's filing requests for. Also, I tend to give priority to orphan requests, as someone else is awaiting to fix packages issues, so giving priority to these requests the packages will be fixed quicker. So, please, Polarian, don't discredit the staff members and respect the work done which is sometimes very heavy and tiring and wasting my time in explaining how the things are is more time I have subtract. I found this your accusation very rude and ungrateful, I hope it was done in good faith, not thinking enough (you never contacted me to asking such details). Having said this, actually we have more than 3000 pending requests, so it's impossible to remember who is awaiting in the queue. Whenever his turn comes the request will be processed like for anyone else. In the 98% of the times, a request is accepted or rejected. The remaining cases are awaiting for requester or maintainer answer. In some rare cases (less than 1 of 100) if I don't understand the issue or I'm unable to understand how the things are I leave the package request to someone else. Also each PM does evaluate the requests by interpreting what the requester wrote, so a clearer explanation in the requests could give better result and quicker response time. I don't even care about the names in the requests, seriously. Incomplete requests, duplicated packages to fix an original package issue (X package is buggy, this Y package of mine fixes that, please merge), at the contrary require more time and sometimes the answers I need to have before processing the request, never come, thus burdening the request in an eternal oblivion. MarsSeed requests are often, so far, the most precise, clear, well explained, with external links and frequently updated with additional details. People should instead learn from his way to report packages. Also, PMs do mistakes, so in the case some wrong thing happens, please contact the PM and ask for a revision or clarification. Best regards [1] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/IRV2H2S7U3DYF4NHYIQBNUNJRGVYWZCC/ [2] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/RJVR2H4XWAHGUIZ53STHOYGYBUMNYUBB/ [3] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/J4E7L5XHG4YGE6WKM3BBWRHYPD3CFGR3/ [4] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/5RKQWGAJB4BZWYEEPTHDT7G7U2KXY7EF/ [5] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/PZUQY7CQR4ZZ76TREOGFIDSK7Y27DKHG/ [6] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/O4G7IFD534NLRJ6ENVZLJHWATQBMAAZ6/ [7] https://lists.archlinux.org/hyperkitty/list/aur-reque...@lists.archlinux.org/thread/VZZGBE346UUNP2TSRP4R5MBDKLOP7OWB/ -- Fabio Castelli aka Muflone
Re: [arch-events] Fwd: Arch Linux Conference Online 2021
Sorry for misunderstanding On Tue, Apr 27, 2021 at 11:16 AM Morten Linderud via arch-events < arch-events@lists.archlinux.org> wrote: > On Tue, Apr 27, 2021 at 11:02:01AM +0200, Luna Jernberg via arch-events > wrote: > > Hello! > > > > There will be no Online Arch Conf this year > > Well, that isn't what I have written on IRC! > > What I said is that I'm personally not going to organize anything and > would much > rather spend my time planning an in-person meetup for next year. I'd > completely > help and support anyone that want to pull off an online conference for > 2021 :) > > Cheers! > > -- > Morten Linderud > PGP: 9C02FF419FECBE16 > ___________ > arch-events mailing list > arch-events@lists.archlinux.org > https://lists.archlinux.org/listinfo/arch-events > ___ arch-events mailing list arch-events@lists.archlinux.org https://lists.archlinux.org/listinfo/arch-events
[PRQ#53365] Deletion Request for python2-backports.shutil_get_terminal_size
MarsSeed [1] filed a deletion request for python2-backports.shutil_get_terminal_size [2]: This has already been deleted twice in response to: - PRQ#30859 (2021-12-18) [a] - PRQ#48185 (2023-09-29) [b] Now it got recreated dead-on-arrival, failing the integrity check. This is very typical with submitter Pellegrino Prevete's packages (who is both @tallero and @truocolo) He is prone to pushing broken commits to AUR repos. Reverse dependency ipython2 has been dead on AUR since 2021, and already got deleted once: - PRQ#31463 (2022-01-12) [c] It does not make sense to keep either packages, as no user commented throughout the AUR existence of either, apart from him and me in the last few days. As per AUR submission guidelines, packages kept here should be in demand by more than a few users. These broken builds clearly don't hit that particular bar. [a]: http://tinyurl.com/aurPRQ30859 / Full URL: https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/S236DZWKIDSSC23J7KHMVVCFBZ2D6FQB [b]: http://tinyurl.com/aurPRQ48185 / Full URL: https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/MO53FSYNYBSYBDUXENSO4IGWA5A7JK33 [c]: http://tinyurl.com/aurPRQ31463 / Full URL: https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/DQCDU4ENTVC6HDQAV5YVCY6ZSDUZO3QR [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/python2-backports.shutil_get_terminal_size/
Re: Proposal to increase the default vm.max_map_count value
On April 1, 2024 12:09:47 PM UTC, Robin Candau wrote: On 3/25/24 9:10 AM, Robin Candau wrote: Hi everyone, I'm writing this mail as proposal to increase the default `vm.max_map_count` value in Arch Linux. It's been a week since this proposal thread [1] was made. For now it only received a few but all positives feedback (both from staff members and users in a related thread on arch-general [2]). Do we have any more thoughts anyone wants to share? Also, if we are to implement this change, anyone has an opinion about which package should provide it? So far, the following packages have been mentioned: - systemd (as Fedora did) - procps-ng (as Ubuntu did) - filesystem Given that the proposal goes through, I'll create the MR to the chosen package accordingly. Also, despite this change being impact-free (as far as we can tell), I think a related news item to inform users about this change would be a great idea (I'll write that as well). Please, share your opinion about the change itself or the best package to provide it if you have any :) [1] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/ <https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/> [2] https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/ <https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/> On 4/1/24 11:11 PM, Ehalls wrote: I would keep it out of systemd. Do you think it is the approproate place? (Copying the above response I received from someone off-list, as it is staff only) Since the change consists of shipping a sysctl file and that sysctl is provided by procps-ng, I personally think procps-ng is the appropriate place. -- Regards, Robin Candau / Antiz OpenPGP_0xFDC3040B92ACA748.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Aur-requests Digest, Vol 13, Issue 98
UnSub Pada tanggal Jum, 15 Sep 2023 17.19, < aur-requests-requ...@lists.archlinux.org> menulis: > Send Aur-requests mailing list submissions to > aur-requests@lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > aur-requests-requ...@lists.archlinux.org > > You can reach the person managing the list at > aur-requests-ow...@lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aur-requests digest..." > > Today's Topics: > >1. [PRQ#47312] Orphan Request for godot-mono-git > (not...@aur.archlinux.org) >2. [PRQ#47313] Deletion Request for protobuf2-c > (not...@aur.archlinux.org) >3. [PRQ#46795] Deletion Request for niacop-git Accepted > (not...@aur.archlinux.org) >4. [PRQ#46800] Merge Request for libfprint-tudor Accepted > (not...@aur.archlinux.org) >5. [PRQ#46810] Deletion Request for amgx Accepted > (not...@aur.archlinux.org) >6. [PRQ#46811] Merge Request for opentrace Accepted > (not...@aur.archlinux.org) >7. [PRQ#47314] Deletion Request for tenshi-rs > (not...@aur.archlinux.org) > > > -- > > Message: 1 > Date: Fri, 15 Sep 2023 09:53:34 + > From: not...@aur.archlinux.org > Subject: [PRQ#47312] Orphan Request for godot-mono-git > To: aur-requests@lists.archlinux.org > Cc: fabio.l...@disroot.org, tasg...@outlook.com > Message-ID: > Content-Type: text/plain; charset="utf-8" > > FabioLolix [1] filed an orphan request for godot-mono-git [2]: > > Need a good revision as mentioned in comments and OOD flag, flagged > OOD for 1+ year > > [1] https://aur.archlinux.org/account/FabioLolix/ > [2] https://aur.archlinux.org/pkgbase/godot-mono-git/ > > ------ > > Message: 2 > Date: Fri, 15 Sep 2023 09:55:43 + > From: not...@aur.archlinux.org > Subject: [PRQ#47313] Deletion Request for protobuf2-c > To: aur-requests@lists.archlinux.org > Cc: davvor...@gmail.com, marcell.mesza...@runbox.eu > Message-ID: > Content-Type: text/plain; charset="utf-8" > > MarsSeed [1] filed a deletion request for protobuf2-c [2]: > > Abandoned, broken PKGBUILD from 2018. > Missing a dependency, source 404. > > [1] https://aur.archlinux.org/account/MarsSeed/ > [2] https://aur.archlinux.org/pkgbase/protobuf2-c/ > > -- > > Message: 3 > Date: Fri, 15 Sep 2023 09:55:52 + > From: not...@aur.archlinux.org > Subject: [PRQ#46795] Deletion Request for niacop-git Accepted > To: aur-requests@lists.archlinux.org > Message-ID: <20230915095552.4dbf75af9...@aur.archlinux.org> > Content-Type: text/plain; charset="utf-8" > > Request #46795 has been Accepted by Antiz [1]: > > [Autogenerated] Accepted deletion for niacop-git. > > [1] https://aur.archlinux.org/account/Antiz/ > > -- > > Message: 4 > Date: Fri, 15 Sep 2023 10:03:45 + > From: not...@aur.archlinux.org > Subject: [PRQ#46800] Merge Request for libfprint-tudor Accepted > To: aur-requests@lists.archlinux.org > Cc: 27stopi...@gmail.com > Message-ID: <20230915100345.0c3975af9...@aur.archlinux.org> > Content-Type: text/plain; charset="utf-8" > > Request #46800 has been Accepted by Antiz [1]: > > [Autogenerated] Accepted merge for libfprint-tudor into > libfprint-2-tod1-synatudor-git. > > [1] https://aur.archlinux.org/account/Antiz/ > > -- > > Message: 5 > Date: Fri, 15 Sep 2023 10:06:41 + > From: not...@aur.archlinux.org > Subject: [PRQ#46810] Deletion Request for amgx Accepted > To: aur-requests@lists.archlinux.org > Message-ID: <20230915100641.422fa5afa...@aur.archlinux.org> > Content-Type: text/plain; charset="utf-8" > > Request #46810 has been Accepted by Antiz [1]: > > [Autogenerated] Accepted deletion for amgx. > > [1] https://aur.archlinux.org/account/Antiz/ > > -- > > Message: 6 > Date: Fri, 15 Sep 2023 10:07:11 + > From: not...@aur.archlinux.org > Subject: [PRQ#46811] Merge Request for opentrace Accepted > To: aur-requests@lists.archlinux.org > Cc: archlinux-arc...@gfw.moe > Message-ID: <20230915100711.01b0b5afa...@aur.archlinux.org> > Content-Type: text/plain; charset="utf-8" > > Request #46811 has been Accepted by Antiz [1]: > > [Autogenerated] Accepted merge for opentrace into opentrace-bin. > > [1] https://aur.archlinux.org/account/Antiz/ > >
[PRQ#37616] Orphan Request for linux-vfio
eclairevoyant [1] filed an orphan request for linux-vfio [2]: I've already reached out to the maintainers via email, offering to maintain or co-maintain the package myself, and have received no response. Additionally, it seems that the current maintainers have regularly missed maintainenance of this package - see https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/TS6UOSRIXLD6K2COUYPKKLL422ZUJ3RZ/ (Feb 2020) and https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/F4JKOMR4FLK56CY2AMBIMOLRKCLDWMA5/ (Oct 2021) [1] https://aur.archlinux.org/account/eclairevoyant/ [2] https://aur.archlinux.org/pkgbase/linux-vfio/
Sockpuppet accounts (was: Toxic user activity on AUR and ArchWikiCN)
Hi all, Leaving aside the technical dispute for a moment, the accounts Cinnamon, Xfce, i3WM, and Hyprland are obviously sockpuppets that have been used for nothing but spamming deletion requests. These accounts should be swiftly blocked. Their deletion requests [6] [7] [8] [9] [10] should be disregarded and closed. I think that zero tolerance should be afforded to users who obviously create sockpuppets so they can file multiple deletion requests. Not only is sockpuppetry in violation of the CoC [1] [2], I also think such accounts should be blocked swiftly to protect AUR staff and to deter other users from doing the same. According to aur-requests [3], there are currently eight pending deletion requests for wechat. Among those eight deletion PRQs, five PRQs were filed within two to four minutes of each other [6] [7] [8] [9] [10], using AUR accounts all created on the same day (2024-12-26), at a time when the dispute in the package comments section was already ongoing. **This pattern cannot be explained by coincidence.** One and the same actor, or group of actors, must have used those five accounts (Cinnamon, davy0710, Xfce, i3WM, and Hyprland) as sockpuppets so they can file multiple requests. Only one of those five has been blocked or deleted. I suggest that the four remaining accounts involved (Cinnamon, Xfce, i3WM, and Hyprland) be blocked indefinitely and that their five deletion requests [6] [7] [8] [9] [10] be disregarded and closed. For the remaining three deletion requests [4] [5] [11], I’d prefer to err on the side of caution. Those three accounts could be active users, who may have filed their deletion requests in (semi-)good faith, even though their timing seems a little unfortunate. Just for reference, here’s the exact timeline of the eight deletion requests: - On Dec. 31, 2024, 12:42 a.m., AUR user unn, a four-months-old account, possibly a genuinely active user, files PRQ#68185 [4]. - Six minutes later, AUR user zhaojian, a seven-days-old account, which may or may not be a sockpuppet, files PRQ#68186 [5]. (OP has stated that zhaojian has also filed abusive out-of-date notifications but I can’t confirm that independently so I’d rather err on the side of caution.) - About five hours after that, AUR user Cinnamon, one of a number of accounts with a similar pattern, files PRQ#68192 [6]. The account Cinnamon is definitely a sockpuppet. - Three minutes later, AUR user davy0710, definitely a sockpuppet, files PRQ#68193 [7]. The account no longer exists. - Another three minutes later, AUR user Xfce, definitely a sockpuppet, files PRQ#68194 [8]. - Four minutes later, AUR user i3WM, definitely a sockpuppet, files PRQ#68195 [9]. - Two minutes later, AUR user Hyprland, definitely a sockpuppet, files PRQ#68196 [10]. - About three hours after that, AUR user Keep-Silence files PRQ#68199 [11]. The account is five-weeks-old, maintains a single package, and has commented on other packages as well. This account may be a genuine user. [1]: https://terms.archlinux.org/docs/code-of-conduct/#spamadvertisingsolicitation [2]: https://terms.archlinux.org/docs/code-of-conduct/#sockpuppetry [3]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/latest [4]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/SHXYY5KDCQLTWV6FFF3UCTEUC6SAH4KX/ [5]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/5ZLHMFNHJWUP4HQZH6ZHGWQLLVBAZKIP/ [6]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/XF3CMCQQRRTKHBOMJBDA75JVMNHKLMOG/ [7]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/R4RUM6YYFT5XKLAATTWTHKAQLJZTSGKQ/ [8]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/2UP7Y2USKVNAF4IWB7R6TKSLFSUDFQTT/ [9]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/MOTEOZJEZUC2BU6OZCCAXEK353FVOUSX/ [10]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/NUQKWV4BZDGQDBOVY7SV6TROO7M5PWZQ/ Regards Claudia (aka Auerhuhn) On 31.12.24 7:18 AM, Kimiblock Moe wrote: Hi, Recently after the merge of wechat-bin, numerous hostile actions has been taken by some users. I’d request some actions taken against them. The users are listed as follows: etoyz: Hostile and bad language in AUR comment[a] intentionally misleading other users to disregard the fact that dependencies should better be complete and wechat (formally wechat-uos-bwrap) is partially duplicated by wechat-universal-bwrap. He then suspiciously changes the Chinese ArchWiki[b] and destroyed the wiki’s context. In his questionable merge request, he ignored the fact that universal bwrap lacks dbus proxy and call it “more reasonably”. gnome: Harassment to the maintainers and their relatives[c]. davy0508: Harassment in a comment[d]. unn: Toxic words in PRQ#68185. zhaojian: Trolling by filing fake out
Re: [PRQ#41675] Deletion Request for mangohud
@serebit: It would help if you actually add it to the extra repo before deleting it. Also, I do not appreciate you sloppifying the PKGBUILD and ignoring VCS package guidelines for submodules. I spent a lot of time on this package doing it right. Sent with Proton Mail secure email. --- Original Message --- On Saturday, May 27th, 2023 at 1:55 PM, aur-requests-requ...@lists.archlinux.org wrote: > Send Aur-requests mailing list submissions to > aur-requests@lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > aur-requests-requ...@lists.archlinux.org > > You can reach the person managing the list at > aur-requests-ow...@lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aur-requests digest..."Today's Topics: > > 1. [PRQ#41615] Deletion Request for booth Accepted > (not...@aur.archlinux.org) > 2. [PRQ#41412] Deletion Request for rstudio-bin Rejected > (not...@aur.archlinux.org) > 3. [PRQ#41411] Orphan Request for owncast Accepted > (not...@aur.archlinux.org) > 4. [PRQ#41674] Deletion Request for googleplay > (not...@aur.archlinux.org) > 5. [PRQ#41675] Deletion Request for mangohud > (not...@aur.archlinux.org) > 6. [PRQ#41675] Deletion Request for mangohud Accepted > (not...@aur.archlinux.org) > 7. [PRQ#41676] Deletion Request for lib32-mangohud > (not...@aur.archlinux.org) > ___ > Aur-requests mailing list -- aur-requests@lists.archlinux.org > To unsubscribe send an email to aur-requests-le...@lists.archlinux.org
[PRQ#51721] Deletion Request for deadbeef-bs2b-git
yan12125 [1] filed a request to merge deadbeef-bs2b-git [2] into deadbeef-plugin-bs2b-git [3]: This is a follow up of PRQ#47847 [1]. Apparently this package was created as a replacement of deadbeef-bs2b [2]. I accepted the other merge request, so this package can be removed. [1] https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/JGXJ4PTVDMBZM2UPL75RANY6SYNQR7YL/ [2] https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/XYOQFABSB6T7I755U753SJMASQTQGMDX/ [1] https://aur.archlinux.org/account/yan12125/ [2] https://aur.archlinux.org/pkgbase/deadbeef-bs2b-git/ [3] https://aur.archlinux.org/pkgbase/deadbeef-plugin-bs2b-git/
Arch Linux in January 2023
## Git packaging sources We have announced the state of the art of the Git packaging migration to `arch-dev-public` [0] including a first item on our distro roadmap to track the remaining effort [1]. We have prepared most of the necessary settings, configurations and the corresponding machine for the new test environment for the Git package workflow. The test phase is expected to start at the beginning of February. ## base-devel We have implemented the `base-devel` and `multilib-devel` meta-package orthogonal to our already existing `base` meta-package [2][3]. Lately we added `debugedit` to `base-devel` in order to provide debug packages via makepkg. This lead to a couple of followup issues with installations missing the new package as changes in a package group are not automatically reflected on system upgrades. ## RFC We are formalizing an RFC [4] to increase `_FORTIFY_SOURCE` level to 3 in our default build flags. For a long time, we have been using `-D_FORTIFY_SOURCE=2` to detect C memory management problems at build time. Recently, glibc (2.34) added `_FORTIFY_SOURCE=3` to add extra checking. This has been supported in clang for some time, and is now available in GCC with the release of version 12. The gains are enhanced buffer size detection and better fortification coverage. ## Staff We would like to welcome Robin Candau (Antiz) among the Arch Linux Package Maintainers [5]. Due to extended inactivity, Kyle Keen (keenerd) has been removed from the Arch Linux Package Maintainers [6]. We would like to express our gratitude to Kyle for many years of packaging work. [0] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/YKKYBXQL62U5RTYIRI2NT2I3EG7V63HT/ [1] https://gitlab.archlinux.org/groups/archlinux/-/epics/7 [2] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/NDOV3CDX2GRWOWOQA6ALGLGFQGP7XGK7/ [3] https://archlinux.org/news/switch-to-the-base-devel-meta-package-requires-manual-intervention/ [4] https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17/ [5] https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/thread/5XZU2PEM5VLNUS2VJG3WUYH2SPW54GMO/ [6] https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/thread/JOOWVVVBP22M253QRSSU37HWVBNP5LJU/ OpenPGP_signature Description: OpenPGP digital signature
Please take actions against a problematic user
Hi all, I'm Kimiblock, requesting AUR moderators to take action against packager 7Ji and 2 packages: wechat-universal-bwrap and wechat-beta-bwrap. Despite the fact that we already discussed[a][b]: wechat-universal-bwrap and wechat-beta-bwrap is now duplicated packages of the original wechat-uos-bwrap (which has been renamed to wechat-uos-qt to avoid confusion[c]), user 7Ji still filed a deletion request against wechat-uos-bwrap[d]. He filed the deletion request because "don't want unrelated comments in the history of -universal, neither its votes". Ironically, he admitted that wechat-beta-bwrap is based on wechat-uos-bwrap and another package wechat-uos-qt is based on -beta-bwrap. He then said he "would want no history from -uos-bwrap". This is a serious violation of AUR submission guidelines[e]: "*Check the AUR* if the package *already exists*. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention." and this is not the end of this user's problematic behaviour. In the merge request of wechat-beta-bwrap filed by me, he said: "Additionally, as of writing, `wechat-beta-bwrap` has 21 votes, and `wechat-uos-bwrap`has 11 votes, it is not right to merge from a highly voted one a lowly voted one". This can't be right: if someone can mislead AUR users and let them vote the duplicated package, then the original package should be merged into the duplicated one? I can't understand the rationale behind this. All in all, please take actions against this user and 2 duplicated packages: wechat-universal-bwrap and wechat-beta-bwrap. -- Sincerely, Kimiblock [a]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/T4I2ZYPOPHTIKYJTUSB7CMHSNA6BHIZ7/ [b]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/A2WERVT4OAER7MXCYLQZQE3PZIZVMGKM/ [c]: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/message/TP77VTLMCJG2GRFKDUFH7C2OFFBZXS6F/ [d]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/message/IOUNAS4QK76VBXBEOI5RRFT6HUAP/ [e]: https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission OpenPGP_0x42A757534D542728.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Your confirmation is needed to join the aur-requests@lists.archlinux.org mailing list.
Confirm On Sat, Jul 15, 2023, 6:40 PM Miguel Flores wrote: > Confirm > > On Thu, Jul 13, 2023, 11:58 PM < > aur-requests-confirm+0d7525db41b49c965c4010b900f23d535423c...@lists.archlinux.org> > wrote: > >> Email Address Registration Confirmation >> >> Hello, this is the GNU Mailman server at lists.archlinux.org. >> >> We have received a registration request for the email address >> >> miguelflores40...@gmail.com >> >> Before you can start using GNU Mailman at this site, you must first >> confirm >> that this is your email address. You can do this by replying to this >> message. >> >> Or you should include the following line -- and only the following >> line -- in a message to aur-requests-requ...@lists.archlinux.org: >> >> confirm 0d7525db41b49c965c4010b900f23d535423c581 >> >> Note that simply sending a `reply' to this message should work from >> most mail readers. >> >> If you do not wish to register this email address, simply disregard this >> message. If you think you are being maliciously subscribed to the list, >> or >> have any other questions, you may contact >> >> aur-requests-ow...@lists.archlinux.org >> >
Re: [PRQ#57991] Merge Request for wechat-universal-bwrap
Hi all, As explained in aur-general[a][b], wechat-universal-bwrap is indeed a duplicate package of wechat-uos-bwrap. And should be merged due to the confusion[c] caused by it. As a side note, the original package was renamed to `wechat-uos-qt`, which now provides & replaces wechat-universal-bwrap. Looking forward to PMs' action, as the confusion is growing in the community... [a]: https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/message/A2WERVT4OAER7MXCYLQZQE3PZIZVMGKM/ [b]: https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/message/QZGIEYDI3FQYQ6AGCCHQBQQHO3DKRY32/ [c]: https://matrix.to/#/!EOKdtPPIPRxceuxXvC:mozilla.org/$2DhVI9uj46XipRaQ5cdu0edwbfTT6sF9n35WA-LoKGI?via=nichi.co&via=matrix.org&via=mozilla.org Sincerely, Kimiblock
Re: unable to build with makepkg (No such file or directory)
Le 29/07/2023 à 06:47, james smith a écrit : trying to build this https://github.com/matthewq337/auto-fdisk <https://github.com/matthewq337/auto-fdisk> https://bpa.st/H6XQ <https://bpa.st/H6XQ> Hi, For the third time now, please use the appropriate mailing list; which is aur-gene...@lists.archlinux.org, not aur-dev@lists.archlinux.org. aur-dev@lists.archlinux.org is reserved to the AUR code and development only. Please, move your thread over to aur-gene...@lists.archlinux.org to get answers. -- Regards, Robin Candau / Antiz OpenPGP_0xFDC3040B92ACA748.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
[arch-dev-public] [RFC] pyalpm maintainership
I'd like to see some improvements in the maintenance of pyalpm. The last update of pyalpm added pacman 5 compatibility support although several improvements patches where posted from October 2015 till 2016. [1] [2] [3] [4] [5]. I would love to see a more active maintenace of pyalpm, since it's vital for the arch-security tracker and namcap. I've mailed Remy about these patches but so far haven't gotten any response. [1] https://git.archlinux.org/users/remy/pyalpm.git/ [2] https://lists.archlinux.org/pipermail/arch-projects/2016-October/004413.html [3] https://lists.archlinux.org/pipermail/arch-projects/2016-October/004424.html [4] https://lists.archlinux.org/pipermail/arch-projects/2016-October/004420.html [5] https://lists.archlinux.org/pipermail/arch-projects/2015-October/004309.html ~ -- Jelle van der Waa signature.asc Description: PGP signature
Re: [PRQ#41675] Deletion Request for mangohud
May 27, 2023 16:32:31 Mark Wagie : > @serebit: It would help if you actually add it to the extra repo before > deleting it. > > Also, I do not appreciate you sloppifying the PKGBUILD and ignoring VCS > package guidelines for submodules. I spent a lot of time on this package > doing it right. > > > > Sent with Proton Mail secure email. > > --- Original Message --- > On Saturday, May 27th, 2023 at 1:55 PM, > aur-requests-requ...@lists.archlinux.org > wrote: > > >> Send Aur-requests mailing list submissions to >> aur-requests@lists.archlinux.org >> >> To subscribe or unsubscribe via email, send a message with subject or >> body 'help' to >> aur-requests-requ...@lists.archlinux.org >> >> You can reach the person managing the list at >> aur-requests-ow...@lists.archlinux.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Aur-requests digest..."Today's Topics: >> >> 1. [PRQ#41615] Deletion Request for booth Accepted >> (not...@aur.archlinux.org) >> 2. [PRQ#41412] Deletion Request for rstudio-bin Rejected >> (not...@aur.archlinux.org) >> 3. [PRQ#41411] Orphan Request for owncast Accepted >> (not...@aur.archlinux.org) >> 4. [PRQ#41674] Deletion Request for googleplay >> (not...@aur.archlinux.org) >> 5. [PRQ#41675] Deletion Request for mangohud >> (not...@aur.archlinux.org) >> 6. [PRQ#41675] Deletion Request for mangohud Accepted >> (not...@aur.archlinux.org) >> 7. [PRQ#41676] Deletion Request for lib32-mangohud >> (not...@aur.archlinux.org) >> ___ >> Aur-requests mailing list -- aur-requests@lists.archlinux.org >> To unsubscribe send an email to aur-requests-le...@lists.archlinux.org Well it's not a VCS package anymore (so those guidelines don't apply) nor does it need to be one since upstream doesn't sign release tags/commits anyway. Why work harder to get the same code with no tangible benefit? The other changes were removing mostly redundant code. Probably the only change I disagree with is removing the provides arrays... - éclairevoyant
Re: [PRQ#63608] Deletion Request for prismlauncher-cracked Rejected
Unless I am mistaken, other packages have been removed for the same reason. Request #40863 <https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/LXP2DQ6J4QWV6RXKAEDGDBSRULORBOFX/#LXP2DQ6J4QWV6RXKAEDGDBSRULORBOFX> and Request #37171 <https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/6QWJJ3USDUA6O2CVJ5R7IFLQLYYKOGFW/#SJUTSZE4ND2SJDSMJ7H2ORMRIVP2TAPL> to name two of them. I believe it also states in the FAQ of the AUR wiki page <https://wiki.archlinux.org/title/Arch_User_Repository#What_kind_of_packages_are_permitted_on_the_AUR?> that everything is allowed **as long as you are in compliance with the licensing terms of the content.** Which this package, among other packages submitted for review today definitely do not follow the Licensing terms of Minecraft. I believe I'm missing what about the AUR would make this among other packages submitted today fine, but the two I have previously brought up not fine. T
Re: Python 3.11 timeline?
On 12/13/22 3:43 AM, David Runge wrote: On 2022-11-08 11:18:57 (-0500), David Rosenstrauch wrote: Anyone know if there's any timeline on when we'll see python 3.11 get released to Arch? Hi David, we are on and off working on it, but not in the past weeks. There are quite a few things to figure out, as described here [1] although a lot of them have been solved technically already. Other than that, there are also a few (potentially) blocking TODOs [2][3]. Best, David [1] https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/ZK57U5LPIDDJWPXWU5DSIYSI3EWUBGPP/ [2] https://archlinux.org/todo/remove-python-pip-from-makedepends/ [3] https://archlinux.org/todo/stop-using-python-setuppy-test/ [4] https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/BHSMYEHPRW3UGOSA4OWMUSPSMZO2DFDR/ Very helpful, David. Thanks much for the response. DR
[PRQ#59778] Deletion Request for pikaur-aurnews
MarsSeed [1] filed a deletion request for pikaur-aurnews [2]: Disguised VCS package, 3rd resubmit after 2 deletions. [a] It is btw a one-line modded duplicate of AUR/pikaur{,-git}, [b], maintained on AUR by upstream, who in my experience is amenable to user suggestions and collaboraiton. @eggz has done this kind of thing multiple times now, see e.g. the continuously broken mate-wayland-session-git (2nd resubmit), [c] or the currently (and typically) broken ffmpeg-nocuda, duplicate of Arch/extra/ffmpeg. [d] [a]: https://lists.archlinux.org/archives/search?q=pikaur- aurnews&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [b]: https://aur.archlinux.org/packages?K=pikaur [c]: https://lists.archlinux.org/archives/search?q=mate-wayland-session- git&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [d]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/NVZTMTOTO3RELF75PW5MQ4HE4PEKBRIQ [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/pikaur-aurnews/
Re: [PRQ#47003] Merge Request for waterfox-current-bin
The target, 'waterfox-g-bin' no longer exists, because it has been renamed and merged to 'waterfox-bin'. I have created a new merge request that targets 'waterfox-bin': PRQ#47812. [a] [a]: https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/WRIWULGREH5G76EGXSHGZQKQ5TLDD4NB/ On 5 September 2023 00:26:42 GMT+02:00, not...@aur.archlinux.org wrote: >aliu [1] filed a request to merge waterfox-current-bin [2] into >waterfox-g-bin [3]: > >Either merge both into a new waterfox-bin, freeze this one back to the >version with the "Current" branding or just merge it. Though it >shouldn't be the same package it currently is. See >https://lists.archlinux.org/archives/list/arch- >gene...@lists.archlinux.org/thread/XKPXKGMRRRC7UG44CTY472UPCSZTEG2T/ > >[1] https://aur.archlinux.org/account/aliu/ >[2] https://aur.archlinux.org/pkgbase/waterfox-current-bin/ >[3] https://aur.archlinux.org/pkgbase/waterfox-g-bin/
Re: unable to build with makepkg (No such file or directory)
On Sat, Jul 29, 2023, 12:13 Robin Candau wrote: > Le 29/07/2023 à 06:47, james smith a écrit : > > trying to build this https://github.com/matthewq337/auto-fdisk > > <https://github.com/matthewq337/auto-fdisk> https://bpa.st/H6XQ > > <https://bpa.st/H6XQ> > > Hi, > > For the third time now, please use the appropriate mailing list; which > is aur-gene...@lists.archlinux.org, not aur-dev@lists.archlinux.org. > > aur-dev@lists.archlinux.org is reserved to the AUR code and development > only. > Please, move your thread over to aur-gene...@lists.archlinux.org to get > answers. > > -- > Regards, > Robin Candau / Antiz > In this context, AUR code and development mean the code used to run the AUR website and working on the code for the AUR website. If your question concern one specific AUR package, the correct list will always be AUR general, as AUR general cover code and development of individual AUR package. >
Re: [PRQ#38118] Orphan Request for polymc-git
For the non-VCS packages that are out of date, they're not even two weeks out of date. They should be given some time to update the packages themselves, calling them "unmaintained" is a stretch. I personally don't see a reason to orphan the other polymc packages at this time, FWIW, *except for polymc-git* which is run by a user who was previously banned for violating Arch's code of conduct (see [PRQ#37842]). On Tue, Nov 1, 2022 at 7:55 PM wrote: > Send Aur-requests mailing list submissions to > aur-requests@lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > aur-requests-requ...@lists.archlinux.org > > You can reach the person managing the list at > aur-requests-ow...@lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aur-requests digest..."Today's Topics: > >1. [PRQ#38116] Deletion Request for chd-git Accepted > (not...@aur.archlinux.org) >2. [PRQ#38116] Deletion Request for chd-git > (not...@aur.archlinux.org) >3. [PRQ#38117] Orphan Request for polymc (not...@aur.archlinux.org) >4. [PRQ#38118] Orphan Request for polymc-git > (not...@aur.archlinux.org) >5. [PRQ#38119] Orphan Request for polymc-bin > (not...@aur.archlinux.org) >6. [PRQ#38120] Orphan Request for polymc-qt5 > (not...@aur.archlinux.org) >7. [PRQ#38121] Orphan Request for polymc-qt5-bin > (not...@aur.archlinux.org) > > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: kcu9...@gmail.com > Bcc: > Date: Tue, 01 Nov 2022 23:04:48 + > Subject: [PRQ#38116] Deletion Request for chd-git Accepted > Request #38116 has been Accepted by NoahArcouette [1]: > > [Autogenerated] Accepted deletion for chd-git. > > [1] https://aur.archlinux.org/account/NoahArcouette/ > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: kcu9...@gmail.com > Bcc: > Date: Tue, 01 Nov 2022 23:04:47 + > Subject: [PRQ#38116] Deletion Request for chd-git > NoahArcouette [1] filed a deletion request for chd-git [2]: > > requires libmsap and libmacsv which arn't in the pacman repos > > [1] https://aur.archlinux.org/account/NoahArcouette/ > [2] https://aur.archlinux.org/pkgbase/chd-git/ > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: yellowglori...@gmail.com, kay...@kaydax.xyz > Bcc: > Date: Tue, 01 Nov 2022 23:54:03 + > Subject: [PRQ#38117] Orphan Request for polymc > Kaydax [1] filed an orphan request for polymc [2]: > > The package is left unmaintained and the current package maintainer > refuses to give the package up to a maintainer that can actively > maintain it > > [1] https://aur.archlinux.org/account/Kaydax/ > [2] https://aur.archlinux.org/pkgbase/polymc/ > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: kay...@kaydax.xyz > Bcc: > Date: Tue, 01 Nov 2022 23:54:17 + > Subject: [PRQ#38118] Orphan Request for polymc-git > Kaydax [1] filed an orphan request for polymc-git [2]: > > The package is left unmaintained and the current package maintainer > refuses to give the package up to a maintainer that can actively > maintain it > > [1] https://aur.archlinux.org/account/Kaydax/ > [2] https://aur.archlinux.org/pkgbase/polymc-git/ > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: c...@cleo.nyc, kay...@kaydax.xyz > Bcc: > Date: Tue, 01 Nov 2022 23:54:30 + > Subject: [PRQ#38119] Orphan Request for polymc-bin > Kaydax [1] filed an orphan request for polymc-bin [2]: > > The package is left unmaintained and the current package maintainer > refuses to give the package up to a maintainer that can actively > maintain it > > [1] https://aur.archlinux.org/account/Kaydax/ > [2] https://aur.archlinux.org/pkgbase/polymc-bin/ > > > -- Forwarded message -- > From: not...@aur.archlinux.org > To: aur-requests@lists.archlinux.org > Cc: sw...@swurl.xyz, kay...@kaydax.xyz > Bcc: > Date: Tue, 01 Nov 2022 23:54:55 + > Subject: [PRQ#38120] Orphan Request for polymc-qt5 > Kaydax [1] filed an orphan request for polymc-qt5 [2]: > > The package is left unmaintained and the current package maintainer > refuses to give the package up to a maintainer that can actively > maintain it > &
Re: DKIM fail messages
On Sunday, 30 October 2022 at 17:58 (-0400), David Rosenstrauch wrote: After posting a message to this list earlier today, I immediately received nearly a dozen DKIM fail messages, all being sent by the "OpenDMARC Filter" at various domains, and all saying that the DKIM fail reason was "signature verification failed". [...] Anyone know why these fail messages might be happening? Is this being caused by a misconfiguration in Arch's mailman installation? Or is this a misconfiguration of the individual OpenDMARC software installations at each of those domains? FWIW, my OpenDKIM with default settings flagged your earlier email with a DKIM fail, but passed this one. The failure mechanism on the first email was "signature verification failed". I'm no DKIM expert, but perhaps there was a DNS resolution problem at that time and the key was inaccessible? Relevant part of received headers follows: From your earlier email: Authentication-Results: mail.kent-dobias.com; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=darose.net header.i=@darose.net header.a=rsa-sha256 header.s=dreamhost header.b=UaDsk2dh Authentication-Results: mail.kent-dobias.com; dmarc=fail (p=none dis=none) header.from=darose.net Authentication-Results: mail.kent-dobias.com; spf=pass smtp.mailfrom=lists.archlinux.org Authentication-Results: lists.archlinux.org; dkim=pass header.d=darose.net header.s=dreamhost header.b=UaDsk2dh; dmarc=pass (policy=none) header.from=darose.net; spf=pass (lists.archlinux.org: domain of dar...@darose.net designates 23.83.214.25 as permitted sender) smtp.mailfrom=dar...@darose.net; arc=pass ("mailchannels.net:s=arc-2022:i=1") From this email: Authentication-Results: mail.kent-dobias.com; dkim=pass (2048-bit key; unprotected) header.d=darose.net header.i=@darose.net header.a=rsa-sha256 header.s=dreamhost header.b=JyPU2yJv Authentication-Results: mail.kent-dobias.com; dmarc=pass (p=none dis=none) header.from=darose.net Authentication-Results: mail.kent-dobias.com; spf=pass smtp.mailfrom=lists.archlinux.org Authentication-Results: lists.archlinux.org; dkim=pass header.d=darose.net header.s=dreamhost header.b=JyPU2yJv; dmarc=pass (policy=none) header.from=darose.net; spf=pass (lists.archlinux.org: domain of dar...@darose.net designates 23.83.212.19 as permitted sender) smtp.mailfrom=dar...@darose.net; arc=pass ("mailchannels.net:s=arc-2022:i=1") Jaron
Re: Arch-mirrors Digest, Vol 7, Issue 3
Hey! Airtel allows port 443 and 80 on static IP. I host https://mirror.albony.xyz/ on my airtel connection Try asking their customer support to raise a request. Thanks --- Original Message --- On Saturday, March 18th, 2023 at 1:36 PM, arch-mirrors-requ...@lists.archlinux.org wrote: > Send Arch-mirrors mailing list submissions to > arch-mirrors@lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > arch-mirrors-requ...@lists.archlinux.org > > You can reach the person managing the list at > arch-mirrors-ow...@lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Arch-mirrors digest..." > > Today's Topics: > > 1. Re: Mirror mirror.chaoticum.net (pitastrudl) > 2. Are alternate ports for HTTP(S) okay? (Strykar) > > > -- > > Message: 1 > Date: Fri, 17 Mar 2023 19:38:16 +0100 > From: pitastrudl pitastr...@archlinux.org > > Subject: Re: Mirror mirror.chaoticum.net > To: arch-mirrors@lists.archlinux.org > Message-ID: e4eb1580-1718-7b8f-0fcc-5e06567a0...@archlinux.org > > Content-Type: multipart/signed; micalg=pgp-sha256; > protocol="application/pgp-signature"; > boundary="1ksPWc0oU0uisqZQWmMtItp3" > > On 3/11/23 11:02, Emmanuel Marquez wrote: > > > Hi Andreas, what I am requesting for is to add our mirror on the archlinux > > mirror list. Arch Linux - Mirror Status > > https://archlinux.org/mirrors/status/ > > > > On Sat, Mar 11, 2023 at 5:57 PM Andreas Pfister > > wrote: > > > > > Dear! > > > Due to hardware failure and family reasons, http://mirror.chaoticum.net > > > is no longer available. > > > > > > Greetings > > > > > > -- > > > PGP Schlüssel für andi-pfister(a)mail80.ch (Longid: 615CD701B915CA4B > > > Shortid: B915CA4B) > > > > > > Anleitung von mozilla.org: > > > > > > https://support.mozilla.org/de/kb/nachrichten-digital-signieren-und-verschlusseln > > > > > > -BEGIN PGP PUBLIC KEY BLOCK- > > > > > > mQENBF3RB/UBCACr6rllJWwwrlVYbiInmsrYapKC6h/MwhHoSOB3UWzP1OhX8mpV > > > 79za/FpGPwczdr6g8fuZI/zarx5UzY+PesHKnI14s202JIT9n0wwmgWOEvmG4WaS > > > WR5QVL9e4MR/BNt8fkVmt6wAhBJBIy7oygggFChIraY3IAgg8VruiP3ZaPzB338G > > > Kh0jm0CMCHFf7AgLKdLJFdt++s4swsEpLlzogGdiM+vpRox8wQlvHUDb225Vw54N > > > MiuPszFgnnxB7egjj8BokUUhxosNMaFpijE4MwMKJGt+cGOMPgFdcsW6PLrgeQS0 > > > Doxi4KlxH7Wl1EDNL8KzBnR7K+JZSNRkQMnhABEBAAG0KEFuZHJlYXMgUGZpc3Rl > > > ciA8YW5kaS1wZmlzdGVyQG1haWw4MC5jaD6JAU4EEwEIADgWIQQztepkA79ivIGb > > > y7xhXNcBuRXKSwUCXdEH9QIbLwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRBh > > > XNcBuRXKSza4B/sEdvFs8NegBVQu97AHH4yLuwD/10hNfBV3vfJf131CF+YJv4B8 > > > BaQWjqMAH71NQrAT00eoogfbwjC3MEZvnJZfu5qdk/UDolNws2zU0u1YXg3wii1x > > > 0fp7pSCv3t0zmIrNJCN4Y8hken0D0V/IxHMIQVaUzmKNsJEoGkAkNCIUTYQ+xv9i > > > jB7Yeyzn9b8AmMrDWOy+Pz3HOxG2w6Iiv0cHGZ7J9VypPDe7Vk+X3ZDxTcyIXemA > > > 9KZPfjtHKcAC3Q3aDCUkJcrPKaB6OwIfyFejv8HGZxDSQLuyZ2faKwizYI10e0n3 > > > iECQupDWILPMcoRt8cO8TCrucOw2PWT3AX/TuQENBF3RB/UBCAC+ZP2S8DNg1Ner > > > deM9i3nNy8sqelXfgd1nZpREMSvs/TNMcqutT3wHq6vcRdEK8o/dMXG1QFozsuhD > > > 5boRPNt6fUAiQIy5vydp3rV5fLcoFO2N0GNLy/BidRYsV5JzR/R7H0DPZCcf1NFM > > > rrWOFhAoS9Cw4bfG70xtCOH3HETjQ/YgXJWHFcDnLpTMQfF9/k4lKJj+oQW54sLN > > > k3MKwhjwwfnqoJcABwDd/WN0i/BizmPjwE+NaS9D0YiIvfG1dku+ysc5kFsFjWwE > > > mxy5BLDLwuQLHMKu+DdruPE1qfHBCwxy9AnbUHs4aOLfNrEOleDEOyAIqdhObuzh > > > 1cv42Em1ABEBAAGJAmwEGAEIACAWIQQztepkA79ivIGby7xhXNcBuRXKSwUCXdEH > > > 9QIbLgFACRBhXNcBuRXKS8B0IAQZAQgAHRYhBMx+Dr8P7bG8r7+pUGYsYj+7C3jn > > > BQJd0Qf1AAoJEGYsYj+7C3jn4A4H/0TmC21rT5hwhK4TyajD19B7IIz9Yz+JnN7t > > > LiihuzM4pgaTt79AzmsQx7bxyOfC2HT9EujYNjfvBjmCyMfLZVa0SPLKYp5bG74m > > > w78tBSiCaHcvv0zfPu4+0i14UaXzEL6e21hQHMq6720S2YEifVJdIWN8dyybEO0g > > > 6CZE7BzbSV0Bwc1VDTeYQVOnPfx0jjqXrSYAW0zzPpeGOS/eCQxjvCDEGYm4DVdk > > > agVPAmZGPEJchlu1wy/+2CvAO3iVYrcMvhXEVD3wg+X8yboqKt94WAKXC6eWYjcT > > > KZXAlGJq0cVeOD5HgiPvNWn9b0OlNXiWqKJV2roY3Ri+e+pngHZPLAf/XgOF4K8a > > > CGFEahknmXyTbN7WdH3KElv9VJ1i3JFJa22lx1udppalZBgWVb6F4FT7KjPgw3HV > > > yzXMaSy7jtJz6IldLpLQQ41dmW1cws5xJVRdh5HGNEPv+gwS+3hqoK7Lamwy11i/ > > > ubVHGHa4iw1ZbI0gXaik3XZu2DRhkvBeVN0ttmZDeC1T1QE3RAyPOx7Qw07pQdvd > > > VcOVjXdz/2ppkN2KrZMlLHC0K8cpVFo8JgUoDKz9MHpgU5JPJWTkvYBuuw9EKU8g > > > C8Jl32hUkZFi3uTV7luNZ+ZSGeiSV3Dz1rzuljwF+mnzLMzTOlWf7I1X2FfmReG3 > > > S
Re: [arch-general] talkingarch
On 2019-08-04 20:46:35 (+0100), adérito wrote: > I did not have jenux because I can not change the language to > Portuguese jenux. because I can't get into settings. Please stop spamming the mailing lists with these one line requests, or you will be put on moderation. You're opening a new mail thread every time ([1][2][3][4]) without any gain for anyone (including yourself). If you would like to discuss a topic, please answer to your own mail thread and the replies you got there (e.g. [2]). Also, please read the mailing lists guideline [5] (again), for best practices on mailing lists. Best, David [1] https://lists.archlinux.org/pipermail/arch-general/2019-August/046692.html [2] https://lists.archlinux.org/pipermail/arch-general/2019-August/046693.html [3] https://lists.archlinux.org/pipermail/arch-general/2019-August/046713.html [4] https://lists.archlinux.org/pipermail/arch-general/2019-August/046717.html [5] https://wiki.archlinux.org/index.php/Code_of_conduct#Mailing_lists -- https://sleepmap.de signature.asc Description: PGP signature
Re: Application as Trusted User
On 3/14/23 18:34, Leonidas Spyropoulos wrote: Hello On 14/03/2023 14:47, Anton Hvornum wrote: ... I aim to co-maintain the following packages: * python-pyparted (added 2023-03-14) * python This involves a bootstrapping mechanism and is part of core not community. That is true, I might have been a bit fuzzy in the description there. I aim to help out with Python releases by helping out testing and submitting patches to upstream whenever there is an issue. For instance by looking at https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/message/VEGSCAK5H2RCQZ3OKZQ7BTTBHK3LV4JF/ and helping debug situations like https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/message/ZK57U5LPIDDJWPXWU5DSIYSI3EWUBGPP/ * synapse synapse or matrix-synapse? Good catch, matrix-synapse :) * keycloak * rdesktop Both keycloak and rdesktop have a few maintainers (3+) Noted, I'll keep an eye on them tho and help test them whenever they're in testing for instance. //Anton OpenPGP_0x5FBBB32941E3740A.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: [PRQ#66057] Orphan Request for origami.ok
On Thu, Nov 21, 2024 at 12:36:20PM +0900, Nicolas Modrzyk wrote: > I am the owner. What needs to be done? What do you mean? The package was disowned automatically because you never addressed the issues pointed out in the comments, and now there is a pending deletion request. If you want to delete this package, then there's nothing to be done; a PM will do it for you. If you want to keep it in the AUR, you need: 1) explain why this package is useful for others (not just you). To me it looks like a personal project. 2) Fix the PKGBUILD as pointed out in the comments. Also fix the package `inlein` since this is a dependency of origami (it's also for deletion due to unfixed issues). Also, you need to reply to this email [1] because as I said, this package will be deleted. [1] https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/message/XWJUNNYXUJIN52VNFDWLEYAJUBHIUMP2/ [2] https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/message/GAVQL7AJ6B42DODVHXXIEV3J6ZHZ5T5P/
Re: Proposal to increase the default vm.max_map_count value
On 4/2/24 9:14 AM, Robin Candau wrote: On April 1, 2024 12:09:47 PM UTC, Robin Candau wrote: On 3/25/24 9:10 AM, Robin Candau wrote: Hi everyone, I'm writing this mail as proposal to increase the default `vm.max_map_count` value in Arch Linux. It's been a week since this proposal thread [1] was made. For now it only received a few but all positives feedback (both from staff members and users in a related thread on arch-general [2]). Do we have any more thoughts anyone wants to share? Also, if we are to implement this change, anyone has an opinion about which package should provide it? So far, the following packages have been mentioned: - systemd (as Fedora did) - procps-ng (as Ubuntu did) - filesystem Given that the proposal goes through, I'll create the MR to the chosen package accordingly. Also, despite this change being impact-free (as far as we can tell), I think a related news item to inform users about this change would be a great idea (I'll write that as well). Please, share your opinion about the change itself or the best package to provide it if you have any :) [1] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/ <https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/> [2] https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/ <https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/> On 4/1/24 11:11 PM, Ehalls wrote: I would keep it out of systemd. Do you think it is the approproate place? (Copying the above response I received from someone off-list, as it is staff only) Since the change consists of shipping a sysctl file and that sysctl is provided by procps-ng, I personally think procps-ng is the appropriate place. Another suggestion I got off-list is to ship that change with the kernel. While I get why it would make sense, we maintain and support multiple kernel packages (6 currently). Making this change __the default__ (which is the aim of this proposal) will imply to ship it in every kernel packages we currently maintain on Arch side (and in every kernel packages we will potentially add in the future). I'm personally more in favor of shipping this change in one central place to avoid the additional maintenance eventually implied by having it in multiple places at once. Shipping it in nprocps-ng felt reasonable to me (as it's the package providing `sysctl`) but if shipping such a "downstream" change to the nprocps-ng package is a concern regarding our "simplicity" principle [1], then I think the filesystem package would be the right place instead. [1] https://wiki.archlinux.org/title/Arch_Linux#Simplicity -- Regards, Robin Candau / Antiz OpenPGP_0xFDC3040B92ACA748.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [aur-requests] [PRQ#2407] Request Rejected
> in such case it wouldn't be "broken" but as far I remember the AUR > helpers cannot find the right dependencies based on provides . > Therefore the package openfoam wouldn't be BROKEN but during the install > phase it **should** claim about some unsolved dependencies and will > refuse to build. Yes, indeed. > Maybe I missed (and I cannot find in the archives) the aur-general > discussion where the maintainers would abandon their packages in favour > of yours, agreeing to the merge, so please send us a link where I can > see the whole discussion. https://lists.archlinux.org/pipermail/aur-general/2015-February/030300.html https://lists.archlinux.org/pipermail/aur-general/2015-February/030301.html https://lists.archlinux.org/pipermail/aur-general/2015-February/030303.html https://lists.archlinux.org/pipermail/aur-general/2015-February/030309.html https://lists.archlinux.org/pipermail/aur-general/2015-February/030310.html There were two more replies though, which (due to reasons that are beyond my understanding) were not archived. Either their authors or other recipients can confirm: 1) Andrew Fischer: I'm not a scotch packager so Ill let others comment on the gory details. But from the openfoam standpoint this sounds like a great idea. I would definitely be onboard. 2) Jed Brown: > You are right :-) ( i hadn't yet discovered the real power of "provides") Seems you got a little overzealous because your package is providing both ptscotch-mpich2 (a package that doesn't exist) and ptscotch-openmpi. MPICH is binary-incompatible with OpenMPI, so these packages can never be merged. I would be happy if someone took over maintainership of ptscotch-{openmpi,mpich}, but ptscotch-mpich (maybe now called scotch-mpich) should continue to exist and be kept consistent. Is that something you're willing to do? Any reason you're dropping support for arch=i686? Probably all architectures should be supported. -- I skipped commenting on the architecture point and ptscotch-mpich2 because these two had already been fixed by then. -- following a separate communication with Jed Brown resulting from a Deletion Request I filed against ptscotch-mpich (which later regretted but couldn't cancel it)... https://lists.archlinux.org/pipermail/aur-requests/2015-February/004963.html https://lists.archlinux.org/pipermail/aur-requests/2015-February/004968.html https://lists.archlinux.org/pipermail/aur-requests/2015-February/004976.html ... I offered to take over ptscotch-mpich. Jed didn't answer and ptscotch-mpich was finally removed but I resubmitted it instantly (an improved version of the PKGBUILD I had proposed to Jed). Anyway, the way I see it, is that there is only two *scotch* packages really needed in AUR in order to cover any scenario. The all-inclusive scotch and ptscotch-mpich... and what's even better is that they don't conflict (as the mpich implementation is stored in /opt). Right now, and for the (foreseeable) future I'll be maintaining both with great care. Best regards, George
Re: [arch-releng] RFC: Automated Install
Hi all, FYI, I have removed and banned the offender from the mailing list: https://lists.archlinux.org/pipermail/arch-releng/2021-July/004031.html https://lists.archlinux.org/pipermail/arch-releng/2021-July/004032.html https://lists.archlinux.org/pipermail/arch-releng/2021-July/004037.html This behavior is not in line with our Code of Conduct [1] and will not be tolerated in this community. Best, David [1] https://gitlab.archlinux.org/archlinux/service-agreements/-/blob/master/code-of-conduct.md -- https://sleepmap.de signature.asc Description: PGP signature
Re: [PRQ#41675] Deletion Request for mangohud
--- Original Message --- On Saturday, May 27th, 2023 at 7:58 PM, é wrote: > May 27, 2023 16:32:31 Mark Wagie mark.wa...@proton.me: > > > @serebit: It would help if you actually add it to the extra repo before > > deleting it. > > > > Also, I do not appreciate you sloppifying the PKGBUILD and ignoring VCS > > package guidelines for submodules. I spent a lot of time on this package > > doing it right. > > > > Sent with Proton Mail secure email. > > > > --- Original Message --- > > On Saturday, May 27th, 2023 at 1:55 PM, > > aur-requests-requ...@lists.archlinux.org > > aur-requests-requ...@lists.archlinux.org wrote: > > > > > Send Aur-requests mailing list submissions to > > > aur-requests@lists.archlinux.org > > > > > > To subscribe or unsubscribe via email, send a message with subject or > > > body 'help' to > > > aur-requests-requ...@lists.archlinux.org > > > > > > You can reach the person managing the list at > > > aur-requests-ow...@lists.archlinux.org > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of Aur-requests digest..."Today's Topics: > > > > > > 1. [PRQ#41615] Deletion Request for booth Accepted > > > (not...@aur.archlinux.org) > > > 2. [PRQ#41412] Deletion Request for rstudio-bin Rejected > > > (not...@aur.archlinux.org) > > > 3. [PRQ#41411] Orphan Request for owncast Accepted > > > (not...@aur.archlinux.org) > > > 4. [PRQ#41674] Deletion Request for googleplay > > > (not...@aur.archlinux.org) > > > 5. [PRQ#41675] Deletion Request for mangohud > > > (not...@aur.archlinux.org) > > > 6. [PRQ#41675] Deletion Request for mangohud Accepted > > > (not...@aur.archlinux.org) > > > 7. [PRQ#41676] Deletion Request for lib32-mangohud > > > (not...@aur.archlinux.org) > > > ___ > > > Aur-requests mailing list -- aur-requests@lists.archlinux.org > > > To unsubscribe send an email to aur-requests-le...@lists.archlinux.org > > Well it's not a VCS package anymore (so those guidelines don't apply) nor > does it need to be one since upstream doesn't sign release tags/commits > anyway. Why work harder to get the same code with no tangible benefit? > > The other changes were removing mostly redundant code. Probably the only > change I disagree with is removing the provides arrays... > > > - éclairevoyant It appears my reaction was a bit hasty and sounded rude. I learned this morning from the arch-dev-public list that serebit initially was not able to push lib32-mangohud to multilib. Perhaps using "sloppify" was a little extreme as well. As far as the VCS package guidelines, I was only referring to the use of submodules which mangohud uses. It also uses Meson subprojects. P.S. Is it customary for Arch mailing lists to reply above or below the quote? I know I saw guidelines somewhere, but can't find them now.
[PRQ#59777] Deletion Request for mate-wayland-session-git
MarsSeed [1] filed a deletion request for mate-wayland-session-git [2]: Broken package, defiant resubmit after it got deleted. (PRQ#58851) [a] @eggz has done this kind of thing multiple times now, see e.g. pikaur- aurnews (3rd resubmit), which is a one-line modded duplicate of AUR/pikaur, maintained by upstream. [b] [a]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/WODWYB2E3RIQHFTYSB5F4FQFX3FHMENZ [b]: https://lists.archlinux.org/archives/search?q=pikaur- aurnews&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/mate-wayland-session-git/
[aur-requests] [PRQ#4379] Merge Request for vscode-bin
dcelasun [1] filed a request to merge vscode-bin [2] into visual- studio-code [3]: visual-studio-code is the original package and it's older. All other duplicates ([0],[1],[2]) have been merged into visual-studio-code in the past. [0] https://lists.archlinux.org/pipermail/aur- requests/2015-April/006609.html [1] https://lists.archlinux.org/pipermail/aur- requests/2015-April/006610.html [2] https://lists.archlinux.org/pipermail/aur- requests/2015-April/006611.html Thanks. [1] https://aur.archlinux.org/account/dcelasun/ [2] https://aur.archlinux.org/pkgbase/vscode-bin/ [3] https://aur.archlinux.org/pkgbase/visual-studio-code/
Re: [arch-dev-public] [RFC] pyalpm maintainership
On 2016-12-24 20:18, Jelle van der Waa wrote: > I'd like to see some improvements in the maintenance of pyalpm. The last > update of pyalpm added pacman 5 compatibility support although several > improvements patches where posted from October 2015 till 2016. [1] [2] > [3] [4] [5]. > > I would love to see a more active maintenace of pyalpm, since it's > vital for the arch-security tracker and namcap. I've mailed Remy about > these patches but so far haven't gotten any response. > > [1] https://git.archlinux.org/users/remy/pyalpm.git/ > [2] > https://lists.archlinux.org/pipermail/arch-projects/2016-October/004413.html > [3] > https://lists.archlinux.org/pipermail/arch-projects/2016-October/004424.html > [4] > https://lists.archlinux.org/pipermail/arch-projects/2016-October/004420.html > [5] > https://lists.archlinux.org/pipermail/arch-projects/2015-October/004309.html > ~ > Let's move it to top level (to "Arch Linux Projects") as opposed to Remy's project and give you push access. I don't see any reason not to. Let's wait +/- 3 days and I will proceed with this. Bartłomiej signature.asc Description: OpenPGP digital signature
Re: Python 3.11 timeline?
BTW, a big thanks to everyone involved with getting Python 3.11 out the door. Clearly it was a big lift. Many thanks to everyone who put in the hard work on it. DR On 12/13/22 9:47 AM, David Rosenstrauch wrote: On 12/13/22 3:43 AM, David Runge wrote: On 2022-11-08 11:18:57 (-0500), David Rosenstrauch wrote: Anyone know if there's any timeline on when we'll see python 3.11 get released to Arch? Hi David, we are on and off working on it, but not in the past weeks. There are quite a few things to figure out, as described here [1] although a lot of them have been solved technically already. Other than that, there are also a few (potentially) blocking TODOs [2][3]. Best, David [1] https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/ZK57U5LPIDDJWPXWU5DSIYSI3EWUBGPP/ [2] https://archlinux.org/todo/remove-python-pip-from-makedepends/ [3] https://archlinux.org/todo/stop-using-python-setuppy-test/ [4] https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/BHSMYEHPRW3UGOSA4OWMUSPSMZO2DFDR/ Very helpful, David. Thanks much for the response. DR
[PRQ#59779] Deletion Request for ffmpeg-nocuda
MarsSeed [1] filed a deletion request for ffmpeg-nocuda [2]: Unbuildable duplicate build of Arch/extra/ffmpeg (though newer version.) This is the 2nd resubmit of this package after it was already deleted once. [a] Maintainer @eggz does not properly test their pushed packages, and defiantly resubmits the ones that get deleted, even if for valid reasons. Arch repo's ffmpeg also builds without cuda support, so there is no benefit in keeping a '-nocuda' pkg. See other instances of defiance: - 3rd resubmit of the one-line modded pikaur-aurnews, disguised VCS package, [b] [c] - 2nd resubmit of the never-buildable mate-wayland-session-git. [d] [e] [a]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/NVZTMTOTO3RELF75PW5MQ4HE4PEKBRIQ [b]: https://aur.archlinux.org/packages/pikaur-aurnews [c]: https://lists.archlinux.org/archives/search?q=pikaur- aurnews&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [d]: https://aur.archlinux.org/packages/mate-wayland-session-git [e]: https://lists.archlinux.org/archives/search?q=mate-wayland-session- git&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/ffmpeg-nocuda/
Re: [aur-general] lists.archlinux.org mailing list memberships reminder
On Wed, Oct 1, 2014 at 7:00 AM, wrote: > This is a reminder, sent out once a month, about your > lists.archlinux.org mailing list memberships. It includes your > subscription info and how to use it to change it or unsubscribe from a > list. > > You can visit the URLs to change your membership status or > configuration, including unsubscribing, setting digest-style delivery > or disabling delivery altogether (e.g., for a vacation), and so on. > > In addition to the URL interfaces, you can also use email to make such > changes. For more info, send a message to the '-request' address of > the list (for example, mailman-requ...@lists.archlinux.org) containing > just the word 'help' in the message body, and an email message will be > sent to you with instructions. > > If you have questions, problems, comments, etc, send them to > mailman-ow...@lists.archlinux.org. Thanks! > > Passwords This is news to me. I never got this kind of stuff from this mailing list. Hope I won't get removed from not doing much about it... cheers! mar77i
Re: Proposal to increase the default vm.max_map_count value
On 4/2/24 11:59 AM, Robin Candau wrote: On 4/2/24 9:14 AM, Robin Candau wrote: On April 1, 2024 12:09:47 PM UTC, Robin Candau wrote: On 3/25/24 9:10 AM, Robin Candau wrote: Hi everyone, I'm writing this mail as proposal to increase the default `vm.max_map_count` value in Arch Linux. It's been a week since this proposal thread [1] was made. For now it only received a few but all positives feedback (both from staff members and users in a related thread on arch-general [2]). Do we have any more thoughts anyone wants to share? Also, if we are to implement this change, anyone has an opinion about which package should provide it? So far, the following packages have been mentioned: - systemd (as Fedora did) - procps-ng (as Ubuntu did) - filesystem Given that the proposal goes through, I'll create the MR to the chosen package accordingly. Also, despite this change being impact-free (as far as we can tell), I think a related news item to inform users about this change would be a great idea (I'll write that as well). Please, share your opinion about the change itself or the best package to provide it if you have any :) [1] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/ <https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/> [2] https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/ <https://lists.archlinux.org/archives/list/arch-gene...@lists.archlinux.org/thread/7X2LRLDCR3L3JMKBM6ZJYUKCXJ6A36QL/> Another suggestion I got off-list is to ship that change with the kernel. While I get why it would make sense, we maintain and support multiple kernel packages (6 currently). Making this change __the default__ (which is the aim of this proposal) will imply to ship it in every kernel packages we currently maintain on Arch side (and in every kernel packages we will potentially add in the future). I'm personally more in favor of shipping this change in one central place to avoid the additional maintenance eventually implied by having it in multiple places at once. Shipping it in nprocps-ng felt reasonable to me (as it's the package providing `sysctl`) but if shipping such a "downstream" change to the nprocps-ng package is a concern regarding our "simplicity" principle [1], then I think the filesystem package would be the right place instead. [1] https://wiki.archlinux.org/title/Arch_Linux#Simplicity As someone reminded me off-list, the filesystem package already ships some Arch specific kernel configs (under /usr/lib/sysctl.d/10-arch.conf) [1]. Adding the change to that file via the filesystem package then feels like the obvious choice. With no expressed concern/objection by next Sunday, I'll make the MR to the filesystem package and start drafting a news. [1] https://gitlab.archlinux.org/archlinux/packaging/packages/filesystem/-/blob/main/sysctl -- Regards, Robin Candau / Antiz OpenPGP_0xFDC3040B92ACA748.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
[arch-announce] Arch Linux mailing list id changes
Due to issues with our anti spam measures, we had to migrate those mailing lists, that were sent from @archlinux.org before to the @lists.archlinux.org domain. Submission to the mailing list is not affected and still works with @archlinux.org. Mails get redirected automagically. The only change that may need to be considered on your side are filters and rules matching the From or List-id header which changed accordingly. URL: https://www.archlinux.org/news/arch-linux-mailing-list-id-changes/ ___ arch-announce mailing list arch-announce@lists.archlinux.org https://lists.archlinux.org/listinfo/arch-announce
Re: [pacman-dev] Any final changes?
On 05/12/2018 09:21 AM, Allan McRae wrote: > I am about to call the final freeze. Anything final to add that I missed? Well, I'd kind of like my modeline changes to go in, since technically they're the continuation of a patchset from over a year ago. https://lists.archlinux.org/pipermail/pacman-dev/2017-January/021819.html https://lists.archlinux.org/pipermail/pacman-dev/2017-January/021829.html I still think https://lists.archlinux.org/pipermail/pacman-dev/2018-April/022433.html should be added, but see my response there. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] https://lists.archlinux.org/
On 2018-11-10 05:36:08 (+0100), Ralf Mardorf via arch-general wrote: > mails to mail...@lists.archlinux.org [1] are rejected. > > I try to get in contact with the owner of one list, but don't get a > reply. > > Regards, > Ralf > > > [1] > "If you are having trouble using the lists, please contact > mail...@lists.archlinux.org." - https://lists.archlinux.org/ The one list you're seemingly having trouble with is arch-proaudio [1]. You have been on moderation there for quite some time (and I reverted this now - as written there a few minutes ago). The owner contact address for that list would be arch-proaudio-owner@. You tried to send your mail to a mail address (mailman@) only (not so) relevant to the mailman setup. I guess a more useful /dev/null address could be put there, as we can assume, that the default mailman@ mailing list is either deactivated or doesn't exist anymore. However, that contact mail address is more aimed at list administrators (AFAIK). In any case: There's no need to send an e-mail to arch-general about your moderation. You simply were on moderation and mailman notifies you about that. There's nothing special about this case, so please stop posting all over the place and simply wait. If you don't get a reply instantly, this doesn't mean noone is receiving your emails. It only means a human on the other end simply either didn't have the time to work on your moderation or to even read your mail. All relevant information about your moderation can be found on arch-proaudio. Best, David [1] https://lists.archlinux.org/listinfo/arch-proaudio -- https://sleepmap.de signature.asc Description: PGP signature
Re: Python 3.11 timeline?
On Tue, Dec 13, 2022 at 9:48 AM David Rosenstrauch wrote: > > > On 12/13/22 3:43 AM, David Runge wrote: > > On 2022-11-08 11:18:57 (-0500), David Rosenstrauch wrote: > >> Anyone know if there's any timeline on when we'll see python 3.11 get > >> released to Arch? > > > Hi David, > > > > we are on and off working on it, but not in the past weeks. > > There are quite a few things to figure out, as described here [1] > > although a lot of them have been solved technically already. > > Other than that, there are also a few (potentially) blocking TODOs > > [2][3]. > > > Best, > > David > > > > [1] > https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/ZK57U5LPIDDJWPXWU5DSIYSI3EWUBGPP/ > > [2] https://archlinux.org/todo/remove-python-pip-from-makedepends/ > > [3] https://archlinux.org/todo/stop-using-python-setuppy-test/ > > [4] > https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/BHSMYEHPRW3UGOSA4OWMUSPSMZO2DFDR/ > > > Very helpful, David. Thanks much for the response. > > DR > Just in addition, if you really want to use/tests new python versions without waiting for it to be available in the official repos, you should try `pyenv` [1] and install the versions you want without the fear of damaging your OS [1] https://github.com/pyenv/pyenv -- CJ
[PRQ#51287] Deletion Request for ut2004-gog Rejected
Request #51287 has been Rejected by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/AXAQ72LFZ6QLD6PVI6YS6EQYCP2DYV5N [1] https://aur.archlinux.org/account/muflone/
[PRQ#40743] Deletion Request for flashrom-stable Rejected
Request #40743 has been Rejected by polyzen [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/QLT2AOG2BS3PIA46SKS54OTJOONNL4R7 [1] https://aur.archlinux.org/account/polyzen/
[PRQ#42998] Merge Request for gnat-gps Accepted
Request #42998 has been Accepted by polyzen [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/HS7IA3ZW7VHCGP6CK5UDZCE5FJKXQ5TG [1] https://aur.archlinux.org/account/polyzen/
[PRQ#64262] Orphan Request for badlion-client Rejected
Request #64262 has been Rejected by Muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/5PIPPRXY5P3JBZI5NRSYJOOK4Z353UWO [1] https://aur.archlinux.org/account/Muflone/
[PRQ#40000] Orphan Request for firefox-esr Accepted
Request #4 has been Accepted by Antiz [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/572IR4ZBOROSCLNCN3RRCL3ZF5H6A7MI/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#53763] Orphan Request for nerd-fonts-fontconfig Accepted
Request #53763 has been Accepted by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/5WOYKYYAMOB5B5BT5FAUNUBI2TFUML7B [1] https://aur.archlinux.org/account/muflone/
[PRQ#42346] Merge Request for python-ffmpeg Accepted
Request #42346 has been Accepted by polyzen [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6JS2AFXZ462WITCHDWJOF3ZWO4C57GS3/ [1] https://aur.archlinux.org/account/polyzen/
[PRQ#44593] Orphan Request for norminette Rejected
Request #44593 has been Rejected by yan12125 [1]: Duplicate of https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/PYXT7X7ONGZTTSCTKKA5LA5YVG5YZXK4/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#46623] Orphan Request for xone-dkms-git Rejected
Request #46623 has been Rejected by gromit [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/MBHPNZ42XDHUUYG4XUJTKNTFTWT262BS/ [1] https://aur.archlinux.org/account/gromit/
[PRQ#64401] Orphan Request for badlion-client Rejected
Request #64401 has been Rejected by Muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/5PIPPRXY5P3JBZI5NRSYJOOK4Z353UWO [1] https://aur.archlinux.org/account/Muflone/
Arch Linux in August 2022
## devtools The code and repository has been restructured [0] as it got out of hand over time. Now it follows a clear distinction and structure with improvements in the build system. The incubating tool `diffpkg` received a lot of new features [1] that will be released shortly. The new tool helps to print differences of the current package build against the last release including file listing, pkginfo, buildinfo, diffoscope. Now it provides additional features for colored output, terminal column width and switch between side-by-side and unified output. ## archlinux-keyring The Web Key Directory (WKD) data for Arch Linux is now automatically generated from the archlinux-keyring repository upon tagging of a new version. This allows for the data to be up-to-date right after a release has been made directly from the source of truth. ## RFC We are formalizing an RFC [2] to merge the pacman repository `[community]` into `[extra]` as well as the packaging VCS location `community` into `packages`. The `[core]` repository remains limited to Developers. New Package Maintainers will be restricted to publish packages solely to `[testing]` for the first two months of their active packaging actions. ## repod The 0.2.0 release as well as subsequent patch-level releases have been made. The new releases introduce rudimentary import of package files and the writing of repository sync databases in configurable repository directories. Upcoming work will focus on establishing a framework for dealing with required steps in common packager workflows. ## buildbot A first workable proof of concept has been created which we continue to iterate over. The current state and an outline of ideas has been posted to `arch-dev-public` [3]. ## Staff We would like to welcome serebit and blakkheim among the Trusted Users [4][5]. On top we would like to welcome kgizdov to their new additional duties as Arch Linux Developers [6]. [0] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/100 [1] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/111 [2] https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/14 [3] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/SM43ASYDCWX4TWGLVBQAKYLUTBY6AK2U/ [4] https://lists.archlinux.org/pipermail/aur-general/2022-August/036929.html [5] https://lists.archlinux.org/pipermail/aur-general/2022-September/036964.html [6] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/LMW64TND44WAFTYZBJS2XIQNFEWWYMGC/ OpenPGP_signature Description: OpenPGP digital signature
Arch Linux in September 2023
## Staff We would like to welcome [Fabian Bornschein (fabiscafe)][0] as part of the Arch Linux Package Maintainer team. ## Bug weekend During the 1st to 3rd of September, we conducted a [bug weekend][1] with the aim of resolving old bugs and implementing proposed solutions. This effort not only reduced the backlog but also contributed to streamlining the upcoming bug tracker migration, resulting in the resolution of approximately 200 bugs. ## devtools We've [released devtools v1.0.4][2], concentrating on bug fixes. Additionally, we implemented unique scope names for nspawn containers, enabling them to fit within a slice hierarchy for better resource management. Also, we now generate a `.SRCINFO` file in the Git repository, simplifying the retrieval of release and source metadata. ## OCI images With the exception of the official DockerHub library image, all [Arch Linux OCI images][3] are now [signed using the built-in sigstore feature][4] in podman and can be verified through cosign. ## RFC We [proposed and accepted an RFC][5] to extend our `LDFLAGS` in order to reduce the size of relocations. You can find more details about [this RFC][5] on GitLab. By making this change, we ensure to reduce the installed size of native packages. ## systemd-boot Starting from version `254.2-1`, the systemd package includes [IA32 systemd-boot EFI binaries][6]. This change allows users with IA32 UEFI systems to opt for the more straightforward [systemd-boot][7] instead of being restricted to the Grub bootloader. ## TU bylaws In September, we discussed and implemented a [change in the Trusted User Bylaws][8]. This update migrates proposed amendments to be submitted as GitLab merge requests, streamlining our workflows and aligning with modern practices applied across our distribution. [0]: https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/thread/LL442WXF42OYPDEUPXLBX62SXDHCOQDP/ [1]: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/VOOVLEAVHFD5SRYDG6XZV3YFVGU7F6WI/ [2]: https://gitlab.archlinux.org/archlinux/devtools/-/releases/v1.0.4 [3]: https://gitlab.archlinux.org/archlinux/archlinux-docker#arch-linux-oci-images [4]: https://gitlab.archlinux.org/archlinux/archlinux-docker/-/merge_requests/77 [5]: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/23 [6]: https://bugs.archlinux.org/task/79531 [7]: https://wiki.archlinux.org/title/systemd-boot [8]: https://lists.archlinux.org/archives/list/aur-gene...@lists.archlinux.org/message/H6RKUGAY3KRAYQVD7LKAEZYZPH5HJNMP/ OpenPGP_signature.asc Description: OpenPGP digital signature
[PRQ#58628] Deletion Request for qgnomeplatform-git Rejected
Request #58628 has been Rejected by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/Q2RFYK332OKHI2MZGBRE2SKAEKE2UGAW/ [1] https://aur.archlinux.org/account/muflone/
[PRQ#37307] Orphan Request for lorien-bin Rejected
Request #37307 has been Rejected by yan12125 [1]: Duplicate of https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/NYGNCAJ66VSUI2YZOL343GBQ7H3EYUVN/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#40069] Deletion Request for apache-netbeans Rejected
Request #40069 has been Rejected by Antiz [1]: Duplicate request: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/RGHA4Z2YBC2LDH2TJEEDQ27HATAWRMIE/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#51698] Merge Request for ktermlaunch Rejected
Request #51698 has been Rejected by Antiz [1]: See https://lists.archlinux.org/hyperkitty/list/aur- reque...@lists.archlinux.org/thread/CGIBMJHFCMJZDM4P25YMCPQN4GL5KI7Q/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#40745] Deletion Request for flashrom-stable Rejected
Request #40745 has been Rejected by polyzen [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/QLT2AOG2BS3PIA46SKS54OTJOONNL4R7 [1] https://aur.archlinux.org/account/polyzen/
[PRQ#41602] Merge Request for cura-appimage-bin Accepted
Request #41602 has been Accepted by polyzen [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/WERCWFSTLCAIMG4UIYMA5NX65R4NQHBP [1] https://aur.archlinux.org/account/polyzen/
[PRQ#43382] Deletion Request for openblas-lapack Rejected
Request #43382 has been Rejected by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/IC7M5234WEYLMCQ4XWHEOYSCMH56SRKG/ [1] https://aur.archlinux.org/account/muflone/
[PRQ#46792] Deletion Request for abgx360gui Accepted
Request #46792 has been Accepted by Antiz [1]: Additional info: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6UPKB2MQTFUS6GFOR2Y426INHCXFTKKU/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#64931] Deletion Request for python2-defusedxml Rejected
Request #64931 has been Rejected by Muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/MLGVBXBI4TGEWB372UDECYSPZTRVWN3B/ [1] https://aur.archlinux.org/account/Muflone/
[PRQ#63821] Merge Request for rednukem-git Rejected
Request #63821 has been Rejected by bertptrs [1]: Duplicate request https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/UCGHJ4FYRBIWX2SZM7GS5YFEKXQVQ6X2 [1] https://aur.archlinux.org/account/bertptrs/
[PRQ#57767] Deletion Request for owncloud-app-notes-git Rejected
Request #57767 has been Rejected by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/WIEYPTGVO4VQBSOFGEJTCQMOBXP3AR2L/ [1] https://aur.archlinux.org/account/muflone/
[PRQ#40150] Deletion Request for surfshark-client Accepted
Request #40150 has been Accepted by Antiz [1]: Duplicate of https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/GFTHKOFU6XAPXISDDWPGTK3GQGQVSJFU/#GFTHKOFU6XAPXISDDWPGTK3GQGQVSJFU [1] https://aur.archlinux.org/account/Antiz/
[PRQ#41898] Orphan Request for sword25 Rejected
Request #41898 has been Rejected by gromit [1]: Maintainer responded :) https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/L66REDMALNN7W2PESDQ2BZE6NPKEGHFS/ [1] https://aur.archlinux.org/account/gromit/
[PRQ#46791] Deletion Request for abgx360 Accepted
Request #46791 has been Accepted by Antiz [1]: Additional info: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/PD4OMAROBNEEPNQQ6FV7RYFILSZOZTEQ/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#57765] Deletion Request for owncloud-app-music-git Rejected
Request #57765 has been Rejected by muflone [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/WIEYPTGVO4VQBSOFGEJTCQMOBXP3AR2L/ [1] https://aur.archlinux.org/account/muflone/
[PRQ#63721] Orphan Request for gnome-shell-git Rejected
Request #63721 has been Rejected by bertptrs [1]: Duplicate of https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/S74OOC5D2EE5D2YLNDVXWSKFH5HPOI4F [1] https://aur.archlinux.org/account/bertptrs/
[PRQ#39903] Orphan Request for libpamac-full Rejected
Request #39903 has been Rejected by Antiz [1]: Duplicate request: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/NSO2VTRU7MCDXQP22UHFO3HJBDR3NZAY/ [1] https://aur.archlinux.org/account/Antiz/
[PRQ#41412] Deletion Request for rstudio-bin Rejected
Request #41412 has been Rejected by polyzen [1]: Superseded by https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/JVAISSZXOTCSWVZAWBVVB4STVCK66BFU [1] https://aur.archlinux.org/account/polyzen/
[PRQ#42642] Orphan Request for gtk4-git Rejected
Request #42642 has been Rejected by yan12125 [1]: Duplicate of https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/HWOWVPSNBEYYOVSQKBJMP24BLQSY7II2/ [1] https://aur.archlinux.org/account/yan12125/
Why was muse-hub-bin deleted?
The most I could find was https://lists.archlinux.org/archives/list/aur-requests@lists.archlinux.org/thread/GMY6P7VMAQOQWOOKJT433FBDYQVVXI2D/#GMY6P7VMAQOQWOOKJT433FBDYQVVXI2D which didn't have an answer either
Re: Systemd service and timer for refreshing archlinux-keyring keys via WKD
On 2022-07-24 12:23:29 (+1000), Allan McRae wrote: > Not shipping keys that are marginally trusted is ideal in principle... > However we have seen it many times recently as main/master keys were > cycled. Hopefully this is less of an issue moving forward. This is > why the keyring was set up to have five main keys, to ensure packager > keys were signed by at least 3 at all times. However, not everyone > has all five main key signatures. Or even 4. In fact, according to > the web page [1], we are screwed if anything happens to Pierre's of > Florian's keys, and to a lesser extent with other keys. I am not sure > the extent that page reflects current reality, but note Pierre's key > is schedule for retirement... The likelyhood for a packager to have three signatures or more (fast) has not been very high over the past year. However, the website is also only showing the signatures correctly, if any given packager setup their current (e.g. new) key in their archweb profile. As notified about earlier [a][b] this is currently not the case and renders the overview a bit useless. Tbh, it would make more sense to automate the population of that subpage and make it completely unreliant on user input, as packagers may have more than one key at a given time. For figuring out current trust (in the yet unreleased keyring), it is possible to list keys with given trust level using `./keyringctl` (see e.g. `./keyringctl list -h`) in the archlinux-keyring repository. > (Is it correct that Giancarlo has signed zero keys? I thought they > were bought on to replace me almost a year ago!) > > [1] https://archlinux.org/master-keys/ Unfortunately yes. I have asked about this probably a dozen times and given up due to lack of action by now. > My conclusion is the reality of the keyring is not perfect. If all > packager keys were signed by all main key holders, and WKD was updated > before packages were released using a key, and if expiry dates were > extended at least 6 months in advance, and , then this would not > be an issue. That is a lot of "ifs" :) > David has put a lot of effort into the keyring to allow us to expose > these issues more easily, and has been pushing for main key holders to > increase their signing coverage, but this has not progressed at any > great rate. The service suggestion really works around limitations in > key signing activity. It would not be needed if main key holders > signed everything and packagers with keys that expire updated their > keys with extensive notice. > > > Onto the service. If the server load and privacy issues were not > issues, this would "solve" the problems above. Daily is probably too > often, even weekly/monthly would be fine. But I guess the concerns > raised mean we should focus on fixing the keyring instead (as futile > as that may seem to David currently...). After reading some of the responses (e.g. Brett's [c] and Filipe's [d]) it might make indeed more sense to envision a system in which we grab updated keys (if we need them) using pacman upon system upgrade (I guess this action can not be paired with that of pulling new keys though as that happens upon package validation AFAIK). This would lower the amount of requests significantly if no update is needed (i.e. only one HTTP request is needed to retrieve a timestamp file) and only update keys if there is a new version of the keyring data deployed to WKD (e.g. timestamp is newer, we are synchronizing the existing keys). Even if we went with the service, a timestamp file would make sense there as well. As mentioned in my reply to Brett [e] I am not sure how to achieve that in the context of pacman and I do see a configuration overhead there that needs addressing, but if you could point me in the right direction, I might be able to figure it out! :) Best, David [a] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/PID6TWOVFPDAHEVA6BWVHEVSQCBHFTHH/ [b] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/DZTBYV5QO7T3MNEAUGQCESXQAWSNITOW/ [c] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/PJ27YL4ORPEUC4PVIJOH2VYITQMXHJZ5/ [d] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/E5WU5JLOXIZKFMRTUL7ZPWBLN7LPSVE3/ [e] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/message/TGC6DREVVGTRHK5ZAZFO4F54SZIQ4KV4/ -- https://sleepmap.de signature.asc Description: PGP signature
Re: [arch-general] After upgrade
Hi, http://bfy.tw/8wi1 Regards, Ralf PS: https://lists.archlinux.org/pipermail/arch-general/2016-November/042594.html https://lists.archlinux.org/pipermail/arch-general/2016-November/042594.html
[PRQ#58905] Orphan Request for pgpgram
muflone [1] filed an orphan request for pgpgram [2]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/3QHTU4PE27EJ35SLNM2RWODRQ6MAWFOW/ [1] https://aur.archlinux.org/account/muflone/ [2] https://aur.archlinux.org/pkgbase/pgpgram/
[PRQ#37655] Orphan Request for neovim-git Rejected
Request #37655 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#37661] Orphan Request for neovim-git Rejected
Request #37661 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#37693] Orphan Request for neovim-git Rejected
Request #37693 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#37696] Orphan Request for neovim-git Rejected
Request #37696 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#37780] Orphan Request for neovim-git Rejected
Request #37780 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#37878] Orphan Request for neovim-git Rejected
Request #37878 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#38027] Orphan Request for neovim-git Rejected
Request #38027 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
Re: [PRQ#47975] Deletion Request for recipes-git
Former maintainer disowned this, and submitted their own deletion request: PRQ#52926 https://lists.archlinux.org/hyperkitty/list/aur-requests@lists.archlinux.org/thread/VGHWQHPX5JASE6FRUM5VNJELGGQIG2AI/
Re: [PRQ#50872] Orphan Request for mkxp-git
Package no longer exists. Got deleted in response to PRQ#51360. [a] [1]: https://lists.archlinux.org/hyperkitty/list/aur-requests@lists.archlinux.org/thread/KK4DDY6K3WYDHXBWVINJ4JID2K3CW4FI/
Re: About the intentionally duplicated package wechat-beta-bwrap and wechat-universal and unmaintained orginal package wechat-uos
Hi, It has been more than a month since this thread was active, and this thread is approaching 3 months old. I'm writing this to request an update about this duplicated package situation. I hope those 2 requests[a][b] are dealt with sooner than later. Arch users generally use AUR, a community driven packaging effort. But this situation really let me, a packager feel upset. I understand the fact that PMs are really busy about moderation stuffs, but that doesn't mean 2 duplicated packages, as discussed above, can live so long without being taken down. What adds on top is one of the wechat-beta-bwrap maintainer's problematic statement at PRQ#57379, taking users' mislead votes as their power. Packaging such a proprietary software and sandbox requires efforts, and that isn't worth being invested by a packager when some random package can duplicate the original one and take the votes away. Sorry for the noise there. Looking forward to an update. -- Sincerely, Kimiblock [a]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/T2NYE4D4OHPQXSOFPZXA6ARBHIQT7XZJ [b]: https://lists.archlinux.org/archives/list/aur-reque...@lists.archlinux.org/thread/WW3N5GWU2KRID4PF42OX7Y7DA37O3M5Y OpenPGP_0x42A757534D542728.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
[PRQ#58906] Orphan Request for trovotutto
muflone [1] filed an orphan request for trovotutto [2]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/23FLXOZQIIFUAOTLI44CSQWO3G6MFY5Z [1] https://aur.archlinux.org/account/muflone/ [2] https://aur.archlinux.org/pkgbase/trovotutto/
[PRQ#38054] Orphan Request for neovim-git Rejected
Request #38054 has been Rejected by yan12125 [1]: Do not submit duplicated requests https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/6X7QPY6BWU2IIB26XSKAV53LUYXFDH22/ [1] https://aur.archlinux.org/account/yan12125/
[PRQ#40677] Deletion Request for ts Rejected
Request #40677 has been Rejected by polyzen [1]: Resolved and created a merge request https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/QDZATDLM4U556J6TJ7RMQGVXPMDWYSVK/ [1] https://aur.archlinux.org/account/polyzen/
[PRQ#64799] Orphan Request for bareos Rejected
Request #64799 has been Rejected by MarsSeed [1]: Accepted by orphan request PRQ#65015. [1] [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/Z3VK3PCW4FV25NXBGMMSOOWW5BZUDZOH/ [1] https://aur.archlinux.org/account/MarsSeed/
Re: Waterfox G
Yeah, I also sent [this](https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/52JZOZ6MY5SEOJKQ3YBOPB34WZIVWKXH/) but apparently I have to do some very specific things for Mailman to recognize that as a reply.
Commit in (wkhtmltopdf)
Date: Thursday, November 17, 2022 @ 19:52:54 Author: foutrelis Revision: 1349402 Remove wkhtmltopdf; unmaintained and depends on QtWebKit https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/Z3YJQFKJT3AXDTI33SBU52C6JK75GL5X/ Deleted: wkhtmltopdf/
[PRQ#45133] Merge Request for python-requirements-language-server Rejected
Request #45133 has been Rejected by Freed [1]: Keep original name according to https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/thread/HWRXAQSPZV74SFKBEZWLSPR4JDMRNGES/ [1] https://aur.archlinux.org/account/Freed/
[PRQ#40856] Orphan Request for paru Rejected
Request #40856 has been Rejected by artafinde [1]: This has been explained in comment and in previous Requests [1]. [1]: https://lists.archlinux.org/archives/list/aur- reque...@lists.archlinux.org/message/MB5GFOSYMHTUWM2ZZMYPLCTAIRZESRWX/ [1] https://aur.archlinux.org/account/artafinde/