Hi Bryce,

I've updated the stable-daily recipe to use 0.92.x and removed the {revno} from the stable recipe.  As soon as I'm back on a Linux machine, I can sort out the directory structure.

The recipe name changes sound fine too.  I've updated them accordingly.

AV

On 9 August 2017 at 03:31, Bryce Harrington <bryce@...961...> wrote:
On Wed, Aug 09, 2017 at 12:12:34AM +0100, Alex Valavanis wrote:
> OK, I've got it to the point where the *recipe* builds and uploads
> successfully.  I'm going to bed, and will hope to see a successful binary
> build in the morning!

Thanks, looks like it did indeed build.  I've finished up work for the
day so will give it a test, but fingers crossed.

It looks like the main change you made was to substitute
"0.92.2" for {debupstream-base:packaging}?  I wonder if the issue we ran
into here is this one?

  https://bugs.launchpad.net/launchpad/+bug/1435621

For the Cairo and Wayland ppas[1][2] I've had some success using that
variable to automatically substitute in the current release number from
the packaging's debian/changelog instead of needing to fiddle the recipe
each release, and was hoping we could do so similarly for Inkscape.

Oh, and I notice you set inkscape-stable-daily-git to pull
the "INKSCAPE_0_92_2" tag...  Actually I think that needs to be "0.92.x"
so it follows the branch as it changes.

> One thing we need to think about... the stable-daily packaging branch
> stores the packaging files in the /debian/ folder, whereas the stable and
> trunk branches stores them in root.  It probably makes sense to make all
> three branches store the files in /debian/ so we can do a simple merge,
> rather than a nest.

Yes, agreed, in fact I wanted to check if you'd be ok changing the trunk
recipe to that style too.

For the inkscape-stable-git recipe, do you think we could drop
"{revno}+" from the version string?  That PPA's always going to be
building against a given tag, so the revno is effectively fixed and just
makes the filename longer.  :-)

While we're at it, what do you think if we rename the recipes from:

 inkscape-stable-git
 inkscape-stable-daily-git
 inkscape-trunk-daily

to:

 inkscape-0.92-stable
 inkscape-0.92-stable-daily
 inkscape-trunk-daily

Here, I'm anticipating that when 0.93 is released we'll be wanting to
continue doing 0.92 stable builds too, since we've been positioning 0.92
as our LTS.  With all the massive changes going into 0.93, we might need
to continue maintaining 0.92 in parallel.

Bryce

1: https://code.launchpad.net/~bryce/+recipe/cairo-daily
2: https://code.launchpad.net/~wayland.admin/+recipe/wayland-daily


>
> AV
>
> On 8 August 2017 at 17:34, Bryce Harrington <bryce@...961...>
> wrote:
>
> > Our PPA to do autobuilds of releases broke with the switch from bzr to
> > git; I tried coaxing it back to life but no go so far.
> >
> > Is anyone familiar with creating .deb packages, and available right now
> > to help build a regular .deb package of Inkscape?  If so, catch me on
> > IRC.
> >
> > Bryce
> >
> > On Wed, Aug 02, 2017 at 08:08:35PM -0700, Bryce Harrington wrote:
> > > == Release Meeting ==
> > >
> > > Following the board meeting, 1pm Pacific time Friday, will be an
> > > opportunity to review status ahead of the release this weekend.  This
> > > meeting will be held on #inkscape-devel.  Everyone's welcome to attend,
> > > but particularly people who have been testing or developing the release
> > > candidate to gather feedback on any remaining issues.  I'd also love to
> > > see members of the new Vectors team to discuss announcement plans.
> > >
> > > Agenda:
> > >   * QA status / issues
> > >   * Translation team status
> > >   * Vector team status
> > >   * Web team status
> > >   * Release team status
> > >   * Final Go/No-go on release
> > >   * Other business
> > >
> > > There was also a question recently about policies for versions of
> > > dependencies (i.e. what do we target for LTS).  Time permitting we could
> > > discuss this a bit as well.
> > >
> > > Thanks,
> > > Bryce
> > >
> > > ------------------------------------------------------------
> > ------------------
> > > Check out the vibrant tech community on one of the world's most
> > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > > _______________________________________________
> > > Inkscape-devel mailing list
> > > Inkscape-devel@...1784...sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >
> > ------------------------------------------------------------
> > ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > Inkscape-devel mailing list
> > Inkscape-devel@...1784...sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel
> >