How do I link my personal branch to my project branch

Asked by linuxrules

How do I link my personal branch (https://code.launchpad.net/~linuxrules/+junk/YaTC) to my project branch (https://code.launchpad.net/yatc)

and where and How do I package it

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Edwin Grubbs Edit question
Solved by:
Edwin Grubbs
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
linuxrules (linuxrules) said :
#1

I think i got it I did the command bzr push lp:~linuxrules/yatc/trunk --use-existing-dir
in the personal branch, but now what do I do to the personal branch?

Revision history for this message
linuxrules (linuxrules) said :
#2

marked personal branch abandoned
with the question "and where and How do I package it" how does a ppa work and how do I do it?
 I looked at "https://help.launchpad.net/Packaging/PPA" and don't understand

Revision history for this message
Edwin Grubbs (edwin-grubbs) said :
#3

I see that you were able to link your branch to the development focus series, which in turn makes it the default branch for the project, lp:yatc.

Here are the directions for building a package from a branch:
https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted

It still requires you to have a good understanding of how to build a package. If you have not built an Ubuntu package on your local machine before, you may want to look at these directions:
https://wiki.ubuntu.com/PackagingGuide/Complete

If you don't need to update the package often, or if you are just modifying an existing package. You may find it easier to use dput to upload a source package that will be built into a binary package.
https://help.launchpad.net/Packaging/PPA/Uploading

Revision history for this message
linuxrules (linuxrules) said :
#4

Thanks Edwin Grubbs, that solved my question.

Revision history for this message
linuxrules (linuxrules) said :
#5

I see we have an expert on our hands:
https://code.launchpad.net/~edwin-grubbs

Revision history for this message
linuxrules (linuxrules) said :
#6

Two more questions:

1) I have more access to my OpenSuSE laptop than my Ubuntu desktop
and I don't know how I can create a PPA without Ubuntu, how can I do it?

2) how do I automatically create a change log
I use the command "bzr log --gnu-changelog -v > change.log"
but that causes uncommitted errors.

Revision history for this message
Edwin Grubbs (edwin-grubbs) said :
#7

> 1) I have more access to my OpenSuSE laptop than my Ubuntu desktop
> and I don't know how I can create a PPA without Ubuntu, how can I do it?

It would definitely be more difficult to create a deb source package on OpenSuSE than on Ubuntu. If you don't want to run Ubuntu directly on your laptop, you could run Ubuntu in a virtual machine such as KVM or VirtualBox. I'm not sure which one is recommended for OpenSuSE. If don't run Ubuntu with Gnome or KDE, the memory requirements will be much smaller. The Ubuntu Server iso image or the Ubuntu Mini Remix may help you get a VM running using minimal memory and hard drive space.

http://www.ubuntu.com/server/get-ubuntu/download
http://www.ubuntu-mini-remix.org/

> 2) how do I automatically create a change log
> I use the command "bzr log --gnu-changelog -v > change.log"
> but that causes uncommitted errors.

I really don't understand why you are getting that error. What version of bzr are you running? Can you paste the full error message?

Revision history for this message
linuxrules (linuxrules) said :
#8

I do this:

mitch@MitchPC:~> cd bzr
mitch@MitchPC:~/bzr> cd YaTC/trunk/
mitch@MitchPC:~/bzr/YaTC/trunk> bzr log --gnu-changelog -v > change.log
mitch@MitchPC:~/bzr/YaTC/trunk> bzr push lp:yatc
bzr: ERROR: Working tree "/home/mitch/bzr/" has uncommitted changes (See bzr status). Use --no-strict to force the push.
mitch@MitchPC:~/bzr/YaTC/trunk> bzr status
modified:
  YaTC/trunk/change.log
unknown:
  YaTC/trunk/YaTC/YaTC.pl.bak
mitch@MitchPC:~/bzr/YaTC/trunk>

To correct the error I do this:
bzr push lp:yatc --no-scrict

But is this the right way to update a change log?

Revision history for this message
linuxrules (linuxrules) said :
#9

Oh, by the way I have & use virtual box so I will put Ubuntu there.

Revision history for this message
linuxrules (linuxrules) said :
#10

maybe i could do this:
.
bzr commit -m "foo renamed to bar"
bzr log --gnu-changelog -v > change.log
bzr commit -m "Update to change.log"
bzr push lp:yatc

Revision history for this message
Best Edwin Grubbs (edwin-grubbs) said :
#11

Right, you want to commit the change.log before you push.

Revision history for this message
linuxrules (linuxrules) said :
#12

Thanks

Revision history for this message
linuxrules (linuxrules) said :
#13

Thanks Edwin Grubbs, that solved my question.