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? -- Dan -- launchpad-users mailing list launchpad-users@xxxxxxxxxxxxxxxxxxxModify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
-- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)