This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I checkout and build NB sources and then do cvs diff I get many .class files shown with '?'. I remember that there used to be a global policy to filter out .class files so I've tried to 'cvs co CVSROOT' but the folder I've got is completely empty! so there is no cvswrappers etc.
*** Issue 56390 has been marked as a duplicate of this issue. ***
*** Issue 56441 has been marked as a duplicate of this issue. ***
If I can speak for all the developers this is *really* annoying because besides of your actual diff you see tons of question marked files so it's easier to overlook something important in your diff. Please fix it ASAP. Thanks a lot in advance.
Shouldn't we bump up priority here? Commiting a .png w/o cvswrappers is going to break it for most CVS users...
Agreed, it is even more serious danger. I'm changing priority to P1.
I am not sure this issue deserves P1. On the other hand I have found another case which cannot be completed when the issue is there. Release Engineering cannot prepare patches for CVSROOT/modules, what could become serious regression.
Collab, can you pls respond ? This was opened as a P2 4 working days ago, haven't seen a response yet. This is a regression, upgrade related. We need all upgrade related issues fixed ASAP.
A few more details and justification in issue #56390, if needed.
Opened an internal issue to get this reviewed. I was able to reproduce but am not sure that since an empty directory came down the files on the server are empty. Searching for clarification of three things: 1) are the files there in CVSROOT at all? (would think so, but have no proof) 2) are the CVSROOT files on the server populated with the expected NB detail (seems not)? 3) why do the files not come down on a cvs checkout?
Perhaps the quickest fix would be to just copy details from the pre-upgrade server.
All the details have been in the cvsroot directory since the upgrade, they were just not able to be checked out. The files in the CVSROOT repository are not in rcs format by default, hence the empty directory on checkout. I tested by uploading .book and .class file and they are set to binary as they should be, thereby proving cvswrappers is populated with your amendments. I checked the modules file as well and it is intact, i.e. no difference between the prior version and the current version, as well. I will attach both cvswrappers and the modules file for your confirmation. Should this issue be considered a request to be able to checkout files under CVSROOT? If so, which files beyond modules and cvswrappers?
Created attachment 20910 [details] cvswrappers
Created attachment 20911 [details] modules
Brian, attach also CVSROOT/cvsignore file.
There is no copy of cvsignore in the CVSROOT directory.
Brian, missing CVSROOT/cvsignore is an issue, upping priority to P2 to get the file back. This missing file is definitely not just P3 as it annoys every cvs user who tried to build NetBeans and then did 'cvs update'. We can later consider upping to P1.
While I am attempting to get this from the old system, can you point me to issues that detail what should be in it?
Created attachment 20926 [details] Sample CVSROOT/cvsignore from Sun-internal CVS server
BTW: we would probably need to get CVSROOT/modules RCS versioned again. We used to have a procedure for updating CVSROOT/modules, which included providing of diff patches for CVSROOT/modules. We had agreement to file P2/TASK issues for patching CVSROOT/modules. As we lost the possibility to prepare patches after upgrade, there needs to be either update to procedure or make CVSROOT/modules file versioned again. If we would go with change of procedure, I assume we could file P1/TASK issues with description what should be done. P1 seems to be necessary as it would require much more precise attention to this task.
I have asked the cvignore detail you provided be added and that at least the cvswrappers, modules and cvsignore files be versioned. Are there any others? Filing an issue as a P1 because it will "require much more precise attention" is not an acceptable use of the priority system. Priorities are based on contractual obligations focused on the _severity_ of the need, not the amount or precision of effort required. A p2/task seems appropriate, especially as it has been agreed to by both parties, unless a business case can be provided proving otherwise.
Note that this issue was opened 3/10 at 10 a.m. Jack then added the following: ------- Additional comments from jcatchpoole Tue Mar 15 16:54:02 +0000 2005 Collab, can you pls respond ? This was opened as a P2 4 working days ago, haven't seen a response yet. This is a regression, upgrade related. We need all upgrade related issues fixed ASAP. That's over 4 days w/o a response from Support. Our support contract states that Priority 2 (Severity 3) Errors require CollabNet to contact Sun within four (4) hours of a Business Day after receipt by CollabNet of notice of an Error. Then, within two (2) Business Days after receipt by CollabNet of notice of an Error, CollabNet will either provide Sun with (i) a Resolution, or (ii) a mutually agreed upon CollabNet Action Plan to resolve such Error(s). Those terms have clearly not been followed or met in this case. Regardless, we just need the fix. So, given the want of NetBeans regarding this issue, Sun will invoke the clause from the hosting agreement, Attachment D, Item 4 stating: "If CollabNet and Sun are unable to agree as the the priority/severity of an Error, then with respect to one (1) Error per calendar month for all Websites in the aggregate, Sun's determination shall prevail." We've not done this for March yet, so I'm raising this issue to a P1(S2). Please adjust treatment of this issue accordingly. For P1(S2) issues, "CollabNet will endeavor to Resolve the Error by the end of one (1) Business Day after receipt by CollabNet of notice of an Error." Thanks, Eric
This is where we stand now. All the component files of CVSROOT, save cvsignore, contain netbeans' customizations as they were prior to the upgrade. The only difference now is they are not under version control, hence cannot be checked out for review. I have attached the files to demonstrate they exist and are in the correct form. To get the files under revisioned will take some level of effort and changes to you instance set. We are presently working on getting that in place and I am still waiting to get a definitive response from netbeans as to which files should be available to be checked out. The list I have so far is cvswrappers, modules and cvsignore. Noone from netbeans has confirmed this is the complete list. In the meantime, when requested, we will produce the files as attachments to issues or any other reasonable location specified.
As I understand the problem you have made a complete backup of the original CVS repository and then you have restored the backup including CVSROOT but the files present in the repository under CVSROOT are not checkout-able. Sorry for my ignorance, I'm not a CVS expert, but if the above is true, then why we are negotioating any sort of list of files that should be checkout-able under CVSROOT in the new repository and why should that list be be confirmed by us? We on NetBeans side simply want the original state of the CVSROOT to be restored so that there is no regression in functionality. Again, I'm not CVS expert, but IMHO I would say that all the files that had ",v" in the original repository under CVSROOT were versioned and should be checkout-able in the new repository.
Correcting summary and awaiting Eric's answer from JGlick on the files in question.
Brian, please make following files version controlled. CVSROOT/modules CVSROOT/cvsignore CVSROOT/cvswrappers This list is enough complete for successful resolution of this issue. In case we need more files, we would file another issue.
Brian, (interim report) I don't know what happened, but question marks stopped appearing in cvs update logs sometime between 20:22 and 21:22 UTC today (Mar 17th). Nonetheless I'm still unable to checkout files from requested list.
The cvsignore file is now on the NB system with the contents Rudolf specified.
We have to customize the instance set to enabled the files to be checked out, which will take some time (I don't have an eta yet). That is why in my prior update specifies we will produce the files upon request until you can check them out. Can we reconsider the priority of this issue given our current status?
Brian, two things. #1 The attached cvsignore file was just a sample, please use a copy from genuine NetBeans.org CVS server instance #2 I assume the files are present in CVSROOT on server side. To make them available for checkout and if there are no special hidden technical barrings, issue following commands on server (under appropriately privileged account). $ cd /path/to/CVSROOT $ ci -q -f -l -t- -wroot -m"Initial checkin" modules $ ci -q -f -l -t- -wroot -m"Initial checkin" cvswrappers $ ci -q -f -l -t- -wroot -m"Initial checkin" cvsignore $ Where 'ci' is a check-in command from RCS version control tools set. Dropping priority as the question marks "?" stopped appearing and this behavior seems persistent. Also we actually don't have any urgent need to update modules or cvsignore files. P3 seems to be sufficient, but it could change later.
The original cvsignore is in place. While your commands would make the files available for checkout, it would also subvert future upgrades as it would not be carried across. That is why I mentioned in a previous comment we are trying to get the changes done in an instance set, which is a customization package applied to the system and ensures changes are preserved through upgrades.
Opened another internal issue to get the instance set updated to version the three CVSROOT component files.
Ping ... what is the status of this issue, is it fixed ?
I am checking internally regarding the status.
This is already in the instance-set for Danube-S. Can you please verify on stage that it works to your satisfaction?
It works for me on CVS server cvs.stage.netbeans.org . I was able to checkout three files. $ cvs -d :pserver:rbalada@cvs.stage.netbeans.org:/cvs co CVSROOT cvs server: Updating CVSROOT U CVSROOT/cvsignore U CVSROOT/cvswrappers U CVSROOT/modules $
Marking fixed.
We recently moved out from Collabnet's infrastructure