landscape-client in oneiric-updates

Dmitrijs Ledkovs dmitrij.ledkov at ubuntu.com
Tue Jun 19 18:58:54 UTC 2012


On 19/06/12 18:16, Andreas Hasenack wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/19/2012 11:57 AM, Andreas Hasenack wrote:
>>> pull-lp-source landscape-client bzr init landscape-client cd 
>>> landscape-client bzr import-dsc 
>>> ../landscape-client_12.04.3-0ubuntu0.11.10.dsc
>>
>>> That will at least give you a branch you can work with. Though 
>>> obviously, it won't have full history nor can you use a merge 
>>> request with it. You'll still have to proved a debdiff in the
>>> end.
>>
>> Thanks, I didn't know about import-dsc either and did all that
> 
> Ok, I dislike import-dsc.
> 
> It commits and uses the debian/changelog for the commit message.
> 

This will help:

    $ cat ~/.bazaar/builddeb.conf
    [BUILDDEB]
    commit-message-from-changelog=False

Which bzr-builddeb are you using? Recent versions default to False.

> Which in my case means spamming the IRC channel with debian/changelog.
> 
> A huge one.
> 

Instead of, bzr commit, you could use:

    debcommit --edit

let's you edit before commiting, if you are doing a merge for example.

These two are better, if you have for example LP: #XYYYZZZ in the
changelog, debcommit / autocommit will automatically link the commit to
the bug leading to linking the branch on launchpad on push automatically
for you.

> In fact, I'm starting to dislike all these bzr "automations/plugins"
> that do unexpected things behind your back. It even mangles po files
> nowadays.
> 

The defaults are meant for majority / most common way of Ubuntu & Debian
packaging.

It is fully customizable to fit your workflow.

-- 
Regards,
Dmitrijs.



More information about the ubuntu-distributed-devel mailing list