reprepro

reprepro 4.1.0

  1. Series 4.0
  2. 4.1.0

Milestone information

Project:
reprepro
Series:
4.0
Version:
4.1.0
Released:
 
Registrant:
Mahyuddin Susanto
Release registered:
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon reprepro_4.1.0.orig.tar.gz (md5, sig) 4.1.0 13
last downloaded 55 weeks ago
Total downloads: 13

Release notes 

Updates between 4.0.2 and 4.1.0:
- rredtool can be used as index hook to maintain a .diff/Index file.
- properly handle relative LogDir in conf/incoming
- add ByHandHooks to conf/distributions (only used by processincoming yet)
- fix extraction of exactly one of section or priority from a tar file.
- new byhand statement for uploaders files and ByHandHook for configuration

Changelog 

View the full changelog

2010-20-10
        * fix failure if trying to extract exactly one of
        section or priority from a tar file.

2010-01-24
        * add ByHandHooks to conf/distributions for hooks
        called by processincoming (and in the future perhaps by include)

2010-01-18
        * properly handle relative LogDir in conf/incoming

2009-12-08
        * add byhand statement to uploaders files

2009-11-22
        * fix build with --without-libgpgme
        (thanks to Reto Gantenbein for reporting)

2009-11-16
        * include <stdint.h> where *int*_t is used

2009-11-13
        * 'include' now errors out early if the .changes includes source files but
        no .dsc file.

2009-11-12
        * add mode to rredtool to act as reprepro index hook and generate
        and update a *.diff/Index file.

2009-11-06
        * when 'include'ing a .changes file, do

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.