Re: [Rpm-ecosystem] Patch review request: zchunk patches for dnf, libsolv and librepo
On Tue, 2018-06-12 at 05:24 -0400, Neal Gompa wrote: > On Tue, Jun 12, 2018 at 5:21 AM Jonathan Dieter wrote: > > > > I've finally finished writing patches to integrate zchunk support into > > dnf/libsolv/librepo[1], and I'd greatly appreciate some code review. A > > vast majority of the code is in librepo, but libsolv has been expanded > > to support zchunk files and dnf has a tiny patch that passes the base > > cache directory to librepo to find source zchunk files to delta > > against. > > > > This is awesome, but we're missing patches for libdnf and > createrepo_c. PackageKit and microdnf rely on libdnf for all of this, > and no one can create zck rpmmd without a suitably enhanced > createrepo_c. Could you please make PRs against both for that? :) And I've done libdnf: https://github.com/rpm-software-management/libdnf/pull/478 Jonathan ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/VXD63P7HB2BGPVLU7MVKB42TNU3OFBDJ/
Re: Patch review request: zchunk patches for dnf, libsolv and librepo
On Tue, 2018-06-12 at 12:21 +0300, Jonathan Dieter wrote: > I would love to get these changes into Fedora 29, and the code is > testable now, but with only three weeks until System-Wide change > proposals are due, I'm not sure if I'm being ambitious. FWIW, I have a COPR available for F28 and Rawhide with zchunk-enabled dnf/libdnf and the supporting libraries. https://copr.fedorainfracloud.org/coprs/jdieter/dnf-zchunk/ Obviously, you'll need a zchunk-enabled repository to test it. Jonathan ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/6SICXCLNH37TIIBZOKHHN2MFE7METTOX/
Re: Fedora and PDC, road forward
On 06/12/2018 07:41 AM, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > So yesterday we held a meeting on #fedora-apps about the future of PDC in > Fedora. > We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora > Here is the gist of it: > > What do we currently store in PDC: > * modules data - the list of what modules have been built, what rpms are in > them, > and which ones are active or not. > * Stream branches, branch ownership, retirement dates (EOL/SLE) > * release/life-circle tracking >* product and product versions (fedpkg gets active Fedora and EPEL > releases > from product versions endpont) As an aside did we ever get that 'in development' addition we wanted so we could point everything still using pkgdb to pdc for release status? > * critpath boolean on packages (bodhi uses this) > * metadata from composes (RPMS/images) > * "dependency" data about which rpms depend on which other rpms and which > containers include other rpms. This is not used by anything and can be > de-prioritized, dropped. (It was originally going to be used in > Freshmaker.) > Endpoints: > * release-component-relationships > * release-components > * List of all packages: fedora-packages uses this list to know what to index. > It sets up the "for loop" from which fedora-packages pulls data from all > our > other systems. >Endpoints: >* global-components > > > After some discussion the decision we reached was: > * The "dependency" data in its current form can be dropped. It's something > we'll > need in the future but the data structure will most likely need to be > adjusted so let's just drop the existing data and worry about this later. > * The critpath boolean can just be imported into bodhi itself, especially > considering that bodhi is the only tool using this flag. ok. Note that this data changes over time, and releng needs a script to update it (or better a automatic updating of it). We might want to bring up the bigger topic of if we want to bother keeping this. The only current use of it is some rules about going stable in bodhi... are those actually useful? > * The modules data is entirely going to move into MBS > > Everything else (ie: composes metadata, release/life-circle tracking, > package/branches information) will need to find a new home. > This new home will be a new django app using the Django Rest Framework (DRF) > in > which we will import the PDC apps as needed (potentially adjusting them where > desired). > > - kellin has agreed to be the project leader for this work but needs a team to > do the actual work. > - pingou has agreed to look for said team > > > If you have any worries, questions or suggestions or if you want to join the > effort, please let us know :) I'm a little worried about Django. True, we have to maintain a version for mailman3, but it's rhel7/python3. Is this new app going to use that? Alternately if we use Fedora, we need to adjust to new Django versions pretty often (one problem we already hit with PDC). Since this is just a simple api, could we do something more simple? Thanks for leading this effort pingou!!! kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/KH6GPSYO6VHL5HENCONYOTZQZOCPJREZ/
Proposed Agenda for 2018-06-14 Infrastructure Meeting 14:00 UTC
= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-06-14 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2018-06-14) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info - your name) #topic announcements and information #info relrod PTO 9 Jun - 19 Jun # this is ongoing. #info smooge PTO 15 Jun -> 18 Jun #info Office hours = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info Nirik is on call from 2018-06-07->2018-06-19 #info Relrod is on call from 2018-06-20->2018-06-26 #info Smooge is on call from 2018-06-27->2018-07-05 #info ?? is on call from 2018-07-06->2018-07-12 #topic Flock - nirik #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=2 Go thru each ticket one by one = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/MB6FQHNWHTX73DITVSWA3Z4SXAHRLZUI/
Re: Fedora and PDC, road forward
On 06/13/2018 03:03 PM, Kevin Fenzi wrote: > ok. Note that this data changes over time, and releng needs a script to > update it (or better a automatic updating of it). Yeah there is a Bodhi ticket about this and I noted that we will need to make sure we still work with releng's script if we make the change: https://github.com/fedora-infra/bodhi/issues/2433 > We might want to bring up the bigger topic of if we want to bother > keeping this. The only current use of it is some rules about going > stable in bodhi... are those actually useful? This sounds like a policy decision, so perhaps the question could be posed to FESCo or possibly the packaging committee. It does make some intuitive sense to me that we would treat certain packages more stringently than we do others, but I don't have data to say one way or the other whether the current policies are beneficial. I will say that I would feel uncomfortable changing the policy without the blessing of a governing body. signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/UV5EB5BGLQE7KMAFPQ7AOBDAHAZNVBLE/
Re: Fedora and PDC, road forward
On Wed, 2018-06-13 at 12:03 -0700, Kevin Fenzi wrote: > On 06/12/2018 07:41 AM, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > > > So yesterday we held a meeting on #fedora-apps about the future of PDC in > > Fedora. > > We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora > > Here is the gist of it: > > > > What do we currently store in PDC: > > * modules data - the list of what modules have been built, what rpms are in > > them, > > and which ones are active or not. > > * Stream branches, branch ownership, retirement dates (EOL/SLE) > > * release/life-circle tracking > >* product and product versions (fedpkg gets active Fedora and EPEL > > releases > > from product versions endpont) > > As an aside did we ever get that 'in development' addition we wanted so > we could point everything still using pkgdb to pdc for release status? All the code got done but no-one has yet/ever put a process in place to actually populate Fedora's PDC with the appropriate data, so it's not there. Things (fedfind, gnome-software...) are still using the 'collections' JSON for now. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/NYKFJDHXPP63HKWWUZCTT5ZCZERC5AXD/
Re: Fedora and PDC, road forward
On 06/13/2018 02:50 PM, Randy Barlow wrote: > On 06/13/2018 03:03 PM, Kevin Fenzi wrote: >> ok. Note that this data changes over time, and releng needs a script to >> update it (or better a automatic updating of it). > > Yeah there is a Bodhi ticket about this and I noted that we will need to > make sure we still work with releng's script if we make the change: > > https://github.com/fedora-infra/bodhi/issues/2433 Yeah, it sure would be nice if we could just have something run in cron once a day or so and just update it. Releng has not been good about running this script often. >> We might want to bring up the bigger topic of if we want to bother >> keeping this. The only current use of it is some rules about going >> stable in bodhi... are those actually useful? > > This sounds like a policy decision, so perhaps the question could be > posed to FESCo or possibly the packaging committee. It does make some > intuitive sense to me that we would treat certain packages more > stringently than we do others, but I don't have data to say one way or > the other whether the current policies are beneficial. I will say that I > would feel uncomfortable changing the policy without the blessing of a > governing body. Yes, this is definitely something for FESCo. They made the update policy that uses it. I can take it to them, I just wanted to see if there was a general sense that it was useful and we should keep it, or it was pointless and we should drop it. Perhaps I'll post to devel about it to see what the general feeling is. kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/LHXEKIFPESJEOVMHB4V4OFMCO4H3LRHV/
Re: Fedora and PDC, road forward
On 06/13/2018 03:19 PM, Adam Williamson wrote: > On Wed, 2018-06-13 at 12:03 -0700, Kevin Fenzi wrote: >> On 06/12/2018 07:41 AM, Pierre-Yves Chibon wrote: >>> Good Morning Everyone, >>> >>> So yesterday we held a meeting on #fedora-apps about the future of PDC in >>> Fedora. >>> We kept notes in etherpad at: http://etherpad.osuosl.org/pdc_fedora >>> Here is the gist of it: >>> >>> What do we currently store in PDC: >>> * modules data - the list of what modules have been built, what rpms are in >>> them, >>> and which ones are active or not. >>> * Stream branches, branch ownership, retirement dates (EOL/SLE) >>> * release/life-circle tracking >>>* product and product versions (fedpkg gets active Fedora and EPEL >>> releases >>> from product versions endpont) >> >> As an aside did we ever get that 'in development' addition we wanted so >> we could point everything still using pkgdb to pdc for release status? > > All the code got done but no-one has yet/ever put a process in place to > actually populate Fedora's PDC with the appropriate data, so it's not > there. Things (fedfind, gnome-software...) are still using the > 'collections' JSON for now. Is that the last thing using pkgdb that we know of? It would be pretty sad to keep running pkgdb, and pdc and the new thing all at the same time. :( kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/5ALVVSZ7ZLOWGNSD3V2LETTZMHOCALJG/
