Re: Bug#934184: ITP: nghttp3 -- C library for HTTP/3 functions
Control: reassign -1 wnpp On Mi, 07 aug 19, 22:11:42, Sakirnth Nagarasa wrote: > Package: nghttp3 > Owner: sakir...@gmail.com > > * Package name: nghttp3 > Upstream Author : nghttp3 contributors > * License : MIT License > Description : Implementation of HTTP/3 mapping over QUIC and QPACK > in C. > > Provides library for HTTP/3 fuctions. > > Greetings, > Sakirnth (Saki) -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Re: Bug#933885: ITP: GNU Health - a hospital information system
Control: reassign -1 wnpp On Du, 04 aug 19, 22:44:51, Sakirnth Nagarasa wrote: > Package: gnuhealth > Owner: sakir...@gmail.com > > * Package name: gnuhealth > Upstream Author : GNU Health contributors > * License : GPL-3+ > Description : GNU Health is a Free/Libre project for health > practitioners, health institutions and governments. It provides the > functionality of Electronic Medical Record (EMR), Hospital Management > (HMIS) and Health Information System (HIS). > > Its modular design allows to be deployed in many different scenarios: > from small private offices, to large, national public health systems. > > Greetings, > > Sakirnth (Saki) -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Re: Bug#931546: RFP: TTG -- SNMP Text Traffic Grapher
Control: reassign -1 wnpp
On Du, 07 iul 19, 14:55:59, Apachez wrote:
> Subject: RFP: TTG -- SNMP Text Traffic Grapher
> Package: TTG
> Severity: wishlist
>
> * Package name : TTG
> Version : 2.2
> Upstream Author : Antoni Sawicki
> * URL : https://github.com/tenox7/ttg
> * License : Apache License 2.0
> Description :
>
> TTG is a small command line utility that displays current throughput
> (bandwidth usage) on an interface of a remote device such as router,
> switch, firewall, etc., over SNMP. You can think of TTG as command line
> version of STG or a high-interval/ad-hoc query/test tool for MRTG, etc. The
> output is very similar to ping(1) command. You can use it to quickly
> check/measure traffic before waiting 5 minute cycle when configuring MRTG,
> as a means of using the data in text form (eg. copy in to an email or
> spreadsheet) or just a general purpose command line network administration
> aid.
>
> TTG allows you to specify: SI prefix k/M/G (default is auto), units
> bits/bytes (b/B), size of "kilo" which can be either 1000 or 1024 depending
> on a personal opinion (default is 1000), interval in seconds and count
> limit. Finally the utility also allows you to list all interfaces of the
> device and can take interface name, such as "FastEthernet1/1" or it's
> abbreviation ("fa1/1") instead of OID name/number as the parameter.
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
Re: getting rid of "testing"
On Ma, 25 iun 19, 08:08:22, Ansgar wrote:
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
AFAIK "unstable" is always symlinked to "sid", so it wouldn't make a
difference and also manages expectations ;)
"stable", besides significantly changing it's meaning at release may
also be actively harmful if one dist-upgrades by mistake[1] with
'stable' in sources.list.
While dist-upgrades are significantly smoother the Release Notes still
have important items that must be taken care of before/during/after
dist-upgrade.
Depending on your intention using "testing" may or may not be what you
want to have in sources.list even through releases.
Users that dist-upgrade early or install the next release while it's
still in testing for $reasons (e.g. hardware support, newer software
that is not available in backports, etc.) should always use the codename
to avoid surprises at release (as per above for "stable).
Those who want to stick with "testing" no matter what I believe[2] are
actually looking for a rolling distribution so it would probably make
sense to rename "testing" to "rolling"[3][4].
[1] because 'apt-get upgrade' doesn't install new packages many users
have developed a habit to always run 'apt-get dist-upgrade', e.g. to
upgrade their kernel package (in case of ABI change).
Users are slowly migrating to 'apt upgrade', but running 'apt-get
dist-upgrade' on stable just to get security upgrades will not disappear
anytime soon.
[2] based on more than 10 years experience on debian-user.
[3] or remove the "testing" symlink/name and add the "bob" rolling
release that was proposed in
https://lists.debian.org/debian-devel/2011/06/msg00136.html
[4] or "roling" to emphasize that it's incomplete :p
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
