February 2013 - rel-eng - Fedora Mailing-Lists

#5219: tomcat6 fedora/rawhide java dependency appears broken

by Fedora Release Engineering

#5219: tomcat6 fedora/rawhide java dependency appears broken -----------------------------+------------------------ Reporter: nkinder | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ <filing on behalf of dknox> Hi, I've performed scratch-builds of the current git contents for fedora tomcat6/rawhide (which built previously). The build is looking for java >= 1.6, fails, then installs gcj java 1.5. When R:java[-devel] >= 0:1.6.0 is specified (versus R:java) the error changes[2] and there is no attempt to install gcj (which I would expect). There are also several "already installed" comments which I don't recall having occured before. [2]http://koji.fedoraproject.org/koji/getfile?taskID=4159550&name=root.log [Open URL] [1] http://koji.fedoraproject.org/koji/getfile?taskID=4159499&name=root.log [Open URL] : <snip from [1]> DEBUG backend.py:862: ['/usr/bin/yum-builddep', '--installroot', '/var/lib/mock/f18-build-1363965-220904/root/', '/var/lib/mock/f18-build-1363965-220904/root///builddir/build/SRPMS/tomcat6-6.0.35-2.fc18.src.rpm'] DEBUG util.py:307: Executing command: ['/usr/bin/yum-builddep', '-- installroot', '/var/lib/mock/f18-build-1363965-220904/root/', '/var/lib/mock/f18-build-1363965-220904/root///builddir/build/SRPMS/tomcat6-6.0.35-2.fc18.src.rpm'] DEBUG util.py:257: Getting requirements for tomcat6-6.0.35-2.fc18.src DEBUG util.py:257: --> ant-1.8.3-2.fc18.noarch DEBUG util.py:257: --> ant-1.8.3-2.fc18.noarch DEBUG util.py:257: --> 1:ecj-3.4.2-13.fc18.x86_64 DEBUG util.py:257: --> Already installed : 1:findutils-4.5.10-5.fc18.x86_64 DEBUG util.py:257: --> apache-commons-collections-3.2.1-13.fc18.noarch DEBUG util.py:257: --> apache-commons-daemon-1.0.10-3.fc18.x86_64 DEBUG util.py:257: --> apache-commons-dbcp-1.4-9.fc18.noarch DEBUG util.py:257: --> apache-commons-pool-1.6-1.fc18.noarch DEBUG util.py:257: --> jakarta-taglibs-standard-1.1.2-4.fc18.noarch DEBUG util.py:257: --> java-1.5.0-gcj-devel-1.5.0.0-39.fc18.x86_64 DEBUG util.py:257: --> jpackage-utils-1.7.5-18.fc18.x86_64 DEBUG util.py:257: --> junit-4.10-5.fc18.noarch DEBUG util.py:257: --> log4j-1.2.17-1.fc18.noarch DEBUG util.py:257: --> Already installed : systemd-185-5.gita2368a3.fc18.x86_64 DEBUG util.py:257: Error: Package: apache-commons- daemon-1.0.10-3.fc18.x86_64 (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 DEBUG util.py:257: Error: Package: apache-commons-pool-1.6-1.fc18.noarch (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 DEBUG util.py:257: Error: Package: hamcrest-1.1-12.fc17.noarch (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 DEBUG util.py:257: Error: Package: junit-4.10-5.fc18.noarch (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 DEBUG util.py:257: Error: Package: qdox-1.12-4.fc17.noarch (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 DEBUG util.py:257: Error: Package: log4j-1.2.17-1.fc18.noarch (build) DEBUG util.py:257: Requires: java >= 1:1.6.0 DEBUG util.py:257: Installing: java-1.5.0-gcj-1.5.0.0-39.fc18.x86_64 (build) DEBUG util.py:257: java = 1.5.0 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5219> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
2
0 / 0

#3759: bad distro tags in Fedora 13/x86_64

by Fedora Release Engineering

#3759: bad distro tags in Fedora 13/x86_64 -------------------+-------------------------------------------------------- Reporter: james | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | -------------------+-------------------------------------------------------- From yum repolist -v fedora ... Repo-id : fedora Repo-name : Fedora 13 - x86_64 Repo-revision: 1274245576 Repo-tags : binary-x86_64 Repo-distro-tags: [cpe:/o:fedoraproject:fedora:13]: rawhide ...this isn't rawhide though. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/3759> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
7
0 / 0

