Re: Csound
Free Ekanayaka wrote: > What about a script that converts the original upstream tarball in a > dfsg-clean one? The script could be kept under SVN and be run against > new upstream releases to obtain the dfsg-clean equivalent (that's more > or less what the kernel team does with the original linux tarball, > which is not dfsg-clean). Ok. > FS> A draft source package is an empty one? > > No, just an initial version of the package, typically obtained by > running dh_make and deleting the useless stuff. And how do you inject only the debian/ directory? -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Csound
|--==> Felipe Sateler writes: FS> On Wednesday 01 August 2007 18:47:22 Free Ekanayaka wrote: FS> Import the upstream source to the "upstream" branch. >> >>We generally avoid importing the upstream source to save space. >> FS> Remove non-free stuff from the source in the "dfsg-clean" branch. >> >>That's interesting, I've never maintained a package for which I had to >>prune the upstream source from non-free parts. Is this the case with >>sound? FS> Yes, because csound used to be under a non-free license, but changed to LGPL FS> later on. However some of the opcodes could not be relicensed because the FS> original author could not be reached/didn't want to relicense. I'm not sure FS> how repacked sources can be managed without importing them into svn. What about a script that converts the original upstream tarball in a dfsg-clean one? The script could be kept under SVN and be run against new upstream releases to obtain the dfsg-clean equivalent (that's more or less what the kernel team does with the original linux tarball, which is not dfsg-clean). >> FS> Do the actual packaging in the "master" branch. >> FS> I'm not sure if this is possible in subversion, or if you are using a FS> different schema. Apparently you are only saving the debian/ >>subfolder in FS> svn. >> >>I generally create draft source package and then: FS> A draft source package is an empty one? No, just an initial version of the package, typically obtained by running dh_make and deleting the useless stuff. >> >>svn-inject -o package.dsc svn+ssh://[EMAIL PROTECTED]/svn/demudi >> >>If I need to change the upstream code, I'm always keeping the patches >>under debian/patches. FS> I'm doing that too (I use dpatch), but that doesn't work for repacked sources. Ciao, Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Csound
Hi Felipe, |--==> Felipe Sateler writes: FS> On Wednesday 01 August 2007 18:04:00 Free Ekanayaka wrote: >> >>Yes we are using svn (because of svn-buildpackage FS> FWIW, there is git-buildpackage too. Yes, but at the time we started the project it was not available. >>and because it's the >>default RCS for Alioth projects). Are you already registered on >>Alioth? If so, please let me have you're login name so that I can >>include you in the demudi Alioth project and you can start commit. FS> My username is fsateler-guest. FS> I'm not sure how should I proceed for the conversion to svn. I'm using the FS> following method for work on git: FS> Import the upstream source to the "upstream" branch. We generally avoid importing the upstream source to save space. FS> Remove non-free stuff from the source in the "dfsg-clean" branch. That's interesting, I've never maintained a package for which I had to prune the upstream source from non-free parts. Is this the case with sound? FS> Do the actual packaging in the "master" branch. FS> I'm not sure if this is possible in subversion, or if you are using a FS> different schema. Apparently you are only saving the debian/ subfolder in FS> svn. I generally create draft source package and then: svn-inject -o package.dsc svn+ssh://[EMAIL PROTECTED]/svn/demudi If I need to change the upstream code, I'm always keeping the patches under debian/patches. Ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Csound
On Wednesday 01 August 2007 18:47:22 Free Ekanayaka wrote: > FS> Import the upstream source to the "upstream" branch. > > We generally avoid importing the upstream source to save space. > > FS> Remove non-free stuff from the source in the "dfsg-clean" branch. > > That's interesting, I've never maintained a package for which I had to > prune the upstream source from non-free parts. Is this the case with > sound? Yes, because csound used to be under a non-free license, but changed to LGPL later on. However some of the opcodes could not be relicensed because the original author could not be reached/didn't want to relicense. I'm not sure how repacked sources can be managed without importing them into svn. > > FS> Do the actual packaging in the "master" branch. > > FS> I'm not sure if this is possible in subversion, or if you are using a > FS> different schema. Apparently you are only saving the debian/ > subfolder in FS> svn. > > I generally create draft source package and then: A draft source package is an empty one? > > svn-inject -o package.dsc svn+ssh://[EMAIL PROTECTED]/svn/demudi > > If I need to change the upstream code, I'm always keeping the patches > under debian/patches. I'm doing that too (I use dpatch), but that doesn't work for repacked sources. -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: Csound
On Wednesday 01 August 2007 18:04:00 Free Ekanayaka wrote: > > Yes we are using svn (because of svn-buildpackage FWIW, there is git-buildpackage too. > and because it's the > default RCS for Alioth projects). Are you already registered on > Alioth? If so, please let me have you're login name so that I can > include you in the demudi Alioth project and you can start commit. My username is fsateler-guest. I'm not sure how should I proceed for the conversion to svn. I'm using the following method for work on git: Import the upstream source to the "upstream" branch. Remove non-free stuff from the source in the "dfsg-clean" branch. Do the actual packaging in the "master" branch. I'm not sure if this is possible in subversion, or if you are using a different schema. Apparently you are only saving the debian/ subfolder in svn. -- Felipe Sateler signature.asc Description: This is a digitally signed message part.
Re: Csound
Hi Felipe, |--==> Felipe Sateler writes: FS> Hi. I'm taking over the csound package from Hans Fugal, and updating it to FS> version 5. However the package has resulted in being bigger than I thought, FS> so I think it would be better if you guys could help me out co-maintaining FS> it. The problem with it is that it csound has grown very big: language FS> bindings, plugins, and more. Plus, the build system is scons which I'm not FS> really familiar with. FS> In short, I'd like to join the team and co-maintain csound with you. I have FS> already started work in csound, but I don't have a public space to make it FS> available. I'm using git, but if you want I can switch to svn (which is FS> what you are apparently using). Yes we are using svn (because of svn-buildpackage and because it's the default RCS for Alioth projects). Are you already registered on Alioth? If so, please let me have you're login name so that I can include you in the demudi Alioth project and you can start commit. Ciao! Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ardour_2.0.4-1_amd64.changes ACCEPTED
Accepted: ardour_2.0.4-1.diff.gz to pool/main/a/ardour/ardour_2.0.4-1.diff.gz ardour_2.0.4-1.dsc to pool/main/a/ardour/ardour_2.0.4-1.dsc ardour_2.0.4-1_amd64.deb to pool/main/a/ardour/ardour_2.0.4-1_amd64.deb ardour_2.0.4.orig.tar.gz to pool/main/a/ardour/ardour_2.0.4.orig.tar.gz Override entries for your package: ardour_2.0.4-1.dsc - source sound ardour_2.0.4-1_amd64.deb - optional sound Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of ardour_2.0.4-1_amd64.changes
ardour_2.0.4-1_amd64.changes uploaded successfully to localhost along with the files: ardour_2.0.4-1.dsc ardour_2.0.4.orig.tar.gz ardour_2.0.4-1.diff.gz ardour_2.0.4-1_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
