Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
server:database:postgresql
barman
barman.changes
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File barman.changes of Package barman
------------------------------------------------------------------- Fri Jul 10 23:54:56 UTC 2020 - Marcus Rueckert <mrueckert@suse.de> - use systemd_ordering ------------------------------------------------------------------- Fri Jul 10 23:46:13 UTC 2020 - Marcus Rueckert <mrueckert@suse.de> - update to 2.11 - Introduction of the barman-cli-cloud package that contains all cloud related utilities. - Add barman-cloud-wal-restore to restore a WAL file previously archived with barman-cloud-wal-archive from an object store - Add barman-cloud-restore to restore a backup previously taken with barman-cloud-backup from an object store - Add barman-cloud-backup-list to list backups taken with barman-cloud-backup in an object store - Add support for arbitrary archive size for barman-cloud-backup - Add support for --endpoint-url option to cloud utilities - Remove strict superuser requirement for PG 10+ (by Kaarel Moppel) - Add --log-level runtime option for barman to override default log level for a specific command - Support for PostgreSQL 13 - Bug fixes: - Suppress messages and warning with SSH connections in barman-cli (GH-257) - Fix a race condition when retrieving uploaded parts in barman-cloud-backup (GH-259) - Close the PostgreSQL connection after a backup (GH-258) - Check for uninitialized replication slots in receive-wal --reset (GH-260) - Ensure that begin_wal is valorised before acting on it (GH-262) - Fix bug in XLOG/WAL arithmetic with custom segment size (GH-287) - Fix rsync compatibility error with recent rsync - Fix PostgreSQLClient version parsing - Fix PostgreSQL exception handling with non ASCII messages - Ensure each postgres connection has an empty search_path - Avoid connecting to PostgreSQL while reading a backup.info file - drop no-connection-from-backupinfo.patch ------------------------------------------------------------------- Sun Dec 15 07:26:09 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - fix bash-completion path ------------------------------------------------------------------- Sun Dec 15 07:14:15 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - update to 2.10 - Pull .partial WAL files with get-wal and barman-wal-restore, allowing restore_command in a recovery scenario to fetch a partial WAL file's content from the Barman server. This feature simplifies and enhances RPO=0 recovery operations. - Store the PostgreSQL system identifier in the server directory and inside the backup information file. Improve check command to verify the consistency of the system identifier with active connections (standard and replication) and data on disk. - A new script called barman-cloud-wal-archive has been added to the barman-cli package to directly ship WAL files from PostgreSQL (using archive_command) to cloud object storage services that are compatible with AWS S3. It supports encryption and compression. - A new script called barman-cloud-backup has been added to the barman-cli package to directly ship base backups from a local PostgreSQL server to cloud object storage services that are compatible with AWS S3. It supports encryption, parallel upload, compression. - Automated creation of replication slots through the server/global option create_slot. When set to auto, Barman creates the replication slot, in case streaming_archiver is enabled and slot_name is defined. The default value is manual for back-compatibility. - Add '-w/--wait' option to backup command, making Barman wait for all required WAL files to be archived before considering the backup completed. Add also the --wait-timeout option (default 0, no timeout). - Redact passwords from Barman output, in particular from barman diagnose (InfoSec) - Improve robustness of receive-wal --reset command, by verifying that the last partial file is aligned with the current location or, if present, with replication slot's. - Documentation improvements - Bug fixes: - Wrong string matching operation when excluding tablespaces inside PGDATA (GH-245) - Minor fixes in WAL delete hook scripts (GH-240) - Fix PostgreSQL connection aliveness check (GH-239) - added no-connection-from-backupinfo.patch ------------------------------------------------------------------- Fri Aug 2 16:39:10 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - update to 2.9 - Transparently support PostgreSQL 12, by supporting the new way of managing recovery and standby settings through GUC options and signal files (recovery.signal and standby.signal) - Add --bwlimit command line option to set bandwidth limitation for backup and recover commands - Ignore WAL archive failure for check command in case the latest backup is WAITING_FOR_WALS - Add --target-lsn option to set recovery target Log Sequence Number for recover command with PostgreSQL 10 or higher - Add --spool-dir option to barman-wal-restore so that users can change the spool directory location from the default, avoiding conflicts in case of multiple PostgreSQL instances on the same server (thanks to Drazen Kacar). - Rename barman_xlog directory to barman_wal - JSON output writer to export command output as JSON objects and facilitate integration with external tools and systems (thanks to Marcin Onufry Hlybin). Experimental in this release. Bug fixes: - replication-status doesn’t show streamers with no slot (GH-222) - When checking that a connection is alive (“SELECT 1” query), preserve the status of the PostgreSQL connection (GH-149). This fixes those cases of connections that were terminated due to idle-in-transaction timeout, causing concurrent backups to fail. ------------------------------------------------------------------- Thu Jun 6 18:50:17 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - update to 2.8 - Add support for reuse_backup in geo-redundancy for incremental backup copy in passive nodes - Improve performance of rsync based copy by using strptime instead of the more generic dateutil.parser (#210) - Add ‘–test’ option to barman-wal-archive and barman-wal-restore to verify the connection with the Barman server - Complain if backup_options is not explicitly set, as the future default value will change from exclusive_backup to concurrent_backup when PostgreSQL 9.5 will be declared EOL by the PGDG - Display additional settings in the show-server and diagnose commands: archive_timeout, data_checksums, hot_standby, max_wal_senders, max_replication_slots and wal_compression. - Merge the barman-cli project in Barman - Bug fixes: - Fix encoding error in get-wal on Python 3 (Jeff Janes, #221) - Fix exclude_and_protect_filter (Jeff Janes, #217) - Remove spurious message when resetting WAL (Jeff Janes, #215) - Fix sync-wals error if primary has WALs older than the first backup - Support for double quotes in synchronous_standby_names setting - Minor changes: - Improve messaging of check --nagios for inactive servers - Log remote SSH command with recover command - Hide logical decoding connections in replication-status command This release officially supports Python 3 and deprecates Python 2 (which might be discontinued in future releases). PostgreSQL 9.3 and older is deprecated from this release of Barman. Support for backup from standby is now limited to PostgreSQL 9.4 or higher and to WAL shipping from the standby (please refer to the documentation for details). Upgrade information Users of rsync backup method on a primary server should explicitly set backup_options to either concurrent_backup (recommended for PostgreSQL 9.6 or higher) or exclusive_backup (current default) before upgrading to Barman 2.8, otherwise Barman emits a warning every time it runs. ------------------------------------------------------------------- Fri Mar 29 15:24:42 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - update to 2.7 - Fix error handling during the parallel backup. Previously an unrecoverable error during the copy could have corrupted the barman internal state, requiring a manual kill of barman process with SIGTERM and a manual cleanup of the running backup in PostgreSQL. (GH#199) - Fix support of UTF-8 characters in input and output (GH#194 and GH#196) - Ignore history/backup/partial files for first sync of geo-redundancy (GH#198) - Fix network failure with geo-redundancy causing cron to break (GH#202) - Fix backup validation in PostgreSQL older than 9.2 - Various documentation fixes ------------------------------------------------------------------- Fri Feb 8 15:10:26 UTC 2019 - Marcus Rueckert <mrueckert@suse.de> - update to 2.6 - Add support for Geographical redundancy, introducing 3 new commands: sync-info, sync-backup and sync-wals. Geo-redundancy allows a Barman server to use another Barman server as data source instead of a PostgreSQL server. - Add put-wal command that allows Barman to safely receive WAL files via PostgreSQL’s archive_command using the barman-wal-archive script included in barman-cli - Add ANSI colour support to check command - Minor fixes: - Fix switch-wal on standby with an empty WAL directory - Honour archiver locking in wait_for_wal method - Fix WAL compression detection algorithm - Fix current_action in concurrent stop backup errors - Do not treat lock file busy as an error when validating a backup ------------------------------------------------------------------- Sat Oct 27 02:05:16 UTC 2018 - Marcus Rueckert <mrueckert@suse.de> - update to 2.5 - Add support for PostgreSQL 11 - Add check-backup command to verify that WAL files required for consistency of a base backup are present in the archive. Barman now adds a new state (WAITING_FOR_WALS) after completing a base backup, and sets it to DONE once it has verified that all WAL files from start to the end of the backup exist. This command is included in the regular cron maintenance job. Barman now notifies users attempting to recover a backup that is in WAITING_FOR_WALS state. - Allow switch-xlog --archive to work on a standby (just for the archive part) - Bug fixes: - Fix decoding errors reading external commands output (issue #174) - Fix documentation regarding WAL streaming and backup from standby ------------------------------------------------------------------- Tue Jun 26 23:49:25 UTC 2018 - mrueckert@suse.de - Migrated to systemd timers for all systemd based distros. You need to run: systemctl enable barman.timer systemctl start barman.timer To reenable the the automatic running again. - move cron and logrotate file to source instead of heredoc ------------------------------------------------------------------- Tue Jun 26 13:38:33 UTC 2018 - mrueckert@suse.de - move package to use python3 - properly use all python3 macros through out the spec file - clean up spec file with spec-cleaner - tighten permissions of config: old: root:root u=rwX,go=rX new: root:barman u=rwX,g=rX,o= - tighten permissions of the log dir old: barman:barman u=rwX,go=rX new: barman:barman u=rwX,go= ------------------------------------------------------------------- Fri Jun 1 12:14:11 UTC 2018 - mrueckert@suse.de - update to 2.4 - Main changes - Add standard and retry hook scripts for backup deletion (pre/post) - Add standard and retry hook scripts for recovery (pre/post) - Add standard and retry hook scripts for WAL deletion (pre/post) - Add --standby-mode option to barman recover to add standby_mode = on in pre-generated recovery.conf - Add --target-action option to barman recover, allowing users to add shutdown, pause or promote to the pre-generated recovery.conf file - Improve usability of point-in-time recovery with consistency checks (e.g. recovery time is after end time of backup) - Minor documentation improvements - Drop support for Python 3.3 - Relevant bug fixes: - Fix remote get_file_content method (Github #151), preventing incremental recovery from happening - Unicode issues with command (Github #143 and #150) - Add --wal-method=none when pg_basebackup >= 10 (Github #133) - Minor bug fixes: - Stop process manager module from ovewriting lock files content - Relax the rules for rsync output parsing - Ignore vanished files in streaming directory - Case insensitive slot names (Github #170) - Make DataTransferFailure.from_command_error() more resilient (Github #86) - Rename command() to barman_command() (Github #118) - Initialise synchronous standby names list if not set (Github #111) - Correct placeholders ordering (GitHub #138) - Force datestyle to iso for replication connections - Returns error if delete command does not remove the backup - Fix exception when calling is_power_of_two(None) - Downgraded sync standby names messages to debug (Github #89) ------------------------------------------------------------------- Fri Sep 8 23:16:56 UTC 2017 - mrueckert@suse.de - update to 2.3 - Add support to PostgreSQL 10 - Follow naming changes in PostgreSQL 10: - The switch-xlog command has been renamed to switch-wal. - In commands output, the xlog word has been changed to WAL and location has been changed to LSN when appropriate. - Add the --network-compression/--no-network-compression options to barman recover to enable or disable network compression at run-time - Add --target-immediate option to recover command, in order to exit recovery when a consistent state is reached (end of the backup, available from PostgreSQL 9.4) - Show cluster state (master or standby) with barman status command - Documentation improvements - Bug fixes: - Fix high memory usage with parallel_jobs > 1 (#116) - Better handling of errors using parallel copy (#114) - Make barman diagnose more robust with system exceptions - Let archive-wal ignore files with .tmp extension - update manual to 2.3 ------------------------------------------------------------------- Sat Aug 5 15:19:41 UTC 2017 - boris@steki.net - create /etc/barman.d as required by default configuration or crontab will fill up logs with info about missing directory ------------------------------------------------------------------- Thu Aug 3 17:34:23 UTC 2017 - mrueckert@suse.de - update to 2.2: - Implement parallel copy for backup/recovery through the parallel_jobs global/server option to be overridden by the --jobs or -j runtime option for the backup and recover command. Parallel backup is available only for the rsync copy method. By default, it is set to 1 (for behaviour compatibility with previous versions). - Support custom WAL size for PostgreSQL 8.4 and newer. At backup time, Barman retrieves from PostgreSQL wal_segment_size and wal_block_size values and computes the necessary calculations. - Improve check command to ensure that incoming directory is empty when archiver=off, and streaming directory is empty when streaming_archiver=off (#80). - Add external_configuration to backup_options so that users can instruct Barman to ignore backup of configuration files when they are not inside PGDATA (default for Debian/Ubuntu installations). In this case, Barman does not display a warning anymore. - Add --get-wal and --no-get-wal options to barman recover - Add max_incoming_wals_queue global/server option for the check command so that a non blocking error is returned in case incoming WAL directories for both archiver and the streaming_archiver contain more files than the specified value. - Documentation improvements - File format changes: - The format of backup.info file has changed. For this reason a backup taken with Barman 2.2 cannot be read by a previous version of Barman. But, backups taken by previous versions can be read by Barman 2.2. - Minor bug fixes: - Allow replication-status to work against a standby - Close any PostgreSQL connection before starting pg_basebackup (#104, #108) - Safely handle paths containing special characters - Archive .partial files after promotion of streaming source - Recursively create directories during recovery (SF#44) - Improve xlog.db locking (#99) - Remove tablespace_map file during recover (#95) - Reconnect to PostgreSQL if connection drops (SF#82) ------------------------------------------------------------------- Tue Feb 7 10:47:08 UTC 2017 - bo@suse.de - update to 2.1: - Add --archive and --archive-timeout options to switch-xlog command - Preliminary support for PostgreSQL 10 (#73) - Minor additions: - Add last archived WAL info to diagnose output - Add start time and execution time to the output of delete command - Minor bug fixes: - Return failure for get-wal command on inactive server - Make streaming_archiver_names and streaming_backup_name options global (#57) - Fix rsync failures due to files truncated during transfer (#64) - Correctly handle compressed history files (#66) - Avoid de-referencing symlinks in pg_tblspc when preparing recovery (#55) - Fix comparison of last archiving failure (#40, #58) - Avoid failing recovery if postgresql.conf is not writable (#68) - Fix output of replication-status command (#56) - Exclude files from backups like pg_basebackup (#65, #72) - Exclude directories from other Postgres versions while copying tablespaces (#74) - Make retry hook script options global - updated manual to 2.1 version ------------------------------------------------------------------- Mon Oct 3 14:12:41 UTC 2016 - mrueckert@suse.de - update to 2.0: - Support for pg_basebackup and base backups over the PostgreSQL streaming replication protocol with backup_method=postgres (PostgreSQL 9.1 or higher required) - Support for physical replication slots through the slot_name configuration option as well as the --create-slot and --drop-slot options for the receive-wal command (PostgreSQL 9.4 or higher required). When slot_name is specified and streaming_archiver is enabled, receive-wal transparently integrates with pg_receivexlog, and check makes sure that slots exist and are actively used - Support for the new backup API introduced in PostgreSQL 9.6, which transparently enables concurrent backups and backups from standby servers using the standard rsync method of backup. Concurrent backup was only possible for PostgreSQL 9.2 to 9.5 versions through the pgespresso extension. The new backup API will make pgespresso redundant in the future - If properly configured, Barman can function as a synchronous standby in terms of WAL streaming. By properly setting the streaming_archiver_name in the synchronous_standby_names priority list on the master, and enabling replication slot support, the receive-wal command can now be part of a PostgreSQL synchronous replication cluster, bringing RPO=0 (PostgreSQL 9.5.5 or higher required) - Introduce barman-wal-restore, a standard and robust script written in Python that can be used as restore_command in recovery.conf files of any standby server of a cluster. It supports remote parallel fetching of WAL files by efficiently invoking get-wal through SSH. Currently available as a separate project called barman-cli. The barman-cli package is required for remote recovery when get-wal is listed in recovery_options - Control the maximum execution time of the check command through the check_timeout global/server configuration option (30 seconds by default) - Limit the number of WAL segments that are processed by an archive-wal run, through the archiver_batch_size and streaming_archiver_batch_size global/server options which control archiving of WAL segments coming from, respectively, the standard archiver and receive-wal - Removed locking of the XLOG database during check operations - The show-backup command is now aware of timelines and properly displays which timelines can be used as recovery targets for a given base backup. Internally, Barman is now capable of parsing .history files - Improved the logic behind the retry mechanism when copy operations experience problems. This involves backup (rsync and postgres) as well as remote recovery (rsync) - Code refactoring involving remote command and physical copy interfaces - Bug fixes: - Correctly handle .history files from streaming - Fix replication-status on PostgreSQL 9.1 - Fix replication-status when sent and write locations are not available - Fix misleading message on pg_receivexlog termination - replace tutorial.pdf with manual.pdf ------------------------------------------------------------------- Wed May 4 01:46:11 UTC 2016 - mrueckert@suse.de - update to 1.6.0 - Support for streaming replication connection through the streaming_conninfo server option - Support for the streaming_archiver option that allows Barman to receive WAL files through PostgreSQL's native streaming protocol. When set to 'on', it relies on pg_receivexlog to receive WAL data, reducing Recovery Point Objective. Currently, WAL streaming is an additional feature (standard log archiving is still required) - Implement the receive-wal command that, when streaming_archiver is on, wraps pg_receivexlog for WAL streaming. Add --stop option to stop receiving WAL files via streaming protocol. Add --reset option to reset the streaming status and restart from the current xlog in Postgres. - Automatic management (startup and stop) of receive-wal command via cron command - Support for the path_prefix configuration option - Introduction of the archiver option (currently fixed to on) which enables continuous WAL archiving for a specific server, through log shipping via PostgreSQL's archive_command - Support for streaming_wals_directory and errors_directory options - Management of WAL duplicates in archive-wal command and integration with check command - Verify if pg_receivexlog is running in check command when streaming_archiver is enabled - Verify if failed backups are present in check command - Accept compressed WAL files in incoming directory - Add support for the pigz compressor (thanks to Stefano Zacchiroli zack@upsilon.cc) - Implement pygzip and pybzip2 compressors (based on an initial idea of Christoph Moench-Tegeder christoph@2ndquadrant.de) - Creation of an implicit restore point at the end of a backup - Current size of the PostgreSQL data files in barman status - Permit archive_mode=always for PostgreSQL 9.5 servers (thanks to Christoph Moench-Tegeder christoph@2ndquadrant.de) - Complete refactoring of the code responsible for connecting to PostgreSQL - Improve messaging of cron command regarding sub-processes - Native support for Python >= 3.3 - Changes of behaviour: - Stop trashing WAL files during archive-wal (commit:e3a1d16) - Bug fixes: - Atomic WAL file archiving (#9 and #12) - Propagate "-c" option to any Barman subprocess (#19) - Fix management of backup ID during backup deletion (#22) - Improve archive-wal robustness and log messages (#24) - Improve error handling in case of missing parameters ------------------------------------------------------------------- Wed Jun 10 16:09:52 UTC 2015 - mrueckert@suse.de - relax the dateutils requires again ------------------------------------------------------------------- Wed Jun 10 15:24:08 UTC 2015 - mrueckert@suse.de - update to 1.4.1 - Fix for WAL archival stop working if first backup is EMPTY (Closes: #64) - Fix exception during error handling in Barman recovery (Closes: # 65) - After a backup, limit cron activity to WAL archiving only (Closes: #62) - Improved robustness and error reporting of the backup delete command (Closes: #63) - Fix computation of WAL production ratio as reported in the show-backup command - Improved management of xlogb file, which is now correctly fsynced when updated. Also, the rebuild-xlogdb command now operates on a temporary new file, which overwrites the main one when finished. - Add unit tests for dateutil module compatibility - Modified Barman version following PEP 440 rules and added support of tests in Python 3.4 - changes from 1.4.0 - Incremental base backup implementation through the reuse_backup global/server option. Possible values are off (disabled, default), copy (preventing unmodified files from being transferred) and link (allowing for deduplication through hard links). - Store and show deduplication effects when using reuse_backup= link. - Added transparent support of pg_stat_archiver (PostgreSQL 9.4) in check, show-server and status commands. - Improved administration by invoking WAL maintenance at the end of a successful backup. - Changed the way unused WAL files are trashed, by differentiating between concurrent and exclusive backup cases. - Improved performance of WAL statistics calculation. - Treat a missing pg_ident.conf as a WARNING rather than an error. - Refactored output layer by removing remaining yield calls. - Check that rsync is in the system path. - Include history files in WAL management. - Improved robustness through more unit tests. - Fixed bug #55: Ignore fsync EINVAL errors on directories. - Fixed bug #58: retention policies delete. - unified tabs and spaces to spaces in the spec file - added barman-tutorial.en.pdf to the documentation - dont use sles_version for the noarch conditional. suse_version > 1110 is better. - python-argcomplete requires didnt use the __python_ver macro got noticed when i tried to build it with python 3 - documentation says we need dateutils < 2 as >= 2.0 requires python3. Encode that also in the requires - add requires for rsync as specified in the docs ------------------------------------------------------------------- Mon Sep 8 09:10:19 UTC 2014 - boris@steki.net - updated to latest upstream version 1.3.3 + most notable changes are: - refactored building of full path of a WAL file - Estimates WAL production rate for a backup - Really fix "ssh" version detection in "barman diagnose" command - Add command line options for retry of backup/recover copy - Implemented the --retry-times (including --no-retry) and --retry-sleep - Display compression ratio for WALs in show-backup - Support for 'last_backup_max_age' This new global/server option allows administrators to set the max age of the last backup, making it easier to detect any issues with periodical backup execution. - Support for "smart" incremental recovery Avoid invoking rsync with --checksum option during recovery - Use Postgres' server time for both begin_time and end_time - Retry option for base backup If a network error happens during rsync, add the ability to retry a defined number of time. - for verbose changelog please read changes info in /usr/share/doc/packages/barman/ChangeLog ------------------------------------------------------------------- Tue Feb 4 08:42:50 UTC 2014 - boris@steki.net - updated to latest upstream version 1.3.0 * Refactored BackupInfo class for backup metadata to use the new FieldListFile class (infofile module) * Refactored output layer to use a dedicated module, in order to facilitate integration with Nagios (NagiosOutputWriter class) * Refactored subprocess handling in order to isolate stdin/stderr/ stdout channels (command_wrappers module) * Refactored hook scripts management * Extracted logging configuration and userid enforcement from the configuration class. * Support for hook scripts to be executed before and after a WAL file is archived, through the 'pre_archive_script' and 'post_archive_script' configuration options. * Implemented immediate checkpoint capability with --immediate-checkpoint command option and 'immediate_checkpoint' configuration option * Implemented network compression for remote backup and recovery through the 'network_compression' configuration option (#19) * Implemented the 'rebuild-xlogdb' command (Closes #27 and #28) * Added deduplication of tablespaces located inside the PGDATA directory * Refactored remote recovery code to work the same way local recovery does, by performing remote directory preparation (assuming the remote user has the right permissions on the remote server) * 'barman backup' now tries and create server directories before attempting to execute a full backup (#14) * Fixed bug #22: improved documentation for tablespaces relocation * Fixed bug #31: 'barman cron' checks directory permissions for lock file * Fixed bug #32: xlog.db read access during cron activities ------------------------------------------------------------------- Fri Oct 4 12:38:06 UTC 2013 - boris@steki.net - updated to latest upstream 1.2.3 - Added support for PostgreSQL 9.3 - Added support for the "--target-name" recovery option, which allows to restore to a named point previously specified with pg_create_restore_point (only for PostgreSQL 9.1 and above users) - Fix python 2.6 compatibility - Added the "bandwidth_limit" global/server option which allows to limit the I/O bandwidth (in KBPS) for backup and recovery operations ------------------------------------------------------------------- Thu Mar 7 18:44:54 UTC 2013 - darin@darins.net - comment require python-abi - require python-argh >=0.21.2 ------------------------------------------------------------------- Wed Mar 6 21:49:48 UTC 2013 - darin@darins.net - Update to 1.2.0 - fix group ------------------------------------------------------------------- Tue Jan 15 18:17:47 UTC 2013 - darin@darins.net - Update and cleanup .spec for OpenSUSE - Moved %changlog to .changes ------------------------------------------------------------------- Thu Nov 29 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - New release 1.1.2 ------------------------------------------------------------------- Tue Oct 16 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - New release 1.1.1 ------------------------------------------------------------------- Fri Oct 12 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - New release 1.1.0 - Some improvements from Devrim Gunduz <devrim@gunduz.org> ------------------------------------------------------------------- Fri Jul 6 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - Open source release ------------------------------------------------------------------- Thu May 17 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - Fixed documentation ------------------------------------------------------------------- Tue May 15 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - Add cron job ------------------------------------------------------------------- Wed May 9 00:00:00 UTC 2012 - marco.nenciarini@2ndquadrant.it - Update to version 0.99.0 ------------------------------------------------------------------- Tue Dec 6 00:00:00 UTC 2011 - marco.nenciarini@2ndquadrant.it - Initial packaging.
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor
