-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/05/2010 03:47 PM, Richard W.M. Jones wrote:
Is there any essential difference between 'fedpkg push' and plain
'git push'?
At the moment no, however to work around the local branches being named
differently than the remote branches, I've been
On Thu, Jul 29, 2010 at 11:25:42AM -0700, Jesse Keating wrote:
fedpkg push (this step could be skipped with fedpkg commit -p)
Is there any essential difference between 'fedpkg push' and plain
'git push'?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
RWMJ == Richard W M Jones rjo...@redhat.com writes:
RWMJ Is there any essential difference between 'fedpkg push' and plain
RWMJ 'git push'?
def push(self):
Push changes to the main repository
cmd = ['git', 'push']
_run_command(cmd)
return
So looks like no.
On Friday 30 July 2010, Toshio Kuratomi wrote:
On Fri, Jul 30, 2010 at 09:49:22AM -0700, Jesse Keating wrote:
That's a good question. fedpkg does not yet have a method for end user
defaults. That's not a quick patch either, but if somebody wants to
work on it, I'll certainly review the
Hi.
On Fri, 30 Jul 2010 21:48:22 -0500, Bruno Wolff III wrote
I got some info from McGrath and added it to the wiki.
I don't think it's a good idea to save informations that are used
to authenticate a connection in a wiki.
--
devel mailing list
devel@lists.fedoraproject.org
On Sat, Jul 31, 2010 at 12:45:13 +0200,
Ralf Ertzinger fed...@camperquake.de wrote:
Hi.
On Fri, 30 Jul 2010 21:48:22 -0500, Bruno Wolff III wrote
I got some info from McGrath and added it to the wiki.
I don't think it's a good idea to save informations that are used
to authenticate a
On Fri, Jul 30, 2010 at 09:49:22AM -0700, Jesse Keating wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 01:06 AM, Enrico Scholz wrote:
Jesse Keating jkeat...@redhat.com writes:
I want to build a new libfoo for rawhide:
fedpkg build
where can be done local
I was unable to find a fingerprint for pkgs.fedoraproject.org. Since the
risk is low, I'll start doing work and check it retroactively.
I think there should be some comment in the documentation about what the
project expects maintainers to do with regard to using it to avoid
man in the middle
On Fri, Jul 30, 2010 at 21:07:08 -0500,
Bruno Wolff III br...@wolff.to wrote:
I was unable to find a fingerprint for pkgs.fedoraproject.org. Since the
risk is low, I'll start doing work and check it retroactively.
I think there should be some comment in the documentation about what the
I noticed that the f14 repo from the kernel mirror seems to have only
things that are tagged dist-f14 and no inherited stuff. (Note that
while there is kitutuki-0.9.9c-1.fc13.i686.rpm, it's tagged both
dist-f13 and dist-f14.)
--
devel mailing list
devel@lists.fedoraproject.org
On Fri, Jul 30, 2010 at 22:24:59 -0500,
Bruno Wolff III br...@wolff.to wrote:
I noticed that the f14 repo from the kernel mirror seems to have only
things that are tagged dist-f14 and no inherited stuff. (Note that
while there is kitutuki-0.9.9c-1.fc13.i686.rpm, it's tagged both
dist-f13 and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/30/10 8:39 PM, Bruno Wolff III wrote:
On Fri, Jul 30, 2010 at 22:24:59 -0500,
Bruno Wolff III br...@wolff.to wrote:
I noticed that the f14 repo from the kernel mirror seems to have only
things that are tagged dist-f14 and no inherited
On Fri, Jul 30, 2010 at 22:39:08 -0500,
Bruno Wolff III br...@wolff.to wrote:
Probably related to this I got some broken package dependency warnings emailed
to me that seem to be for things that weren't rebuilt for F14. Is it safe
to ignore this batch of warnings?
I see this got answered
Jesse Keating jkeat...@redhat.com writes:
I want to build a new libfoo for rawhide:
fedpkg build
where can be done local customization like in ~/.cvsextrasrc?
E.g. I set
| BUILD_CLIENT = ${HOME}/bin/tkoji
| KOJI_FLAGS= --nowait
there.
fedpkg new-sources file [file file]
Where can
Le 30/07/2010 01:07, Jesse Keating a écrit :
https://fedoraproject.org/wiki/Using_Fedora_GIT
We just might finish up before the 48 hour window is up!
Thanks for that great work !
Just updated my first package. No issue :)
Could be usefull to have a tips (in the wiki page) on how to
2010/7/30 Remi Collet fed...@famillecollet.com:
Le 30/07/2010 01:07, Jesse Keating a écrit :
https://fedoraproject.org/wiki/Using_Fedora_GIT
We just might finish up before the 48 hour window is up!
Thanks for that great work !
Just updated my first package. No issue :)
Could be
On Fri, Jul 30, 2010 at 10:08 AM, Chen Lei supercyp...@gmail.com wrote:
2010/7/30 Remi Collet fed...@famillecollet.com:
Le 30/07/2010 01:07, Jesse Keating a écrit :
https://fedoraproject.org/wiki/Using_Fedora_GIT
We just might finish up before the 48 hour window is up!
Thanks for that
On Wed, Jul 28, 2010 at 10:18 AM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 11:54 PM, Jesse Keating wrote:
The conversion will take a couple days, which means our normal short
outage for branching will be a bit extended. I wish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 07:14 AM, pbrobin...@gmail.com wrote:
On Wed, Jul 28, 2010 at 10:18 AM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 11:54 PM, Jesse Keating wrote:
The conversion will take a
On 07/29/2010 02:04 PM, Jesse Keating wrote:
Over 10K repos have been converted, but I do have to run a script over
those repos and make sure the conversion actually succeeded. We've
also gotten dist-f14, dist-f13, dist-f12, and el6 in a state that we can
build with, however we do have to do
On Thu, Jul 29, 2010 at 8:10 PM, Tom spot Callaway
tcall...@redhat.com wrote:
This may be a dumb question (I'm full of dumb questions sometimes),
Even dumber question. Are bugzilla fedora-cvs flags getting renamed?
And do we need to make New Package Git Requests now?
--
Iain.
--
devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:10 AM, Tom spot Callaway wrote:
On 07/29/2010 02:04 PM, Jesse Keating wrote:
Over 10K repos have been converted, but I do have to run a script over
those repos and make sure the conversion actually succeeded. We've
also gotten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:18 AM, Iain Arnell wrote:
On Thu, Jul 29, 2010 at 8:10 PM, Tom spot Callaway
tcall...@redhat.com wrote:
This may be a dumb question (I'm full of dumb questions sometimes),
Even dumber question. Are bugzilla fedora-cvs flags
On Thu, Jul 29, 2010 at 7:04 PM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 07:14 AM, pbrobin...@gmail.com wrote:
On Wed, Jul 28, 2010 at 10:18 AM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash:
On 07/29/2010 02:25 PM, Jesse Keating wrote:
Option C:
fedpkg clone -B libfoo
cd libfoo/f13/
This doesn't seem to work... perhaps because of the transition?
http://fpaste.org/FV5g/
If I can get this working, I'd be willing to help write wiki pages. :)
~spot
--
devel mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:51 AM, Tom spot Callaway wrote:
On 07/29/2010 02:25 PM, Jesse Keating wrote:
Option C:
fedpkg clone -B libfoo
cd libfoo/f13/
This doesn't seem to work... perhaps because of the transition?
http://fpaste.org/FV5g/
If I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:48 AM, pbrobin...@gmail.com wrote:
Completely ignore OLPC* they are historical and are no longer used.
I see active build targets in koji for dist-olpc{2,3,4},
olpc2-{ship2,trail3,update1}. Are you saying we could remove all of
On Thu, Jul 29, 2010 at 8:15 PM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:48 AM, pbrobin...@gmail.com wrote:
Completely ignore OLPC* they are historical and are no longer used.
I see active build targets in koji for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 02:25 PM, Jesse Keating wrote:
But for the typical tasks here we go:
I want to build a new libfoo for rawhide:
fedpkg clone libfoo
cd libfoo
edit files
fedpkg commit
input commit message
fedpkg push (this step could
On Thu, 2010-07-29 at 15:58 -0400, Stephen Gallagher wrote:
...
fedpkg: error: invalid choice: 'push' (choose from 'clog', 'help',
'mockbuild', 'sources', 'diff', 'gimmespec', 'build', 'import',
'verrel', 'local', 'prep', 'tag-request', 'clean', 'build_common',
I'd love to know
On Thu, 2010-07-29 at 13:04 -0700, Adam Williamson wrote:
On Thu, 2010-07-29 at 15:58 -0400, Stephen Gallagher wrote:
...
fedpkg: error: invalid choice: 'push' (choose from 'clog', 'help',
'mockbuild', 'sources', 'diff', 'gimmespec', 'build', 'import',
'verrel', 'local',
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 12:58 PM, Stephen Gallagher wrote:
This didn't work for me. 'fedpkg push' just gives me:
You need a newer fedpkg. I linked above to the latest builds. We're
working on getting them pushed out in updates for people.
- --
Jesse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 04:13 PM, Jesse Keating wrote:
On 07/29/2010 12:58 PM, Stephen Gallagher wrote:
This didn't work for me. 'fedpkg push' just gives me:
You need a newer fedpkg. I linked above to the latest builds. We're
working on getting them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 29.07.2010 22:15, schrieb Stephen Gallagher:
Just updated to the latest build. 'fedpkg diff' fails with: File
/usr/bin/fedpkg, line 959, in module args.command(args) File
/usr/bin/fedpkg, line 440, in diff mymodule =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 04:15 PM, Stephen Gallagher wrote:
On 07/29/2010 04:13 PM, Jesse Keating wrote:
On 07/29/2010 12:58 PM, Stephen Gallagher wrote:
This didn't work for me. 'fedpkg push' just gives me:
You need a newer fedpkg. I linked above to the
On Thu, 29 Jul 2010, Stephen Gallagher wrote:
Never mind, turns out this was me trying to use fedpkg 0.5.0 against a
checkout made for 0.4.2 (against the test environment)
Note that fedpkg 0.5.1 is out now.
Michael Young
--
devel mailing list
devel@lists.fedoraproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2010 11:04 AM, Jesse Keating wrote:
On 07/29/2010 07:14 AM, pbrobin...@gmail.com wrote:
On Wed, Jul 28, 2010 at 10:18 AM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 11:54 PM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 11:54 PM, Jesse Keating wrote:
The conversion will take a couple days, which means our normal short
outage for branching will be a bit extended. I wish there was another
way, but converting over 9K cvs repos into git repos does take
On Wed, Jul 28, 2010 at 10:18 AM, Jesse Keating jkeat...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 11:54 PM, Jesse Keating wrote:
The conversion will take a couple days, which means our normal short
outage for branching will be a bit extended. I wish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2010 08:15 AM, pbrobin...@gmail.com wrote:
So once the package is converted is the git repo read/write so we can
begin updates or is it all down until the conversion is complete?
Kinda, but not for production use. Once they are all
On Saturday, July 24, 2010 08:54:53 Jesse Keating wrote:
Hey all! It's
that time again, we're gearing up to branch for Fedora 14
this coming
Tuesday! There is a major twist this time around, we're
going to attempt
a roll out of dist-git!
What we will find in git? Only rawhide? F-14? All
not
git branch -a will show you all branches (remote included)
Until fedpkg is updated, to track any remote branch other than master
(ie: F-13):
git checkout -b f13 remotes/origin/F-13
Then, you juste have to do for switching: git checkout my_branch
Best regards,
H.
--
devel mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2010 10:25 AM, Chen Lei wrote:
Can we filter out all .cvsignore and Makefile files it git repo? It
seems those files are irrelevant to dist-git.
Yes, in the latest conversion scripts branch, import.log, and Makefile
files are removed. The
Jesse
Another dumb question. I uploaded a package, frama-c. Will it be included in
14.
Sent from my iPhone
On Jul 24, 2010, at 2:54 AM, Jesse Keating jkeat...@redhat.com wrote:
Hey all! It's that time again, we're gearing up to branch for Fedora 14
this coming Tuesday! There is a major
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/26/10 5:39 PM, Mark Rader wrote:
Another dumb question. I uploaded a package, frama-c. Will it be included in
14.
If it has been built for rawhide prior to the branch event, then it will
be in 14.
- --
Jesse Keating
Fedora -- Freedom² is
On Mon, Jul 26, 2010 at 10:28 PM, Adam Williamson awill...@redhat.com wrote:
On Sat, 2010-07-24 at 15:31 +0100, Richard W.M. Jones wrote:
On Sat, Jul 24, 2010 at 09:10:24AM -0400, Brandon Lozza wrote:
On Sat, Jul 24, 2010 at 2:54 AM, Jesse Keating jkeat...@redhat.com wrote:
Hey all! It's
On Mon, 2010-07-26 at 22:33 -0400, Brandon Lozza wrote:
Also, of course, one of the truisms about git is that it doesn't only
make it easier to *fork*: it makes it easier to *merge*. So even if the
change does let people fork Fedora more easily, it also lets us
incorporate their changes
Hey all! It's that time again, we're gearing up to branch for Fedora 14
this coming Tuesday! There is a major twist this time around, we're
going to attempt a roll out of dist-git!
Dist-git is our replacement for the CVS system we are currently using.
This is a pretty big deal, but we're going
On Sat, Jul 24, 2010 at 2:54 AM, Jesse Keating jkeat...@redhat.com wrote:
Hey all! It's that time again, we're gearing up to branch for Fedora 14
this coming Tuesday! There is a major twist this time around, we're
going to attempt a roll out of dist-git!
--snipped---
I'm just curious but
49 matches
Mail list logo
