RE: [Fink-devel] Master mirror message... Usability?
And what's in the fink.conf manpage seems pretty clear, too. I din't realize that Ben had posted the relevant snippet because my system stopped taking mail for a while when my mbox got too big--and I didn't search the list archives. I definitely agree that we don't want to update the main docs for features that are still just for the cvs version. -Original Message- From: Ben Hines [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 2:01 AM To: Alexander K. Hansen; Randal Schwartz; 'David'; [EMAIL PROTECTED] Subject: Re: [Fink-devel] Master mirror message... Usability? The location is in 'man fink.conf', by the way - since mirroring is a configure setting. There is nowhere for it to fit in man fink. Additionally, i even pasted that manpage text to the mailing list. Apparently 'reasonable intelligence' according to Randal doesn't include searching list archives, either. (its an advanced skill i guess :) Easier to complain about the efforts of people working for free in their spare time. https://sourceforge.net/mailarchive/message.php?msg_id=4294542 Updating the web docs in sync with adding features fink cvs is problematic because we don't want to 'document' things on the web that aren't released yet. We could use branches for that if the doc maintainers wanted to. -Ben On Monday, June 2, 2003, at 10:44 PM, Ben Hines wrote: I requested feedback on these messages - repeatedly. I said I didn't think they were perfect - repeatedly. There was basically no response. Max gave a couple notes. Thus, no complaints or 'I consider myself of reasonable intelligence' snarkiness allowed. The manpages were definitely updated with info on the new mastering setup, but possibly not the web pages. -Ben On Monday, June 2, 2003, at 02:21 PM, Alexander K. Hansen wrote: As one of the people likely to enter this into the docs, I'd like to say that it's not 100% obvious to me, either. I assume it means to switch over to the list of master mirrors, and pick the next one? 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 David Sent: Monday, June 02, 2003 4:47 PM To: [EMAIL PROTECTED] Subject: Re: [Fink-devel] Master mirror message... Usability? On Montag, Juni 2, 2003, at 06:26 Uhr, Randal L. Schwartz wrote: David == David [EMAIL PROTECTED] writes: David I was wondering if Retry using next mirror set master is such a David user friendly message. I consider myself of reasonable intelligence, and I haven't the slightest clue yet what it means. Nor would I even know where to go to find out the docs for it. Nor would I expect the docs to be there given the previous experience with other undocumented parts of fink. :( Personally I do think that Fink is very well documented for an Open Source project where no one really likes to write documentation. Since this should be a feature of only unstable I do not expect it to be documented either. All a greater scheme? evil plot? Well no, just part of our effort to create a set of distfile mirrors. I am sure it will be added to the docu asap. - we may race and we may run, but we can not undo what has been done. --- 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
[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
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
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
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 grin -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
