Your message dated Thu, 25 Sep 2014 18:22:47 +0200
with message-id <[email protected]>
and subject line Re: Bug#762678: RFS: hexer/0.1.8-1 (new upstream, refresh
packaging, ack NMU)
has caused the Debian Bug report #762678,
regarding RFS: hexer/0.1.8-1 (new upstream, refresh packaging, ack NMU)
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 [email protected]
immediately.)
--
762678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762678
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "hexer"; my previous sponsor,
Erik Schanze, seems to be too busy at the moment to either upload the
package or grant me the right to upload it myself via "dak dm". This is
a new upstream version, incorporating some Debian and Ubuntu fixes,
along with some refreshments of the Debian packaging.
* Package name : hexer
Version : 0.1.8-1
Upstream Author : Peter Pentchev <[email protected]>
* URL : http://devel.ringlet.net/editors/hexer/
* License : BSD-3
Section : utils
It builds a single binary packages that has been tested with sbuild,
Lintian, cme, and adequate:
hexer - interactive binary editor with a Vi-like interface
The package is available at mentors.d.n:
http://mentors.debian.net/package/hexer
dget -x http://mentors.debian.net/debian/pool/main/h/hexer/hexer_0.1.8-1.dsc
Changes since the last upload:
hexer (0.1.8-1) unstable; urgency=medium
* Acknowledge the NMU; thanks, Thibaut and Luca!
* Switch to debhelper 9:
- get the dpkg-buildflags information from debhelper, drop the build
dependency on dpkg-dev
- get the hardening flags from debhelper, drop the build dependency
on hardening-includes
- append -DBSD to CPPFLAGS, not CFLAGS
* Add --as-needed to the linker flags so that hexer is not needlessly
linked against libncurses when it only seems to need libtinfo.
* Update the copyright file:
- bring it up to the final version of the 1.0 format specification
- add the header License field
- bump my Debian packaging copyright year
* Remove the obsolete DM-Upload-Allowed source control field.
* Bump Standards-Version to 3.9.6 with no changes.
* Do not install the README file; it documents the installation only.
* Drop the source compression options; dpkg-dev's defaults are good enough.
* Let the watch file look for *.tar.bz2 release tarballs.
* Add my PGP public key and let uscan verify the upstream signature.
* New upstream version:
- drop the negative_size patch, applied upstream
- update the upstream copyright years
-- Peter Pentchev <[email protected]> Tue, 23 Sep 2014 17:43:32 +0300
I would be very grateful for any assistance with uploading this package!
G'luck,
Peter
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
* Peter Pentchev <[email protected]>, 2014-09-25, 15:27:
dget -x https://mentors.debian.net/debian/pool/main/h/hexer/hexer_0.1.8-1.dsc
Uploaded!
Here[0], hexer doesn't restore background color on exit. I don't like
my shell prompt in blue! :-(
Hm. This is an interesting one, I'll have to research it a bit more.
The funny part? I can reproduce it - when I run hexer with TERM=linux
from a Bash shell!
Yup, I'm using bash.
If I run it from Zsh, there's no problem. I will definitely look into
it, maybe take a look at a couple of other programs that use libtinfo;
to be honest, ISTR Bash having a problem with recovering from "man" on
some other Linux distributions a couple of years ago, I wonder if it
could be related.
FWIW, I don't recall having such problems with any other program.
--
Jakub Wilk
--- End Message ---
