Re: [aur-general] Away until January 31st
Of course. On Wed, Jan 30, 2019, 15:17 Chih-Hsuan Yen via aur-general < aur-general@archlinux.org wrote: > > > Felix Yan via aur-general 於 2019/1/30 下午8:12 寫道: > > On 2019/1/30 下午4:33, Jerome Leclanche wrote: > >> Due to more internet issues I have to extend this until Jan 4th. > >> Unfortunately this is coinciding with a new LXQt release, if someone > >> feels up to taking care of it… > > > > I have bumped the packages into [community-testing]. Let me know if I > > broke anything! > > > > Thank you very much for the efforts Felix! > > > On the other hand, Jerome, do you mind if I co-maintain LXQt-related > packages? As another LXQt developer, I'm also interested in keeping > those Arch Linux packages in a good shape. > > Best Regards, > > Chih-Hsuan Yen > >
Re: [aur-general] Away until January 31st
Felix Yan via aur-general 於 2019/1/30 下午8:12 寫道: > On 2019/1/30 下午4:33, Jerome Leclanche wrote: >> Due to more internet issues I have to extend this until Jan 4th. >> Unfortunately this is coinciding with a new LXQt release, if someone >> feels up to taking care of it… > > I have bumped the packages into [community-testing]. Let me know if I > broke anything! > Thank you very much for the efforts Felix! On the other hand, Jerome, do you mind if I co-maintain LXQt-related packages? As another LXQt developer, I'm also interested in keeping those Arch Linux packages in a good shape. Best Regards, Chih-Hsuan Yen signature.asc Description: OpenPGP digital signature
Re: [aur-general] Away until January 31st
On 2019/1/30 下午4:33, Jerome Leclanche wrote: > Due to more internet issues I have to extend this until Jan 4th. > Unfortunately this is coinciding with a new LXQt release, if someone > feels up to taking care of it… I have bumped the packages into [community-testing]. Let me know if I broke anything! -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [aur-general] Away until January 31st
Due to more internet issues I have to extend this until Jan 4th. Unfortunately this is coinciding with a new LXQt release, if someone feels up to taking care of it… J. Leclanche On Fri, Jan 25, 2019 at 4:47 PM Bruno Pagani wrote: > > Le 24/01/2019 à 23:33, Jerome Leclanche a écrit : > > Hey folks, > > > > I'm on a pretty awful laptop + internet right now and unable to attend > > to TU duties until end of the month. > > I'll note that I'm unable to even load https://aur.archlinux.org -- it > > seems to hang at the TLSv1.3 handshake on my 4G (tethered or not). > > This has been the case since forever but it's now an issue. I > > initially thought it was just down. Then thought it was on my side but > > the rest of the archlinux domains work fine. > > Any idea what could cause this? > > Some middlebox not being updated to work with TLSv1.3? Though I thought > that they added some layers of compatibility for this exact case, so… > >
Re: [aur-general] Away until January 31st
Le 24/01/2019 à 23:33, Jerome Leclanche a écrit : > Hey folks, > > I'm on a pretty awful laptop + internet right now and unable to attend > to TU duties until end of the month. > I'll note that I'm unable to even load https://aur.archlinux.org -- it > seems to hang at the TLSv1.3 handshake on my 4G (tethered or not). > This has been the case since forever but it's now an issue. I > initially thought it was just down. Then thought it was on my side but > the rest of the archlinux domains work fine. > Any idea what could cause this? Some middlebox not being updated to work with TLSv1.3? Though I thought that they added some layers of compatibility for this exact case, so… signature.asc Description: OpenPGP digital signature
[aur-general] Away until January 31st
Hey folks, I'm on a pretty awful laptop + internet right now and unable to attend to TU duties until end of the month. I'll note that I'm unable to even load https://aur.archlinux.org -- it seems to hang at the TLSv1.3 handshake on my 4G (tethered or not). This has been the case since forever but it's now an issue. I initially thought it was just down. Then thought it was on my side but the rest of the archlinux domains work fine. Any idea what could cause this? J. Leclanche
