makeself-2.2.0-2.fc20 not tagged as an update candidate

[Dridi Boukelmoune]

Hi,

I don't know whether this belongs to the packaging or devel list, but
I'm stuck somewhere in the workflow for this package. I recently
noticed it wasn't available for Fedora 20 and decided to push it in
the repos.

So I did this:
dridi@localhost ~/fedora/makeself (f20 u=)$ fedpkg update
Creating a new update for  makeself-2.2.0-2.fc20
Password for dridi:
Creating a new update for  makeself-2.2.0-2.fc20
makeself-2.2.0-2.fc20 not tagged as an update candidate

So I've tried to build it then:
dridi@zenika ~/fedora/makeself (f20 u=)$ fedpkg build
Could not execute build: makeself-2.2.0-2.fc20 has already been built

I don't know what I've done differently between the f1? branches and f20:
https://koji.fedoraproject.org/koji/buildinfo?buildID=458671 (f18)
https://koji.fedoraproject.org/koji/buildinfo?buildID=458670 (f19)
https://koji.fedoraproject.org/koji/buildinfo?buildID=458672 (f20)

Best,
Dridi

[Tom Hughes]

On 16/10/13 08:40, Dridi Boukelmoune wrote:

>  So I did this:
>  dridi@localhost ~/fedora/makeself (f20 u=)$ fedpkg update
>  Creating a new update for  makeself-2.2.0-2.fc20
>  Password for dridi:
>  Creating a new update for  makeself-2.2.0-2.fc20
>  makeself-2.2.0-2.fc20 not tagged as an update candidate 
You can't make an update for it because it's already in f20.

It looks like it was built before the updates system was turned on for 
f20 so it never actually needed to go through as an update and 
automatically went in to the tree as soon as it was built.

Tom

-- 
Tom Hughes (tom(a)compton.nu)
http://compton.nu/

[Dridi Boukelmoune]

OK, this is strange, I don't see it in bodhi:

$ bodhi -m
Password for dridi:
 numatop-1.0.1-5.fc20                         newpackage   testing   2013-10-13
 numatop-1.0.1-5.fc18                         newpackage   testing   2013-10-14
 numatop-1.0.1-5.fc19                         newpackage   testing   2013-10-14
 makeself-2.2.0-2.fc18                        newpackage   stable    2013-09-03
 makeself-2.2.0-2.fc19                        newpackage   stable    2013-08-24
5 updates found

I've filed a BZ [1], thank you for your help.

Dridi

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1019668

On Wed, Oct 16, 2013 at 8:58 AM, Tom Hughes <tom(a)compton.nu&gt; wrote:
>  On 16/10/13 08:40, Dridi Boukelmoune wrote:
>
> > So I did this:
> > dridi@localhost ~/fedora/makeself (f20 u=)$ fedpkg update
> > Creating a new update for  makeself-2.2.0-2.fc20
> > Password for dridi:
> > Creating a new update for  makeself-2.2.0-2.fc20
> > makeself-2.2.0-2.fc20 not tagged as an update candidate
>
>
>  You can't make an update for it because it's already in f20.
>
>  It looks like it was built before the updates system was turned on for f20
>  so it never actually needed to go through as an update and automatically
>  went in to the tree as soon as it was built.
>
>  Tom
>
>  --
>  Tom Hughes (tom(a)compton.nu)
>  http://compton.nu/
>  --
>  packaging mailing list
>  packaging(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/packaging

[Tom Hughes]

On 16/10/13 09:37, Dridi Boukelmoune wrote:

>  OK, this is strange, I don't see it in bodhi: 
It never went through bodhi, because bodhi wasn't active for F20 at the 
time. Bodhi is only turned on after the release has branched, and there 
is usually a short delay of a few days between branching and it being 
turned on.

F20 was branched on 20th August, and your build was on 23rd. Bodhi 
wasn't enabled until 4th September when the Alpha Change freeze hit.

Tom

-- 
Tom Hughes (tom(a)compton.nu)
http://compton.nu/

[Dridi Boukelmoune]

So any build before the freeze is automatically added to the distribution ?

On Wed, Oct 16, 2013 at 9:47 AM, Tom Hughes <tom(a)compton.nu&gt; wrote:
>  On 16/10/13 09:37, Dridi Boukelmoune wrote:
>
> > OK, this is strange, I don't see it in bodhi:
>
>
>  It never went through bodhi, because bodhi wasn't active for F20 at the
>  time. Bodhi is only turned on after the release has branched, and there is
>  usually a short delay of a few days between branching and it being turned
>  on.
>
>  F20 was branched on 20th August, and your build was on 23rd. Bodhi wasn't
>  enabled until 4th September when the Alpha Change freeze hit.
>
>
>  Tom
>
>  --
>  Tom Hughes (tom(a)compton.nu)
>  http://compton.nu/
>  --
>  packaging mailing list
>  packaging(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/packaging

[Tom Hughes]

On 16/10/13 09:57, Dridi Boukelmoune wrote:

>  So any build before the freeze is automatically added to the
> distribution ? 
The details are all in the updates policy:

   http://fedoraproject.org/wiki/Updates_Policy#Branched_release

Strictly speaking that says bodhi is enabled as soon as the branch 
happens but in practice there has always been a short delay and on this 
occasion it doesn't seem to have happened until Alpha Freeze as far as I 
can see from the announcements on the devel list.

Tom

-- 
Tom Hughes (tom(a)compton.nu)
http://compton.nu/