Re: [Fink-devel] vnc-3.3.7-1 migrating to stable
On Dienstag, Juni 3, 2003, at 04:50 Uhr, Steven Tamm wrote: Hi *, I'm the package maintainer for vnc-3.3.7, and a couple people were asking me how to get it migrated from unstable to stable. The list archives appear to be down so I couldn't find out for myself. The documentation talks nebulously about how the packages need to be "tested" first. It is basically your call. If you have CVS write access you simnply move it to stable. If you have no access you ask on the list and one of us will do it. However you should have substantial feedback from your users that everything worked fine for a while, because they will be complaining to you if things blow up on them -d - we may race and we may run, but we can not undo what has been done. PGP.sig Description: This is a digitally signed message part
Re: package validation [was Re: [Fink-devel] vnc-3.3.7-1 migrating to stable]
Charles Lepple said: > Also, anyone looked into porting Debian's fakeroot system for builds? > (apologies if this has been discussed; I can't get to the archives to > check). Sorry, it was a proxy problem on my end, and I just got through to the archive. I found the fakeroot threads. -- Charles Lepple <[EMAIL PROTECTED]> http://www.ghz.cc/charles/ --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
package validation [was Re: [Fink-devel] vnc-3.3.7-1 migrating to stable]
Christian Schaffner said: > - Check for them touching anything outside of %d or %b during build and > install. Not legal except in very special cases. I got tripped up by this with one of my submissions. Basically, I never would have caught it myself, since the man page ended up in the right place on my hard drive (but bypassed the 'prefix=%d' part, and so wasn't in the build root). Do other developers have scripts to search for unpackaged files in /sw? Or are there better ways to catch mistakes such as this? Also, anyone looked into porting Debian's fakeroot system for builds? (apologies if this has been discussed; I can't get to the archives to check). -- Charles Lepple <[EMAIL PROTECTED]> http://www.ghz.cc/charles/ --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] vnc-3.3.7-1 migrating to stable
Hi Steven I had a quick look at your package. The only problem I found was that you have a '/sw' in your patch file. You should replace that with PREFIX and have it tested again. What normally needs to be done for testing a package (written by Ben Hines <[EMAIL PROTECTED]>): - fink validate on the .deb file and the .info file - dpkg -c on the deb file just to make sure... make sure to do this for each splitoff. - Check for hardcoded /sws in the info and patch (should be %p) - Check for them touching anything outside of %d or %b during build and install. Not legal except in very special cases. - Make sure license and Homepage is in the package and is right - Make sure Maintainer is in the package and is the person who submitted the package. If not make sure they have the maintainer's permission. - Check dependencies, run something like this: 'dpkg -L wml | xargs otool -L' will list all libraries linked to by everything in that package. make sure it depends on each (didnt someone make a perl script to do that?.. i think so), and make sure none are BuildDependsOnly. - Try to check builddepends as much as possible (can be hard to get them all sometimes) - Make sure description is readable and appropriate - Sometimes I will let them know if they are doing crazy build hacks they don't need to be doing - Let them know if they are missing fink fields, like if they have a .conf file but forgot ConfFiles: field, or are not using fields like ConfigureParams: - Make sure they have splitoffs if they include shared libraries, and comply with the full -shlibs policy if necessary. - Make sure library versions in the Shlibs: field are correct. - python modules: must comply with fink python policy - perl modules: must comply with fink perl module policy You can do all that yourself. Once you think your package is ready for stable, announce it here again. Hope that helps, Chris. On Dienstag, Juni 3, 2003, at 04:50 Uhr, Steven Tamm wrote: Hi *, I'm the package maintainer for vnc-3.3.7, and a couple people were asking me how to get it migrated from unstable to stable. The list archives appear to be down so I couldn't find out for myself. The documentation talks nebulously about how the packages need to be "tested" first. How can I get a package moved into stable? Thanks, -Steven --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
RE: [Fink-devel] vnc-3.3.7-1 migrating to stable
My understanding is that if you've gotten sufficient positive feedback (by your standards) on the package, then you can request to have it migrated, which effectively means that somebody with commits access will put the .info/.patch files into stable. So you've basically done what's required. Alexander K. Hansen Associate Research Scientist, Columbia University visiting MIT Plasma Science and Fusion Center Levitated Dipole Experiment 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Tamm Sent: Tuesday, June 03, 2003 10:50 AM To: [EMAIL PROTECTED] Subject: [Fink-devel] vnc-3.3.7-1 migrating to stable Hi *, I'm the package maintainer for vnc-3.3.7, and a couple people were asking me how to get it migrated from unstable to stable. The list archives appear to be down so I couldn't find out for myself. The documentation talks nebulously about how the packages need to be "tested" first. How can I get a package moved into stable? Thanks, -Steven --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
