#5859: Releng improvements ideas 2014
by Fedora Release Engineering
#5859: Releng improvements ideas 2014
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+------------------------
Ideas to improve releng:
- Properly announce in advance if meetings are skipped
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5859>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 10 months
#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21
by Fedora Release Engineering
#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21
-----------------------------+------------------------
Reporter: jreznik | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 21 Alpha | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Fedora Working Groups are discussing different options how to deliver
specific Fedora Products. These deliverables has to be collected (and
agreed on) to plan changes in Fedora release engineering process.
This ticket should serve to collect requirements from WGs in a centralized
way (as there's possible overlap etc). For specific implementation
details, new tickets will be created.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5891>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 10 months
#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed
by Fedora Release Engineering
#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed
-----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Big Data cloud image isn't going to make the milestone, so we should stop
trying to make the image.
Still hoping to do this for F22, so if we can keep the rawhide one,
awesome.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5944>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 10 months
#6004: Trigger new Atomic builds based on bash vulnerability
by Fedora Release Engineering
#6004: Trigger new Atomic builds based on bash vulnerability
-----------------------------+------------------------
Reporter: jzb | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: koji
Keywords: security | Blocked By:
Blocking: |
-----------------------------+------------------------
We have packages out for the bash vulnerability for Fedora 21 alpha, but
users cannot "yum update" the Atomic images. We need to spin + push out
new images and/or an update tree for users who are on Atomic.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6004>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 10 months
#6010: Create Fedora 21 Beta test compose (TC) and release candidate (RC)
by Fedora Release Engineering
#6010: Create Fedora 21 Beta test compose (TC) and release candidate (RC)
----------------------------+------------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Time flies, so it's time for Beta...
Please build a Fedora 21 Beta Test Compose. I don't believe there are any
special build requests at this point in time, let's just fire a TC1 and
see where we stand.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6010>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 1 month
[PATCH] Don't suppress error messages
by Mathieu Bridon
If a failure occured when trying to create the cache folder, mash would
just silently ignore the error and happily continue cranking along. It
might of course fail later on, but the problem is impossible to debug if
errors are silently suppressed.
However, if the error is merely that the directory already exists (as
opposed to a permission issue, for example), then that is fine to
ignore.
Likewise, if a failure occurs when trying to download, merely saying
"can't download" is not helpful. Adding the actual error message makes
it easier to figure out what went wrong.
---
mash/__init__.py | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/mash/__init__.py b/mash/__init__.py
index 566b8c1..27cdc47 100644
--- a/mash/__init__.py
+++ b/mash/__init__.py
@@ -12,6 +12,7 @@
# with this program; if not, write to the Free Software Foundation, Inc.,
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+import errno
import glob
import os
import logging
@@ -269,8 +270,11 @@ class Mash:
path = os.path.join(koji.pathinfo.build(builds_hash[pkg['build_id']]), koji.pathinfo.rpm(pkg))
try:
os.mkdir(os.path.dirname(cachepath))
- except:
- pass
+ except Exception as e:
+ if e.errno != errno.EEXIST:
+ # If the directory already exists, that's fine
+ self.logger.error(e)
+
try:
result = urlgrabber.grabber.urlgrab(path, cachepath)
except:
@@ -279,8 +283,9 @@ class Mash:
path = os.path.join(koji.pathinfo.build(builds_hash[pkg['build_id']]), koji.pathinfo.rpm(pkg))
try:
result = urlgrabber.grabber.urlgrab(path, cachepath)
- except:
- self.logger.error("ERROR: can't download %s from %s" % (nevra(pkg), path))
+ except Exception as e:
+ self.logger.error("ERROR: can't download %s from %s: %s"
+ % (nevra(pkg), path, e))
return None
fd = open(result)
--
2.1.0
9 years, 1 month