This is the third alpha for the upcoming 2.3.x releases. This release
includes important bug fixes and enhancements beside the optimizations
for speed.
Following new features are also implemented in this release:
- Support for specifiying different update types and actions for each
sub-package,
- Warnings for packages that need the restart of some services and
system reboot,
- Ability to rename service scripts.
Changes since 2.3_alpha1
------------------------
atolboo (1):
Dutch language update of /trunk/pisi/po.nl.po
fatih (43):
Thinko fix: Old and new file hashes might be different.
Fix concatenation error
More consistent messages
Optimize get_package_requirements a little
Little optimization for Install class
Refactor reverseDependencyUpdate search
Accelerate iteration to find security updates
Use brightred for error messages
Add make_version function
Add split_version function to split version, release and build parts of a package version
index: If the build numbers are same, use the release number.
api: Do not use Version class for full package versions
version: Modify Version class to use make_version
tests: Remove release numbers from version strings as they are no longer supported
api: Remove unused variable
atomicoperations: Use make_version instead of Version class
Return immediately if a condition is not satisfied
Use make_version instead of Version class
repodb: Reduce the number of calls to piksemel.parse
repodb: Make error messages translatable
upgrade: Do not call get_replaces twice
packagedb: Accelerate get_replaces
installdb: Store package node and use it later to reach sub-nodes
util: Add utility functions to print a list of strings by columns
cli/upgrade: Print package lists in a more readable format
cli/update-repo: Use ui.action to print 'Updating repository:' message
cli/upgrade: Replace a ui.info with ui.status
specfile: Initial bits for Type tags and Action attributes
Add support to specify update types and actions for each sub-package
specfile: Replace get_update_types_and_actions function with faster ones
specfile: Rename targetPackage attribute in Action tags as target
dtd,rng: Update DTD and RelaxNG shemas for the recently added features
upgrade: Use a single loop for finding packages to be upgraded
upgrade: Check the reverse dependencies of installed packages
cli/install,upgrade: Colorize package size info
upgrade: Remove redundant variable
cli/install: Make package lists more readable and colorize messages
cli/remove,upgrade: Revise safety switch messages
cli/upgrade: Show packages that need serviceRestart and systemRestart before upgrade
build: Copy additional source files when a build step is given too
upgrade: Take all deps into account for the correct upgrade order
db: Remove repodb members to avoid caching of RepoDB instance
po: Update for new messages
ozan.caglayan (8):
Use delta suffix value from constants.py
Use constants from constants.py
Add forgotten log
Those given parameters are nonsense and noop. Just give DESTDIR to install() for correct installation into sandbox.
Don't use underscores for filenames in infodir
Add ability to rename System.Service scripts
Don't install blacklisted system.base packages on update and new package install
Implement configure()
patrik (1):
Swedish translation
sdalgic (3):
add a prototype python script for GPG Key management in Pisi. Being adopted from apt-key script in apt. A step in Package Signing ;)
add some file_existence checks, implement add, del, update func. , some improvements in the code.. Still Prototypesvn diff
implement list_keys, list_fingerprints, export and exportall parts.
If a package is added to the upgrade list because of a
reverseDependencyUpdate action (e.g. google-gadgets because of
libproxy), runtime dependencies of that package are not examined (e.g.
webkit-gtk not installed although it is a dep of google-earth). This
commit also fixes this issue.
<Provides>
<COMAR script="iscsi-service.py" name="iscsi">System.Service</COMAR>
<COMAR script="iscsid-service.py" name="iscsid">System.Service</COMAR>
</Provides>
Will register two separate system services called respectively "iscsi" and "iscsid". This way
we don't have to split packages to give them separate names or to provide more than 1 services
in a sub-package.
Following is an example to specify "security" type and
"reverseDependencyUpdate" action for different sub-packages.
<Update release="30">
<Date>2010-02-17</Date>
<Version>2.4.18</Version>
<Comment> ... </Comment>
<Type package="libdrm-intel">security</Type>
<Requires>
<Action package="libdrm-nouveau">reverseDependencyUpdate</Action>
</Requires>
<Name>Fatih Aşıcı</Name>
<Email>fatih@pardus.org.tr</Email>
</Update>
It is also possible to specify different targets for the actions. In the
following example, new release of mod_php package requires a restart of apache
service.
<Update release="30">
<Date>2010-02-17</Date>
<Version>5.2.13</Version>
<Comment> ... </Comment>
<Requires>
<Action package="mod_php" targetPackage="apache">serviceRestart</Action>
</Requires>
<Name>Fatih Aşıcı</Name>
<Email>fatih@pardus.org.tr</Email>
</Update>
Serdar Dalgıç
Ozan Çağlayan
Transifex SVN Submitter
Fatih Aşıcı
Klemens Häckel
Patrik Karlsson
Anton Tolboom