Skip to content
Snippets Groups Projects
  1. Dec 14, 2010
  2. Dec 13, 2010
  3. Dec 11, 2010
    • Dan McGee's avatar
      Fix possible null pointer deref in check_arch · eedf4f4e
      Dan McGee authored
      
      If we have a corrupted database, a package can come through without an arch,
      causing the code to blow up when making strcmp() calls. It might even be
      possible with perfectly valid database entries lacking an 'arch =' line.
      This behavior was seen as at least one of the problems in FS#21668.
      
      Ensure pkgarch is not null before doing anything further.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      eedf4f4e
  4. Nov 08, 2010
  5. Oct 28, 2010
  6. Oct 18, 2010
    • Xavier Chantry's avatar
      alpm/sync: very small memleak fix · 30734c9a
      Xavier Chantry authored
      
      Signed-off-by: default avatarXavier Chantry <chantry.xavier@gmail.com>
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      30734c9a
    • Xavier Chantry's avatar
      libalpm/remove: fix funny progress bar problem with empty packages · a2d7f6f2
      Xavier Chantry authored
      
      $ pacman -Rd kde-meta
      
      Remove (15): kde-meta-kdewebdev-4.5-1 [0.00 MB]  kde-meta-kdeutils-4.5-1 [0.00 MB]
                   kde-meta-kdetoys-4.5-1 [0.00 MB]  kde-meta-kdesdk-4.5-1 [0.00 MB]
                   kde-meta-kdeplasma-addons-4.5-1 [0.00 MB]  kde-meta-kdepim-4.5-1 [0.00 MB]
                   kde-meta-kdenetwork-4.5-1 [0.00 MB]  kde-meta-kdemultimedia-4.5-1 [0.00 MB]
                   kde-meta-kdegraphics-4.5-1 [0.00 MB]  kde-meta-kdegames-4.5-1 [0.00 MB]
                   kde-meta-kdeedu-4.5-1 [0.00 MB]  kde-meta-kdebase-4.5-1 [0.00 MB]
                   kde-meta-kdeartwork-4.5-1 [0.00 MB]  kde-meta-kdeadmin-4.5-1 [0.00 MB]
                   kde-meta-kdeaccessibility-4.5-1 [0.00 MB]
      
      Total Removed Size:   0.06 MB
      
      Do you want to remove these packages? [Y/n]
      ( 1/15) removing kde-meta-kdewebdev      [------------------------] 100%
      $ it stopped here..
      
      On one side, libalpm did not initialize the progress bar at 0 percent.
      So with meta-packages that have 0 files, there was only one progress bar
      call with percent == 100.
      
      On the other side, pacman callback kept track of the last percent that
      it received. When there are only meta-packages, we always received only
      100, so pacman believed the progress bar needed not update. Thus only
      the first package was actually displayed.
      
      A proper fix for the callback would be to keep track of last package
      name to make sure the recorded prev percent applies.
      
      But since we now specify that both Add and Remove should at least send
      percent=0 at beginning and percent=100 at the end, there is no need
      for that.
      
      Signed-off-by: default avatarXavier Chantry <chantry.xavier@gmail.com>
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      a2d7f6f2
  7. Oct 11, 2010
    • Dan McGee's avatar
      Read 'force' entry from packages · 3a06a9fa
      Dan McGee authored
      
      We weren't reading this in from our packages, thus causing us not to write
      it out to our local database. Adding this now will help ease the upgrade
      path for epoch later and not require reinstallation of all force packages.
      
      Signed-off-by: default avatarDan McGee <dan@archlinux.org>
      3a06a9fa
  8. Oct 05, 2010
  9. Sep 15, 2010
  10. Sep 04, 2010
  11. Sep 02, 2010
  12. Aug 27, 2010
  13. Aug 25, 2010
  14. Aug 24, 2010
  15. Aug 18, 2010
  16. Jul 27, 2010
Loading