#2244: How to mass branch s390utils and other non-primary arch packages

by Fedora Release Engineering

#2244: How to mass branch s390utils and other non-primary arch packages --------------------+------------------------------------------------------- Reporter: toshio | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | --------------------+------------------------------------------------------- This is a rel-eng decision that I'll need input on. Currently the packagedb branches packages which are not blocked in koji. Some packages which are not built for the primary arch are blocked in koji -- s390utils for instance. Does the packagedb need to whitelist these or should the packages be unblocked as they are discovered? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2244> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
5
0 / 0

#4605: bodhi crashes with 500 internal server error when i try to remove a build from a ticket

by Fedora Release Engineering

#4605: bodhi crashes with 500 internal server error when i try to remove a build from a ticket ---------------------+------------------------------------------------------ Reporter: lennart | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ---------------------+------------------------------------------------------ Wanted to edit https://admin.fedoraproject.org/updates/selinux- policy-3.9.16-9.fc15,systemd-22-1.fc15 and replace selinux-policy-3.9.16-9.fc15 by selinux-policy-3.9.16-10.fc15, and i couldn't, because bodhi crashed. Regardless whether I tried to replace -9 with -10, or just tried to remove -9. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4605> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
4
0 / 0

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases

by Fedora Release Engineering

#4986: Create a 'Deliverables' page / SOP listing exactly what images, torrent files, signatures, checksums etc should be provided with (pre)-releases ----------------------+----------------------------------------------------- Reporter: adamwill | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: koji Keywords: | ----------------------+----------------------------------------------------- Going through the F16 QA retrospective, there's this series of linked points from Andre Robatino: "robatino - Alpha and Beta torrents often have unsigned checksum files - this just happened with 16 Alpha. It also happened during F13 and F14 - see http://lists.fedoraproject.org/pipermail/test/2010-April/090106.html for F13 Beta, and https://bugzilla.redhat.com/show_activity.cgi?id=638738 for F14 Alpha and Beta. When it's pointed out, we're told that it's not feasible to change them once people have started downloading, but if this is true, there needs to be better checking (at least as much as for mirror content, which can be changed) to make sure the torrents are correct before being posted. Filed https://fedorahosted.org/fedora-qa/ticket/237 and https://fedorahosted.org/rel-eng/ticket/4906 . No response from releng as of yet. Unless QA is given access prior to public posting, it is powerless to prevent this. robatino - Also, it's possible that the checksum files can be signed more than once. There are two versions of the signed checksum files for F15, one on the torrents (the original ones) and a different one on the mirrors. See http://robatino.fedorapeople.org/checksums/15-Final/ for the two versions - for example, Fedora-15-i386-CHECKSUM.orig and Fedora-15-i386-CHECKSUM. While not nearly as serious as the above issue (since the checksums are the same and both signatures are good), it could be confusing. " A quick mail discussion prompted the suggestion from Andre that the best way to cover all these issues would be for there to be a Deliverables wiki page / SOP which clearly lists all the 'bits' that should be delivered for each image drop - Alpha, Beta, Final, TC and RC. This would provide a simple reference for whoever's doing the build to make sure everything has been provided. It would make most sense for this to live in releng's wiki space, I think, so filing against releng trac, but a QA person could certainly take care of creating the page in theory, I think. We should have this in place prior to F17 Alpha TC1. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4986> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
5
0 / 0

#5512: cleanup f18-updates-testing

by Fedora Release Engineering

#5512: cleanup f18-updates-testing -----------------------------+------------------------ Reporter: sharkcz | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ There seems to be builds tagged as f18-updates-testing while a newer update was even released. I think it happened when f18 0-day updates were tagged into f18-updates or such. thunderbird-17.0-1.fc18 csmith-2.1.0-6.fc18 libfreenect-0.1.2-3.fc18 vzctl-4.1-2.fc18 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5512> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
1
0 / 0

#5450: Joining the release engineering team

by Fedora Release Engineering

#5450: Joining the release engineering team -----------------------------+------------------------ Reporter: apinnt231 | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 19 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Hello, I would like to join the release engineering team. I have exp. with system management and deployment. I have designed a few custom applications in c++ and php. Email me for more info. alan.pinnt(a)gmail.com and my username is apinnt231 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5450> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
1
0 / 0

#5318: tomcatjss build failure on FC19

by Fedora Release Engineering

