Re: TU Application - Antiz
On 1/3/23 22:58, Robin Candau wrote: Le 03/01/2023 à 21:29, Robin Candau a écrit : Yeah, I definitely have an issue with my PGP settings in Thunderbird. I assume this mail will have problems as well. I'm really sorry about that... I'm looking that up for the next messages! It seems like my protonmail address doesn't want to send properly signed mails for some reasons ¯\_(oO)_/¯ I'm switching to my gmail address which, hopefully, will produces a properly signed mail. Regards, Antiz (Robin C.) Can confirm it produced a valid and working signatures :) Thanks for trying to debug this :) Cheers, Levente OpenPGP_signature Description: OpenPGP digital signature
Re: TU Application - Antiz
Le 03/01/2023 à 21:29, Robin Candau a écrit : Yeah, I definitely have an issue with my PGP settings in Thunderbird. I assume this mail will have problems as well. I'm really sorry about that... I'm looking that up for the next messages! It seems like my protonmail address doesn't want to send properly signed mails for some reasons ¯\_(oO)_/¯ I'm switching to my gmail address which, hopefully, will produces a properly signed mail. Regards, Antiz (Robin C.) OpenPGP_0xD33FAA16B937F3B2.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: TU Application - Antiz
Le 03/01/2023 à 21:21, Levente Polyak a écrit : > On 1/3/23 21:16, Robin Candau wrote: >> Le 03/01/2023 à 20:37, Morten Linderud a écrit : >>> On Tue, Jan 03, 2023 at 07:10:47PM +, Robin Candau wrote: Le 03/01/2023 à 18:40, Morten Linderud a écrit : >>> Note: >>> You sent a clear text email to the list, and an encrypted email to >>> me. It seems >>> like your email client gets confused and produces an invalidly >>> signed email as a >>> result. >>> >>> I'd recommend just disabling encrypted emails when it goes over the >>> mailing >>> list. It's also very annoying to deal with encrypted emails on the >>> reciving end >>> when there is no need for it. >> Whoops... Didn't mean to. I disabled encrypted emails. >> > > First: Good luck :) Hi, thanks :) > > Hm it looks like you now also disabled signed messages all together, > which isn't really desired :D > > Also I'm not sure if its just my end, but I'm unable to verify any of > your signed emails unfortunately. > > Cheers, > Levente Yeah, I definitely have an issue with my PGP settings in Thunderbird. I assume this mail will have problems as well. I'm really sorry about that... I'm looking that up for the next messages! Regards, Antiz (Robin C.) OpenPGP_0xBE9EDC422FD6DD9B.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
Re: TU Application - Antiz
On 1/3/23 21:16, Robin Candau wrote: Le 03/01/2023 à 20:37, Morten Linderud a écrit : On Tue, Jan 03, 2023 at 07:10:47PM +, Robin Candau wrote: Le 03/01/2023 à 18:40, Morten Linderud a écrit : Note: You sent a clear text email to the list, and an encrypted email to me. It seems like your email client gets confused and produces an invalidly signed email as a result. I'd recommend just disabling encrypted emails when it goes over the mailing list. It's also very annoying to deal with encrypted emails on the reciving end when there is no need for it. Whoops... Didn't mean to. I disabled encrypted emails. First: Good luck :) Hm it looks like you now also disabled signed messages all together, which isn't really desired :D Also I'm not sure if its just my end, but I'm unable to verify any of your signed emails unfortunately. Cheers, Levente OpenPGP_signature Description: OpenPGP digital signature
Re: TU Application - Antiz
Le 03/01/2023 à 20:37, Morten Linderud a écrit :
> On Tue, Jan 03, 2023 at 07:10:47PM +, Robin Candau wrote:
>> Le 03/01/2023 à 18:40, Morten Linderud a écrit :
>>
>>> I looked over them and they generally seem fine. The only weird part I have
>>> found is this install script that symlinks `/usr/bin/clipboard` to
>>> `/usr/bin/cb`
>>> in 3 packages. Why did you pick this solution?
>>>
>>> https://aur.archlinux.org/cgit/aur.git/tree/clipboard.install?h=clipboard
>> This is something originally done by upstream in the Cmake build
>> instructions file [1] since this is how upstream decided to handle the
>> possibility to run both the `clipboard` and `cb` command.
>> Obviously, it results as a permission issue when built with `makepkg` (since
>> it tries to modify something outside of the `pkgdir`) preventing me to deal
>> with that directly in the PKGBUILD as well. So to stay as close as possible
>> to the upstream packaging method I deported that symlink instruction to a
>> post install script.
>>
>> I imagine there's certainly a more elegant way to deal with this symlink,
>> I'll look into it.
> https://pkgbuild.vdwaa.nl/?q=ln%20-s=nope=nope===
>
> Generally you can do something like
>
> ln -s "/usr/bin/old_name" "${pkgdir}/usr/bin/new_name"
Well... I guess it's always the easiest solutions that are the hardest
to find in the first place, right? :p
I don't know how I missed that to be honest... Anyway, thanks a lot. I
made the associated corrections on the clipboard* PKGBUILDs!
As a TU, I'm looking forward to help with the AUR moderation (reviewing
PKGBUILDs, answering AUR related questions and handling AUR requests).
I'd also be interested in moving the following AUR packages to Community:
[snip]
- protonmail-bridge
>>> Is this covered under the "protonmail" trademark? Can we redistribute this
>>> with
>>> the name "protonmail"? Is there any other terms or restrictions on this?
>> It is indeed copyrighted under the "Proton AG" trademark, but the
>> protonmail-bridge app itself is distributed (and allowed to be
>> redistributed/modified) under the GPL3 license [3] so I'd say we should be
>> allowed to redistribute it with the name "protonmail"? I didn't thought
>> about that (yet) to be honest but I'll search deeper into it if I ever have
>> the chance to move it to community.
> GPL3 doesn't give any permissions to trademarks of the project. Generally this
> isn't a problem since few GPL licensed projects are written by companies and
> have trademarks registered.
>
> This is something that can be explored when it becomes relevant :)
>
>>> A few of these have two maintainers already, is there any orphaned packages
>>> you
>>> would like to maintain in the repositories?
>>> Keep in mind that any packages in [extra] is not accessible to TUs
>>> currently,
>>> but the plan is for this to change.
>> Indeed, my bad. Here's a stripped-down list of packages that only have one
>> maintainer currently:
>>
>> - glow
>> - xautolock
>> - hq
>> - hexchat
>> - zathura suite (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf,
>> zathura-pdf-poppler, zathura-ps)
>> - icewm
>> - firewalld
>> - picom
>> - notification-daemon
>> - blueman
>> - redshift
>> - gsimplecal
>> - tint2
>> - feh
>>
>> I haven't found any packages I personally use or would want to maintain in
>> the community/extra's orphaned packages at first glance to be honest, but I
>> could still adopt some if needed.
>> As I said, my primary goal with this application is to contribute/help
>> further :)
> There are no rules that says you can't have more than 2 maintainers, but we
> try
> to always keep two maintainers on any given package. Generally it's better to
> adopt a package with one maintainer then adopting a package with two
> maintainers. It spreads out the work.
>
> You'll always find something to adopt if you later anyways :)
Fair enough.
>
> Note:
> You sent a clear text email to the list, and an encrypted email to me. It
> seems
> like your email client gets confused and produces an invalidly signed email
> as a
> result.
>
> I'd recommend just disabling encrypted emails when it goes over the mailing
> list. It's also very annoying to deal with encrypted emails on the reciving
> end
> when there is no need for it.
Whoops... Didn't mean to. I disabled encrypted emails.
Regards,
Antiz (Robin C.)
Re: TU Application - Antiz
On Tue, Jan 03, 2023 at 07:10:47PM +, Robin Candau wrote:
> Le 03/01/2023 à 18:40, Morten Linderud a écrit :
>
> > I looked over them and they generally seem fine. The only weird part I have
> > found is this install script that symlinks `/usr/bin/clipboard` to
> > `/usr/bin/cb`
> > in 3 packages. Why did you pick this solution?
> >
> > https://aur.archlinux.org/cgit/aur.git/tree/clipboard.install?h=clipboard
>
> This is something originally done by upstream in the Cmake build
> instructions file [1] since this is how upstream decided to handle the
> possibility to run both the `clipboard` and `cb` command.
> Obviously, it results as a permission issue when built with `makepkg` (since
> it tries to modify something outside of the `pkgdir`) preventing me to deal
> with that directly in the PKGBUILD as well. So to stay as close as possible
> to the upstream packaging method I deported that symlink instruction to a
> post install script.
>
> I imagine there's certainly a more elegant way to deal with this symlink,
> I'll look into it.
https://pkgbuild.vdwaa.nl/?q=ln%20-s=nope=nope===
Generally you can do something like
ln -s "/usr/bin/old_name" "${pkgdir}/usr/bin/new_name"
> > > As a TU, I'm looking forward to help with the AUR moderation (reviewing
> > > PKGBUILDs, answering AUR related questions and handling AUR requests).
> > >
> > > I'd also be interested in moving the following AUR packages to Community:
> > >
> > > [snip]
> > >
> > > - protonmail-bridge
> > Is this covered under the "protonmail" trademark? Can we redistribute this
> > with
> > the name "protonmail"? Is there any other terms or restrictions on this?
>
> It is indeed copyrighted under the "Proton AG" trademark, but the
> protonmail-bridge app itself is distributed (and allowed to be
> redistributed/modified) under the GPL3 license [3] so I'd say we should be
> allowed to redistribute it with the name "protonmail"? I didn't thought
> about that (yet) to be honest but I'll search deeper into it if I ever have
> the chance to move it to community.
GPL3 doesn't give any permissions to trademarks of the project. Generally this
isn't a problem since few GPL licensed projects are written by companies and
have trademarks registered.
This is something that can be explored when it becomes relevant :)
> > A few of these have two maintainers already, is there any orphaned packages
> > you
> > would like to maintain in the repositories?
> > Keep in mind that any packages in [extra] is not accessible to TUs
> > currently,
> > but the plan is for this to change.
>
> Indeed, my bad. Here's a stripped-down list of packages that only have one
> maintainer currently:
>
> - glow
> - xautolock
> - hq
> - hexchat
> - zathura suite (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf,
> zathura-pdf-poppler, zathura-ps)
> - icewm
> - firewalld
> - picom
> - notification-daemon
> - blueman
> - redshift
> - gsimplecal
> - tint2
> - feh
>
> I haven't found any packages I personally use or would want to maintain in
> the community/extra's orphaned packages at first glance to be honest, but I
> could still adopt some if needed.
> As I said, my primary goal with this application is to contribute/help
> further :)
There are no rules that says you can't have more than 2 maintainers, but we try
to always keep two maintainers on any given package. Generally it's better to
adopt a package with one maintainer then adopting a package with two
maintainers. It spreads out the work.
You'll always find something to adopt if you later anyways :)
Note:
You sent a clear text email to the list, and an encrypted email to me. It seems
like your email client gets confused and produces an invalidly signed email as a
result.
I'd recommend just disabling encrypted emails when it goes over the mailing
list. It's also very annoying to deal with encrypted emails on the reciving end
when there is no need for it.
--
Morten Linderud
PGP: 9C02FF419FECBE16
signature.asc
Description: PGP signature
Re: TU Application - Antiz
Le 03/01/2023 à 18:40, Morten Linderud a écrit : > On Tue, Jan 03, 2023 at 11:03:07AM +, Robin Candau wrote: >> Hello, > Yo, Hi >> My name's Robin Candau and I'd like to apply to become a Trusted User. >> My sponsors are Leonidas Spyropoulos and T.J. Townsend >> . > Thanks for you application and good luck! Thanks! >> - I maintain some packages on the AUR. > I looked over them and they generally seem fine. The only weird part I have > found is this install script that symlinks `/usr/bin/clipboard` to > `/usr/bin/cb` > in 3 packages. Why did you pick this solution? > > https://aur.archlinux.org/cgit/aur.git/tree/clipboard.install?h=clipboard This is something originally done by upstream in the Cmake build instructions file [1] since this is how upstream decided to handle the possibility to run both the `clipboard` and `cb` command. Obviously, it results as a permission issue when built with `makepkg` (since it tries to modify something outside of the `pkgdir`) preventing me to deal with that directly in the PKGBUILD as well. So to stay as close as possible to the upstream packaging method I deported that symlink instruction to a post install script. I imagine there's certainly a more elegant way to deal with this symlink, I'll look into it. >> - More recently, I've been working with Rudra Saraswat (the Ubuntu >> Unity project lead) to help him properly packaging the Unity desktop >> environment for Arch (this is still a WIP) [5]. > Nice, I looked over the original packaging and was disappointed in the > package quality. Hopefully it will shape up nicely in the future. Yeah, I left a comment on the AUR web page of the initial Unity package (which has been deleted since then) to point out what could/should be improved regarding the packaging guidelines/best-practices and eventually offer my help to Rudra to properly package Unity for Arch; and this is how we started to work together on this. For the moment, all of the Unity packages has been moved to a dedicated pacman repo [2]. As I said, this is still a WIP I'm looking forward to continue on with Rudra. Hopefully it will shape up nicely in the future, indeed :) >> As a TU, I'm looking forward to help with the AUR moderation (reviewing >> PKGBUILDs, answering AUR related questions and handling AUR requests). >> >> I'd also be interested in moving the following AUR packages to Community: >> >> [snip] >> >> - protonmail-bridge > Is this covered under the "protonmail" trademark? Can we redistribute this > with > the name "protonmail"? Is there any other terms or restrictions on this? It is indeed copyrighted under the "Proton AG" trademark, but the protonmail-bridge app itself is distributed (and allowed to be redistributed/modified) under the GPL3 license [3] so I'd say we should be allowed to redistribute it with the name "protonmail"? I didn't thought about that (yet) to be honest but I'll search deeper into it if I ever have the chance to move it to community. >> - unrar-free (which I currently maintain) > I had similar concerns with `unrar`, but it seems like Fedora and Ubuntu is > packaging this. I'd assume this should be safe then. > > https://repology.org/project/unrar-free/versions Indeed, this one is already packaged by several other distributions, so it should be fine. >> Finally, those are the packages I use and/or I'd be interested in >> (co-)maintaining in Community: >> - glow >> - flameshot >> - xautolock >> - numlockx >> - playerctl >> - autorandr >> - hq >> - hexchat >> - pacman-contrib >> - zathura* (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf, >> zathura-pdf-poppler, zathura-ps) >> - tmux >> - icewm >> - firewalld >> - picom >> - notification-daemon >> - blueman >> - redshift >> - xautolock >> - gsimplecal >> - tint2 >> - feh > A few of these have two maintainers already, is there any orphaned packages > you > would like to maintain in the repositories? > Keep in mind that any packages in [extra] is not accessible to TUs currently, > but the plan is for this to change. Indeed, my bad. Here's a stripped-down list of packages that only have one maintainer currently: - glow - xautolock - hq - hexchat - zathura suite (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf, zathura-pdf-poppler, zathura-ps) - icewm - firewalld - picom - notification-daemon - blueman - redshift - gsimplecal - tint2 - feh I haven't found any packages I personally use or would want to maintain in the community/extra's orphaned packages at first glance to be honest, but I could still adopt some if needed. As I said, my primary goal with this application is to contribute/help further :) [1] https://github.com/Slackadays/Clipboard/blob/ab064974c931f49d84caa7d512178f4b2ec126db/CMakeLists.txt#L114 [2] https://unity.ruds.io/arch-unity/ [3] https://github.com/ProtonMail/proton-bridge/blob/master/COPYING_NOTES.md Regards, Antiz (Robin C.) OpenPGP_0xBE9EDC422FD6DD9B.asc Description: application/pgp-keys OpenPGP_signature Description: PGP
proble installing Skychart
Hello I'm pretty new on Arch linux. Already installed AUR packages. I'm experiencing problem installing SKYCHART link: https://aur.archlinux.org/packages/skychart Installed separately the two missed dependencies - libpasastro - xplanet Received these errors on compiling skychart -- Compiling bgrafreetype.pas bgrafreetype.pas(31,60) Fatal: Can't find unit EasyLazFreeType used by BGRAFreeType Fatal: Compilation aborted make[3]: *** [Makefile:1270: bgrabitmappack_nogl.ppu] Error 1 make[3]: Leaving directory '/home/carlo/skychart/src/skychart-4.2.1-4073-src/skychart/component/bgrabitmap' make[2]: *** [Makefile:2188: bgrabitmap_all] Error 2 make[2]: Leaving directory '/home/carlo/skychart/src/skychart-4.2.1-4073-src/skychart/component' make[1]: *** [Makefile:1731: component_all] Error 2 make[1]: Leaving directory '/home/carlo/skychart/src/skychart-4.2.1-4073-src/skychart' make: *** [Makefile:1593: skychart_all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... -- help is appreciated thanks a lot Carlo -- Carlo Vinante Presidente Associazione Astronomica Euganea Fiduciario Regionale Nord Est UAI Sezione Comete & Progetto CARA UAI ARI Sez. Padova - IZ3XTL
Re: TU Application - Antiz
On Tue, Jan 03, 2023 at 11:03:07AM +, Robin Candau wrote: > Hello, Yo, > My name's Robin Candau and I'd like to apply to become a Trusted User. > My sponsors are Leonidas Spyropoulos and T.J. Townsend > . Thanks for you application and good luck! > - I maintain some packages on the AUR. I looked over them and they generally seem fine. The only weird part I have found is this install script that symlinks `/usr/bin/clipboard` to `/usr/bin/cb` in 3 packages. Why did you pick this solution? https://aur.archlinux.org/cgit/aur.git/tree/clipboard.install?h=clipboard > - More recently, I've been working with Rudra Saraswat (the Ubuntu > Unity project lead) to help him properly packaging the Unity desktop > environment for Arch (this is still a WIP) [5]. Nice, I looked over the original packaging and was disappointed in the package quality. Hopefully it will shape up nicely in the future. > As a TU, I'm looking forward to help with the AUR moderation (reviewing > PKGBUILDs, answering AUR related questions and handling AUR requests). > > I'd also be interested in moving the following AUR packages to Community: > > [snip] > > - protonmail-bridge Is this covered under the "protonmail" trademark? Can we redistribute this with the name "protonmail"? Is there any other terms or restrictions on this? > - unrar-free (which I currently maintain) I had similar concerns with `unrar`, but it seems like Fedora and Ubuntu is packaging this. I'd assume this should be safe then. https://repology.org/project/unrar-free/versions > Finally, those are the packages I use and/or I'd be interested in > (co-)maintaining in Community: > - glow > - flameshot > - xautolock > - numlockx > - playerctl > - autorandr > - hq > - hexchat > - pacman-contrib > - zathura* (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf, > zathura-pdf-poppler, zathura-ps) > - tmux > - icewm > - firewalld > - picom > - notification-daemon > - blueman > - redshift > - xautolock > - gsimplecal > - tint2 > - feh A few of these have two maintainers already, is there any orphaned packages you would like to maintain in the repositories? Keep in mind that any packages in [extra] is not accessible to TUs currently, but the plan is for this to change. -- Morten Linderud PGP: 9C02FF419FECBE16 signature.asc Description: PGP signature
Re: TU Application - Antiz
On 03/01/2023 18:14, T.J. Townsend wrote: > Confirming my sponsorship too. This marks the beggining of the discussion period which will conclude in two weeks on 2023-01-18. The voting will start on the same day and conclude on 2023-01-25. -- Leonidas Spyropoulos PGP: 59E43E106B247368 OpenPGP_0x59E43E106B247368.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: TU Application - Antiz
> Hello, > > My name's Robin Candau and I'd like to apply to become a Trusted User. > My sponsors are Leonidas Spyropoulos and T.J. Townsend > . > > I'm looking forward to contribute more to Arch Linux. > Thanks for reading my application! Confirming my sponsorship too. signature.asc Description: PGP signature
Re: TU Application - Antiz
On 03/01/2023 13:03, Robin Candau wrote: > Hello, > > My name's Robin Candau and I'd like to apply to become a Trusted User. > My sponsors are Leonidas Spyropoulos and T.J. Townsend > . I confirm my sponsorship. Cheers, -- Leonidas Spyropoulos PGP: 59E43E106B247368 OpenPGP_0x59E43E106B247368.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
TU Application - Antiz
Hello, My name's Robin Candau and I'd like to apply to become a Trusted User. My sponsors are Leonidas Spyropoulos and T.J. Townsend . I'm 26 years old and I live in France. I'm working as a Linux system, Infrastructure and DevOps engineer. I've been using Linux for the last decade and been using Arch for a few years now. During my Arch journey, I started contributing to it in various ways: - I subscribed to every "major" mailing lists and reply to users' questions in it from time to time (mostly in the AUR-General one). - I'm answering questions on the Arch subreddit (even though I'm aware it is not an official Arch resource) and on the IRC channels from time to time. I'm a bit less present on IRC though, but I'm still passing by here and there. - I contribute to some wiki pages. - I maintain some packages on the AUR. - I'm reviewing PKGBUILDs (both on aurweb and the AUR-General mailing list). - I'm a member of the "Arch Testing Team" and I'm regularly testing and signing off packages. - I made rare contributions to the Arch DevOps Gitlab's issues (this is something I'd like to do more in the future, I just haven't take the time yet). Since I started contributing to Arch, my interest for it kept growing and I'd like to do more. This is why I'm applying to become a TU through this mail. For the minimum requirements: - I'm fine with shell scripting. - I maintain a few packages in the AUR with what I think are high-quality/clean PKGBUILDs [1]. - I'm doing basic community involvement (as stated earlier). - I can Google. - Aside from Arch, I've been involved in a few open-source projects: - My own open-source projects are hosted on GitHub [2]. - I'm a package and infrastructure maintainer for Crystal-Linux [3] which is an Arch based distribution that promotes the use of current and modern technologies and that brings an alternative to some widely used software through its own tools such as "jade" (the Crystal Linux's installer) or "amethyst" (the Crystal Linux's pacman wrapper and AUR helper). I'm basically maintaining the Crystal's specific PKGBUILDs [4] and helping them with infrastructure stuff. - More recently, I've been working with Rudra Saraswat (the Ubuntu Unity project lead) to help him properly packaging the Unity desktop environment for Arch (this is still a WIP) [5]. As a TU, I'm looking forward to help with the AUR moderation (reviewing PKGBUILDs, answering AUR related questions and handling AUR requests). I'd also be interested in moving the following AUR packages to Community: - protonmail-bridge - distrobox - unrar-free (which I currently maintain) - ddgr (which I currently maintain) Finally, those are the packages I use and/or I'd be interested in (co-)maintaining in Community: - glow - flameshot - xautolock - numlockx - playerctl - autorandr - hq - hexchat - pacman-contrib - zathura* (zathura, zathura-cb, zathura-djvu, zathura-pdf-mupdf, zathura-pdf-poppler, zathura-ps) - tmux - icewm - firewalld - picom - notification-daemon - blueman - redshift - xautolock - gsimplecal - tint2 - feh Globally, my package interests are CLI tools and GTK apps, but I can maintain anything else if needed. My primary goal is to help/contribute :) Also, even though it has no direct link with the TU position, I'm willing to take the time to bring some help and contributions to the DevOps side of things in the future, as stated in the beginning of my application. I'm looking forward to contribute more to Arch Linux. Thanks for reading my application! [1] https://aur.archlinux.org/packages?O=0=M=Antiz==p=d=50=Go [2] https://github.com/Antiz96 [3] https://getcryst.al/site [4] https://git.getcryst.al/crystal/pkgbuilds [5] https://gitlab.com/users/Antiz96/activity Regards, Robin Candau - Antiz OpenPGP_0xBE9EDC422FD6DD9B.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
