[gentoo-dev] Packages up for grabs due to retirement
Hi, due to my retirement, the following packages need a new maintainer: dev-java/boilerpipe dev-libs/grok dev-python/cfgio dev-python/disqus-python dev-python/django-openid-auth dev-python/django-opensearch dev-python/django-otp dev-python/django-otp-yubikey dev-python/django-phonenumber-field dev-python/django-two-factor-auth dev-python/ipcalc dev-python/pSQL dev-python/phonenumbers dev-python/py2neo dev-python/requests-oauthlib dev-python/shortuuid dev-python/twilio dev-python/twython dev-python/yubiotp net-analyzer/nagios-check_linux_bonding net-misc/openvpn-auth-ldap sci-biology/picard openvpn-auth-ldap, grok and django-two-factor-auth have open bugs: https://bugs.gentoo.org/buglist.cgi?email1=ercpe%40gentoo.org_to1=1=equals_format=advanced=--- Regards, Johann signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] debootstrap equivalent for Gentoo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.12.2014 03:11, Sebastian Pipping wrote: I'm wondering if there is an equivalent of debootstrap of Debian anywhere. By equivalent I mean a tool that .. I wrote gentoo-bootstrap (https://github.com/ercpe/gentoo-bootstrap) some time ago to automate the creation of Gentoo Xen DomU's at work. It can do a lot of more things (e.g. installing packages, overlays, etc.). I stopped at the works for me state, so some work might be neccessary to work for you. * I can run like command FOLDER with a chroot-able Gentoo system in FOLDER after and It only has a LVM storage backend, but a folder storage backend should by easy to implement. * for both stage3 and portage tarballs * Downloading tarball * Downloading signature file * Verifying signature * Extracting (shame on me) it doesn't do signature verification yet. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBAgAGBQJUn9rQAAoJEKCEBkJ3xQHtFVYH/AoroRwFvH6u1TYuGgxlsGAM A8siVENR8hhlIdSCBc17tI8YCD3A+u2G/duv1gygXAWHSXHtzCZm0mLg4kPhEBgp G4529V3pfyQYknN1fDQn16N4F8XPaikvOnWaEnlqtaWmTfreDgddaDiVAk5kTyrJ M0x/UjBcvw/YFM62kcrTROeVkFTv+j0Gq7mb1eMLx9NMVCogfIWJ5Iujb5Sev45d IRHDrN/I0XF3cRhdJpwwDKioxGABKhWz1JA26brDzyZNDW9SqM1tc/RR75sjw8SI AKcNLPMi4i0Y8TijttcW9fYxakDz47hY0yTxejvBjAp4s5zUOKQNVcqa6xvyigo= =0HLA -END PGP SIGNATURE-
Re: [gentoo-dev] keep a gen 2013 snapshot on mirrors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 long story short having a portage-20130126.tar.bz2 snapshot (before the EAPI 5 switch) greatly simplified the upgrade of an old server on a client. I have done the switch to the current profile+portage on many server recently and i don't think that it is neccessary to keep an old portage snapshot around. Updating from old portage versions or profiles isn't fun but it basically boils down to - - Update python to latest 2.7/3.2 - - Run python-updater and select 2.7/3.2 as the main python version - - Drop old python version - - Update Portage, layman, eix - - Switch to the current profile - - Update the rest If you switched to the new profile with an old portage too early (happens to me *twice*), you will get at some point many blockers due to EAPI=5 and have to hack either the ebuilds or update portage manually. The goal is to be able to update a device for a year. Not updating at least once a year is not supportable, and should be discouraged. I'm sorry for your pain, I really am, but I hope that it pushes you to update twice a year instead of zero times. I think that even half a year is a very long period in Gentoo. Updating the core packages (portage, openrc, udev, etc.) on a (bi-)monthly basis makes sure that you don't run in such troubles. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJShFOwAAoJEKCEBkJ3xQHtVB8H/jTp17a1nuQP8N8wajkG90/o pc353PvxW/JgRYBKBrdmWEqW0dS1wRsdbPVnZuOkWpWw4CXbXc7fTJ6gualYUx8L 6FgwsGwWRu/WpSVIvu9gYmtc+yWSPv3YBVmdi0d0KfzUU10sAZn74+0tHUKaSglE TkunxAB6YSGRYj4VC6ZfaFK38gq5owgyzNjLa90rEPY4QFuTum16Y7Jr6RKtQGa1 LuJygufXPGxasW001dUmVTyQUH+vOxF3nWWaaj92zgGf33t67GeY6MMSnwFVXnnr AYlHykYQr0RmPGmZShAnhr8B3HL7vDdm0CXzmg23noyiT67RqRXOqDJxwTw+29o= =jQEK -END PGP SIGNATURE-
Re: [gentoo-dev] Suggestion: support the Dev team with system resources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07.11.2013 21:18, Rich Freeman wrote: Seriously, though, I'd love to see these needs better supported. I think we need to start by defining what the needs actually are (less redundancy, more consistency, etc). Then we figure out how to best address them. It could be individuals donating VMs, or it might be Gentoo buying resources from any number of vendors, or it could be Gentoo going out and looking for donors. I agree with that. It's easier to decide what to do if we know what we need. A solution built by the infra team would be the best solution for the same reasons why it's better to put stuff on the devspace instead of private servers (availabilty; who can fix stuff, logins, etc). But if someone need resources and a box to play with I would happily provide an Xen instance. Just wondering: How is the AT for $minorarch done? Is it possible to run, say, mips on xen/whatever through some emulation layer or is real hardware a requirement for this archs? For the security concerns: I think these boxes should be used for testing only and not for development - every commit must be done from a box fully under the dev's control. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSfHDMAAoJEKCEBkJ3xQHt2NgH/RxKb8nQDTnpjmTjkiJs/i04 JC36jxOj/ZMSSmyayssw/lpIHVB0z3V+nypLwDZnoTR5AfqQZ2O63G2OUSQwl0MN SCHYNvrQrqxPeRmQ8SBP8VMiDK6vClgRSSnJaRAKKI+ZzpDVf5BjljRr4YeakV/t iEvVpWeFt+gRDZBdFL2mInkbJ+3QBuPU08PS2p2mdrfZ3/b046eqZBQcmjnIk2/r rfVkaQ69IzS90tvv55AM3jjGIFxa/Fh5eIw7CC/VCyhiqH2egRfTTaCfdFz4VWTs 2IWNuwK3K9hxiCxzsH+IvLtqIvNYVXHdqy/6JfcIfGdlEI7/rdk2/I8VpWaOKy0= =36Sm -END PGP SIGNATURE-
Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I do not believe we have discovered any useful pattern, other than that is seems to happen more frequently with people who do not run full world updates. I don't think that running a world update should be valid solution to solve blocking issues. At work, we have some servers with pretty ancient package-sets because with newer versions third party apps are broken. I bump parts of the systems where it's neccessary and leave the rest alone. As a result i have to deal with all kinds of strange blockers or blockers which i haven't seen for years. I'm strongly against this, but it is how it is. So i have to totally agree with mgorny on I was considering writing a news item for it but we discussed it on IRC and decided that users are really expected to be able to handle themselves, especially wrt to: 1. using 'emerge -Du @world' to upgrade their systems, 2. reading the blocker output to see that it states 'dev-python/python-exec-1' - which suggests: what if I upgrade to 1? Gentoo isn't a click-and-play distribution. I totally prefer automatic blocker resolution (as nearly all blockers can nowadays), but if something can't be solved automatically, everyone should be able to fix this manually. As long as it doesn't happen every week, i don't think that it's such a big thing. Autobuilds break, gentoo can't be installed, the distro dies. I know, sounds like I'm making something out of nothing but every time people look at the stages and notice they are months out of date we find another blog post announcing how gentoo is dead. I totally understand your point, but if i throw gentoo python-exec blocker into google, the second hit is this thread and the first post has the solution. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSdgEuAAoJEKCEBkJ3xQHtPH0H/0jZYUgYW1RB2LhSVM67dm+4 5Y76A5APck+cEnDcFBH7S5CQe93yeGwGWmgzBas8A3mvgI80d/IR1x/1iAVjZ9mW zjtC3gNGjkrqo8ciIOZUIQY4+iA+8XDtTezYGBdGn2H+LZGoqjycwT05Vf8+R06D CnlL9wyIVaY6VoA0QTSCez0EBd6Pnf7SxVwQHUwI/wt1fi4/hu8NkjFMC6QxLNQh oBCtI3P/akHrBs8GdZwaXqFTkGRdLUEF0BNljJS4TSg7mum3ZcoU2WgRj8DYL8Ty /wQX9JERjYb6hU5F6aXrJglUpJ5DKE7KESI6oDOK7DmxORMfndke1i8AKlXaKV8= =Dzg9 -END PGP SIGNATURE-
Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2013 14:51, Tom Wijsman wrote: From what I heard so far this isn't reproducible by the committer; so, is anyone else being able to reproduce this? I didn't experience this either; so, maybe this is only reproducible on a stable system? This one hit me too on several systems: up-to-date arch/~arch mixed system and stable-only systems. I haven't looked into the block that deep but removed the old one and emerged the new one. At work i have several systems now with the block - if someone needs some information, ping me on IRC or via mail. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSdQpDAAoJEKCEBkJ3xQHt58gH/18Ulp6IILZ+Y/h6vqOnVICh dMe1+GMb4tRtph5LzdqTNnziRVQvOclspPfSealgW1VJozgJvYdHaRg/vyHBMarI aMPN4FIB4xw3PcXa/pbdemVU5Mzf+jHnlIz6HRdARxFp/zg3a7DyppPhJy0gObuh 5Ah9phraKJLgdmVqDZnG+9vEgn4+2PiLd7SAadR4nY+muL+X+HExxr64xmI4t7Jk FwwyjHgDz558Dd1jZ34oilYXrtDpVcLtCp67S091e/L3lq5vdneF/pxjAkG/bTVH V9VEQKlJ6p0HFpueB57bdLEmhNLSPPwzoAjF1E24Tc+A95PwYBp35G8WW3CoPU0= =5pRK -END PGP SIGNATURE-
