#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, 2 months
#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, 2 months
#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, 2 months
#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, 2 months
#5700: mass bugzilla script uses wrong urls
by Fedora Release Engineering
#5700: mass bugzilla script uses wrong urls
-------------------+------------------------
Reporter: ausil | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: other
Keywords: | Blocked By:
Blocking: |
-------------------+------------------------
the script for mass filing bugs puts the wrong urls in to log files. they
are short lived anyway. we need to find a better way to deal with them.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5700>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#5814: please remove private branch llvm/private-jvcelak
by Fedora Release Engineering
#5814: please remove private branch llvm/private-jvcelak
-----------------------------+------------------------
Reporter: jvcelak | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Please remove private branch llvm/private-jvcelak from dist-git.
{{{
% git push origin :private-jvcelak
remote: + refs/heads/private-jvcelak llvm jvcelak DENIED by fallthru
remote: error: hook declined to update refs/heads/private-jvcelak
To ssh://jvcelak@pkgs.fedoraproject.org/llvm
! [remote rejected] private-jvcelak (hook declined)
error: failed to push some refs to
'ssh://jvcelak@pkgs.fedoraproject.org/llvm'
}}}
Btw, builds which are preserved in Koji are built only from non-private
branches. And devels can create private branches, but cannot delete them.
Is there any reason for that?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5814>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
[PATCH] De-hardcode 'origin' as the remote name
by Mathieu Bridon
By default, Git remotes are named 'origin', but some pyrpkg-based tools
might be used to interact with several remotes for the same package
module.
This change allows sites to define how remotes should be called by
simply overriding the Commands.remote attribute.
That attribute is set to "origin" though, to not break existing clones.
The rpkg bash completion resource had to be modified accordingly. Since
the fedpkg one already handles this properly, a simple copy-paste of
that specific line was enough.
---
This is important for us at $dayjob.
We have this rpkg-based tool called nbpkg, which we use to interact with
our packaging infrastructure, similar to fedpkg:
https://github.com/network-box/nbpkg
But as I'm also a Fedora packager, I like to be able to interact with
both our internal infrastructure, and the Fedora one, in the same Git
clone, as it allows me to easily flow changes in both directions.
This workflow requires having different names for each remote though,
they can't just be all called 'origin'. This patch makes this possible.
I can imagine a similar use case for RHEL packagers, which could
probably want to interact with both the Fedora and RHEL packaging
infrastructures in the same Git clone, flowing changes both ways.
I know RPMFusion would be interested as well (I added Nicolas as CC).
src/pyrpkg/__init__.py | 21 ++++++++++++++-------
src/rpkg.bash | 3 +--
2 files changed, 15 insertions(+), 9 deletions(-)
diff --git a/src/pyrpkg/__init__.py b/src/pyrpkg/__init__.py
index c5b4ae4..89a84a2 100644
--- a/src/pyrpkg/__init__.py
+++ b/src/pyrpkg/__init__.py
@@ -135,6 +135,9 @@ class Commands(object):
self._ver = None
self.log = log
+ # The local name of the remote (might be overridden by subclasses)
+ self.remote = "origin"
+
# Define properties here
# Properties allow us to "lazy load" various attributes, which also means
# that we can do clone actions without knowing things like the spec
@@ -961,6 +964,11 @@ class Commands(object):
else:
self.log.debug('Cloning %s' % giturl)
cmd.extend([giturl])
+
+ if not bare_dir:
+ # --bare and --origin are incompatible
+ cmd.extend(['--origin', self.remote])
+
self._run_command(cmd, cwd=path)
return
@@ -1009,14 +1017,14 @@ class Commands(object):
for branch in branches:
try:
# Make a local clone for our branch
- top_git.clone("--branch", branch, repo_path, branch)
+ top_git.clone("--branch", branch, '--origin', self.remote,
+ repo_path, branch)
- # Set the origin correctly
+ # Set the remote correctly
branch_path = os.path.join(top_path, branch)
branch_git = git.Git(branch_path)
- branch_git.config("--replace-all", "remote.origin.url", giturl)
- # Bad use of "origin" here, need to fix this when more than one
- # remote is used.
+ branch_git.config(
+ "--replace-all", "remote.%s.url" % self.remote, giturl)
except (git.GitCommandError, OSError), e:
raise rpkgError('Could not locally clone %s from %s: %s' %
(branch, repo_path, e))
@@ -1452,8 +1460,7 @@ class Commands(object):
self.log.debug('No local branch found, creating a new one')
totrack = None
for remote in remotes:
- # bad use of "origin" here, will have to be fixed
- if remote.replace('origin/', '') == branch:
+ if remote.endswith(branch):
totrack = remote
break
else:
diff --git a/src/rpkg.bash b/src/rpkg.bash
index 047c98d..a2e45b6 100644
--- a/src/rpkg.bash
+++ b/src/rpkg.bash
@@ -283,8 +283,7 @@ _rpkg_branch()
local git_options= format="--format %(refname:short)"
[[ -n $1 ]] && git_options="--git-dir=$1/.git"
- git $git_options for-each-ref $format 'refs/remotes/origin/*' \
- | sed 's,origin/,,'
+ git $git_options for-each-ref $format 'refs/remotes' | sed 's,.*/,,'
git $git_options for-each-ref $format 'refs/heads'
}
--
1.8.5.3
9 years, 4 months
#5872: Block unalz in F21
by Fedora Release Engineering
#5872: Block unalz in F21
-----------------------------+------------------------
Reporter: ppisar | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
I've retired ''unalz'' package in Fedora 21 (bug !#1076853). Please block
it in the koji.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5872>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 4 months
#5893: Please unretire and unblock perl-Class-Trigger in EPEL-6
by Fedora Release Engineering
#5893: Please unretire and unblock perl-Class-Trigger in EPEL-6
-----------------------------+------------------------
Reporter: pghmcfc | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Some perl modules that replaced EPEL-6 were introduced in a recent EL-6
point release, and the EPEL-6 packages were retired. However, the new
packages were not made available in EL-6 for ppc64 and this has resulted
in broken dependencies for other packages in EPEL-6 for ppc64.
In particular, I would like to unretire perl-Class-Trigger and re-
introduce it to EPEL-6 with a zero release number as per the guidance at
https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5893>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 5 months