Re: Copy packages to same PPA, different distro

[Pau Garcia i Quiles <pgquiles@xxxxxxxxxxx>]

Quoting Celso Providelo <celso.providelo@xxxxxxxxx>:

> On Mon, May 26, 2008 at 6:53 PM, Pau Garcia i Quiles
> <pgquiles@xxxxxxxxxxx> wrote:
> > Quoting Dan <danmbox@xxxxxxxxx>:
> >
> > It does not work for me, either. I even blogged about that:
> > http://www.elpauer.org/index.php?p=253
> >
> >
> > > Hi all, I am having trouble creating binaries for both Gutsy AND Hardy
> > > in the same PPA. Here's what happened:
> > >
> > > 0) My package was initially made for Debian, so the most recent
> > > changelog entry points to "unstable". Therefore,
> > >
> > > 1) I uploaded the source package to ~myname/ubuntu/hardy
> > >
> > > 2) The package built fine, and Hardy .deb's showed up in the PPA
> > >
> > > 3) I requested "Copy Packages" to the same PPA / target distro Gutsy,
> > > without checking the "copy binary packages" checkbox
> > >
> > > 4) The package again built fine (the build logs contained no errors
> > > and the PPA front page says my packages are published for Gutsy)
> > >
> > > But I cannot find the Gutsy binaries. For example,
> > >
> > > http://ppa.launchpad.net/myname/ubuntu/dists/gutsy/main/binary-i386/Packages
> > >
> > > is empty (0 bytes in size)
> > >
> > > Upon further inspection, I don't even see how this could work *in
> > > principle*, since the Hardy .deb's in pool/main/m/mypackage have no
> > > indication that they are Hardy-specific. That is, even if Gutsy .deb's
> > > were built, they would have no place to go (short of over-riding the
> > > Hardy .deb's in pool/main/...)
> > >
> > > What am I doing wrong? What is the right way to create both Hardy and
> > > Gutsy .deb's?
>
> You should either:
>
> 1. Build the source once in Gutsy and copy source & binaries to Hardy
> (the opposite should also work, but it depends on the which features
> you used in your package).

Copy binaries?

What I used to do is build on Gutsy, then copy source to Hardy. Soyuz  
then built the Hardy version of those packages but they were never  
made available to users.

> 2. Upload new versions of the source to build to build in Hardy.

Yes, that works but then you are not using the "copy packages"  
feature. BTW, being able to automate package copy would also be nice.

> For instance, 1/3 (5796/16673) of Hardy sources was carried out from
> previous series, so it might be worth to check if you really need a
> rebuild before uploading new sources.
>
> The 'copy UI' in edge.l.n (and soon in production, l.n) will refuse to
> perform source-only copies within the same PPA, because the rebuilt
> binaries would never reach the archive since their contents would be
> different of the same files already published in the archive.
>
> []
> --
> Celso Providelo <celso.providelo@xxxxxxxxxxxxx>
> IRC: cprov, Jabber: cprov@xxxxxxxxxx, Skype: cprovidelo
> 1024D/681B6469 C858 2652 1A6E F6A6 037B B3F7 9FF2 583E 681B 6469



--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)