July 2013 - rel-eng - Fedora Mailing-Lists

#5654: Report full image creation for quality website updates

by Fedora Release Engineering

#5654: Report full image creation for quality website updates -----------------------------+------------------------ Reporter: shaiton | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hi, we already discussed a bit about this issues with nirik, before the F19 release day. However, yesterday was worse as expected. Please see the number of fixes: https://git.fedorahosted.org/cgit/fedora-web.git/log/ (7 important fixes after the merge into prod aedf487eb). == Summary of major issues: * http://torrent.fedoraproject.org/spins/ changed to http://torrent.fedoraproject.org/torrents and we had no idea about this. * The naming scheme of the file changed which introduced a bug in our spins website build as it is based against the Json file. We had to fix a 2 years old python code. And we did not know about this. * Each release we have the 32 bit arch named i686 or i386, it's always changing. We defined variables in order to help us maintain the websites.. And this does not help us. I know that it depends of the proc instruction set. But where is the need to change that really? Could we avoid it? Sooner or later we will drop 32 bit arch... Couldn't we define which arch to stick with? * We don't know before last minute if the Spin has built for GA and therefore if it is going to be released. We need to check it manually. And really, we can't do it all manually. (as lazy programmers we can't even think about this). * Even the spins name has changed in the past, which break our code and already existing URLs. And then we need to define URL redirect... I hope jam-kde won't be changed to jam-mate-compiz-fusion-dark at some point.. Just wondering... * The secondary (ARM) path changed from Images/arm/ to Images/armhfp/.. I understand the need to tell if it's using FP or not, but again we didn't know about this before testing in prod. That should not happen again. Please, help me define the best way to avoid this. It could be improving SOP, or updating a file after each build.. whatever. It's a probably wider collaboration issues as it is involving primary, secondary, SIGs (spins, cloud).. But starting with Releng we can probably sort this and define the smoother solution for all. What we need in a simple way (script friendly) and easy to generate for you is a way to get: All image full name, path (if possible before release), size (not needed for torrents), format (torrent, spin, dvd, cloud... whatever) and checksum. What can't be available easily can have an easy process to get them or at least we need to know how and when to get them. The most important of course is the image full name. If we don't know that this image exists (or died), we won't be able to update it. Any brillant idea? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5654> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 3 months

1
9
0 / 0

#5679: merge buildbranched/buildrawhide into a single script

by Fedora Release Engineering

#5679: merge buildbranched/buildrawhide into a single script -----------------------------+------------------------ Reporter: ausil | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 20 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ in order to simplify things it would be good to make a single script to build rawhide and branched. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5679> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 5 months

1
2
0 / 0

#4071: Block pushes to origin/ in gitolite ACLs

by Fedora Release Engineering

#4071: Block pushes to origin/ in gitolite ACLs ----------------------+----------------------------------------------------- Reporter: jkeating | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: git Keywords: | ----------------------+----------------------------------------------------- Common typo to create a new branch that starts with "origin/". We can stop that at the ACL level. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4071> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 7 months

1
5
0 / 0

#4355: metadata for "grouped" files on master mirror

by Fedora Release Engineering

#4355: metadata for "grouped" files on master mirror ---------------------+------------------------------------------------------ Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: | ---------------------+------------------------------------------------------ This may be less of an issue now that we don't have the split CD set, but I would like it if rel-eng could produce a file into the master mirror tree for "groups" of files that should be a single consistent download set, such as a DVD and the checksum file, or the set of files that are together inside a single torrent. MirrorManager is growing the idea of a "file group", a single requestable entity that will return a metalink listing each of the files in the file group. The intent was to use it for the multi-CD download sets, but it's just as valuable for the DVD and checksum file, or other similar groups. But it needs to be a file (say, .fileset or something), in a directory that MM can find and use to build the FileGroups. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4355> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 7 months

1
2
0 / 0

#5653: script automatic weekly install rawhide trees

by Fedora Release Engineering

#5653: script automatic weekly install rawhide trees --------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | --------------------+------------------------ This was removed as part of the No Frozen Rawhide at the anaconda team's request. Dennis mentions that at this point they're for having a weekly tree (but no more). Dennis further notes that this is basically just a matter of * setup a cronjob * get the compose box to mount /pub/alt rw * automate cleanup of old trees And Kevin noted that the rw mount was no problem. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5653> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 7 months

1
11
0 / 0

#3903: change component owner in bugzilla

by Fedora Release Engineering

#3903: change component owner in bugzilla ----------------------+----------------------------------------------------- Reporter: mmaslano | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: | ----------------------+----------------------------------------------------- Could you create perl-fedora-maint as bug owner for all my perl-* modules and perl component? I'm sharing bugs with my colleagues in RHEL and we'd like to have it also for Fedora. I suppose set up mailing list is also needed. This should be applied only for perl modules, where I am an owner of the package. Not only co-maintainer. The group perl-fedora-maint should include mmaslano, ppisar, psabata. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3903> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 7 months

1
15
0 / 0

#5362: Use XZ for repository metadata compression

by Fedora Release Engineering

