[aur-general] TU Application - Robin Broda
Hello, I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. I've been an Arch user since ~2014, using it on several devices including most of my servers. I'm more or less active on IRC, very interested in open-source development[0], federated networks, & reproducible builds - and would like to increase the amount of reproducible packages in Arch. I maintain a couple of PKGBUILDs in the AUR and I'm looking to adopt more[2]. Eli Schwartz has agreed to sponsor my application. After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I would also like to potentially tackle some of the TODOs[1]. As mentioned earlier, I also plan to look into reproducibility issues and improving the infrastructure around reproducible builds (and the verification thereof). I'm available on IRC with the username 'coderobe' (Freenode), on Matrix[3] (@coderobe:cdr.li), and via e-mail - should you have questions about anything. My timezone is UTC+1. Thank you for considering. Regards, Rob [0] https://github.com/coderobe [1] https://www.archlinux.org/todo/ [2] https://aur.archlinux.org/packages/?O=0&SeB=M&K=coderobe&outdated=&SB=n&SO=a&PP=50&do_Search=Go [3] https://matrix.org/
Interestingly enough, the signature went bad after transit. This message should verify fine. Regards, Rob On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. I've been an Arch user since ~2014, using it on several devices including most of my servers. I'm more or less active on IRC, very interested in open-source development[0], federated networks, & reproducible builds - and would like to increase the amount of reproducible packages in Arch. I maintain a couple of PKGBUILDs in the AUR and I'm looking to adopt more[2].
Eli Schwartz has agreed to sponsor my application.
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I would also like to potentially tackle some of the TODOs[1]. As mentioned earlier, I also plan to look into reproducibility issues and improving the infrastructure around reproducible builds (and the verification thereof).
I'm available on IRC with the username 'coderobe' (Freenode), on Matrix[3] (@coderobe:cdr.li), and via e-mail - should you have questions about anything. My timezone is UTC+1.
Thank you for considering.
Regards, Rob
[0] https://github.com/coderobe [1] https://www.archlinux.org/todo/ [2] https://aur.archlinux.org/packages/?O=0&SeB=M&K=coderobe&outdated=&SB=n&SO=a&PP=50&do_Search=Go [3] https://matrix.org/
On 03/02/2018 11:34 AM, Robin Broda via aur-general wrote:
Interestingly enough, the signature went bad after transit. This message should verify fine.
Regards, Rob
On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. I've been an Arch user since ~2014, using it on several devices including most of my servers. I'm more or less active on IRC, very interested in open-source development[0], federated networks, & reproducible builds - and would like to increase the amount of reproducible packages in Arch. I maintain a couple of PKGBUILDs in the AUR and I'm looking to adopt more[2].
Eli Schwartz has agreed to sponsor my application.
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I would also like to potentially tackle some of the TODOs[1]. As mentioned earlier, I also plan to look into reproducibility issues and improving the infrastructure around reproducible builds (and the verification thereof).
I'm available on IRC with the username 'coderobe' (Freenode), on Matrix[3] (@coderobe:cdr.li), and via e-mail - should you have questions about anything. My timezone is UTC+1.
Thank you for considering.
Regards, Rob
[0] https://github.com/coderobe [1] https://www.archlinux.org/todo/ [2] https://aur.archlinux.org/packages/?O=0&SeB=M&K=coderobe&outdated=&SB=n&SO=a&PP=50&do_Search=Go [3] https://matrix.org/
I confirm my sponsorship, let the discussion period begin! :) -- Eli Schwartz Bug Wrangler and Trusted User
On 03/02/2018 11:50 AM, Eli Schwartz wrote:
On 03/02/2018 11:34 AM, Robin Broda via aur-general wrote:
Interestingly enough, the signature went bad after transit. This message should verify fine.
Regards, Rob
On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. I've been an Arch user since ~2014, using it on several devices including most of my servers. I'm more or less active on IRC, very interested in open-source development[0], federated networks, & reproducible builds - and would like to increase the amount of reproducible packages in Arch. I maintain a couple of PKGBUILDs in the AUR and I'm looking to adopt more[2].
Eli Schwartz has agreed to sponsor my application.
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I would also like to potentially tackle some of the TODOs[1]. As mentioned earlier, I also plan to look into reproducibility issues and improving the infrastructure around reproducible builds (and the verification thereof).
I'm available on IRC with the username 'coderobe' (Freenode), on Matrix[3] (@coderobe:cdr.li), and via e-mail - should you have questions about anything. My timezone is UTC+1.
Thank you for considering.
Regards, Rob
[0] https://github.com/coderobe [1] https://www.archlinux.org/todo/ [2] https://aur.archlinux.org/packages/?O=0&SeB=M&K=coderobe&outdated=&SB=n&SO=a&PP=50&do_Search=Go [3] https://matrix.org/
I confirm my sponsorship, let the discussion period begin! :)
Discussion period is over, time to cast your votes, everyone! https://aur.archlinux.org/tu/?id=105 -- Eli Schwartz Bug Wrangler and Trusted User
Eli Schwartz via aur-general <aur-general@archlinux.org> hat am 7. März 2018 um 22:16 geschrieben:
Discussion period is over, time to cast your votes, everyone!
I've cast my vote the moment I saw this email. Last time I didn't, I got an angry phone call from my email provider because his server crashed from the sheer amount of reminder mails. :P Alad
On 03/07/2018 05:15 PM, Alad Wenter via aur-general wrote:
Eli Schwartz via aur-general <aur-general@archlinux.org> hat am 7. März 2018 um 22:16 geschrieben:
Discussion period is over, time to cast your votes, everyone!
I've cast my vote the moment I saw this email. Last time I didn't, I got an angry phone call from my email provider because his server crashed from the sheer amount of reminder mails. :P
Alad
Please tell them to email complaints@archlinux.org -- Eli Schwartz Bug Wrangler and Trusted User
On Wed, Mar 07, 2018 at 05:21:39PM -0500, Eli Schwartz via aur-general wrote:
On 03/07/2018 05:15 PM, Alad Wenter via aur-general wrote:
Eli Schwartz via aur-general <aur-general@archlinux.org> hat am 7. März 2018 um 22:16 geschrieben:
Discussion period is over, time to cast your votes, everyone!
I've cast my vote the moment I saw this email. Last time I didn't, I got an angry phone call from my email provider because his server crashed from the sheer amount of reminder mails. :P
Alad
Please tell them to email complaints@archlinux.org
You are mistaken. The mail has been deprecated in favor of /dev/null@archlinux.org -- Morten Linderud PGP: 9C02FF419FECBE16
On 03/07/2018 05:29 PM, Morten Linderud via aur-general wrote:
On Wed, Mar 07, 2018 at 05:21:39PM -0500, Eli Schwartz via aur-general wrote:
On 03/07/2018 05:15 PM, Alad Wenter via aur-general wrote:
Eli Schwartz via aur-general <aur-general@archlinux.org> hat am 7. März 2018 um 22:16 geschrieben:
Discussion period is over, time to cast your votes, everyone!
I've cast my vote the moment I saw this email. Last time I didn't, I got an angry phone call from my email provider because his server crashed from the sheer amount of reminder mails. :P
Alad
Please tell them to email complaints@archlinux.org
You are mistaken. The mail has been deprecated in favor of /dev/null@archlinux.org
That's like saying systemd-sysvcompat is deprecated because we no longer use SysVinit. -- Eli Schwartz Bug Wrangler and Trusted User
On 07.03.2018 23:29, Morten Linderud via aur-general wrote:
Please tell them to email complaints@archlinux.org
You are mistaken. The mail has been deprecated in favor of /dev/null@archlinux.org
That has been moved to devnull@archlinux.org because that's easier to write on a phone. Florian PS: That address really exists. Not sure what you'd use it for, but it just dumps mails to /dev/null.
On 03/07/2018 04:16 PM, Eli Schwartz wrote:
Discussion period is over, time to cast your votes, everyone!
The voting period is over and the results are in! Yes No Abstain Total Voted Participation 23 8 14 45 Yes 95.74% Congratulations, Robin, and welcome to the team! I've upgraded your AUR account, and added you to the Community Packages and internal Keyring projects on the bugtracker. Take a look through the TODO list here, and make sure to take care of any outstanding items: https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines#TODO_list_f... -- Eli Schwartz Bug Wrangler and Trusted User
On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User.
Hi Robin, good luck. You can already start helping with reproducible build stuff, feel free to ask for advice in #archlinux-reproducible we have toolchain to be extended and bugs filed against upstream. find some notes related to your packages: streem + streem-git - They don't honor existing CFLAGS and LDFLAGS (later at all). For now, you can fix both with a small sed command but i recommend bringing this issue upstream as a easy PR. Always checking for respect of those flags is important. - If you touch the Makefile anyway maybe a install target with respecting PREFIX and DESTDIR would make sense. indicator-sysmonitor - 80.patch is not a unique file name per se, this is important for shared srcdir setups. a prefix using the $pkgname should be better. - /usr/bin/indicator-sysmonitor invokes stuff and imports py files provided in usr/lib. This can result in untracked file creations if the application is run as root. cache files should be created before packaging, but this should also be possible solved upstream for the make install call - sysmonitor-budgie-git and sysmonitor-appindicator-git should also provide their own non-git variants to possibly satisfy sysmonitor-budgie or sysmonitor-appindicator instead of the general shared indicator-sysmonitor provides. - just style, but in package() instead of pkgdesc="${pkgdesc} you can also simply use pkgdesc+=" glava - seems to work/build just fine with non-git glfw-x11, is the -git required? - LDFLAGS is not properly handled in Makefile leading to non -znow (and other flags) linking. should be temporarily fixed in PKGBUILD and possibly a patch submited upstream. daemontools-encore - quite weird Makefile with their conf-cc and print-cc.sh calls, anyway does not respect CFLAGS and LDFLAGS at all. should be fixed. This Makefile made me giggle :D cheers, Levente
On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. Hi Robin,
good luck. Thanks! You can already start helping with reproducible build stuff, feel free to ask for advice in #archlinux-reproducible we have toolchain to be extended and bugs filed against upstream.
find some notes related to your packages:
streem + streem-git - They don't honor existing CFLAGS and LDFLAGS (later at all). For now, you can fix both with a small sed command but i recommend bringing this issue upstream as a easy PR. Always checking for respect of those flags is important. Fixed & patch submitted upstream. - If you touch the Makefile anyway maybe a install target with respecting PREFIX and DESTDIR would make sense. I'm considering it. Right now there's no install target at all, and i don't think the maintainer has an idea about which files to install and where even. I'll keep an eye on further development either way and i'll submit a patch should a future install target not respect PREFIX and/or DESTDIR. indicator-sysmonitor - 80.patch is not a unique file name per se, this is important for shared srcdir setups. a prefix using the $pkgname should be better. Good point. Done. - /usr/bin/indicator-sysmonitor invokes stuff and imports py files provided in usr/lib. This can result in untracked file creations if the application is run as root. cache files should be created before packaging, but this should also be possible solved upstream for the make install call I'm not really sure how to fix that, i'm not that familiar with python and its cache generation. - sysmonitor-budgie-git and sysmonitor-appindicator-git should also provide their own non-git variants to possibly satisfy sysmonitor-budgie or sysmonitor-appindicator instead of the general shared indicator-sysmonitor provides. - just style, but in package() instead of pkgdesc="${pkgdesc} you can also simply use pkgdesc+=" Fixed! glava - seems to work/build just fine with non-git glfw-x11, is the -git required? You're right. I was under the impression glava used a couple of features
On 03/02/2018 06:17 PM, Levente Polyak via aur-general wrote: that weren't yet included in the release build. Fixed.
- LDFLAGS is not properly handled in Makefile leading to non -znow (and other flags) linking. should be temporarily fixed in PKGBUILD and possibly a patch submited upstream. Fixed & submitted a patch. daemontools-encore - quite weird Makefile with their conf-cc and print-cc.sh calls, anyway does not respect CFLAGS and LDFLAGS at all. should be fixed. After figuring out the flow i've added two patches to the package that address this. This Makefile made me giggle :D Yeah their "build system" certainly is uh, special - to say the least.
cheers, Levente Thanks for the feedback!
Regards, Rob
On 03/02/2018 02:09 PM, Robin Broda via aur-general wrote:
- /usr/bin/indicator-sysmonitor invokes stuff and imports py files provided in usr/lib. This can result in untracked file creations if the application is run as root. cache files should be created before packaging, but this should also be possible solved upstream for the make install call I'm not really sure how to fix that, i'm not that familiar with python and its cache generation.
You can just run: python -m compileall -d '/' "${pkgdir}/" python -O -m compileall -d '/' "${pkgdir}/" A setuptools-based build would generate .pyc and .pyo files automatically. -- Eli Schwartz Bug Wrangler and Trusted User
On 03/02/2018 08:09 PM, Robin Broda via aur-general wrote:
On 03/02/2018 06:17 PM, Levente Polyak via aur-general wrote:
find some notes related to your packages:
[...]
Thanks for the feedback!
Regards, Rob
You're welcome. BTW: How are you tracking upstream updated so you can bump your packages before someone flags them? cheers, Levente
On 03/05/2018 05:11 PM, Levente Polyak via aur-general wrote:
On 03/02/2018 08:09 PM, Robin Broda via aur-general wrote:
On 03/02/2018 06:17 PM, Levente Polyak via aur-general wrote:
find some notes related to your packages:
[...]
Thanks for the feedback!
Regards, Rob
You're welcome.
BTW: How are you tracking upstream updated so you can bump your packages before someone flags them?
cheers, Levente
The ones i've submitted the patches to notified me via email on merge/activity (GitHub default), and my current non-vcs packages don't update very frequently - so beyond occasionally checking upstream, i'm not doing anything special yet. Regards, Rob
On 03/05/2018 05:20 PM, Robin Broda via aur-general wrote:
On 03/05/2018 05:11 PM, Levente Polyak via aur-general wrote:
On 03/02/2018 08:09 PM, Robin Broda via aur-general wrote:
On 03/02/2018 06:17 PM, Levente Polyak via aur-general wrote:
find some notes related to your packages:
[...]
Thanks for the feedback!
Regards, Rob
You're welcome.
BTW: How are you tracking upstream updated so you can bump your packages before someone flags them?
cheers, Levente
The ones i've submitted the patches to notified me via email on merge/activity (GitHub default), and my current non-vcs packages don't update very frequently - so beyond occasionally checking upstream, i'm not doing anything special yet.
Regards, Rob
Hey Rob, ah I see... thanks for the fast handling of my feedback :P I would recommend taking a look at a way to track upstreams for release tarballs/tags beyond that... there is a big amount of tools to achieve this (trying not to turn this thread into an advertisement-repy-war so not mentioning any). For projects hosted on git i find it handy to have some of them observing 'git ls-remote --tags https://someurl.foo/project.git'. I recommand having something in place to track maintained packages. cheers, Levente
On 03/05/2018 05:27 PM, Levente Polyak via aur-general wrote:
On 03/05/2018 05:20 PM, Robin Broda via aur-general wrote:
On 03/05/2018 05:11 PM, Levente Polyak via aur-general wrote:
On 03/02/2018 08:09 PM, Robin Broda via aur-general wrote:
[...] You're welcome.
BTW: How are you tracking upstream updated so you can bump your packages before someone flags them?
cheers, Levente
The ones i've submitted the patches to notified me via email on merge/activity (GitHub default), and my current non-vcs packages don't update very frequently - so beyond occasionally checking upstream, i'm not doing anything special yet.
Regards, Rob
Hey Rob,
ah I see... thanks for the fast handling of my feedback :P
I would recommend taking a look at a way to track upstreams for release tarballs/tags beyond that...
I've already looked into doing that in the future when maintaining active non-vcs packages.
there is a big amount of tools to achieve this (trying not to turn this thread into an advertisement-repy-war so not mentioning any).
For most software, curl & git will probably suffice i think.
For projects hosted on git i find it handy to have some of them observing 'git ls-remote --tags https://someurl.foo/project.git'.
I recommand having something in place to track maintained packages.
cheers, Levente
Oh yeah definitely. Regards, Rob
On 03/02/2018 05:16 PM, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User. I've been an Arch user since ~2014, using it on several devices including most of my servers. I'm more or less active on IRC, very interested in open-source development[0], federated networks, & reproducible builds - and would like to increase the amount of reproducible packages in Arch. I maintain a couple of PKGBUILDs in the AUR and I'm looking to adopt more[2].
Eli Schwartz has agreed to sponsor my application.
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I would also like to potentially tackle some of the TODOs[1]. As mentioned earlier, I also plan to look into reproducibility issues and improving the infrastructure around reproducible builds (and the verification thereof).
I'm available on IRC with the username 'coderobe' (Freenode), on Matrix[3] (@coderobe:cdr.li), and via e-mail - should you have questions about anything. My timezone is UTC+1.
Thank you for considering.
Regards, Rob
[0] https://github.com/coderobe [1] https://www.archlinux.org/todo/ [2] https://aur.archlinux.org/packages/?O=0&SeB=M&K=coderobe&outdated=&SB=n&SO=a&PP=50&do_Search=Go [3] https://matrix.org/
Hi Robin, I might be wrong, but dont we require to have at least 10 votes on AUR to move a package to [community]? In this case none of your packges has more than 6 votes at the time of writing this. There is also a rule about >=1% popularity on pkgstats, but it seems every package has at least 1%? Or does this TU application count as a proposol on which 3 TUs must aggree? Are those rules even up to date? This is somehow offtopic, the TU application just made me wonder about it. To me it looks like those rules are outdated and in the end everyone can move whatever they want to [community]. https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines ~Nico
On 2018-03-03 23:50, Nico via aur-general wrote:
I might be wrong, but dont we require to have at least 10 votes on AUR to move a package to [community]? In this case none of your packges has more than 6 votes at the time of writing this. There is also a rule about >=1% popularity on pkgstats, but it seems every package has at least 1%? Or does this TU application count as a proposol on which 3 TUs must aggree?
None of this was ever a rule. Think of it as indicator whether new package would actually have some users besides the maintainer. B
On 03/03/2018 05:50 PM, Nico via aur-general wrote:
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion.
I might be wrong, but dont we require to have at least 10 votes on AUR to move a package to [community]? In this case none of your packges has more than 6 votes at the time of writing this. There is also a rule about >=1% popularity on pkgstats, but it seems every package has at least 1%? Or does this TU application count as a proposol on which 3 TUs must aggree?
Okay? rutorrent -- 126 votes psensor -- 89 votes gtkhash -- 49 votes polybar -- 87 votes Yes, streem has only 1 vote, while glava-git has only 6 + no actual stable releases... but it was also only recently uploaded and that might easily change, besides which coderobe did say "and the popularity/votes are high enough to warrant inclusion." We will most likely not be blitzed by a series of unpopular fringe-use packages. :p
In this case none of your packges has more than 6 votes at the time of writing this.
It sort of feels like you are incredibly focused on the packages that he has stated a desire to see in [community], which intersect with the packages which he personally maintains, to the exclusion of the rest...
Are those rules even up to date? This is somehow offtopic, the TU application just made me wonder about it. To me it looks like those rules are outdated and in the end everyone can move whatever they want to [community].
https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines
~Nico
But yeah, those rules are guidelines. They're not generally policed, for one, and probably no one can tell afterwards anyway because once the package is cleaned up from the AUR we can't really see how many votes it had. But really, the idea is to generally avoid filling the repos with packages no one other than the TU who uploaded it is actually interested in... and votes are a rough guide as to whether that is likely. -- Eli Schwartz Bug Wrangler and Trusted User
On 03/03/2018 05:50 PM, Nico via aur-general wrote:
After becoming a TU, I'd like to look into promoting a couple of packages from the AUR over time, including but not limited to `rutorrent`, `psensor`, `glava` (currently `glava-git`, waiting for tagged releases), `gtkhash`, `streem`, & `polybar` - assuming that no issues preventing the packaging (& inclusion in the repos) turn up and the popularity/votes are high enough to warrant inclusion. I might be wrong, but dont we require to have at least 10 votes on AUR to move a package to [community]? In this case none of your packges has more than 6 votes at the time of writing this. There is also a rule about >=1% popularity on pkgstats, but it seems every package has at least 1%? Or does this TU application count as a proposol on which 3 TUs must aggree? Okay?
rutorrent -- 126 votes psensor -- 89 votes gtkhash -- 49 votes polybar -- 87 votes
Yes, streem has only 1 vote, while glava-git has only 6 + no actual stable releases... but it was also only recently uploaded and that might easily change, besides which coderobe did say "and the popularity/votes are high enough to warrant inclusion." I am assuming the popularity of these packages is going to rise. The newcomer glava-git alone got most of its popularity last week iirc, and i'm expecting more over the next couple as development continues & awareness increases. I definitely don't plan to publish unused/unpopular
On 03/04/2018 03:02 PM, Eli Schwartz via aur-general wrote: packages to [community].
We will most likely not be blitzed by a series of unpopular fringe-use packages. :p
In this case none of your packges has more than 6 votes at the time of writing this. It sort of feels like you are incredibly focused on the packages that he has stated a desire to see in [community], which intersect with the packages which he personally maintains, to the exclusion of the rest...
Right. I don't plan to promote any of my AUR packages without reason. Regards, Rob
On Fri, Mar 02, 2018 at 05:16:52PM +0100, Robin Broda via aur-general wrote:
Hello,
I'm Robin 'coderobe' Broda, born in '99, and I'm writing to become a Trusted User.
[SNIP]
Yo Robin! Super happy to see you applying for TU, and I appreciate the support you have been doing on IRC. However! I think it's too early. Most of the packages mentioned doesn't have many updoots and they have frankly been added barely a month ago to the AUR. I'd love to see more AUR packages from you, and maybe that you adopt some orphan packages from community. -- Morten Linderud PGP: 9C02FF419FECBE16
participants (8)
-
Alad Wenter
-
Bartłomiej Piotrowski
-
Eli Schwartz
-
Florian Pritz
-
Levente Polyak
-
Morten Linderud
-
Nico
-
Robin Broda