Need people to help with kernel updates
Hello, For a few years, I've been handling updates of the linux-libre kernel by myself. Now I want some more people to help with this. The work itself is fairly mechanical and updates occur about once a week. It takes about 30 minutes to prepare the patches and push them to CI or send them to the mailing list. When a new major kernel version is released, then we also need to make a new kernel config file, which takes a few hours in total. There is plenty of support for the CI and QA infrastructure to build the kernels, so you don't need a powerful computer. This isn't the sort of the task that needs to be performed by a single person. The work could be spread, like most other packages in Guix. If you want to join in, please reply! Leo
Re: IDEA: missing-tests-pypi-error? condition
Hi, Munyoki Kilyungi writes: > Hi Maxim! > > Maxim Cournoyer > aliandika: > >> Hi, >> >> Munyoki Kilyungi writes: >> >>> "jgart" aliandika: >>> Hi Guixers, I was recently reviewing a patch by a contributor and was discussing the notion of preferring upstream to PyPI when tests are missing on PyPI. >>> What's the policy on this. Shouldn't we prefer >>> upstream over PyPI? Sometimes, PyPI versions lag >>> behind upstream versions. >> >> There's no written policy about it at this time, but I think it's common >> knowledge in Guix that we try hard to: >> >> 1. Unbundle dependencies (that one is documented) >> 2. Run test suites (that one isn't) >> >> We could hint at this globally in the contributing section, and perhaps >> expound with more specific details in the Python Modules contributing >> section, mentioning that when the PyPI source archive lacks tests, >> fetching from the git repository should be preferred. >> >> Another thing we could do is default to fetch from git for the Python >> importer. >> > Thanks for this info. I'm dedicating an hour of > my day from work to try to contrib to the > eco-system with Jgarte's help. What's, if I may > naively ask, the process for documenting this > knowledge? I can take a stub at trying to > document this and asking for reviews. That's a pretty cool workplace you've got :-). The process would be the same as for authoring any other changes to Guix. You'll want to 'make doc/guix.info' to test your changes (or just 'make'), and you can review the new work with 'info doc/guix.info'. 'info Texinfo' can be used as a handy reference for the Texinfo specifics. -- Thanks, Maxim
Re: IDEA: missing-tests-pypi-error? condition
Hi, Munyoki Kilyungi writes: > "jgart" aliandika: > >>> Sometimes, PyPI versions lag behind upstream versions. >> >> Hi Bonz, >> >> Yes, in my experience that has sometimes been the case because maintainers >> don't make timely releases to PyPI. >> >>> What's the policy on this. Shouldn't we prefer upstream over PyPI? >> >> Our importer works with the JSON API that PyPI provides at >> https://pypi.org/pypi/baz/json >> >> See here: >> >> https://git.savannah.gnu.org/cgit/guix.git/tree/guix/import/pypi.scm?h=master#n141 >> >> That API provides a lot of package data that GitHub does not track in a >> unified and structured way. >> > Then given the above ... >>> Adding extra glue can add unnecessary complexity. >> >> You're right. I thought about that after I sent the email with the idea ;() >> > > PyPi unless we need to use upstream is the way to > go ;) Yes, I was thinking continuing to use PyPI, but attempt to find the repository URL from PyPI's metadata and used that when generating a package definition with the pypi importer. I don't know how feasible that would be. -- Thanks, Maxim
Re: Is this a bug in guix refresh with respect to Common Lisp packages?
> These are the 7 packages: I didn't get that output from `./pre-inst-env guix refresh -l sbcl-enhanced-eval-when` I get the following: [jgart@fedora guix]$ guix refresh -l sbcl-enhanced-eval-when Building the following 1 package would ensure 7 dependent packages are rebuilt: cl-definitions-systems@2.0.1 I realize that those are all the dependents it just doesn't print from refresh -l for me for the said package. It works for python-requests though: [jgart@fedora guix]$ guix refresh -l sbcl-enhanced-eval-when Building the following 1 package would ensure 7 dependent packages are rebuilt: cl-definitions-systems@2.0.1 [jgart@fedora guix]$ guix refresh -l python-requests Building the following 633 packages would ensure 1362 dependent packages are rebuilt: sdkmanager@0.6.5 r128gain@1.0.7 borgmatic@1.7.12 patman@2023.07.02 python-canopen@2.0.0 python-behave-web-api@1.0.6 xenon@0.9.0 pwntools@4.4.0 trydiffoscope@67.0.1 greaseweazle-host-tools@1.12 docker-compose@1.29.2 cozy@1.2.1 anki@2.1.16 beancount@2.3.5 electron-cash@4.3.1 renpy@8.1.0 qgis@3.30.1 python-geoip2@2.9.0 nerd-dictation-sox-ydotool@0-1.0eb44b7 nerd-dictation-xdotool@0-1.0eb44b7 nerd-dictation-sox-wtype@0-1.0eb44b7 nerd-dictation-sox-xdotool@0-1.0eb44b7 toot@0.38.1 units@2.22 instantmusic@1.0-1.300891d curseradio@0-1.1bd4bd0 gandi.cli@1.6 pass-rotate@0.1 python-pytest-services@1.3.1 trytond-authentication-sms@6.2.0 trytond-user-role@6.2.0 trytond-ldap-authentication@6.2.1 trytond-party-relationship@6.2.0 trytond-dashboard@6.2.0 trytond-gis@6.2.0 trytond-google-maps@6.2.0 trytond-marketing-automation@6.2.1 trytond-marketing-email@6.2.0 gpodder@3.11.1 python-flask-markdown@0.3 python-flask-restx@0.5.1 python-flask-assets@2.0 python-flask-multistatic@1.0 python-flask-misaka@1.0.0 python-flask-principal@0.4.0 python-flask-oidc@1.4.0 python-flask-restful-swagger@0.20.1 python-flask-htpasswd@0.3.1 python-flask-migrate@3.1.0 python-flask-htmlmin@1.2 python-flask-seasurf@1.1.1 dynaconf@3.1.7 buku-run@0.1.1 python-flask-login@0.6.0 python-qtsass@0.4.0 python-rauth@0.7.3 python-pyega3@3.4.1 zulip-term@0.5.2 conda@22.9.0 python-flask-combo-jsonapi@1.1.0 python-wsgiproxy2@0.4.6 python-beren@0.7.0 python-pynetbox@7.2.0 python-pywinrm@0.4.1 whoogle-search@0.8.2 python-google-api-client@1.12.8 python-requests-ftp@0.3.1 python-pyfxa@0.6.0 magic-wormhole@0.12.0 python-wsgi-intercept@1.2.2 grip@4.6.1 httpie@3.2.1 hydrus-network@495 python-openai@0.28.1 python-woob@3.0 dosage@2.17 python-consul@0.6.1 nbss-upload@0.1 trytond-account-rule@6.2.1 trytond-account-move-line-grouping@6.2.0 trytond-account-de-skr03@6.2.0 trytond-account-fr@6.2.0 trytond-account-dunning-email@6.2.0 trytond-project-plan@6.2.0 trytond-party-avatar@6.2.0 trytond-attendance@6.2.0 trytond-product-price-list-parent@6.2.0 trytond-stock-location-sequence@6.2.0 trytond-stock-split@6.2.0 trytond-account-dunning-fee@6.2.0 trytond-stock-quantity-issue@6.2.1 trytond-production-split@6.2.0 trytond-stock-lot-unit@6.2.0 trytond-stock-assign-manual@6.2.0 trytond-stock-quantity-early-planning@6.2.2 trytond-account-be@6.2.0 trytond-account-invoice-correction@6.2.0 trytond-account-invoice-defer@6.2.2 trytond-account-tax-cash@6.2.0 trytond-account-statement-ofx@6.2.0 trytond-account-statement-coda@6.2.0 trytond-account-statement-aeb43@6.2.1 trytond-account-invoice-history@6.2.0 trytond-account-deposit@6.2.0 trytond-stock-product-location@6.2.0 trytond-product-classification-taxonomic@6.2.0 trytond-customs@6.2.0 trytond-product-price-list-dates@6.2.1 trytond-sale-shipment-grouping@6.2.0 trytond-sale-shipment-tolerance@6.2.0 trytond-sale-complaint@6.2.1 trytond-stock-lot-sled@6.2.0 trytond-product-image-attribute@6.2.0 trytond-sale-gift-card@6.2.0 trytond-sale-extra@6.2.0 trytond-notification-email@6.2.2 trytond-commission-waiting@6.2.1 trytond-stock-inventory-location@6.2.0 trytond-account-stock-landed-cost-weight@6.2.0 trytond-sale-secondary-unit@6.2.0 trytond-sale-discount@6.2.1 trytond-account-stock-shipment-cost@6.2.1 trytond-carrier-subdivision@6.2.0 trytond-sale-subscription-asset@6.2.0 trytond-product-cost-warehouse@6.2.1 trytond-sale-supply-production@6.2.1 trytond-analytic-sale@6.2.0 trytond-project-invoice@6.2.3 trytond-purchase-invoice-line-standalone@6.2.0 trytond-sale-stock-quantity@6.2.0 trytond-production-outsourcing@6.2.0 trytond-production-work-timesheet@6.2.0 trytond-stock-location-move@6.2.0 trytond-stock-supply-forecast@6.2.0 trytond-carrier-percentage@6.2.0 trytond-carrier-weight@6.2.0 trytond-purchase-secondary-unit@6.2.0 trytond-product-kit@6.2.2 trytond-stock-supply-day@6.2.0 trytond-analytic-purchase@6.2.0 trytond-stock-consignment@6.2.0 trytond-account-cash-rounding@6.2.0 trytond-purchase-price-list@6.2.1 trytond-purchase-amendment@6.2.1 trytond-account-tax-rule-country@6.2.0 trytond-sale-credit-limit@6.2.0 trytond-incoterm@6.2.0 trytond-account-es@6.2.0 trytond-account-payment-sepa-cfonb@6.2.0
Re: Is this a bug in guix refresh with respect to Common Lisp packages?
"jgart" writes: > make -j6 && ./pre-inst-env guix refresh -l sbcl-enhanced-eval-when > > I don't see 7 dependent packages that would be rebuilt... Just three. > > Building the following 1 package would ensure 7 dependent packages are > rebuilt: cl-definitions-systems@2.0.1 These are the 7 packages: cl-enhanced-eval-when@1.0 cl-enhanced-defclass@2.1 cl-canonicalized-initargs@2.0 cl-definitions-systems@2.0.1 sbcl-enhanced-defclass@2.1 sbcl-canonicalized-initargs@2.0 sbcl-definitions-systems@2.0.1 -- Ricardo