#5318: tomcatjss build failure on FC19 --------------------+------------------------ Reporter: cfu | Owner: rel-eng@… Type: defect | Status: new Milestone: | Component: koji Keywords: | Blocked By: Blocking: | --------------------+------------------------ Received the following error from Koji build system. kwright reported success when trying with mock. Package: tomcatjss-7.0.0-3.fc19 Tag: f19 Status: failed Built by: cfu ID: 351714 Started: Tue, 04 Sep 2012 18:39:19 UTC Finished: Tue, 04 Sep 2012 18:45:27 UTC tomcatjss-7.0.0-3.fc19 (351714) failed on buildvm-07.phx2.fedoraproject.org (noarch), buildvm-30.phx2.fedoraproject.org (noarch): BuildError: error building package (arch noarch), mock exited with status 1; see build.log for more information SRPMS: tomcatjss-7.0.0-3.fc19.src.rpm Failed tasks: ------------- Task 4453578 on buildvm-07.phx2.fedoraproject.org Task Type: build (rawhide, /tomcatjss:a97fa0c8ba166eb60474533b6a358843403e3b17) Task 4453587 on buildvm-30.phx2.fedoraproject.org Task Type: buildArch (tomcatjss-7.0.0-3.fc19.src.rpm, noarch) logs: http://koji.fedoraproject.org/koji/getfile?taskID=4453587&name=build.log http://koji.fedoraproject.org/koji/getfile?taskID=4453587&name=mock_outpu... http://koji.fedoraproject.org/koji/getfile?taskID=4453587&name=root.log http://koji.fedoraproject.org/koji/getfile?taskID=4453587&name=state.log Closed tasks: ------------- Task 4453579 on buildvm-35.phx2.fedoraproject.org Task Type: buildSRPMFromSCM (/tomcatjss:a97fa0c8ba166eb60474533b6a358843403e3b17) logs: http://koji.fedoraproject.org/koji/getfile?taskID=4453579&name=build.log http://koji.fedoraproject.org/koji/getfile?taskID=4453579&name=checkout.log http://koji.fedoraproject.org/koji/getfile?taskID=4453579&name=mock_outpu... http://koji.fedoraproject.org/koji/getfile?taskID=4453579&name=root.log http://koji.fedoraproject.org/koji/getfile?taskID=4453579&name=state.log Task Info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4453578 Build Info: http://koji.fedoraproject.org/koji/buildinfo?buildID=351714 -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5318> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 9 months

1
2
0 / 0

#4149: Need a way to point EC2 instances to specific mirrors

by Fedora Release Engineering

#4149: Need a way to point EC2 instances to specific mirrors --------------------+------------------------------------------------------- Reporter: gholms | Owner: rel-eng(a)lists.fedoraproject.org Type: task | Status: new Milestone: | Component: other Keywords: | --------------------+------------------------------------------------------- To get Fedora working well on Amazon's EC2 cloud computing service ![1] the Cloud SIG is working on creating yum mirrors inside Amazon's network. Doing so provides a number of benefits: * Faster updates for users * People with hundreds of Fedora instances don't overload other public mirrors * No data transfer costs for users or those who fund the EC2 mirrors (traffic within a given cloud region is free) Unfortunately, data transfers are only free if they stay within a given region. This, combined with the fact that EC2's IP addresses freely roam between regions, makes normal IP-based direction via !MirrorManager impossible. We therefore need another way of directing clients toward the mirrors that reside within their own regions. Our list of proposed solutions to this are posted in the "Client Access" portion of my overall proposal for EC2 mirror infrastructure ![2]. Could you folks (a) offer any feedback, or (b) choose which solution would be best? I apologize if this is more of a FESCo question; I can take it to them if that would be better. ![1] https://fedoraproject.org/wiki/Features/EC2 ![2] https://fedoraproject.org/wiki/User:Gholms/EC2_Mirror_Proposal#Client_Access -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4149> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 10 months

1
10
0 / 0

#5427: Clean obsoleted packages from repositories

by Fedora Release Engineering

#5427: Clean obsoleted packages from repositories -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 18 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ See http://lists.fedoraproject.org/pipermail/devel/2012-December/175557.html Packages which are obsoleted by other packages effectively can't be installed. (They can be added by hand, but will be replaced on yum update in the default configuration.) If they're obsolete, we shouldn't ship them, so they should be cleaned from the F18 (and rawhide?) trees. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5427> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

10 years, 10 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng February 2013