Re: [arch-general] Multi-threaded mkinitpcio
Em abril 4, 2020 12:13 Jelle van der Waa escreveu: multi-threaded compression does not create a predictable reproducible archive (for xz/zstd). Zstd is multi-thread safe, as far as I know, xz is not. But the kernel does not support zstd. Sure, has nothing to do with reproducibility however. It has, because lzop is the only algorithm that produces unreproducible builds due to them adding their own timestamp, which there's no flag to remove. Of course lzop will be faster than xz, but mkinitcpio's default is gz, which should be comparable, at least in speed, with lzop. Regards, Giancarlo Razzolini pgpW22pQ7tQDH.pgp Description: PGP signature
Re: [arch-general] Problem with packaging pyxdg and xdg from PyPI
On 4/4/20 7:32 PM, Ricardo Band wrote: > Ahoi, > > I maintain a tool called virtualfish [1] on the AUR. It is writte in > python and one dependency of it is called xdg [2]. It is not packaged > in archlinux so I would just do that on the AUR. Problem is there > already is a package in archlinux extra which is called python-xdg [3]. > That package includes a python library called pyxdg [4] which does > nearly the same as xdg but is still a different library. > > In my opinion the arch packages python-xdg and python2-xdg have an > incorrect name. They should be called python-pyxdg so the xdg module > could be packaged under python-xdg. > > The naming schema with the python-py prefix looks odd but isn't new. It > is already used in the pyserial [5] package. > > How do we solve this problem? Also keep in mind that since both provide 'import xdg', renaming the package wouldn't let you install both of them. Also when renaming a repository package, we must add provides/conflicts/replaces which means a new python-xdg package would never be found from the AUR, and if manually installed, would prompt to replace it with the repo package on every singe pacman -Syu. Fragmentation is fun. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] Problem with packaging pyxdg and xdg from PyPI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thx, I hopped on the issue. Let's hope this can get resolved soon. Seems like an easy fix. - -- Greetings Ricardo Band https:// www.ricardo.band mailto:// em...@ricardo.band xmpp://jab...@ricardo.band -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEhyzgFNiV8yZuI1T5Gp1lfQa1gg4FAl6J+wYACgkQGp1lfQa1 gg5VcA/8CfHi9OJkJbx3fb3KF0kX5pcCBs1NBGjQswbaMk8Cu17RjrzJed6AJC7L dmhvOwOQ9CInCu6cSYtOAtz/rYuPfkBYgUrkZBkNQId/jOHWNqNS5LW5z+6qYKtc mgW9EyYqxx8k5MLZnnzU6ST6dMmE7KB2oCSqUKeUI7JghvvFJA8zXWmtuuoDYpLu ZFmBht2xmJnp4jarEWniWuOX9vxV46yPN8NT3cPVIRE5mclEAm5mn3fW9mJw7KiU +GsWEQl5PBCbk8ul4nTYLoKPFKAzXIrVFE/KaRXbqD/EkaZigSiPegAA+m3xx9bD Pl0XDJVfjQzZeeDHeinT41oCvNqKAvpW8dgyb2Dq7hHYiFKlXu42L/rT6kYofMRQ SN/GB5CrnWKpOury6RvwoOy7evBfeUaVvygXy/0J/H1Z1kBBJQMXn1MC7EpBq61Y JzTi9IXqq2gXRmLOBDnPSN2e/uuSbqS6jDC16Pn9tbdxftWaDbd8ZKki+XFg1DTR iEEaOgM1XfGbAySFG23l6mLREDsxHzMGhzwU0cd+OlJ0+1JdfDkZ+kw/jw5Alxhm QoUk8WW7dJwh1p8JqmqD1H3I69fWUvo8wJrb/R60cbGbhdUXW+ZAEQgpz2SHQ0ys 77F7D/33gI0OdCQJkNvY6b7rEVIaZpxf63RWCPcLUdTt46wHt7I= =X0Tk -END PGP SIGNATURE-
Re: [arch-general] Problem with packaging pyxdg and xdg from PyPI
Sorry for the "payload".
Re: [arch-general] Problem with packaging pyxdg and xdg from PyPI
https://bugs.archlinux.org/task/64173 Il giorno dom 5 apr 2020 alle ore 01:32 Ricardo Band ha scritto: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Ahoi, > > I maintain a tool called virtualfish [1] on the AUR. It is writte in > python and one dependency of it is called xdg [2]. It is not packaged > in archlinux so I would just do that on the AUR. Problem is there > already is a package in archlinux extra which is called python-xdg [3]. > That package includes a python library called pyxdg [4] which does > nearly the same as xdg but is still a different library. > > In my opinion the arch packages python-xdg and python2-xdg have an > incorrect name. They should be called python-pyxdg so the xdg module > could be packaged under python-xdg. > > The naming schema with the python-py prefix looks odd but isn't new. It > is already used in the pyserial [5] package. > > How do we solve this problem? > > > [1]: https://pypi.org/project/virtualfish/ > [2]: https://pypi.org/project/xdg/ > [3]: https://www.archlinux.org/packages/extra/any/python-xdg/ > [4]: https://pypi.org/project/pyxdg/ > [5]: https://www.archlinux.org/packages/community/any/python-pyserial/ > > - -- > > Greetings > > Ricardo Band > > https:// www.ricardo.band > mailto:// em...@ricardo.band > xmpp://jab...@ricardo.band > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEhyzgFNiV8yZuI1T5Gp1lfQa1gg4FAl6JGRgACgkQGp1lfQa1 > gg76dQ/8D+4Fo3AiKoPw+CFcQsATGs7Ry+W5l8awSHzEUjrI7lcMJCFEXS2CjzxO > +LBzSpmP1p36LI/Ec/TAAc60nl3i3tmY8SZY4lPhQJDWHSo8F3az3aMCsy4TfBCa > YQRIZPzx3iMRKYEiJx8GVHiSW/GebebT4ilp4ssQjgkIrq28HT5G0rK7N7O6/Yp0 > gZHo4TlgqpOVZ8HgXfX2lVoO4O1/7isyIKtL5YMCMwbGxsFBaYxkwbahcd1FTd7A > AIC6XP3wGNZbpPEtZQGDGFd1soJ0abh1bxUsvwlgPswoEkho/HKq9L3WhbsqFS4x > wLt07/7ucpRXZ+16ajmDoLyjjhvLjUfSlO4sXi5sAwrIUYS/rbnB4L7qoUfGkyRs > KJ6e07iW+T7ZQRfNpodTs+N/RBDxUzNk5Pj5F5e7VgCWGEsUmePMG4TO5+06skIH > OH9EXrATYLUjL31077rO1WzxSKShcoZ17Z0lW8IKYut4RDG1EgUMuIH/hyydKhWj > 2VOVMjDY5PxdUtlvphSXHpdpbzGD+9n7TsAEFE3opQigayMbjBnprsUmk/ubX0Og > pHXwAs45K5g3Kqa1qY7tow8Rw5a528Tsc3+FZGAEvNj7tRlynrAS370oFnKys9Wc > gING0Q/UB2siV1LJRuExBNXLP63yezCqVqdp7LvkvodRdwL06Zg= > =4gAQ > -END PGP SIGNATURE- -- in questo cielo liquido ci tuffiamo ad ___
