Your message dated Thu, 12 Apr 2018 16:44:52 +0200
with message-id <>
and subject line fgetty uploaded
has caused the Debian Bug report #890437,
regarding RFS: fgetty/0.7-3 
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fgetty"

* Package name     : fgetty
  Version          : 0.7-3
  Upstream Author  : Felix von Leitner <>
* Url              :
* Licenses         : GPL-2+
  Programming Lang : C
  Section          : admin

 fgetty is a small, efficient, console-only getty for Linux.  It is derived
 from mingetty but hacked until it would link against diet libc to produce
 the smallest memory footprint possible for a simple yet complete getty.
 fgetty includes a login program that supports the checkpassword
 authentication interface, and also a checkpassword program that uses the
 standard C library interface to passwd and shadow.

It builds those binary packages:

  * fgetty

This package succesfully builds on debomatic machine:
Please note, that package is maintained with dgit(1) tool
using dgit-maint-merge(7) workflow. For more information about how to
sponsor this package, see dgit-sponsorship(7).

  Git repository:
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone fgetty
  $ cd fgetty
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild

Changes since last upload:

  * Acknowledge NMU
  * Bump debhelper version to 11
  * Install upstream changelog
  * Remove forgotten debian/fgetty.lintian from source package
    is meant to be used by user, rebuilding package.
  * Update Vcs-* fields in debian/control.
  * Update standards version to 4.1.3 (no changes needed)
  * Use secure URL when in debian/changelog `Format` field

  Dmitry Bogatov

--- End Message ---
--- Begin Message ---



--- End Message ---

Reply via email to