Please sync to 2.2.0 release

[Jeffrey Baker]

Binary package hint: gerbv

Gerbv 2.2.0 was released in January 2009. It fixes many problems, including a crash in the PDF exporter which is quite common. 2.2.0 builds cleanly on Jaunty amd64.

[Stefan Petersen (spe)]

There is actually a 2.3.0 release available. If the packaging team needs to gets updates into the source to simplfy packaging please contact me or the gerbv developing team. It would be great if 2.3.0 would be available for Karmic.

[Kelvin Gardiner (kelvingardiner)]

I've packaged version 2.3.0 for amd64, which I've attached. This is my first attempt at a package hopeful it's okay.

[Scott Howard (showard314)]

Thanks for your help, Kelvin!

1) This package is an automatic import from Debian. Debian has not upgraded it in over 8 months [1], so Ubuntu still has the old version. Our choices are to push Debian to get the new package, either by supplying them a debdiff of the new package or by doing an NMU or to upgrade it for Ubuntu, and let Debian know we upgraded it. In general, the first method is preferred, but if you are unfamiliar with Debian work, packaging solely in Ubuntu and just drop a note in the Debian BTS.

2) Thanks for the .deb, but Debian/Ubuntu works with source packages (the three "files" of .dsc, .orig.tar.gz, .diff.gz). See:
https://wiki.ubuntu.com/PackagingGuide/Complete
To get this sponsored, you should generate a "debdiff" of the old package to new package with somethieng like the following:
$ debdiff <old package>.dsc <new package>.dsc > gerbv_upgrade.debdiff

that command will make a patch file that shows the work you did. To make a source package, either use the "dpkg-buildpackge -S" command or use "pbuilder" [2] from the source directory.

Then upload the debdiff as a patch to this bug

MOTU sponsors can look at this patch and sponsor the upload of the source package.

So, for now you can make a "debdiff" of the package you already made, and upload it here for the MOTU sponsors. We can then work to get it into Debian, and us re-sync with Debian.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539237
[2] https://wiki.ubuntu.com/PbuilderHowto

[Kelvin Gardiner (kelvingardiner)]

Thanks, for your reply Scott. I've attached the diff file.

[Scott Howard (showard314)]

Thanks, I think you should read over the Ubuntu packaging guide and
some of the MOTU classroom sessions" on packaging. I didn't look that
closely, but I caught at least two critical things:

1) Don't delete the debian/changelog In fact, you keep it and
append your changes. There is a helper program called "dch" that will
help you format and change it properly. If you type "dch -i" it will
add an entry for you, make sure the name and email matches yours and
that the version number is correct (see the ubuntu wiki on how to do
that). Add that it is an upgrade from upstream, place " (LP:
#374343) " somewhere in the description. The version number should
be something like:
<packagename>_<versionnumber>-0ubuntu1

0ubuntu1 means:
0 --> not in Debian
ubuntu --> ubuntu local changes that are not in Debian
1 --> first revision in Ubuntu

2) debian/control needs to be formatted as described on the wiki. You
put Ubuntu developers or MOTU down as the maintainer (whatever the
wiki says to do) and make the debian maintainer the XSBC maintainer
like below:
Maintainer: Ubuntu MOTU Developers <email address hidden>
XSBC-Original-Maintainer: Captain Packager <email address hidden>

also in debian/control : Don't change the section and the priority.
They have important meanings (see the Debian Policy Manual:
http://www.debian.org/doc/debian-policy/)

3) In general we want these packages to be as close to the Debian
packages as possible, so we want to do the minimal changes possible.
If a simple upgrade of the upstream source code builds, all you should
need to do is increment the changelog "dch -i" and then change the
maintainer in debian/control as above (this is all described on the
wiki).

If you have questions, check on #ubuntu-motu, people are very helpful there!

[Kelvin Gardiner (kelvingardiner)]

I've removed the old debdiff and attached the new version. I've followed the process on the wiki for updating packages, and only made the changes given on the wiki.

I think the changelog error was due to creating a package from scratch last time out of interest before working on the patch.

The old /debian directory had a patch file in that has already been applied to the new code, I had a chat on #ubuntu-motu about how to handle this, and have removed the patch file.

Hopeful the new diff should be much better.

[Fabrice Coutadeur (fabricesp)]

Hi,

Can you please review your debdiff, as I'm seeing a lot of generated files that shouldn't be there: the debdiff should contains only files inf the debian directory.

thanks,
Fabrice

[Kelvin Gardiner (kelvingardiner)]

Fabrice,

Thanks for your reply. I followed the packaging guide to create the debdiff. How can I generate the debdiff with only the debain directory changes? Why does the debdiff only need these changes and not the code changes as well?

Thanks

[Michael Bienia (geser)]

gerbv 2.3.0-1 got synced into Ubuntu lucid.