Re: [arch-dev-public] Orphaned packages from arcanis
On Sat, 2020-11-21 at 20:09 +0100, Morten Linderud via arch-dev-public wrote: > scala Adopted. -- Regards, Felix Yan signature.asc Description: This is a digitally signed message part
Re: [arch-dev-public] News draft: nvidia 455.28 is incompatible with linux >= 5.9
On Mon, 2020-10-19 at 23:01 +0200, Sven-Hendrik Haase via arch-dev- public wrote: > nvidia is currently partially incompatible with linux >= 5.9 [1][2]. > While graphics should work fine, CUDA and OpenCL are broken. Users > who've already upgraded and need those features are advised to switch > to > the linux-lts kernel for the time being. > > [1] > https://forums.developer.nvidia.com/t/nvidia-driver-not-yet-supported-for-linux-kernel-5-9/157263 > [2] https://bugs.archlinux.org/task/68312 Looks good to me. Hope nvidia will fix this sooner. -- Regards, Felix Yan signature.asc Description: This is a digitally signed message part
Re: [arch-dev-public] Packages up for adoption
On Wed, 2020-10-14 at 14:39 -0300, Giancarlo Razzolini via arch-dev- public wrote: > Em outubro 14, 2020 14:31 Bartłomiej Piotrowski via arch-dev-public > escreveu: > > Hi, > > > > Due to lack of free time, I've orphaned some packages I don't want > > to > > think about: > > > > bash > > bash-completion > > chrome-gnome-shell > > expat > > gdbm > > libcap > > libffi > > libunistring > > libusb > > networkmanager-fortisslvpn > > ncurses > > openfortivpn > > readline > > texinfo > > wpa_supplicant > > > > I've also disowned some packages I've been co-maintaining with > > other > > packagers but that's not so interesting. > > > > Bart > > > > Hi, > > I have adopted both bash and bash-completion and I'm also going to > adopt > readline. But I think these packages should have at least one co- > maintainer, > given their importance, so, co-maintain away, please. Adopted expat, libcap, libffi, libunistring, libusb, ncurses, wpa_supplicant and co-maintained bash, bash-completion, readline. Please feel free to co-maintain, too. -- Regards, Felix Yan signature.asc Description: This is a digitally signed message part
Re: [arch-dev-public] Removing dependency on fontconfig/xorg-mkfontscale of font packages
I noticed that xorg-fonts-alias and xorg-fonts-encodings were still kept: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/ttf-indic-otf=104e24f18c7138d6a0a260a86465375682d4edfa If they should be removed as well, perhaps this could also be mentioned in the TODO? -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Proposal to remove PyGTK
On 3/17/20 7:15 AM, Eli Schwartz wrote: > - zbar > > Felix, the zbar package currently builds python2-zbar bindings using > pygtk. These aren't used by any package, and upstream documents support > for python3 and GObject Introspection bindings usable via > python2/python3: https://github.com/mchehab/zbar#python-widgets > > Please drop the unused pygtk bindings and build python3/gobject ones > instead. :D Thanks for the info. I have enabled gir for zbar-gtk and switched the binding to python 3 in 0.23-3. > - python2-twisted > > ported to gobject for gtk3, which should work fine in python3, maybe we > can just drop this checkdepends/optdepends and disable those tests to > not advertise its existence? Done in 19.10.0-3. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
[arch-dev-public] deepin-kwin removed from [community-testing]
There are multiple major issues with the new version 5.0.0, and upstream doesn't yet have figured them out after a month. Currently it would be better to stick with 0.1.0. -- Regards, Felix Yan
[arch-dev-public] Dropping dingo from [community]
Hi All, I have removed dingo the Google DNS-over-HTTPS client from [community]. The upstream is inactive for years and supports Google only. I would recommend dns-over-https [1] instead which has support for multiple protocols and is still actively maintained. Note that Google announced [2] yesterday that they recommend to use the newer IETF protocol (at a new endpoint), which is also the protocol of all other major DoH providers (CloudFlare, Quad9, etc). [1] https://www.archlinux.org/packages/community/x86_64/dns-over-https/ [2] https://security.googleblog.com/2019/06/google-public-dns-over-https-doh.html -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
[arch-dev-public] nodejs 12 removed from [community-testing]
Binary packages do not build as nan doesn't support the new version yet [1]. nodejs 11.15.0 has been pushed to [community] instead. [1] https://github.com/nodejs/nan/issues/849 -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Mongodb and SSPL
On 2019/1/16 下午10:35, Allan McRae via arch-dev-public wrote: > Drop the package. I have dropped the two packages (mongodb and wiredtiger) to the AUR, since I did not use MongoDB for quite some time anyway. Thanks for all the input here. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] /r/linux AMA
On 8/10/18 12:41 AM, Morten Linderud via arch-dev-public wrote: > If you are interested participating please reply to the list with the > following > information: > > * Reddit username. > * What you do. > * What Monday fits for you? * /u/felixonmars * Python, Haskell, Nodejs, Qt, KDE, DDE, Chinese i18n, VPN/Proxies, Wine, and some others. * Most Mondays Hope I'm not too late! -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Improving the package guidelines
On 06/29/2018 05:06 AM, Eli Schwartz via arch-dev-public wrote: > Also I'd like to discuss what seems to me a common misconception in > python packaging -- specifically, the use of cp -r source source-py2 and > building both separately. > > Best I can tell, this is primarily motivated by fear of py2/py3 specific > bytecode being generated, but the thing is, this bytecode is all > generated during package() inside of "$pkgdir" during the install step. > You can check the contents of the build/ directory... it just copies the > .py files and builds any ext_modules. The main reason behind this (or why I started doing this) was sometimes the tests run inside the sources tree made both versions' .pyc files into the tree itself, and finally end up in the package. I had this problem for several times and end up having the separated build directories as template for new packages. This seems not the case for most packages now, so I agree that it should be avoided. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] [core] / [extra] cleanup
On 06/23/2018 10:37 PM, Doug Newgard via arch-dev-public wrote: *Remove* - pcmciautils - Ancient technology >>> >>> Felix moved it to [extra], not sure why? So removed it from [core] >> >> Was a mistake when trying to rebuild for the BUILDINFO todo. Sorry for that. >> > > And two and a half weeks later and it's still there? I'm still waiting for a conclusion of original proposal, the other packages are still not removed either. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] [core] / [extra] cleanup
On 06/05/2018 04:01 AM, Jelle van der Waa wrote: > On 02/06/18 17:06, Jelle van der Waa wrote: >> Looking at the packages in the BUILDINFO rebuild list, I've found some >> packages which are so old that they might not longer suit [core] or our >> repos in general. So I'd like to propose that we either move or remove >> the following packages: >> >> *Remove* >> - pcmciautils - Ancient technology > > Felix moved it to [extra], not sure why? So removed it from [core] Was a mistake when trying to rebuild for the BUILDINFO todo. Sorry for that. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
Re: [arch-dev-public] Unit tests for python packages
For testing with not installed python modules, invoking setup.py commands are often preferable and addresses both PYTHONPATH and 2to3. For nosetests: Use "python setup.py nosetests" instead. For pytest: Use "python setup.py pytest" instead. Note that "python-pytest-runner" needs to be in checkdepends. There are additional common hacks if the tests need to invoke an entry points or requires the versioned distribution object. Either: 1) Installing it in a temporary place and hack PYTHONPATH/PATH. 2) Create a sitecustomize.py and add the build dir to site. (See python2-faulthandler for an example) And finally if above still didn't solve it, you may choose to skip the problematic part of the tests or use "heavier" workarounds like a venv. -- Regards, Felix Yan signature.asc Description: OpenPGP digital signature
