Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Dmitry Bogatov]

[2019-08-15 17:59] Paride Legovini 
> Dmitry Bogatov wrote on 06/08/2019:
> > So, please:
> > 
> >  * drop --as-needed
> >  * fix spelling
> >  * finalize changelog (dch -r)
>
> Done.

Uploaded. Tagged. Permissions granted.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Dmitry Bogatov]

[2019-08-05 22:33] Paride Legovini 
> Dmitry Bogatov wrote on 23/07/2019:
> > [2019-07-21 11:36] Paride Legovini 
> >>> 1. In [942ed5e] you added this line:
> >>>
> >>> export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
> [...]
> That's my understanding too. In this case I'm pretty sure the binaries
> are not getting linked against extra libraries. Maybe in larger project
> it could be helpful to have a final prune of eventual extra libs.
>
> Do you suggest dropping those extra flags?

Yes.

> >>> 3. What is "irqbalance-ui"? It has no manpage, not referenced in
> >>>irqbalance(1) and even after source diving I can't understand how to
> >>>use it.
> >>
> >> I'll probably add a stub manpage for it.
> > 
> > Good.
>
> Done, and I upstreamed it:
>
> https://github.com/Irqbalance/irqbalance/commit/28575ddb46773a44

I: irqbalance: spelling-error-in-manpage usr/share/man/man1/irqbalance.1.gz 
similiar similar
I: irqbalance: spelling-error-in-manpage usr/share/man/man1/irqbalance.1.gz 
occured occurred

> >>>  5. Do we really need debconf to configure oneshot feature? Debconf
> >>> question block installation process, so they are not to be used
> >>> lightly, imho. Even ssh server does not use debconf to make me
> >>> review its config, which is of much more importance.
> >>
> >> I am more than happy with dropping it entirely.
> > 
> > Good.
>
> Done; I hope the note in d/NEWS is clear enough.

Yes, it is fine.

So, please:

 * drop --as-needed
 * fix spelling
 * finalize changelog (dch -r)

By the way, why

[ -z "${IRQBALANCE_ONESHOT+x} ]

instead of plain

[ -z "${IRQBALANCE_ONESHOT}" ]

?
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Dmitry Bogatov]

control: clone 932438 -2
control: reassign -2 irqbalance
control: retitle -2 add support for oneshot invocation with runit
control: owner -2 kact...@debian.org

[2019-07-21 11:36] Paride Legovini 
> > 1. In [942ed5e] you added this line:
> > 
> > export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
> > 
> >Why is it needed? Maybe, these flags should be provided by
> >dpkg-buildflags(1)?
>
> dpkg-buildflags does not currently provide the --as-needed flag to the
> linker, see:
>
> https://wiki.debian.org/HardeningWalkthrough
>
> or just try. The flags are not needed but I think using them when
> possible is good practice. For what --as-needed does see ld(1).

As I understand, this with this flag linker does not make dynamically
linked binary depend on library, that was passed on command line, but
none of its symbols is used.

If this is correct, question is why build system system links unused
library in first place.

> > 2. I think manpage in wrong direction should be patched, not overrided.
> > 
> > On package in general (does not block upload). These issues were present
> > before your changes, but it would be nice to solve them.
>
> I was expecting this comment :-)
>
> I don't really oppose patching the manpage section, and I'm willing to
> do so should you suggest it again in the next review round, but I
> personally don't like the idea very much.
> [...]

Convincing. Let there be override.

> > 3. What is "irqbalance-ui"? It has no manpage, not referenced in
> >irqbalance(1) and even after source diving I can't understand how to
> >use it.
>
> I'll probably add a stub manpage for it.

Good.

> > 4. Situation with "oneshot" option is quite... inconvenient.
> > 
> >* If you have ONESHOT option set, `/etc/init.d/irqbalance status`
> >  will report failure. It can be fixed by checking for ONESHOT
> >  variable in status) clause;
>
> Looks reasonable.
>
> >* current runscript does not respect ONESHOT option. It can be fixed
> >  with something like
> > 
> >#!/bin/sh
> >. /etc/default/irqbalance
> >if [ -n "${ONESHOT:-}" ] ; then
> >irqbalance --oneshot
> >sv down irqbalance
> >else
> >exec irqbalance --foreground
> >fi
> > 
> >  but it would be quite unnatural. I think proper solution would be
> >  separation of /etc/init.d/irqbalance and 
> > /etc/init.d/irqbalance-oneshot.
>
> I agree calling `sv down` from the runscript is ugly, on the other side
> I don't really like the idea of having two sets of init scripts for
> three init systems. Moreover while dh_installsystemd and dh_installinit
> have a --no-enable option, dh_unit does not, requiring some manual
> (hacky) handling.

Runit does not have support for "one-shot" invocations by design: it is
process supervisor, after all. But I agree, doubling number of initfiles
for three init systems is considerable burden.

So please check for $ONESHOT in init.d script, I will provide patch for
runscript after.

> >  5. Do we really need debconf to configure oneshot feature? Debconf
> > question block installation process, so they are not to be used
> > lightly, imho. Even ssh server does not use debconf to make me
> > review its config, which is of much more importance.
>
> I am more than happy with dropping it entirely.

Good.

> I'll ping you again when the updated branch is ready to be reviewed
> again. Thanks again.

Sure.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#932438: RFS: irqbalance/1.6.0-1 [ITA] -- Daemon to balance interrupts for SMP systems

[Dmitry Bogatov]

[2019-07-19 12:57] Paride Legovini 
> Package: sponsorship-requests
> Severity: normal
>
> Please review my packaging branch for irqbalance/1.6.0-1 at:
>
>   https://salsa.debian.org/paride-guest/irqbalance
> [...]

On your changes:

1. In [942ed5e] you added this line:

export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed

   Why is it needed? Maybe, these flags should be provided by
   dpkg-buildflags(1)?

2. I think manpage in wrong direction should be patched, not overrided.

On package in general (does not block upload). These issues were present
before your changes, but it would be nice to solve them.

3. What is "irqbalance-ui"? It has no manpage, not referenced in
   irqbalance(1) and even after source diving I can't understand how to
   use it.

4. Situation with "oneshot" option is quite... inconvenient.

   * If you have ONESHOT option set, `/etc/init.d/irqbalance status`
 will report failure. It can be fixed by checking for ONESHOT
 variable in status) clause;

   * current runscript does not respect ONESHOT option. It can be fixed
 with something like

   #!/bin/sh
   . /etc/default/irqbalance
   if [ -n "${ONESHOT:-}" ] ; then
   irqbalance --oneshot
   sv down irqbalance
   else
   exec irqbalance --foreground
   fi

 but it would be quite unnatural. I think proper solution would be
 separation of /etc/init.d/irqbalance and /etc/init.d/irqbalance-oneshot.

 5. Do we really need debconf to configure oneshot feature? Debconf
question block installation process, so they are not to be used
lightly, imho. Even ssh server does not use debconf to make me
review its config, which is of much more importance.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#931814: RFS: daggy/1.1.2-1 [ITP]

[Dmitry Bogatov]

[2019-07-10 22:17] Михаил Миловидов 
>
> part 2 text/plain1010
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "daggy":
>
> * Package name : daggy
>   Version : 1.1.2-1
>   Upstream Author  : Mikhail Milovidov milovidovmikh...@gmail.com
> * URL  : https://daggy.dev
> * License : Expat
>   Section  : net
>
> It builds those binary packages:
>
> daggy - run multiple commands on remote servers and save output locally

How does it compare with heap of ssh multiplexers already in Archive?
For example,

$ apt-cache search ssh multiplex
[... filtered a bit ...]
sslh - Applicative protocol multiplexer
taktuk - efficient, large scale, parallel remote execution of commands

-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#931576: RFS: blackbox-themes/0.6

[Dmitry Bogatov]

[2019-07-07 22:38] Juhani Numminen 
> Alternatively, one can download the package with dget using this command:
>   dget -x 
> https://mentors.debian.net/debian/pool/main/b/blackbox-themes/blackbox-themes_0.6.dsc

404.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]

[Dmitry Bogatov]

[2019-05-09 22:35] Bastian Germann 
> I have changed that and also made the smoke test run.

Fine. Uploaded. I also suggest you to use Gitlab CI. See here:

https://salsa.debian.org/salsa-ci-team/pipeline/
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#928637: RFS: emacs-neotree/0.5.2-1 [ITP]

[Dmitry Bogatov]

[2019-05-07 22:48] Nicholas D Steeves 
> Package: sponsorship-requests
> Severity: wishlist
> Control: block 872873 by -1
>
> I am looking for a sponsor for my package "emacs-neotree".  Neotree is
> a very popular Emacs addon on MELPA (Emacs addon repository), and is
> at the 99th percentile for MELPA unstable, and the 98th for MELPA stable.
>
>   https://melpa.org/#/neotree
>   https://stable.melpa.org/#/neotree
>
> Package name: emacs-neotree
> Version : 0.5.2-1
> Upstream Author : jaypei 
> URL : https://github.com/jaypei/emacs-neotree
> License : GPL-3+
> Section : lisp
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/e/emacs-neotree/emacs-neotree_0.5.2-1.dsc

Everything super-nice, just uploaded. One minor request: on next upload,
add field "Upstream-Contact" into debian/copyright.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]

[Dmitry Bogatov]

[2019-05-06 01:31] Bastian Germann 

> Thanks for coming back to me. I have fixed the things you pointed out.

In debian/rules you write ${DEB_VERSION_UPSTREAM} -- note "{", not "(".
Make uses $(foo) syntax for variable access. Build still successfull,
but, well, please double check this moment.

Also, you have no autopkgtest. I heard, default one for python could be
added with following in "debian/control".

Testsuite: autopkgtest-pkg-python
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Re: Configure your PC to contribute to Debian community

[Dmitry Bogatov]

[ Please, format your emails by 80 column ]

[2019-05-08 15:12] Vipul 
> Hey there,
>
> I've been using Debian from couples of years but haven't contributed
> yet back to community. I want to contribute to Debia n by maintaining
> packages and fixing bugs. Since I'm using Debian for work purpose also
> so, I don't want to mess-up  with my system by installing unstable
> packages or libraries. Is there a way to get isolation for work &
> contribution purpose to keep yourself organized?  I can get isolation
> by using Docker image or install one more copy of Debian in PC and
> switch between them but that w ould be painful. I want to hear from
> contributors & maintainers Which method they are using or prefer to
> get isolation?

You can work in chroot (debootstrap) and/or you can build packages in
schroot.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]

[Dmitry Bogatov]

[2019-05-03 17:18] Bastian Germann 
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "freetype-py". This closes a
> very long-standing wnpp issue. I posted an earlier version last
> September but got no attention so far.
>
>  * Package name: freetype-py
>Version : 2.1.0.post1-1
>Upstream Author : Nicolas P. Rougier
>  * URL : https://github.com/rougier/freetype-py
>  * License : BSD
>Section : python
>
> It builds those binary packages:
>
>   python3-freetype - Freetype Python bindings for Python 3

Here what I found interesting:

 * Lintian complains about "font-in-non-font-package" and
   "font-outside-font-dir". Why do you ship .ttf font in examples
   directory?

 * Policy is slightly outdated.

 * In debian rules, instead of "cat PKG-INFO | sed ..." you can use
   $DEB_VERSION_UPSTREAM. See /usr/share/dpkg/pkg-info.mk. By the way,
   it is useless-use-of-cat.

 * You can use B-D: debhelper-compat (= 11). Why not 12, by the way?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#927702: RFS: python-aiosqlite/0.10.0-1 [ITP] -- sqlite library for Python 3 using asyncio

[Dmitry Bogatov]

[2019-04-24 00:26] Benjamin Hof 
> On 23 April 2019, 12:36 +0000, Dmitry Bogatov wrote:
> >...
> > > I am looking for a sponsor for my package "python-aiosqlite":
> > 
> > Is this package dependency of some application?
>
> Yes, postfix-mta-sts-resolver (#917366).

I see. Please package test-dependency too, run tests and I will upload.
Feel free to add me to X-Debbugs-CC if you need sponsor for
test-dependency.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#927702: RFS: python-aiosqlite/0.10.0-1 [ITP] -- sqlite library for Python 3 using asyncio

[Dmitry Bogatov]

[ Benjamin Hof  ]
> I am looking for a sponsor for my package "python-aiosqlite":

Is this package dependency of some application?

> Alternatively, one can download the package with dget using this
> command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/p/python-aiosqlite/python-aiosqlite_0.10.0-1.dsc

Debianization looks fine, but it is quite unfortunate, that tests can't
be run.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#927283: RFS: lebiniou/3.31-1 -- displays images that evolve with sound

[Dmitry Bogatov]

[2019-04-18 13:21] Olivier Girondel 
> On 4/18/19 12:24 PM, Dmitry Bogatov wrote:
> > Looks fine. Are you sure you want to upload into unstable now, during
> > freeze? It may cause inconvenience should need to fix RC bug in
> > previous version arise.
>
> Hi Dmitry,
> No problem, this can wait.

I was not implying that I refuse to upload.

I can upload as-is, into unstable (but consider possible interactions
with release-team) or you can s/unstable/experimental/ and I will upload
to experimental.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#927363: RFS: urlwatch/2.17-1

[Dmitry Bogatov]

[2019-04-18 15:30] Maxime Werlen 
> I am looking for a sponsor for my package "urlwatch"
>
>  * Package name: urlwatch
>Version : 2.17-1
>Upstream Author : Thomas Perl
>  * URL : https://thp.io/2008/urlwatch/
>  * License : BSD-3-clause
>Section : web
>
> It builds those binary packages:
>   urlwatch   - monitors webpages for you
>
> To access further information about this package, please visit the
> following URL:
>   https://mentors.debian.net/package/urlwatch
>
> Alternatively, one can download the package with dget using this command:
>   dget -x
> https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.17-1.dsc
>
> More information about urlwatch can be obtained from
> https://github.com/thp/urlwatch.
>
> Changes since the last upload:
>
> urlwatch (2.17-1) unstable; urgency=medium
>
>   * New upstream release
>   * Handling .gitignore properly in d/.gitignore

Into unstable? Are you sure? During freeze we usually upload into
experimental, unless you are going to get unblock from release team.

Otherwise fine.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#927283: RFS: lebiniou/3.31-1 -- displays images that evolve with sound

[Dmitry Bogatov]

[2019-04-17 12:33] Olivier Girondel 
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "lebiniou":
>
>  * Package name: lebiniou
>Version : 3.31-1
>Upstream Author : Olivier Girondel 
>  * URL : https://biniou.net
>  * License : GPL-2+
>Section : graphics
>
> It builds this binary packages:
>
>   lebiniou - displays images that evolve with sound

Looks fine. Are you sure you want to upload into unstable now, during
freeze? It may cause inconvenience should need to fix RC bug in
previous version arise.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-16 19:10] Mathieu Mirmont 
> Both issues fixed, I re-uploaded the package to mentors (same links).

