elog 3.1.3-1-1build1 source package in Ubuntu

Changelog

elog (3.1.3-1-1build1) bionic; urgency=high

  * No change rebuild against openssl1.1.

 -- Dimitri John Ledkov <email address hidden>  Mon, 05 Feb 2018 23:21:23 +0000

Upload details

Uploaded by:
Dimitri John Ledkov on 2018-02-05
Uploaded to:
Bionic
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
misc
Urgency:
Very Urgent

See full publishing history Publishing

Series Pocket Published Component Section
Eoan release on 2019-04-18 universe misc
Disco release on 2018-10-30 universe misc
Cosmic release on 2018-05-01 universe misc
Bionic release on 2018-02-08 universe misc

Downloads

File Size SHA-256 Checksum
elog_3.1.3-1.orig.tar.gz 1.4 MiB aff2950737afffc0e235501c0762d692d875c096fe80e35f2e7363cd59563cb2
elog_3.1.3-1-1build1.debian.tar.xz 18.0 KiB aad1c187935e718d6fcffd70d078d74ea2dceb6601a4ed1e7c5346ac73b761dd
elog_3.1.3-1-1build1.dsc 1.5 KiB ee85ca7a306095f07f975ef65736f61eff9b4020813eef3a91968b7bef918412

View changes file

Binary packages built by this source

elog: Logbook system to manage notes through a Web interface

 The Electronic Logbook (ELOG) provides a Web interface to manage notes. Its
 general purpose is to make it easy for people to put and access information
 online; in the form of short, time stamped text messages with optional HTML
 markup for presentation, and optional file attachments. ELOG has its own
 daemon, there is no need for a full-fledged server (e.g. Apache). It stores
 notes as simple as plain text; no special formatting. Its features:
 .
   * Personal logbooks: Personal notes can be written into ELOG and can then be
     retrieved from anywhere with a Web browser.
   * Shared logbooks: Logbooks can be shared by several people, for reading and
     optionally for writing. Work groups can share and exchange information
     like in a (simplified) news group.
   * Small databases: Since arbitrary attributes can be defined for a logbook,
     it can be used as a small database with search facilities.
   * Problem collections: A system can consist of two logbooks, in one of which
     users enter bugs or problems. Whenever someone adds a problem, an email
     is automatically sent to the administrator.
   * Shift logbooks: If the Allow delete and Allow edit flags are off, an entry
     cannot be modified once it's been entered. This can be useful for shift
     logbooks for example in Physics experiments where each entry becomes a
     "document" with a time and author stamp.
   * File collections: Since files can be attached to ELOG entries, the system
     can be used to store and retrieve files.