[02:55] <tsimonq2> Unit193: syncpackage: Error: Debian version 1.4.1-1 has not been picked up by LP yet. Please try again later.
[02:56] <tsimonq2> Unit193: (typically dinstall + two hours is a safe bet)
[02:56] <Unit193> Nevertheless.
[02:58] <tsimonq2> Yep.
[02:59] <tsimonq2> Unit193: When are you going to be able to do this yourself again? :P
[03:00] <Unit193> You keep asking, I keep answering the same thing.  Also technically not up to me.
[03:01] <tsimonq2> Maybe you could find enough people in the US on the board to schedule a meeting and still have quorum.
[03:02] <tsimonq2> Now that I look, only two members aren't in the US+Canada part of the world.
[03:03] <tsimonq2> So you might be able to talk to them and figure something out, if doing it over email isn't an option.
[03:03] <tsimonq2> (iirc you only need four people for quorum)
[05:59] <Unit193> Weell that's veery interesting then.  Diff between xca Ubuntu/Debian:
[05:59] <Unit193>  xca (1.4~pre3-1) unstable; urgency=medium
[05:59] <Unit193>    [ Tino Mettler ]
[05:59] <Unit193> -  * New upstream git snapshot from commit ead8320a
[05:59] <Unit193>    * As XCA does not use QT4 anymore, mention just QT in the short description
[05:59] <tsimonq2> Harumph. :/
[06:02] <Unit193> Only upstream diff is Debian doesn't have ./configure, so what I'm guessing is this tarball was created in git.
[06:02] <Unit193> (Not downloaded.)
[06:02] <tsimonq2> Sigh, c'mon Debian.
[06:02] <Unit193> It's an actual workflow.
[06:03] <Unit193> Git repo's 'upstream' being upstream's repo.  In theory, pristine-tar/actual tarball should be the upstream tarball, buuuut.
[06:03] <tsimonq2> I guess.
[06:04] <tsimonq2> But then upstream, y u no keep what you release and your Git repository consistent?
[06:04] <Unit193> Because autotools so the release tarballs will have at least ./configure?  Really, it's GNU to blame here. :>
[06:05] <tsimonq2> Heh.
[06:51] <persia> Almost nobody keeps their git repo and release tarballs consistent.  Lots of people have strong arguments for why it is better to have a careful release process (and for users not to use SCM code).
[06:52] <Unit193> As a DM, I use upstream tarballs, committing to upstream and the delta to pristine-tar. :3
[06:54] <persia> That is commendable behaviour, but definitely a downstream attitude (as you have the luxury of consuming a signed tarball).
[06:55] <Unit193> Xfce is pretty fantastic about their releases, sure they're not signed but they never re-release or any other weirdness.
[06:59] <Unit193> persia: I do get what you're saying though, it can be hard to host tarballs too.  I have one where I have no idea how I'll handle releases now. :/
[07:00] <persia> No, actually I'm saying that folk that host tarballs tend to have careful processes to prepare, sign, and host them, and this means there are usually all sorts of differences between release tarballs and the source code management system, often including things that are hard to blame on autotools.
[07:01] <persia> And there are a vast number of components (especially core components) that are difficult to build from SCM, as the right bits aren't always there.
[07:02] <Unit193> Ah, autotools was (partially) a joke, just one that happens a lot.  Yes there can be a lot involved.
[09:42] <Unit193> tsimonq2: Confirmed, generated from git repo.
[09:43] <tsimonq2> Unit193: Ah ok.
[21:24] <Unit193> tsimonq2: So did you want to take care of those libayatana-appindicator and libayatana-indicator syncs?
[23:28] <tsimonq2> Unit193: Sure.
[23:30] <tsimonq2> Unit193:
[23:30] <tsimonq2> grr
[23:30] <tsimonq2> .