Custom Query (894 matches)


Show under each result:

Results (22 - 24 of 894)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Owner Reporter Resolution Summary
#821 dclark dclark fixed debian packaging: apt is confused if python2.5 isn't already installed (I think)
The following packages are BROKEN:
The following NEW packages will be installed:
  bcfg2 debsums{a} file{a} libdb4.5{a} libmagic1{a} libxml2{a} libxslt1.1{a} lsb-release{a} mime-support{a} openssl{a} python{a} python-apt{a} python-central{a} python-lxml{a} python-m2crypto{a}
  python-minimal{a} python-pkg-resources{a} python-support{a} python2.4{a} python2.4-minimal{a} sgml-base{a} ucf{a} xml-core{a}
0 packages upgraded, 24 newly installed, 0 to remove and 0 not upgraded.
Need to get 8704kB of archives. After unpacking 32.3MB will be used.
The following packages have unmet dependencies:
  python-ssl: Depends: python (>= 2.5) but 2.4.4-6 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:

Keep the following packages at their current version:
python-ssl [Not Installed]

Leave the following dependencies unresolved:
bcfg2 recommends python-ssl | python2.6 | python3.0 | python3.1 | python3.2
Score is -141
#826 dclark dclark fixed 1.0.1rc3 Debian Packaging TODO
gregcoit | so I built and installed the 1.0.1rc3 debs.  Now I get Server failure:       
         | Protocol Error: 401 Unauthorized                                             
    solj | gregcoit: are you using ssl certs for authentication?                        
gregcoit | this server is both a bcfg2 client and server, and used random password      
gregcoit | solj: so, i think the answer is no                                           
    solj | can you paste a sanitized copy of your bcfg2.conf?                           
gregcoit | solj: sure                                                                   
gregcoit | solj:                                          
    solj | ok, so that's using the ssl certs                                            
    solj | try commenting out the cert/key/ca parts of the [communication] section      
    solj | see if that works                                                            
gregcoit | kk                                                                           
gregcoit | yep, that worked                                                             
    solj | k, i have a feeling that the debian installer is setup to regenerate keys or 
         | something                                                                    
    solj | maybe djbclark knows about that                                              
gregcoit | solj: ok, now a huge issue atm                                               
gregcoit | solj: and thanks!                                                            
    solj | np                                                                           
djbclark | solj: I'm pretty sure that's not there; if it is, I didn't add it. It's      
         | possible we need to tell ucf about files it doesn't currently know about. I  
         | should have time tomoorrow to update the ubuntu and debian testing repos with
         | rc3, and also test for config file overwriting problems.                     
    solj | djbclark: sounds good                                                        
Sol Jerome wrote:
> A release candidate for bcfg2 1.0.1rc3 is now available for final
> testing:
> This release is geared toward bugfixes and packaging fixes. The
> following highlights some of these changes:
>  * Improve debian/ubuntu packaging
> Many thanks to all who contributed/tested 1.0.0. Daniel Clark cleaned up
> the debian packaging. In addition, he setup both stable and testing PPAs
> for Ubuntu while also adding a debian archive at
> Thorsten Lockert tested out the reporting system and contributed various
> patches. Lisa Giacchetti tirelessly stress tested the server to find the
> file descriptor leaks. And, of course, Narayan Desai fixed those. Others
> have helped in testing as well.
#1 desai desai fixed switch to lxml

Switch to lxml for a few reasons:

  • Speed
  • Schema Validation
  • XPath support
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.