reprepro

reprepro 4.2.0

  1. Series 4.0
  2. 4.2.0

Milestone information

Project:
reprepro
Series:
4.0
Version:
4.2.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.2.0.orig.tar.gz (md5, sig) 4.2.0 21
last downloaded 55 weeks ago
Total downloads: 21

Release notes 

Updates between 4.1.1 and 4.2.0:
- allow patterns in override files
- apply override files when doing 'pull' and 'update'
- add special '$Component' override field
- create InRelease file additionally to Release.gpg

Changelog 

View the full changelog

2010-07-10
        * create InRelease files when signing...

2010-07-05
        * special $Component in override files will force
        placing packages in the specified component
        upon inclusion (unless -C is given).

2010-07-04
        * consult override files when importing packages
        with 'update' or 'pull'.

2010-07-01
        * fix inconsistency in changelog.example.
        Thanks to Christoph Mathys.

2010-06-30
        * allow patterns in override files

2010-06-29
        * do not stop with error if a downloaded Packages
        file contains unexpected wrong Architecture lines
        but only print a warning. Add --ignore=wrongarchitecture
        to not print that warning.

2010-06-26
        * store override data in a tree instead of an list and
        some preparations for patterns in override files.

2010-06-25
        * Ignore overrides for fields starting with '$' and
        warn about unknown fields to allow later introduction
        of special values.
        * disallow overrides of core fields (Package, Version,
        Filename, ...)

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.