QApt 1.0.1

Milestone information

Project:
QApt
Series:
1.0.x
Version:
1.0.1
Released:
 
Registrant:
Jonathan Thomas
Release registered:
Active:
No. Drivers cannot 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 libqapt-1.0.1.tar.bz2 (md5, sig) Source tarball 52
last downloaded 40 weeks ago
Total downloads: 52

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

* Fixed what is hopefully the last of "libapt-pkg gives LibQApt null const char pointers if for some reason libapt-pkg can't get the string we want" crashes. (Bug 247439)
* Fixed a typo in the API documentation
* Slightly optimized the QApt::Package::isSupported() function by using better logic to reduce the amount of queries we make about package info.
* A few coding style fixes
* Fixed a bug where the worker would never send a "finished" signal if a download ended in error. (Bug 247534)
* Report errors that occur while APT is initializing the package system. (This was an oversight... the error type was there, but was never used...) This prevents crashes on startup when errors like invalid lines in the package sources list being malformed and such. (Bug 247533)
* A small memory leak was fixed by mlaurent. Thanks! This leak should not have had an impact on virtually any application using LibQApt that I know of, since the Backend class that had this leak on deconstruction does not get constructed/deconstructed a lot in practice.
* Quieted some console debug messages.
* Enhance QApt Batch's handling of InitErrors to show the newly-available details about these errors, and quit after the user has been presented with the error and has closed the error message box.
* In step with the Aptdaemon project, allow unprivileged users to check for updates by default. This can still be configured in the PolicyKit settings for those who wish to lock it down more, but really it shouldn't be a security risk.

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.