[pkg-boost-devel] Bug#583862: standalone asio package into pkg-boost

[Markus Wanner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Daniel,

On 02/22/2013 08:19 PM, Daniel Pocock wrote:
> I've also created a git VCS for tracking the asio package, it is 
> currently under collab-maint

Cool.

> but I'd like to move it under pkg-boost control.  Can one of the
> pkg-boost admins please enable git through alioth?

Uh.. given the point of the separate asio package is to be independent
from boost, does it really make sense to join the boost packaging team
in Debian?

It might well make sense - maybe not technically, but from an
organizational perspective. I just want to check.

> Markus, I'm not sure how far down the process you are, but can you
> do the following:
> 
> - - if your PGP key is already signed by any DDs, could you send a 
> signed email to all of us (reply to this email)?

I've got some signatures, but I'm not sure if any is from a DD. How do
I check? (Email should be signed).

> - - and joining the pkg-boost mailing list is a separate step: 
> http://lists.alioth.debian.org/mailman/listinfo/pkg-boost-devel

Done.

> - - there is a script here: 
> http://anonscm.debian.org/gitweb/?p=collab-maint/asio.git;a=tree;f=debian/scripts;hb=HEAD
>
>  that will fetch all 1.4.x releases for import.  I got up to 1.4.3 
> which requires a manual correction upon merging.  The procedure to 
> import them:
> 
> mkdir ~/ws/asio-deb cd ~/ws/asio-deb git clone
> git://git.debian.org/git/collab-maint/asio.git 
> asio/debian/scripts/downloads.sh cd asio git-import-orig -u 1.4.3
> ../asio_1.4.3.orig.tar.gz (... resolve any issue, finish the merge
> ...) git-import-orig -u 1.4.4 ../asio_1.4.4.orig.tar.gz

I'm not quite following. What problem are you trying to solve, here?
Want some history of the asio code in your git repo?

> It's better to import the intermediate packages rather than just 
> importing 1.4.8, because you won't be able to import them easily
> after 1.4.8

Note that I've tried to clean up asio-1.4.1 and resolve existing bugs,
first. However, that didn't work out and caused more problems than it
solved.

With Simon, we decided to not care about earlier versions and just
continue with packaging 1.4.8.

Regards

Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREDAAYFAlEnyO0ACgkQsPwMloDjyo/fEgCfRrInaUkrNXuI75sXsjmjhfPy
/QsAoIMmw0Bt3ePCFqiGGBJp3sCm6Les
=toT/
-----END PGP SIGNATURE-----