From admin at helixcommunity.org  Wed Nov  7 12:46:49 2007
From: admin at helixcommunity.org (Helix Bug Tracker)
Date: Wed Nov  7 12:21:34 2007
Subject: [Ribosome-issues] [Bug 7273] New: Need better error reporting when
	unpriveledged user attempts to build restricted code
Message-ID: 

https://bugs.helixcommunity.org/show_bug.cgi?id=7273

rustyl created:

          Priority: TRIAGE                                                  
  Operating System: Linux                                                   
        AssignedTo: jfinnecy                                                
         QAContact: 0                                                       
           Summary: Need better error reporting when unpriveledged user atte
                    mpts to build restricted code                           
          Severity: TRIAGE                                                  
            Status: NEW                                                     
          Hardware: PC                                                      
           Version: current                                                 
           Tracker: Bugs                                                    
           Project: ribosome                                                
  Target Milestone: milestone 1                                             

Attempting to build a project that requires access to a restricted portion of the CVS repository
will result in the build system hanging in the code checkout portion of the build, and after several
minutes a python stack trace is printed to the console while the build system continues to hang.

I see this when attempting to follow the RealPlayer build instructions where:
* I first successfully build helix-player using:
   - SYSTEM_ID = linux-2.2-libc6-gcc32-i586
   - bif branch = hxplay_gtk_current
   - target = player_all
   - profile = helix-client-all-defines-free
* attempt to build realplayer by changing the bif branch to realplay_gtk_current

Eventually, the build appears to hang with the following output on the console:

datatype/amr/codec/amr-nb exists
datatype/smil/renderer/smil2/brush/fileformat exists
datatype/rm/audio/codec/ra8lbr exists

... and then after several minutes i notice the following additional text on the console:

[#-00008603][2007-11-07 11:20:41][-1209919280][INFO ] : Available threads:
 =========== -1228141680 ==========
    stack:
      __call__ @ /home/rusty/hx-stuff/build/lib/chaingang.py # 401
      __writeMessage @ /home/rusty/hx-stuff/build/lib/log.py # 594
      __log @ /home/rusty/hx-stuff/build/lib/log.py # 538
      info @ /home/rusty/hx-stuff/build/lib/log.py # 426
      info @ /home/rusty/hx-stuff/build/lib/log.py # 261
      update @ /home/rusty/hx-stuff/build/lib/cvs.py # 323
      update @ /home/rusty/hx-stuff/build/lib/cvs.py # 400
      checkout @ /home/rusty/hx-stuff/build/lib/cvs.py # 370
      Checkout @ /home/rusty/hx-stuff/build/lib/cvs.py # 208
      Checkout @ /home/rusty/hx-stuff/build/lib/cvs.py # 581
      Checkout @ /home/rusty/hx-stuff/build/lib/cvs.py # 708
      find_distribution_cvs @ /home/rusty/hx-stuff/build/lib/distributions.py # 192
      find_distribution @ /home/rusty/hx-stuff/build/lib/distributions.py # 262
      get_distribution @ /home/rusty/hx-stuff/build/lib/distributions.py # 294
      get_distribution @ /home/rusty/hx-stuff/build/lib/buildapp.py # 850
      checkout_module @ /home/rusty/hx-stuff/build/lib/buildapp.py # 942
      run @ /home/rusty/hx-stuff/build/lib/chaingang.py # 169
      doit @ /home/rusty/hx-stuff/build/lib/chaingang.py # 254
      doit @ /home/rusty/hx-stuff/build/lib/chaingang.py # 618
      worker @ /home/rusty/hx-stuff/build/lib/chaingang.py # 263
      worker @ /home/rusty/hx-stuff/build/lib/chaingang.py # 765

Again, this was seen while attempting to build realplayer from an account that did not have any
restricted access.  I would expect the build system to exit with an error letting the user know they
do not have permission to access some part of the repository that is needed to build the target.

-- 
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.

This e-mail is sent to you automatically from the Helix Bug Tracker.  Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.

From admin at helixcommunity.org  Mon Nov 19 16:28:10 2007
From: admin at helixcommunity.org (Helix Bug Tracker)
Date: Mon Nov 19 15:47:26 2007
Subject: [Ribosome-issues] [Bug 7280] New: Add a smart build.reg regenerator
Message-ID: 

https://bugs.helixcommunity.org/show_bug.cgi?id=7280

jfinnecy created:

          Priority: P4                                                      
  Operating System: Windows XP                                              
        AssignedTo: jfinnecy                                                
         QAContact: 0                                                       
           Summary: Add a smart build.reg regenerator                       
          Severity: S4                                                      
            Status: NEW                                                     
          Hardware: PC                                                      
           Version: current                                                 
           Tracker: Feature Requests                                        
           Project: ribosome                                                
  Target Milestone: milestone 1                                             

Ribosome often choke after a BIF file was modified or some SDK path 
defines were removed from a BIF file.
I wonder if it makes sense to fix Ribosome in some ways (where it makes 
sense) so that it would detect some such situation and automatically 
regenerate a new .reg file.

The advantage of fixing it that way is that developers don't need to 
know that build.reg can be removed to have Ribosome starts over more 
cleanly while keeping existing local source tree (much faster), making 
clean check up needed less often.
Also, having Ribosome doing it means that developers can keep the same 
Ribosome settings (BIF Branch, Target, and Profile) that are lost after 
build.reg is removed.

-- 
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.

This e-mail is sent to you automatically from the Helix Bug Tracker.  Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.

From admin at helixcommunity.org  Mon Nov 19 16:52:14 2007
From: admin at helixcommunity.org (Helix Bug Tracker)
Date: Mon Nov 19 16:18:24 2007
Subject: [Ribosome-issues] [Bug 4933] Distribution modules don't check out
	properly on windows platforms.
Message-ID: 

https://bugs.helixcommunity.org/show_bug.cgi?id=4933

jfinnecy changed:

           What    |Removed                     |Added                       
----------------------------------------------------------------------------
             Status|OPEN                        |RESOLVED                    
         Resolution|                            |NOTREPRO                    

------- Additional Comments From jfinnecy 2007-19-11 16:52 GMT-0800 -------
No repro on following CVS versions:

Concurrent Versions System (CVS) 1.11.2 (client)

Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2382 (client/server)

Both versions create a tmp directory and show same behavior re: cvs_dir_check() as linux client.

-- 
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.

This e-mail is sent to you automatically from the Helix Bug Tracker.  Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.

From admin at helixcommunity.org  Mon Nov 19 16:52:29 2007
From: admin at helixcommunity.org (Helix Bug Tracker)
Date: Mon Nov 19 16:18:24 2007
Subject: [Ribosome-issues] [Bug 4933] Distribution modules don't check out
	properly on windows platforms.
Message-ID: 

https://bugs.helixcommunity.org/show_bug.cgi?id=4933

jfinnecy changed:

           What    |Removed                     |Added                       
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED                      

------- Additional Comments From jfinnecy 2007-19-11 16:52 GMT-0800 -------
closed

-- 
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.

This e-mail is sent to you automatically from the Helix Bug Tracker.  Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.