Re: master branch still invokes build in f17-candidate??

2012-03-01 Thread Vít Ondruch
Dne 29.2.2012 20:13, Jesse Keating napsal(a): unless we move away from using master for rawhide and instead always have a specific branch for each release. Please don't do that. Thank you. Vit -- devel mailing list devel@lists.fedoraproject.org

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Vít Ondruch
Dne 29.2.2012 06:05, Mathieu Bridon napsal(a): On Wed, 2012-02-29 at 05:31 +0100, Kevin Kofler wrote: Tom Lane wrote: Kevin Koflerkevin.kof...@chello.at writes: Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Jesse Keating
On 2/28/12 12:58 AM, Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the %{?dist} from local machine instead? It makes no sense. It might work for other

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Jesse Keating
On 2/28/12 8:47 AM, Josh Boyer wrote: I was looking for a way to determine the behavior of the master branch (for the sake of dist values) without hitting the network, as that would break git's ability to work offline. The best I could come up with at the time this code was written was to

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Tom Lane
Jesse Keating jkeat...@redhat.com writes: On 2/28/12 12:58 AM, Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the %{?dist} from local machine instead? It

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Jesse Keating
On 2/29/12 1:25 PM, Tom Lane wrote: Jesse Keatingjkeat...@redhat.com writes: On 2/28/12 12:58 AM, Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the

Re: master branch still invokes build in f17-candidate??

2012-02-29 Thread Bruno Wolff III
On Wed, Feb 29, 2012 at 16:25:22 -0500, Tom Lane t...@redhat.com wrote: In the particular case here it was harmless, since I would've just gone and built the identical SRPM in f17 a bit later anyway, and (I trust) rawhide will inherit the new f17 package too. I believe rawhide still

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Vít Ondruch
Dne 28.2.2012 02:59, Jesse Keating napsal(a): On 2/27/12 5:53 PM, Kevin Kofler wrote: Jesse Keating wrote: I was looking for a way to determine the behavior of the master branch (for the sake of dist values) without hitting the network, as that would break git's ability to work offline. The

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Richard W.M. Jones
On Mon, Feb 27, 2012 at 12:14:49PM -0800, Jesse Keating wrote: On 2/27/12 8:37 AM, Tom Lane wrote: Orion Poplawskior...@cora.nwra.com writes: On 02/27/2012 09:09 AM, Tom Lane wrote: WTF? Do I need to fix this, and if so how? git pull (to bring in the f17 branch and mark devel as f18)

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Kevin Kofler
Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the %{?dist} from local machine instead? It makes no sense. It might work for other branches, but master is

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Josh Boyer
On Tue, Feb 28, 2012 at 11:18 AM, Richard W.M. Jones rjo...@redhat.com wrote: On Mon, Feb 27, 2012 at 12:14:49PM -0800, Jesse Keating wrote: On 2/27/12 8:37 AM, Tom Lane wrote: Orion Poplawskior...@cora.nwra.com  writes: On 02/27/2012 09:09 AM, Tom Lane wrote: WTF?  Do I need to fix this, and

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Tom Lane
Kevin Kofler kevin.kof...@chello.at writes: Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the %{?dist} from local machine instead? It makes no sense.

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Kevin Kofler
Tom Lane wrote: Kevin Kofler kevin.kof...@chello.at writes: Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote machine? Why it takes the %{?dist} from local machine instead? It

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Mathieu Bridon
On Wed, 2012-02-29 at 05:31 +0100, Kevin Kofler wrote: Tom Lane wrote: Kevin Kofler kevin.kof...@chello.at writes: Vít Ondruch wrote: If you say to Koji that it should checkout master at remote machine, build a SRPM etc, why the Koji can't determine the proper %{?dist} at remote

Re: master branch still invokes build in f17-candidate??

2012-02-28 Thread Kevin Kofler
Mathieu Bridon wrote: I would certainly be very confused if `fedpkg mockbuild` produced a f17 rpm but `fedpkg build` produced an f18 one. build is the common case and should always work; srpm, mockbuild etc. are extras, I don't care if they break. Kevin Kofler -- devel mailing list

master branch still invokes build in f17-candidate??

2012-02-27 Thread Tom Lane
I'm definitely checked out in the master branch: [tgl@rh3 master]$ git push Counting objects: 11, done. Delta compression using up to 4 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 1.13 KiB, done. Total 6 (delta 3), reused 0 (delta 0) To

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Orion Poplawski
On 02/27/2012 09:09 AM, Tom Lane wrote: I'm definitely checked out in the master branch: [tgl@rh3 master]$ git push Counting objects: 11, done. Delta compression using up to 4 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 1.13 KiB, done. Total 6 (delta 3), reused

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Tom Lane
Orion Poplawski or...@cora.nwra.com writes: On 02/27/2012 09:09 AM, Tom Lane wrote: WTF? Do I need to fix this, and if so how? git pull (to bring in the f17 branch and mark devel as f18) Hmm, that package indeed hadn't had f17 git pull'd yet. (I had scripted a git pull in all my package

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Vít Ondruch
Dne 27.2.2012 17:09, Tom Lane napsal(a): I'm definitely checked out in the master branch: [tgl@rh3 master]$ git push Counting objects: 11, done. Delta compression using up to 4 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 1.13 KiB, done. Total 6 (delta 3), reused

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Jesse Keating
On 2/27/12 8:37 AM, Tom Lane wrote: Orion Poplawskior...@cora.nwra.com writes: On 02/27/2012 09:09 AM, Tom Lane wrote: WTF? Do I need to fix this, and if so how? git pull (to bring in the f17 branch and mark devel as f18) Hmm, that package indeed hadn't had f17 git pull'd yet. (I had

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Kevin Kofler
Jesse Keating wrote: I was looking for a way to determine the behavior of the master branch (for the sake of dist values) without hitting the network, as that would break git's ability to work offline. The best I could come up with at the time this code was written was to check and see what

Re: master branch still invokes build in f17-candidate??

2012-02-27 Thread Jesse Keating
On 2/27/12 5:53 PM, Kevin Kofler wrote: Jesse Keating wrote: I was looking for a way to determine the behavior of the master branch (for the sake of dist values) without hitting the network, as that would break git's ability to work offline. The best I could come up with at the time this code