Uploaded. For next upload, please, take a look at following:

 * in `debian/rules' you skip dh_dwz step. Please write comment why.
 * in socklog-init init script you mix tabs and spaces. It is of no
   importance to Policy, but looks wierd.
 * file a bug aganist Lintian and either add comment into
   'd/socklog.lintian-override', or, hopefully, this file will be
   unneeded by time of next upload of `socklog'.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-13 11:11] Mathieu Mirmont 
> On Fri, Apr 12, 2019 at 05:22:35PM +0000, Dmitry Bogatov wrote:
> > [2019-04-10 23:48] Mathieu Mirmont 
> > >
> > > part 1 text/plain 434
> > > On Wed, Apr 10, 2019 at 08:20:30AM +, Dmitry Bogatov wrote:
> > > > You can repack it as new upstream version. New version would be
> > > > something like `2.1.0+repack-1'. Do not forget add clarification into
> > > > Debian.source.
> > >
> > > I've updated the package and uploaded to mentors:
> > >
> > > https://mentors.debian.net/package/socklog
> > > https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0+repack-1.dsc
> > 
> > Lintian (2.11.0) warnings:
> > 
> > W: socklog: missing-versioned-depends-on-init-system-helpers 
> > postinst:152 "update-rc.d defaults
> -disabled" needs i
> > nit-system-helpers >= 1.50
>
> Embarassingly I don't know how to get rid of this one. I've added a
> depencency on init-system-helpers (>= 1.50) naturally but the warning
> remains.
>
> Since ${misc:Pre-Depends} already includes init-system-helpers (>=
> 1.54~) I added lintian overrides. It's a bit dirty though, and the
> line number makes it a moving target. I'll fix the line numbers in the
> lintian overrides but if you know how to fix this in a better way I'm
> all ears.

I see. I suggest you to submit bug aganist Lintian, but in mean time I
am fine uploading with overrides. It may be useful to add reference to
that bug in override comment.

> > Oh, and extremely minor notice: in `debian/control' you align fields
> > with tabs. It does not look pretty, if tabstop is not 8. What about
> > expand(1)?
>
> Ah yeah sorry, I'll untabify this.

Thank you. By the way, you know about wrap-and-sort(1)?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-10 12:46] Mathieu Mirmont 
> > Are you sure you need "Depends: runit"? Maybe it is just me, but I
> > thought that `socklog' is just an implementation of `syslog'. If
> > so, hard dependency on bin:runit is quite heavyweight.
>
> It heavily relies on runsv and svlogd, that's how it splits files by
> syslog service name. Essentially socklog is a data collector for svlogd.
>
> The alternative would be to re-implement runsv and svlogd by redirecting
> the output of socklog to a file and using logrotate, but clearly that
> would be a hack, it's not how it's meant to be run, and it would have
> the risk of losing messages when logrotate kicks in.
>
> The dependency on runit is less risky than that. Also the dependency is
> on runit alone, not on any of the runit-* packages that call runsvdir,
> so it's quite lite.

I see. Fine.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-10 23:48] Mathieu Mirmont 
>
> part 1 text/plain 434
> On Wed, Apr 10, 2019 at 08:20:30AM +0000, Dmitry Bogatov wrote:
> > You can repack it as new upstream version. New version would be
> > something like `2.1.0+repack-1'. Do not forget add clarification into
> > Debian.source.
>
> I've updated the package and uploaded to mentors:
>
> https://mentors.debian.net/package/socklog
> https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0+repack-1.dsc

Lintian (2.11.0) warnings:

W: socklog: missing-versioned-depends-on-init-system-helpers 
postinst:152 "update-rc.d defaults-disabled" needs i
nit-system-helpers >= 1.50
W: socklog: missing-versioned-depends-on-init-system-helpers 
postinst:165 "update-rc.d defaults-disabled" needs i
nit-system-helpers >= 1.50
W: socklog: missing-versioned-depends-on-init-system-helpers 
postinst:178 "update-rc.d defaults-disabled" needs i
nit-system-helpers >= 1.50

Oh, and extremely minor notice: in `debian/control' you align fields
with tabs. It does not look pretty, if tabstop is not 8. What about
expand(1)?
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-08 01:03] Mathieu Mirmont 
> On Sat, Apr 06, 2019 at 07:13:56PM +0000, Dmitry Bogatov wrote:
> > 
> > [2019-04-04 13:30] Mathieu Mirmont 
> > > > * I know, it is pain, but there should be init.d script. You may want to
> > > >   take a look at bcron=0.11-8.
> > >
> > > Sure, no worries. How about systemd service files? It makes little sense
> > > to run socklog along with systemd I think, but for the principle it may
> > > be required to profile service files. What do you think?
> > 
> > Up to you. Presence of systemd unit files is not mandated by Policy,
> > unlike init.d scripts.
>
> Done, the init scripts call daemon(1) and runsv(1) and they work
> pretty nicely.

Are you sure you need "Depends: runit"? Maybe it is just me, but I
thought that `socklog' is just an implementation of `syslog'. If
so, hard dependency on bin:runit is quite heavyweight.

> > > >   I believe there should be separate sysuser for socklog-* services.
> > > >   Ideally, separate sysuser for /every/ from socklog-* service, but I do
> > > >   not know, whehter it is possible.
> > >
> > > Yeah good point. I tend to think that a single user for all socklog-*
> > > services would be enough, but if you prefer I can add one user per
> > > service.
> > 
> > Yes, I'd prefer as much separation, as possible.
>
> Done, one user per service.

I see. Thank you.

> There is one more issue that I noticed this weekend: the orig.tar.gz
> file that is registered in debian archives is not the same as the
> upstream tarball. It is in fact a tarball of the upstream tarball
> (!). I don't know why it's done this way, and it pretty much breaks
> breaks source format 3.0 (quilt) because I can't get dpkg-source to
> unpack the tarball before applying the patches. Do you know how to
> deal with that?

You can repack it as new upstream version. New version would be
something like `2.1.0+repack-1'. Do not forget add clarification into
Debian.source.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-04 13:30] Mathieu Mirmont 
> > * I know, it is pain, but there should be init.d script. You may want to
> >   take a look at bcron=0.11-8.
>
> Sure, no worries. How about systemd service files? It makes little sense
> to run socklog along with systemd I think, but for the principle it may
> be required to profile service files. What do you think?

Up to you. Presence of systemd unit files is not mandated by Policy,
unlike init.d scripts.

> >   I believe there should be separate sysuser for socklog-* services.
> >   Ideally, separate sysuser for /every/ from socklog-* service, but I do
> >   not know, whehter it is possible.
>
> Yeah good point. I tend to think that a single user for all socklog-*
> services would be enough, but if you prefer I can add one user per
> service.

Yes, I'd prefer as much separation, as possible.

> Thanks for the review!

My pleasure. By the way, you seems to forgot to add changelog entry
about new maintainer. Something in lines:

  * Set myself as maintainer (Closes: #)
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#926306: RFS: socklog/2.1.0-9

[Dmitry Bogatov]

[2019-04-03 10:45] Mathieu Mirmont 
> Package: sponsorship-requests
> Severity: normal [important for RC bugs, wishlist for new packages]
>
> Dear mentors,
>
> I am looking for a sponsor for my package "socklog"
>
> * Package name: socklog
>   Version : 2.1.0-9
>   Upstream Author : Gerrit Pape 
> * URL : http://smarden.org/socklog
> * License : BSD
>   Section : admin
>
> It builds those binary packages:
>
> socklog - system and kernel logging services (programs)
> socklog-run - system and kernel logging services
>
> To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/socklog
>
>
> Alternatively, one can download the package with dget using this
> command:
>
>   dget -x 
> https://mentors.debian.net/debian/pool/main/s/socklog/socklog_2.1.0-9.dsc
>
> Changes since the last upload:
>
>   * Convert the package to debhelper (Closes: #857208)
>   * patches: Import previous patches
>   * patch: remove the chkshsgr test
>   * watch: add the uscan watch file
>   * socklog-run: migrate to dh-runit (Closes: #668718, #834089)
>   * gitlab-ci.yml: add GitLab CI file
>   * control: update the Vcs fields
>   * doc-base: register the html documentation
>   * lintian: add overrides


* Please, do not use ${runit:Conflicts}. As suggested by Lintian, it is
  very strong relations. Use ${runit:Breaks} only. The very
  introduction of ${runit:Conflicts} was my mistake. It will make
  Lintian override unneeded.

* Please, consider merging bin:socklog-run into bin:socklog. Option
  `since' for dh_runit will be useful for it.

* I know, it is pain, but there should be init.d script. You may want to
  take a look at bcron=0.11-8.

* Please, add description to 0002-import-patch-tryto. It is unclear,
  what issue this patch resolves.

* In patch 0003-remove-chkshgrp you remove test, that fails on CI. Does
  it also fails in sbuild? If not, probably it should only be disabled in
  Gitlab CI?

* It is matter of taste, but are you aware, that you can

Build-Depends: debhelper-compat (= 12)

  and remove `debian/compat'?

* Dep-5 would be nice.

* What is the purpose of 'log' user, you create with dh_sysuser? You
  know, that bin:runit provides user `runit-log' since -20, don't you?

* All services run as same user, 'nobody'. It is unfortunate, since nobody is
  quite popular owner for NFS files. 

  I believe there should be separate sysuser for socklog-* services.
  Ideally, separate sysuser for /every/ from socklog-* service, but I do
  not know, whehter it is possible.

* I believe, README file is useless -- it contains copyright, authorship
  and homepage information only, which is already present in Debian
  package files.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#921482: RFS: note/1.3.26-3

[Dmitry Bogatov]

[2019-02-05 23:48] eamanu15 
> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-CC: kact...@debian.org
>
> Dear mentors,
>
> I am looking for a sponsor for my package "note"
>
> * Package name: note
>  Version : 1.3.26-3
>  Upstream Author : Thomas von Dein  >
> * URL : http://www.daemon.de/NOTE
> * License : Gnu Public License(GPL)
>  Section : utils
>
> It builds those binary packages:
>
>   note  - small program managing notes from commandline
> [...]
> Changes since the last upload:
>
> * Add me to Maintainer Field on d/control:
>   - For some reason that I ignore the Maintainer field
>   on d/control was not updated.

Sorry, I do not understand this sentense. Mind to simplify explaination
what changed?

> * Update fix-spelling.patch because is old.

Wording is strange. "because is old" is not full sentense. Usually, this
process is called patch refresh (quilt terminology), like

  * Refresh `fix-spelling.patch'

> * Delete NOTEDB folder and NOTEDB.pm because they are
>   not on upstream from ad6cb95 commit (Github).

What is ad6cb95 commit? For person who do not follow upstream
development, this changelog entry brings more questions, then
explainations.

> * Delete install.sh.
>- This file was forgotten to be deleted by the
>upstream author.
>- delete-install.patch was created

Line splitting is odd. First sub-entry fits 75 columns.

Also, why create patch to remove file? Does existence of this file
breaks build process?

In general, it is perfectly fine to ignore files upstream ship in
release and do not use it. Autotools-based releases ship `configure'
script, but we at Debian ignore it and regenerate it ourself.

> * Update d/watch file to download the upstream version from CPAN repository.

I'd elaborate this entry and added, that previously `debian/watch' used
author personal site.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#919614: RFS: note/1.3.26-2 [ITA]

[Dmitry Bogatov]

[2019-02-04 11:02] eamanu15 
> There is proposal (DEP-14) to create tags, like debian/2.1.2-5
> > in git repository, that mark state of source package, uploaded in
> > archives.
> >
>
> I pretend use gbp, I That create the tags and branch
> that you mention.
>
> I have a new version 1.3.26-3 applied the fix. I need to create start an
> mentors.d.n process
> or just I let it know when I ready?

