<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
>>>>> I hear that OpenSUSE's build server will build Debian packages, but<br>
>> I've<br>
>>>>> never used it. It would be very useful if someone set that up, I<br>
>> think can<br>
>>>>> also build Fedora and SUSE packages.<br>
>>>>><br>
>>>>><br>
>>>> I played around with OpenSUSE's OBS but it's not a success yet.<br>
>>>> It needs a something.spec file for building RPMs and a something.dsc<br>
>> file<br>
>>>> for DEBs. Both files serve to define a source package.<br>
>>>> For the spec file, I started from one well worked out for Planet CCRMA<br>
>> by<br>
>>>> Fernando Lopez-Lezcano. It's looking good for the OBS right now except<br>
>> that<br>
>>>> I'm struggling with the source definition, i.e. it doesn't seem to be<br>
>> able<br>
>>>> to grab the tar.gz from sourceforge.<br>
>>>> For the debian dsc file, I used Paul Brossier's one. The dsc is much<br>
>>>> simpler, but it cannot accept source urls, only local files. That's<br>
>> where<br>
>>>> OBS's so-called "Source Service" comes into the picture, which can<br>
>> download<br>
>>>> a tar.gz or even checkout an svn repo and tar.gz it for me. I'm<br>
>> struggling<br>
>>>> with this too, because (1) I'm unable to grab the resulting tar.gz from<br>
>> the<br>
>>>> dsc (it's created with an odd name that contains a colon) and (2) in the<br>
>>>> dsc an MD5 checksum of the tar.gz needs to be present which is unknown<br>
>> in<br>
>>>> the case of an archive newly created from SVN.<br>
>>>> I'll try to grow smarter with OBS, but in the meantime, any advice is<br>
>>>> highly appreciated. :)<br>
>>>><br>
>>> Update: both source access problems are solved for now.<br>
>>> The deb build at the moment is stuck at the point where it doesn't<br>
>>> recognize the source package as a valid one. Dunno why.<br>
>>> The rpm build got as far as where it would have needed mp3lame - seems<br>
>> that<br>
>>> it's only available with Planet CCRMA (?). GEM builds fine. I'm playing<br>
>>> around with conditionals for requires for different CPU capabilities,<br>
>>> because OBS's spec file parser is somewhat limited.<br>
>>> More news soon, hopefully.<br>
>> Deb source packages are too tricky to create manually, use the Debian<br>
>> tools. If you are working from a git repo, like for puredata, the use<br>
>> "git-buildpackage -S". For any repo with the debian/ folder there, you<br>
>> can use "debuild -S"<br>
>><br>
>> You will need to change the debian/changelog to have your name and email<br>
>> in it, so that the signing part works, if opensuse requires signed<br>
>> packages. Launchpad, Debian, and Ubuntu all do.<br>
>><br>
>> At the very least, you'll want to do:<br>
>><br>
>> sudo apt-get install dpkg-dev devscripts debhelper cdbs<br>
>><br>
>> You can also download the source packages from the Debian or Ubuntu<br>
>> official packages, but they'll be signed by the original uploaders key.<br>
>> That wouldn't work with Launchpad but might with OBS, if it has looser<br>
>> signing restrictions.<br>
>><br>
> Cool, I've actually paid less attention to the deb process on OBS knowing<br>
> that it's already worked out and up-to-date somewhere else. I'll take a<br>
> look at how I can reuse those packages.<br>
> OBS doesn't need signed packages, an I haven't tried if it accepts packages<br>
> signed by someone else.<br>
<br>
</div></div>It could be a useful way to provide Debian/squeeze packages.<br>
<div class="im"><br>
>> If you want to try my new Pd-extended proper debian support, run:<br>
>><br>
>> $ ~/auto-build/pd-extended/scripts/auto-build/pd-extended-source-tarball.sh<br>
>> $ mv /tmp/Pd-extended_0.43.1~20120926-source.tar.bz2<br>
>> ~/auto-build/pd-extended_0.43.1~20120926.orig.tar.bz2<br>
>> $ cd ~/auto-build/pd-extended<br>
>> $ debuild -S -uc -us<br>
>><br>
> Hm, I don't have this script yet in ~auto-build/ ... It seems it doesn't<br>
> work if I just download it to any place along with its whole folder, but I<br>
> cannot run it from the main run-automated-builder script either, because<br>
> rsync cannot reach the server.<br>
<br>
</div>you need to get them from SVN:<br>
<br>
cd ~/auto-build/pd-extended/scripts<br>
svn up<br>
cd ..<br>
svn up<br></blockquote><div><br>That did the trick!<br>The script itself didn't succeed at the first run but the third run completed clean.<br>And it deletes the file at the end so I needed to copy it before it finished :o)<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The rsync method is gone for now, and perhaps permanently. I'm trying<br>
to see if I can make the cleaning process work without rsync.<br>
<div><div class="h5"><br>
><br>
>> (the -uc -us) means ignore the whole signing procedure, including the<br>
>> name in the debian/changelog)<br>
><br>
>> Also, its great that you are taking on the spec file for RPMs! Once you<br>
> get 'puredata' working, then it would be very handy if you could make<br>
>> one for the externals/template. Then it'll be easy to make RPMs for<br>
>> most of the libraries in Pd-extended, just like what's in Debian.<br>
>><br>
>> I've never made RPMs before, but I've done a lot of other packaging, so<br>
>> I'll help where I can.<br>
>><br>
> Well, the deb thing is stuck at this line now:<br>
><br>
>> dpkg-source: error: unrecognized file for a v1.0 source package:<br>
>> Pd-0.42.5-extended.tar.gz<br>
>><br>
> The file is pulled from<br>
> <a href="http://sourceforge.net/projects/pure-data/files/pd-extended/0.42.5/Pd-0.42.5-extended.tar.gz" target="_blank">http://sourceforge.net/projects/pure-data/files/pd-extended/0.42.5/Pd-0.42.5-extended.tar.gz</a><br>
> (It has a packages/linux_make/debian folder but still no good.)<br>
> Is there a .tar.gz for pd-extended online which is suitable for deb<br>
> packaging and I could link to it? I don't want to reinvent the wheel...<br>
> BTW, Is there a Pd-0.42.5-extended-dev.deb (or alike) that I could study or<br>
> use for parts?<br>
><br>
> The rpm is losing it here:<br>
><br>
>> `test -f<br>
>> /home/abuild/rpmbuild/BUILD/Pd-0.42.5-extended/externals/unauthorized/mp3live~/../linux/mp3streamin~.libs<br>
>> && cat<br>
>> /home/abuild/rpmbuild/BUILD/Pd-0.42.5-extended/externals/unauthorized/mp3live~/../linux/mp3streamin~.libs`<br>
>> /usr/bin/ld: cannot find -lmp3lame<br>
>><br>
> As far as I understood lame-devel is not available in Fedora. How do I<br>
> proceed?<br>
><br>
> András<br>
><br>
<br>
</div></div>For Debian/squeeze, we rely on the libmp3lame-dev that's in<br>
squeeze-backports. Previously, it was required that people downloaded<br>
it from <a href="http://deb-multimedia.org" target="_blank">deb-multimedia.org</a>. I guess you'd need to get it from somewhere<br>
else, but I don't know enough about Fedora to say. Does PlanetCCRMA<br>
include lame? I think that would be the best place for dependencies.<br></blockquote><div><br>Planet CCRMA does have lame, but the OBS doesn't have Planet CCRMA.<br>It is possible to fetch and build the lame sources into with pd but then we would have the lame binary bundled into pd which is not something we want, do we?<br>
So my best idea right now is to disable the external(s) that use lame.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think it'll be a lot easier if you start with just 'puredata' and the<br>
libs based on the Library Template. Then once you get the hang of basic<br>
RPM packaging, you can take on the whole pd-extended, which can be<br>
painful. Also, I think that Pd-extended 0.43.1 will be a lot easier to<br>
package since I've fixed all of the problems that came up during the<br>
proper debian packaging.<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote><div><br>Well... I'm actually enjoying RPM packaging, it's a nice compact thing with everything controlled from a single spec file, and at the moment the simpler way for me is to try to get pd-extended build, and to get into the Library Template, which I'm completely unfamiliar with, at a later point. The problems which I'm having are with some individual externals, but this way when I solve one, the next one comes up, so it's easy to go through all of them. At least I hope so.<br>
I'd even say: let me finish packaging 0.42.5-extended as a monolith now (according to the original topic), and let's do 0.43 with the Library Template approach later. Is that OK?<br><br>Again, I'm focusing more on the RPM side and I'd by happy if I could feed a debian-ready source tar.gz to the OBS, and I'd provide only the dsc. The less cool way is to upload a static file (like the one generated by pd-extended-source-tarball.sh), the more cool way would be to link to one which is online somewhere. Is there one?<br>
</div></div><br><br>András<br>