new package built, now what?

[Alois Mahdal]

Hi,

so I'm following "Join the package collection maintainers", I'm at the
late phase when I've submitted new package, ran `fedpkg build` from
master, koji is happy, etc.


https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd...

Now I tried to just follow with "Update Your Branches (if desired)", but
that fails, because F27 and F28 branches don't exist -- OTOH I don't
expect them to spawn from nowhere; both versions are already released,
so I wonder if it's even possible to add new ones.

So what should I do?  Just forget about F27/F28 and wait for F29?  Do
[something] to have the F27/28 branches created?

And should the guide be updated?  (It seems that this will happen to
every new package)


Thanks,
aL.

PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
"jump through these hoops", I'm asking because I want to notify upstream
yet I kinda don't know what can I tell them. :D


-- 
Alois Mahdal <amahdal(a)redhat.com&gt;
Platform QE Engineer at Red Hat, Inc.
#brno, #daemons, #preupgrade

[Robert-André Mauchin]

On jeudi 28 juin 2018 23:43:09 CEST Alois Mahdal wrote:
>  Hi,
>  
>  so I'm following "Join the package collection maintainers", I'm at the
>  late phase when I've submitted new package, ran `fedpkg build` from
>  master, koji is happy, etc.
>  
>  
>  https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=Pa
>  ckageMaintainers/Join#Import.2C_commit.2C_and_build_your_package 
 
>  Now I tried to just follow with "Update Your Branches (if
> desired)", but
>  that fails, because F27 and F28 branches don't exist -- OTOH I don't
>  expect them to spawn from nowhere; both versions are already released,
>  so I wonder if it's even possible to add new ones.
>  
>  So what should I do?  Just forget about F27/F28 and wait for F29?  Do
>  [something] to have the F27/28 branches created?
>  
>  And should the guide be updated?  (It seems that this will happen to
>  every new package)
>  
>  
>  Thanks,
>  aL.
>  
>  PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
>  "jump through these hoops", I'm asking because I want to notify upstream
>  yet I kinda don't know what can I tell them. :D
>  
>   
You can request new branches just after requesting your repo:

fedpkg --module-name ydiff request-branch f28
fedpkg --module-name ydiff request-branch f27

fedpkg --module-name slop request-branch f28
fedpkg --module-name slop request-branch f27

(You can omit --module-name if you running the command from within the already 
created GIT repo).

Then wait for Gwyn to do her magic.

Afterwards you can:

 1. git pull to get the new branches
 2. fedpkg switch-branch f28
 3. git merge master
 4. fedpkg push
 5. fedpkg build
 6. fedpkg update

[Christopher]

Maybe run the following? Not sure. Hard to find docs on this.
    fedpkg request-branch f28


On Thu, Jun 28, 2018 at 5:51 PM Alois Mahdal <amahdal(a)redhat.com&gt; wrote:

>  Hi,
>
>  so I'm following "Join the package collection maintainers", I'm at the
>  late phase when I've submitted new package, ran `fedpkg build` from
>  master, koji is happy, etc.
>
>
>
>
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd...
>
>  Now I tried to just follow with "Update Your Branches (if desired)", but
>  that fails, because F27 and F28 branches don't exist -- OTOH I don't
>  expect them to spawn from nowhere; both versions are already released,
>  so I wonder if it's even possible to add new ones.
>
>  So what should I do?  Just forget about F27/F28 and wait for F29?  Do
>  [something] to have the F27/28 branches created?
>
>  And should the guide be updated?  (It seems that this will happen to
>  every new package)
>
>
>  Thanks,
>  aL.
>
>  PS: I don't want to sound impatient; I'm OK if the answer is "wait" or
>  "jump through these hoops", I'm asking because I want to notify upstream
>  yet I kinda don't know what can I tell them. :D
>
>
>  --
>  Alois Mahdal <amahdal(a)redhat.com&gt;
>  Platform QE Engineer at Red Hat, Inc.
>  #brno, #daemons, #preupgrade
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>
> https://lists.fedoraproject.org/archives/list/[e-mail].o...
>

[Matthew Miller]

On Thu, Jun 28, 2018 at 05:58:55PM -0400, Christopher wrote:
>  Maybe run the following? Not sure. Hard to find docs on this.
>      fedpkg request-branch f28 
Documented here:

https://fedoraproject.org/wiki/Changes/fedrepo-req-to-fedpkg


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Adam Williamson]

On Thu, 2018-06-28 at 18:13 -0400, Matthew Miller wrote:
>  On Thu, Jun 28, 2018 at 05:58:55PM -0400, Christopher wrote:
>  > Maybe run the following? Not sure. Hard to find docs on this.
>  >     fedpkg request-branch f28
>  
>  Documented here:
>  
>  https://fedoraproject.org/wiki/Changes/fedrepo-req-to-fedpkg 
No it isn't. A Change page is not documentation. It's essentially a
transient thing that documents the Change itself for the purpose of the
Change process.

If this is a permanent step in a permanent packager process it should
be documented in the actual documentation of that packager process.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Matthew Miller]

On Thu, Jun 28, 2018 at 03:23:35PM -0700, Adam Williamson wrote:
>  > > Maybe run the following? Not sure. Hard to find docs on
> this.
>  > >     fedpkg request-branch f28
>  > Documented here:
>  > https://fedoraproject.org/wiki/Changes/fedrepo-req-to-fedpkg
>  No it isn't. A Change page is not documentation. It's essentially a
>  transient thing that documents the Change itself for the purpose of the
>  Change process. 
Oh, yeah, I agree -- I was just shorter than I should have been. I'd
really like to see this documented along with other packaging tools and
process at ttps://docs.fedoraproject.org/

That's not even a proper Change page, and it's not clear if it's meant
to be, or was just put in that namespace.


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Alois Mahdal]

On 06/28/2018 11:43 PM, Alois Mahdal wrote:
>  Hi,
>  
>  so I'm following "Join the package collection maintainers", I'm at the
>  late phase when I've submitted new package, ran `fedpkg build` from
>  master, koji is happy, etc.
>  
>  
>
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd...
>  
>  Now I tried to just follow with "Update Your Branches (if desired)", but
>  that fails, because F27 and F28 branches don't exist -- OTOH I don't
>  expect them to spawn from nowhere; both versions are already released,
>  so I wonder if it's even possible to add new ones.
>  
>  So what should I do?  Just forget about F27/F28 and wait for F29?  Do
>  [something] to have the F27/28 branches created? 
Thanks for all the replies.  My newpkg updates are already in bodhi! :-)


>  And should the guide be updated?  (It seems that this will happen to
>  every new package) 
Seems like it should.  Filed as BZ#1596438.

aL.

-- 
Alois Mahdal <amahdal(a)redhat.com&gt;
Platform QE Engineer at Red Hat, Inc.
#brno, #daemons, #preupgrade