Ubuntu PPA Maintenance Coordination

[NormandC]

If you remove it quickly, it will effect fewer people.

It's too late, once the package is uploaded, I can't upload a lower version anymore because Launchpad will refuse it, even if I deleted the previous one.

This is why I wanted to remove the epoch number (1:) for Xenial:

0.16 < 0.17 < 1:0.16

[NormandC]

All that said it doesn't build https://code.launchpad.net/~clhclh/+rec ... usty-daily

I can't tell what you wrote as recipe, since it's under your own name I can't edit it. Would you mind pasting the recipe contents here?

When I hover my mouse over the two lp: links, I get a tooltip saying

No such product: '+git'.

The Could not be uploaded correctly error was after this commit https://git.launchpad.net/~freecad-main ... 607dcfedd1

I'm guessing you were trying to work around the failed binary build where you got this error?

https://launchpadlibrarian.net/25443571 ... ING.txt.gz

Code: Select all

-- Build files have been written to: /«PKGBUILDDIR»/obj-x86_64-linux-gnu
cp -f src/Build/Version.h obj-x86_64-linux-gnu/src/Build/Version.h
cp: cannot stat ‘src/Build/Version.h’: No such file or directory
make[1]: *** [override_dh_auto_configure] Error 1

And I guess you noticed that in the same build log, you have this:

Code: Select all

/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/Build/Version.h written

Which seems to indicate that the Version.h file is generated, somthing that didn't work with the bazaar repo.

I'm trying to catch up...

[sgrogan]

I'm trying to catch up...

Me too. I will post answers tomorrow. I'm my nieces algebra tutor so time is tight.
I think we need to copy the eigen packages from the daily to the stable. I'm looking at thishttps://help.launchpad.net/Packaging/PPA/Copying but it doesn't seem directly relevant.

[NormandC]

I think we need to copy the eigen packages from the daily to the stable.

What's the problem with the Stable PPA?

Shoot. I'm just now realizing that I've seen errors tonight in the Report view about SparseQR not being compatible. I was wondering why Abdullah uploaded these Eigen3 packages to the Daily Builds, I guess this explains it.

This means I'll have to build the Stable packages again.

Copying packages from a PPA to another is easy. In the PPA page you want to copy packages from, you click on "View package details", then at top right, you will get two links, "Copy packages" and "Delete packages". Then the "Copy packages" page is pretty straightforward. Just select "Copy existing binaries" instead of "Rebuild the selected sources", and for Destination series select "The same series". And of course, the destination PPA.

[sgrogan]

Thanks,

This means I'll have to build the Stable packages again.

Hold tight there has been at least one commit backported to 0.16. There might be one more?

Copying packages from a PPA to another is easy

OK, I think I get it, what if you want to copy across a series. I can change the series but not the package name.
See for instance my failed attempt for ccx for wiley on the daily PPA.

[NormandC]

I can change the series but not the package name.

Package names cannot be changed, they need to be rebuilt.

See for instance my failed attempt for ccx for wiley on the daily PPA.

I can't find any trace of this attempt anywhere.

[sgrogan]

See here:https://launchpad.net/~freecad-maintain ... /+packages
The package is named ccx - 2.7-1ppa2~trusty1 but I published it under the wily series. I think your previous answer solves it for me.
Thanks for your patience. Every answer leads to two new questions for me. I think I'm finally starting to realize what I don't know. I've gone back to here: https://www.debian.org/doc/manuals/main ... ex.en.html In the past I've skimmed for a solution. Now I'm reading for comprehension.

[NormandC]

See here:https://launchpad.net/~freecad-maintain ... /+packages
The package is named ccx - 2.7-1ppa2~trusty1 but I published it under the wily series.

The ccx - 2.7-1ppa2~trusty1 package I see there is listed under the Trusty series, I see no such package listed for Wily.

The ~trusty1 suffix is taken from the changelog, no way around that. If a package doesn't need to be recompiled between different Ubuntu versions, then it can be named without the suffix:

Code: Select all

ccx (2.7-1ppa2) trusty; urgency=low

But most of our packages need to be built with specific library versions.

[NormandC]

In regard to viewtopic.php?f=4&t=15222&start=20#p122217

All that said it doesn't build

I'm testing a local build.

1. I git cloned master from Github into "freecad"

   Code: Select all

   git clone https://github.com/FreeCAD/FreeCAD.git freecad

2. I copied the debian folder into it
3. I used your latest rules file https://git.launchpad.net/~freecad-main ... bian/rules
4. I used all the other files from my Stable trusty package: freecad_0.16.6700-1ppa1~trusty1.debian.tar.gz
5. I edited the version in the changelog:

   Code: Select all

   freecad (0.17~alpha-1ppa1~trusty1) trusty; urgency=low

6. I edited debian/sources/format and set it to 1.0 like the Daily Builds so debuild does not require a tarball. (For the Stable PPA, the format file contains "3.0 (quilt)" which requires a tarball)
7. Then I ran debuild, without options.

   Code: Select all

   cd freecad
   debuild

This creates source packages and binary packages, but only for the host system architecture.

The build just finished successfully, I will install it to test.

Error: a more recent package is already installed.

Dammit! The 1: epoch number strikes again. I hate that thing. Will have to uninstall my 1:0.16.6700 package first.

[NormandC]

Yesssssssss!

FC_0.17.7423_01.png (180.27 KiB) Viewed 1477 times

This is taken from the freecad_0.17~alpha-1ppa1~trusty1_amd64.deb package I built following the process in my previous post.

This proves we don't require a versioning branch anymore. Now to find out why your recipe won't successfully build...

Hey, I have a thought:

Code: Select all

# git-build-recipe format 0.4 deb-version 0.17-1ppa1
lp:~freecad-maintainers/+git/gitmaster
nest-part packaging lp:~freecad-maintainers/+git/gitpackaging-trusty debian

Have you looked at https://help.launchpad.net/Packaging/So ... ds/Recipes

If you're using git, then the format is similar, but you should normally provide a branch name as a revision specifier (if you don't, then the recipe builder will assume HEAD):

lp:germinate master

Also, nest-part is supposedly still not supported with git. So maybe it's best using merge.

If you're using git, then the format is similar, but you should normally provide a branch name as a revision specifier:

merge fix-build lp:~contributor/germinate fix-build

In theory, your recipe should look like this

Code: Select all

# git-build-recipe format 0.4 deb-version 0.17-1ppa1
lp:~freecad-maintainers/+git/gitmaster master
merge gitpackaging-trusty lp:~freecad-maintainers/+git/gitpackaging-trusty master

Testing here: https://code.launchpad.net/~gemnoc/+rec ... daily-test

EDIT: so far so good! The source package successfully built, the binary packages are now building, if they work they will be published to my own PPA: https://launchpad.net/~gemnoc/+archive/ubuntu/ppa