Let us go regular RFS/mentors route.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#921020: RFS: imaplibext/0.7.6-1 [ITP]

[Dmitry Bogatov]

[2019-02-01 10:46] Thomas Ward 
> >> Dear mentors,
> >> [...]
> >> Alternatively, one can download the package with dget using this command:
> >>
> >>   dget -x 
> >> https://mentors.debian.net/debian/pool/main/i/imaplibext/imaplibext
> >> _0.7.6-1.dsc

Never wrap links, no matter how long they are.

Otherwise, fine. Uploaded.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#917854: RFS: pygithub/1.43.3-1

[Dmitry Bogatov]

[2019-02-02 00:51] Dmitry Shachnev 
> Hi Dmitry!
>
> On Thu, Jan 03, 2019 at 04:12:53AM +0000, Dmitry Bogatov wrote:
> > Looks fine, but I do not understand following line in `debian/rules':
> >
> > rm -rfv debian/python3-github/usr/lib/python3.*
> >
> > What is removed and why same statement it is not needed for python2
> > version?  Comment in `debian/rules' would be nice.
>
> I suggested to add that line. Quoting from my mail in #900368:
> [...]
> Now that Python 3.6 is no longer supported (and there is only one supported
> Python 3 version), that hack can be dropped.

Comment [remote it at/when] in such cases would be definitely helpful.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#921020: RFS: imaplibext/0.7.6-1 [ITP]

[Dmitry Bogatov]

[2019-01-31 12:49] Thomas Ward 
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "imaplibext"
>
>  * Package name: imaplibext
>Version : 0.7.6-1
>Upstream Author : Thomas Ward 
>  * URL : https://gitlab.com/teward/imaplibext
>  * License : AGPL-3+
>Section : python
>
> It builds those binary packages:
>
>   python3-imaplibext - imaplib extension library for UID-based commands (Pyth
> on 3)

Shouldn't source package name be python-imaplibext?

> Alternatively, one can download the package with dget using this command:
>
>   dget -x https://mentors.debian.net/debian/pool/main/i/imaplibext/imaplibext
> _0.7.6-1.dsc

There seems some reproducible source of confusion. I do not have your
(or any other sponsoree) key. Write `dget -ux', please.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#919614: RFS: note/1.3.26-2 [ITA]

[Dmitry Bogatov]

[2019-01-31 09:19] eamanu15 
>   * you seems to not push debian/* tags. They makes understanding history
> >of package simplier
> I don't understand this point

There is proposal (DEP-14) to create tags, like debian/2.1.2-5
in git repository, that mark state of source package, uploaded in
archives.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#919614: RFS: note/1.3.26-2 [ITA]

[Dmitry Bogatov]

[ Adding bug back into CC ]

[2019-01-30 00:05] eamanu15 
> You can see the change on salsa https://salsa.debian.org/eamanu-guest/note
> Regards!

Following does not matter as far as packaging concerned -- maintainer
workflow is matter of personal taste, but you may be interested:

 * you seems to not push debian/* tags. They makes understanding history
   of package simplier
 * commit 0bb88, that updates upstream sources is not merge,
   as customary with git-buildpackage workflow
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#841270: RFS: debrequest/0.2 ITP

[Dmitry Bogatov]

control: reopen -1

[2016-10-21 08:09] Gianfranco Costamagna 
> >It might be more useful to add this to `devscripts` or some other
> >existing package rather than adding a new package.

Hi!

For now, I uploaded debrequest into experimental, but ideally it should
be merged into devscripts.

Dear devscript maintainers, how should we proceed?

-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#920558: RFS: liboauth/1.0.3-2 [QA]

[Dmitry Bogatov]

[2019-01-27 10:59] Carlos Maddela 
>
> part   text/plain1706
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "liboauth"
>
>  * Package name: liboauth
>Version : 1.0.3-2
>Upstream Author : Robin Gareus 
>  * URL : http://liboauth.sourceforge.net/
>  * License : Expat
>Section : libs
>
>   It builds these binary packages:
>
>  liboauth-dev - C library implementing OAuth Core 1.0a API (development files)
>  liboauth0  - C library implementing OAuth Core 1.0a API (runtime)
>
>   To access further information about this package, please visit the 
> following URL:
>
>   https://mentors.debian.net/package/liboauth
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -ux 
> https://mentors.debian.net/debian/pool/main/libo/liboauth/liboauth_1.0.3-2.dsc

Uploaded. By the way, what is the purpose of dh_autoreconf --as-needed?

PS. Thank you, I learnt about future=+lfs.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#920433: RFS: wiggle/1.1-1 [QA]

[Dmitry Bogatov]

[2019-01-25 22:45] Carlos Maddela 
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "wiggle"
>
>  * Package name: wiggle
>Version : 1.1-1
>Upstream Author : Neil Brown 
>  * URL : https://neil.brown.name/wiggle
>  * License : GPL-2+
>Section : vcs
>
>   It builds this binary package:
>
> wiggle - apply patches with conflicting changes
>
>   To access further information about this package, please visit the 
> following URL:
>
>   https://mentors.debian.net/package/wiggle
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/w/wiggle/wiggle_1.1-1.dsc

Uploaded. Thank you for your contribution.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#919865: RFS: scdoc/1.6.0-1

[Dmitry Bogatov]

[2019-01-20 10:53] Birger Schacht 
> Alternatively, one can download the package with dget using this command:
> dget -x
> https://mentors.debian.net/debian/pool/main/s/scdoc/scdoc_1.6.0-1.dsc
> 
> Alternatively, you can access package debian/ directory via git from URL:
> https://salsa.debian.org/bisco-guest/scdoc.git
> 
> More information about scdoc can be obtained from
> https://git.sr.ht/~sircmpwn/scdoc
> Changes since last upload:
> 
>   * New release

I see much more changes -- debhelper bump, standards bump, Vcs-* fields,
refreshed patches. They all must be documented in `debian/changelog'.

PS. I suggest to use 'New upstream release' instead of just 'New release'.

-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#917629: RFS: xhk/1.0-1

[Dmitry Bogatov]

[2019-01-20 18:39] Kieran Bingham 
> This log shows you have pushed then released the space before pressing
> the next key to mirror.  [...]

Yes. This way it works.

But documentation still have to be improved -- manpage is almost
unreadable and refers to non-existent info manual.  I think in current
state this package is not ready for upload.


-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#910608: RFS: libtheft/0.4.5-1 ITP #910296

[Dmitry Bogatov]

[2018-11-01 23:22] Richard Ipsum 
> On Fri, 26 Oct 2018, at 02:47, Dmitry Bogatov wrote:
> > 
> > [2018-10-23 23:53] Richard Ipsum 
> > > Fixed remaining issues, sorry this took me a while to get to.
> > > I have uploaded a new version of the package to mentors.
> > 
> > Looks incredible clean, but I still found one issue :)
> > 
> > The package your does not follow multiarch path conventions.
> > For example, for libyaml-dev
> > [...]

> thanks for the feedback, I'm afraid I will be away for some time, so
> it may be several weeks before I'm able to look at f ixing this.

Any progress?

Bug#919614: RFS: note/1.3.26-2 [ITA]

[Dmitry Bogatov]

[2019-01-17 23:13] eamanu15 
> Dear mentors,
> 
> I am looking for a sponsor for my package "note"
> 
> * Package name: note
>  Version : 1.3.26-2
>  Upstream Author : Thomas von Dein 
> * URL : http://www.daemon.de/NOTE
> * License : Gnu Public License(GPL)
>  Section : utils
> 
> It builds those binary packages:
> 
>   note  - small program managing notes from commandline
> 
> To access further information about this package, please visit the
> following URL:
> 
> https://mentors.debian.net/package/note
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x
> https://mentors.debian.net/debian/pool/main/n/note/note_1.3.26-2.dsc
> 
> More information about note can be obtained from http://www.daemon.de/NOTE

Uploaded. There is some things you may want to address in next revision:

 * debian/watch uses plain http. Any chance for https?
 * there is a lot of spelling errors. Please fix them and submit patch
   upstream.
 * /usr/share/perl5/NOTEDB/README is bad. Move it into documentation.

Bug#917629: RFS: xhk/1.0-1

[Dmitry Bogatov]

[2019-01-04 12:29] Kentaro Hayashi 
> On Fri, 4 Jan 2019 02:17:57 +0100 Adam Borowski  wrote:
> > Am I holding it wrong?
> 
> step 1. launch xhk
> step 2. press "j" key, then "j" is typed
> step 3. press space and "j" key, then "f" is typed.
> 
> If xhk works as above, it is OK (expected behavior).

It does not work for me like this to me. Here is log (-d):

-- HalfKey Xorg Driver Utility 1.0 --
SetPriority call failed : -1
Process Priority set at 0
XOpenDisplay(":0")
XI Version 2.0
Device Virtual core XTEST keyboard (id: 5) is a slave keyboard
Device is attached to/paired with 3
Device Power Button (id: 6) is a slave keyboard
Device is attached to/paired with 3
Device Video Bus (id: 7) is a slave keyboard
Device is attached to/paired with 3
Device Power Button (id: 8) is a slave keyboard
Device is attached to/paired with 3
Device Sleep Button (id: 9) is a slave keyboard
Device is attached to/paired with 3
Device Apple Inc. Apple Internal Keyboard / Trackpad (id: 10) is a 
slave keyboard
Device is attached to/paired with 3
Device FaceTime Camera (Built-in): Fac (id: 12) is a slave keyboard
Device is attached to/paired with 3
Floating device ID 10
Keyrelease 36 (Return), keycode = 36 (Return) time=385249722

Keypress 44 (j), keycode = 44 (j) time=385251136

jKeyrelease 44 (j), keycode = 44 (j) time=385251264

Keypress 65 (space), keycode = -1 ((null)) time=385251704
Keyrelease 65 (space), keycode = 65 (space) time=385251808

 Keypress 44 (j), keycode = 44 (j) time=385252784

jKeyrelease 44 (j), keycode = 44 (j) time=385252936

Keypress 65 (space), keycode = -1 ((null)) time=385253024
Keyrelease 65 (space), keycode = 65 (space) time=385253192

 Keypress 66 (Control_L), keycode = 66 (Control_L) time=385253568

Keypress 54 (c), keycode = 54 (c) time=385256208

cKeyrelease 54 (c), keycode = 54 (c) time=385256368

Keyrelease 66 (Control_L), keycode = 66 (Control_L) time=385256376

Keypress 111 (Up), keycode = 111 (Up) time=385256528

