On 08/05/2010 10:56 PM, Cristian Gafton wrote:
> Congratulations guys, this is awesome work. I know it has been painful
> and I have a rough idea about the level of effort involved. Looking
> over the transition, this is truly solid work, and I am confident it
> will carry (and exceed) the packager
Congratulations guys, this is awesome work. I know it has been painful
and I have a rough idea about the level of effort involved. Looking
over the transition, this is truly solid work, and I am confident it
will carry (and exceed) the packager's needs for at least another 13
releases or so... :-)
On Wed, 2010-08-04 at 01:33 -0700, Matt McCutchen wrote:
> On Tue, 2010-08-03 at 22:09 +, Ben Boeckel wrote:
> > Matt McCutchen wrote:
> > > No. If the attacker MITMs the entire connection, they can lie about the
> > > values of the remote refs too, so there is no need to find a hash
> > > co
Hi.
On Wed, 04 Aug 2010 09:30:41 -0700, Adam Williamson wrote
> Clearly Linus stood out even in his youth =)
He is a bit obsessed with the number 5, though.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, 2010-08-03 at 11:29 -0400, Martin Langhoff wrote:
> On Tue, Aug 3, 2010 at 11:16 AM, Matt McCutchen
> wrote:
> > don't want malware landing on my machine because someone did a MITM
> > attack on a Fedora maintainer's unencrypted "git fetch" and inserted
> > some extra patches to get pushe
On Tue, 2010-08-03 at 22:09 +, Ben Boeckel wrote:
> Matt McCutchen wrote:
> > No. If the attacker MITMs the entire connection, they can lie about the
> > values of the remote refs too, so there is no need to find a hash
> > collision.
>
> And how would you then be allowed to push? The git se
Matt McCutchen wrote:
> No. If the attacker MITMs the entire connection, they can lie about the
> values of the remote refs too, so there is no need to find a hash
> collision.
And how would you then be allowed to push? The git server would see that
your history doesn't match the history it has
On Tue, 2010-08-03 at 11:29 -0400, Martin Langhoff wrote:
> On Tue, Aug 3, 2010 at 11:16 AM, Matt McCutchen
> wrote:
> > don't want malware landing on my machine because someone did a MITM
> > attack on a Fedora maintainer's unencrypted "git fetch" and inserted
> > some extra patches to get pushe
On Tue, Aug 3, 2010 at 11:16 AM, Matt McCutchen wrote:
> don't want malware landing on my machine because someone did a MITM
> attack on a Fedora maintainer's unencrypted "git fetch" and inserted
> some extra patches to get pushed back to the real repository later.
The git protocol makes it extre
On Fri, 2010-07-30 at 09:14 -0700, Josh Stone wrote:
> A git trick I'd like fedpkg to learn is to use separate url/pushurl,
> e.g. in .git/config:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = git://pkgs.fedoraproject.org/foo
> pushurl = ssh://u...@p
On Fri, Jul 30, 2010 at 2:17 PM, Matěj Cepl wrote:
> Everybody was bitching about CVS for years,
I'm pretty sure I wasn't. But I'll still pile on with a +1 for the
switch over to git
-jef"getting git to compile on qnx is no fun"spaleta
--
devel mailing list
devel@lists.fedoraproject.org
https:
On 08/02/2010 07:02 PM, Harald Hoyer wrote:
On 07/30/2010 08:13 PM, Jesse Keating wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 08:52 AM, Daniel J Walsh wrote:
fedpkg build
fedpkg build
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 959, in
a
On 07/30/2010 08:13 PM, Jesse Keating wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/30/2010 08:52 AM, Daniel J Walsh wrote:
>>
>> fedpkg build
>> fedpkg build
>> Traceback (most recent call last):
>>File "/usr/bin/fedpkg", line 959, in
>> args.command(args)
>>Fil
On Fri, Jul 30, 2010 at 11:08:37AM +0100, pbrobin...@gmail.com wrote:
> I think you need to get the latest package from koji so it points to
> the live git repos and not the test ones.
yes, the old version (which is still in F-12) uses
pkgs.stg.fedoraproject.org, but the right URL is
pkgs.fe
Josh Stone writes:
> A git trick I'd like fedpkg to learn is to use separate url/pushurl,
> e.g. in .git/config:
>
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = git://pkgs.fedoraproject.org/foo
> pushurl = ssh://u...@pkgs.fedoraproject.org/foo
Or mor
On Sun, Aug 1, 2010 at 1:12 PM, Andrea Musuruane wrote:
> On Sun, Aug 1, 2010 at 1:05 PM, Dominic Hopf wrote:
>> I just yesterday had similar problems and then found out my
>> ~/.fedora.cert was out of date since five days ago. Maybe it's the same
>> for you, did you already had a look there? :)
On Sun, Aug 1, 2010 at 1:05 PM, Dominic Hopf wrote:
> I just yesterday had similar problems and then found out my
> ~/.fedora.cert was out of date since five days ago. Maybe it's the same
> for you, did you already had a look there? :)
Yes. It will be valid until Dec 7, 2010.
Bye,
Andrea.
--
Am Sonntag, den 01.08.2010, 11:42 +0200 schrieb Andrea Musuruane:
> On Sat, Jul 31, 2010 at 11:56 AM, Andrea Musuruane wrote:
> > OK. I deleted the current repo and started again. I do have
> > fedora-packager 0.5.1.
> >
> > Now fedora-packager crashes when uploading new sources.
> >
> > $ fedpkg
On Sat, Jul 31, 2010 at 11:56 AM, Andrea Musuruane wrote:
> OK. I deleted the current repo and started again. I do have
> fedora-packager 0.5.1.
>
> Now fedora-packager crashes when uploading new sources.
>
> $ fedpkg clone zaz
> Cloning into zaz...
> [..]
> Resolving deltas: 100% (11/11), done.
>
On Sat, Jul 31, 2010 at 11:50 AM, Rahul Sundaram wrote:
> On 07/31/2010 03:19 PM, Andrea Musuruane wrote:
>> l return(int(fedoras[-1].strip('f')) + 1)
>> IndexError: list index out of range
>>
>> Help is really appreciated.
>>
>> Thanks!
>
> make sure you update fedora-packager to 0.5.1, remov
On 07/31/2010 03:19 PM, Andrea Musuruane wrote:
> lreturn(int(fedoras[-1].strip('f')) + 1)
> IndexError: list index out of range
>
> Help is really appreciated.
>
> Thanks!
make sure you update fedora-packager to 0.5.1, remove and clone the repo
again and follow the same steps. It will work.
Hi all,
I do not know anything about GIT and I tried to follow this thread
and the Using_Fedora_GIT in the wiki to make my first commit
The workflow was more or less the following:
$ fedpkg clone zaz
$ cd zaz/
$ cp -a ~/rpmbuild/SOURCES/zaz-0.8.0.tar.bz2 .
$ cp -a ~/rpmbuild/SPECS/zaz.spec .
$
Dne 30.7.2010 09:48, Phil Knirsch napsal(a):
> I only have 2 words for you and everyone who has put so insanely much
> work into this effort for such a long time:
>
>T H A N K Y O U !
Everybody was bitching about CVS for years, so now we all should say to this
+1000
Thank you
--
There is
On 07/30/2010 03:02 PM, Jon Ciesla wrote:
> On 7/29/2010 10:55 PM, Jesse Keating wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> This evening we opened up dist-git for business. Dist-git is our git
>> based replacement for dist-cvs, the source control system we were using
>> for
On 7/29/2010 10:55 PM, Jesse Keating wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This evening we opened up dist-git for business. Dist-git is our git
> based replacement for dist-cvs, the source control system we were using
> for our package specs, patches, and source files. This
On Fri, 2010-07-30 at 10:42 -0700, Jesse Keating wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/30/2010 02:13 AM, Martin Sourada wrote:
> > Ok, so trying to update a package (libass) I've noticed a tiny problem:
> > the fedpkg switch-branch does not seem to set up proper track
On 07/30/2010 11:36 AM, Hans Ulrich Niedermann wrote:
> On Fri, 2010-07-30 at 11:15 -0700, Jesse Keating wrote:
>> On 07/30/2010 09:14 AM, Josh Stone wrote:
>>> A git trick I'd like fedpkg to learn is to use separate url/pushurl,
>>> e.g. in .git/config:
>>>
>>> [remote "origin"]
>>> fetch = +r
On Fri, 2010-07-30 at 11:15 -0700, Jesse Keating wrote:
> On 07/30/2010 09:14 AM, Josh Stone wrote:
> > A git trick I'd like fedpkg to learn is to use separate url/pushurl,
> > e.g. in .git/config:
> >
> > [remote "origin"]
> > fetch = +refs/heads/*:refs/remotes/origin/*
> > url = git://pk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 01:49 AM, pbrobin...@gmail.com wrote:
> One thing I've never got around to working out how to do in git which
> is different from previous is dealing with branches. Where previously
> it was as simple as changing directories to deal with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 10:53 AM, Konstantin Ryabitsev wrote:
> On Fri, Jul 30, 2010 at 1:35 PM, Konstantin Ryabitsev
> wrote:
>> Hmm... Doesn't seem to be working at all for me.
>>
>> $ fedpkg co verbiste
>> Traceback (most recent call last):
>> File "/usr/bi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 09:14 AM, Josh Stone wrote:
> Thanks for dist-git -- one step closer to banishing CVS from my life! :)
>
> A git trick I'd like fedpkg to learn is to use separate url/pushurl,
> e.g. in .git/config:
>
> [remote "origin"]
> fetch =
Am 30.07.10 10:02, schrieb Michal Hlavinka:
> Thanks for your hard work! Could you describe this in more
> details:
> OLD CVS | NEW GIT | Notes
> make tag | N/A | Explicitly tagging
> source states for package builds is no longer necessary.
>
> how this exactly
Each commit has an unique numb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 08:52 AM, Daniel J Walsh wrote:
>
> fedpkg build
> fedpkg build
> Traceback (most recent call last):
> File "/usr/bin/fedpkg", line 959, in
> args.command(args)
> File "/usr/bin/fedpkg", line 297, in build
> mymodule.init_k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 01:02 AM, Michal Hlavinka wrote:
> On Friday 30 of July 2010 05:55:09 Jesse Keating wrote:
>> ... Wiki
>> pages
> will get filled out as knowledge of how to interact with dist-git
>> starts
> to spread ( https://fedoraproject.org/wiki/Usi
On Thu, Jul 29, 2010 at 11:55 PM, Jesse Keating wrote:
> Once again I want to thank everybody who helped out and for all the
> (continued) patience! I'll be available via email and IRC as much as
> possible the next few days to help anybody with dist-git issues. Look
> for Oxf13 on freenode. Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 02:13 AM, Martin Sourada wrote:
> Ok, so trying to update a package (libass) I've noticed a tiny problem:
> the fedpkg switch-branch does not seem to set up proper tracking of
> remote branches which then results in (uhm, I'm using git co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 05:43 AM, Miroslav Suchý wrote:
> On 07/30/2010 05:55 AM, Jesse Keating wrote:
>> starts to spread ( https://fedoraproject.org/wiki/Using_Fedora_GIT is a
>> good start ).
>
> I made:
>
> fedpkg clone python-debian
> cd python-debian
> f
On Fri, Jul 30, 2010 at 1:35 PM, Konstantin Ryabitsev
wrote:
> Hmm... Doesn't seem to be working at all for me.
>
> $ fedpkg co verbiste
> Traceback (most recent call last):
> File "/usr/bin/fedpkg", line 959, in
> args.command(args)
> File "/usr/bin/fedpkg", line 409, in clone
> pyfedpkg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 03:06 AM, Peter Lemenkov wrote:
> Great news!
>
> Few questions still remains unanswered for me:
>
> * Should I use git now?
Yes.
> * May I still use cvs?
read-only
> * If I'll add some changes right now using git/cvs will they be
>
Thanks for dist-git -- one step closer to banishing CVS from my life! :)
A git trick I'd like fedpkg to learn is to use separate url/pushurl,
e.g. in .git/config:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git://pkgs.fedoraproject.org/foo
pushurl =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
fedpkg build
fedpkg build
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 959, in
args.command(args)
File "/usr/bin/fedpkg", line 297, in build
mymodule.init_koji(args.user, kojiconfig)
File "/usr/lib/python2.7/site-pac
On Fri, Jul 30, 2010 at 16:18, Stanislav Ochotnicky
wrote:
> Excerpts from Christof Damian's message of Fri Jul 30 16:10:44 +0200 2010:
>> I am trying to update one of my packages with git for the first time.
>> Works good, but "fedpkg build" fails for me.
>>
>> It complains that it can't retrieve
Rahul Sundaram wrote:
> FYI, git-svn is for users who want to continue to use Subversion on
> the server but interact using Git from clients. It is not a tool
> for conversion. It is a common mistake.
Not so much. Many folks use git-svn to convert from svn to git. Once
you have cloned an svn
Excerpts from Christof Damian's message of Fri Jul 30 16:10:44 +0200 2010:
> I am trying to update one of my packages with git for the first time.
> Works good, but "fedpkg build" fails for me.
>
> It complains that it can't retrieve the sources:
> http://koji.stg.fedoraproject.org/koji/getfile?ta
Many thanks!
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de InformaticaFono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile 234 Fax: +56 32 2797513
--
devel
I am trying to update one of my packages with git for the first time.
Works good, but "fedpkg build" fails for me.
It complains that it can't retrieve the sources:
http://koji.stg.fedoraproject.org/koji/getfile?taskID=2239266&name=root.log&offset=-4000
When I open the URL open with firefox/curl t
On 07/30/2010 02:43 PM, Miroslav Suchý wrote:
> On 07/30/2010 05:55 AM, Jesse Keating wrote:
>> starts to spread ( https://fedoraproject.org/wiki/Using_Fedora_GIT is a
>> good start ).
>
> I made:
>
> fedpkg clone python-debian
> cd python-debian
> fedpkg switch-branch f14
>edit spec file
> fed
On 07/30/2010 05:55 AM, Jesse Keating wrote:
> starts to spread ( https://fedoraproject.org/wiki/Using_Fedora_GIT is a
> good start ).
I made:
fedpkg clone python-debian
cd python-debian
fedpkg switch-branch f14
edit spec file
fedpkg commit -m 'edit changelog entry' -p
fedpkg push
And the last
On Fri, Jul 30, 2010 at 11:18, Rahul Sundaram wrote:
> On 07/30/2010 02:44 PM, Christof Damian wrote:
>> Thank you for all the work.
>>
>> I am currently in the process of convincing my employer to change from
>> svn to git and know how much work this is. Running git-svn clone alone
>> takes a fe
On Fri, Jul 30, 2010 at 11:06 AM, Peter Lemenkov wrote:
> Great news!
>
> Few questions still remains unanswered for me:
>
> * Should I use git now?
> * May I still use cvs?
> * If I'll add some changes right now using git/cvs will they be
> available in cvs/git respectively?
> * I just noticed th
Great news!
Few questions still remains unanswered for me:
* Should I use git now?
* May I still use cvs?
* If I'll add some changes right now using git/cvs will they be
available in cvs/git respectively?
* I just noticed that some freshly cloned git repositories are about
one month old (namely,
2010/7/30 Martin Sourada :
> On Fri, 2010-07-30 at 09:49 +0100, pbrobin...@gmail.com wrote:
>> Excellent news! Thanks for all the work.
>>
>> One thing I've never got around to working out how to do in git which
>> is different from previous is dealing with branches. Where previously
>> it was as s
On Fri, 2010-07-30 at 09:49 +0100, pbrobin...@gmail.com wrote:
> Excellent news! Thanks for all the work.
>
> One thing I've never got around to working out how to do in git which
> is different from previous is dealing with branches. Where previously
> it was as simple as changing directories to
On Fri, 2010-07-30 at 11:20 +0200, Martin Sourada wrote:
> On Fri, 2010-07-30 at 17:17 +0800, Chen Lei wrote:
> > 2010/7/30 Martin Sourada :
> > > On Thu, 2010-07-29 at 20:55 -0700, Jesse Keating wrote:
> > >
> > >> Without the help of many others, this project would never have gotten
> > >> don
On Fri, 2010-07-30 at 17:17 +0800, Chen Lei wrote:
> 2010/7/30 Martin Sourada :
> > On Thu, 2010-07-29 at 20:55 -0700, Jesse Keating wrote:
> >
> >> Without the help of many others, this project would never have gotten
> >> done. Folks helped out with Koji modifications, with fedpkg
> >> contrib
On 07/30/2010 02:44 PM, Christof Damian wrote:
> Thank you for all the work.
>
> I am currently in the process of convincing my employer to change from
> svn to git and know how much work this is. Running git-svn clone alone
> takes a few weeks for us.
FYI, git-svn is for users who want to conti
2010/7/30 Martin Sourada :
> On Thu, 2010-07-29 at 20:55 -0700, Jesse Keating wrote:
>
>> Without the help of many others, this project would never have gotten
>> done. Folks helped out with Koji modifications, with fedpkg
>> contributions, with repeated testing of attempted conversions, with
>>
Thank you for all the work.
I am currently in the process of convincing my employer to change from
svn to git and know how much work this is. Running git-svn clone alone
takes a few weeks for us.
I will check out all my packages on the weekend.
Happy Branching!
--
devel mailing list
devel@lists
On Thu, 2010-07-29 at 20:55 -0700, Jesse Keating wrote:
> Without the help of many others, this project would never have gotten
> done. Folks helped out with Koji modifications, with fedpkg
> contributions, with repeated testing of attempted conversions, with
> logic checking of my plans, of hel
On Fri, Jul 30, 2010 at 4:55 AM, Jesse Keating wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This evening we opened up dist-git for business. Dist-git is our git
> based replacement for dist-cvs, the source control system we were using
> for our package specs, patches, and source f
On Friday 30 of July 2010 05:55:09 Jesse Keating wrote:
> ... Wiki
> pages
will get filled out as knowledge of how to interact with dist-git
> starts
to spread ( https://fedoraproject.org/wiki/Using_Fedora_GIT is a
> good
start ).
Thanks for your hard work! Could you describe this in more
details:
On 07/30/2010 05:55 AM, Jesse Keating wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This evening we opened up dist-git for business. Dist-git is our git
> based replacement for dist-cvs, the source control system we were using
> for our package specs, patches, and source files. Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This evening we opened up dist-git for business. Dist-git is our git
based replacement for dist-cvs, the source control system we were using
for our package specs, patches, and source files. This has been a long
time coming and a massive effort. I w
63 matches
Mail list logo
