[Pkg-ltsp-devel] pkg-ltsp bzr repository status and more.

[Petter Reinholdtsen]

[Gustavo Franco]
> Hi list,
>
> There's a pkg-ltsp "official" repository being prepared right now to
> host the branch(es) that we should use to do the upcoming ltsp Debian
> package uploads.

Sounds good.  But until that is ready, I'll try to get a new release
out based on my old branch.

> We used mdz as a start point and it's already available[0], but you
> *don't* want to branch out from that tree yet. claviola converted both
> vagrant and pere repositories from baz to bzr and otavio merged them
> over pkg-ltsp branch in a different location[1].

When will this be ready to branch from?  Can I get a branch of my old
branch with a common anchestor with Matt and Oliver?

> What needs to be done before the first pkg-ltsp upload:
>
> * You can review [1] and let us if there's something weird there;

There is.  There are typos in ltsp-build client:

=== modified file 'server/ltsp-build-client'
--- server/ltsp-build-client
+++ server/ltsp-build-client
@@ -176,14 +176,15 @@
          echo "ERROR: unsupported --arch argument: "$ARCH_OPT
          exit 1
          ;;
-      esac
+      esac
+      ;;
     --help) get_help
       exit 0
       ;;
-    --serial-console) use_serial_console="true"
+    --serial-console) use_serial_console="true" ;;
     --disable-rootpass) ROOTPASS="disable" ;;
     --prompt-rootpass) ROOTPASS="prompt" ;;
-    --debconf-seeds) DEBCONF_SEEDS="$2"
+    --debconf-seeds) DEBCONF_SEEDS="$2" ;;
     *) echo "ERROR: unknown option: $1"
       get_help
       exit 1


I have not figured out how to push my branch to a public site yet, so
I provide the patch instead. :)

I also noticed that the uploaders list in debian/control was wrong, so
I wonder if this is really based on my branch or not.

> * Otavio will "replace" pkg-ltsp repository[0] content with [1], at
> this point we will have mdz + pere + vagrant in place. It will be
> the pkg-ltsp start point in terms of repository;

OK.

> * ogra changes. We need to hear his feedback, and see what we can
> merge back from his branches

We imediately want his sound support patches, and probably a few
others.

> * pqm[2]. Each person involved will maintain at least one branch and
> we will have a central one at alioth, it would be good use a patch
> queue manager. The main idea behind that, is ask for merges by mail,
> and let the script handle some of the workload in the central
> repository.

What is the alternative to this?  Earlier, we just picked one branch
as the "official" branch, and used it to release.  Matts branch (and
now Olivers branch) was used for ubuntu, and mine was used for Debian.
Is that a working alternative?