^[[AKeyrelease 111 (Up), keycode = 111 (Up) time=385256704

Keypress 66 (Control_L), keycode = 66 (Control_L) time=385257192

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-12-29 19:54] Vincent Bernat 
> > Probably not. Violations of FHS is violation of policy, and to get
> > authorization to policy violation is long road, starting with discussion
> > on debian-devel@.
> >
> > But, can't we just configure Nix to store it under /var/nix?
> 
> This would break the ability to use pre-built stuff and make nix
> slow.

I belive you, but just for my curiosity, what will break if we download
substitute (nar, almost tar archive) and extract it not in /nix, but in
/var/nix?

In mean time, I took a look at your debianization. Great work. One
question:

 * You install developer stuff (headers, pkg-config files) in nix
   package. It is not needed for mere user, so I believe you should
   make three binary packages -- nix, libnix and libnix-dev.

   By the way, who are users of nix development files?

Bug#919131: RFS: apt-listbugs/0.1.27

[Dmitry Bogatov]

[2019-01-13 00:21] "Francesco Poli (wintermute)" 
> Package: sponsorship-requests
> Severity: normal
> 
> Hi!
> 
> I have just finished preparing a new version of the apt-listbugs
> package (0.1.27): it is ready to be uploaded to Debian sid.
> Could someone please build the package from commit
> [eb4d507254f84432405d36a8f563226a4f145522], and sponsor its upload
> to unstable?
> 
> [eb4d507254f84432405d36a8f563226a4f145522]: 
>  6a8f563226a4f145522>

Uploaded. Still no dep5?

Bug#919105: RFS: uriparser/0.9.1-1

[Dmitry Bogatov]

[2019-01-12 19:28] Jörg Frings-Fürst 
> Severity: normal
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "uriparser"
> 
>Package name: uriparser
>Version : 0.9.1-1
>Upstream Author : Sebastian Pipping 
>URL : https://github.com/uriparser/uriparser
>License : BSD-3-clause, LGPL-2.1+, GPL-3+
>Section : libs
> [...]
>   dget -x 
> https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.1-1.dsc

It 404 for me.



pgpr4nNmfh_Fx.pgp
Description: PGP signature

Bug#917624: RFS: ncurses-hexedit/0.9.7+orig-6

[Dmitry Bogatov]

[2018-12-31 09:20] Carlos Maddela 
> > [ Dmitry Bogatov ]
> > Looks fine. Uploaded. But what does +orig means in version?
> > 
> 
> When I took over as maintainer, I wanted to know why the project's
> original tarball in Debian differed from that of the one available
> upstream. I found that they only differed in the way that the top level
> directory was named. From what I gather, this was necessary for Debian's
> earlier build system, as documented here:
> https://wiki.debian.org/Packaging/Intro. See Q for "do we need to
> repack the original tarball if it doesn't contains a properly named
> foo-1.0 folder?" Since, it's no longer necessary to repack the original
> tarball, I thought it would be best to revert to using the original
> upstream tarball without any changes. However, the only way I could do
> so was to upload it with a higher version number, hence the +orig. If in
> the unlikely event that a new upstream version were to be released, the
> +orig can be dropped once again.

I see. Thank you. May I suggest you to put this wonderful explanation into
`debian/README.source'. It may save trouble for future maintainer or
save you from questions from another sponsor :)

Re: RFS: pygithub/1.43.3-1

[Dmitry Bogatov]

As other folks already mentioned, you do not use CC: you already use
X-Debbugs-CC. In this particular case, email with bug number got
filtered-out as duplicate in my setup.

[2018-12-31 00:16] eamanu15 
> I am looking for a sponsor for my package "pygithub"
> 
> * Package name: pygithub
> Version : 1.43.3-1
> Upstream Author : Adam Dangoor 
>   Vincent Jacques 
>   Jeremy Phelps 
> * URL : https://pypi.python.org/pypi/PyGithub
> * License : LGPL-3+
>   Section : python
> 
> It builds those binary packages:
> 
> python-github - Access to full Github API v3 from Python2
> python3-github - Access the full Github API v3 from Python3

Looks fine, but I do not understand following line in `debian/rules':

rm -rfv debian/python3-github/usr/lib/python3.*

What is removed and why same statement it is not needed for python2
version?  Comment in `debian/rules' would be nice.

And some very minor suggestions:

 * Standards-Version slightly outdated
 * debhelper-compat style reduces redundancy
 * Probably F-variables could be used to avoid repetition in
   binary package descriptions? (See dpkg-substvars(5))

I do not know habits of Python Modules Team, but would not it be more
apporiate for this packages to be sponsored by DD from team? I can check
basic things, but I do not know whole picture, like transitions or
reverse dependencies.

PS. I am glad to see that pygithub finally moved under aegis of
Python Modules Team.

Bug#917624: RFS: ncurses-hexedit/0.9.7+orig-6

[Dmitry Bogatov]

control: owner -1 kact...@debian.org

[2018-12-29 23:48] Carlos Maddela 
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "ncurses-hexedit"
> 
>  * Package name: ncurses-hexedit
>Version : 0.9.7+orig-6
>Upstream Author : Adam Rogoyski 
>  * URL : http://www.rogoyski.com/adam/programs/hexedit/
>  * License : GPL-2.0+
>Section : editors
> 
>   It builds this binary package:
> 
> ncurses-hexedit - Edit files/disks in hex, ASCII and EBCDIC
> 
>   To access further information about this package, please visit the 
> following URL:
> 
>   https://mentors.debian.net/package/ncurses-hexedit
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> https://mentors.debian.net/debian/pool/main/n/ncurses-hexedit/ncurses-hexedit_0.9.7+orig-6.dsc

I believe it should be `dget -ux'. In general, sponsor does not have
sponsoree's key in his keyring.  Could you please file bug aganist
mentors.debian.net about it and add me in CC?

>   Changes since the last upload:
>
>   * Set "Rules-Requires-Root: no".
>   * Simplify process by which mutable files are backed up and restored.

I like this idea. Thank you.

>   * Allow build to be as verbose as possible.
>   * Fix spelling errors detected by lintian and mwic.
>   * Indicate compliance with Debian Policy 4.3.0.

Looks fine. Uploaded. But what does +orig means in version?

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-12-27 11:24] Kai Harries 
> > [2018-02-26 22:46] Andrey Rahmatullin 
> >> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> >> > > The source package you've uploaded is broken, as .dsc mentions
> >> > > nix_1.11.15-2~a1.debian.tar.xz.
> >
> > Hi!
> >
> > What is state of affairs with packaging nix? I am interested in getting
> > things done, maybe I could contribute somehow?
> 
> We need to discuss with ftp-masters if we can get an exemption from
> the non-standard-toplevel-dir lintian rule (see this bug [1]). I am
> still planning to write a request to them, do you know if
> ftpmas...@debian.org would be the right address to start this
> discussion?

Probably not. Violations of FHS is violation of policy, and to get
authorization to policy violation is long road, starting with discussion
on debian-devel@.

But, can't we just configure Nix to store it under /var/nix?

> Furthermore I am waiting for the 2.2 Nix upstream release (see here [2])
> the master was not buildable for me the last time I tried it (see here
> [3]).

I will take a look.

Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager

[Dmitry Bogatov]

[2018-02-26 22:46] Andrey Rahmatullin 
> On Sun, Feb 25, 2018 at 11:14:37PM +0100, Kai Harries wrote:
> > > The source package you've uploaded is broken, as .dsc mentions
> > > nix_1.11.15-2~a1.debian.tar.xz.

Hi!

What is state of affairs with packaging nix? I am interested in getting
things done, maybe I could contribute somehow?

Bug#916285: RFS: extsmail/2.2-1 -- enables the robust sending of e-mail to external commands

[Dmitry Bogatov]

[2018-12-19 02:23] Olivier Girondel 
> Hi Dmitry,
> 
> I use this repository to host the debian/ directory usesd to build the
> package: https://github.com/oliv3/extsmail-debian

Yes, use it.

> Or should I just drop Vcs-Git ?

No! Missing Vcs-Git is very bad.

Bug#916285: RFS: extsmail/2.2-1 -- enables the robust sending of e-mail to external commands

[Dmitry Bogatov]

[2018-12-19 14:01] Olivier Girondel 
> On Wed, 19 Dec 2018 02:12:11 +0100 Olivier Girondel  
> wrote:
> > On Thu, 13 Dec 2018 16:15:40 +0100 Adam Borowski 
> > wrote:
> > > Alas, it doesn't build:  http://ix.io/1vVp
> > > 
> > > common.c:37:10: fatal error: conf_parser.tab.h: No such file or directory
> > >  #include "conf_parser.tab.h"
> > >   ^~~
> > > 
> > > (I didn't review further.)
> > 
> > Hi Adam,
> > 
> > (...)
> > dh_auto_build: make V=1 -j6 returned exit code 2
> > 
> > It's a parallel build issue, most likely due to missing Makefile
> > dependencies, upstream is aware of this.
> > 
> I'll make a patch to address this issue.

You could pass --no-parallel to `dh', you know?

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-12-19 15:41] Adrian Nuta 
> >  * your documentation should be in /usr/share/doc/manticore, not MANTICORE
> >
> removed that folder (not sure why cmake was using uppercased name)
> 
> >  * I believe you install not all available documentation. You may want
> >to create bin:manticore-doc for it.
> >
> We don't have a text version of the documentation and it's pretty large.
> Not sure how would make sense to include it in package when it's online.

HTML local documentation is fine too.

Including it has a lot of sense. It brings convenience -- not everybody
has fast (>= 1Mb/sec) access to Internet and privacy -- local
documentation do not have trackers and access.log.

>  * chown manticore:manticore /etc/sphinxsearch is strage. Files in /etc
>
> >are not meant to be edited by someone, but root. Ideally, you should
> >assume /etc is mounted read-only.
> >  * What are relations with bin:sphinxsearch? Are they co-installable?
> >
> About these ... there's a big omission I've made: manticore is a
> replacement for sphinxsearch
> (mantictore is a fork from last OSS version of sphinx, the current
> sphinxsearch is some kind of free binary only).

I believe in this case you'd better coordinate your work with maintainer
of bin:sphinxsearch, Radu Spineanu . He would be much
more compenent sponsor in your case. Added him in Cc.

> I added Replace and  Break in control file.
> The reason /etc/sphinxsearch is chowned in case user switch to manticore
> (we use different folders for log and data, but kept same config file
> path).

I foresee issues when user installs manticore, and after that try to
install sphixsearch. You definitely need to coordinate.

> One question about debian/watch: when checking, is the orig.tar.gz
> uploaded on mentors used or the version from watch?  Because right now
> the upstream release doesn't include many of the fixes (they will be
> all on next one)

uscan downloads what is written in `debian/watch'. In your case it would
be github release. If it is incomplete, they you have to make it
complete :)

Bug#916658: RFS: apt-listbugs/0.1.26

[Dmitry Bogatov]

