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

Daniel Pocock daniel at pocock.com.au
Fri Feb 22 23:26:46 UTC 2013

Hash: SHA256

On 22/02/13 20:37, Markus Wanner wrote:
> 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.

This won't create any technical connection between the packages.

I just think that as there is so much overlapping code, and it is
likely that some bug fixes will overlap, then there is some
compatibility with the pkg-boost team

>> 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).

You probably need to write a script that extracts all the email
addresses of all the people who signed your key

Then do the same thing to the debian keyring - import the DD keys with
all their email addresses, and then export the email addresses to a
text file

Finally, compare the text files to find out if anything overlaps

>> - - 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?

Yes, exactly

Also, if we do persuade the release team to take an updated package in
wheezy, they might only take 1.4.2, not 1.4.8

I notice 1.4.2 has the fix for the issue with clang, for example, so
it would still be a small victory

>> 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.

In any case, you wouldn't `release' all the intermediate versions, and
you wouldn't even mention them in debian/changelog.  If it wasn't for
the merge conflict in 1.4.3, I would have imported them all with a script.

Once you get them into git, they will just be on the `upstream'
branch, in case they are needed for some future purpose.  It can be
convenient to browse the history with gitk too.

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


More information about the pkg-boost-devel mailing list