Skip to content

Releases: MidnightBSD/mport

2.4.9

10 Dec 05:32
Compare
Choose a tag to compare

Fix a bug that causes mport upgrade to always fail and hang indefinetely.

2.4.8

05 Dec 22:45
Compare
Choose a tag to compare

Fixed a crash bug

2.4.7

19 Sep 15:04
Compare
Choose a tag to compare

Fix a small leak.

Fix a crash when the dependency list is empty on package creation.

2.4.6

19 Sep 13:40
f2992e0
Compare
Choose a tag to compare

Fixes a segmentation fault in mport_createextras_free caused by a bug in mport_parselist.

This bug would result in some ports causing crashes when creating a package.

2.4.5

05 Sep 18:25
1697fcf
Compare
Choose a tag to compare
  • New experimental feature to automatically select the closest package mirror by ping: mport mirror select
  • Now displays disk usage of the installed package and all packages. It must be calculated at package creation time so it doesn't work on old packages.

This release has a new bundle version (6) and master database schema change. It will update your sqlite3 master database upon running for the first time. Once you update to this release, you shouldn't run an older mport version on the database.

2.4.4

28 Aug 04:40
Compare
Choose a tag to compare
  • Adds mport config list to display all configured values
  • Fixes a bug with non-interactive console messages when downloading a file. (Uses percent and cuts down on output)

2.4.3

26 Aug 18:51
Compare
Choose a tag to compare
  • mport clean now removes temporary files that might get left behind by other operations
  • mport clean now removes left over /var/db/mport/infrastructure/* folders that might get left behind prior to a fix for mtree files last year. (mostly for older systems)
  • mport's internal rmtree functionality has been modified to use native C routines rather than executing rm -r as a system command. (Please report any issues with removing files in packages on delete with this) This is slightly faster with very large packages. (0.03 seconds or so)
  • mport list updates will now give you better information about why a package is not found in the index. If the package is listed in the MOVED file in mports repository, it will tell you if it's removed/expired or moved to another location.

Now that MOVED file contents are part of the index, we can start doing smarter updates in the future. The first package build to include this data is the latest amd64 3.1 build that is likely going to be used for the upcoming midnightbsd 3.1 release.

2.4.1

04 May 17:00
d2117e9
Compare
Choose a tag to compare

Improvements to the mport audit command:

mport -q audit
prints out a list of packages with package name - package version
e.g.
apr-1.7.0.1.6.1_2
argyllcms-1.9.2_1

mport audit -r
prints out packages that depend on the given vulnerable package in addition to the normal output.

2.4.0

29 Apr 16:16
Compare
Choose a tag to compare

Introduces the mport audit command.

Usage:
mport audit

Will print out vulnerable packages installed on the system based on matching their CPE data against a NVD feed. Will not work on packages missing CPE data.

I also added a new flag at the top level of mport -q or --quiet. Will hide some output from mport commands such as download progress on files.

NOTE:
this has a breaking change with the mport_instance_init as there is a new quiet parameter. In most cases, you'll want it false.

2.3.0

08 Apr 21:04
Compare
Choose a tag to compare

Fixes a segmentation fault with mport search functionality.