[2018-12-17 00:21] "Francesco Poli (wintermute)" 
> Hello everybody!
> 
> I prepared a new version of the apt-listbugs package (0.1.26):
> it is ready to be uploaded to Debian unstable.
> Could someone please build the package from commit
> [c04fcb88ed8ba0f87c62d5711f394dd455231754], and sponsor its upload to
> sid?
> 
> [c04fcb88ed8ba0f87c62d5711f394dd455231754]: 
>  d5711f394dd455231754>
> 
> The changes since the last upload are:
> 
>   * fixed "executes xdg-open as root user": implemented a way to drop root
> privileges when invoking querybts or a browser, if we can figure out
> which regular user became root (via "su -", "sudo", ...) and if
> package s6 is installed (Closes: #910122)
>   * added xdg-open to the list of possible ways to invoke an appropriate
> web browser
>   * enhanced interface consistency regarding external program (querybts
> and web browser) invocation
>   * enhanced error handling consistency regarding external program invocation
>   * converted README.Debian into README.md (in markdown syntax) and
> improved the document a bit
>   * created FAQ.md by taking some parts from README.md
>   * updated German translation, thanks to Chris Leick! (Closes: #914703)
>   * updated Russian translation, thanks to Sergey Alyoshin! (Closes: #915374)
>   * updated Portuguese translation, thanks to Miguel Figueiredo!
> (Closes: #915802)
>   * updated Italian translation, thanks to Luca Monducci!
>   * updated Dutch translation, thanks to Frans Spiesschaert! (Closes: #916365)
>   * updated Danish translation, thanks to Morten Bo Johansen! (Closes: 
> #916384)
>   * updated French translation, thanks to Jean-Baka Domelevo Entfellner!
> (Closes: #916509)

Uploaded. You are not DM yet, aren't you?


pgp5Y2K18kp2v.pgp
Description: PGP signature

Re: a proposal to update the abcm2ps package

[Dmitry Bogatov]

[2018-12-14 13:01] Tong Sun 
>
> part   text/plain 310
> On Fri, Dec 14, 2018 at 10:27 AM Patrice Duroux wrote:
> 
> > And so here is the current work available at Salsa on my guest account:
> > https://salsa.debian.org/Peutch-guest/abcm2ps
> 
> I'm not an expert at all, but I think the project on Salsa should
> include 3 branches, including upstream, pristine-tar & debian.

Personally, I believe that `pristine-tar' is required only if upstream
ships PGP signature. Otherwise, restoring orig tarball from git tag on
`upstream' branch is good enough.

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

> Added a debian/watch, not sure why mentor lintian doesn't see it, uscan
> doesn't report any error, it should get our official tar.gz release for
> github.

You run `lintian -EvIL +pedantic', don't you? Missing `debian/watch'
considered low-severity issue

> Fixed the overrides and indentation.

Nice. It builds. I found at least following issues.

 * no manpage for wordbreaker. You will not pass NEW without it.
 * whitespace errors in debian/rules, debian/copyright, ...
 * missing years in some entries in debian/copyright
 * your documentation should be in /usr/share/doc/manticore, not MANTICORE
 * I believe you install not all available documentation. You may want
   to create bin:manticore-doc for it.
 * I doubt usefullness for end-user of internal-coding-standard.txt
 * lists in descriptions in `debian/control' are usually indented
   by one space
 * `manticore' system user seems to not get removed on package purge
 * What is the point of 'foo || exit $?' construct with `set -e' set?
 * chown manticore:manticore /etc/sphinxsearch is strage. Files in /etc
   are not meant to be edited by someone, but root. Ideally, you should
   assume /etc is mounted read-only.
 * What are relations with bin:sphinxsearch? Are they co-installable?

I will stop here for now. I am sorry to see you use analytics. Your
right as upstream, sure, but it must not appear in html files, provided
by debian.

Also, I remind you that new packages have only one changelog entry, with
revision -1 and single line "Initial release (Closes: #ITP-number)"

Bug#916285: RFS: extsmail/2.2-1 -- enables the robust sending of e-mail to external commands

[Dmitry Bogatov]

[2018-12-12 17:38] Olivier Girondel 
> Severity: normal
> 
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "extsmail"
> 
>  * Package name: extsmail
>Version : 2.2-1
>Upstream Author : Laurence Tratt 
>  * URL : https://tratt.net/laurie/src/extsmail/
>  * License : BSD/MIT
>Section : mail
> 
>   It builds this binary package:
> 
> extsmail   - enables the robust sending of e-mail to external commands
> 
>   The package appears to be lintian-clean
> 
>   To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/extsmail

Seems you have Vcs-* fields in `debian/control' wrong. They must point
to debianization Git, not to upstream Git.

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-12-10 22:13] Adrian Nuta 
>   * Using output of `lsb_release' in CPP flags could be issue for
> > reproducibility. Is it strictly necessary?
> >
> 
> That flag is for our cmake to know on which distro is (the output of that
> command involving lsb_release should be  'debian' )  -  we already have it
> setup to build for several distros, but need to tell him on which he is.
> I saw others use lsb_release output in control for similar job. I'm open to
> suggestions.

(Debian hat) Fine.

(Programmer hat) Why build system need to know, which distro it is build
on?  I guess (did not check sources) you actually interested in
something more specific, then name of distribution (my
linux-from-scratch installation does not have name, for example).

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-12-09 23:03] Adrian Nuta 
> Hi, git repo is at https://github.com/manticoresoftware/manticoresearch.
> 
> Right now I have debhelper (>= 11), but previous used debhelper-compat (=
> 11), same message.

[ Comments below are about commit 0f016406 ---
  remote HEAD at time of writing ]

Can't help about debhelper, because I failed to find .orig.tar.gz.
You have neither `debian/watch' nor `upstream' branch. I suggest you

 * add `debian/watch' file (very desirable)
 * take a look at `git-buildpackage' manual. Just one of many tools,
   but very fine tool, IMHO.

In mean time,

 * debian/control indented strangely. Maybe wrap-and-sort(1) from devscripts?

 * there is no point in such overrides:

override_dh_auto_build:
dh_auto_build

   overrides are used when you want to perform some actions before/after
   default, provided by debhelper.

  * Using output of `lsb_release' in CPP flags could be issue for
reproducibility. Is it strictly necessary?

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-12-07 16:39] Adrian Nuta 
> Switched to quilt, but I don't understand why mentor lintian says "No
> compatibility level set!"

Can you please remind, where are git sources of your package?

I could be that mentor lintian is old and does not recognize

Build-Depends: debhelper-compat (= 11)

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[ Top posting is discouraged ]


[2018-11-27 21:11] Adrian Nuta 
>  * Since this package is not debian-specific, and have its own release
>process, package must be foreign (with -1 revision), not native.
> changed to 1.0, not sure if this is correct

No. Source format 1.0 is long deprecated. You want to use 3.0 (quilt).

And, by the way, where is the source of debianization?

While not strictly mandatory, Vcs-* fields are very useful. I suggest
git, obliviously.

Bug#914174: RFS: easy-rsa [ITA]

[Dmitry Bogatov]

[2018-11-20 08:45] Michele Orrù 
> 
> * Package name: easy-rsa
>   Version : 3.0.5-1
>   Upstream Author : the Open-Source OpenVPN development community
> * URL : https://github.com/OpenVPN/easy-rsa/
> * License : GPLv2
> 
> It builds those binary packages:
> 
>   easy-rsa - Simple shell based CA utility

For commit 7a17:

 * typo in `debian/control': correct is `Rules-Requires-Root'
  ^
 * FTBFS:

dh_installdocs: Cannot find (any matches for) 
"debian/README-Debian-much-features-such-wow" (tried in ., debian/tmp)

Bug#914132: RFS: cwm/6.3-1 -- lightweight and efficient window manager for X11

[Dmitry Bogatov]

[2018-11-19 18:44] James McDonald 
> It builds those binary packages:
> 
>   cwm -- lightweight and efficient window manager for X11
> [...]
> 
>   dget -x https://mentors.debian.net/debian/pool/main/c/cwm/cwm_6.3-1.dsc

404.

Bug#913091: RFS: scdoc/1.5.2-1

[Dmitry Bogatov]

[2018-11-08 21:43] Birger Schacht 
> > Here is my review for commit (6b2f11).
> 
> Thanks for your feedback! I've adjusted the files accordingly, pushed
> dddbe9 to salsa and uploaded a new package to mentors.

Fine. Uploaded.

Let me suggest you to put tags like 'debian/1.5.2-1' after package hit
sid. Otherwise, if your sponsor or ftp-team ask you to make any changes,
you end with either wrong tag or tag rewriting.

Bug#913091: RFS: scdoc/1.5.2-1

[Dmitry Bogatov]

[2018-11-06 22:03] Birger Schacht 
> Dear mentors,
> 
> I am looking for a sponsor for my package "scdoc"
> 
> * Package name : scdoc
>   Version  : 1.5.2-1
>   Upstream Author  : Drew DeVault
> * Url  : https://git.sr.ht/~sircmpwn/scdoc
> * Licenses : MIT
>   Programming Lang : C
>   Section  : text
> 
>  scdoc is a tool designed to make the process of writing man pages more
>  friendly. It reads scdoc syntax from stdin and writes roff to stdout,
>  suitable for reading with *man*(1).
>  scdoc is a build dependency for swaywm.

Here is my review for commit (6b2f11).

What stops me from uploading


 * I believe using *such* notation in package description is bad idea;
   it is confusing to those, who are not accustomized to markdown, and
   is not processed specially by tools.

 * There is unused comment in `debian/watch'

 * There is commented debian/source/local-options

Minor suggestions
-

 * Consider adding 'Upstream-Author' into `debian/copyright'

 * You may want add 'Rules-Requires-Root: no' field into `debian/control'

 * I prefer use of parensis: (Closes: #00)

Re: Salsa repository request

[Dmitry Bogatov]

[2018-11-05 15:38] Thomas Perret 
>
> part 1.1   text/plain1182
> Dear mentors,
> 
> I'm currently preparing packaging of paperwork[0] which depends on a few
> package I'm also packaging[1-4].
> I'm not sure if this is a good idea but would it be possible to create a
> group or subgroup (is it necessary a team?) named openpaperwork which
> would contain the following empty repositories:

There is self-service: signup.salsa.debian.org

Bug#912736: RFS: apt-listbugs/0.1.25

[Dmitry Bogatov]

[2018-11-03 11:11] "Francesco Poli (wintermute)" 
> Hello everybody,
> my usual sponsor has some blocking issues and is currently unable to
> upload packages on my behalf.
>
> I prepared a new version of apt-listbugs (0.1.25): it is ready to be
> uploaded.
> Could someone please build the package from commit
> [999e167ed8a45ce97283977ec534657b90d808fe],
> and sponsor its upload to sid?

Sure. Uploaded. Please consider makeing dep-5 `debian/copyright'.
Since you seems to be sole author, it should not be hard.

Bug#902324: RFS: zeyple/1.2.2-3 [ITP]

[Dmitry Bogatov]

Next batch of notes:

 * Please remove 'this manual page documents briefly the zeyple
   command' and paragraph after this in manpage. It adds no information;
   after all, if I type `man foo', I know that I will receive manual for
   `foo'

 * There is no need to build-depends on `debhelper' if you
   build-depends on `debhelper-compat'.

 * Issue with cleaning after build seems to persist. This time
   time `zeyple/.pytest_cache/v/cache/nodeids' is not cleaned.

   Please note that I do not claim, that this is only file not cleaned
   properly, I just quote error dpkg-buildpackage gives me right now.

 * Please investigate, whether shebang patch is really needed. If not,
   I propose to drop it. Not really essential, but less patches -- less
   work.

 * Purely matter of style. Maybe it worth to avoid duplication in
   debian/rules with Make functions? I am perfectly fine, if you prefer
   it this way.

It seems you make force pushes into master. For now, it is okay, but
note that rewriting history after it become public (e.g after upload) is
very disruptive for other (prospective?) contributors.

Bug#912201: RFS: manticore/2.7.3 [ITP]

[Dmitry Bogatov]

[2018-10-29 09:39] Manticore Search Maintainers 
>   I am looking for a sponsor for my package "manticore"
> dget -x 
> https://mentors.debian.net/debian/pool/main/m/manticore/manticore_2.7.3.dsc

As time of writing (Mon Oct 29 20:44:20 UTC 2018), I see following
issues with package on mentors:

 * Since this package is not debian-specific, and have its own release
   process, package must be foreign (with -1 revision), not native.
 * I have no idea what -DDISTR_BUILD=jessie means, but it looks
   suspicious. New packages are built in sid environment, which in
   future will become stretch release.
 * compat=11 implies --parallel. No need to mention it in `debian/rules'
 * Policy version is old. Current is 4.2.1
 * You claim compat=11, but build-depends on debhelper >= 10. You'd
   better use new style: build-depends on `debhelper-compat (=11)' and
   remove `debian/compat'. See debhelper(7)
 * Maintainer could be a mailing list, but upload is always done by
   human, who is mentioned in `debian/changelog'.
 * Your build system tries to download dependencies. It is wrong. You
   have to declare dependencies in `debian/control' and make sure that
   build success without network access. `unshare -rn' could be of use,
   as more complex sbuild/pbuild solutions.

I will stop here for now.

-- 
Best regards, Dmitry Bogatov, a Debian Developer.

Note, that I fetch/send email at most once every 24 hours. In case of
emergency, use Signal (+7 985 316 75 70) to message/call.

Bug#902324: RFS: zeyple/1.2.2-3 [ITP]

[Dmitry Bogatov]

// removed items that I have no comments on.
[2018-10-27 20:12] Piper McCorkle 
> >  * Build-depend on debhelper >= 11~ (mind the tilde). Be nice to
> >backporters.

Just recently discovered, that debhelper introduced new syntax for
compat: Build-Depends: debhelper-compat (= 11), and `debian/compat'
is no longer used. Not significant, just FYI. See debhelper(7).

> >  * There seems to be typos in zeyple.1
> I can't seem to find any typos, could you give an example?

Sure.

 * In BUGS section, https:// part of URL to upstream bugtracker seems
   ito be missing.
 * In FILES section, `/etc/foo.conf' is referenced. I believe it have
   to be `/etc/zeyple.conf'
 * DESCRIPTION section is rather non-informative. Maybe you could use
   something from README on github?
 * According to `zeyple/zeyple.py:278', SYNOPSIS should a least mention

zeyplin [recepient ...]

There is also following issues, I did not noticed last time
{or they did not exist}

  * Your identities in debian/control and debian/changelog differs.
Debian tools compare not only emails, but full name too.
  * You build-depends on dh-exec, but seems to not actually use it.
  * You package does not build twice, since `dh_clean' does not
clean __pycache__ after previous build. Consider something like

override_dh_auto_clean:
dh_auto_clean
rm -r tests/__pycache__ zeyple/__pycache__

debhelper automatically manages this for packages, that use
setuputils. Probably worth discussing with upstream?
  * It seems that zeyple is new package. So it must have revision -1
and you have to remove all entries for next revisions. Revision
reflects changes between versions, uploaded into Archives.

  * Urgency of new packages is always low (`debian/changelog':23)

All above apply to commit b6c366.

Bug#910608: RFS: libtheft/0.4.5-1 ITP #910296

[Dmitry Bogatov]

[2018-10-23 23:53] Richard Ipsum 
> Fixed remaining issues, sorry this took me a while to get to.
> I have uploaded a new version of the package to mentors.

Looks incredible clean, but I still found one issue :)

The package your does not follow multiarch path conventions.
For example, for libyaml-dev

/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libyaml.a
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/yaml-0.1.pc
/usr/lib/x86_64-linux-gnu/libyaml.so

Since the package does not use autotools, I am afraid you will have to
tinker with `override_dh_autoinstall' manually.

Bug#902324: RFS: zeyple/1.2.2-3 [ITP]

[Dmitry Bogatov]

control: owner -1 kact...@debian.org

[2018-06-24 20:54] Zebulon McCorkle 
> part 1 text/plain1032
> Package: sponsorship-requests
> Severity: wishlist
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "zeyple"
> zeyple - Automatically encrypt outgoing emails

I like idea of this package, so below is my review; mind you I do not
host any Postfix servers, so I did not checked that it actually works.

 * Standards-Version: 4.2.1
 * cp zeyple/zeyple.py zeyple/zeyple fails on second invocation of
   dpkg-buildpackage. Either (in decreasing order of preference)

 + use dh-exec, which allow you to install and rename
 + add file into 'debian/clean'
 + use 'cp -f'
 * Build-depend on debhelper >= 11~ (mind the tilde). Be nice to
   backporters.
 * Seems that source is written to be compatible with both python3 and
   python2. If it true, use python3 dependencies.
 * In postinst you create user, but never removes it. Please fix it.
   Consider using dh-sysuser, which tries to automate bookkeeping of
   system users.
 * You seems to run upstream tests as autopkgtest. Any chance to run it
   at build time?
 * There seems to be typos in zeyple.1
 * Maybe it is just my ignorance, but I do not understand reason for the
   patch. Mind to write dep-3 description?

Bug#899175: RFS: mini-httpd-run/1.0 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "mini-httpd-run"

* Package name : mini-httpd-run
  Version  : 1.0
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/iu-guest/mini-httpd-run
* Licenses : GPL-3+
  Programming Lang : 
  Section  : admin

 mini-httpd implements all basic features of a HTTPD, including: GET,HEAD,POST
 methods, common MIME types, basic authentication, virtual hosting, CGI,
 directory listing, trailing-slash redirection, standard logging, custom error
 pages etc. It also can be configured to do SSL and IPv6.
 .
 This package contains scripts to run mini-httpd under Runit
 supervision system.

It builds those binary packages:

  * mini-httpd-run

More information about mini-httpd-run can be obtained from
https://salsa.debian.org/iu-guest/mini-httpd-run


Regards,
  Dmitry Bogatov

Bug#899174: RFS: tup/0.7.6-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : tup
  Version  : 0.7.6-1
  Upstream Author  : 2005-2016 Mike Shal <mar...@gmail.com>
* Url  : http://gittup.org/tup
* Licenses : BSD-2-clause,GPL-2+,public-domain,BSD-1-clause,BSD-3-clause
  Programming Lang : 
  Section  : devel

 Tup is a file-based build system for Linux, OSX, and Windows. It
 takes as input a list of file changes and a directed acyclic graph
 (DAG). It then processes the DAG to execute the appropriate commands
 required to update dependent files. Updates are performed with very
 little overhead since tup implements powerful build algorithms to
 avoid doing unnecessary work. This means you can stay focused on your
 project rather than on your build system.

It builds those binary packages:

  * tup

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).

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/tup.git tup
  $ cd tup
  $ origtargz
  $ dgit sbuild


Regards,
  Dmitry Bogatov

Bug#896455: RFS: cdist/4.8.4-1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : cdist
  Version  : 4.8.4-1
  Upstream Author  : Nico Schottelius <nico-debian-cd...@schottelius.org>
* Url  : http://www.nico.schottelius.org/software/cdist/
* Licenses : GPL-3,GPL-3+
  Programming Lang : Python
  Section  : admin

 cdist is a usable configuration management system.
 It adheres to the KISS principle and is being used in
 small up to enterprise grade environments. It has the
 following noteworthy features:
 .
  * shell scripting configuration language
  * access to all control structures (if, case, for, while)
  * idempotent target properties
  * zero-dependencies: target system need only /bin/sh and ssh
  * push-based distribution
  * highly-scalable
 .
 cdist is an alternative to other configuration management systems
 like cfengine, bcfg2, chef and puppet.

It builds those binary packages:

  * cdist
  * cdist-doc

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/cdist/4.8.4-1

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).

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/cdist.git cdist
  $ cd cdist
  $ origtargz
  $ dgit sbuild

Changes since last upload:

  * New upstream release
  * Drop patch-fix-spelling-errors-in-manpages.patch (applied upstream)
  * Update standards version to 4.1.4 (no changes needed)
  * Explicitly add /sbin:/usr/sbin to PATH when executing remote code.
Without this change some types fail when ssh server is dropbear, not
openssh.

Regards,
  Dmitry Bogatov

Bug#896163: RFS: runit/2.1.2-12

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : runit
  Version  : 2.1.2-12
  Upstream Author  : Gerrit Pape <p...@smarden.org>
* Url  : http://smarden.org/runit/
* Licenses : BSD-3-clause
  Programming Lang : C
  Section  : admin

 runit is a collection of tools to provide system-wide service supervision
 and to manage services.  Contrary to sysv init, it not only cares about
 starting and stopping services, but also supervises the service daemons
 while they are running.  Amongst other things, it provides a reliable
 interface to send signals to service daemons without the need for pid-files,
 and a log facility with automatic log file rotation and disk space limits.
 .
 runit service supervision can run under sysv init or replace the init
 system completely.  Complete init replacement provided by 'runit-init'
 package.

It builds those binary packages:

  * runit
  * runit-systemd
  * runit-sysv
  * getty-run
  * runit-init

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/runit/2.1.2-12

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/runit-team/runit.git runit
  $ cd runit
  $ origtargz
  $ dgit sbuild

Changes since last upload:

  * Improve 'contrib/1' to support boot in single mode. (Closes: #895914)
+ Thanks: Lorenzo Puliti <lorenzo.r...@gmail.com>
  * Simplify code (in particular, debian/rules), generating getty runscripts.
  * Improve getty runscripts to not waste CPU when tty is already busy.
(Closes: #895904)
 + Thanks: Lorenzo Puliti <lorenzo.r...@gmail.com>

Regards,
  Dmitry Bogatov

Bug#895848: RFS: inotify-tools/3.14-5

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inotify-tools"

* Package name : inotify-tools
  Version  : 3.14-5
  Upstream Author  : Radu Voicilas <rvoici...@gmail.com>
* Url  : https://github.com/rvoicilas/inotify-tools/wiki/
* Licenses : LGPL-2.1+,GPL-2.1+
  Programming Lang : C
  Section  : misc

 Inotify is a Linux kernel feature enabling user space programs to
 monitor parts of the filesystem in a efficient way. libinotifytools
 is a thin layer on top of the kernel interface which makes it easy
 to set up watches on many files at once, read events without having
 to deal with low-level I/O, and several utility functions for inotify-
 related string formatting

It builds those binary packages:

  * libinotifytools0
  * libinotifytools0-dev
  * inotify-tools

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/inotify-tools/3.14-5
To access further information about this package, visit the following URL:

https://mentors.debian.net/package/inotify-tools

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/i/inotify-tools/inotify-tools_3.14-5.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/iu-guest/inotify-tools.git

More information about inotify-tools can be obtained from
https://github.com/rvoicilas/inotify-tools/wiki/


Changes since last upload:

  * Disable sanitize build flags (Closes: #895811)

Regards,
  Dmitry Bogatov

Bug#895684: RFS: dh-runit/2.7.2

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dh-runit"

* Package name : dh-runit
  Version  : 2.7.2
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/runit-team/dh-runit
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-runit provides a debhelper sequence addon named 'runit' and the
 dh_runit command.
 .
 The dh_runit command installs runscripts and adds the appropriate code to
 the postinst, prerm and postrm maint scripts to properly enable/disable
 runscripts.

It builds those binary packages:

  * dh-runit
  * runit-helper

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/runit-team/dh-runit.git

More information about dh-runit can be obtained from
https://salsa.debian.org/runit-team/dh-runit

Changes since last upload:

  * Invoke runit-helper only if it is available. It ensures, that in
pathological case, when it isn't (piuparts), postrm script do not fail.
  * Bump compat version to 11 (no changes needed)
  * Update standards version to 4.1.4 (no changes needed)

Regards,
  Dmitry Bogatov

Bug#895668: RFS: runit/2.1.2-11

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : runit
  Version  : 2.1.2-11
  Upstream Author  : Gerrit Pape <p...@smarden.org>
* Url  : http://smarden.org/runit/
* Licenses : BSD-3-clause
  Programming Lang : 
  Section  : admin

 runit is a collection of tools to provide system-wide service supervision
 and to manage services.  Contrary to sysv init, it not only cares about
 starting and stopping services, but also supervises the service daemons
 while they are running.  Amongst other things, it provides a reliable
 interface to send signals to service daemons without the need for pid-files,
 and a log facility with automatic log file rotation and disk space limits.
 .
 runit service supervision can run under sysv init or replace the init
 system completely.  Complete init replacement provided by 'runit-init'
 package.

It builds those binary packages:

  * runit
  * runit-systemd
  * runit-sysv
  * getty-run
  * runit-init

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/runit/2.1.2-11
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: https://salsa.debian.org/runit-team/runit.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/runit-team/runit.git runit
  $ cd runit
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild


Changes since last upload:

  * Install contrib/runscript into share/doc, since
  + /usr/bin/runscripts conflicts with bin:minicom (Closes: #895607)
  + it is not part of runit suite, it is auxiliary script
  * Improve contrib/runscript (Closes: #873836)
  + fix typo: unprivilleged -> unprivileged
  + ensure that nested runsv processes are not left unmanaged
- Thanks: chrysn <chr...@fsfe.org>
  * Remove debugging code from runit.preinst (Closes: #881357)

Regards,
  Dmitry Bogatov

Bug#895203: RFS: sent/1-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : sent
  Version  : 1-1
  Upstream Author  : Markus Teich <markus.te...@stusta.mhn.de>
* Url  : http://tools.suckless.org/sent
* Licenses : ISC
  Programming Lang : C
  Section  : misc

 sent does not need LaTeX, libreoffice or any other fancy file format,
 it uses plaintext files to describe the slides and can include images
 via farbfeld.  Every paragraph represents a slide in the
 presentation.
 .
 The presentation is displayed in a simple X11 window. The content of
 each slide is automatically scaled to fit the window and centered so
 you also don't have to worry about alignment. Instead you can really
 concentrate on the content.

It builds those binary packages:

  * sent

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/sent/1-1
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: https://salsa.debian.org/iu-guest/sent.git
  Git branch: dgit/sid

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/sent.git sent
  $ dgit sbuild


Regards,
  Dmitry Bogatov

Bug#893904: RFS: dh-sysuser/1.3.2

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dh-sysuser"

* Package name : dh-sysuser
  Version  : 1.3.2
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/runit-team/dh-sysuser
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-sysuser provides a debhelper sequence addon named 'sysuser'
 and command 'dh_sysuser', which provide declarating way to
 ensure, that required users are present after package installation
 and correctly handled after package removal.

It builds those binary packages:

  * dh-sysuser
  * sysuser-helper

This package succesfully builds on debomatic machine:

  http://debomatic-i386.debian.net/distribution#unstable/dh-sysuser/1.3.2

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/runit-team/dh-sysuser.git

More information about dh-sysuser can be obtained from
https://salsa.debian.org/runit-team/dh-sysuser

Changes since last upload:

  * Remove user on purge, not remove (Closes: #848239)
+ Thanks: Antoine Beaupré <anar...@debian.org>

Regards,
  Dmitry Bogatov

Bug#893422: RFS: cdist/4.8.3-1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : cdist
  Version  : 4.8.3-1
  Upstream Author  : Nico Schottelius <nico-debian-cd...@schottelius.org>
* Url  : http://www.nico.schottelius.org/software/cdist/
* Licenses : GPL-3+,GPL-3
  Programming Lang : Python
  Section  : admin

 cdist is a usable configuration management system.
 It adheres to the KISS principle and is being used in
 small up to enterprise grade environments. It has the
 following noteworthy features:
 .
  * shell scripting configuration language
  * access to all control structures (if, case, for, while)
  * idempotent target properties
  * zero-dependencies: target system need only /bin/sh and ssh
  * push-based distribution
  * highly-scalable
 .
 cdist is an alternative to other configuration management systems
 like cfengine, bcfg2, chef and puppet.

It builds those binary packages:

  * cdist
  * cdist-doc

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/cdist/4.8.3-1

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: https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git 
cdist
  $ cd cdist
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild

Changes since last upload:

  * New upstream release
  * Refresh 'do-not-assume-git-checkout.patch'
  * Update debian/copyright
  * Use secure protocol when referring to copyright format uri.
  * Update standards version to 4.1.3 (no changes needed)
  * Update debhelper version to 11 (no changes needed)
  * Install examples of alternative scp/ssh commands

Regards,
  Dmitry Bogatov

Bug#892924: RFS: gdbm/1.14.1-6

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : gdbm
  Version  : 1.14.1-6
  Upstream Author  : bug-g...@gnu.org
* Url  : https://gnu.org/software/gdbm
* Licenses : GPL-3+,GFDL-1.3+
  Programming Lang : C
  Section  : libs


 GNU dbm ('gdbm') is a library of database functions that use extendible
 hashing and works similarly to the standard UNIX 'dbm' functions.
 .
 The basic use of 'gdbm' is to store key/data pairs in a data file, thus
 providing a persistent version of the 'dictionary' Abstract Data Type
 ('hash' to perl programmers).

It builds those binary packages:

  * libgdbm5
  * gdbm-l10n
  * libgdbm-dev
  * gdbmtool
  * libgdbm-compat4
  * libgdbm-compat-dev

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/gdbm/1.14.1-6

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: https://salsa.debian.org/iu-guest/gdbm.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/gdbm.git gdbm
  $ cd gdbm
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild

Changes since last upload:

  * Fix description of libgdbm-compat4 binary package (Closes: #892846)
+ Thanks: Vincent Lefevre <vinc...@vinc17.net>

Regards,
  Dmitry Bogatov

Bug#892634: RFS: dh-runit/2.7.1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

!Just recently I got upload to experimental recently.
 I am sorry, I meant unstable!

Dear mentors,

I am looking for a sponsor for my package "dh-runit"

* Package name : dh-runit
  Version  : 2.7.1
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/runit-team/dh-runit
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-runit provides a debhelper sequence addon named 'runit' and the
 dh_runit command.
 .
 The dh_runit command installs runscripts and adds the appropriate code to
 the postinst, prerm and postrm maint scripts to properly enable/disable
 runscripts.

It builds those binary packages:

  * dh-runit
  * runit-helper

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/dh-runit/2.7.1
To access further information about this package, visit the following URL:

https://mentors.debian.net/package/dh-runit

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.7.1.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/runit-team/dh-runit.git

More information about dh-runit can be obtained from
https://salsa.debian.org/runit-team/dh-runit


Changes since last upload:

  * Upload to unstable.

Regards,
  Dmitry Bogatov

Bug#892581: RFS: dh-sysuser/1.3.1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dh-sysuser"

* Package name : dh-sysuser
  Version  : 1.3.1
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/runit-team/dh-sysuser
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-sysuser provides a debhelper sequence addon named 'sysuser'
 and command 'dh_sysuser', which provide declarating way to
 ensure, that required users are present after package installation
 and correctly handled after package removal.

It builds those binary packages:

  * dh-sysuser
  * sysuser-helper

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/dh-sysuser/1.3.1
To access further information about this package, visit the following URL:

https://mentors.debian.net/package/dh-sysuser

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/d/dh-sysuser/dh-sysuser_1.3.1.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/runit-team/dh-sysuser.git

More information about dh-sysuser can be obtained from
https://salsa.debian.org/runit-team/dh-sysuser


Changes since last upload:

  * Fix description of sysuser-helper package: s/it's/its. (Closes: #844342)
+ Thanks: Toby Speight <t.m.speight...@cantab.net>
  * Remove system user without home directory at package uninstall. If
there is no home directory, it seems safe to assume that no files
belong to that user, and removing that user will not cause harm.
  * Create system users with /usr/sbin/nologin as shell.
  * Do not impose dependency on bin:adduser. It is unneeded, since
bin:sysuser-helper uses useradd(8), which is provided by bin:passwd,
with is of required priority.
  * Document in manpage, that sysuser-helper delegates its job to useradd(8)
(Closes: #848240)
  * Remove useless account locking in prerm.
  * Ensure that content of /etc/skel is not copied into home directory.
  * Update Vcs-* and Homepage fields in debian/control.
  * Update standards version to 4.1.3 (no changes needed)
  * Bump compat version to 11 (no changes needed)
  * Document and implement login, that system user is removed
when it has either empty home directory or none at all (Closes: #848239)

Regards,
  Dmitry Bogatov

Bug#892580: RFS: dh-runit/2.7

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dh-runit"

* Package name : dh-runit
  Version  : 2.7
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : https://salsa.debian.org/runit-team/dh-runit
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-runit provides a debhelper sequence addon named 'runit' and the
 dh_runit command.
 .
 The dh_runit command installs runscripts and adds the appropriate code to
 the postinst, prerm and postrm maint scripts to properly enable/disable
 runscripts.

It builds those binary packages:

  * dh-runit
  * runit-helper

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/dh-runit/2.7
To access further information about this package, visit the following URL:

https://mentors.debian.net/package/dh-runit

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/d/dh-runit/dh-runit_2.7.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/runit-team/dh-runit.git

More information about dh-runit can be obtained from
https://salsa.debian.org/runit-team/dh-runit


Changes since last upload:

  * Change naming of generated system users for logging to start
with underscore.
  * Add missing dependency on dh-sysuser.
  * Improve readability of code, generating /etc/sv//log/run
script using here-doc notation.
  * Remove 'logdir' option for simplicity sake. Strictly speaking it is
backward-incompatible change, hence the version major bump, but I am
unaware of any actual users of this option.
  * Ensure that after package removal logs belong to root.
  * Introduce new binary package 'runit-helper', allowing packages to
access fixes and improvements in 'dh-runit' without rebuild.
  * Update Vcs-* and Homepage fields in debian/control.

Regards,
  Dmitry Bogatov

Bug#892579: RFS: runit/2.1.2-10

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : runit
  Version  : 2.1.2-10
  Upstream Author  : Gerrit Pape <p...@smarden.org>
* Url  : http://smarden.org/runit/
* Licenses : BSD-3-clause
  Programming Lang : 
  Section  : admin

 runit is a collection of tools to provide system-wide service supervision
 and to manage services.  Contrary to sysv init, it not only cares about
 starting and stopping services, but also supervises the service daemons
 while they are running.  Amongst other things, it provides a reliable
 interface to send signals to service daemons without the need for pid-files,
 and a log facility with automatic log file rotation and disk space limits.
 .
 runit service supervision can run under sysv init or replace the init
 system completely.  Complete init replacement provided by 'runit-init'
 package.

It builds those binary packages:

  * runit
  * runit-systemd
  * runit-sysv
  * getty-run
  * runit-init

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/runit/2.1.2-10
 
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: https://salsa.debian.org/runit-team/runit.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/runit-team/runit.git runit
  $ cd runit
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild


Changes since last upload:

  * Replace DEB_BUILD_OPTIONS with DEB_BUILD_MAINT_OPTIONS, since the former
is meant for user, rebuilding package and overrides the latter.
  + Thanks: Gianfranco Costamagna <locutusofb...@debian.org>
  * Add 'runscript' program into 'runit' binary package, intended to
simplify for system administrator management of per-user 'runsvdir'
processes.
  * Incorporate NMU. Bring back runit-init package.
  * Add compiler flags for large file support.
  * Add support for sysvinit control pipe into shutdown script, solving issue
with reboot just after runit-init installation. (Closes: #861536)
  * Add dependency on initscripts. While initscripts probably could be
simplified, right now it is simpler to rely on it to make sure, that
transition from sysvinit is smooth. On other hand, if both runscript
and initscript are present, runscript is favored.
  * Write CFLAGS and LDFLAGS into conf-ld/conf-cc. Without it, upstream
build system strips binaries, wasting precious debug information that
must be stored in -dbg symbols.
  * Check for executable bit on /run/runit.reboot with stat(1), not
test(1).  If /run is mounted with 'noexec' option, test(1) gives
unexpected results.
  * Reduce timeout between SIGTERM and SIGKILL on system shutdown.

Default 7 seconds is reasonable for well-behaving program, and waiting
longer does not help with programs, which ignore SIGTERM, like
startx(1) in some configurations.
  * Fix problem with bash completion script when ls(1) output color control
sequences.
  * Update Vcs-* fields in debian/control. Now on GitLab instance at
salsa.debian.org
  * Bump compat version to 11, rendering dh-sysuser unneeded.
  * Drop explicit --parallel from debian/rules, since it is default since
debhelper-10.
  * Use secure URL when referencing to debian/copyright format.
  * Bump standards version to 4.1.3 (removed priority 'extra')
  * Remove version conflicts on sysvinit, since it is no longer present
in Archives.

Regards,
  Dmitry Bogatov

Bug#891005: RFS: gdbm/1.14.1-5

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

!Important! This upload re-enables diet libc support {conditional, via
build profiles}. Input from developers, experienced with Debian
bootstrap is very, very welcome.

Dear mentors,

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

* Package name : gdbm
  Version  : 1.14.1-5
  Upstream Author  : bug-g...@gnu.org
* Url  : https://gnu.org/software/gdbm
* Licenses : GPL-3+,GFDL-1.3+
  Programming Lang : C
  Section  : libs

 GNU dbm ('gdbm') is a library of database functions that use extendible
 hashing and works similarly to the standard UNIX 'dbm' functions.
 .
 The basic use of 'gdbm' is to store key/data pairs in a data file, thus
 providing a persistent version of the 'dictionary' Abstract Data Type
 ('hash' to perl programmers).

It builds those binary packages:

  * libgdbm5
  * gdbm-l10n
  * libgdbm-dev
  * gdbmtool
  * libgdbm-compat4
  * libgdbm-compat-dev

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/gdbm/1.14.1-5
 
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: https://salsa.debian.org/iu-guest/gdbm.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/gdbm.git gdbm
  $ cd gdbm
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild

Changes since last upload:

  * Update Vcs-* fields in debian/control.
  * Bump compat version to 11 (no changes needed)
  * Enable dietlibc build, unless pkg.gdbm.nodietlibc profile is in effect.
  * Change section of bin:gdbm-l10n to 'localization'
  * Fix spelling error on manpage
  * Enable large file support

Regards,
  Dmitry Bogatov

Bug#890666: RFS: mmh/0.3-3

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : mmh
  Version  : 0.3-3
  Upstream Author  : markus schnalke <mei...@marmaro.de>
* Url  : http://marmaro.de/prog/mmh/
* Licenses : BSD-3-clause
  Programming Lang : C
  Section  : mail

 This is the mmh mail user agent (reader/sender), a command-line based mail
 reader that is powerful and extensible.  mmh is an excellent choice for
 people who receive and process a lot of mail.
 .
 Unlike most mail user agents, mmh is not a single program, rather it is a
 set of programs that are run from the shell.  This allows the user to
 utilize the full power of the Unix shell in coordination with mmh.
 .
 Mmh is a modified version of the electronic mail handling system nmh.
 Nmh (new MH) itself was originally based on the package MH-6.8.3, and
 was intended to be a (mostly) compatible drop-in replacement for MH.
 In contrast, mmh is not intended to be a drop-in replacement for nmh,
 rather mmh breaks compatibility to nmh in order to modernize and
 simplify it.

It builds those binary packages:

  * mmh

This package succesfully builds on debomatic machine:

  https://debomatic-i386.debian.net/distribution#unstable/mmh/0.3-3
 
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: https://salsa.debian.org/iu-guest/mmh.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/mmh.git mmh
  $ cd mmh
  $ make -f debian/rules get-orig-source # 'gbp buildpackage' is fine
  $ dgit sbuild


Changes since last upload:

  * Update Vcs-* fields in debian/control.
  * Compile with large file support
  * Update standards version to 4.1.3 (no changes needed)
  * Bump compat version to 11 (added explicit --no-parallel, since upstream
build system does not use Automake and is not parallel-safe)
  * Remove useless build-dependency on dh-autoreconf, which is implied by
debhelper (>= 10)
  * Fix incorrect reference to nmh in description
  * Replace generic BSD-3-clause with specific version from COPYRIGHT file in
debian/copyright due request of upstream author.
  * Patch config/version.sh to not insert non-reproducible data into binaries

Regards,
  Dmitry Bogatov

Bug#890437: RFS: fgetty/0.7-3

[Dmitry Bogatov]

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 <felix-fge...@fefe.de>
* Url  : https://www.fefe.de/fgetty
* 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:

  https://debomatic-i386.debian.net/distribution#unstable/fgetty/0.7-3
 
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: https://salsa.debian.org/iu-guest/fgetty.git
  Git branch: master

With /bin/sh following commands should suffice:

  $ git clone https://salsa.debian.org/iu-guest/fgetty.git 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
  * Use DEB_BUILD_MAINT_OPTIONS instead DEB_BUILD_OPTIONS. Later
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

Regards,
  Dmitry Bogatov

Bug#889968: RFS: inotify-tools/3.14-4

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inotify-tools"

* Package name : inotify-tools
  Version  : 3.14-4
  Upstream Author  : Radu Voicilas <rvoici...@gmail.com>
* Url  : https://github.com/rvoicilas/inotify-tools/wiki/
* Licenses : GPL-2.1+,LGPL-2.1+
  Programming Lang : C
  Section  : misc

 Inotify is a Linux kernel feature enabling user space programs to
 monitor parts of the filesystem in a efficient way. libinotifytools
 is a thin layer on top of the kernel interface which makes it easy
 to set up watches on many files at once, read events without having
 to deal with low-level I/O, and several utility functions for inotify-
 related string formatting

It builds those binary packages:

  * libinotifytools0
  * libinotifytools0-dev
  * inotify-tools

To access further information about this package, visit the following URL:

https://mentors.debian.net/package/inotify-tools

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/i/inotify-tools/inotify-tools_3.14-4.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://salsa.debian.org/iu-guest/inotify-tools.git

More information about inotify-tools can be obtained from
https://github.com/rvoicilas/inotify-tools/wiki/


Changes since last upload:

  * Upload to unstable
  * Enable all paranoid options of dpkg-buildflags(1)
  * Mark packages as multiarch-compatible (Closes: #875462)
  * Update Vcs-* fields in debian/control.
  * Update standards version to 4.1.3 (no changes needed)
  * Drop explicit dependency on autotools (implied by debhelper-10)
  * Use secure URL when referencing to copyright-format
  * Remove lintian-override about embedded javascript library.
Lintian now knows, that there is nothing can be done in case of
Doxygen.
  * Add sanity-check symbols into symbols file.

Regards,
  Dmitry Bogatov

Bug#858531: RFS: delight/1.5-1 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : delight
  Version  : 1.5-1
  Upstream Author  : Phil Sainty <psai...@orcon.net.nz>
* Url  : https://savannah.nongnu.org/projects/delight
* Licenses : GPL-3+
  Programming Lang : Emacs Lisp
  Section  : lisp

 Emacs add-on 'delight' provides functionality to customise the
 mode names displayed in the mode line.
 .
 For major modes, the buffer-local `mode-name' variable is modified.
 For minor modes, the associated value in `minor-mode-alist' is set.

It builds those binary packages:

  * elpa-delight

To access further information about this package, visit the following URL:

https://mentors.debian.net/package/delight

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/d/delight/delight_1.5-1.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://anonscm.debian.org/git/pkg-emacsen/pkg/delight.git

More information about delight can be obtained from
https://savannah.nongnu.org/projects/delight

Regards,
  Dmitry Bogatov

Bug#856910: RFS: inotify-tools/3.14-3

[Dmitry Bogatov]

On Wed, Mar 08, 2017 at 08:46:43AM +0300, Dmitry Bogatov wrote:
> > I need help with this. If I write
> > [...]

Thank you. It is settled. One more review, please?

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpKKnPzGor6N.pgp
Description: PGP signature

Bug#855439: RFS: cvm/0.97

[Dmitry Bogatov]

control: tag -1 -moreinfo

[2017-03-06 20:54] Sean Whitton <spwhit...@spwhitton.name>
> Dear Dmitry,
>
> On Sat, Feb 18, 2017 at 10:23:46AM +0300, Dmitry Bogatov wrote:
> > Note, that this is not full-scale modernization of package. It is just
> > a NMU, required for libbg1 -> libbg2 transition.
>
> Could you explain the background, please?  Stretch is frozen.  Have the
> release team authorized this transition?

No. It is upload into experimental

> It's rarely appropriate for an NMU to update to a new upstream version.
> If you are just performing the transition in experimental, there is no
> justification for it.

I believe I have justification for this. Previous version (cvm-0.96) is
source-incompatible with (bglibs >= 2.03).

> > Please note, that package is maintained with dgit(1) tool using
> > dgit-maint-merge(7) workflow. In particular, it means that quilt patches
> > are squashed in source package and are not intended for review. For more
> > information about how to sponsor this package, see dgit-sponsorship(7).
>
> This is not appropriate for an NMU.  Indeed, I see that you've changed
> the source format to 3.0 (quilt) -- also not appropriate for an NMU.

Well, I can revert it, but truth is that this package is maintained by
Gerrit Pape, who is not active for some years. I took over some of his
packages, but I am not interested in `cvm'. I just need to transit
bglibs, since latest version of `bcron', in which I am interested,
requires latest bglibs.

Probably this upload should be QA upload, not NMU for lack of actual
maintainer. It is any way to ask QA team to make this upload on their
behalf? Sure, I can adopt, upload and fill RFA at same time, but it
feels wrong.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgp1VXkruMg5x.pgp
Description: PGP signature

Bug#856910: RFS: inotify-tools/3.14-3

[Dmitry Bogatov]

control: tags -1 -moreinfo

[2017-03-06 20:46] Sean Whitton 
> - Your conversion of d/copyright has lost some information, by merging
>   the stanzas for McGovern and McCutchan.  If you use two separate
>   stanzas the conversion would not be lossy.

Fixed.

> - In your changelog you wrote that you bumped the std-ver.  It's
>   conventional to say what version you bumped it to.

Fixed.

> - The Lintian override could use a wildcard so that it only matches the
>   doxygen file, not any other javascript that might appear in a new
>   upstream release (unlikely though that is)

I need help with this. If I write

embedded-javascript-library usr/share/doc/libinotifytools0-dev/jquery.js

into debian/libinotify0-dev.lintian-overrides, it does not match and lintian
complains about unused override.

> - You've modified debian/*.install but this isn't in the changelog.

Fixed.

> - The dgit-maint-merge patch header has been updated to a better text.
>   Please consider using it: https://manpages.debian.org/dgit-maint-merge

Fixed.

> - Changes to d/rules not in changelog.

Fixed.

> - Just fyi: https://manpages.debian.org/git-deborig

Fine. Useful.

> Don't forget `dch -r` once you've addressed these.
>
> - you could install NEWS as the upstream changelog

No, thanks.

% cat NEWS

 * 19 October 2005
   inotify-tools begun.


> - you could add a doc-base registration

Fixed.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgplVoTdqfGuj.pgp
Description: PGP signature

Bug#856910: RFS: inotify-tools/3.14-3

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inotify-tools"

* Package name : inotify-tools
  Version  : 3.14-3
  Upstream Author  : Radu Voicilas <rvoici...@gmail.com>
* Url  : https://github.com/rvoicilas/inotify-tools/wiki/
* Licenses : LGPL-2.1+,GPL-2.1+
  Programming Lang : C
  Section  : misc

 Inotify is a Linux kernel feature enabling user space programs to
 monitor parts of the filesystem in a efficient way. libinotifytools
 is a thin layer on top of the kernel interface which makes it easy
 to set up watches on many files at once, read events without having
 to deal with low-level I/O, and several utility functions for inotify-
 related string formatting

It builds those binary packages:

  * libinotifytools0
  * libinotifytools0-dev
  * inotify-tools

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: 
https://anonscm.debian.org/cgit/users/kaction-guest/inotify-tools.git
  Git branch: master
  Orig tar.gz: from tag v3.14

With /bin/sh following commands should suffice:

  $ git clone 
https://anonscm.debian.org/cgit/users/kaction-guest/inotify-tools.git 
inotify-tools
  $ cd inotify-tools
  $ git archive -o ../inotify-tools_3.14.orig.tar.xz v3.14
  $ dgit sbuild

Changes since last upload:

  * New maintainer (Closes: #856293)
  * Convert package to dgit-maint-merge workflow (patches are squashed
in uploaded source package)
  * Bump debhelper compat to 10
  * Reformat 'debian/changelog' according to DEP-5
  * Enable hardening
  * Update Vcs-* fields
  * Bump standards version (No changes needed)
  * Add lintian override concerning embedded javascript file. It is way
how doxygen works and it can not be fixed.
  * Fix segfault with cvs output when filename contains comma (Closes: #702738)

Regards,
  Dmitry Bogatov

Bug#856631: RFS: dh-runit/2.7

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "dh-runit"

* Package name : dh-runit
  Version  : 2.7
  Upstream Author  : Dmitry Bogatov <kact...@gnu.org>
* Url  : 
https://anonscm.debian.org/cgit/users/kaction-guest/dh-runit.git
* Licenses : GPL-3+
  Programming Lang : Perl
  Section  : admin

 dh-runit provides a debhelper sequence addon named 'runit' and the
 dh_runit command.
 .
 The dh_runit command installs runscripts and adds the appropriate code to
 the postinst, prerm and postrm maint scripts to properly enable/disable
 runscripts.

It builds those binary packages:

  * dh-runit
  * runit-helper

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: 
https://anonscm.debian.org/cgit/users/kaction-guest/dh-runit.git
  Git branch: master
  Orig tar.gz: from tag 2.7

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/dh-runit.git 
dh-runit
  $ cd dh-runit
  $ git archive -o ../dh-runit_2.7.orig.tar.xz 2.7
  $ dgit sbuild

Changes since last upload:

  * Change naming of generated system users for logging to start
with underscore.
  * Add missing dependency on dh-sysuser.
  * Improve readability of code, generating /etc/sv//log/run
script using here-doc notation.
  * Remove 'logdir' option for simplicity sake. Strictly speaking it is
backward-incompatible change, hence the version major bump, but I am
unaware of any actual users of this option.
  * Ensure that after package removal logs belong to root.
  * Introduce new binary package 'runit-helper', allowing packages to
access fixes and improvements in 'dh-runit' without rebuild.

Regards,
  Dmitry Bogatov

Bug#855440: RFS: bglibs/2.03+dfsg-2

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : bglibs
  Version  : 2.03+dfsg-2
  Upstream Author  : Bruce Guenter <br...@untroubled.org>
* Url  : http://untroubled.org/bglibs/
* Licenses : GPL-2+,LGPL-2+,LGPL-2.1+
  Programming Lang : C
  Section  : libs

 ${S:Long-Desc}
 .
 This package contains the shared libraries.

It builds those binary packages:

  * libbg2
  * libbg-dev
  * libbg2-doc

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git
  Git branch: master
  Orig tar.gz: from tag 2.03+dfsg

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git 
bglibs
  $ cd bglibs
  $ git archive -o ../bglibs_2.03+dfsg.orig.tar.xz 2.03+dfsg
  $ dgit sbuild

Changes since last upload:

  * QA upload
  * Remove Conflict field from libbg-dev.
  * Install build tools into libbg-dev package, since they are required
for building other packages of same upstream.
  * Fix spelling error in cli-generate.1

Regards,
  Dmitry Bogatov

Bug#855439: RFS: cvm/0.97

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : cvm
  Version  : 0.97
  Upstream Author  : Bruce Guenter <br...@untroubled.org>
* Url  : http://untroubled.org/cvm/
* Licenses : LGPL-2+,GPL-2+,LGPL-2.1+
  Programming Lang : C
  Section  : libs

 CVM is a framework for validating a set of credentials against a database
 using a filter program.  The modules act as a filter, taking a set of
 credentials as input and writing a set of facts as output if those
 credentials are valid.  Optional input is given to the module through
 environment variables.
 .
 Some of the ideas for CVM came from experience with PAM (pluggable
 authentication modules), the checkpassword interface used by qmail-pop3d,
 and the "authmod" interface used by Courier IMAP and POP3.  This framework
 places fewer restrictions on the invoking client than checkpassword does,
 and is much simpler to implement on both sides than PAM and the authmod
 framework.

Note, that this is not full-scale modernization of package. It is just a
NMU, required for libbg1 -> libbg2 transition. There is still a lot of
Lintian warnings, I know.

It builds those binary packages:

  * cvm
  * cvm-mysql
  * cvm-pgsql
  * libcvm1
  * libcvm1-dev

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt patches
are squashed in source package and are not intended for review. For more
information about how to sponsor this package, see dgit-sponsorship(7).

  Git repository: https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git
  Git branch: master
  Orig tar.gz: from tag upstream/0.97

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git 
bglibs
  $ cd bglibs
  $ git archive -o ../cvm_0.97.orig.tar.xz upstream/0.97
  $ dgit sbuild

Changes since last upload:

  * Non-maintainer upload.
  * New upstream release (compatible with bglibs >= 2.03)
  * Write watch file and verify GPG signature
  * Upgrade dependendency on bglibs (libbg1-dev -> libbg-dev >= 2.03)
  * Drop rpath related patch (fixed upstream)
  * Adjust debian/rules to changed upstream Makefile
  * Add ldconfig trigger

Regards,
  Dmitry Bogatov

Bug#855101: RFS: bcron/0.11-1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : bcron
  Version  : 0.11-1
  Upstream Author  : Bruce Guenter <bru...@em.ca>
* Url  : http://untroubled.org/bcron
* Licenses : GPL-2+
  Programming Lang : C
  Section  : admin

 ${S:Long-Desc}
 .
 This package contains the bcron programs.

It builds those binary packages:

  * bcron
  * bcron-run

To access further information about this package, visit the following URL:

https://mentors.debian.net/package/bcron

Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/b/bcron/bcron_0.11-1.dsc

Alternatively, you can access package debian/ directory via git from URL:
https://anonscm.debian.org/cgit/users/kaction-guest/bcron.git

More information about bcron can be obtained from
http://untroubled.org/bcron

Changes since last upload:

  * New upstream release
  * Force dependency on bglibs-2.*
  * Refresh patches
  * Do not assume ${USER} value in tests.sh
  * Restore default bcron-spool socket location
(Drop 0002-Spool-socket-is-var-run-.bcron-spool-instead-of-var-r.diff)
  * Enable hardening=+pie

Regards,
  Dmitry Bogatov

Bug#854212: RFS: synergy/1.8.7-stable+dfsg.1-1 [ITA]

[Dmitry Bogatov]

[2017-02-06 09:08] Arturo Borrero Gonzalez 
>
> part   text/plain 639
> On 5 February 2017 at 07:12, Joshua Honeycutt
>  wrote:
> > Alternatively, one can download the package with dget using this command:
> >
> > dget -x 
> > https://mentors.debian.net/debian/pool/main/s/synergy/synergy_1.8.7-stable+dfsg.1-1.dsc
> >
> > More information about hello can be obtained from https://www.example.com.
> >
>
>  please review a bit more the template :-)

Advertisement: use my debrequest tool 
(https://anonscm.debian.org/cgit/users/kaction-guest/debrequest.git)
 which fill in template automatically, inspecting your debian/*

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpcSsYmY7pxa.pgp
Description: PGP signature

Bug#853925: RFS: bglibs/2.03+dfsg-1

[Dmitry Bogatov]

control: tags -1 -moreinfo

[2017-02-02 18:49] Gianfranco Costamagna 
> missing licenses, e.g.
> bglibs-2.03+dfsg/include/md4.h
> md5.h

Fixed

> why not a single plain libbg-dev?
> soname in the development package is painful to maintain

Because there was libbg1-dev. But you are right. Changed.

Changes are in git, g7f72977.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpIbt8Y7UIoO.pgp
Description: PGP signature

Bug#853925: RFS: bglibs/2.03+dfsg-1

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name : bglibs
  Version  : 2.03+dfsg-1
  Upstream Author  : Bruce Guenter <br...@untroubled.org>
* Url  : http://untroubled.org/bglibs/
* Licenses : LGPL-2.1+
  Programming Lang : C
  Section  : libs

 ${S:Long-Desc}
 .
 This package contains the shared libraries.

It builds those binary packages:

  * libbg2
  * libbg2-dev
  * libbg2-doc

Please note, that package is maintained with dgit(1) tool using
dgit-maint-merge(7) workflow. In particular, it means that quilt
patches are squashed in source package and are not intended for
review. For more information about how to sponsor this package,
see dgit-sponsorship(7).

  Git repository: https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git
  Git branch: master
  Orig tar.gz: from tag 2.03.dfsg

With /bin/sh following commands should suffice:

  $ git clone https://anonscm.debian.org/cgit/users/kaction-guest/bglibs.git 
bglibs
  $ cd bglibs
  $ git archive -o ../bglibs_2.03+dfsg.orig.tar.xz 2.03.dfsg
  $ dgit sbuild

Changes since last upload:

  * QA upload
  * New upstream release
  * Add debian/watch file and associated upstream GPG key
  * Replace manual invocation of dpkg-buildflags in debian/rules
with inclusion of /usr/share/dpkg/default.mk
  * Disable network-accessing tests
  * Change binary package names, since this version of library
is both source-incompatible (headers are restructured) and
binary-incompatible (soname is chaged)
  * Convert debian/rules to debhelper
  * Rebuild doxygen documentation during build process
  * Re-enable hardening
  * Generate symbols file
  * Register documentation with doc-base

Regards,
  Dmitry Bogatov

Re: Packaging doxygen documentation

[Dmitry Bogatov]

[2017-01-28 22:43] wf...@niif.hu (Ferenc Wágner)
> Dmitry Bogatov <kact...@gnu.org> writes:
> >  - freshly rebuilt with doxygen at build time documentation again
> >contain minified JS file and Lintian again complains about it.
> > Help or experience sharing are welcome.
>
> See https://sources.debian.net/src/doxygen/1.8.8-5/debian/README.jquery/
> for some background.  I usually add a Lintian override to my
> documentation packages along the lines of:
>
> # This file is installed by Doxygen and is more than just a minimized jQuery
> # copy.  The Doxygen maintainers recommend against trying to replace it with
> # a symlink to the version in libjs-jquery.
> embedded-javascript-library usr/share/doc/*/api/html/jquery.js please use 
> libjs-jquery

Thank you. It answers my question.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpQUz4zVqZi6.pgp
Description: PGP signature