ok, so to recap... * test my changes locally (`cygport astyle.cygport all check` etc) * `git push` to ssh://cygwin.com/git/cygwin-packages/astyle/ * watch the scalliwag job: https://cygwin.com/cgi-bin2/jobs.cgi?srcpkg=astyle * deploy: ssh cyg...@cygwin.com "jobs deploy xxx" * compose announcement email: cygport astyle.cygport announce
I've done all that. So I think I'm done for now. Michael On Mon, Feb 3, 2025 at 12:36 AM Marco Atzeri via Cygwin-apps <cygwin-apps@cygwin.com> wrote: > > On 02/02/2025 18:29, Michael Cook wrote: > > Let's see if I understand correctly... > > > > In cygwin-packages I have this: > > > > $ git remote -v > > origin https://cygwin.com/git/cygwin-packages/astyle/ <https:// > > cygwin.com/git/cygwin-packages/astyle/> (fetch) > > origin https://cygwin.com/git/cygwin-packages/astyle/ <https:// > > cygwin.com/git/cygwin-packages/astyle/> (push) > > $ git status > > On branch master > > Your branch is up to date with 'origin/master'. > > > > > > > Then I can do > > > > cygport astyle.cygport all > > cygport astyle.cygport up > > > > Hi Michael, > > after the git push, SCALLYWAG will try to build your package, > see status for all at: > > https://cygwin.com/cgi-bin2/jobs.cgi > > if build succeded, than you can ask it to deploy its build with > > ssh cyg...@cygwin.com "jobs deploy 9355" > > as 9355 is the astyle ID build for this round. > > Using SCALLYWAG is very convenient if the upstream source is not > changing structure. > The logs are very useful to understand what went wrong if the > upstream package changed structure or build method. > > Regards > Marco
