#aptly

/

      • Son_Goku joined the channel
      • Son_Goku has quit
      • PatrolDoom has quit
      • [d__d] has quit
      • -- BotBot disconnected, possible missing messages --
      • [d__d] joined the channel
      • bvi joined the channel
      • wandering_vagran joined the channel
      • kimpa joined the channel
      • daniel2 joined the channel
      • Son_Goku joined the channel
      • Son_Goku has quit
      • Son_Goku joined the channel
      • Son_Goku has quit
      • Son_Goku joined the channel
      • wandering_vagran joined the channel
      • Eleventh_Doctor is now known as Pharaoh_Atem
      • Son_Goku has quit
      • Son_Goku joined the channel
      • Son_Goku has quit
      • kimpa has quit
      • antonw joined the channel
      • wandering_vagran has quit
      • reedjc joined the channel
      • reedjc
        I am learning aptly. I have been using reprepro for 10 months. With reprepro when I include a new package (via .changes) the old packages are removed, effectively replaced.
      • I know "aptly won't complain if package is added to the repo which is complete duplicate." So with my continous integration setup I may have many packqges rebuilt day after day. Currently I hjave multiple packages shown by aot-get policy for same software (versioning is based on timestamp down to the second).
      • I only need the latest there. Is there way to replace automatically? or is there a management method to periodically cleanup?
      • I don't want to use -force-replace because I do want it to complain about duplicate versions.
      • kimpa joined the channel
      • I see this is a known issue https://github.com/smira/aptly/issues/291
      • kimpa has quit