#5362: Use XZ for repository metadata compression -------------------------+------------------------ Reporter: elad | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: other Keywords: | Blocked By: Blocking: | -------------------------+------------------------ See [https://bugzilla.redhat.com/show_bug.cgi?id=700020 bug #700020] for details. I was informed that yum and createrepo already support xz compression for metadata, yet in Fedora still use bz2. We should probably switch repositories to use xz as well. I was told to talk with rel-eng, I hope this is the right place to do so. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5362> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

9 years, 11 months

1
23
0 / 0

#5214: Setup koji tags and repo for Docs

by Fedora Release Engineering

#5214: Setup koji tags and repo for Docs -----------------------------+------------------------ Reporter: crantila | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: docs | Blocked By: Blocking: | -----------------------------+------------------------ Posted here as per [https://fedorahosted.org/fedora- infrastructure/ticket/3320] '''phenomenon''' To support simpler and more robust updates to docs.fp.o, need to setup koji to handle a new tag and repo for Docs. '''implementation recommendation''' <Sparks> What would be required to stand up a separate instance of koji for Docs? <dgilmore> Sparks: why would you want a seperate instance? <dgilmore> Sparks: i dont see any valid reason to do so <Sparks> dgilmore: For the Docs website. Publican has the ability publish documentation from packages (separate repo from the Fedora repo) for the website. We want to replace the git repo that operates it now. <dgilmore> Sparks: and why does that need a seperate koji? <Sparks> The git repo has gotten HUGE and is becoming an issue. <dgilmore> Sparks: so, why does that mean a seperate koji instance <dgilmore> Sparks: we could use a seperate tag and targets in koji <dgilmore> i dont see why it would need its own koji <Sparks> dgilmore: It's either that or try to get everyone setup as packagers. <dgilmore> Sparks: get everyone setup as packagers <Sparks> dgilmore: Except that they really won't be packagers. <dgilmore> Sparks: though you dont need to be a a packager to get a koji cert <dgilmore> you just need fas <dgilmore> Sparks: what would be the workflow? <Sparks> dgilmore: Okay, and with that we can send packages through koji and tag them separately? <Sparks> dgilmore: Basically we just tell Publican to build the package and submit it to koji. The Publican software does all the work. <dgilmore> Sparks: I still really dont know what your trying to do. pretend im an idiot(not really that hard) and explain what it is and how it should work <Sparks> dgilmore: I'm not far off... <Sparks> dgilmore: So Publican will make an SRPM package, submit it to koji destined for a repo. Our Publican backend will install those packages and publish the data to the website. <Sparks> ...as I understand it <dgilmore> Sparks: so we would need to set up seperate tags and tagets for it, defining a koji policy allowing srpms to be built. likely we would add a new group to koji and add people allowed to build docs to it and limit access to the tags/targets to people in that group <dgilmore> Sparks: so its all doable <Sparks> dgilmore: Well that's a lot easier. :) <Sparks> dgilmore: We already have a group in FAS for people that should have access (docs- publishers). Should I open a ticket? <dgilmore> Sparks: koji doesnt know anything about fas <dgilmore> Sparks: please file a ticket. We wont be able to make changes until after f17 is done <Sparks> dgilmore: That's fine. We're not completely ready for the transition so after F17 would be good. <Sparks> dgilmore: Thanks! -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5214> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 3 months

1
16
0 / 0

#3624: fullfilelist changes

by Fedora Release Engineering

#3624: fullfilelist changes -------------------------+-------------------------------------------------- Reporter: mmcgrath | Owner: rel-eng(a)lists.fedoraproject.org Type: enhancement | Status: new Milestone: | Component: other Keywords: | -------------------------+-------------------------------------------------- After each push, we need to run the following command: rsync -r . > fullfilelist This should overwrite the fullfilelist that's there and isn't very useful at the moment: http://download.fedora.redhat.com/pub/fedora/fullfilelist We can't do this via a cron job, it has to go out after each push so it needs to be added to those scripts. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3624> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 3 months

1
3
0 / 0

#5418: Adopt policy that SCM request should be accepted from authorized users only

by Fedora Release Engineering

#5418: Adopt policy that SCM request should be accepted from authorized users only --------------------+------------------------ Reporter: ppisar | Owner: rel-eng@… Type: defect | Status: new Milestone: | Component: git Keywords: SCM | Blocked By: Blocking: | --------------------+------------------------ FESCo ticket [https://fedorahosted.org/fesco/ticket/981] moved to rel-eng quee. = Phenomenon Release engineers proceed SCM request from non-authorized applicants. = Background Analysis spot added SCM change request for 4 packages he does not own nor co- maintain and release engineer has processed the requests. The requests were to create new branches owned by master owners. Example [https://bugzilla.redhat.com/show_bug.cgi?id=835544#c7]: {{{ From: Tom "spot" Callaway 2012-12-11 21:50:00 GMT Package Change Request ====================== Package Name: perl-Pod-Markdown New Branches: f16 f17 Owners: jplesnik mmaslano ppisar psabata InitialCC: perl-sig From: Jon Ciesla 2012-12-12 13:14:20 GMT Git done (by process-git-requests). }}} This undermines regular maintainers' rights and obligations because they cannot even be sure which branches their packages exist and which they are responsible for. This conflicts with current policy for creating additional branches on behalf third persons (the third person, owner of new branch, asks current owner and current owner submits SCM request.) = Implementation recommendation Release engineers will accept SCM changes only from requesters who own or co-maintaint the package. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5418> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 3 months

1
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2013